A Weekly Supplier Payment Run: The Order That Prevents Double Payments

Paying suppliers "when there is time" produces three standing costs: suppliers calling to ask, invoices paid twice, and no picture of what the business owes. One fixed payment day a week solves all three, provided the order inside it is defined.

Why a fixed day beats paying under pressure

Without a fixed day, payment order is set by who called. That produces a familiar distortion: quiet suppliers wait two months and suppliers who call get paid immediately, with no relation to the terms agreed with them.

The larger cost is the hidden one. When there is no batched run, there is no moment at which all supplier debt is visible together, so cash flow decisions are made without the central number. A fixed day creates that moment once a week, for free.

The seven steps of the run

1. Cut-off - every invoice received and approved by noon the previous day is in; later than that, next week.
2. Filter by due date - a supplier's net-30 does not start on arrival but on the agreed term.
3. Document check - a valid withholding tax certificate, current bank details, an approved invoice.
4. Build the payment list - amounts, payees, references.
5. Approval - whoever approves is not whoever entered; that alone prevents most errors.
6. Create and send the file - and immediately afterwards mark the invoices as paid.
7. Reconcile - after the value date, confirm every row went out and handle rejections.

Step 6 is the heart of it. Many businesses mark an invoice paid only once they see it on the bank statement, and that is a two-day window in which the invoice looks open - and somebody pays it again.

What to check before building the file

The withholding certificate check is made against the Tax Authority's certificates system by business or company number, and it returns the withholding rate or the exemption. There is depth on that step in checking a withholding tax certificate before paying a supplier.

The cut-off is the most important decision

Step 1 looks like an administrative detail and it is what decides whether the run works. Without a defined cut-off, every invoice arriving on the morning of payment day gets in "because it is already here", the run is then delayed an hour to approve it, and sometimes an invoice nobody checked is paid.

A one-day cut-off fixes that for two reasons. First, it gives whoever approves real time to check rather than a gap between two calls. Second, it turns the answer to a supplier who calls into a simple one: the invoice arrived after the cut-off, it is in the next run, on this date. That answer ends a conversation; "we will try this week" generates another one in three days.

What has to be explicit in the cut-off is not only the time but what exactly is counted: the date the invoice was received, or the date it was approved. Both definitions are legitimate, and confusing them is a source of internal argument at nearly every business that never wrote them down.

Changed bank details: the check you cannot skip

The pattern repeats: an email arrives apparently from a long-standing supplier announcing a change of bank account, close to a payment date. The address is similar, the signature is right, and the request is entirely reasonable.

The only operational rule that works is never to verify a change of bank details on the channel it arrived through. A phone call to the number stored in your system - not the number in the email - is all it takes, and it has to be a mandatory step on the checklist rather than the judgement of whoever is handling it.

What to do with a rejected row?

A rejection in a payment run is nearly always one of three: a wrong account number, a closed account, or an identifying detail that does not match. The first response is not to retry immediately - a retry with the same data will fail again.

The simple procedure: mark the invoice unpaid again, contact the supplier for verified details, and pay in the next run. The exception is a supplier awaiting a critical payment, in which case the transfer is made manually - but it is still recorded in the same place, or it will be paid again next week. Full background on the rejection codes is in errors in a supplier payment file.

What the run produces besides payment

The list built at step 4 is an asset in itself, and nearly every business throws it away. It answers three questions that have no other answer: how much the business owes right now, to whom, and when it is due to leave.

Keep the weekly list - even as a plain file - and within two months a trend emerges: whether supplier debt is growing, which suppliers hold most of it, and whether there are invoices recurring week after week without ever being paid. The third item is the interesting one, because an invoice pushed back repeatedly nearly always conceals an unresolved dispute rather than a cash flow problem.

At a business that also collects, it is worth putting both lists side by side on the same day: what is due in this week and what is due out. That is the picture most owners try to assemble in their heads, and it already exists - it is simply not kept.

How long this should take

A weekly run at a small to mid-sized business is between twenty minutes and an hour, and the variance comes almost entirely from data quality rather than supplier count. A business whose bank details and certificates are stored and current finishes fast; one that hunts for details mid-run extends it again every week.

So the investment that pays is not in speeding up payment day but in an orderly supplier onboarding process that ensures everything required exists before the first invoice arrives.

Sources

• Israel Tax Authority - withholding and bookkeeping certificates
• Masav - payment services
• Checking a withholding tax certificate before paying a supplier
• Errors in a supplier payment file
• Book a call