The waste-hauler invoice problem: tickets, tonnage, and contamination fees

Every load crosses the scale and becomes a paper ticket. Between that ticket and a correct invoice sits a person re-keying tonnage into the billing system. That is where the margin goes.

The scale house is the system of record nobody designed. A truck crosses in, crosses out, and the scale prints a ticket: gross, tare, net tons, material, the disposal site. That ticket is the invoice waiting to happen — every downstream number starts as ink on that slip. The tonnage billed, the per-ton rate, the contamination fee, the fuel surcharge. In most hauling operations, someone then types it into the billing system by hand. Multiply that by every load, every day, across every yard.

The ticket is the invoice

Re-keying is where the errors breed. Handwriting on the ticket, a transposed digit on the tonnage, the wrong customer rate applied to the right load. Contamination fees are assessed per contract — one customer’s contract charges them, another’s caps them, a third’s requires photo evidence from the hopper. Fuel surcharges move on their own table. The billing clerk carries all of this in their head, and when they are out, billing waits or guesses. Every guess becomes an invoice line, and every wrong invoice line is money lost or a dispute.

Why has software not fixed waste-hauler billing?

Because the exceptions are the business. Ticket formats differ by landfill and transfer station. Rates differ by customer, material, and municipality. Fuel surcharges follow contract-specific tables, and contamination fees depend on terms negotiated customer by customer — capped, evidenced with photos, or waived. Off-the-shelf billing and AP tools ship generic rules, so every real variant lands back on a person with a stack of tickets. What works is encoding the hauler’s own rules: read the scale ticket as data, match it to the contract rate, apply the surcharge tables, and flag only what the rules cannot resolve — a ticket that matches no order, a fee with no contract basis. The reading is a solved problem. The judging has to be yours, written down — a rule set that outlives the clerk who carried it around in their head.

The same language shows up on the other side of the ledger. Brokers and PE-backed platforms paying hauler invoices see the mirror image: price creep of a few dollars a pull hidden inside fuel surcharges and environmental fees, pass-through charges that were billable to a customer and never got billed through, invoices from acquired routes arriving with no PO at all. Operators describe eating nearly all of the pass-throughs; on a national footprint the leak runs to millions. Nothing on either side gets caught by reading invoice totals — the variance lives at line level, per ticket, per ton.

What encoding looks like

This is not a software purchase, because nobody sells the rule set your contracts already contain. It is an implementation engagement: we sit inside the billing flow and the AP inbox, catalog every exception type — no-PO bills, rate drift, unbilled pass-throughs, tickets that match nothing — and encode the rules against the systems already in place. Clean items flow; the rest land in a queue with the reason attached. In one deployment, field-level accuracy on emailed hauler invoices runs 97–98% against a 40–50% OCR baseline, and 500 bills out of every 5,000 reach a human.

The leak is not the invoice total. It is the four-dollar line inside it.

The industry picture — brokers, haulers, roll-ups, and the workflows worth encoding first — is on our waste services page (zaigo.ai/industries/waste-services). The AP-side mechanics are on the AP invoice automation page (zaigo.ai/workflows/ap-invoice-automation).

If your billing depends on one person’s reading of the tickets, the next step is a 30-minute working call: zaigo.ai/book-a-call. Bring a week of scale tickets and the ugliest customer contract you have — we will tell you on the call what your rules look like written down.