Once invoices are approved, paying them is largely a matter of rhythm and control. Three decisions shape the experience for both sides: how often payment runs happen, who is allowed to release one, and whether the supplier is told what a payment covers. None is technically difficult and all three are frequently left to whatever happened historically.
The rhythm
Weekly runs suit most organisations. Fortnightly adds an average wait that suppliers experience as slowness, and daily mostly adds administration without changing anything a supplier notices. Whatever you choose, choose it deliberately and tell suppliers, because a predictable payment date removes most of the chasing you currently receive.
The release
Whoever prepared the run should not be the only person able to release it. This separation is old, simple and effective, and the moment it usually lapses is absence, which means the cover arrangement deserves as much thought as the rule. Automation should make it enforceable rather than quietly optional below some threshold.
The remittance
A short note listing which invoices the payment covers, sent automatically as part of the run. A supplier receiving one transfer covering eleven invoices cannot allocate it without this, and an unallocated payment produces a call to you. It costs nothing, it is one of the few payables improvements with no trade-off at all.
Questions people ask about invoice payments
Should we ever pay outside a run?
Sometimes you must, and it should be visible as an exception with a reason. Ad hoc payments are where controls most often lapse.
Is paying early worth it?
Only where a discount exceeds your cost of capital and the cash is available. It is a finance decision rather than a payables one.
How do we handle bank detail changes?
Verify through contact details you already hold, by somebody other than whoever received the request, and record the verification.