The Calendar Behind the Calendar: Why a 30-Day Invoice Can Take Forty-Five

Most suppliers treat the payment term as the promise. A purchase order says 30 days, the invoice is dated correctly, and the assumption is that the money will arrive on day 30. In practice, the term is only one input into a larger machine. The date on which cash actually leaves a customer's bank account is set by an internal payment-run calendar — a sequence of approval windows, invoice cut-offs and settlement cycles that sits behind the contractual term. Miss the right window and a compliant invoice can wait another month. The cut-off that matters is often the one before the cut-off you have been told about.

Where the real due date lives

For a small supplier, an invoice is a request for payment. For a larger customer, it is a record that must pass through goods receipt, purchase-order matching, authorisation and, finally, a scheduled payment run. Each stage has its own timetable. The finance team may process supplier payments only once a week, twice a month or on a fixed day near month-end. The accounts payable system may reject an invoice that lacks a valid purchase order number, even if the work was authorised by email. A missing remittance detail can hold a payment after approval has been given.

The contractual due date remains legally important. It determines when statutory late-payment remedies may become available and when a supplier is entitled to press for interest. But the contractual date does not tell you when the customer's bank will actually release funds. That is a cash-flow question, and it deserves a separate answer before you agree terms.

Three clocks, not one

A useful way to think about the payment run is to separate three clocks.

The first is the approval clock. How long does the customer take to confirm that the goods or services were received satisfactorily? In some organisations, a manager has five working days to approve an invoice. In others, approval waits for a monthly review meeting. The approval clock can run independently of the payment term, and it often starts only when the invoice reaches the right queue.

The second is the cut-off clock. The customer's finance function will have a date and time by which an approved invoice must be loaded into the next payment run. This may be several days before the run itself. An invoice that arrives after the cut-off is not necessarily disputed; it is simply queued for the following cycle. A 30-day term can therefore produce a 45-day wait without anyone breaching the contract.

The third is the settlement clock. BACS payments still follow a processing cycle rather than arriving instantly. A payment entered into BACS does not usually reach the supplier's account on the same day. Faster Payments can move money quickly, but many organisations use batch processes for supplier runs. If a payment run falls just after a weekend or a bank holiday, the settlement clock adds further days.

Mapping the rhythm before you quote

Suppliers often discover the real payment cycle only after the first invoice is overdue. A better approach is to ask before the first order. The questions need not be confrontational. They are simply part of understanding the customer's cash-flow arrangements.

Ask the customer's accounts payable team four practical questions: when the supplier payment run takes place; what the invoice cut-off is for that run; what approval is required before an invoice can be included; and whether the organisation observes a month-end or year-end freeze. A procurement contact may not know the answers, so ask for the accounts payable contact early.

Public information can help. Large UK companies and limited liability partnerships are required to report payment practices, and their published reports often reveal average payment days and the proportion of invoices paid within agreed terms. That data does not show the internal cut-off, but it can tell you whether the customer's stated terms are realistic. A company that reports long average payment times alongside a 30-day term is signalling that the payment-run calendar is doing more work than the contract implies.

Build cut-off dates into terms and follow-up schedules

Once the rhythm is known, it should be written into the commercial arrangement. If the customer's payment run is on the 20th of each month and the cut-off for inclusion is the 10th, a supplier can agree that invoices will be issued by the 5th. That gives both sides a workable timetable and removes the ambiguity that leads to disputes.

The follow-up schedule should follow the same logic. Do not wait until day 30 to check whether an invoice has been received. Confirm receipt within two working days, confirm approval within the customer's stated approval window, and confirm inclusion in the next payment run before the cut-off passes. If the customer cannot confirm inclusion, ask which cycle the invoice is expected to enter. A short written record of that exchange is valuable if the payment later slips.

Warning signs that an invoice has fallen into the next cycle

The most common warning sign is silence after delivery. If the customer usually sends a remittance advice but none arrives, the invoice may not have been loaded. Another sign is a request for a duplicate invoice shortly before a payment run. That often means the original was mislaid or rejected by the matching process. A change in the purchase order number, a query about a delivery note, or a sudden request for a credit note can all push an invoice out of the current cycle.

Suppliers should also watch for the month-end freeze. Many organisations close their ledgers for a period at month-end or year-end and do not process new supplier invoices during that window. An invoice submitted in the last week of the month may be treated as received in the following month, even if it is dated earlier. The same applies around public holidays and the Christmas period, when finance teams operate with reduced staff and payment runs are compressed.

A routine worth keeping

None of this requires confrontation. It requires a calendar. For each significant customer, record the payment-run date, the invoice cut-off, the approval window and any known freeze periods. Diarise the cut-off a week in advance and check that the invoice is in the queue. When a payment is made, note the date and compare it with the contractual due date. Over time, the pattern becomes clear, and the supplier can quote and plan with a more accurate view of when cash will actually arrive.

The contractual term tells you what the customer has promised. The payment-run calendar tells you what the customer's finance function will do. A supplier who understands both is better placed to avoid the quiet gap between an invoice arriving on time and a payment leaving on time.