A Payment Run Is a Cash Control, Not an Admin Routine
In a lot of growing businesses, supplier payments happen when someone gets to them. An invoice arrives and gets paid. A supplier calls and gets paid. Someone opens the banking platform on a Thursday and clears whatever's visible.
It feels responsive. It's actually one of the more expensive habits in the finance function.
What ad hoc payment costs
You lose the value of your terms. If your suppliers give you 30 days and you pay on day 10, you have voluntarily shortened your own working capital cycle by twenty days. On a business spending $400,000 a month with suppliers, that's roughly $260,000 of cash sitting outside the business earlier than it needed to. You negotiated those terms — or inherited them — and then gave them back for nothing.
Prioritisation becomes reactive. Without a run, payment order is determined by who applies pressure. That's an inversion of commercial logic. The supplier who chases hardest is rarely the one whose relationship matters most to your delivery, and the one you can least afford to lose is often the one who doesn't chase at all.
Controls fall away. A payment run creates a natural checkpoint where someone reviews the batch before it's released. Ad hoc payments have no such point. Duplicate payments, invoices paid without the goods being received, price variances against the PO, and payments to accounts that were never verified all become materially more likely.
Forecasting becomes impossible. This is the one that matters most. A thirteen-week cashflow forecast is only as good as its outflow assumptions. If nobody can say what's leaving next Tuesday, the forecast is an estimate built on an estimate.
What a payment run looks like
The mechanics are simple, and the whole thing is a one-hour setup.
A fixed day each week. A cut-off — invoices approved by close of business the day before are included; anything after waits for the next run. A batch prepared by the bookkeeper, listing every payment with supplier, amount, invoice date, due date and job reference where relevant. A review by whoever holds authority, checking totals, exceptions and anything unusual. Then one release.
Two things make it work in practice.
The first is a genuine exception process. There will always be a payment that can't wait — a deposit releasing a long-lead item, a subcontractor who can't mobilise otherwise. Exceptions are fine. Undocumented exceptions that become the norm are not. Name them, approve them separately, and count them. If you're running twelve exceptions a week, the run isn't working.
The second is paying on due date rather than as early as the run allows. The run tells you what's payable; it shouldn't automatically mean everything gets paid this week. Sequence by due date and hold what isn't due.
The reporting that falls out of it
Once payments are batched, some genuinely useful information becomes available almost for free.
You get a forward outflow number — what's due next week, the week after, and the week after that. That single figure turns a cashflow forecast from a guess into a schedule.
You get supplier concentration — what proportion of your spend goes to your top five suppliers, which is worth knowing before you need to negotiate with any of them.
You get a real view of whether you're actually using your terms, which tends to be a surprise. Most businesses that check discover their average payment day is well inside their agreed terms.
The wider point
Accounts payable is often treated as the lowest-value activity in the finance function — data entry followed by button pressing.
It's actually one of the few places where a process change produces an immediate, measurable cash improvement without touching pricing, sales or delivery. Moving average payment day from 12 to 28 is a one-off working capital release, and it requires nothing more than deciding when payments happen.
Structure at the transaction level is what makes control possible at the management level.