Ask a payables team how often they pay and the honest answer is usually “weekly, plus the urgent ones”. The urgent ones are the tell. A schedule that needs regular exceptions is not a schedule; it is a default with a list of overrides.
Why runs multiply
They multiply because a missed invoice is somebody’s problem immediately and the schedule’s problem never. Nobody defends the calendar at four in the afternoon when a supplier is threatening to stop shipping, so the run happens, and the next invoice that misses has a precedent to point at.
Within two quarters the calendar describes nothing and every invoice is potentially urgent, which means every invoice has to be looked at when it arrives rather than when it is due.
What a single run needs
Three things, none of them a tool:
- A cut-off that is earlier than the payment date by the length of the approval chain. If approvals take four days, a Friday run has a Monday cut-off, and that has to be written down where suppliers can read it.
- A named exception path with a cost attached. Off-cycle payments should be possible and visibly more expensive in effort, or they become the path.
- Terms that were negotiated against the calendar. A supplier on net 14 and a monthly run is a guaranteed exception every single month.
The part that is actually about relationships
Suppliers do not mind being paid on a schedule. They mind not knowing which schedule. A supplier who can predict the date plans around it; a supplier who cannot calls, and the calls are what makes payables feel like an interrupt-driven job.
Publishing the run dates on the purchase order does more for the phone volume than any amount of internal process work.
Measuring it
Count off-cycle payments as a share of total, and the days between approval and payment. If off-cycle is above one in twenty, the cut-off is wrong rather than the discipline.
