Weighbridge-to-Ledger Reconciler

Where it works well

It catches the discrepancies that hide in the paperwork — tare drift, moisture cap errors — and shows exactly why.

Most valuable during harvest receival when docket volumes are high and the risk of unreconciled underpayments or overcharges is greatest.
Best for a grain handler or receival-site office manager processing a daily queue of 20-plus dockets across multiple growers and commodity grades.
At that volume, the capacity recaptured from manual cross-referencing goes back into the grower conversation and exception resolution, not the rekeying.

The expensive part of weighbridge reconciliation is not the arithmetic — it is tracing a tare weight back to the registered vehicle record, or checking whether the moisture percentage on a scanned docket actually clears the GTA lab certificate cap before applying a shrink deduction. Done by hand across a day's docket queue, those checks are the first thing to slip under pressure.

Where it works badly

It is only as current as the contracts and lab certs it holds — and a stale reference makes a confident wrong call.

Weak on dockets where the tare is a manual field-entry from a site without an electronic weighbridge master record — it can flag the discrepancy but cannot resolve it without a confirmed reference tare.
If most of your docket volume is non-standard commodity arrangements or spot-price trades with one-off contract terms, the matching logic gives you less than your grower-manager's judgement already does.

The honest test

If you cannot say, right now, which seasonal price schedule and which version of the delivery contract each docket was reconciled against — this tool makes your wrong call faster, not safer.

Point it at a delivery contract whose seasonal price schedule has been updated but not refreshed in the system, or a docket where the moisture certificate has not yet arrived from the GTA lab, and it will reconcile cleanly against the wrong number. The output looks exactly as authoritative as a correct reconciliation.

What it doesn't do — and shouldn't

It reconciles and drafts. A grain handler clears. That line is deliberate.

WHAT IT DOES

Surfaces each discrepancy with the docket field, the reference value, and the evidence source (weighbridge ticket number, contract reference, lab cert)

Drafts the adjustment note with the per-line underpayment or overcharge figures ready for a person to review and send

Flags every exception rather than silently rounding or absorbing a difference

WHAT IT WON’T

Post an invoice or adjustment to Xero without a person raising it

Override or resolve a tare discrepancy on its own

Certify that the docket meets the GTA receival standards or NMI trade-measurement requirements

A weighbridge docket used for grower payment is a trade-measurement instrument under the National Measurement Act, and the grower is owed payment to the settled tonnes. An unresolved tare error or an incorrect moisture-shrink deduction is a financial error with a real grower on the other side. The grain handler stays on the decision because the consequence — to the grower and to the co-op's receival ledger — lands on them, not the tool.

What your data has to look like

Docket fields as readable values, a current price schedule per grower contract, and a GTA lab certificate for each moisture claim.

Typical readiness

across orgs we see, before the first job

Weighbridge dockets with structured or extractable fields

Usual weak point

Grower delivery contracts, current season

Needs shaping

Weighbridge master ticket for tare verification

Usual weak point

Accredited lab moisture certificates, matched to docket

Needs shaping

Grower NGR register, current

Usually ready

The real first job

The delivery contracts and lab certificates are almost always the weak point — price schedules that live in a folder nobody updates at seasonal rollover, GTA certs that arrive days after the docket and get filed separately. Getting those documents into a current, referenced, structured form is usually the real first job — larger and more valuable than the reconciliation layer on top. Once the inputs are reliable, every docket after that is faster and right by default.

Right fit if…

You process a regular daily docket queue across multiple growers and commodity grades

Your grower contracts, tare records and GTA lab certs exist as documents you can point to today

Harvest receival periods put real pressure on the back office and create the most risk of unreconciled errors

You want exception exceptions surfaced with their evidence, not buried in end-of-day spreadsheet reconciliation

Walk away if…

Most of your docket volume is informal or verbal arrangements with no structured contract to match against

Your tare records live only in a weighbridge operator's head or a notebook that gets transcribed weekly

GTA lab certs don't come in until well after the settlement deadline and you have no way to hold dockets against them

You need a tool that self-certifies compliance with NMI trade-measurement requirements

Open questions

The worried-buyer questions, answered straight

No — that is exactly the boundary the tool is built around. Nothing posts to Xero on its own. Every docket is classified as verified or exception; exceptions are held in a queue with the discrepancy figure and the evidence source — weighbridge ticket, contract, GTA lab cert — laid out for a grain handler to check. A person raises the adjustment or dismisses the flag; the tool never does it on their behalf. A grower underpayment only clears the queue when a person has reviewed and authorised it.

Digital dockets from a scale management system are the cleanest input. Scanned paper works where the key fields — gross, tare, grade, moisture, vehicle registration — are legible and consistently laid out. Where a field is missing, smudged or hand-corrected, the tool flags the docket as an exception rather than guessing a value. If a significant proportion of your scanned dockets have illegible tare or moisture fields, those will land in the exception queue every time — the first job is getting those sites onto a digital scale output or a cleaner paper form.

No. It removes the cross-checking — the part where someone has to trace a tare back to the vehicle record, verify the moisture shrink against the GTA lab cert, and key the settlement figure into the accounting system — so the grain handler can focus on the exceptions that actually need judgement: a contested tare, a grade dispute, or a grower who needs an explanation. The reconciliation is still theirs to approve. The capacity it frees goes back into grower relationships and exception resolution, not the paperwork.

Current to the delivery. Price schedules are set at seasonal rollover and can be updated mid-season; a delivery contract that was not refreshed when the price changed will produce a wrong settlement figure, and the tool cannot detect that — it will reconcile correctly against the wrong contract. GTA lab moisture certificates apply to a specific sample; using a cert from a different delivery or a prior load is a data error the tool will carry forward. The honest check: do you know, today, which contract version and which lab cert number each docket was reconciled against?

Grower NGR numbers, delivery contracts, tare records and settlement figures are commercially sensitive and subject to the Privacy Act where growers are individuals. Any deployment is scoped to your own systems and data handling — we specify where the data sits and who can access it as part of the build. The demo at apps.realmindsai.com.au/reconciler runs on fabricated docket and grower data; Tarrawingee Pastoral and the other growers shown are not real entities.

No — and it should not. The tool works from the docket the weighbridge produces; it does not inspect or certify the scale instrument itself. Whether a weighbridge is a legal-for-trade instrument under the National Measurement Act, and whether its current calibration certificate is valid, is the site operator’s obligation and is verified by a NMI-accredited technician. The tool flags discrepancies in the docket values; it does not stand behind the measurement that produced them.

What it takes to build

3–4 weeks · 4 phases

Reused from template~65%

Bespoke to this skin~35%

stack · Claude · Xero API · review UI

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One contained change, low risk

Pilot build

Most builds land here

Embedded support

Scale on proof

Considering this for your receival operation?

The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where the docket reconciliation hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work