Bacs users can help prevent returned payments by following their simple best practices.
If you have a returned payment Bacs will let you know via an Automated Return of Unapplied Credits Service (ARUCS) or Automated Return of Unpaid Direct Debits (ARUDD) report, which will include details of the payment and a reason code explaining why it has been returned.
Returned payments are a nuisance for many organisations, disrupting cash flow and requiring time and effort to fix.To help prevent returned payments follow these simple best practices:
Regularly check and action AWACS and ADDACS reports to make sure your payment records are up-to-date. Where possible, allow customers to choose a Direct Debit collection date (e.g.: to coincide with their pay day). This can help them ensure funds are available in their account. Make sure you give your Direct Debit customers sufficient advance notice taking into account delivery time (e.g. post) – guidance can be found in The Service User's Guide and Rules to the Direct Debit Scheme. Consider using AUDDIS (Automated Direct Debit Instruction Service) to submit Direct Debit Instructions to reduce manual keying errors.View the full list of reason codes, along with explanation of how they should be dealt with.
Handling unpaid Direct Debits
In some cases you may re-present unpaid Direct Debits up to one month from the original collection date. It is recommended to liaise with your customer and give at least 5 working days’ notice of a new collection date. Bacs strongly recommend referring to the guide and rules for advice and guidance on re-presenting.
