Trade Work Still Prints Tickets

"Run your trucks for me the first two weeks of May, and take your base rock off me this season. We'll square up over the winter."

That deal gets made every March, at a diner or across a tailgate. Call them Carl, who runs the quarry, and Denny, whose excavation outfit runs the trucks. They've known each other twenty years, and neither would dream of signing anything. The trucks show up in May, the rock flows all summer, and both men consider the matter handled.

Both scales keep printing tickets anyway. That's the part worth sitting with. A trade changes how a load gets paid for. It changes nothing about the load itself: the rock still crosses the scale, the ticket still prints a serial, a weight, a truck, and a destination. One ticket, one billable event. The handshake didn't repeal that rule. It just took the event out of the one system built to count it.

The tickets don't know it's a trade

Follow the paper on both sides and watch it go soft.

At the quarry, Denny's loads get keyed the only way the screen allows: to his account, at some rate. Except these aren't supposed to bill, so the scale operator writes "N/C, trade" on the ticket, or keys it to the house account, or the office holds the invoice at month end because Carl said not to bill Denny. Three different clerks handle it three different ways over the season. By August there are trade tickets in the billing system, trade tickets in a folder, and trade tickets that quietly rolled up into internal use.

At the contractor's shop, the May hauling lives in the dispatcher's notebook: loads run per day, per truck, for two weeks. No settlement request went anywhere, because nobody's getting paid in dollars. When the dispatcher's notebook goes home in a coat pocket, the count goes with it.

Neither side is being careless. Each one is being polite. Billing a friend feels like an accusation, so both offices do what politeness suggests, which is nothing. The result is two half-ledgers pointed at each other, and no date on the calendar when anyone has to add them up.

Memory settles low, and it settles late

Come December, the square-up happens the way it was always going to: two owners, two coffee cups, two numbers neither can prove. Denny remembers two solid weeks of trucks. Carl's scale says the rock side ran to about 1,400 tons of base, except he's working from the tickets he can find, and the ones keyed to internal use aren't in the stack. Call the rock $16,000 at the posted rate. Call the hauling $27,000 at what Denny bills strangers. Neither number was ever written where the other man could see it grow.

Here's what twenty years of friendship does to that conversation: both men round toward the other guy. Denny knocks a few days off his truck count because one rig broke down, he thinks, or was that the year before. Carl doesn't mention the loads he can't find paper for. They settle on "call it even, you get the first two weeks in May again." But even is a number, and nobody computed it. Whichever side was actually ahead just donated the difference, and the donation compounds, because next year's deal starts from this year's guess.

A skeptic will say the gap washes out over a long relationship. Ask the skeptic how he knows. The whole feature of this arrangement is that no record exists to check. A wash you can't verify isn't a wash. It's a hope with a friendship riding on it.

flowchart TD
  A["Rock crosses the scale: ticket prints"] --> B{"Standing trade rule behind the ticket?"}
  B -- "no: N/C scrawled in the margin" --> C["Tickets scatter: system, folder, internal use"]
  B -- "yes" --> H["Both sides invoice at ruled rates"]
  D["Denny's trucks haul in May"] --> E["Load count lives in a notebook"]
  C --> F["December: two owners, two guesses"]
  E --> F
  F --> G["Settled at 'call it even'"]

Bill your friend at full rate

The fix costs you a habit that feels rude: run the trade like two customer relationships that happen to point at each other. Every load of rock invoices to the contractor at the posted rate, on paper, on schedule. Every hour or load of May hauling invoices back at his standard rate. The invoices net against each other, and once a season somebody writes one small check for the difference.

Plenty of owners flinch here, and the objection deserves a straight answer. The invoice isn't a collection demand. It's the count. You can trade at a discount or forgive the whole balance at Christmas, and both of those are decisions you can only make about a number you have. Skip the counting and what you're left with isn't generosity, since neither of you knows who gave what.

Structurally this is ordinary billing. The trade partner is a customer account. The arrangement itself is reference data: which account, what work offsets what, over what window, at what rates. Written down once, not retold each December. The rate is a billing rule, so a trade load prices like any other load instead of inheriting whatever the scale operator improvised. A ticket marked no-charge with no standing arrangement behind it isn't invoice-ready, and it should get flagged the week it's captured, while somebody still remembers which handshake it belongs to. Termco's part is exactly that machinery: digitize the tickets, flag the ones no rule can explain, hold the arrangement as structured rules and reference data, and assemble invoice totals from tickets that priced cleanly. Whether you ever cash the netted check is between you and Denny.

The test that comes before any of that is one count on last season: every ticket marked no-charge, trade, or keyed to the house account over 90 days, priced at posted rates, set against whatever paper says what came back in trade over the same stretch. Two numbers that land close mean the handshake is holding. A second number that can't be produced at all means something more useful: this operation is on the unpaid side of a deal it can't even size.

If you'd rather have another reader on that stack, send 10-20 sample tickets to hi@termco.ai, no-charge and trade tickets included, and we'll send back what we find within 48 hours.