The Fixed Date You Missed by One Day
Money leaves a large organisation on fixed dates. An invoice approved the day after one waits for the next, which is usually a month.
Theirswho controls this stretch
Where thirty-day terms went on four consecutive invoices, same buyer
Caught the run; close to the stated terms.
Approved two days after the cut-off.
Caught the run again.
Missed it again, by three days.
The same terms produced thirty-one days twice and about fifty days twice, and the difference was the cut-off. Nothing was breached in any of the four. One supplier's own record with one buyer, not a benchmark.
Large organisations do not pay invoices as they are approved. They pay in runs, on fixed dates — weekly, fortnightly or monthly — and an invoice approved the day after a run waits for the next one.
The delay in “The Fixed Date You Missed by One Day” needs separate timestamps for work, approval, invoicing and settlement. Teams reviewing how to calculate idle time for service teams for how to calculate idle time can strengthen the work-record part of that chain without pretending to explain what happened inside the customer’s accounts-payable process.
A single day can therefore cost four weeks, and nothing about the invoice or the work has changed.
For an independent reference relevant to “The Fixed Date You Missed by One Day”, consult NFIB small-business finance resources. Compare general information with the contract, jurisdiction, payment route and accounting records involved.
Why runs exist
Because paying individually is expensive and because batching lets the organisation manage its own cash.
It is ordinary treasury practice and not directed at anybody.
How often they happen
Monthly in many large companies, fortnightly in some, weekly in a few. Public bodies often run more frequently.
The frequency is the single biggest determinant of how variable your payment dates will be.
The cut-off before the run
An approved invoice must be in the ledger by a cut-off date, typically several days before the run.
So the practical deadline is earlier than the run, and earlier again once approval time is allowed for.
What this does to "thirty days"
An invoice due on the 20th, approved on the 22nd, with runs on the 1st, is paid on the 1st of the following month: forty-two days from a thirty-day term, with nobody at fault.
Knowing the dates
Ask. Two questions to accounts payable, answered immediately.
With them, you can predict your own receipts far better than any forecast built from terms alone.
Invoicing to catch a run
Entirely legitimate and worth doing. If approval takes a fortnight and the run is on the 1st, an invoice sent on the 5th catches the next one and an invoice sent on the 20th does not.
This is the practical reason to invoice the day the work is done.
Off-cycle payments
Most organisations can make one, for emergencies, with senior approval. It is a favour, it is remembered, and it should be spent on a genuine cash crisis rather than on irritation.
Asking for one routinely ensures it will not be granted when it matters.
The supplier who is always just missing
A pattern worth looking for in your own records: invoices consistently paid five weeks after a four-week term.
It usually means your invoicing day sits just after their cut-off, and moving it by three days fixes it permanently.
What the run tells you about lateness
An invoice that has been approved and scheduled is not late in any useful sense, whatever the term says. It has a date.
An invoice that is approved and not scheduled is a different situation and worth asking about.
Why a run is not an inconvenience
Batching payments is how any organisation with more than a few hundred suppliers controls its cash and its bank authorisations. One authorised file on a known date, reconciled once, with one set of approvals, instead of several hundred individual transfers requiring individual sign-off.
From inside the buyer it is basic treasury practice. From outside it looks like an arbitrary delay attached to money that was already approved.
Both are true, and the second is not a grievance anybody will act on. What the run gives a supplier is predictability: a payment that depends on a fixed date is much easier to forecast than one that depends on how busy somebody is, and the dates do not move.
What this does to a stated term
Thirty-day terms against a monthly run do not produce payment on day thirty. They produce payment on the first run that follows approval, which for a supplier whose invoices tend to be approved just after the cut-off is reliably day fifty or more.
Nothing is being breached. The term governs when the invoice becomes payable; the run governs when payable invoices are paid.
This is why comparing a customer's stated terms with your actual experience so often produces a gap that nobody can account for, and why the gap is stable rather than random. A supplier who records the dates discovers that the same customer pays on the same part of the month every time, and can then do the only thing available: move its own submission earlier so that approval lands before the cut-off rather than after it.
That adjustment is free, repeatable and invisible to the buyer, which makes it the most useful thing in this note.
Recording it
Per customer: run dates, cut-off, typical approval time. Three fields.
From them you can compute, before sending, the date you will actually be paid — which is the information every cash forecast needs and almost none contains.