There is one question that can almost always stop a monthly estate meeting in its tracks: what was this division's cost per kilogram last week? Not last month — last week. At most estates we visit, that question cannot be answered. Not because the data is missing, but because the data has not yet met itself.
Wages and bonuses sit in the foreman's tally. Fertiliser usage sits on warehouse slips. Equipment hours sit in the operator's log. Tonnage sits on the mill's weighbridge ticket. All four are correct, all four are complete, and all four only meet on an accountant's desk in the second week of the following month.
The gap is not about calculation speed
The first temptation is to conclude that the problem is processing speed — if only accounting worked faster, the number would come out faster. In our experience this is rarely true. Accounting is usually already working as fast as the shape of the data they receive allows.
The real problem is upstream: those four data sources share no common key. The foreman's tally knows worker names and section numbers. The warehouse slip knows material codes and the requester's name. The weighbridge ticket knows vehicle and dispatch note numbers. To turn all of it into a cost per kilogram for a single block, somebody has to translate the four by hand. That translation is what takes three weeks — not the arithmetic.
If four data sources cannot be joined without manual translation, your reporting speed is limited by the speed of the translator — not by the speed of the system.
It all comes back to one unit
The solution does not start with accounting software but with an agreement about the unit. On plantations that unit is almost always the block. In horticulture it is usually the planting batch or the bed. Whichever you choose, the requirement is the same: every operational transaction must carry that unit from the moment it is recorded, not have it attached later.
In practice that means four things:
- Attendance records the worker and the block they worked in that day, not just their presence.
- Material issued from the warehouse records the block it will be applied to, not just who requested it.
- Equipment hours are recorded per block worked, not per vehicle alone.
- Harvest tonnage carries its source block all the way to the weighbridge ticket, not stopping at a vehicle number.
Not one of these four requires an AI model, a sensor, or satellite imagery. They are all decisions about the shape of the record. And precisely because they are simple, this part often gets skipped — assumed settled when it is not.
The denominator people forget
Cost per kilogram has two sides, and the denominator is slipperier than people assume. Which tonnage do you use: what the foreman recorded in the field, or what the mill received?
Both are valid, and each answers a different question. Field tonnage answers how much was harvested. Mill tonnage answers how much arrived. The gap between them is information in its own right — and at many estates that gap, not the cost, is the most expensive problem.
So we suggest computing both side by side from the start rather than picking one. When the field and mill versions of cost per kilogram drift apart, that is a signal; when they move together, your number can be trusted.
What to settle first
- Fix one costing unit — block or planting batch — and use it consistently across every module.
- Make sure every transaction carries that unit as it is recorded, not attached afterwards.
- Compute field and mill tonnage side by side; the gap is information, not noise.
- Measure success by elapsed time, not by the number of reports produced.
What changes when the number is daily
The first benefit people usually name is reporting speed. To us that is the smallest one. What matters more is the change in the kind of conversation held.
When cost per kilogram only becomes visible a month later, meetings are explanations about the past. When the number is visible the same day, meetings are decisions about the week in progress: which rotation to shift, which block needs more labour, which application to postpone because of rain.
That change does not come from the dashboard. A dashboard only displays what has already been settled in the field. If upstream recording still needs manual translation, the prettiest dashboard will still be showing last month's figures.
Where to start
If you want to try, take one division and one month. Not the whole estate. Fix the costing unit, make sure the four data sources above carry it, then compute cost per hectare and per kilogram every day for a full month.
The most useful outcome of that exercise is usually not the number but the list of things that turn out not to be recorded correctly. That list is the real work.
The VarmOS cost and budget module is built on the same principle — see how the module works, or talk through your estate's cost structure with us.