The Rent Nobody Invoices

A farmer, call him Loren, delivered 22,000 bushels of corn to your elevator last October and priced it this July. The settlement sheet prints four deductions, and the one he reads twice is storage: $7,700. He doesn't dispute the math. He stands at the counter looking at it, checkbook out, and your manager, who has known him twenty years, says let's call it six thousand even.

Nobody booked a $1,700 loss that morning. There was nothing to book it against. The charge had never been invoiced, so forgiving a fifth of it reversed nothing. It set the price of a number that had accrued quietly for nine months and surfaced thirty seconds before it was negotiated away.

A ticket with a meter on it

One ticket, one billable event. At the scale that rule is clean: the load crosses, the ticket prints, the line bills. Storage is the case where the ticket does one thing more. Every inbound load that lands in open storage starts a meter. Your own rate schedule, taped to the office window, states the terms the way a landlord would: 60 days free, then five cents a bushel per month until the grain prices or moves.

Rent is the right word, and it exposes the strange part. Rent never waits. Your landlord doesn't hold three years of it for move-out day and hope the conversation goes well. Storage at most elevators is the only rent in the county that bills once, at the end, in a lump, at the exact moment the tenant is holding a check.

And the bin worked the whole time. It held his bushels through a winter and a spring, carried the aeration, took up space you could have offered the next patron while the paper sat quiet.

Nineteen clocks, one guess

The free period runs from the ticket date, and harvest doesn't arrive on one ticket. Loren's corn came in on 19 loads between September 18 and October 24, which means the schedule handed your office 19 clocks, each starting its own 60 days.

Nobody runs 19 clocks by hand. At settlement, months later, the clerk picks a date: the last load, or November 1, or whenever the dryers shut down that fall, and starts every bushel's meter there. It's the defensible choice, since no farmer will argue with the latest possible date. It's also a gift. The September loads just collected free weeks the schedule never granted. On this one account, call it 14,000 early bushels times three extra free weeks at a nickel a month: about $520. Small, until you multiply it by every storage account in the book, every year, and notice the guess only ever lands on the late side.

Commodity terms compound it. If your house posts corn free through December 31 but beans at 60 days flat, the clerk under a month-end stack tends to apply whichever rule she reaches for first, to both.

Accruals age into arguments

A storage charge presented once, at settlement, shows up already weakened.

It lands at the worst moment, while the patron watches his gross get whittled. It's old: the storage from month two is seven months stale by now, your ticket stack against his memory of when he hauled. And on that sheet it's the only soft number. He can't argue the moisture, a probe measured it. He can't argue the weight. The storage line is built from dates and a schedule, and dates, unlike weights, feel negotiable.

So the counter does what counters do. The disputed ones get shaved. The undercomputed ones sail through, because no farmer in recorded history has flagged a storage bill for being too small. The asymmetry runs through all ticket billing, except here you built it yourself, by letting the number get old enough to argue with.

flowchart TD
  A["Inbound ticket: 1,180 bu, Oct 3"] --> B["Free period: 60 days from ticket date"]
  B --> C["Storage accrues: 5 cents per bushel per month"]
  C --> D{"When does it bill?"}
  D -- "once, at settlement" --> E["Months of charges in one old line"]
  E --> F["Negotiated down at the counter"]
  D -- "monthly, like rent" --> G["Small current invoices, paid as billed"]

Send the bill while it's still rent

Here's the claim your board will push back on: storage that appears only at settlement isn't a rate. It's an opening bid. Either invoice it monthly, at whatever number you post, or strike it from the schedule and build it into your basis, where at least you'll collect it.

The objections are real. Patrons hate paper. The house across the river bills at settlement, always has. A $95 monthly invoice costs something to produce and something more in goodwill. Fine, weigh that honestly. But weigh it against what you're doing now, which is running an undocumented monthly discount program priced by whoever's behind the counter and whatever kind of morning they're having. A farmer who gets twelve invoices for $150 pays twelve invoices for $150. Nobody rounds one of them down to make a check feel better. The knockdown needs a big, old, arguable number to work on, and settlement-day billing manufactures exactly that.

There's also the grain that never reaches your counter at all: bushels shipped against a contract or transferred to another house, where storage gets computed in a hurry, or waved off entirely, to get the trucks loaded. Try waving off a charge that's already been invoiced for ten months. Nobody does. It's a balance by then, and balances get paid.

Give every clock a keeper

None of this asks your clerk to run nineteen clocks by hand. It asks the clocks to live in structure instead of in her stack.

Start where the clock starts. Inbound tickets get digitized the day they print, dates and bushels intact, so every load carries its own start date instead of inheriting a guess months later. The free period and the rate become billing rules with effective dates, one per commodity and program, and each ticket's storage line prices from its own date against its own rule. Corn's calendar rule and beans' 60-day rule stop sharing a habit. Which class each patron's grain sits in, open storage, warehouse receipt, or applied to contract, is reference data. A ticket whose storage line prices from some other start date, a guess, doesn't clear. It gets flagged as non-compliant before anything prints, instead of surfacing when a farmer walks in with a shoebox of his own scale copies. Invoice totals, monthly or at settlement, assemble only from tickets that cleared.

That slice is what Termco builds: digitizing the tickets, flagging the ones that break a rule, structuring the billing rules, managing the reference data, assembling the totals. The rate, the free period, and whether Loren still gets a deal remain entirely your call. The deal just becomes one you chose, on the schedule, instead of one the counter improvised with the checkbook open.

You can size both leaks this week from paper you already have. Pull the last dozen settlements that carried storage lines. Recompute each from the actual ticket dates and the posted schedule, no mercy, and set your number beside the printed one, then beside what was collected. The first gap is the guessed clocks. The second is the counter. Price them separately. They need different fixes, and only one of them is a decision you meant to make.

If you'd rather have a second reader on it, send 10-20 sample tickets to hi@termco.ai, inbound storage tickets and the settlements they fed especially, and we'll send back what we find within 48 hours.