Batch payments: How to pay suppliers and employees at scale

A batch payment groups multiple supplier invoices or employee expense reimbursements into one file, submitted as a single instruction. It generally means fewer transfers, lower fees, and a clear picture of where your cash is going.

If your finance team processes more than a handful of payments each week, batch processing is the difference between a clean end of week and a Friday spent chasing approvals while the Bacs cut-off approaches.

A well-run batch process also reduces errors, speeds up month-end close, and gives you a single reconciliation event instead of dozens of individual ones. For anything specific to your legal or tax situation, always speak to your accountant or HMRC directly. If your batch workflow relies on manual invoice handling upstream, it's worth reviewing your accounts payable process first.

How batch payments work across UK and European payment rails

The payment rail you choose for each batch determines settlement speed, file format, and per-transaction cost. Most mid-market teams use more than one rail, depending on urgency and whether the payee is in the UK or Europe.

UK payment rules have tightened. The Authorised Push Payment (APP) fraud reimbursement rules now apply to Faster Payments and CHAPS, and the EPC rulebook update taking effect in November 2026 will require cleaner supplier data in SEPA messages. If you haven't reviewed your batch payment controls recently, now is the time.

Bacs Direct Credit

Bacs Direct Credit is the standard rail for scheduled UK batch payments. Operated by Pay.UK, it processes payments on a three-day cycle:

• Day one (Input Day): You submit your payment file via the BACSTEL-IP secure channel, either directly if you hold a Service User Number, or through an approved bureau.

• Day two (Processing Day): Bacs delivers files to recipient banks.

• Day three (Entry Day): Payments are credited to beneficiaries and debited from your account at the same time.

You can submit instructions in advance, which gives you flexibility to schedule payment runs around your cash flow. If you need to correct an error, you can submit an extraction request on day one before the processing cut-off. After that, the payment is committed. The file format is Bacs Standard 18, though ISO 20022 XML translations are available in Pay.UK guidance.

At 5p to 50p per transaction, depending on your bank and submission method, Bacs is also the cheapest option at volume. CHAPS costs run from £15 to £35 per payment. For a mid-market company running 50 to 200 supplier payments a week, that difference alone makes Bacs the practical default.

SEPA Credit Transfer

If you pay EU suppliers, SEPA Credit Transfers are usually the main rail. The SCT Rulebook requires funds to reach the beneficiary's bank within one business day of submission. Files use ISO 20022 XML format, and you need an IBAN and SWIFT BIC for each payee.

From 15 November 2026, unstructured address formats in SEPA payment messages are no longer accepted, per EPC guidance. If your supplier master data still uses free-text addresses, you need to migrate to structured fields before then.

Since the UK left the EU, euro payments to EU suppliers usually route through SEPA via your banking provider. That extra step is worth factoring into your cut-off planning. Some providers apply earlier same-day cut-offs, so check your bank's timetable before each run.

Faster Payments and CHAPS

Faster Payments settles near real-time, 24/7/365, which makes it better suited to urgent one-off payments than to routine batch runs. CHAPS settles the same day during business hours, but the per-transaction cost makes it impractical for anything except high-value transfers like property completions. You wouldn't run a weekly supplier batch through CHAPS. By volume, CHAPS is a small share of total UK payments, but by value, it dominates.

How to process a batch payment run in 5 stages

Your batch payment workflow needs to work backwards from the Bacs processing calendar, because every stage that slips pushes settlement by a full working day.

1. Aggregate and capture invoices

Collect invoices from all channels, including email, supplier portals, and post, into one inbound queue. The most common hold-up at this stage is invoices sitting in someone's personal inbox or arriving without a purchase order reference, so anything that delays capture delays the entire run. If you still receive paper invoices, scan and digitise them on receipt so they enter the same workflow as digital ones. A centralised invoice management process helps here.

2. Verify with three-way matching

Before any invoice enters your payment batch, match it against the purchase order, the goods received note, and the invoice itself. This is three-way matching, and it catches pricing discrepancies and duplicate invoices before they reach the payment file. If the documents don't match, hold the invoice for resolution and keep it out of the batch. Errors that slip into the file are far harder to unpick after submission.

