A harvest-weight reconciliation should begin with a narrower question than “Where did the crop go?” Ask instead: which defined quantity is being compared, at which handover, and with which records?
A field estimate, a scale ticket and a packing record may all be valid while describing different material, different times or different weight treatments. One record may cover picked containers, another a vehicle load including packaging, and another only material accepted into packing. Treating those figures as interchangeable totals can turn a record-boundary problem into an apparent production loss.
The practical objective is not to force every figure to match. It is to identify which loads or lots match, which do not, what difference is confirmed by the documents, and what possible cause still needs evidence.
Start with one reconciliation question and a defined record boundary
Set the comparison boundary before calculating any variance. A useful boundary might be:
- one identifiable vehicle load;
- one field or lot for one dispatch day;
- all loads received during a defined shift; or
- one clearly stated lot period from harvest through packing receipt.
Write the boundary at the top of the worksheet. Include the crop or product description, field or lot, dates and times covered, movement stage, and the weight definition being compared.
For example, “Field load records dispatched from Lot B on 14 June compared with receiving scale tickets for the same load IDs” is a workable question. “Field harvest versus packing output for June” may be useful for management review, but it is too broad for investigating a missing ticket or a tare error.
This distinction matters because field, receiving and packing records can represent different points in the material flow. A harvest entry may contain the lot, entry time, container count and net weight, with optional references to a scale ticket or field statement. The Arlo Agro harvest-entry documentation illustrates this kind of record structure; it is not a universal farm recordkeeping standard.
ACA’s practical recommendation is to reconcile the closest comparable stages first. Match field collection to dispatch, dispatch to receiving, and receiving to packing as separate checks. Only then should the team roll results into a wider period or management report.
Build a matching sheet before investigating the difference
Do not begin by debating explanations. First build a sheet that makes each source record visible and linkable.
A load identifier, ticket number or lot code is usually more useful than a grand total. Where identifiers are not consistent, a combination of field, date, dispatch time, vehicle, container count and destination may help locate possible matches. That combination is weaker than a unique load ID, so mark any match made this way as provisional until the team can confirm it.
Guidance from Offshore Bookkeepers recommends retaining fields such as crop, variety, field, harvest date, container count, field weight, load identifier, destination, dispatch time and unit of measure. These are sensible matching fields, but teams should adapt them to their own operational and buyer requirements.
A working reconciliation sheet can use the following columns:
| Field | Why it is needed |
|---|---|
| Source record ID | Preserves the original ticket, entry or receipt reference. |
| Load or lot ID | Links records across handovers where available. |
| Field or origin | Confirms that material belongs in the comparison boundary. |
| Harvest, dispatch or receipt timestamp | Identifies timing differences and late entries. |
| Unit of measure | Prevents kilograms, pounds, bins or other quantities from being compared as if equivalent. |
| Gross weight | Shows the total weighed load where this is the reported value. |
| Tare | Shows the container, packaging or vehicle amount removed from gross weight. |
| Net weight | Shows product weight only when the source defines it that way. |
| Container count and type | Helps test whether tare and unit-count logic is plausible. |
| Destination or receiving point | Distinguishes split loads and alternative delivery routes. |
| Record status | Shows whether the item is matched, pending, cancelled or corrected. |
| Correction reference and reviewer | Preserves the audit trail and follow-up responsibility. |
Use one row per source record rather than combining several field tickets into one number at the outset. If three field tickets were loaded onto one truck, retain the three ticket rows and add a separate link to the receiving ticket. If one field load was split between destinations, record the split rather than forcing one receiving record to carry the entire load.
This approach makes several common conditions visible: a missing receipt, a duplicated ticket, a cancelled record still included in a report, or a combined scale ticket that needs to be allocated back to several source loads.
Check units and tare before calculating a variance
A variance is meaningful only after the compared figures use the same unit and the same weight basis.
Start by marking each figure as one of the following:
- Gross weight: product plus the packaging, containers or other stated tare.
- Tare: the non-product contribution deducted from gross weight.
- Net weight: product content after the relevant tare has been removed.
- Unknown weight basis: a figure whose ticket or system label does not establish whether it is gross or net.
The Adaptiv Stratum discussion of harvested and saleable yield usefully stresses a basic control: do not subtract tare again from a record already identified as net. Its workflow is a proposed reconciliation approach, not a legal-metrology instruction for every jurisdiction or supply chain.
Where vehicle weighing is used, some systems calculate net weight by subtracting an empty vehicle weight from the loaded scale weight. The Arlo Agro documentation describes that type of vehicle flow. Before relying on the result, check what the recorded empty weight represents and whether containers or other packaging are already included in it.
Working example, not a farm observation: A receiving ticket states 1,240 kg gross and 140 kg tare, producing 1,100 kg net. If a field report already states 1,100 kg net, the initial comparison is 1,100 kg against 1,100 kg. Subtracting the 140 kg tare from the field report would create an artificial difference.
Also confirm the unit of measure for every record. A container count is not a weight unless the record clearly defines a valid conversion basis, and an estimated container capacity may not equal an actual weighed quantity. Where units differ, retain the original values and document the conversion method, person and date used for the comparison.
Trace the handovers where records can diverge
Once records are matched and weight bases are clear, trace the physical and administrative handovers. A useful sequence is:
- Field collection to dispatch: Were all recorded field loads assigned a dispatch or destination? Were tickets cancelled, corrected or held back from entry?
- Dispatch to receiving: Does each dispatched load have a receiving or scale-ticket reference? Were loads combined, split or redirected?
- Receiving to packing: Does the receiving record represent all material delivered, or only material accepted into a particular process or lot?
- Packing to disposition: Are packed, rejected, held, returned or otherwise separated materials recorded as distinct dispositions rather than silently excluded from a total?
Sequential ticket numbers can support this investigation, especially when the team checks gaps, duplicates and cancelled records. Comparing dispatched loads with packing-house receipts is also a useful control described in the Offshore Bookkeepers guidance.
At this stage, keep a critical distinction: an unmatched record is a confirmed record condition; it is not yet a confirmed physical loss.
Commercial guidance from 2nd Sight Bio lists possible reasons that field and packing-house weights may differ, including moisture-related change, eliminations, clerical error, tare treatment, scale calibration and report-exclusion settings. These are useful investigation categories. They should not be treated as an explanation for a particular farm’s variance unless the relevant tickets, scale records, inspection records or system settings establish it.
For example, a lower packing receipt may lead the team to ask whether material was rejected before receipt, whether the load was partly delivered elsewhere, or whether the field record includes containers. It does not establish any of those causes by itself.
Record confirmed discrepancies separately from suspected causes
A discrepancy log should separate evidence from interpretation. This protects the team from closing issues too early and preserves a useful handover for operations, finance, quality and packing staff.
Use status labels such as:
- Matched
- Timing difference confirmed
- Unit or tare issue confirmed
- Duplicate record confirmed
- Missing record confirmed
- Adjustment pending evidence
- Unresolved
For each open item, record four things:
- What is confirmed: for example, “Field Ticket F-184 has no linked receiving ticket within the defined receiving period.”
- What is suspected: for example, “Possible delayed receipt entry; not verified.”
- Who owns follow-up: name the operational role or responsible team, not a vague instruction to “check records.”
- What evidence closes the item: such as a scale ticket, dispatch log, corrected receipt, system audit record or documented cancellation.
Do not replace an original value with a correction and lose the reason for the change. The Offshore Bookkeepers guidance recommends keeping the original value, correction reason, date and approver. Similarly, Adaptiv Stratum argues that original tickets, worksheet references, versions and review times should remain identifiable. These are sound audit-trail principles, though local accounting, buyer, food-safety and legal requirements may require additional controls.
A correction can resolve a numerical difference while still leaving a process issue to address. If the revised ticket now matches receiving, the discrepancy may be closed. But the team may still need to decide whether the original entry method, approval step or handover timing needs improvement.
Use the next harvest to tighten the control point
Do not try to redesign every record at once. Select one recurring mismatch type from the reconciliation: missing load IDs, unclear tare treatment, delayed receiving entries, or combined tickets without allocation references.
Assign ownership at the handover where the information first becomes available. For instance, a dispatch coordinator may confirm load IDs before departure, while receiving staff may be responsible for attaching the scale-ticket reference. The point is not to shift blame; it is to make the record complete when the physical event can still be checked.
For the next defined reconciliation period, test one bounded control:
- require a load ID on both field and receiving records;
- add an explicit gross, tare or net label to the worksheet;
- require a correction reason and approver; or
- review unmatched records at the end of each receiving day.
Then assess whether the same mismatch remains and whether the new field is actually being completed consistently. A control that exists in a form or app but is routinely left blank does not solve the handover problem.
The useful result is not a promise that all differences will disappear. It is a clearer chain from field event to scale ticket to packing record, with unresolved differences visible early enough for the team to investigate them.
Frequently asked questions
Why do field weights and packing-house weights differ?
They may refer to different record boundaries, times, units or weight bases. A field figure may describe harvested containers, while a packing record may describe received or accepted material. Differences can also arise from missing, duplicated, split or combined records. Possible physical or system causes should be investigated, not assumed from the difference alone.
What information should be on a harvest load record?
At minimum, include a source record ID, crop or product description, field or lot, date and time, load or lot identifier, container count, unit of measure, reported weight basis, destination and responsible recorder. If a scale ticket exists, record its reference. Add correction details rather than overwriting the original entry.
How do you calculate net harvest weight when tare is involved?
Where the ticket defines gross weight and tare for the same load and unit, net weight is gross weight minus tare. First verify that the reported field or receiving value is not already net. Do not subtract tare twice, and preserve the original gross, tare and net fields for review.
Should a corrected harvest ticket replace the original record?
No. Retain the original record and link the correction to it. Record the correction reason, date, approver and revised value. This allows the team to explain why the number changed and helps distinguish a corrected data-entry issue from an unresolved receiving or packing difference.
Source and further reading
ACA’s practical examples and working checklists are independent editorial analysis. The linked source provides the underlying reference; it does not endorse this article.



