Bulk and batch payments: paying many suppliers at once

What are batch payments and how do they work?

A batch payment is a collection of individual payment instructions grouped into a single file and submitted to a payment scheme or bank in one operation. The file contains the sort code, account number, payment reference, and amount for each recipient. Once it passes validation, each line is processed as a separate credit to the named account, but the submission, approval, and funding step happen once, not dozens of times.

In the UK, the dominant rail for batch payments is Bacs Direct Credit, operated by Pay.UK. A business or its payroll bureau builds a file in Bacs Standard 18 format (STD18), a fixed-width record structure, which a bank or approved bureau submits to Bacs before the input window closes at 10:30pm on a working day. The scheme processes the instructions overnight and credits recipient accounts on day three, giving both payer and payee a window to spot errors before funds move.

Modern Nasara Pay platforms extend this model by letting you upload a CSV or spreadsheet, validate it against stored payee records, and convert it automatically to the correct scheme format. That removes the need for dedicated bureau software and puts submission into the same dashboard your team uses for everything else.

Batch payments are not limited to Bacs. Some businesses batch Faster Payments submissions through an API, sending many near-instant credits in rapid succession. This suits cases where speed matters more than cost, such as releasing contractor payouts after a project milestone. The two approaches sit at opposite ends of a cost-speed trade-off this guide explores in detail.

Bacs Direct Credit vs Faster Payments: choosing the right rail

The choice between Bacs Direct Credit and Faster Payments comes down to four variables: timing, cost, reversibility, and transaction limits. Getting that right at the design stage can save a meaningful amount of money each year.

Bacs is the low-cost workhorse. Per-transaction fees through a bureau or modern payment platform are typically a small fixed amount, making it highly economical for large batches. The trade-off is the three working-day settlement cycle: you submit on day one, the scheme processes overnight, and funds arrive on day three. Weekends and bank holidays extend the window, so a Thursday submission will not settle until the following Tuesday if the Monday is a bank holiday.

Faster Payments settles in seconds, around the clock, every day of the year, making it the right choice for time-sensitive payouts: a final payment to a supplier who has flagged a cash-flow concern, or one that could not be planned three days ahead. The cost per transaction is typically higher, and the critical difference is reversibility. Once a Faster Payment has been sent it cannot be recalled unilaterally; if the account details are wrong, recovering the funds depends on the receiving bank and the recipient's co-operation. The single-transaction limit was raised to £1 million in February 2022, so most supplier payments fit within it.

CHAPS, the same-day high-value rail, is generally reserved for large single transactions such as property completions and is rarely used for bulk runs because of its per-payment cost. For most planned supplier cycles, Bacs remains the most cost-effective and operationally straightforward option.

A practical rule of thumb: use Bacs for scheduled runs you can plan three days ahead, and Faster Payments for exceptions and urgencies. Build that into your payment policy so the choice is made at policy level, not each time a payment is queued.

Setting up a batch payment run: step by step

The first step is building and maintaining a verified payee register: a list of every supplier with their confirmed sort code, account number, and payment reference. Payee details should be collected directly from the supplier, never copied from an email without verification, and stored in a system that restricts editing rights. A compromised or mis-keyed payee record is the most common source of misdirected payments.

Once your payee register is in place, the run starts by pulling approved invoices from your purchase ledger. Each invoice maps to a payee record, a due date, and an amount, and your finance platform or ERP consolidates those into a draft file. Before submission, a second team member or a rule engine reviews the file for duplicate payments, amounts that exceed supplier credit limits, and any entry that deviates from the expected pattern for that supplier.

Submission to Bacs must reach the scheme within the input window, which closes at 10:30pm on the input day. Most businesses submit during business hours to leave time to correct any rejection, which happens at scheme level if a file fails format validation. Individual lines in an accepted file can be returned by the recipient bank if the account does not exist or is closed; these returns arrive on day two, giving you a day to investigate before the rest of the batch settles.

After the batch settles, your bank statement shows a single debit for the total value funded, while your platform generates a line-by-line remittance report. Reconciling the debit against the sum of individual lines closes the cycle. Platforms like Nasara Pay automate this, matching each payment to its originating invoice and marking it settled in your purchase ledger.

Fraud controls and payment authorisation for batch runs

Batch payments carry a fraud risk individual transfers do not: a single compromised file can redirect many payments at once. The two most common attack vectors are authorised push payment (APP) fraud, where an attacker impersonates a supplier and requests a bank detail change before a run, and internal fraud, where a finance-team member adds a fictitious payee or inflates an amount in the file.

The standard control is dual authorisation: the person who builds the payment file must differ from the person who approves and submits it. This segregation of duties means a single compromised credential or dishonest employee cannot complete a fraudulent payment alone, and most UK finance platforms enforce it at the workflow level.

Confirmation of Payee (CoP), introduced by the Payment Systems Regulator in 2020 and extended to hundreds more firms in subsequent phases, adds a further layer. When you set up a new payee or change bank details, CoP checks that the account name matches the sort code and number before the payment is authorised. A mismatch or no-match result is a clear signal that the details may have been changed fraudulently.

