This guide explains what each AUDDIS (Automated Direct Debit Instruction Service) reason code means, why it occurs and how to fix it. It also outlines how AUDDIS differs from ADDACS and ARUDD messages, so you know exactly what action to take.
What is an AUDDIS reason code in Bacs?
AUDDIS (Automated Direct Debit Instruction Service) allows organisations to send Direct Debit instructions (DDIs) electronically rather than using paper forms. It is mandatory for new service users submitting directly to Bacs. Invalid instructions are reported back via the AUDDIS “Bank Rejected DDI” report.
A DDI, otherwise known as a Direct Debit mandate, is the agreement between the payer and the organisation (service user) that allows the payer’s bank to withdraw funds on the service user’s behalf.
What causes most Direct Debit setup failures?
The payer’s bank rejects a DDI if anything is missing, invalid or incompatible. The bank then reports the error via an AUDDIS Bank Rejected DDI report, which your finance or operations team should monitor.
Common triggers for an AUDDIS code include:
- Incorrect sort code or account number
- Missing payer details
- Duplicate payer reference
- Unsupported account type
- Customer or bank‑initiated cancellation
- Expired or invalid mandates
Fixing these issues before attempting any collections helps avoid ARUDD returns later in the payment process.
Common AUDDIS reason codes
Codes related to cancellations or account changes
| AUDDIS code | What it means | What to do |
| 1 - Instruction cancelled by payer | Payer asked their bank to cancel the DDI. | Speak with the payer to agree on the next steps for any outstanding funds and obtain a new DDI if collections are to continue. |
| 2 - Payer deceased | Account holder is deceased. | Cease collections and follow your bereavement process. |
| 3 - Account transferred | Account moved to another bank/building society. | If you haven’t received the new details, obtain a new DDI before collecting. Pause collections until setup and advance notice are reissued. |
| B - Account closed | Payer closed the account. | Obtain a new DDI for a different account before attempting to collect. |
| C - Account transferred to a different branch | Bank supplies new account details. | Update your records and continue collecting. (Do not send a 0C/0N pair off the back of this advice.) |
Codes related to incorrect or invalid data
| AUDDIS code | What it means | What to do |
| 5 - No account | Account number not recognised. | Verify the mandate details with the payer and correct and resubmit if necessary. |
| 6 - No instruction | No DDI on the bank’s database. | Verify the mandate details with the payer; if needed, collect a new DDI. |
| 7 - DDI amount not zero | The “amount” field is not zero (DDIs should be set to “unlimited amount”). | Correct the record (set to zero) and resubmit the DDI. |
| F - Invalid account type | Account type does not allow Direct Debits. | Ask the payer for a current account that supports DDIs; collect a new DDI. |
| G - Bank does not accept Direct Debits on this account | The payer’s bank disallows DDIs on this account. | Obtain new account details from the payer and set up a new DDI. |
| H - Instruction has expired | You tried to convert/use a DDI that has expired on the bank’s database. | Submit a new (0N) DDI to re‑activate before collecting. |
| I - Payer reference not unique | Duplicate payer reference detected. | Amend to a unique reference and resubmit. |
| K - Instruction cancelled by the bank | The bank has cancelled the mandate. | Contact the payer to understand the context; collect a new DDI if required. |
| L - Incorrect payer account details | The sort code/account details are incorrect. | Validate with the payer, correct any errors in your data, and resubmit. (Modulus checking helps prevent this.) |
| M - Transaction code/user status incompatible | The submission type/user status conflicts with the mandate. | Review your submission settings/user status, and correct any errors before resubmission. |
| N - Transaction disallowed at payer’s branch | Branch restrictions prevent this transaction. | Request alternative account details from the payer. |
| O - Invalid reference | The payer reference format/length is invalid. | Correct reference formatting and resubmit. |
| P - Payer name not present | The payer name field is missing. | Add the payer’s name exactly as required and resubmit. |
| Q - Service user name blank | Missing your (service user) name field. | Complete your service user name field and resubmit. |
For the latest and complete specification, consult the Bacs website.
AUDDIS vs ADDACS vs ARUDD – what’s the difference?
Understanding the difference between these message types helps your team prioritise correctly.
AUDDIS
Used during mandate setup. Errors relate to missing or invalid DDI details.
ADDACS
Used for amendments or cancellations after the mandate is set up. These must be acted on within three working days to avoid failed collections and to stay compliant.
ARUDD
Used for unpaid Direct Debit collections, usually reported up to two working days after the collection attempt.
What happens if you ignore an AUDDIS message?
Ignoring invalid mandates can have serious consequences:
- Delayed collections - You cannot collect funds without a valid DDI, causing unnecessary cash flow gaps.
- Higher risk of indemnity claims - Incorrect collections may result in refunds under the Direct Debit Guarantee.
- Operational backlog - Unresolved errors create manual workload for finance and operations teams.
- Customer friction - Repeated requests for information or failed setup attempts undermine trust.
How to reduce AUDDIS reason codes
- Use paperless Direct Debit to remove manual data entry and reduce keystroke errors.
- Apply modulus checking and account validation at the point of capture.
- Ensure payer references are always unique.
- Capture all required payer details, including full legal name.
- Confirm the account type supports Direct Debits.
- Process ADDACS messages promptly to keep mandate records up to date .
How Access PaySuite helps
Access PaySuite simplifies exception handling by centralising reporting and automating next steps. We provide:
- Centralised Bacs reporting
AUDDIS, ADDACS and ARUDD messages are available in one place with clear explanations. - Workflow automation
Trigger automated reminders, customer outreach or internal tasks based on the code received. - Auto‑pause collections
Prevent failed payments by pausing schedules when a mandate becomes invalid. - Smart resubmission logic
Where appropriate, the system can automatically reattempt setup or collection. - Data accuracy via system integration
Sync mandate information with your CRM or finance system for consistent records. - End‑to‑end mandate lifecycle management
From setup through to amendments, expiries and cancellations, PaySuite provides a controlled, compliant process.
Want to improve DDI success rates?
If you want to reduce setup failures and streamline Direct Debit operations, Access PaySuite can help you automate exceptions, improve data quality and protect cash flow. Get in touch with a member of our knowledgeable team to find out more.
FAQs
What is an AUDDIS reason code?
It’s a short code the bank returns when a DDI setup fails. Each code explains why the mandate was rejected and what you must fix before you can collect.
Are AUDDIS reason codes the same as Bacs reason codes?
AUDDIS codes are one category of Bacs reason codes. They relate specifically to errors when setting up a Direct Debit Instruction. Other Bacs code types include ADDACS for mandate changes and ARUDD for unpaid collections.
Which AUDDIS reason codes are most common?
In practice, frequent issues include incorrect account details (L), invalid account type (F), non‑unique payer reference (I), and no account (5).
Why was my Direct Debit Instruction rejected?
DDIs are usually rejected because of incorrect data, missing details, unsupported account types, customer cancellations or expired mandates.
How fast should we act on our reports?
Process ADDACS within 3 working days (ideally same day). Process AUDDIS as soon as they arrive to avoid failed collections later.
Can I still collect a payment if a mandate was rejected?
No. You must fix the issue or obtain a new mandate before attempting to collect any future payments.
We got ARUDD code ‘0 – Refer to Payer’. Is that AUDDIS?
No. That’s an ARUDD (unpaid collection) code, commonly due to insufficient funds. You should contact the payer and consider a retry with proper notice.
Is there a definitive list of all AUDDIS reason codes?
Pay.UK/Bacs maintain the authoritative specifications. Industry references that consolidate codes are helpful day‑to‑day but always validate against the latest Pay.UK material or your sponsoring PSP.
Is there an AUDDIS reason code 4?
No. The AUDDIS code list skips from 3 to 5; there is no code 4 in the AUDDIS list. Code 4 exists only in ARUDD (unpaid collections), where it means “Advance notice disputed.” This often causes confusion, so always check which report the code came from:
• AUDDIS = mandate setup issues
• ARUDD = unpaid Direct Debit collections
What is the difference between AUDDIS and ARUDD codes?
AUDDIS codes relate to mandate setup errors. ARUDD codes relate to payments that failed after collection was attempted.
How can I reduce the number of AUDDIS rejections?
Validate bank details, ensure unique references, use paperless Direct Debit, process ADDACS updates quickly and capture all required payer information.