UK Direct Debit for businesses: SUN, advance notice and scheme rules

How Direct Debit collection works

Direct Debit is a payment instruction that lets an organisation — the originator or service user — collect amounts from a payer's bank account under a mandate the payer has authorised. Collections run over the Bacs scheme, operated by Pay.UK, and pass through a sponsoring bank into the Bacs processing cycle before the payer's account is debited.

The distinction from a standing order matters commercially. A standing order is set up and controlled by the payer, at a fixed amount the recipient cannot change. A Direct Debit mandate lets the originator vary the amount and the date, provided proper advance notice is given. That is why Direct Debit, not standing order, is the instrument for subscription billing, membership fees and any collection whose amount moves.

Collections settle on the standard three-working-day Bacs cycle described in our BACS payments guide: submitted on day one, processed on day two, debited on day three. You can work out specific dates around weekends and bank holidays with the payment timing calculator.

What a Service User Number (SUN) is

A Service User Number is the unique reference issued to an organisation approved to originate Direct Debit collections through Bacs. It identifies the collecting organisation on the payer's bank statement, which is how payers recognise who has taken money from their account.

A SUN is not issued by Bacs or Pay.UK directly to applicants. A business applies through a sponsoring bank — itself a Bacs member — which submits the application and then carries responsibility for that service user's compliance with the scheme rules. That sponsorship relationship is the reason the application involves an assessment at all.

Sponsoring banks assess applicants against their own risk criteria. In practice that assessment looks at the applicant's financial standing and credit position, trading history, expected collection volumes and values, what is being billed for, and the existing banking relationship. The specific thresholds are set by each sponsor rather than by the scheme, so they differ between banks — there is no single published minimum turnover or trading history that applies across the industry, and any source quoting one should be treated with caution.

Own SUN or a bureau: choosing a route

Organisations that do not hold their own SUN, or do not want to go through sponsorship, can still collect by using an intermediary that already holds one. A Bacs-approved bureau submits files to Bacs on behalf of its clients. A facilities management provider holds its own SUN and lets client businesses collect under its umbrella, typically through an API or dashboard, with no sponsoring-bank approval needed by the client at all.

For payroll bureaus the statement-name question is often decisive: once volumes justify the sponsorship process, holding a direct SUN means client employers see the bureau's own name rather than a third party's. Accounting firms collecting fees from client accounts face the same trade-off at smaller scale.

Advance notice rules

Advance notice is the formal warning the originator must give before collecting, or before changing an amount or date already notified. It is a scheme rule, not a courtesy: a failure to give it creates a valid claim under the Direct Debit Guarantee even where the money was genuinely owed.

A notice must state the amount to be collected (or how a variable amount will be calculated), the date it will be taken, and enough description for the payer to recognise what it is for. It can be given by letter, email, invoice or another agreed channel, as long as it reaches the payer inside the notice window.

Where a previously notified amount or date changes, a fresh notice covering the new figure is required on the same terms. This catches out subscription businesses running annual price changes: the increase needs its own notice, on the full notice period, not merely a line in the terms and conditions.

Separately from notifying the payer, Direct Debit Instructions should be submitted to the payer's bank within 10 working days of the customer signing, even where the first collection is some way off.

The Direct Debit Guarantee

Every UK Direct Debit mandate is covered by the Direct Debit Guarantee, and an originator cannot opt out of it or narrow it. Under the Guarantee, a payer is entitled to an immediate refund from their own bank where a Direct Debit was collected in error — the wrong amount, the wrong date, or without adequate advance notice. The payer's bank processes the refund; the originator carries the reversal.

Direct Debit removes the chasing step entirely, which matters more for some customers than others — our analysis of UK payment practices data shows how widely large firms differ in how reliably they settle on time.

The practical consequence for finance teams is that a collected Direct Debit is not risk-free revenue on the day it lands. It carries a reversal exposure comparable to a card chargeback, and forecasting should treat it that way. The controls that reduce that exposure are unglamorous: notices that are accurate and on time, billing descriptors a payer will actually recognise on a statement, and reconciliation of mandate data against the billing system before each run.

AUDDIS: lodging mandates electronically

AUDDIS — the Automated Direct Debit Instruction Service — lets mandates be lodged electronically rather than by exchanging a signed paper form. The payer's authorisation, captured online or by phone through an approved channel, is transmitted through Bacs to the payer's bank, which sets the mandate up. This is what allows a subscription business to onboard a paying customer the same day rather than waiting on post.

AUDDIS, ADDACS and ARUDD: the three messages

Bacs returns information to originators through standard message types with reason codes, so billing systems can act on them automatically rather than parsing free text. Three cover the Direct Debit lifecycle:

A fourth message, ARUCS (Automated Return of Unapplied Credits), is often listed alongside these but belongs to the other direction of travel: it returns Bacs Direct Credits that could not be applied to the intended account. Teams reconciling Bacs output should treat ARUCS as a payment-out problem, not a failed collection.