The Payment Systems Regulator's mandatory APP fraud reimbursement rules, which went live on 7 October 2024, mean payment service providers must reimburse victims of APP fraud over Faster Payments in many circumstances, up to a maximum of £85,000 per claim. Businesses still have a duty of care to apply reasonable precautions: verifying bank detail change requests by calling the supplier on a known number, and keeping an immutable audit log of every change to the payee register, are the minimum expected standards.

The cost of manual accounts payable and the case for automation

The cost argument for automating batch payments is straightforward. Manual invoice handling consumes finance-team time on re-keying data, chasing approvals, and correcting errors, all of which scale with your supplier base. Automation removes most of that work, so capacity no longer grows line by line with your invoice volume.

The hidden costs are significant. Research published by the UK government estimates that late payments cost the UK economy almost £11 billion a year, equivalent to around 0.4 percent of GDP, and that roughly 14,000 businesses close each year as a result. Delayed supplier payments are often caused not by cash-flow problems but by slow, manual approval workflows. An invoice that sits in an inbox for ten days waiting for a signature has effectively extended your payment terms by ten days without the supplier's agreement.

Automation is measurably shifting the workload. Industry research from the Institute of Financial Operations and Leadership found that in 2024, 52 percent of AP professionals reported spending more than ten hours a week processing invoices, down from 62 percent the year before, while manual keying of invoices into accounting software fell to 60 percent from 85 percent.

The government has also moved to address the structural late-payment problem. In its March 2026 response to the late payments consultation, it confirmed plans to introduce a statutory maximum payment term of 60 days between businesses, to require that all commercial contracts carry a right to statutory interest at 8 percent above the Bank of England base rate (removing the ability to negotiate that away), and to give the Small Business Commissioner new powers to investigate, adjudicate, and fine persistent late payers. That 8 percent rate already applies today under the Late Payment of Commercial Debts (Interest) Act 1998. For large buyers, a batch payment process that settles invoices on time and to the correct account will become a compliance requirement, not just good practice.

Payroll as a batch payment: HMRC obligations and Bacs timing

Payroll is the most common and most time-sensitive batch payment most businesses run. Under Real Time Information (RTI) rules, HMRC requires employers to submit a Full Payment Submission (FPS) on or before each payday, reporting the gross pay, tax, and National Insurance for every employee. The FPS is the data submission; paying PAYE and National Insurance is a separate step, and the deadline for electronic payments is the 22nd of the month following the tax month.

Because Bacs takes three working days to settle, an employer paying HMRC by Bacs must submit early enough for the payment to clear by the 22nd, or risk a late payment penalty. A bureau or integrated platform often schedules this automatically, but businesses running payroll in-house need to build the three-day lag into their calendar, particularly when the deadline falls close to a weekend or bank holiday.

Employee payroll follows the same three-day logic. If payday is the last working day of the month, the Bacs file must be submitted three working days earlier. Most payroll software generates the file automatically and flags the deadline. Platforms that connect payroll to Nasara Pay can submit it without manual export and re-import, cutting the risk of corruption or missed deadlines.

Some businesses use Faster Payments for payroll instead, because it is always-on and allows same-day submission, letting employees be paid on a fixed calendar date. For most, though, the cost saving of Bacs outweighs that flexibility when the payment calendar is well managed.

Choosing a payment platform for batch and bulk supplier runs

Not all UK business bank accounts offer batch payment functionality as standard. Traditional high-street bank accounts typically require either a dedicated Bacs bureau service or a corporate online banking product with a file upload facility, both of which involve additional contracts, setup fees, and sometimes minimum volumes.

Specialist payment platforms built for businesses, including Nasara Pay, integrate batch payment submission directly into the accounts payable workflow. You upload a spreadsheet or connect your ERP, the platform validates each payee against your register, applies your dual-authorisation policy, and submits the Bacs or Faster Payments file on your behalf. Remittance advices go to each supplier automatically, and the reconciliation file returns to your accounting software once settlement is confirmed.

When evaluating a platform, the key questions are: which rails does it support (Bacs, Faster Payments, CHAPS, international); what file formats can it ingest; does it enforce dual authorisation at file level; how does it handle Bacs returns; and what audit trail does it provide. Certifications such as ISO 27001 and PCI DSS compliance are baseline expectations. Integration matters too: look for native, bidirectional links with Xero, QuickBooks, Sage, or your ERP, so runs trigger from approved invoices and settlements flow back to mark them paid.

Conclusion

Batch payments are one of the highest-leverage operational improvements available to a growing UK business. Approving, submitting, and settling payments to dozens or hundreds of suppliers in a single workflow saves staff time, reduces errors, and pays suppliers on time without your finance team scaling linearly with your supplier base. With 1.83 billion Bacs Direct Credit transactions processed in 2025 alone, the infrastructure is mature, reliable, and cost-effective at almost any scale.

The practical steps are clear: build a verified payee register, choose Bacs for planned runs and Faster Payments for urgencies, enforce dual authorisation at every stage, and use a platform that connects your approval workflow directly to submission and reconciliation. Whether you run monthly supplier cycles or weekly contractor payouts, getting the batch payment process right is one of the most direct ways to protect cash flow and keep your finance team focused on the work that matters.

Frequently asked questions