A payment run is a scheduled financial process in accounts payable where approved supplier invoices are grouped, authorised, and disbursed in a single batch. Rather than paying bills one by one as they arrive, finance teams collect mature liabilities and execute settlements together through corporate banking rails.
Operating regular payment runs allows organisations to maintain predictable cash outflows, meet agreed payment terms, and protect commercial relationships. It also strengthens financial control by concentrating review, approval, and reconciliation into structured routines.
What is a payment run?
In business accounting, a payment run refers to the systematic compilation and clearing of outstanding vendor debts. When an organisation receives a supplier invoice, accounts payable staff verify the details and log the liability on the purchase ledger. As due dates approach, qualifying items are pulled into a payment batch, or payment proposal, for managerial sign-off and banking transmission.
Batching payments offers clear operational benefits over processing invoices individually. Settling fifty invoices in one structured run cuts administrative time, minimises banking transaction charges, and keeps the general ledger orderly. More importantly, it gives treasury and finance leaders visibility over near-term liquidity, preventing uncoordinated disbursements from draining reserves unexpectedly.
In the UK, maintaining orderly payment cycles is closely tied to statutory compliance. Under the Late Payment of Commercial Debts (Interest) Act 1998, qualifying commercial debts become overdue 30 days after invoice receipt or delivery unless agreed otherwise. Creditors hold a statutory right to claim interest at 8% above the Bank of England base rate, alongside tiered statutory compensation for debt recovery costs (GOV.UK). Scheduled payment runs ensure liabilities are cleared systematically before late penalties arise.
How a payment run works step by step
A reliable payment run follows four stages, moving from initial document matching to post-payment accounting.
Step 1: Invoice verification and batch selection
The run begins by filtering the purchase ledger for invoices that are due or eligible for early-settlement discounts. AP staff ensure that every transaction has passed internal validation, such as 3 way matching against purchase orders and delivery receipts.
The system compiles these approved records into a provisional batch proposal. Finance teams review the list to identify any disputed lines, confirm applied credit notes, and ensure the total cash requirement aligns with available liquidity before advancing the run.
Step 2: Dual authorisation and approval rules
Sound internal governance requires strict segregation of duties across the disbursement lifecycle. The clerk who compiles the batch proposal should never hold sole authority to release the funds.
Organisations establish approval rules based on transaction value thresholds and cost centre hierarchies. For substantial runs, two senior signatories, such as the Financial Controller and Finance Director, must independently inspect the payment summary and confirm that all vendor bank details and settlement sums are legitimate.
Step 3: Payment execution and file generation
Once authorised, the accounting system exports an electronic payment instruction file formatted for bank transmission. Legacy UK environments often use the Bacs Standard 18 format, which enforces an 18-character reference limit and routes funds using standard domestic bank account details.
Modern enterprise systems increasingly generate ISO 20022 pain.001 XML files. This standardised schema can bundle transactions across different payment rails into a single submission. Within pain.001, the Batch Booking flag (BtchBookg) dictates how entries appear on your bank statement: setting it to true yields a single consolidated debit for the entire batch, whereas setting it to false produces individual line items for each payee.
Step 4: Bank reconciliation and remittance advice
After the banking platform processes the file, the final stage is bank reconciliation. Finance teams match the bank debit against the cleared entries on the purchase ledger, closing the outstanding liabilities.
Simultaneously, the business generates and distributes remittance advice to every supplier included in the batch. Providing an itemised statement of paid invoice numbers and settlement amounts allows vendors to allocate the receipts correctly, avoiding administrative queries and unnecessary chasing.
Common UK payment methods for payment runs
Finance teams in the UK select payment rails based on settlement speed, transaction costs, and urgency.
- Bacs Direct Credit: The standard rail for scheduled bulk payments. Bacs payment workflows operate on a three-working-day cycle: file submission on Day 1, network processing on Day 2, and simultaneous debiting and crediting on Day 3. Because non-working days do not count, a file submitted on a Friday settles the following Tuesday.
- Faster Payments: The UK instant clearing rail provides near-real-time settlement, operating 24 hours a day. While traditionally used for ad hoc transfers, many modern accounting platforms now execute automated payment runs over the Faster Payment System to achieve same-day supplier settlement.
Payment run vs pay run
Finance teams handle distinct disbursement workflows across accounts payable and payroll:
- Payment run: A scheduled, batch-driven accounts payable process that clears outstanding trade supplier invoices. It consolidates multiple vendor liabilities into a single operational workflow using rails like Bacs Direct Credit or batch Faster Payments.
- Pay run: A dedicated payroll disbursement process focused on compensating employees. Unlike trade payment runs, a pay run involves calculating gross salaries, statutory PAYE taxes, pension contributions, and National Insurance deductions. Employers submit a Full Payment Submission (FPS) to HMRC on or before payday. According to Pay.UK (2025), between 80% and 90% of the UK workforce receives wages via Bacs Direct Credit pay runs.
Best practices for error and fraud prevention
Batch disbursements aggregate substantial capital, making them prime targets for internal mistakes and criminal manipulation. In the UK, losses to invoice and mandate scams amounted to £41.3 million in 2025 across 2,305 cases (UK Finance, 2026). Establishing robust operational controls protects company liquidity and maintains an effective audit trail.
- Implement out-of-band supplier verification: When a supplier requests a change to their bank details, never rely on email correspondence or altered PDF invoices alone. Always verify modifications through an established telephone number with a known vendor contact before updating the master record.
- Deploy Confirmation of Payee checks: Standard Bacs batch uploads to banking portals bypass real-time confirmation of payee checks during file processing. Finance teams should run bulk name-checking tools prior to file submission to confirm the beneficiary name matches the registered account holder.
- Enforce segregation of duties: Prevent single points of failure by ensuring that team members who create or modify supplier master records cannot approve invoices or release banking files.
- Automate duplicate detection: Use accounting software that scans for identical invoice reference numbers, matching amounts, or duplicate supplier details across open proposals to catch accidental double payments before execution.