The Season Close You Can't Defend
A pool season runs for months, but a member statement has to hold up in a single conversation. When proceeds and charges aren't tied to source lots from the start, defending one number means rebuilding the whole season under pressure. A pool isn't a spreadsheet of distributions — it's a governed financial model.
A pool season runs for months before it runs out. Lots come in from different growers or members at different times, sold into different buyers at different prices. Charges accumulate against those lots the whole way through — packing, storage, freight, marketing assessments — each one supposed to land against the specific lot it belongs to.
Then the season ends, and someone has to turn all of that into a single number per member: here's what your lots earned, here's what got charged against them, here's your settlement. Usually that reconstruction happens in a spreadsheet, built fresh each season, because last season's version doesn't quite fit this season's buyer terms or charge structure.
Most of the time it holds together. Then one member questions their statement — a number looks low, a charge looks unfamiliar — and someone has to trace that specific figure back through the season: which lots, which sales, which charges, applied in what order. If the answer isn't sitting somewhere ready to be pulled up, it has to be rebuilt, under time pressure, for one member, using the same fragile process that produced the number in the first place.
Running a pool without a cooperative's back office
This problem hits differently depending on who's running the pool. A large grower-owned cooperative usually has a dedicated back office built around exactly this work. A packhouse or processor running a private pool for its growers or members usually doesn't — it's a lean finance team doing season-close work on top of everything else they're responsible for, rebuilding the allocation logic largely from memory of how it worked last time.
That's where the real risk concentrates, for a few specific reasons:
Proceeds don't arrive as one number. They arrive lot by lot, sale by sale, spread across the season, and have to be tied back to a source lot to mean anything. Lose that lineage, even in one place, and every allocation downstream of it inherits the same uncertainty.
Charges get allocated by estimate more often than by rule. A packing charge, a storage fee, a marketing assessment — each one is supposed to apply to specific lots under specific terms. Under time pressure, it's common for these to get spread proportionally as an approximation rather than calculated precisely against the rule that actually governs them, which is exactly the kind of shortcut that produces a number nobody can defend later.
Exceptions get discovered after the pool closes, not before. A lot that came in short. A shipment a buyer partially rejected. A charge posted against the wrong lot. In a well-run close, these get caught and resolved as part of closing the pool. In a rushed one, they surface afterward, as a member dispute, which is the most expensive place to find them.
A pool is not a spreadsheet of distributions. It's a governed financial model, where every member's outcome should be traceable — from the source lot and the proceeds it generated, through every charge and allocation, to the statement and settlement that closed it out.
What a defensible close actually requires
None of this needs a cooperative-scale back office to fix. It needs the close to run on structure instead of reconstruction:
Establish the pool season and participation before activity arrives — who's in the pool, on what terms, before the first lot shows up, not pieced together after the fact from whoever remembers the agreement.
Preserve source-lot and proceeds lineage through every allocation — so a dollar in a member's final statement can be traced back to the specific lot and sale that produced it, not just to a season-level total.
Route exceptions for review before the pool closes — a short lot, a rejected shipment, a misapplied charge, caught and resolved as a normal part of closing, not discovered afterward as a dispute.
Produce member statements and settlements connected to the accounting behind them — so when a member asks why their number is what it is, the answer is a lookup, not a rebuild.
Interpreting an unusual charge, investigating why one lot's numbers look off, explaining a settlement to a member who's questioning it — that's where judgment matters, and where assistance genuinely helps. The allocation math itself — what each lot earned, what got charged against it, what the member is actually owed — should run the same governed way every season, regardless of how much has changed since the last one.
A season close should hold up on its own
The measure of a good pool close isn't just that the numbers balance. It's that every one of them can be defended, on the spot, by tracing it back to where it came from — without a scramble, without a rebuild, and without asking a member to just trust a total.
That's the discipline pool accounting needs to run on: proceeds and charges tied to source lots from the start, exceptions resolved before close instead of after, and member statements that come with their own evidence attached — so the season closes once, correctly, instead of getting reopened every time someone asks a reasonable question about their own number.