3. Route approvals using the four-eyes principle

No single person should both create and authorise a payment batch. The four-eyes principle is segregation of duties applied to payment runs: one person prepares, another approves.

A tiered approval structure works well for mid-market teams.

The person who prepares the payment file should not be the same person who approves it for release.

If your team is small, move controls upstream to the purchase requisition stage. That way, approvals are already in place before invoices arrive, rather than piling up at the point of payment.

Getting this balance right matters more than most teams realise. Too many approval gates and you become the bottleneck that slows every purchase. Too few and you're exposed to maverick spend. The goal is enough oversight to maintain control without making finance the reason everything takes a week longer.

If you use a spend management platform, look for a visual approval workflow builder that supports multi-condition routing. That way, your finance team only sees payments that already have budget-owner sign-off.

4. Prepare and submit the payment file

For Bacs, you compile your approved invoices into a Standard 18 file and submit via BACSTEL-IP. Always check the annual Bacs calendar for bank holidays. If you submit on a Friday before a Monday bank holiday, settlement moves to Wednesday, not Tuesday. That catches people out more often than you'd expect. For SEPA, you generate an ISO 20022 XML file with IBAN and BIC for each payee.

Here's what a typical run looks like. Your AP specialist approves 47 supplier invoices totalling £128,400 on Tuesday morning and generates the Bacs file from your accounting software by 14:00. Your finance manager reviews and authorises it before the BACSTEL-IP cut-off, and suppliers receive their funds on Friday.

5. Reconcile and retain records

After settlement, match the bank statement debits against your payment file totals. Then verify individual payee credits against invoice values. Investigate any returned or unmatched payments straight away. Don't let them sit.

Failed Bacs Direct Credit payments are returned as Automated Return of Unapplied Credits (ARUCS) reports. Common causes include closed accounts, incorrect sort codes, and insufficient funds. If a payment fails, correct the payee data and resubmit in the next batch rather than chasing it as a one-off.

Retain batch payment records in line with HMRC requirements. For routine PAYE records, that means at least three tax years. The Payment Systems Regulator (PSR) also sets compliance obligations for APP-related payments.

Batch payment fraud controls and compliance requirements

Since October 2024, getting payment controls wrong has a direct financial cost. Under PSR directions, payment providers must reimburse APP fraud victims up to £85,000 per claim on Faster Payments and CHAPS. The cost split falls equally on sending and receiving banks. To put that in context: UK Finance data shows APP fraud losses hit £459.7 million across 232,429 cases in 2024.

Three controls matter most if you run batch payments.

Confirmation of Payee is the first line of defence. Before any payment goes through, your provider needs to verify that the receiving account name matches the name you submitted. In a batch file with dozens of payees, one substituted account number is all it takes to redirect funds to a fraudster. PSR Direction 17 makes this check mandatory for covered providers.

Sanctions screening catches regulatory risk before submission. Every payee in your batch needs to be screened against the UK Consolidated List before the file is submitted. Manual screening isn't realistic at batch volumes, so you need automated screening that holds or rejects matches. The FCA sanctions guide sets out the requirements.

Strong Customer Authentication (SCA) protects the file's integrity. The authentication code for a batch must be dynamically linked to the total amount and total number of beneficiaries in the file, per European Banking Authority (EBA) SCA standards. If someone alters the file after authentication, the batch is invalid.

These controls aren't optional extras. For mid-market finance teams running weekly batch payments, they're the baseline that keeps your payment process compliant and your suppliers' funds where they're supposed to go.

Supplier vs. employee batch payments: Tax, VAT, and timing differences

When you batch supplier and employee payments, the file mechanics may look similar, but the tax rules can get quite complicated.

VAT treatment is the first difference. For supplier invoices, you can usually reclaim input VAT in the period when you receive a valid VAT invoice, regardless of when you actually pay it. But if an invoice remains unpaid after six months, VAT rules require you to repay the VAT you claimed until payment is made. In practice, that means a disputed supplier invoice sitting in your AP queue can create a VAT liability you didn't plan for. Employee expense reimbursements are trickier. According to ACCA guidance, reimbursements are subject to VAT, while disbursements fall outside its scope.

