What Is a Bacs Payment? How It Works, Timing and Costs

What is a Bacs payment?

A Bacs payment is an electronic transfer between UK bank or building society accounts made through the Bacs Payment System. It takes one of two forms – a Bacs Direct Credit, used to send money such as salaries or supplier payments, or a Direct Debit, used to collect authorised payments – and clears over a standard three-day processing cycle.

The question of what is Bacs payment usually comes down to who operates it and how the money actually moves. Pay.UK operates the Bacs Payment System through its subsidiary, Bacs Payment Schemes Limited, moving salaries, benefits, supplier payments and recurring collections between banks, building societies and payment institutions across the UK. In 2025 it processed 6.86 billion payments worth £6.05 trillion, according to Pay.UK’s Bacs statistics – 5.03 billion of them Direct Debits.

What does Bacs stand for?

The historical Bacs meaning is Bankers’ Automated Clearing Services, the name the scheme launched under in 1968. It has grown well beyond that original acronym since, and the convention this guide follows, matching current usage, is to treat Bacs as the name of the payment system itself rather than expand it.

What are the two types of Bacs payment?

A Bacs payment moves money in one of two directions: a Direct Credit pushes money into an account, and a Direct Debit pulls an authorised amount out of one.

What is Bacs Direct Credit?

Bacs Direct Credit sends money directly into a recipient’s account – what most people mean by “paid by bank transfer.” Employers use it for payroll, government bodies for pensions and benefits, and businesses for supplier payments and dividends.

What is Bacs Direct Debit?

Bacs Direct Debit lets an organisation collect an authorised payment from a customer’s account on a recurring or variable basis. It is the standard method for utility bills, subscriptions, loan repayments and insurance premiums, and every instruction is covered by the Direct Debit Guarantee described later in this guide.

How does a Bacs payment work?

A Bacs payment clears over three English bank working days, moving through a fixed input, processing and entry cycle rather than settling immediately.

1. Input day. The paying organisation, bank or Bacs-approved bureau submits the payment file to Bacs, typically between 07:00 and 22:30.
2. Processing day. Bacs validates the file and distributes the payment instructions to the receiving banks, which prepare to apply them.
3. Entry day. Funds move simultaneously – debited from the payer’s account and credited to the recipient’s – completing the cycle.

Payments can be submitted up to 30 days ahead, and the sending organisation can recall an instruction before the relevant cut-off, but once entry day arrives the movement of funds is final.

How long does a Bacs payment take?

Weekends and English bank holidays are not processing days. Under the normal cycle, a file submitted on Thursday is processed on Friday and reaches entry day on Monday, assuming Monday is not a bank holiday. Exactly when funds appear on entry day still depends on the receiving bank’s own processing, not a single guaranteed hour across every provider.

How do you make or receive a Bacs payment?

Receiving a Bacs payment needs nothing from the recipient beyond a UK account and its sort code and account number; knowing how to make a Bacs payment as a business means submitting a payment file through a bank or an approved bureau. Most consumers never interact with Bacs directly: a payment simply arrives because an employer, government body or supplier has already set it up.

What details are needed for a Bacs payment?

A Bacs payment needs the following details, though the exact submission flow depends on the sending bank or software provider:

• Account name – the registered name on the recipient’s account.
• Sort code – the six-digit code identifying the recipient’s bank or building society branch.
• Account number – the recipient’s individual account number.
• Payment reference – where relevant, so the recipient can identify the payment.

How businesses submit Bacs payment files

Businesses reach the Bacs scheme through one of three routes, which differ in cost, control and the technical work needed to connect:

• Directly through a bank’s own channel – online or business banking submission built into the bank’s own platform.
• Through connected payment or accounting software – payroll or accounting tools that submit files on the business’s behalf.
• Through a Bacs-approved bureau – a third party that handles submission for businesses that don’t submit directly.

What is a Service User Number (SUN)?

A Service User Number (SUN) is the six-digit identifier Bacs allocates to an organisation authorised to submit Direct Debit or Direct Credit instructions, and it is required before a business can submit Bacs payments in its own name.

Bacs vs Faster Payments vs CHAPS

Bacs, Faster Payments and CHAPS are three separate UK payment rails built for different jobs: Bacs batches payments over three days, Faster Payments moves money in seconds around the clock, and CHAPS settles same-day, high-value payments with no upper limit. None is universally “best” – the right choice depends on urgency and value.

Bacs vs Faster Payments

Bacs batches instructions and clears them over three days; Faster Payments processes each payment individually and typically completes it within seconds, part of the broader shift toward real-time payments. The Faster Payments scheme limit caps an individual payment at £1m, though the sending bank or provider can – and often does – set a lower limit of its own.

Bacs vs CHAPS

