What is a Direct Debit re-present?
A Direct Debit represent is the process of retrying a payment that failed the first time. Often, payments fail because the customer temporarily lacks sufficient funds rather than because of a permanent issue, meaning a well-timed retry can recover the revenue without any manual intervention.
That said, represents must follow Bacs scheme rules:
- Retry within 30 days of the original failure
- The amount must be identical to the original payment
- Use Code 18 to flag the transaction as a re-present
- Maintain the original Direct Debit Instruction (DDI)
- Notify the payer in advance of the retry date
- Check the ARUDD report to understand why the payment failed, and only retry where there is a reasonable chance of success
These requirements exist to protect payers and ensure the process remains fair and auditable for everyone involved.
Why do Direct Debits fail?
Payments fail for a range of reasons. Insufficient funds is the most common cause, but failures can also stem from incorrect account details, mandate issues, bank rejections such as closed accounts or lack of authority, or technical errors in submission timing.
Understanding the specific reason matters. The ARUDD report provides this insight, and reviewing it before retrying helps you focus efforts where they are most likely to succeed, rather than retrying payments that have no realistic chance of clearing.
Introducing Configurable Represents
Many Direct Debit providers offer fixed retry schedules with little room for adjustment. Access PaySuite's Configurable Represents feature takes a different approach, giving organisations genuine control over how and when failed payments are retried.
Rather than following a standard timetable, clients can set retry delays of between 3 and 15 working days, configure up to three retry attempts, and tailor schedules to match their customers' payment cycles. Full visibility of retry history is maintained through an audit trail, and role-based access controls who can configure settings and view payment outcomes.
The result is a retry strategy that fits how your customers actually get paid, improving recovery opportunities while remaining fully compliant with Bacs rules.
How Configurable Represents works
The process is straightforward. When a payment fails due to insufficient funds, the system checks the client's configured retry settings and applies the chosen delay period. The payment is then represented to Bacs using Code 18. If that attempt is also unsuccessful, additional retries can follow based on the configuration in place. Every step is recorded in the audit trail, giving finance teams a clear, complete picture of each payment's history.
The rules at a glance
| Rule | Requirement | Why it matters |
| Timing | Retry within 30 days | Keeps the process compliant |
| Transaction code | Use Code 18 | Signals the retry to banks |
| Amount | Must match original | Avoids disputes |
| Notification | Inform the payer | Builds trust |
| Reason check | Review ARUDD | Improves success rate |
Benefits of Configurable Represents
Manually managing failed payments is time-consuming and error-prone. Automation applies consistent rules, reduces admin, and improves recovery rates, and the impact is felt across the business:
- Better cash flow through higher collection success
- Lower operational costs and reduced administrative burden
- Improved customer experience through clearer, timely communication
- Compliance assurance with auditable retry logic built in
Automating compliant re-presents lifts recovery and gives finance teams back hours each week. It means fewer manual chases and more predictable cash flow.
Best practices for successful re-presents
Automation handles the heavy lifting, but strategy still matters. Timing retries to align with customer payment cycles, rather than applying a one-size-fits-all delay, gives each attempt the best chance of success. Clear communication with customers about retry dates and amounts reduces friction and builds trust, particularly for those who may not realise a payment has failed.
Before retrying, review the ARUDD report to understand the reason for failure. Retrying a payment that failed due to a closed account or lack of authority wastes a submission and achieves nothing. Where the root cause can be addressed, such as updating account details, doing so before the retry significantly improves the outcome.
Finally, track your success rates over time. Monitoring performance across different retry delays and customer segments lets you refine your approach and make the most of the three attempts available under Bacs rules.
Take control of failed payments today
Failed payments do not have to mean lost revenue. With smart, compliant Direct Debit represents, organisations can tailor retry timing to suit their customer base and recover more of what they are owed, without adding to the workload of their finance teams.
Access PaySuite makes this straightforward with automated re-presents that keep you compliant and in control. Ready to improve your Direct Debit success rate? Book a demo with Access PaySuite and discover how Configurable Represents can help you recover more payments with less effort.
FAQs
How many times can you represent a failed Direct Debit?
Under Bacs scheme rules, you can retry a failed Direct Debit up to two additional times, giving a maximum of three attempts in total. Each retry must use Code 18, must match the original payment amount, and must take place within 30 days of the original failure date.
How long do you have to represent a failed Direct Debit?
You have 30 days from the date of the original failed payment to submit a represent. After this window closes, the payment can no longer be retried under the same Direct Debit Instruction and would need to be handled through a different collection method.
Do you need to notify the customer before representing a payment?
Yes. Bacs rules require that payers are notified in advance of a retry. Letting customers know the date and amount of the upcoming re-present reduces the risk of a second failure and helps maintain a positive relationship, particularly where the original failure was due to a temporary shortfall.
What is the ARUDD report and why does it matter for represents?
ARUDD stands for Automated Return of Unpaid Direct Debits. It is the report issued by Bacs that details why a payment was returned unpaid. Reviewing the ARUDD before retrying a payment is essential, it tells you whether the failure was due to insufficient funds (where a retry may succeed) or a more permanent issue such as a closed account or cancelled mandate (where retrying would be futile).
How does Access PaySuite's Configurable Represents feature differ from standard retry tools?
Most Direct Debit providers apply a fixed retry schedule with no flexibility. Access PaySuite's Configurable Represents feature lets organisations set their own retry delays, between 3 and 15 working days, and configure up to three attempts. This means retries can be aligned with individual customer payment cycles rather than a generic timetable, improving recovery rates while maintaining full Bacs compliance and a complete audit trail.