The Footnote Nobody Keys

Line 41 of last month's Hendricks Landscaping invoice reads $90.10: 2.65 tons of inch and a half river rock at $34 a ton, picked up at the retail window on a Tuesday. Footnote 3 of your own rate sheet reads: minimum charge $150 per pickup load. Line 41 went out at least $59.90 light. It passed every check your office runs. Hendricks is never going to call about it.

Nobody miskeyed anything. The tons are right, the product is right, the rate matches the sheet. The line is wrong anyway, and the reason it's wrong lives in the geography of the rate sheet itself.

A rate sheet has two halves

Look at the sheet the way a system would. The top two thirds is a grid: products down the side, prices across, one number per cell. That half got keyed into your billing system years ago, and it gets read on every ticket.

The bottom third is footnotes, in smaller type. Minimum charge $150 per pickup load. Loads under 5 tons carry a $25 small load fee. After-hours loadout, $75. Waiting time past 15 minutes, $60 an hour. Saturday delivery adds $2 a ton. Every one of those lines is money, and the sheet treats them as fine print. At $34 a ton, the first two even overlap below about 4.4 tons, and nobody in your building has ever ruled on whether they stack, which is its own small footnote problem.

The two halves differ in kind, not just in type size. The grid states amounts. The footnotes state conditions: if the load is under this, if the clock is past that, if the truck is one of these, then charge something extra or charge something different. The keying screen has a field for tons and a field for rate and it multiplies them. It has no field for "unless." So the grid half of your rate sheet lives in the system, the footnote half still lives on paper, and every conditional dollar you're owed depends on a person noticing the condition, mid-stack, at keying speed.

Conditions are what volume drops first

Picture the clerk at ticket 240 of a month-end stack. Applying the grid is transcription: read tons, read rate, key both. Applying footnote 3 is different work. She has to read the extension the screen just computed, notice that $90.10 sits under the $150 floor, remember that this account is a retail pickup and not a contract hauler, and then override the number the screen is showing her. That's a judgment call run 240 times, and by 4:30 in the afternoon it isn't running. The first fifty tickets of the day get their footnotes. The last fifty get arithmetic.

Small loads make this the worst leak per dollar on the sheet, for a percentage reason. Miss a footnote on a 24-ton load and you've lost rounding. Miss the minimum on a 2.65-ton load and the footnote was most of the price: $90.10 against $150 is 40% of the line gone. And the retail window prints more tickets per dollar of revenue than anything else you do. Pull your own counts and don't be surprised if a third of your tickets are carrying a twentieth of your tonnage. The tickets most likely to carry a condition are the ones flying past the clerk in the biggest numbers.

The gap never comes back, either. A customer's AP department rereads your invoice looking for reasons to pay less, and a minimum that didn't bill is a reason to say nothing. The only party who could catch it is your own office, which is the party that just missed it.

Put loose numbers on a season, yours to swap. Say 25 pickup loads a week cross one of your thresholds, and the afternoon half get keyed straight tons times rate. Twelve misses a week at an average $45 gap is $540 a week. Over a 48-week year that's about $26,000, leaked in pieces too small for any single invoice to look wrong.

flowchart TD
  A["Ticket: 2.65 tons at $34"] --> B{"How does the line price?"}
  B -- "keying screen: tons x rate" --> C["$90.10 invoice line"]
  C --> D["Nobody calls, gap never surfaces"]
  B -- "minimum held as a rule" --> E["Rule reads the line against the $150 floor"]
  E --> F["Flagged as non-compliant for review before it invoices"]

Bill it or strike it

Here's the claim to argue about at the counter: a footnote you don't consistently bill is worse than no footnote at all, and you should either enforce every minimum, best accounts included, or take it off the sheet.

Most owners keep the minimum as a deterrent, not a charge. The point was never the $150, it was to keep the single-axles from clogging the loadout for $90 of rock. But a deterrent that never bills deters nothing, and your regulars already know it never bills. You're training the exact customers you wanted to discourage: the ones who've learned the footnote is decorative send the small truck twice a day.

The half-enforced version is worse than the ignored one. When the morning clerk applies the minimum and the afternoon clerk doesn't, two customers hauling identical loads in the same week get different totals, and the difference is which hour their ticket got keyed. Sooner or later two landscapers compare invoices at a supply house counter. The one who paid $150 calls, and there's no answer to give him that doesn't sound like what it is. Now you're crediting the enforced ones down to the leaked ones, which is the footnote billing at 0% with extra steps.

Give the condition a field

The fix is to move the footnotes into the same system the grid lives in, as rules instead of reminders.

Each footnote is a billing rule with its condition attached: the threshold, the amount, the effective date, and who it applies to. Who it applies to is reference data, because "retail pickup" and "contract hauler" have to be properties of the account, not facts the clerk carries. Tickets digitized at capture arrive with the fields the conditions read: tons, time, account. Then the comparison she was running in her head at 4:30 runs on every ticket the same way it ran on the first one, and a pickup load that prices below its ruled minimum isn't invoice-ready. It gets flagged as non-compliant that day, while the fix is one look at the account type, and invoice totals get assembled only from lines that cleared. That slice is what Termco builds: digitize the tickets, flag the ones that break a rule, structure the rules, manage the reference data, assemble the totals. What the footnotes say, and whether footnote 3 survives at all, stays your call.

You can size this one with a single sort. Pull a month of tickets under your smallest threshold and read the invoice lines they became. Count how many billed at the minimum and how many billed at straight arithmetic. The second pile, priced at the gap, is what the fine print cost you last month, and it'll cost the same next month at whatever pace your retail window runs.

If you'd rather have a second reader on it, send 10-20 sample tickets to hi@termco.ai, small pickup loads especially, and we'll send back what we find within 48 hours.