How to reduce debit order failures: 12 practical fixes

Most debit order failures come from four fixable causes: collecting before customers are paid, wrong bank details, customers not recognising the debit, and no quick follow-up when a collection fails. Align collection dates with paydays, verify accounts before the first run, use a recognisable statement name, notify customers before each debit and give them an instant way to pay when a debit bounces, and you'll recover a meaningful share of what's currently lost.

Here are twelve fixes, grouped by where in the lifecycle they apply.

At sign-up

1. Let customers choose their collection date

A fixed "everyone on the 1st" policy guarantees unpaids for customers paid on the 15th or on SASSA dates. Offer several dates and let customers pick. See debit order action dates and public holidays.

2. Verify bank details before the first collection

Account verification services (AVS) check that the account exists, is open, accepts debits and belongs to the named person. It costs a few rand per check but prevents 26 (no such account), 03 (debits not allowed) and 12 (account closed) unpaids on the very first run, which is when customers are most likely to cancel.

3. Capture a complete, clear mandate

Missing branch codes, the wrong account type or a mandate signed by someone who isn't the account holder all cause failures and disputes. Use the mandate checklist.

4. Explain the debit in plain language

At sign-up, show exactly what will happen: "R650.00 will be debited on the 25th of each month. It will appear on your statement as ACMEGYM." Customers dispute what they don't recognise.

Before each collection

5. Use a recognisable abbreviated name

Your statement name is limited (Netcash allows 10 characters), so make it obvious: "BRIGHTKIDS" beats "BKEDU PTY". If you trade under several brands, consider separate short names.

6. Send pre-debit notifications

An email or SMS three to five days before the action date ("Your debit of R650.00 will run on 25 June") gives customers time to make sure funds are available and cuts "I didn't know" disputes. It's essential after a price change.

7. Communicate price changes properly

Give written notice, in line with your contract and mandate, before collecting a higher amount. A surprise increase is one of the fastest routes to a dispute or a stopped payment (code 04).

8. Keep customer data current

Make it easy for customers to update bank details themselves (with a new mandate) through a portal, rather than waiting for a 12 or 26 to tell you they've changed banks.

When a collection fails

9. Respond within 24 hours

The chance of recovering a failed payment drops the longer you wait. Automate an email and SMS the day the unpaid is received. See unpaid debit order reason codes for how to respond to each code.

10. Include a payment link in every failure notice

Don't ask customers to "please pay by EFT to the account below." Give them a link that accepts card or instant EFT and settles the specific invoice. Conversion is much higher when paying takes one tap.

11. Retry smartly, not repeatedly

For funds-related unpaids, a single retry timed after the customer's payday recovers many payments. Repeatedly re-presenting the same debit annoys customers, adds fees and can breach your provider's rules. Never retry stopped, cancelled or disputed debits.

Long term

12. Consider DebiCheck for high-risk segments

If disputes (rather than insufficient funds) are your problem, DebiCheck mandates, confirmed with the customer's bank, can't be disputed when collections match the mandate. It adds onboarding friction, so target it where it pays off. See DebiCheck explained.

Measure what's happening

Track these monthly:

A high first-collection failure rate points to sign-up problems; a high rate on one date points to timing; a high 04 or 30 rate points to customers who don't recognise or don't want the debit.

Quick wins checklist

• Offer at least three collection dates
• Verify bank accounts before the first debit
• Check your abbreviated name is obvious to customers
• Send pre-debit reminders
• Automate unpaid notifications with a payment link
• Define a retry policy per reason code
• Review the metrics table every month

How CentraPoint helps

CentraPoint combines Netcash debit orders with the tools around them: online mandate signing at sign-up, a customer portal for updating details, automated dunning emails with payment links when a collection fails, and reports that break down unpaids by period and reason. Customers can settle arrears by card or instant EFT through a hosted checkout page. Read the debit order docs or see all features.

Frequently asked questions

What is a good unpaid rate for debit orders?

It varies widely by industry and customer base. Rather than chasing a benchmark, track your own rate monthly by reason code and collection date, and work on the causes you can fix.

Why do debit orders fail in January?

December spending and early December salary payments often leave accounts short until the January payday. Send reminders early and consider collecting later in January.

Does verifying bank accounts really help?

Yes. Verification catches wrong account numbers, closed accounts and accounts that don't accept debits before the first collection, which is exactly when a failure is most likely to lose you the customer.

Should I charge a penalty for unpaid debit orders?

You can if your agreement allows it and it was disclosed upfront. Many businesses find that fast follow-up with an easy payment link recovers more than penalties do.