AUDDIS Reason Codes: The Complete List & Guide to Bacs Reason Codes

An AUDDIS reason code is a short code returned by a payer's bank when it rejects a new Direct Debit Instruction (DDI), explaining exactly why the setup failed and what must be corrected before collections can proceed.

AUDDIS (Automated Direct Debit Instruction Service) enables organisations to submit Direct Debit Instructions electronically through Bacs rather than using paper forms. When a bank identifies an issue during validation, it returns one of several AUDDIS reason codes through the Bank Rejected DDI report.

Understanding the AUDDIS meaning behind each code helps finance and operations teams resolve setup issues quickly, minimise failed collections and maintain accurate mandate records.

Most AUDDIS and Direct Debit rejection codes can be traced back to a small number of common issues during mandate setup.

Common causes include:

• Incorrect sort code or account number
• Missing payer details
• Duplicate payer reference
• Unsupported account type
• Customer or bank-initiated cancellation
• Expired or invalid mandate

These issues prevent the payer's bank from validating the AUDDIS Direct Debit instruction successfully and must be resolved before collections can begin.

Common Mistakes to Avoid

• Don't resubmit a cancelled DDI without obtaining a new mandate first. The bank is likely to reject it again.
• Don't reuse payer references. Duplicate references frequently trigger rejection code I.
• Don't continue scheduling collections after an invalid setup. Fix the root cause first to avoid failed payments and unnecessary administration.

The most common AUDDIS codes fall into three broad categories: customer cancellations and account changes, incorrect or incomplete data, and bank-imposed restrictions. These Bacs codes help identify the exact cause of a failed Direct Debit setup so organisations can take the correct corrective action and avoid future collection problems.

Codes related to cancellations or account changes

Codes related to incorrect or invalid data

For the latest and complete specification, consult the Bacs website. 

AUDDIS, ADDACS and ARUDD are the three main Bacs message types used throughout the Direct Debit lifecycle. Understanding which message you've received helps determine whether you're dealing with a setup issue, a mandate amendment or a failed collection.

AUDDIS reason codes identify setup problems before collections begin.

ADDACS, ADDACS codes and ADDACS reason codes relate to mandate amendments and cancellations after setup.

ARUDD, ARUDD codes and ARUDD reason codes relate to unpaid collections that have already been submitted for payment. 

Together, these message types make up some of the most important Bacs reason codes that finance teams need to monitor.

Ignoring an AUDDIS rejection can create operational and compliance issues that become more costly to resolve later.

• Delayed collections – You cannot collect funds without a valid DDI, creating unnecessary cash-flow delays.
• Higher risk of indemnity claims – Incorrect collections may result in refunds under the Direct Debit Guarantee. 
• Operational backlog – Unresolved setup issues create avoidable work for finance and operations teams.
• Customer friction – Repeated requests for information and failed setup attempts can damage customer trust.

Whether you're reviewing AUDDIS messages, DDIC reason codes or other DD rejection codes, prompt action helps reduce risk and improve collection success rates.

Many common Bacs reason codes can be prevented through stronger mandate capture and validation processes. The following best practices help improve setup success rates and reduce administrative effort.

1. Use paperless Direct Debit wherever possible (helps prevent codes L, 5 and P).
2. Apply modulus checking and account validation at the point of capture (helps prevent codes L and 5).
3. Ensure payer references are unique (helps prevent code I).
4. Capture all required payer details, including full legal name (helps prevent code P).
5. Confirm the account type supports Direct Debits before setup (helps prevent codes F and G).
6. Process ADDACS updates promptly and maintain an accurate DD Main DDI record (helps prevent codes 1, 3, B, C and related amendment issues)

Combining these controls helps reduce setup errors and improve overall Direct Debit performance.

Managing AUDDIS exceptions manually can be time-consuming, particularly for organisations processing large volumes of Direct Debits. Access PaySuite simplifies exception management by centralising reporting, automating workflows and helping ensure mandate data remains accurate throughout the customer lifecycle.

We provide:

• Centralised Bacs reporting: AUDDIS, ADDACS and ARUDD messages available in one place with clear explanations.
• Workflow automation: Trigger customer communications and internal actions automatically based on received codes.
• Auto-pause collections: Prevent failed collections when a mandate becomes invalid.
• Smart resubmission logic: Automatically reattempt setup or collection where appropriate.
• Data accuracy through system integration: Synchronise mandate information with CRM and finance platforms.
• End-to-end mandate lifecycle management: Manage setup, amendments, expiries and cancellations within a controlled, compliant process.

Our payments specialists help organisations reduce failed setups, improve operational efficiency and maintain healthier cash flow. To learn more, speak with the Access PaySuite team using the contact option below.