Before the Account Exists
10 October 2026
The first load for Miller Grading crossed your scale at 7:40 Monday morning. The account that pays for it won't exist until Thursday.
That's not a failure. That's how these industries win work. The call came Sunday night, a contractor your asphalt customer vouched for, needs base rock for a lot he's prepping this week, and your dispatcher said bring your trucks at 7. Right answer. The operation that says "we'll start hauling once your credit application clears" loses the job to the pit that says yes, and everybody who runs a scale knows it.
The billing system doesn't know it. A billing system can only invoice accounts that exist, and creating one takes things Monday morning doesn't have: a legal name instead of "Miller, the guy Danny knows," a billing address, a tax status, a credit decision, somebody in the office with twenty free minutes. So for three or four days the operation runs in a state the paperwork has no name for. Trucks are hauling and tickets are printing for a customer who, on paper, isn't one.
Watch what happens to the tickets.
The clip, the placeholder, and the phone rate
The scale operator does the only sensible thing. She writes "Miller Grading" on the ticket by hand, same as she'd write anything, and the paper is fine. Paper doesn't need the account to exist. The trouble starts at the keying desk, where the ticket needs a customer number, and there are only three ways through.
The first is the clip. Tickets for the new guy go under a binder clip on the corner of the desk, waiting for Thursday. By Thursday there are 31 of them. Then a fourth truck gets added, the week gets loud, and the clip migrates under a vendor statement. The invoice run at month end bills every account in the system, which is its whole job, and the clip isn't in the system. Nothing about that run looks wrong, because an invoice register has no line for the customer it never heard of.
The second is the placeholder. The tickets get keyed somewhere so they're at least keyed: the CASH account, a MISC customer, or, worst of all, the established account that vouched for him, "for now, we'll move them." Moving them is a job with no deadline and no owner. Six weeks later those tons are a mystery inside somebody else's statement, and untangling them means calling your best customer to explain why he was billed for a stranger's rock.
The third way through is the one that bills on time and still leaks. Thursday arrives, the office manager sets up the account, and she sets it up from the credit application, because that's the paper in front of her. The one thing the credit application doesn't say is the price. The price lives in Sunday night's phone call. $13.25 delivered, winter rate, because Danny vouched and the dispatcher wanted the work. The account gets built at list, $14.10, the first invoice goes out, and Miller's first experience of your office is a bill that breaks his quote. Or the dispatcher catches it in time, the account gets built at $13.25, and the number rides along for years, on every product, with nobody left who remembers it was a favor priced for one lot in October.
Add it up in one direction and it's a bad week: 31 tickets, call it 740 tons at $13.25, is about $9,800 sitting under a binder clip. Add it up in the other direction and it's worse, because everything decided in that scramble, from the spelling of the name to the rate, hardens into the account's permanent record. A new account is reference data written at the worst possible moment, by whoever was busiest, and it outlives the week by a decade.
flowchart TD
A["Monday ticket: Miller Grading, no account number"] --> B{"Where does it go?"}
B -- "the clip" --> C["Held for Thursday"]
C --> D["Month closes without them"]
B -- "a placeholder" --> E["Keyed to CASH or the vouching account"]
E --> F["Moving them is nobody's job"]
B -- "Thursday's setup" --> G["Account built from the credit app, at list"]
G --> H["First invoice breaks the phone quote"]
The credit app is not the account
Here's the claim your office manager will fight: the account should exist before the first truck loads, created Sunday night if the deal was made Sunday night, and the credit application has nothing to do with it.
The pushback is immediate. We can't open accounts for every tire-kicker who calls, and anyway credit hasn't cleared, so we shouldn't be setting him up to bill. Half these one-job guys never come back.
All true, and all of it about a different question. Whether Miller gets 30-day terms is a risk decision, and it deserves its Thursday deliberation. But whether Miller exists stopped being a decision the moment the dispatcher said bring your trucks. An account record is a name and a rate. The tax question can be answered properly later, creating the record costs two minutes, and it commits you to nothing. The conflation of those two decisions, no credit file means no customer number, is the entire reason the clip and the placeholder exist. Your scale found room for Miller on day one. Your records should be at least that fast.
If you ran one of the operations systems sold in the 2010s, you may remember how that era handled this. The ticket form wanted a valid customer record before it would save, so the gap moved out to the parking lot, where a driver idled while the office hunted down a federal tax ID the contractor didn't know. The scale operator writing "Miller Grading" in ink and sorting it out later was always the better system. Keep her. What needs fixing is that the sorting out never reliably happens.
That's the shape of what Termco does with the Monday gap. Tickets get digitized the day they're written, as written, and a ticket naming a customer the reference data doesn't know gets flagged that day instead of surfacing at month end. The new account and its phone rate get keyed once, as reference data and a billing rule dated to Monday, while the dispatcher still remembers the quote, and the 31 tickets price themselves when they land. Invoice totals assemble from tickets that cleared, including the first week's. Nothing changes at the scale, where the operator keeps writing names in ink, and the credit call stays yours, made on whatever day your office makes it.
Count the orphans on the desk
The test takes ten minutes, today. Go to the keying desk and count the tickets waiting for an account number, then ask how old the oldest one is. Pull your CASH and MISC accounts for the last quarter and read the handwritten names on those tickets; every name that appears more than twice is a customer you have without having. Price what you find at your average load.
Then keep one eye on the next Sunday-night phone call, because another Miller is coming, and the week before his account exists is the week you've already agreed to work for him. If you'd like a second reader on it, send 10-20 sample tickets to hi@termco.ai, the ones from your newest accounts especially, and we'll send back what we find within 48 hours.
More from the Termco blog.
October 09, 2026
The Forty-Tab Workbook
The old software couldn't read a ticket until you described your whole operation in advance. The owners who refused to fill out the workbook were right.
Read postOctober 08, 2026
The Eighty That Isn't
Scale tickets get weighed. Acres get remembered. Per-acre work billed off the remembered number leaks the same ground every pass.
Read postOctober 07, 2026
Four Yards on a Ten-Yard Truck
The batch ticket on a short load is completely true, and billing exactly what it says is how the short load fee dies. Minimums leak at three desks.
Read post