An ARUDD report details any unpaid Direct Debits. You can receive ARUDDS reports one to three working days after the payment collection. A Direct Debit (DDI) may be returned unpaid for a variety of reasons, these are listed below.
📌Note: If you use your own Service User Number (SUN), unpaid Direct Debits are collected directly from your bank account by your sponsoring bank.
📌Note: If a payer accidentally cancels a Direct Debit and it has been archived, it can't be reinstated. A new contract must be created.
📌Note: If you have a query regarding any of these reason codes contact our Access Digital Assistant for support. If the assistant can't resolve your query, you're connected to a support agent for further investigation.
If you receive an ARUDDS message stating "Ignored ADDACS/ARUDDS code for contact because bank details in report do not match customer bank details in the system", it means the system has already been updated and the incoming data doesn't match current records. No action is required.
To view your ARUDD report:
From the main menu, click BACS.
Under the HISTORY OF BACS ACTIONS tab, select your report criteria:
Bank ref: Input this to look at an individual contract.
Date: Input a date range here to look at a specific time period.
Report type: ARUDD.
Code: Leave blank to view all codes or input a specific BACS code if you want to view only that one.
Click SEARCH. The results show on-screen.
To view on a spreadsheet, click DOWNLOAD CSV.
ARUDD reason codes and consequences
Code | Reason | Circumstances | Consequences |
0 | Refer to Payer | Insufficient funds in customers account | Contract remains active payments continue as normal - payment is represented if this option is switched on |
1 | Instruction cancelled | Instruction cancelled by customer or their bank | Contract is cancelled - new DDI must be obtained before Direct Debit can be restarted |
2 | Payer deceased | Payer is deceased | Contract is cancelled |
3 | Account transferred | Account transferred to new bank | Contract is cancelled - new DDI must be obtained before Direct Debit can be restarted |
4 | Advance notice is disputed | Customer disputes date, amount or frequency of advance notice | Contract is cancelled - new DDI must be obtained before Direct Debit can be restarted |
5 | No account/or wrong account type | Account number is not recognised at the paying bank | Contract is cancelled - new DDI must be obtained before Direct Debit can be restarted |
6 | No instruction | No instruction held at paying bank | Contract is cancelled |
7 | Amount differs | Customer states the amount of the DDI differs from the advance notice | Contract is suspended- refer to payer to resolve dispute |
8 | Amount not yet due | Customer states date of debit differs from advance notice | Contract is suspended - refer to payer to resolve dispute |
9 | Presentation overdue | Presentation overdue | Payer states date of presentation is more than three working days after due date on fixed DDI or Advance Notice to payer. |
A | Service user differs | Identity of service user differs from DDI | Contract is cancelled |
B | Account closed | Customer has closed their account for unknown reason | Contract is cancelled - new DDI must be obtained before Direct Debit can be restarted |
How to restart a Direct Debit that has been cancelled by ARUDD
Please follow Restart a cancelled Direct Debit for instructions.
Cancel and archive contracts option
This is a feature where when cancellation BACS messages are received they're automatically cancelled and archived in Access PaySuite DDCMS. If you would like us to switch this feature on for you please contact our Access Digital Assistant for support. If the assistant can't resolve your query, you're connected to a support agent for further investigation.