How Bacs Direct Debit Actually Works, Step by Step

Bacs Direct Debit is the workhorse behind most recurring UK payments — utility bills, subscriptions, insurance premiums, and loan repayments. Unlike a card payment or a bank transfer, a Direct Debit is a pull: the biller reaches into the payer's account and collects. That power is why the scheme wraps every collection in strict rules, a fixed timetable, and a consumer guarantee. This post walks through the mechanics day by day.

The mandate comes first

Nothing can be collected until the payer signs a Direct Debit Instruction (DDI), also called a mandate. The mandate authorises a specific Service User — identified by a Service User Number (SUN) — to collect from the payer's account. Before the first collection, the biller lodges the mandate with the payer's bank using AUDDIS (Automated Direct Debit Instruction Service). AUDDIS sends the new instruction electronically so the paying bank can register it against the account ahead of time.

If the account details are wrong or the account cannot accept Direct Debits, the paying bank rejects the AUDDIS message and the biller learns before attempting a collection. This front-loads validation and keeps the failure rate on live collections low.

The three-day processing cycle

Bacs runs on a predictable three-banking-day cycle. Every collection touches three distinct days:

• Day 1 – Input day. The Service User (or their bureau) submits a file to Bacs, typically before the 22:30 cut-off. Files are formatted to the Standard 18 specification and usually signed and transmitted through the Bacstel-IP channel using smart-card authentication.
• Day 2 – Processing day. Bacs sorts the file and distributes records to each paying bank. The paying banks see the pending debits against their customers' accounts.
• Day 3 – Entry day. The money actually moves. The payer's account is debited and the collecting (Service User's) account is credited. Settlement between the banks occurs across their settlement accounts at the Bank of England.

Because the timetable is fixed, billers must submit at least two working days before the intended collection date, and the scheme requires giving payers advance notice (commonly ten working days, though this can be shortened by agreement) before the first collection or any change to amount or date.

The reports that flow back

Direct Debit is a two-way conversation. Alongside AUDDIS, several report messages keep the biller's records aligned with reality:

• ADDACS (Automated Direct Debit Amendment and Cancellation Service) tells the biller when a payer has cancelled a mandate, changed banks, or the account has closed. Ignoring ADDACS is a common cause of failed collections.
• ARUDD (Automated Return of Unpaid Direct Debits) reports collections that were attempted but returned unpaid — for example, due to insufficient funds or a disputed instruction.
• AUDDIS reports confirm whether new instructions were accepted or rejected.

A well-run collections operation reconciles these reports every cycle, updates the mandate store, and retries or dunning-flags failures accordingly.

The Direct Debit Guarantee

The scheme's trust rests on the Direct Debit Guarantee. If an error is made — wrong amount, wrong date, or a collection taken without a valid mandate — the payer is entitled to an immediate refund from their own bank, no questions asked. The bank then reclaims the disputed amount from the biller through the DDICA (Direct Debit Indemnity Claim Advice) process. This shifts dispute risk onto billers and is precisely why banks police mandate accuracy so tightly.

Why the design matters to builders

For anyone integrating Direct Debit, the fixed cycle has real product consequences. You cannot collect same-day; the earliest funds arrive is entry day, so cash-flow forecasting must account for the lag. Indemnity claims can arrive long after collection, so you need reserves and a clear reconciliation trail. And because the rail is pull-based on a shared timetable, batching and cut-off discipline matter far more than they do on real-time push rails.

Key takeaways

• Direct Debit is a pull-based collection governed by a mandate (DDI) lodged via AUDDIS.
• Collections follow a fixed three-day cycle: input day, processing day, entry day.
• ADDACS, ARUDD and AUDDIS reports must be reconciled every cycle to keep mandates accurate.
• The Direct Debit Guarantee gives payers immediate refunds; billers absorb the dispute risk through DDICA indemnity claims.
• Files use the fixed-width Standard 18 format submitted through Bacstel-IP before the daily cut-off.