The AUDDIS report is triggered by the submission of a file from the Service User to Bacs, (AUDDIS is an acronym made up from the Automated Direct Debit Instruction Service).
It is available to Service Users the day after a file of new Direct Debit Instructions has been submitted. If the instruction is valid and is able to be set up against the customer’s account then the AUDDIS report will not contain any details. If however there is a problem and a new instruction is not accepted either by Bacs or the payer’s bank and is therefore not lodged against the customer’s account then you will receive an AUDDIS report detailing this and the reasons why.
There are a number of different reasons why a Direct Debit Instruction may not be accepted and each reason has a corresponding reason code on the AUDDIS report. These are as follows:
- Instruction cancelled by payer
- Payer deceased
- Account transferred
- Account transferred to another bank/building society
- No account
- No Instruction
- DDI amount not zero
- Account closed
- Account transferred to a different branch of the bank/building society
- Invalid account type
- Bank will not accept Direct Debits on account
- Instruction has expired
- Payer Reference is not unique
- Instruction cancelled by paying bank
- Incorrect payer’s Account Details
- Transaction Code / User Status incompatible
- Transaction disallowed at payer’s branch
- Payer’s Name not present
- Service user’s name blank
The rationale behind each of these reason codes and the appropriate actions to take in response to them are all detailed on our Clear Direct Debit training courses, more details of which can be accessed on our training pages. If you still have questions, please contact us for more information.