Reason codes cover situations such as an instruction cancelled by the payer, an account transferred or closed, details that do not match, a payer who has died, or a bank that cannot process and needs the payer contacted. The authoritative code lists sit in the Bacs service guides for each message type; because they are revised, build your mapping against the current guide rather than a third-party summary.

Direct Debit, recurring cards and Open Banking VRP

Three mechanisms compete for recurring collection, and they fail in different ways rather than one simply being cheaper.

Direct Debit is priced per collection rather than as a percentage, which is why it dominates where amounts are large or margins thin. Its failure mode is want of funds, reported by ARUDD and retryable on a later cycle. Bank details change rarely, so mandates decay slowly.

Recurring card payments confirm authorisation immediately, which suits sign-up flows where you need to know now that payment will work. They fail more often for reasons the payer must fix — expiry, replacement, a blocked card — which creates ongoing involuntary churn that Direct Debit largely avoids.

Open Banking Variable Recurring Payments are built on explicit, revocable consent held at the payer's bank, with instant settlement. Commercial adoption beyond sweeping use cases is still developing, and pricing varies widely by provider, so treat any cost comparison as provider-specific rather than a scheme-level figure.

For euro collections the equivalent instrument is SEPA Direct Debit, which has its own mandate and notice regime — see the SEPA payments guide. Where a single high-value payment needs same-day certainty instead of a recurring pull, that is CHAPS territory.

Pre-launch checklist

Before submitting a first collection, confirm:

• Route decided: your own SUN through a sponsoring bank, or a bureau / FM provider
• Mandate capture built, with consent properly recorded on an approved channel
• Advance notice templates and timing wired into the billing workflow — 10 working days plus postal time unless a shorter period is specifically agreed
• Instructions lodged within 10 working days of the payer signing
• Billing system reads and acts on AUDDIS, ADDACS and ARUDD codes automatically
• ADDACS advices actioned within three working days
• Reconciliation and provision for Guarantee indemnity claims
• Staff briefed on Guarantee obligations and how disputes are handled

Frequently asked questions

What is a Direct Debit Service User Number (SUN)?

A Service User Number (SUN) is the unique reference issued to an organisation approved to collect Direct Debit payments through the Bacs scheme. It is obtained through a sponsoring bank, which submits the application and takes on responsibility for the organisation's compliance with the Direct Debit scheme rules. The SUN identifies the collecting organisation on the payer's bank statement.

How long is the Direct Debit advance notice period?

In the absence of any other agreement, the default advance notice period is a minimum of 10 working days plus postal time before the collection date. A shorter period is only permitted where it has been specifically agreed with the payer; an originator cannot shorten it unilaterally. The same rule applies to the first collection and to any change in the amount, date or frequency.

What happens if a business does not give proper advance notice for a Direct Debit?

The payer is entitled to an immediate refund from their own bank under the Direct Debit Guarantee. That right applies regardless of whether the underlying charge was legitimately owed, because the Guarantee protects the payer's right to notice, not only the accuracy of the amount. Repeated failures also affect the originator's standing with the sponsoring bank, which carries scheme-compliance responsibility for the SUN.

What is AUDDIS and how soon can I collect after lodging a mandate?

AUDDIS (Automated Direct Debit Instruction Service) is the Bacs facility for lodging Direct Debit Instructions electronically instead of exchanging paper mandates. A collection can be taken two working days after the instruction is lodged with the payer's bank, provided the payer has already received advance notice, though Bacs recommends allowing five working days so that any lodgement rejection can be dealt with first.

What is the difference between AUDDIS, ADDACS and ARUDD?

The three messages cover different stages of the mandate lifecycle. AUDDIS is used to lodge a new Direct Debit Instruction. ADDACS (Automated Direct Debit Amendment and Cancellation Service) tells the originator that an existing instruction has been amended or cancelled, and those advices must be actioned within three working days. ARUDD (Automated Return of Unpaid Direct Debits) reports collections the payer's bank did not pay, most often for want of funds.

Should a business get its own SUN or use a Direct Debit bureau?

Holding your own SUN means applying through a sponsoring bank and passing its credit and risk assessment, but your own organisation's name appears on the payer's statement and you control the collection process. A bureau or facilities management provider already holds a SUN and lets you collect under its umbrella, which avoids the sponsorship process and is usually quicker to start, at the cost of some control over the payer-facing relationship.

How long does a Direct Debit collection take to reach my account?

Direct Debit collections run on the standard three-working-day Bacs cycle: the file is submitted on day one, processed on day two, and the payer's account is debited on day three. Weekends and bank holidays are not working days, so a collection submitted on a Thursday would normally be taken on the following Monday.

Written by the financeb2b editorial team · Scheme rules sourced from Bacs and the Service User's Guide and Rules · Last updated 30 August 2026 · Editorial policy