Your Rate Sheet Has a Date on It

A scale ticket records what happened: 24.1 tons of crusher run, truck 14, August 12, delivered to the Miller site. What that load is worth appears nowhere on the ticket. The price lives in other paper entirely: a haul contract signed three years ago, a rate sheet somebody emailed last spring, a fuel surcharge table stapled inside a binder in the billing office.

All of that other paper shares one property: every piece of it has a date on it. The contract has an effective date and an escalator clause keyed to its anniversary. The rate sheet says "effective March 1" at the top. The surcharge table changes with a published diesel index, weekly, whether you look at it or not.

One ticket, one billable event means more than "every load gets invoiced." It means every load gets invoiced at the rate that was in force on the day the load happened. That second half is where operations that never lose a single ticket still leak money, because the ticket and the rate live on two different calendars, and nobody's job is to keep those calendars joined.

Terms that only exist on certain days

Some pricing terms sit still. A flat $8.50 per ton for pit-run gravel is the same in January as it is in July, and any clerk can apply it from memory.

The terms that leak are the ones with a clock inside them:

• Escalators. The haul contract says rates increase 3% on each anniversary, and the anniversary is a Tuesday in April. Nothing happens on that Tuesday unless a person makes it happen, and the person who negotiated the clause is rarely the person cutting invoices.
• Index-linked surcharges. The fuel surcharge steps up when the DOE diesel average crosses a threshold. The index moved in October. Your surcharge table was printed in June.
• Seasonal rates, which switch on and off by date: winter maintenance premiums, harvest hauling, frost-law detours.
• Temporary terms that were supposed to die. The discount you gave a customer "through end of Q2" to win a job. Q2 ended. The discount didn't.

Notice the shape of the failure in each case. No ticket goes missing. No quantity is miskeyed. Every invoice adds up and every line matches a real load. The books are internally consistent and quietly wrong, because the rate applied was the rate in force on some earlier date.

The uninvoked escalator, priced out

Run the arithmetic on the mildest case, a hypothetical but a familiar one. A hauler moves 60 loads a week for one aggregate customer, averaging 22 tons a load, at $7.00 per ton. The contract carries a 5% annual escalator. The anniversary passes and nobody invokes it.

That's 35 cents a ton left on the table. Per week: 60 loads times 22 tons times $0.35, or $462. Across a year, about $24,000, from one clause, on one customer, with zero tickets lost. If the same anniversary slips two years running, the miss compounds, and the eventual catch-up conversation gets harder, not easier, because now you're asking a customer to accept a 10% jump they never budgeted.

Here's the claim worth arguing about: skipping that escalator bought you nothing. It isn't goodwill. Your customer didn't notice, because nobody audits an invoice for charges that should be higher. There was no phone call where you generously waived it. The money just stayed still, the way a ticket under a truck seat stays still. If you actually want to give a loyal customer a break, you can do that on purpose, in writing, and get credit for it. A lapsed escalator is a discount nobody thanked you for.

The same logic runs in reverse, and it's worse. An expired winter rate still billing in May, or a temporary premium that outlived its job, is an overcharge. Those get noticed. That's a credit memo, a dispute, and a customer who now reads every invoice line for a year.

flowchart LR
  A["Haul contract: 5% escalator each April"] --> B["Rate in force: $7.35/ton"]
  C["Rate sheet in billing office: dated last year"] --> D["Rate applied: $7.00/ton"]
  E["Haul ticket: 22 tons, Aug 12"] --> D
  B --> F["Gap: $0.35/ton on every ticket since April"]
  D --> F

Why the calendar has no owner

Walk through who touches the price. The scale operator prices nothing; the ticket leaves the scale house with a weight and a product code. The driver prices nothing. The billing clerk applies whatever table is in front of them, and the table in front of them is the last one anybody handed over. The person who actually negotiated the escalator was the owner or the sales lead, and their attention moved to the next contract the week this one was signed.

So the knowledge that a rate should change on a date lives with the person least involved in applying rates, and the person applying rates has no reason to doubt the sheet in front of them. That gap isn't carelessness so much as structure, and it will produce the same miss next April regardless of how conscientious everyone is between now and then.

Month-end true-ups are the tell. If your team regularly issues catch-up invoices or credits once somebody "remembers the new rates," each true-up is an admission that tickets were priced wrong the first time and a person, not the process, caught it. Whatever that person doesn't remember will sit unbilled the same way.

What "in force on the ticket's date" takes

Asking everyone to be more vigilant won't hold. The rate term has to carry its own dates, the same way the ticket already carries one.

A billing rule that says "$7.00 per ton" is incomplete. The complete version says "$7.00 per ton, effective April 2024 through March 2025, then $7.35." Once rules are structured that way, pricing a ticket stops being a memory exercise: the ticket has a date, the rule has a window, and the join is mechanical. A ticket that prices against a rate whose window doesn't cover the ticket's date isn't invoice-ready, and it should get flagged the same way a ticket with a missing job number gets flagged.

That's the standard worth holding your process to, whether you build it in software or in a disciplined spreadsheet: could a stranger, given only your tickets and your written rate terms, reproduce this month's invoices to the penny? If the honest answer is "they'd also need to ask Dave about the Miller account," some of your pricing lives in Dave, and Dave takes vacations. Every clause with a date in it is a place where this month's invoices can drift from this month's contract without a single ticket going missing.

If you want a second set of eyes on yours, send 10-20 sample tickets to hi@termco.ai and we'll send back what we find within 48 hours.