The Truck Got Paid Either Way

An owner-operator leased onto your fleet hauls nine loads of base rock on a Tuesday. Two weeks later his settlement request lands on the desk: nine ticket copies, folded in thirds, rubber-banded, in serial order. Not eight. Never eight. His truck payment is due on the 15th and those tickets are how he makes it, so his paperwork is immaculate in a way your own drivers' never quite is.

Now pull the invoice you sent the customer for that Tuesday. If it shows seven loads, nothing in your office will ever say so out loud. The settlement gets paid from his stack. The invoice gets built from yours. The two stacks describe the same nine trucks through the same gate, and nobody sets them side by side.

One ticket, two obligations

Every ticket is supposed to become exactly one billed line. When the truck under the load is hired, that same ticket carries a second promise: money going out. One piece of paper, two ledgers, and the load counts as finished only when both agree it happened, not when it's dumped and not when it's billed.

Those two ledgers are not equally trustworthy, and the difference has nothing to do with your people. The payable side has an auditor with skin in the game: the trucker counts his own loads, keeps his own copies, and calls by Friday if his settlement comes up a ticket short. The receivable side has no such person. Your customer will never phone to report that Tuesday's invoice looks light. So the pay ledger converges on the true count while the billing ledger drifts under it, and the drift only ever runs one direction.

That makes your subhaulers' settlements something most owners never recognize: an independent census of your billable events, compiled for free, by people motivated to get it exactly right.

How the stacks split

The fork happens at the tailgate, and it's built into how hired trucks get paid.

Your own drivers turn in every copy to one place because their paychecks are hours, not tickets. The owner-operator splits the paper: one copy for his settlement, one for you, one signed at the site. His copy always arrives, attached to a request for money. Yours rides back in a door pocket, if it rides back at all. When a load evaporates on the billing side, it's usually your copy that went missing, and his that survived.

The units hide the gap even when both copies arrive. You pay him $95 a load, flat, because that's how haul trucks price. You bill the customer $6.20 a ton, because that's how material prices. A clerk keying tonnage has no reason to notice the load count, and the bookkeeper cutting his settlement has no reason to look at tonnage. The two numbers never meet in anyone's field of view. They aren't even in the same units.

Then there's the paid-but-unbillable load: he ran a legitimate ninth load to a job whose number he heard on the radio and wrote down wrong. His settlement pays it, because he plainly hauled it. Your billing can't place it, so it parks in a folder of tickets to sort out later. His ledger closed. Yours never did.

What the gap actually costs

Run a month of it. Three hired trucks, 420 paid loads. Suppose the billing side captured 407, a 3% slip, about one lost ticket per truck per week. Thirteen loads at 22 tons and $6.20 is about $1,770 of material and hauling that was delivered, signed for, and never invoiced.

But that's the smaller number. You also paid $95 for each of those thirteen loads: $1,235 in cash, already out the door. A missed load on your own truck costs you the revenue. A missed load on a hired truck costs revenue plus the check you wrote to move it. Failing to sell it was half the loss. Paying to deliver it was the other half.

flowchart TD
  A["Ticket 20455: hired truck, 22 tons of base"] --> B["Trucker's copy, banded to his settlement"]
  A --> C["Your copy rides back in a door pocket"]
  B --> D["Paid $95 on the 15th, every time"]
  C --> E{"Reached the billing office?"}
  E -- yes --> F["Invoiced: 22 tons at $6.20"]
  E -- no --> G["Never billed. The $95 still left."]

Here's the claim your bookkeeper may want to argue with: on jobs that run hired trucks, the settlement stack is a better record of what you're owed than your own ticket file. It feels backwards, because his paper documents what you owe, not what you're due. But records are only as good as the person with a reason to complete them, and on the pay side that person exists. Trust the count that someone hungry has already verified. Then make your billing match it.

Make the payable prove the receivable

The reconciliation is one afternoon a month, and it's blunt: for every ticket a settlement pays, find the invoice line it became. Loads paid minus loads billed, job by job. The remainder is deliveries you financed and never charged for, and each one still has a serial number you can chase while the trucker remembers the job.

The standing version turns that afternoon into structure. The hired-truck roster and the jobs each truck hauls on are reference data, kept current in one place instead of in the dispatcher's head. The bill rate for each of those jobs lives in a billing rule, so a captured ticket either prices cleanly or gets flagged for a person. Digitize tickets as they turn in, including the copies that arrive banded to settlement requests. A serial that shows up on settlement paper and nowhere in billing gets flagged that week, not in a year-end margin meeting. That's the lane Termco works in: tickets captured from both stacks, the ones that don't reconcile flagged, billing rules and reference data kept structured, and invoice totals assembled only from tickets that priced against a rule. What you pay the truck stays in your settlement file. The reconciliation only needs the serial numbers to match.

Your last settlement run already holds the test: loads paid versus loads billed, on the same jobs, for the same month. Expect the first number to be bigger. Whatever the gap is, that's freight you bought and gave away.

If you'd rather have a second set of eyes on it, send 10-20 sample tickets to hi@termco.ai, settlement copies welcome, and we'll send back what we find within 48 hours.