Handle mandate exceptions
Most of the operational costs in Authenticated Collections come from exceptions, and many of these are mishandled because staff treat a payment failure and a mandate failure as the same problem. Each requires a different next step, so teams need to distinguish between them using the terminology found in their bank and provider files.
When a collection is authenticated, it is eligible for submission, provided the returned parameters match the agreement. The next permitted action is to submit the collection within the mandate terms. If the outcome is rejected by the payer, the collection is not eligible for submission. Staff should determine whether the customer disputes the terms or the contract and contact the customer before attempting any resubmission.
If the outcome is no response (NRSP), the collection is not eligible. Staff should verify the cellphone number held by the customer’s bank and either re-initiate the process or register a Registered Mandate within 10 calendar days. In the case of a validation failure, the collection is also ineligible. Staff must identify the field-level mismatch against the registered record, correct the data, and then resubmit or amend the mandate as appropriate.
An unpaid collection due to insufficient funds is different because the collection remains eligible, subject to the applicable terms. Staff should check the tracking window and the collection date against the salary date, then track the payment, re-present it within the permitted terms, or amend the date where allowed. Finally, if a mandate is suspended, the collection is not eligible. Staff must establish when and why the customer suspended it and resolve the underlying service issue so the customer can lift the suspension.
No customer response
An unanswered request is the most common outcome and the least informative. The usual cause is an outdated cellphone number at the bank, so the first call is to the customer. Cap automatic retries, because every attempt carries a fee.
Registered Mandate is the fallback, and its availability depends on your arrangement. Under FirstRand's terms a user may only request one after the DebiCheck mandate request produced a no-response code, and only within 10 calendar days of receiving it. Registered Mandate replaced the older Registered Mandate Service on 12 May 2025 and now clears in the evening window, so check what your sponsoring bank supports before you design the fallback path.
Rejected or mismatched
A customer rejection is a relationship event. Someone understood the request and said no, which means the terms or the sales conversation needs attention before you try again. Resubmitting an identical request to a customer who declined it wastes money and erodes trust.
A validation mismatch is a data event. The amount sits above the authenticated instalment or the date falls outside approved terms. Another mismatch is a mandate reference on the collection that differs from the registered reference. Kwik's troubleshooting guide is blunt about the remedy: fix the data or amend the DebiCheck mandate, because retrying an unchanged mismatching collection will fail every time. Where the change touches frequency or the contract reference, you need a fresh agreement and a new request.
Collection unsuccessful
Insufficient funds against a valid DebiCheck mandate is not a mandate problem, and routing it to your mandate queue clogs the queue. The tools for it are tracking and date alignment. Since DebiCheck already presents first in the early morning window after salary credits, repeated failures point at the collection date.
Reconciliation should close the loop daily so that outcome codes match back to instalments and unpaid items stay distinguishable from tracked and settled ones. Escalate to the mandate team only when the return code indicates suspension or cancellation, and also when it indicates validation failure. Weaver Fintech reported that it responded to industry changes by migrating 95% of collections onto DebiCheck. It described the result as "improving reliability and predictability of cash flows," which is the payoff for keeping these two queues apart.
Compare collection options
The three payment streams differ in where the mandate is stored and who validates it, and these two factors determine how each process works. The comparison follows the structure published by the Payments Association of South Africa.
With DebiCheck, the customer authenticates the mandate through their bank, which stores the registered terms and validates each collection against them. Collections are processed in the early-morning window with first priority, and tracking is available for up to 10 days. Disputes can be raised within 60 calendar days, with the authenticated record serving as supporting evidence. Operationally, you rely on the bank-held authenticated terms alongside your own records.
With a Registered Mandate, the customer does not authenticate the mandate directly; instead, the bank notifies them of its registration. The mandate is stored at the customer’s bank, and collections are validated against the registered parameters. Processing takes place in the evening at 19:00 SAST, and tracking is available for up to 10 days, from noon to midnight. Disputes can also be raised within 60 days. Your supporting evidence consists of the registered terms and your own records.
With a standard EFT debit order, the customer acknowledges the mandate through the service provider, which stores the mandate. The bank does not validate each collection against registered parameters, and tracking is not available. Processing takes place late in the evening, after Registered Mandate processing. Disputes can be raised within 60 days, but you must produce the mandate yourself. This means your own records are the primary operational evidence.
The important point in the dispute comparison is that the 60-day window is the same across all three streams. The difference lies in the strength of the evidence available when a dispute arises. For lenders experiencing high dispute volumes, that is a key reason to consider DebiCheck mandates.
Implementation questions
Put these to your sponsoring bank and technology provider before you sign, and get the answers in writing.
-
Connectivity model, supported transaction types, and which DebiCheck authentication channels reach your customer base
-
Certification and test coverage, including negative paths for rejection and validation failure
-
Response handling: which field confirms authentication rather than transmission, and how mandate records and amendments are exposed
-
Reconciliation files, support hours, failover arrangements, reporting, and the audit trail available to your compliance team
Doocat builds core and digital banking software for lenders and microfinance institutions, with loan servicing and integrations into national payment systems. If you're designing or reviewing how your systems carry a DebiCheck mandate end to end, book a call with our team.