CHAPS settles on the same working day and has no scheme-level minimum or maximum payment amount. It is commonly used for high-value or time-critical transfers such as property completions. Bacs is better suited to routine, non-urgent batch payments and has a maximum individual payment value of £20 million under its scheme rules.

Which UK payment method should a business use?

It comes down to urgency and value: Bacs for routine, non-urgent batches such as payroll and supplier runs; Faster Payments for everyday transfers that need to arrive quickly; CHAPS for high-value or time-critical payments where same-day, guaranteed settlement matters more than cost.

Are Bacs payments safe and protected?

Bacs payments run over a regulated scheme with bank-level security controls, and Direct Debit collections carry an additional layer of protection through the Direct Debit Guarantee. Scheme security, a bank’s own fraud controls and the Guarantee are three separate layers, not one blanket assurance.

How the Direct Debit Guarantee works

The Direct Debit Guarantee entitles a customer to an immediate refund from their own bank if a Direct Debit is taken in error or without proper notice, and it applies automatically to every Direct Debit instruction without the customer needing to sign anything extra. It sits alongside a business’s own payment fraud prevention controls rather than replacing them.

What to do if a Bacs payment is missing

If an expected Bacs payment has not arrived, first check that entry day has passed and the account details were correct, then contact the sending organisation or your own bank – Bacs itself does not offer payment tracking to individual customers.

How much does a Bacs payment cost?

What a Bacs payment costs depends on the bank, bureau, payment volume and service plan involved rather than a single published figure – providers typically charge per transaction, per file or through a bundled account fee. A business running a high volume of payroll or supplier payments should compare pricing directly rather than rely on a generic per-payment estimate.

When does Bacs make sense for a business?

Bacs makes sense wherever payments are predictable, non-urgent and processed in batches – the reason it remains the default rail for payroll and recurring collections rather than one-off, time-sensitive transfers.

Common Bacs use cases

The most common Bacs use cases are:

• Payroll – regular salary payments run through payroll system software on a fixed schedule.
• Pensions and benefits – recurring state or workplace payments to large numbers of recipients.
• Direct Debit collections – utilities, subscriptions, loan repayments and insurance premiums.
• Supplier payment runs – scheduled B2B payments where same-day settlement isn’t required.

When another payment rail may fit better

Faster Payments fits better when a payment needs to arrive the same day without the value or urgency justifying CHAPS, and CHAPS fits better when the payment is high-value or time-critical, such as a property completion. This matters most for businesses running corporate banking products, where customers may need both batch and instant rails available. SDK.finance’s overview of payment rails covers how Bacs and Faster Payments fit into a broader payments stack alongside other account-to-account and card-based rails.

SDK.finance as the software layer for Bacs-enabled products

SDK.finance is a B2B FinTech software provider offering a modular technology foundation for launching and modernising payment and financial products. In a setup that uses Bacs, its software can provide the application and operational layer – including accounts, transaction workflows, ledgering, reconciliation and back-office tools – while a connected bank, PSP or EMI provides regulated Bacs scheme access, payment submission and settlement. SDK.finance’s guide to payment processing system architecture covers how this software layer and the regulated rail beneath it fit together.

Capabilities relevant to a Bacs-enabled product include:

• Accounts and ledgering – maintain balances and auditable transaction records for salary, benefit and supplier-payment workflows. SDK.finance can support multiple currencies across the wider product, but Bacs payments themselves are processed in sterling.
• Configurable transaction workflows – create and track payment instructions and update their statuses when integrated with a Bacs-enabled provider. The precise statuses and automation available depend on the provider interface and implementation scope.
• Configurable fees and limits – define rules by customer segment, product or payment type without changing the core platform code.
• Reconciliation workflows – match internal transaction records with reports or statements received from the connected provider. Available data and automation depend on the integration.
• Provider integrations and 650+ API endpoints – connect the platform with banking, payment, identity-verification and other external services. A Bacs-enabled product requires a suitable provider integration; the existence of SDK.finance integration options does not itself provide Bacs scheme access.
• Back-office tools and roles – help operations and finance teams monitor payments, investigate exceptions and review transaction records.

The necessary regulatory authorisation, Bacs access arrangements, payment submission and settlement responsibilities remain with the connected regulated provider. SDK.finance supplies the software and does not itself provide Bacs scheme access or regulated financial services.

The Bottom Line on Bacs Payments

A Bacs payment is not a faster alternative to a modern bank transfer. It is a batch-processed, three-day scheme built for predictable, high-volume payments such as payroll and recurring collections, with Faster Payments and CHAPS covering the cases where speed or value make a same-day or instant rail the better fit.

Explore SDK.finance’s money transfer software or payment processing software to see how a transaction platform can sit around whichever UK payment rail a product needs.