AUDDIS file management overview
AUDDIS, the Automated Direct Debit Instruction Service, allows Direct Debit Instructions (DDIs) to be electronically transferred between Originators and paying banks. An AUDDIS Originator simply sends new DDIs via BACS to the paying bank for lodgement, reducing costs and administration, and resulting in a better quality of service. AUDDIS has a significant positive impact for housing organisations on the way new Direct Debits are processed, giving greater control and efficiency over the 'paper' alternative. The time to set up a Direct Debit is also substantially reduced.
When a new Direct Debit payment method is agreed with a tenant, the electronic notification to their bank is included as part of the standard BACS service, which sorts automated payment instructions to allow for the transfer of funds, both in terms of the initial new instruction and subsequent regular payments. The required information is all contained within the BACS file, which adheres to a prescribed format and is fully supported by Civica Cx Housing. There are two methods by which an Originator may submit files to BACS:
Once a Direct Debit payment schedule has been created for a tenant, an AUDDIS DDI is required prior to any Direct Debits being collected. These instructions are managed in batches and any number of new tenant instructions can be combined into one or more batch files. On submitting the batch, the prescribed BACS output file is generated, ready for processing by the contracted Bureau or intermediary software.
As part of the process, the Originator is advised of any AUDDIS DDIs which have been rejected by BACS or returned by the paying bank; these notifications are supported by a standard set of reason codes. Once an Originator has applied the necessary advice, the affected instructions can be resubmitted using a new output file.
Separate help articles have been created for each key aspect of AUDDIS file management, including: