What is Bacs?

Bacs (Bankers' Automated Clearing System) is the UK's longstanding automated payment scheme for bank-to-bank transfers. It operates on a three working-day settlement cycle and handles two distinct types of payments: Direct Credit (push payments like payroll and supplier invoices) and Direct Debit (pull payments like utility bills and subscriptions). Founded in 1968, it is now operated by Pay.UK, the organisation responsible for the UK's retail interbank payment infrastructure.

Today, most UK employees are paid using it. Most household bills are collected through it. And if your business has ever run payroll or transferred money to a supplier, Bacs was almost certainly the mechanism behind it. In 2024, Bacs processed 6.81 billion transactions with a combined value of £5.8 trillion.

Despite being ubiquitous, many businesses struggle with the same questions: Why do Bacs payments take three working days? What’s the difference between Direct Credit and Direct Debit? When should you use Bacs instead of faster alternatives? This guide answers those questions.

The two types of Bacs payments

Bacs handles two distinct transaction types, each serving different business purposes.

Bacs Direct Credit

Bacs Direct Credit is a push payment: money sent from one account into another. It is the primary mechanism for paying employees at scale, with the vast majority of UK payroll runs processed this way. It is also used for supplier payments, dividends, expense reimbursements, and government benefit disbursements.

Bacs Direct Debit

Bacs Direct Debit is a pull payment: money collected from a customer's account by an organisation, with prior authorisation. It is the mechanism behind most recurring payments: utility bills, subscriptions, insurance premiums, loan repayments, and membership fees. The Direct Debit Guarantee gives customers a right to an immediate refund from their bank if a payment is taken in error or without authorisation.

How Bacs works: settlement, reporting, and the five-day operational cycle

Bacs settles payments over three working days. For Direct Credit, day three is the end of the process: funds are credited and the payment is complete. For Direct Debit collections, settlement is only the midpoint. Days four and five bring the Automated Return of Unpaid Direct Debits (ARUDD) reporting cycle, which confirms which collections succeeded and which failed. Businesses running Direct Debit at scale should plan their operational workflows around five days, not three.

Day one: file submission to Bacs

The payment file is submitted (by the business or their software provider) to the Bacs system, before the daily cut-off time. Most banks set this to around 5pm.

Day two: processing by banks

The payment is processed by Bacs, and the receiving banks prepare to release funds.

Day three: settlement

The funds are credited to the recipient's account.

For Direct Credit payments, this is the end of the cycle. For Direct Debit collections, the settlement is confirmed but the reporting cycle continues.

One detail that regularly catches businesses out is that once a Bacs file has passed the daily cut-off, it cannot be cancelled. If a payment is submitted in error, the only option is to request a recall after the funds have arrived, with no guarantee of recovery on Direct Credit payments.

Day four: ARUDD reporting

Day four is when banks report Direct Debits that could not be collected. Automated Return of Unpaid Direct Debits (ARUDD) is the Bacs mechanism for this: each failed collection is returned with a reason code explaining what went wrong. Common reasons include insufficient funds, account closed, instruction cancelled, or the payer stopping the payment.

At this stage, the failure is visible but not yet fully confirmed and enriched through the Bacs reporting cycle. Businesses can see that something has gone wrong but acting on it before day five means acting on incomplete information.

Day five: confirmed outcomes and follow-up

Day five is the first point at which a business can act on a known, complete payment outcome. ARUDD reporting has been received and applied, the reason code is available, and the right next step is clear: contact the payer, update mandate details, arrange a retry where the failure reason allows it, or move to an alternative payment method where it does not.

Acting before day five, particularly on the basis of partial ARUDD data, risks taking the wrong action. Businesses need to understand that whilst the three-day settlement number is technically accurate, the five-day operational window is the one worth planning against.

How to plan payments with Bacs' three-day cycle

For businesses running payroll or managing supplier payments, Bacs' three-day settlement cycle, known as T+3 (submission date plus 3 working days), creates a forward-planning requirement. If salaries are due on the 30th, the file needs to be submitted by the 27th, and the funds need to be available from that point.

At scale this gets more complex. A payroll run, a batch of outbound supplier payments, and a pension contribution cycle can all fall in the same week, creating significant working capital planning requirements. The three-day window also creates a reporting gap: a submitted but uncleared Bacs run does not immediately reduce your available balance in most accounting systems, which can produce a mismatch between your system view and your true cash position.

This does not make Bacs unworkable. Millions of businesses manage it effectively. But it does mean that treating it as a set-and-forget mechanism carries operational risk, particularly at month-end or around bank holidays when the settlement calendar compresses. Where the T+3 window becomes a genuine operational cost, Faster Payments settles near-instantly and runs 24/7, making it worth considering for time-sensitive payments.

What do Bacs payments cost?

Bacs can be one of the most cost-efficient payment methods available to UK businesses. The cost depends on how you access the scheme.

Routine Bacs Direct Credit transfers made through an online business banking portal are typically free, or carry a very small per-transaction fee of a few pence. At higher volumes, businesses often use Bacs-approved software and submit files directly: this usually involves a software licence and a per-transaction fee, typically well under £0.25 per payment. Businesses using a payments platform or bureau service should expect to pay more, reflecting the additional processing, automation, and reconciliation capability those services provide.

Businesses that want to originate Direct Debit collections need a Service User Number (SUN), issued through a sponsoring payment service provider, such as a bank or Electronic Money Institution like Modulr. Alternatively, businesses can use a third-party bureau or payment platform that holds a SUN and enables Direct Debit collection on their behalf. Costs vary by provider, typically ranging from pence per transaction for bureau services to integrated solutions within payment platforms.

Choosing between Bacs and other UK payment schemes

Understanding when to use Bacs versus other UK payment schemes depends on factors beyond cost alone. Settlement speed, availability, transaction limits, and use case all matter.

Bacs vs Faster Payments vs CHAPS

Bacs sits alongside two other main UK payment schemes, covered in the comparison below.

How Faster Payments compares to Bacs

Faster Payments processes near-instantly (most payments clear within seconds) and runs 24 hours a day, seven days a week, including bank holidays. It handles payments up to £1m, though individual banks often set their own lower limits. It is the default method for most one-off business bank transfers. Faster Payments continues to grow year-on-year as businesses increasingly shift one-off, urgent and recurring payments to the faster rail.

How CHAPS compares to Bacs

CHAPS, the UK's high-value payment system, settles on the same day provided instructions are submitted before the bank's cut-off time, usually early afternoon. There is no upper limit on payment size. CHAPS is used for property purchases, large commercial settlements, and foreign exchange transactions. The cost (typically £25 to £35 per transaction) makes it unsuitable for anything high-volume.

For routine, high-volume, predictable payments where same-day settlement is not required, Bacs remains the right tool.

When manual Bacs management becomes the constraint

For many businesses, Bacs works well as a straightforward function. As payment volumes grow (more employees, more suppliers, more complex collections cycles) the manual overhead of managing files, monitoring cut-off times, and chasing failed Direct Debits starts to carry a real cost.

Businesses at that point often look at both sides of their Bacs operation. For Direct Debit collections, the focus is usually automation: integrating collections with accounting software, building approval workflows, and connecting failures to a recovery process. For outbound payments, such as payroll and supplier runs, some businesses find it makes more sense to move to Faster Payments altogether, gaining same-day settlement and removing the T+3 planning requirement. The trade-off is cost per transaction, but for businesses where the operational overhead of Bacs planning has become significant, it is often worth it.

Moving forward with Bacs

Bacs is not going anywhere. It remains the UK's most cost-efficient payment rail for high-volume, scheduled transactions, and understanding how to manage it well is essential for any business processing payroll or collections at scale.

The key is knowing when manual processes stop working and building the infrastructure, whether through software integrations, approval workflows, or payment platforms, that removes the operational drag as your business grows. That's when Bacs stops being an administrative overhead and starts working at scale.

Find out how Modulr automates Bacs workflows and scales with your business.

This article is for informational purposes only and should not be construed as financial, legal, or regulatory advice.

TL;DR

Bacs is a secure, reliable, and cost-efficient payment scheme that underpins payroll and collections across the UK economy. It handles two transaction types (Direct Credit, a push payment, and Direct Debit, a pull payment) and settles in three working days (T+3). Its settlement cycle and cut-off time requirements mean businesses need to plan payments in advance. Its batch-file architecture means errors cannot be reversed once submitted.

Understood and managed well, Bacs is a workhorse that can serve a business for years. The challenge arrives when volume grows and manual management becomes the bottleneck.

FAQs

What does Bacs stand for?

Bacs stands for Bankers' Automated Clearing System. It is the UK's primary scheme for automated bank-to-bank transfers, processing payroll, Direct Debits, and supplier payments. According to Pay.UK, it processed 6.81 billion transactions worth £5.8 trillion in 2024.

How long does a Bacs payment take to clear?

Bacs payments settle in three working days. A payment submitted on Monday arrives on Wednesday; one submitted on Thursday arrives the following Monday. Payments submitted after the daily cut-off (typically around 5pm) do not start the cycle until the next working day.

What is the difference between Bacs Direct Credit and Direct Debit?

Bacs Direct Credit is a push payment (money sent from a business to a recipient) used mainly for payroll and supplier payments. Direct Debit is a pull payment (money collected from a customer's account by a business with prior authorisation) used for bills, subscriptions, and recurring collections.

Can a Bacs payment be cancelled after submission?

Once a Bacs payment file has passed the daily cut-off, it cannot be cancelled. If a payment is submitted in error, you can request a recall after the funds arrive, but recovery is not guaranteed for Direct Credit payments.

Is Bacs free for businesses to use?

Bacs Direct Credit payments via a business banking portal are typically free or carry a small fee of a few pence per transaction. Businesses originating Direct Debit collections via a bureau or payment platform typically pay a per-transaction fee, usually well under £0.25