Termco
Termco

The Rate Table Has No Yesterday

16 November 2026

Every September some version of the memo goes out: effective November 1, 1 inch minus goes from $10.75 to $11.50 a ton. New sheets printed. Customers told twice, once by letter and once at the counter. Nobody could call it a surprise.

On the first Monday of November, the clerk sits down to key the last week of October. Sixty-some tickets, all dated in ink, all hauled at $10.75. Every one of them prices at $11.50, because the rate table was updated over the weekend and the system holds exactly one price for 1 inch minus: the current one.

She isn't making an error. She's typing a ticket dated October 29 into a system that has no October in it.

One price per product

Open the rate screen on almost any operations system sold to pits, elevators, and hauling outfits between 2000 and 2020 and you'll find the same shape: customer, product, number. No start date. No end date. To change a price was to overwrite it, and the old number went wherever overwritten numbers go. The system held your price, singular, and nothing else.

The design followed from an assumption the whole product rested on: that records get entered the day the work happens. If every load is keyed before dinner, the current price and the load's price are always the same number, and a dated rate table is a feature nobody needs.

Your operation never worked that way. The work gets ticketed at the gate, in ink, at gate time, and the keying happens when the office catches up, a few days behind in a good week. That gap costs nothing at all, right up until a price moves, and a price moves every fall.

Compare the drawer the system replaced. The paper era kept the old rate sheet when the new one came out, usually with "thru 10/31" penciled across the top. A clerk pricing paper read the date on the ticket and reached for the sheet that matched. That's effective dating, implemented in a drawer, for free. The software didn't improve on the drawer. It deleted it.

Two ways to eat the same week

The boundary leaks in whichever direction your office picks.

Update the table on schedule, and every October ticket still in the tray bills at November's price. The paving contractor's PM has your October quote in his job folder, finds 14 loads at the wrong rate, and now you're writing a credit memo for your own price increase, on your own letterhead.

So offices learn, and the learning hardens into a workaround: nobody touches the rate table until the tray is empty. Now the increase waits on the backlog. The loads hauled November 1 through 7 bill at $10.75, because the table couldn't hold both numbers and the tray held a week of October. Put a figure on it: 35 loads a day, 23 tons apiece, 75 cents a ton, seven days. Call it $4,200, given away in a week, every fall, for as long as you've run the system. Nobody approves it. There's no line for it anywhere. The increase simply starts a week after it started.

The same collision runs all year at smaller scales. The fuel surcharge that moved Monday meets Thursday's keying, and the discount you granted mid-month meets loads hauled before it. The annual escalator on the paving contract ticks over while its tickets are still riding home in a cab.

The quiet version costs the most. Two years on, a customer disputes what the price was on a given day, and your system can't testify, because the table holds no history. It knows what you charge. It has no idea what you charged. Whoever kept paper wins that argument, and if neither side did, the louder one does.

The workaround was the process change

Ask the vendors of that era about the boundary week and you got procedure, not apology. Complete all pending entries before updating rates. Schedule changes for Sunday night. Effective-dated pricing existed, in fairness, in the enterprise tier, priced for operations with an IT department. At the tier a pit or a 12-truck outfit could buy, every answer amounted to the same instruction: rebuild your office's calendar around the software's amnesia. Freeze the keying and hope nothing arrives late.

Here's the claim that should start a fight with whoever sold you the system: if it keeps one price per product, you have never billed an increase week correctly except by hand, with a clerk overriding lines one at a time, which is the keying the system was bought to end. Left to the table, you overcharged the stragglers or you undercharged the new week, and the only question was which, settled by whether the update ran before or after the tray cleared.

The owner who kept the carbon books and the drawer of dated sheets took his share of grief through those years. Notice what he held that the system never did: a complete price history of his own business, in ink, with dates on it. His office could answer "what did we charge last March" by walking to a drawer. The office that modernized had to answer it from memory. He was declining to trade a drawer with dates for a screen without them, and the wait paid: software can finally read the drawer instead of replacing it.

flowchart TD
  A["Ticket in ink: Oct 29, 23.2 tons at $10.75"] --> B{"Where does the boundary land?"}
  B -- "table updated on time" --> C["Keyed Nov 3: bills at $11.50"]
  C --> D["Customer holds the October quote: credit memo"]
  B -- "table frozen until tray clears" --> E["Nov 1-7 loads bill at $10.75"]
  E --> F["A week of the increase never bills"]
  B -- "dated rates, ticket read as written" --> G["Each load priced by its own day"]
  G --> H["Invoice matches the quote, both weeks"]

Price every load off its own day

The fix starts with the date your gate already wrote, which is the posture Termco is built on. Each ticket gets digitized as written, ink date included, and rates live in reference data with a start and an end, so the table finally has a yesterday. Billing rules price each load off its own day. A load priced against the wrong period gets flagged as non-compliant before the invoice leaves, and invoice totals assemble from the tickets that cleared. Nothing changes at the window or in the trucks: same books, same pens, and the tray can run as deep as the season makes it, because the date rode in on the paper.

If you want to see how your own tickets would price across a boundary, send 10-20 samples to hi@termco.ai, especially the ones from an increase week. Findings come back within 48 hours.

Run this fall's test either way. Pull the tickets hauled in the last week before your most recent increase and the first week after, and check the rate each one actually billed. The ones keyed across the line will tell you which direction your office eats the boundary, and what the habit costs you a year. The date was on every ticket, written at the scale by somebody watching the truck. The paper always remembered. The system you bought to replace it was the only part of your operation that couldn't.