A direct debit mandate, properly a Direct Debit Instruction, is the authority your customer gives their own bank to let you collect from their account. It's valid when the wording and layout match the scheme's template, your sponsoring bank has approved the design in writing, and you have lodged it with your customer's bank. Your customer can't lodge it for you.
In this article
The short version
- All DDIs must follow the scheme's wording and the order of the information, and your sponsoring bank has to approve the design in writing before you issue it.
- A DDI can only be lodged with your customer's bank by you, never by your customer.
- Paperless mandates need AUDDIS compliance first, plus your own verification of your customer's identity and account details.
- Confirmation goes to your customer within three working days of a verbal or internet instruction.
- Of every mandate ever created on Adfin, 58.6% are active, 24.5% cancelled, 11.4% created but not yet lodged, and 4.5% deleted by the business before they went anywhere (Adfin platform data).
What a Direct Debit Instruction is
The mandate is an instruction from your customer to their payment service provider, authorising you to collect varying amounts from their account as long as they've had advance notice of the amounts and dates. The authority runs between your customer and their bank. You're named in it, but you don't hold it.
That structure explains most of what feels odd about mandates in practice. Your customer can cancel at their bank without telling you, and you find out when a message arrives from the bank. Your bank, the sponsoring one, carries the risk if you get collections wrong, which is why it gets a say in how your paperwork looks before you send any of it out.
The scheme's rules on wording and layout
Bacs publishes DDI templates and a logo, and the rules attached to them are short and strict. "All DDIs must follow all of the wording and the order of the information in the downloadable files", and "the design of all Direct Debits must be approved in writing by your sponsoring payment service provider before they can be issued".
So the layout of a mandate form isn't a design decision you get to make. You can put your branding around it, and the required fields, the order they appear in and the Guarantee text that goes with them stay as published. If you're using a provider, they've already done this and their form is the approved one.
Two more requirements from the same page affect what you do with a completed form. You have to make sure the DDI is correctly completed before it's despatched to your customer's bank. And you have to check your customer hasn't added any amount or date restrictions to it. People do that in good faith now and then, by writing a cap in the margin. A mandate carrying a handwritten limit isn't the instruction the scheme describes, so it needs redoing rather than filing.
Beyond those published rules, the detail lives in the Bacs rulebook and the Service User's Guide, both of which are behind a login for registered service users. Anything you read online that goes further than the template page is somebody's account of a document you can't check, so treat provider guidance as guidance and confirm anything material with your sponsor or your provider.
Why only you can lodge a mandate
One line on the Bacs template page settles a question that comes up in almost every migration and every new client onboarding: DDIs "can only be lodged with the paying payment service provider by you and not directly by the customer".
You'll still meet customers who say they've set the direct debit up at their end, usually through online banking. What they've done is something else, often a standing order, and your collection will come back unpaid because no instruction is held against their account. When you hear it, ask them to sign your mandate anyway. It saves a failed collection and an awkward conversation a fortnight later.
The same rule is why a mandate can't simply be handed between providers when you switch. Either the new provider runs a Bacs bulk change so the existing instructions move without your customers signing anything, or your customers sign a new mandate. Adfin does the first for books of 50 mandates or more and the second below that, and both keep collections running.
Paper and paperless mandates
A paper mandate is signed and returned to you, then lodged with your customer's bank. It works, and it's slow in the way anything requiring a signature on paper is slow.
Paperless is what most businesses now want, and the scheme sets conditions before you can use it. Paperless Direct Debit "enables organisations to sign up customers for Direct Debit collections for example over the telephone, Internet, telephone keypad, face-to-face or by interactive TV", and it "is therefore only available to organisations using the AUDDIS service and who can satisfy additional criteria".
| Requirement | What it means for you |
|---|---|
| AUDDIS compliance first | Service users wanting paperless "must become AUDDIS compliant first" |
| Verification is yours | "It is the organisation's responsibility to verify the customer and validate their details, for example: identity, account details, customer address" |
| Confirmation in three working days | "You must then send confirmation to the customer within three working days of their verbal or internet instruction" |
| Bank checks | Technical and financial checks, plus a new indemnity if the original was signed before 1 January 2004 |
| Ongoing review | Annual reviews of your paperless process are possible, and failure to comply can mean losing sponsorship |
AUDDIS itself is the service that "enables organisations to send new Direct Debit Instructions to their customers' payment service provider (PSP) electronically, instead of in paper format". Bacs lists four steps to get on it: complete and submit an AUDDIS application form, prepare your systems and software for the new submission and message format, complete the AUDDIS testing procedures, then go online and start using it.
If you collect through a provider, all of that has already happened and you inherit it. Signing up a client on a call or through a link is only possible because somebody in the chain is AUDDIS compliant and has satisfied the additional criteria.
The life of a mandate
A mandate moves through a small number of states: created when you raise it, pending while it's on its way, active once your customer's bank holds it, and cancelled when either side ends it. Amendments and reinstatements arrive from the bank in between.
What nobody publishes is how a real book of mandates distributes across those states, so here's ours.
| Status | Share of mandates | What it means |
|---|---|---|
| Active | 58.6% | Held at the bank and collectable |
| Cancelled | 24.5% | Ended by your customer, their bank, or you |
| Created | 11.4% | Raised but not yet lodged with the bank |
| Deleted | 4.5% | Discarded by the business before it went anywhere |
| Pending | 1.1% | In flight |
(Adfin platform data, a snapshot of every mandate ever created on Adfin, taken 18 August 2026)
The two small numbers at the bottom are the ones you'll rarely see discussed. Around one in nine mandates has been created and hasn't reached a bank yet, mostly the ordinary lag of a client who hasn't signed. And 4.5% were deleted by the business itself, meaning somebody raised a mandate and then binned it: a duplicate, a client who never onboarded, a fee arrangement that changed before it started.
Reading those two together tells you something useful about your own book. Around a sixth of the mandates in a system at any moment aren't collecting and never were, so a headline count of mandates overstates what you can actually bill. If you're forecasting from the number in your dashboard, the active figure is the one to use.
The cancelled quarter deserves less alarm than it usually gets. Mandates accumulate over years and clients leave, so a cancellation is often just the end of a relationship recorded properly. What matters more is whether you find out promptly, and the bank tells you through the ADDACS service when a mandate is amended or cancelled.
Keeping your mandates in a usable state
Most mandate problems are administrative, and a few habits keep them small.
- Chase the unsigned ones on a schedule. The 11.4% sitting in created status are the cheapest collections you'll ever recover, because the client has usually agreed already. Adfin chases unsigned mandates automatically, and a signature is worth more than a reminder about the invoice it would have paid.
- Get the mandate at the moment of agreement. Asking for bank details after the engagement letter is signed adds a step your client has to remember; asking at signature adds nothing.
- Act on ADDACS messages the week they arrive. A cancelled mandate that nobody reads becomes a failed collection next month and a conversation you could have had earlier.
- Clear your own dead records. Mandates raised in error and left in place inflate what you think you can collect.
- Keep the advance notice tied to the mandate. Your customer's authority depends on being told the amount and date, so a billing run that skips the notice puts the mandate's usefulness at risk even though the mandate is valid.
Common questions
What makes a direct debit mandate valid? The wording and the order of the information have to match the scheme's template, your sponsoring bank has to approve the design in writing before you issue it, and the completed instruction has to be lodged with your customer's bank by you. Any amount or date restriction your customer adds makes the form unusable.
Can my customer set up a direct debit themselves? No. Bacs states that DDIs can only be lodged with the paying bank by the collecting organisation and not directly by the customer. A customer who has set something up in their banking app has usually created a standing order.
What do I need for paperless direct debit? AUDDIS compliance first, plus the ability to satisfy additional criteria. You take responsibility for verifying your customer's identity, account details and address, and you send confirmation within three working days of their verbal or internet instruction.
How long does a mandate stay active? Indefinitely, until your customer cancels at their bank, the account closes, or you cancel it. Of every mandate ever created on Adfin, 58.6% are active and 24.5% have been cancelled, which reflects years of accumulated client relationships ending rather than a sudden problem.
Do I have to re-sign mandates when I change provider? Not always. A Bacs bulk change moves existing instructions without your customers signing anything, and Adfin uses that route for books of 50 mandates or more. Below that, customers sign a new mandate and there's no Bacs waiting period.
Why do some mandates never become active? Usually because nobody signed. Across Adfin, 11.4% of mandates are created and not yet lodged, and a further 4.5% were deleted by the business itself before lodgement, often duplicates or clients who never onboarded.
Sources
- Bacs — AUDDIS (accurate as of August 2026)
- Bacs — Direct Debit (accurate as of August 2026)
- Bacs — Direct Debit instruction templates and logo (accurate as of August 2026)
- Bacs — Paperless Direct Debit (accurate as of August 2026)
This article explains how direct debit mandates work and is not legal or financial advice. Last updated August 2026.
