Direct Debit Explained: How Payments and the Guarantee Work

What a Direct Debit is and how it differs from other payment methods

A Direct Debit is an instruction from a payer that authorises a specific organisation to collect variable or fixed amounts from their bank account on agreed dates. The payer sets it up once; after that, the collecting organisation pulls each payment automatically and can adjust the amount or date provided it gives the required advance notice.

That is the critical difference from a standing order. A standing order is a push payment the payer controls entirely: they set the amount, date and frequency, and only they can change any of those. If your price increases or your billing cycle shifts, a standing order does not adapt and the customer has to act, which many do not.

A recurring card payment sits somewhere between the two. Cards expire, get reissued after fraud, or get reported lost, and any of those events can silently break a billing relationship. Direct Debit is tied to a bank account rather than a card, making it far more durable for long-term collections.

The key roles and the Bacs three-day processing cycle

Four parties make every Direct Debit work. The payer is the customer who authorises the collection. The service user (also called the biller or originator) is the organisation collecting the money. Behind the service user sits a sponsoring bank that vouches for the service user in the scheme and carries responsibility for their conduct under the rules. Bacs, owned and managed by Pay.UK, operates the scheme, sets the rules and clears payments between all participating banks.

Collections move on a Bacs three working day cycle. The system accepts file submissions between 07:00 and 22:30 Monday to Friday, excluding bank holidays. Service users can submit up to 30 days in advance of the intended collection date.

Setting up a mandate: DDI, AUDDIS and ADDACS

Every collection starts with a mandate, formally called a Direct Debit Instruction (DDI). The payer authorises it, and the service user lodges it with the payer's bank before submitting any collection. Collections without a valid, live mandate are a breach of scheme rules.

Most service users lodge mandates electronically through AUDDIS, the Automated Direct Debit Instruction Service. The service user retains the signed authority and transmits the details to the payer's bank electronically. AUDDIS has been mandatory for all new organisations submitting directly to Bacs since 2008. It enables paperless mandate setup by phone or online, cuts errors because data is entered once, and any rejected instruction is reported so the service user can correct it before the first collection.

Once a mandate is live, amendments and cancellations flow back through ADDACS, the Automated Direct Debit Amendment and Cancellation Service. When a payer cancels, switches bank or their bank amends the instruction, ADDACS delivers an electronic report to the service user, who must act on it within three working days. Ignoring ADDACS reports is one of the most common causes of indemnity claims.

The Direct Debit Guarantee

Payer confidence in Direct Debit rests on the Direct Debit Guarantee, offered by every bank and building society that accepts Direct Debit instructions. It is the scheme's central consumer protection, and as a service user you are legally and contractually bound by it.

The Guarantee has three elements. First, if the amount, date or frequency of a Direct Debit is going to change, the organisation collecting must notify the payer in advance, normally at least 10 working days before the account is debited, or as otherwise agreed between the parties. The advance notice must clearly state the amount, due date, frequency and reference details. Second, if an error is made by either the collecting organisation or the bank, the payer is entitled to a full and immediate refund from their bank or building society. The refund is unconditional from the payer's perspective. Third, a payer can cancel a Direct Debit at any time simply by contacting their own bank, with no need to go via the collecting organisation.

For businesses, the practical implication is that a refund claim under the Guarantee sits with the service user, not the bank. An indemnity claim is notified via DDICA, the Direct Debit Indemnity Claims Advice service. Keeping mandates accurate, sending advance notice on time, and collecting exactly what you told the customer you would collect is how you avoid them.

Becoming a service user: direct sponsorship or via a provider

There are two routes into the scheme. Direct sponsorship means arranging a facility with a Bacs member bank, which issues you a unique six-digit Service User Number (SUN). This typically takes four to six weeks. The bank must be satisfied about your financial standing, ability to manage Bacs submissions and reporting, and capacity to absorb refund liabilities under the Guarantee. At least two staff must also complete Paperless Direct Debit training before going live.

The alternative is collecting through a bureau or commercial payments provider that already holds scheme access. The provider submits files on your behalf, handles Bacs reporting and manages the software. This is how most fintechs and scaling businesses start: it removes the need for direct sponsorship, shortens time to first collection to one to two weeks, and bundles scheme compliance. Some providers offer Facilities Management arrangements where you collect under their SUN but with your own name shown to payers.

Either route carries the same obligations. Scheme rules, the Guarantee, advance notice requirements and mandate management standards apply regardless of access method. A provider reduces the operational barrier; it does not reduce your responsibility as the collecting party.

Pros, cons and reducing failed collections

Direct Debit is hard to beat for recurring revenue. It is automated, bank-account-tied rather than card-tied, cost-effective at volume (typically 20p to 50p per transaction through a provider versus 1.5 to 3 per cent for card processing), and produces predictable cash flow. The main trade-offs are the three-day settlement lag and the advance notice and Guarantee obligations that must be met consistently.

When a collection cannot be processed, the payer's bank returns it via ARUDD with a reason code. The most common are code 0 (refer to payer, typically insufficient funds), code 1 (instruction cancelled), code B (account closed) and code 6 (no mandate on file). Code 7 (amount differs) indicates the amount did not match the advance notice, which is a compliance failure rather than a customer issue.

Failure rates can be cut with a few disciplines: give timely advance notice so payers expect the debit; act on ADDACS reports within three working days; verify sort code and account number at mandate setup; re-present failed items within 30 days using the correct transaction code; and let payers choose a collection date aligned to their payday.

Conclusion

Direct Debit remains the backbone of recurring payments in the UK because it is durable, automated and trusted. The Guarantee gives payers the confidence to authorise collections, while the Bacs cycle gives businesses a predictable, low-cost infrastructure that processes billions of transactions each year.

If you are building a recurring revenue model, the key decisions are how you access the scheme and how you embed the operational discipline the rules demand: accurate mandates, timely advance notice, and prompt action on every ADDACS and ARUDD report.

Frequently asked questions