Hauled on the Second, Billed on the Thirty-First

Your invoice says net 30. Follow one load and count the real number.

The ticket is dated July 2: 24.3 tons of three quarter clean, delivered to a paving contractor who's been on terms with you for years. The yellow copy comes home that afternoon and lands in the keying tray. There it sits, in good company, while July happens. The tray gets keyed the last week of the month, the invoice run prints on the 31st, and the envelopes go out August 1. Net 30 from invoice date: due August 30.

The contractor pays to the day, fifty-nine days after your loader touched his truck. He kept his word exactly. The other twenty-nine days were a loan from you to him, and you made the same loan to every load in the month, every month, without once writing it down as a policy.

Terms start when the invoice exists

Net 30 doesn't begin at the scale. It begins at the invoice date, and the invoice can't exist until the tickets behind it are keyed. Every day a ticket spends in the tray gets added to the front of the terms, where no aging report will ever show it. The aging clock starts at the invoice. The waiting before the invoice is nobody's column.

Do the spread. A load hauled on the 2nd waits 29 days to bill. One hauled on the 28th waits three. Across a month the average load waits about two weeks, which means on a monthly cycle your real terms average out near net 45 across the book, including for customers you'd never have approved at net 45 if they'd asked.

They didn't ask. That's the part worth sitting with. Stretching a customer's terms is a credit decision, the kind that should carry an owner's initials. This one got made by a tray.

Nobody chose monthly

Ask why the office bills monthly and you'll hear that customers expect it, or that it's how it's always been done. Trace it honestly and the answer is mechanical: billing is monthly because keying is monthly, and keying is monthly because keying is batch work that loses to everything louder than it. The cycle wasn't designed. It's a shadow cast by the backlog.

You can test that in one sentence. Ask your office what it would take to invoice any one job you pick for just last week, today. If the answer involves pulling paper out of the tray and keying it specially, your billing frequency isn't a policy. It's a symptom. The office that says we bill monthly almost always means we key monthly, and those are different confessions.

flowchart TD
 A["July 2: 24.3 tons delivered"] --> B{"When does the tray get keyed?"}
 B -- "month end" --> C["July 31: invoice prints"]
 C --> D["Due August 30: 59 days from the load"]
 B -- "keyed daily" --> E["July 3: ticket priced and cleared"]
 E --> F["July 4: weekly invoice prints"]
 F --> G["Due August 3: 32 days from the load"]

A four week old invoice collects four week old arguments

The float is the visible cost. The quieter one is what a month of distance does to disputes.

When the July invoice lands on the contractor's desk in early August, the loads on it are four to six weeks old. His project manager reviews 23 lines in one sitting, long after the foreman who waved those trucks in has moved to another site. Any line he doubts, he doubts from paperwork, and so do you, because your driver doesn't remember July 9 either. Questions that would've been settled in one radio call while the job was live become letters. And while one line gets argued, the other 22 wait, because he holds the whole invoice, not the line.

A weekly invoice puts the same question on his desk while the crew is still on site and the week is still in everyone's head. You're also still hauling for him, which is a politer form of pressure than a statement in October.

There's an inside version of the same decay. The tray is where your own problems surface: the ticket with no signature, the serial that should be there and isn't. On a monthly cycle, you discover the hole on the 29th, when the ticket that could explain it is four weeks gone and the trail is cold. So the lag costs you twice: the money arrives late, and so does your knowledge of your own month.

Weekly, and the honest objections

So here's the claim your office manager will push back on: account customers should get an invoice every week, and monthly consolidation should be something a customer asks for and you grant, not something your backlog imposes on everyone.

The objections deserve a straight answer. Some AP departments really do want one invoice a month, matched to a statement, and will pay two consolidated invoices slower than one. Fine. Give those accounts monthly on purpose, written into their terms like any other term, priced like one too, because next to a weekly cycle, consolidation holds your money about eleven extra days on the average load. Most of your accounts never asked. They got monthly because you had a tray.

The sharper objection is speed: a faster cycle ships errors faster. If your invoices are clean because a veteran clerk repairs tickets on the way through, then weekly billing means weekly mistakes. True, and notice what it argues for. It says the keying is the weak joint, not the calendar. Sitting on the paper for three extra weeks never made the paper more correct; the mistakes just wait in the tray with everything else.

Count your own lag

The audit takes twenty minutes. Pull ten recent invoices. For each line, subtract the ticket date from the invoice date, then average the whole set. That number is your invoice lag: the days of credit you extend before your own terms begin. Multiply it by your average daily billing and you're looking at the money that lives permanently in the gap, cash you've lent out at zero and borrow back at whatever your line costs.

Closing the lag is mostly a reading problem, which is the slice Termco works in. Tickets get digitized the day they're written, exactly as your drivers and scale operators write them, checked against your billing rules, with the broken ones flagged that day instead of discovered on the 29th. Invoice totals assemble from the tickets that cleared, so the totals for last week's invoice can exist on Friday, and each account's cycle, weekly or consolidated, lives in reference data instead of in habit. Nothing changes in the truck or at the window: same books, same pens, no app. If you want to see whether your paper could carry a weekly cycle, send 10-20 sample tickets to hi@termco.ai and findings come back within 48 hours.

The contractor on that July invoice was never late, not once in years. Check how long he's actually holding your money before you credit him for that. The slowest step between his truck and your bank account isn't his AP department. It's your tray, and it's the only step in the whole chain that you own outright.