No Charge, No Questions
27 August 2026
Every ticketing system has a code that makes a load worth nothing. Yours might call it NC, or INT, or YARD, or 00. Key it into the rate or customer field and the ticket is handled: not pending, not missing. Just free.
You need that code. A pit moves its own material between stockpiles all day. A farm hauls grain from the field to the home bin. A redo load goes out to replace one that came back out of spec, and billing it twice would start a fight you'd lose. A demo load lands with a contractor you're courting. None of that should invoice, and the scale shouldn't have to pretend otherwise, so the honest answer is a code that says: real load, no charge.
What almost nobody does next is watch the code. And an unwatched no-charge code turns into something you never intended: the quietest exit a billable ticket can take.
The busiest person in the operation sets the price
Picture the scale house on a Friday in August. Six trucks in line, radio going, and the driver at the window can't name his job number. The PO isn't in the system yet, or the customer record the operator can find doesn't match what's painted on the door. The load is real and it's blocking the queue. The operator has two honest options: hold the truck and let the line build, or ticket it with a question mark and let billing sort it out. There's also a third option, and it takes four keystrokes. Code it internal. The scale prints and the truck rolls.
He means to fix it after the rush. Sometimes he does.
Now look at what actually happened in that moment. A zero-dollar ticket is a pricing decision. Not a small one either: it's a 100% discount, granted in full, on the spot. You would never let a scale operator key a special rate for a customer he can't identify. Keying no charge is a steeper concession than any rate he could invent, and in most operations it's the one concession that requires no approval and no second look. The person with the least visibility into the contract holds the deepest discount in the building, and he reaches for it precisely at the moments when nobody has time to think.
The billing office has its own version. A ticket that won't resolve sits in the exception queue and nags. Coding it no charge clears it. The clerk isn't stealing anything; she's making a Friday deadline, and the code was right there.
Resolved is worse than lost
Here's the part worth slowing down on. A lost ticket leaves a hole. The ticket sequence has a gap, the scale log shows a load with no matching bill, and any decent count will eventually snag on it. A no-charge ticket fills its own hole. The load count reconciles. The ticket count reconciles. Every line has a disposition. An audit built on counting, which is what most billing audits are, passes clean.
flowchart TD
A["Ticket that won't bill clean"] --> B{"What happens at the desk?"}
B -- "park it" --> C["Exception pile: visible, nagging"]
C --> D["Chased and resolved while the job is open"]
B -- "code it no charge" --> E["Zero-dollar ticket: processed"]
E --> F["Every count reconciles"]
F --> G["No invoice line, so no customer ever reviews it"]
That last box is the trap. Your customers audit your invoices for free, at least in one direction: a line that shouldn't be there gets a phone call. A zero-dollar ticket never becomes a line, so the one external reviewer your billing process has never sees it. Inside the building, revenue reports don't show it either, because zero contributes nothing to any total and nothing to any variance. The ticket exists, fully documented, in a place no report and no customer will ever visit.
So the claim, and plenty of owners will want to argue: your no-charge code is probably leaking more than your lost tickets are. Lost tickets at least fail loudly enough to have built themselves a reputation. Free ones are filed as finished.
Put a number on it
Run a hypothetical with round figures. A pit turns 2,800 loads a month, and zero-dollar tickets run 3% of volume, which is 84 loads. Sit down with the quarry manager and list the internal moves that are supposed to exist: stockpile shuffles, plant feed, the county road you maintain at the entrance. Call that 50 loads. The other 34 are unexplained. At 23 tons and $9.25 a ton, that's about $7,200 of material a month that crossed the scale and turned into nothing.
Not all of it is leakage. Some of those loads are legitimate demos and redos that just never got a reason written down. Say half survive scrutiny. The remainder is roughly $3,600 a month, call it $43,000 a year, from one field on one screen, in an operation where every count reconciles perfectly.
Watch the trend, too. The share of loads coded free tends to creep upward, because every awkward ticket that gets coded NC teaches the next shift that the code works. Nobody notices 3% become 4%, and at the volumes above, that one extra point is another 28 loads, about $6,000 of material, every month.
Zero is a price, so give it a rule
Asking operators to be more careful at the exact moments they're busiest won't hold. Treat zero like any other rate instead.
A billing rule can say who gets free material and under what conditions: these products, these destinations, these customers, this approver. Reference data carries the list of places a free load may legitimately go, your own yards, your own bins, the named internal jobs. Then a zero-dollar ticket that falls outside those bounds gets flagged as non-compliant and chased while the driver still answers the phone and the job is still open. Capturing tickets digitally makes the reason cheap to record at the moment of ticketing, instead of a memory exercise afterward. That's the shape of what Termco does with this paper: digitize it, check it against your rules and your reference data, and build invoice totals only from lines that earned their price, including the ones whose price is genuinely zero.
The self-audit costs one afternoon. Pull every zero-dollar ticket from last quarter and sort by reason. If your system has no reason to sort by, that's the first finding. Then take the unexplained ones and look at where the material went. A free load delivered to a paying customer's job site is a question, and you only need a few of those to pay for the afternoon.
If you'd rather have a second set of eyes, send 10-20 sample tickets to hi@termco.ai, including a few of your zero-dollar ones, and we'll send back what we find within 48 hours.
More from the Termco blog.
August 26, 2026
When the Other Side Writes the Ticket
Broker tallies, destination weights, and elevator grain tickets are billing records your counterparty controls. That control has a price.
Read postAugust 25, 2026
Two Spellings, Two Prices
When one customer lives in your system as two records, the negotiated terms fork, and each ticket bills at whichever copy the clerk picks.
Read postAugust 21, 2026
Every Credit Memo Has a Silent Twin
Credit memos document the billing errors customers caught. The same processes that overbill also underbill, and nobody calls about those.
Read post