Route accounting basics: from pick ticket to proof of delivery
"Route accounting" sounds like bookkeeping, but it's really a chain-of-custody problem: product leaves the warehouse worth an exact amount, rides a truck through a dozen stops, and comes back as some mix of signed invoices, credits, returns, and cash. Route accounting is the discipline of making those two ends reconcile — and every manual link in the chain is a place where margin quietly falls off the truck.
The chain, link by link
The pick ticket. Everything starts with what was actually picked — not what was ordered. Shorts and substitutions happen at pick time, and if they're only discovered at the customer's back door, the delivery turns into a negotiation. The pick ticket should be the order, annotated with reality, before the truck is loaded.
The load check. The cheapest audit in distribution: does what's on the truck match the sum of the pick tickets? Thirty minutes at the dock catches what would otherwise become five stop-level disputes and a driver taking the blame for a warehouse miss.
The stop. At each stop, three things can diverge from plan: the customer refuses items, quantities get adjusted, and returns come back on the truck. The failure mode is recording this on paper — a scribbled adjustment on a delivery ticket that someone must decipher and rekey at day's end, or more often, doesn't. Whatever happens at the stop has to be captured at the stop.
Proof of delivery. The signature (or photo) is the legal and practical end of the argument "we never got that." Chains deduct aggressively on delivery disputes; independents dispute more politely but just as expensively. A POD with a timestamp, a name, and the stop's final quantities converts "he said, she said" into a record — and it's the trigger that says this stop is ready to invoice.
The invoice and the credit. The invoice should reflect what was delivered, not what was ordered — which is only possible if the stop-level adjustments made it back as data. Same for credits: a return captured at the stop becomes a clean credit memo; a return remembered at settlement becomes a mystery.
Settlement. End of day, the route reconciles: product out versus delivered + returned + shorted, invoices generated versus signed, cash and checks collected versus recorded. When every link above is data, settlement is a report you review. When the links are paper, settlement is an hour per route of forensic accounting — and the errors that survive it are permanent.
Where the money actually leaks
Distributors who tighten this chain usually find the leaks weren't dramatic theft but steady friction: undocumented stop adjustments that never became credits (or became credits twice), returns that rode the truck for a week, deliveries invoiced as ordered rather than as delivered, and disputes lost for want of a signature. Individually each is small; across every truck, every day, they're a real percentage of route revenue.
What good tooling changes
The pattern that fixes route accounting is the same one that fixes EDI hygiene: every document generated from the previous one, no rekeying anywhere. Orders wave into pick tickets; pick reality flows into the load; the driver's app captures stop adjustments, returns, and the POD as they happen; the invoice generates from the stop's final numbers as it closes; settlement compares data to data. That's how routes work in DistroLync OMS — route planning with stop-level proof of delivery, returns and adjustments captured on the spot, and invoices that match what actually came off the truck. Walk through it with your route sheet and count the rekeying steps that disappear.