Why paying suppliers monthly beats paying them fast.

Operators assume their suppliers want money sooner. Ask the suppliers and you get a different answer: what they want is to know when it is coming. Predictability is worth more to them than speed — and it is worth considerably more to you.

The typical independent venue pays suppliers reactively. Someone rings, or an account goes on stop, or a delivery is refused, and a payment goes out that afternoon. It feels responsive. In practice it is the most expensive way to run a purchase ledger.

What reactive payment actually costs

Three costs, none of which appear as a line in your accounts.

• Your time, at the worst possible moment. Supplier calls land during service, because that is when someone answers the phone. Every one of them pulls a manager off the floor.
• Terms quietly shrinking. Credit controllers grade accounts by how predictably they pay. Erratic payers get shorter terms, tighter limits and less flexibility, and nobody ever rings to tell you it has happened.
• No cash visibility. If you do not know what is going out next week, you cannot plan anything — not a refurbishment, not a deposit on a second site, not whether this is the month to replace the combi oven.

There is a fourth cost that is harder to see. When payment is reactive, invoices get paid because someone chased rather than because they were checked. The loudest supplier gets paid first, and the quiet ones go unexamined for months.

Paying fast rewards whoever shouts. Paying predictably rewards whoever is right.

The case for one date a month

Pick a date. Tell every supplier in writing. Pay on that date, every month, without exception. That is the entire mechanism, and it changes the relationship immediately.

A supplier who knows they are paid on the 15th does not ring you on the 8th. Their credit controller marks the account as reliable. When you need a favour — an emergency delivery on a Saturday, thirty covers' worth of something you have run out of — you are calling someone who has no outstanding grievance with you.

And critically, a monthly cycle gives you something a weekly one cannot: time to check before you pay.

The verification is the point

A fixed payment date is only half of it. If you pay predictably but pay the wrong amounts, you have simply industrialised your overpayment.

This is why the calendar runs the way it does:

1. Statements in by the 3rd. A standing instruction to every supplier, set up once. Statements arrive without anybody having to ask.
2. Reconciled by the 10th. Every invoice checked against both the ledger and the inventory system — what was ordered, what actually arrived, what you were charged.
3. Queries raised by the 10th. Price discrepancies, short deliveries, missing credits and duplicates all go back to the supplier while the invoice is still unpaid.
4. Payment on the 15th. One authorised batch, remittances sent automatically.

The five days between raising a query and paying is what gives the query force. After payment, you are asking for a credit note and waiting. Before payment, you are simply agreeing what is owed.

"But what if someone needs paying sooner?"

Then you pay them sooner. Off-cycle payments are fine — a pro-forma for a one-off order, a new supplier on different terms, a genuine emergency.

The difference is that it becomes a deliberate exception rather than the default. One decision a month, instead of forty small ones made under pressure. That is the whole benefit: you are choosing, rather than reacting.

What changes

Operators who move to a fixed monthly run tend to report the same three things, in the same order. The phone stops ringing during service. Cash becomes predictable enough to plan around. And within a couple of months, suppliers start getting their pricing right first time, because they have worked out that it is being checked.

None of that requires new software or a bigger finance team. It requires a date, a standing instruction, and the discipline to verify before paying.