AUDDIS (Automated Direct Debit Instruction Service) is the Bacs service enabling organisations to set-up new Direct Debit Instructions (DDIs) to their payer’s Payment Service Provider (PSP) electronically.
AUDDIS Reports
Invalid Direct Debit Instructions (DDIs) are returned to Service Users via the bank returned AUDDIS service.
AUDDIS Reason Codes and their meanings:
| Code | Reason | Circumstances | Special Instructions |
| 1 | Instruction cancelled by payer | Payer has instructed paying PSP to cancel DDI | Service user must liaise with payer to agree the payment method for collection of any outstanding funds |
| 2 | Payer deceased | Payer deceased | |
| 3 | Account transferred | Account transferred to another bank / building society | First check you have not been notified of the new bank details, if not you must obtain a new DDI from the payer. Collection must be suspended until a new DD set up and advance notice is issued to the payer |
| 5 | No account | Account number is not recognised at the paying bank | Service user should check Direct Debit information and/or liaise with payer |
| 6 | No Instruction | Does not exist on paying bank’s database | Service user should check the DDI and/or liaise with payer |
| 7 | DDI amount not zero | Validation has detected field 8 not zero or blank space filled | Service user should correct the record and resubmit |
| B | Account closed | Payer has closed his account for an unknown reason | If the Direct Debit is to continue the service user must obtain a new DDI for a different/new account |
| C | Account transferred to a different branch of the bank/building society | New account details supplied to the service user by paying bank | Service user should apply change to data file and continue with Direct Debit collections. A 0C/0N pair must not be sent on receipt of this message |
| F | Invalid account type | Paying PSP does not allow Direct Debits on this type of account | Service user will need to obtain new account details from the payer. The Direct Debit cannot be applied |
| G | Bank will not accept Direct Debits on account | Paying PSP does not allow Direct Debits on this account | Service user must liaise with payer and obtain a new DDI for a different/new account |
| H | Instruction has expired | Occurs when a service user attempts to convert a DDI which is shown as expired on the paying PSP’s database | A 0N DDI will be required to re-activate this DDI if collections are to resume. Service users must ensure they have the payer’s authorisation to collect under expired Instruction |
| I | Payer Reference is not unique | Paying PSP has matched the DDI to an existing DDI with a similar reference that has more or fewer characters | Service user should allocate a different reference and lodge DDI, again using 0N |
| K | Instruction cancelled by paying PSP | Paying PSP has cancelled the DDI | Service user cannot collect via Direct Debit on this account. If Direct Debit is to continue the service user must obtain a new DDI for a new account |
| L | Incorrect payer’s account details | Either: The sort code / account number has failed the modulus check OR the sort code does not exist OR the account number is not all numeric or is all zeros OR the account type is invalid. |
Service user should undertake sort code validation and modulus checking prior to sending the DDI transactions to BACS or, if already doing this, should ensure that they are using the latest version |
| M | Transaction code / user status incompatible | Transaction codes which are not allowed whilst in this status have been sent | Service user has sent ‘0S’ DDI transactions after being given ‘LIVE’ status on the BACS master files. Service user should re-submit transactions with 0N as the transaction code |
| N | Transaction disallowed at payer’s branch | This code will be returned where paying PSP’s have expressly disallowed the set-up of DDIs at the branch in field 1 of the transaction | Service user should refer back to their payer and obtain a DDI for a different/new account |
| O | Invalid reference | The reference in field 10 of the DDI record does not comply with the AUDDIS rules | Service user should ensure that references meet the rules of the AUDDIS service |
| P | Payer’s name not present | Validation has detected field 11 is blank. A payer’s name should always be entered | Service user should correct the record and re-submit |
| Q | Service user’s name blank | Validation has detected field 9 is blank. The service user’s company or trading name should always be entered | Service user should correct the record and re-submit |
Give your organisation the stability and freedom it needs to drive higher levels of growth by seamlessly automating your payment processes.
