In this guide 6 sections
Capture gross and tare once. Do it at the weighbridge, against a vehicle and an order, so the delivery note and the invoice read the net weight from that ticket instead of retyping. Contractors stop arguing once every document carries the same net figure and the same ticket number as the paper slip in the driver’s hand.
Walk one load through your current paper trail
A tipper arrives for aggregate. The weighbridge operator writes the gross weight, the truck loads or unloads, the tare follows, and a ticket is printed or handwritten before the driver takes a copy away.
Later the clerk types the net weight into a delivery note, and on another day types it again into the invoice without checking either entry against the ticket. One number, keyed twice.
Each retype risks a transposed digit. A load of 24.60 tonnes becomes 26.40 on the invoice, and the contractor refuses the line until someone finds the original ticket in a drawer. He knows the truck carried less.
See where the dispute starts
The contractor checks the invoice against the driver’s slip and finds the weights differ by a few hundred kilograms, with no way to tell which copy is right. The clerk’s version carries no ticket number.
Units cause trouble too. The ticket says tonnes, the order says cubic metres, and the invoice says bags or pieces, with the conversion done in someone’s head. Neither side can rebuild it later.
Night loads add another risk. The operator goes home. The ticket book stays in the cabin overnight, the morning clerk reads a smudged carbon copy, and the dispute that follows rests on handwriting.
- Digits swapped when copying net weight
- Ticket number missing from the invoice
- Unit converted by hand between documents
- Vehicle tare changed since the last trip
Set up the order, the vehicle and the ticket as linked records
Start with the order. The order names the customer, the material, the rate basis and the site, and the weighbridge ticket attaches to it once the operator picks the vehicle number.
Store a vehicle master with each registered tare and a flag for how often the truck must be re-weighed, so a stale tare never slips into a net weight. A weighbridge indicator with a serial port can feed gross and tare straight in, and without one the operator types them once, at the bridge, and nowhere else.
Keep the entry screen to three fields. Those are the vehicle, the order and the weight. Ticket numbers run in sequence and are never reused, and if the indicator display fails, only a supervisor can open the weight field for typing, with a logged reason.
Generate the delivery note and invoice from the ticket
Once the ticket closes, the delivery note is a print of fields already stored, and the invoice pulls net weight, rate and tax from the order. The clerk reviews and approves. Nothing is typed.
Solid blocks are sold by count, so the ticket carries a count instead of a weight and the order decides which field prices the line. Store both fields.
Allow a correction path. If the operator keyed a wrong weight, a supervisor reissues the ticket as a revision, and the old one stays visible as cancelled so the trail stays whole.
- Delivery note prints from the ticket
- Invoice reads net weight and rate from the order
- Revised tickets keep the cancelled original
- Contractor statement lists ticket numbers
Start with one weighbridge and one customer
Pick your busiest contractor. Run their orders through the linked flow for a month, then compare invoice disputes against the previous month and ask the clerk which step still involves a pen.
Print the ticket number on each line. Contractors will quote it when they ring, and your clerk can find the load in seconds instead of searching a month of carbon copies. Then add the other customers and the second weighbridge, and review the corrections log every Monday for repeated causes such as a smudged tare or a wrong vehicle number.
Train the operator first. He is the only person who now enters the weight, so a mistake at the bridge reaches every later document, from delivery note to monthly statement. Show him the revision step on day one and walk through two cancelled tickets together before the first real load arrives, so the correction path feels familiar.
Load to invoice mapping sheet
One row per field that travels from the weighbridge ticket to the delivery note and invoice, such as gross, tare, net weight, unit and ticket number. Columns record the field name, where it is first captured, who captures it, which documents show it and whether anyone retypes it by hand.
Open a blank worksheet to printQuestions owners ask
Does the weighbridge need to connect to the software?
Not strictly. A connection removes typing, yet without one the operator keys gross and tare once at the ticket and every later document reads from that entry.
How do we handle a driver who disputes the weight?
Re-weigh the truck with the order and vehicle selected, then keep both tickets, since the first stays visible as cancelled and the difference is documented rather than argued.
Can one invoice cover several loads?
Yes. Many contractors prefer a weekly invoice, so list each ticket number and net weight as a line and let them tick the lines against their own receiving notes.
What should the clerk check before approving an invoice?
Three things: the ticket number exists and is closed, the net weight matches the delivery note, and the rate matches the order. Everything else is already filled in.