Unpaid vs Disputed: Why Your Debit Orders Fail, and How the Money Comes Back
Unpaid and disputed debit orders are not the same problem. Here is how South African businesses can tell the difference and recover failed collections.
By the Paysoft Editorial Team
A failed debit order is not the end of a transaction. It is the start of a decision your business has to make, often without enough information to make it well.
Every recurring revenue business in South Africa runs into this. A subscription payment does not go through. A membership fee bounces. An instalment does not land. The question is never whether this will happen. It is how much of that revenue you recover afterwards, and how fast.
Unpaid is not the Same as Disputed
These two words get used interchangeably by finance teams, and that is a costly habit.
An unpaid debit order is one that never collected in the first place. The customer’s account did not have the funds, the account was closed, or the details were wrong. The money never left their bank.
A dispute is different. The debit order was successful. The money moved. Then, at a later point, the customer contested it through their bank and the funds were reversed.
The two need completely different responses. An unpaid item is a collections problem, solved by retrying, contacting the customer, or updating their details. A dispute is a compliance and evidence problem, solved by having a clean, verifiable mandate on record. Businesses that treat both the same way waste time fixing the wrong thing.
This distinction matters even more since 13 April 2026, when the dispute window for EFT Debit Orders, DebiCheck and Registered Mandate collections shortened to 60 calendar days, down from the 12 months businesses were used to. A shorter dispute window is good news for revenue certainty. It does nothing for your unpaid rate. That still depends entirely on what happens in the days after a collection fails.
What happens after a Debit Order fails
When a debit order is returned, it comes back with a reason code attached. Insufficient funds is the most common by far. Others point to a closed account, incorrect account details, or a customer instructing their bank directly to stop the debit.
Each reason code calls for a different next step. Insufficient funds is often resolvable simply by trying again closer to payday. A closed account needs a new mandate before you try anything else. Resubmitting every failed item the same way, without reading the reason code first, is one of the fastest ways to waste money on avoidable processing fees and damage your standing with the banks processing your collections.
How Credit Tracking recovers the failed Attempt
For DebiCheck and Registered Mandate collections, an unpaid item does not have to be resubmitted by hand. It can be held in Credit Tracking and re-presented automatically for up to 10 calendar days after the original action date, instead of your finance team manually retrying or chasing the customer for a basic administrative failure.
There is a limit worth knowing about on the other end of this process too. After 7 consecutive unsuccessful collection attempts against a mandate, the mandate is automatically suspended at banking infrastructure level. This is not a decision Paysoft or any collections provider makes. It is a rule built into the National Payment System itself. If a customer’s mandate has quietly gone inactive and nobody told you why, this is very often the reason, and it means you need a fresh mandate rather than another retry.
Why this is a Cash Flow Problem, not just an Operations One
Every unpaid item sitting untracked is revenue you have already earned and are not yet holding. For a business collecting from thousands of customers a month, even a small gap between your unpaid rate and your recovery rate compounds into a material hit to working capital.
Finance teams that only look at the headline collection percentage miss this. The number that actually matters is how much of what failed on day one gets recovered by day ten, without a single phone call or a finance team member chasing a spreadsheet.
Getting this Right
EFT Debit Orders, DebiCheck and Registered Mandate collections each serve a different risk profile, and Paysoft supports all three within one platform, with Credit Tracking on failed DebiCheck and Registered Mandate items so your business is not left manually resubmitting or chasing customers for basic administrative failures. Full visibility into unpaid reason codes, batch reporting and mandate status sits in one place, so your finance team can tell the difference between a customer who needs a nudge and a mandate that needs replacing.
If your current collection process cannot tell you how a failed payment gets recovered, or why a mandate has gone quiet, that is worth fixing before it costs you more than it already has.
Book a demo to see how Paysoft’s Collections platform handles unpaid items, disputes and mandate tracking in one place.