If you receive, store or sell bulk product by weight, the problem usually isn't the weighbridge. The ticket is right. The trouble is everything after it: the same load gets typed again into a contract spreadsheet, again into a grower or supplier payment calculation, again for the shipping paperwork and again into the accounts, and those copies never quite agree. So when someone asks how much of a contract has been delivered today, nobody can answer without an afternoon of adding up.
Picture an ordinary week in harvest or a busy haul period. Trucks are crossing the weighbridge from first light. The operator prints tickets, or they sit on a standalone weighbridge PC in the office. Someone in admin keys the tonnes into a spreadsheet that tracks each contract. Moisture and grade results come back from the sample shed or the lab on a separate sheet. A grower rings on Thursday asking why their statement is short. The accounts in Xero or MYOB show a total for the month, but only after someone has reconciled it, and that's usually a few weeks later.
Signs you have this problem
- Weighbridge tickets are printed and handed in, or exported from the weighbridge PC as a file someone retypes.
- Contract tonnages, delivery periods and prices live in a spreadsheet that one person keeps up to date.
- Nobody can say, without checking, how many tonnes are still open on a contract or how much a grower has left to deliver.
- Moisture, screenings, test weight, protein or grade adjustments are applied by hand when payments are worked out.
- Grower, supplier or harvest contractor payments are calculated in a spreadsheet, then keyed into the accounts as a bill or an RCTI.
- Deductions such as levies, cartage, storage or shrink are worked out differently depending on who does the run.
- Export or shipping documents, such as the packing details, phytosanitary paperwork and the bill of lading, are prepared from a separate set of figures.
- The stockpile or silo figure is estimated before a vessel or a big sale, rather than known.
- The accounts show the month's totals weeks after the month ends, and they don't always match the contract register.
- When the person who keeps the contract spreadsheet is on leave, payments slow down.
Why it happens
Each part of the operation got its own tool when it needed one. The weighbridge came with software to record weights. Contracts were tracked in a spreadsheet because they change constantly and the accounting system doesn't understand tonnes, grades or delivery periods. Quality results came from the lab in whatever format the lab sends. Payments were worked out in yet another spreadsheet, because the rules for adjustments and deductions are specific to your business and your contracts. Export paperwork followed its own process because it has its own requirements.
None of those choices were wrong. The problem sits in the gaps between them. A load is one event: a truck, a supplier, a product, a contract, a weight and a quality result. But it's recorded in four or five places, by different people, at different times. Every retype is another chance for a wrong number, a missed ticket or a load counted twice. And because each copy is updated on its own schedule, they're never in step on any given day.
That's why buying another app rarely fixes it alone. A new contract management tool still needs the tickets. A new payments tool still needs the contract prices and the quality results. A better weighbridge system still produces a ticket that someone has to carry to the other systems. Unless the pieces are connected, the new app becomes one more place the same load gets typed into.
What it costs you
The cost is rarely one big failure. It's a steady leak of time, cash timing and confidence in the numbers.
- Time. Admin staff spend days each month keying tickets, checking totals between spreadsheets and chasing missing dockets. In harvest, that's when you can least afford it.
- Payment disputes. When a grower or contractor queries a statement, the answer means finding the ticket, the sample result, the contract price and the deduction that was applied. If those live in different places, a ten-minute question takes half a day, and the relationship suffers.
- Contract risk. If you can't see open tonnes on each contract, you can over-commit on sales or under-deliver on purchases. For example, if a sales contract needs a set tonnage by the end of a shipping window and your register is a week behind, you may only find out you're short when it's too late to source more.
- Margin you can't see. Adjustments for moisture and grade, plus storage, cartage and shrink, decide whether a contract made money. When those are only added up at month end, you learn a contract's margin after it has finished.
- Cash timing. Late customer invoices mean you're funding the gap yourself, and late grower payments damage trust.
- Key-person dependence. If one person understands how the contract spreadsheet and the payment calculations fit together, the business is exposed every time they're away, and when they eventually leave.
- Audit trail. Buyers and auditors expect to trace a shipment back to the loads behind it. Rebuilding that from paper is slow and error-prone.
What fixing it generally involves
Start with the simplest step, and only go further if you need to.
- Agree how a load should flow. Write down what happens from the truck arriving to the payment and invoice: who records what, which contract it belongs to, when the quality result is attached, and how adjustments and deductions are worked out. Our business process improvement guide covers how to map this.
- Check what you already have. Some weighbridge software can record the contract, grower and quality result on the ticket, and export cleanly. If yours can and nobody has set it up, that's the cheapest fix there is. We'd tell you so.
- Capture each load once, at the weighbridge. The ticket should carry the supplier, product, contract and load details from the start, so nothing has to be retyped later. The weighbridge stays the record of the weight.
- Connect the systems. Tickets flow to wherever contracts, stock and payments are managed, and from there to Xero or MYOB as bills, RCTIs or invoices. Quality results attach to the load they belong to. Remote sites need a link that keeps recording when the connection drops and catches up without missing or doubling a load.
- Report from one place. Open tonnes by contract, deliveries by grower, stock on hand and margin by contract all come from the same set of records, so the figure you see on Tuesday is Tuesday's figure.
This is work we know well. Since 2012 Kenomont has built and looked after a forestry export and woodchip port management system for Australian forestry companies, covering deliveries in, stockpiles, shipments out and the records behind them. Since 2015 it has received ticket data from the weighbridge system as each load is weighed, and executive reporting dashboards are built on the same records. You can read how the forestry export system and weighbridge link work. The same approach applies to grain, hay, produce and quarry: the record is right at the weighbridge and goes wrong after it.
If you want to see where this fits for your type of operation, see our pages for forestry and timber and agriculture, or how we approach weighbridge integration. If the deeper issue is that different reports give you different totals, when your systems give different numbers explains why that happens.
Frequently asked questions
Why don't our weighbridge totals match the accounts?
Usually because the tickets reach the accounts through one or more manual steps: a spreadsheet, a payment calculation, a batch entry. Voided or split tickets, late dockets, adjustments applied at different times and loads reassigned between contracts all create small differences that add up by month end.
Do we need to replace our weighbridge software?
Usually not. Most weighbridge software records weights reliably. The fix is normally to capture the right details on the ticket and pass the ticket data to the systems that need it. Your weighbridge and its software stay as they are, and your weighbridge supplier still looks after the scales and calibration.
How do we see how much of a contract has been delivered today?
Each ticket needs to be tied to a contract when the truck is weighed, and those tickets need to flow somewhere that adds them up against the contract tonnage as they arrive. If the link between ticket and contract is made later by hand, the figure will always be behind.
Can grower payments with moisture and grade adjustments be automated?
Yes, as long as the rules are written down and agreed. Once the ticket, the contract price and the quality result are connected, the adjustments and deductions can be calculated the same way every time, with a person checking exceptions before payments are approved. Our article on the horticulture award and payday super covers the payroll side of the same season.
Where does AI fit in?
Mostly in the office, reading dockets and supplier paperwork and doing a first pass that a person checks. It works far better once the underlying records are connected. See AI in the farm office.
What does it cost?
Costs vary widely depending on the size of the business, how many systems are involved and how much needs to be custom-built, so we scope every project first and give you a fixed quote after a free initial chat. If you're not sure yet what needs fixing, the $5,000 Process & Systems Audit maps your processes and systems and gives you a written report.
If your tickets, contracts and payments are kept in step by hand every week, book a free initial chat and we'll talk through where each load goes after the weighbridge and what's worth connecting first.