PAYE and NICs can apply to employee reimbursements that fail the exclusively and necessarily test. The expense must be wholly, exclusively, and necessarily incurred for employment duties. Fail any of those conditions, and the payment becomes taxable income, triggering Class 1 NICs for both you and the employee. Supplier payments don't create PAYE obligations.

Timing also differs. Supplier runs tend to follow quarterly VAT deadlines and cash flow policy, with many teams processing them weekly. Employee reimbursements usually align with the monthly payroll and the annual making-good deadline of 6 July under HMRC guidance.

Moving from manual to automated batch payments

If your team still builds batch files by hand, the bottleneck isn't the payment rail. It's everything that happens before the file is submitted: chasing invoices, matching documents, routing approvals, and formatting files. That's where automation has the most impact.

The cost of staying manual is measurable. The Government's consultation response from July 2025 puts a number on it: invoice processing costs UK businesses £30 to £50 per invoice when handled manually. For medium-sized businesses with 50 to 249 employees, late payment costs alone average £193,635 per year.

When you start evaluating tools to automate batch payments, the options tend to fall into a few categories.

• Accounting software with batch features: Many finance systems handle AP workflows natively, but some teams add dedicated software for direct Bacs file generation, stronger approval routing, or higher-volume execution.

• Dedicated payment platforms: These provide direct connectivity to UK payment rails and suit teams that have outgrown the payment-count limits in standard online banking.

• Spend management platforms with payment capabilities: These connect invoice processing, approvals, bookkeeping, and payment execution in one workflow. For mid-market teams making batch payments alongside card spend and expense claims, this approach removes the friction of switching between separate tools.

A sensible place to start is with your accounts payable automation. Redesign the approval process first, then automate high-volume, low-value transactions such as purchases under £500. Keep manual oversight for anything complex or high-value.

Batch payments don't have to mean month-end stress. Codat, for example, cut their month-end close from a full day to 30 minutes after moving AP onto Spendesk. Get the controls and approval paths right, and your finance team can give the rest of the business autonomy to spend while maintaining full visibility over every payment. Friday afternoon stops being a scramble to get the file out before the Bacs cut-off, and starts being the time your team actually closes the week clean. If you want to see what that looks like, take a look at how Spendesk handles accounts payable and related approval workflows.

Frequently asked questions about batch payments

What is the difference between batch payments and bulk payments?

Batch payments group multiple payment instructions into one file processed on a scheduled cycle, such as a weekly Bacs run. Bulk payments usually emphasise high volume rather than a specific schedule. In UK practice, the terms are often used interchangeably, but batch usually points to grouped file-based processing.

How long do batch payments take in the UK?

Bacs Direct Credit takes three working days from submission to settlement. SEPA Credit Transfers settle within one business day. Faster Payments settles near real-time but is usually reserved for urgent payments rather than routine runs. CHAPS settles the same day, but costs £15 to £35 per payment.

What should you look for in batch payment software?

The right tool depends on your payment volume and how many systems your finance team currently switches between. At minimum, look for configurable approval workflows, direct connectivity to UK payment rails (Bacs and Faster Payments), and automated sanctions screening. You also want a reconciliation process that maps payments back to invoices without manual matching. Spendesk, for example, connects OCR (Optical Character Recognition) extraction, approval routing, and payment execution in a single workflow through its invoice management module, so supplier payments and employee expense claims follow the same path from capture to reconciliation.

Can you make batch payments through accounting software?

Most UK accounting systems support some level of batch processing, but teams that handle high volumes often find the built-in tools limited for approval routing and payment reconciliation. If your current system handles the file generation but not the controls around it, a spend management platform layered on top can fill the gap without replacing your accounting software.

What fraud controls are mandatory for UK batch payments?

Since October 2024, the PSR's mandatory APP fraud reimbursement rules require payment providers to reimburse victims up to £85,000 per claim on Faster Payments and CHAPS. You also need Confirmation of Payee, sanctions screening against the UK Consolidated List, and Strong Customer Authentication dynamically linked to the batch total and beneficiary count.