If you run a business or manage payroll in the UK, you’ve likely heard the term Bacs payment. As one of the most widely used systems for transferring money between bank accounts, Bacs has played a vital role in UK banking for decades. But what does paying by Bacs sctually involve, and how does it compare to other payment options?
This guide will help you understand how to pay by Bacs, what the process entails, and whether it’s the right method for your payment needs.
Bacs stands for Bankers’ Automated Clearing Services. It’s a UK-specific payment system that allows organisations to move money electronically between bank accounts. There are two main types of Bacs payments: Direct Debit, where money is collected from a payer with their permission, and Direct Credit, which is used to send money—most commonly for things like payroll or supplier payments.
When we talk about paying by Bacs, we’re usually referring to Direct Credit, where a business or organisation sends funds directly to another bank account. Bacs has been a cornerstone of UK financial infrastructure since the 1960s, processing billions of transactions each year.
A Bacs payment follows a three-working-day cycle. On day one, a payment file is submitted to the Bacs system. This file includes details of who is being paid, how much, and when. On day two, the payment is processed by the banking system. Finally, on day three, the money arrives in the recipient’s bank account.
This structure makes Bacs predictable and reliable. However, it also means that payments are not immediate. Bacs is best suited for payments that can be scheduled in advance, such as monthly payroll or regular supplier invoices.
Payments submitted via Bacs only move on business days. If a file is submitted on a Friday, for example, the funds would usually arrive on the following Tuesday. This is one reason why businesses using Bacs need to plan their payment schedule carefully.
Bacs is a popular choice across various sectors. Large and small businesses use it to process payroll, while government departments rely on Bacs for benefits and tax refunds. Charities may also use Bacs to distribute grant funding.
The common factor is scale. If a business makes dozens, hundreds, or even thousands of payments each month, Bacs offers a low-cost, automated solution. The ability to send high volumes of payments in a single batch is one of Bacs’ core advantages.
One of the main reasons companies choose to pay by Bacs is cost-efficiency. Unlike same-day systems such as CHAPS, Bacs transactions are inexpensive and can be handled in bulk. That makes it ideal for recurring payments that don’t require immediate settlement.
Security is another strength of the Bacs system. Payments made through Bacs are regulated by Pay.UK, the operator of the UK’s payment infrastructure. Transactions are encrypted and subject to strict compliance standards, helping protect against fraud or misuse.
In addition, Bacs integrates easily with most accounting and payroll systems. Popular platforms like Xero, QuickBooks, and Sage allow businesses to generate Bacs-compatible payment files, streamlining the process even further.
To start paying by Bacs directly through your business, you’ll need to apply for a Service User Number (SUN) from your bank. This identifies your business within the Bacs network and enables you to submit payment files directly. The application process is relatively straightforward but typically reserved for businesses with a high volume of transactions.
Once you’ve been approved for a SUN, you’ll also need Bacs-approved software to create and send payment files. These tools generate the .BACs files needed to process payments and often include checks to ensure data is correct before submission.
Alternatively, if your business does not have the volume or infrastructure to manage Bacs in-house, you can use a Bacs-approved bureau. These third-party providers submit payments on your behalf and are often the simplest way for small businesses to access the Bacs system without dealing with complex setup.
While Bacs is ideal for scheduled, non-urgent payments, it’s not the only method available in the UK. Other common systems include Faster Payments and CHAPS.
Faster Payments typically arrive within seconds and are used for more immediate, one-off transactions. There is usually a cap on the amount that can be sent, though this varies by bank. Meanwhile, CHAPS is designed for high-value, same-day transfers, often used in property transactions or urgent supplier payments. However, CHAPS comes with significantly higher fees.
The key difference is speed versus cost. Bacs is slower but cheaper and more scalable, while Faster Payments and CHAPS offer speed at a premium. Choosing the right system depends on your business’s payment needs and the urgency of each transaction.
Paying by Bacs remains a dependable, low-cost way for businesses to manage regular outgoing payments in the UK. While it lacks the speed of newer systems, its reliability, integration options, and low fees make it ideal for payroll, supplier payments, and recurring transactions.
If your business can plan payments in advance and prioritises cost efficiency, Bacs payments are well worth considering. For many UK organisations, Bacs continues to be the backbone of their financial operations.
Whether you’re just exploring or ready to switch, we’d love to hear from you. Fill in our Let’s Talk form to contact us for a quote, advice or a demo.
If you’d like to discuss your business requirements and how paygate can help, get in touch.
"*" indicates required fields
A Bacs payment is a UK bank transfer method used to move money electronically between accounts through the Bacs network. It is commonly used for payroll, supplier payments and benefits, allowing organisations to send large volumes of payments securely and efficiently.
Businesses pay with Bacs by creating a payment file using Bacs-approved software or a bureau service and submitting it through the Bacs network. The file contains payment instructions that are processed and transferred to recipient bank accounts.
Bacs works by allowing organisations to submit electronic payment instructions to the banking network. These instructions are processed over a structured cycle, enabling banks to transfer funds between accounts in a reliable and controlled way.
A Bacs payment normally takes three working days to complete. The first day is submission, the second day is processing by the banking system, and the third day is when the funds reach the recipient’s account.
Bacs is typically used for scheduled for bulk payments, Faster Payments transfers funds almost instantly for smaller transactions, while CHAPS is designed for same-day high-value payments and is often used in property or large financial transfers.
Yes, Bacs payments operate within the UK banking infrastructure and use secure submission protocols, encryption and authentication controls. These measures help protect payment data and reduce the risk of fraud or unauthorised transactions. Read about 7 key steps to improve your Bacs security.
To send a Bacs payment, organisations usually need the recipient’s name, account number, sort code and payment reference. These details are included in a payment file submitted through approved payment software.
Paying by Bacs requires access to Bacs-approved software or a Bacs bureau provider. Once payment details are entered, the system generates a payment file that is securely transmitted to the Bacs network for processing.
✓
| paygate on prem | paygate v2 | paygate v3 | |
|---|---|---|---|
Security policy manager * Includes: password complexity manager, inactive timeout, time restrictions, IP address restrictions | ✓ | ✓ | ✓ |
AWS ISO27001 hosted * Primary fail over and back up UK data centres | ✓ | ✓ | |
SFTP file uploads/downloads *Secure way to move files across the internet, customers can use their own certificates | ✓ | ✓ | ✓ |
| Gemalto security tokens MFA | ✓ | ✓ | ✓ |
| Email MFA | ✓ | ||
| SMS MFA | ✓ | ✓ | ✓ |
APP MFA * Works with common auth apps such as Google Authenticator, Authy. Works on Android or iOS. | ✓ | ||
| PG Platform ISO27001 | ✓ | ||
Fraud tool *Currently support Blacklists and Whitelists. In a blacklist you add various sortcodes / account numbers and the system will prevent any payment to those accounts. In a whitelist you add sortcodes and account numbers and the system will ONLY allow payments to accounts on the whitelist. We include various tools to help build and maintain the lists. | ✓ | ||
GDPR subject access request * Search tools to help perform a GDRP lookup. Then can optionally ‘sanitise’ personal data from the system. | ✓ | ✓ | ✓ |
GDPR Data cleansing *Remove historical data by bulk or individual. | ✓ | ||
Browser compatbility * We maintain support for Chrome, Edge and Firefox. | ✓ | ||
Built for performance * Version 3 runs on super modern, high-end infrastructure | ✓ | ||
Single Platform * Customers have a single user account that they can use across all services (Enterprise, Online, Validate, etc). | ✓ | ||
Agent rebuilt key management system * Very secure way to get files to and from the Paygate cloud. Supports ways to automate files being sent into the paygate cloud and retrieving reports from the cloud. Key management was rebuilt for V3 to further increase security. | ✓ | ||
HTTPS uploads/downloads * paygate v3 supports both SFTP and HTTPS. | ✓ | ||
In browser File and Folder handling * Allows customers to securely organise their files and folders that are stored on paygate | ✓ |
| PG on prem | PG Ev2 | PGv3 | |
|---|---|---|---|
| Logging tickets by email | ✓ | ✓ | ✓ |
| Logging tickets by portal | ✓ | ||
| Logging tickets by phone | ✓ | ✓ | ✓ |
| Dedicated account management | ✓ | ✓ | ✓ |
| Uptime improvements | ✓ | ||
| Ongoing development | ✓ | ||
| Bug fixing | ✓ | ||
|
Auto File Import *Automatically imports a payment file and validates it. Users no longer need to manually browse for and import a file, paygate will do this in the background and present the validation results to the user. |
✓ |
| PG on prem | PG Ev2 | PGv3 | |
|---|---|---|---|
|
Designer in browser * In V2 Workflows use an older style desktop app. In V3 workflows are built and managed in the Paygate Browser app. It’s much easier to deploy and manage. |
✓ | ||
| Designer 3rd party app | ✓ | ✓ | |
|
Improved logging * A feature mainly for PS/CS to help them diagnose problems with workflows. Problems can be diagnosed and fixed faster. |
✓ | ||
|
New scheduler triggers * A new trigger type that allows the user to set up a workflow like you set up a meeting in Outlook. For some, this is more flexible and easier to understand than using CRON. |
✓ | ||
|
Triggers for multiple workflows * You can use a single trigger to start multiple workflows. It’s a simple feature that will make things easier to manage if you have a lot of workflows. |
✓ | ||
|
Workflow validation * Troubleshoots new workflows, validation |
✓ | ||
|
Workflow chaining * Allows a workflow to call another workflow. Using this you can simplify large complicated workflows in smaller separate ones. Easier to manage and diagnose issues. |
✓ | ||
|
New nodes * Various new nodes that help to build new types of workflows or help manage existing workflows. |
✓ | ||
|
Full documentation V3 will be fully documented with help guides and tutorials.
and tutorials * |
✓ | ||
|
Multiple filename variables * Supporting multiple filename variables should make designing complex workflows a bit easier. |
✓ | ||
|
Future developments * Pure Excel Importer – XLSX; BACS Calendar Widget; Workflow Timeline; Workflow / Mobile App notification / management; S3 Connector |
✓ | ||
|
Download and distribute A Reports * When you have workflow and HSM you can automate the entire BACS report download process. They can automatically be converted to other formats for integration into finance apps. They can be emailed to customers as html, pdf or zips. They can be made available for collection via SFTP. Or, if you use Agent, they can be security delivered to the customer’s private network. |
✓ | ✓ | ✓ |
| Partial submission | ✓ | ✓ | ✓ |
|
Lightsout submission * No signing |
✓ | ✓ | ✓ |
| Standard nodes for initiation | ✓ | ✓ | ✓ |
| PG on prem | PG Ev2 | PGv3 | |
|---|---|---|---|
| Batched bureau submissions | ✓ | ✓ | ✓ |
| Manual & Automated submission builder | ✓ | ✓ | ✓ |
| Customer import | ✓ | ✓ | ✓ |
| Bacs reporting tools | ✓ | ✓ | ✓ |
| Recall Bureau Customers by ID | ✓ | ||
|
Submission Re-entry * Complete your submissions over any amount of time
|
✓ | ||
|
Familiar workflow throughout *It will be familiar to V2 customer but they will notice improvements. |
✓ | ||
| Revamped manual submission mode *This is completely new in V3 Bureau.
Those customers wanting a more manual way of building their submission (Rather than using Jobs) will find a new, efficient way of working.
|
✓ | ||
|
Drag and drop files from anywhere *Like in other areas of V3. User can just drag and drop file in Bureau for processing. They can also use the Restricted File Browser and Server file browser – that add more security – if they wish. |
✓ | ||
|
Support for multiple file formats per submission * No longer limited to single Standard 18 submission for example
|
✓ | ||
|
Better default filename support *Makes working with files easier. |
✓ | ||
|
Usage Reporting over data range *Small but useful improvement to reporting. User can set a date range on the usage report. |
✓ |
| PG on prem | PG Ev2 | PGv3 | |
|---|---|---|---|
|
Validate *Validate is integrated in V3 and so customers that have both products can access them from the same client with the same account. |
✓ | ||
|
API Access *Validate API and the Payment API.
|
✓ | ||
| 4x Faster | ✓ | ||
|
Save Submissions *Save an ‘in-progress’ submission and return to it later. Build up a submission during the day |
✓ | ||
| Improved payment and submission searching | ✓ | ||
|
Customisable dashboard *Many useful, module specific, dashboard widgets, e.g. Payments, collections, workflow, etc. |
✓ |
| PG on prem | PG Ev2 | PGv3 | |
|---|---|---|---|
| Enhanced reporting including real-time usage | ✓ |
