Migrate From NAEDO to DebiCheck Before Collection Rates Slip Further
If your South African business is still collecting against a post-NAEDO mandate book, banks have already moved the early window to authenticated DebiCheck. Every month on evening EFT or Registered Mandate rails costs recovered revenue your competitors are already capturing.
A structured DebiCheck migration restores collection rates and puts you on the authenticated standard.
Sound Familiar?
These are the exact issues our clients faced while still collecting on post-NAEDO rails:
- Collection rates keep slipping as legacy NAEDO-origin mandates run on evening EFT or Registered Mandate rails instead of authenticated DebiCheck
- Finance cannot tell which mandates in the book were ever bank-authenticated, so every unpaid batch is a guessing game
- Customers dispute and reverse collections that never completed DebiCheck authentication, wiping out recovered revenue weeks later
- TT1 and TT2 authentication campaigns stall because the mandate data exported from the old NAEDO file is incomplete or mismatched
- Every month of delay costs recovered revenue while authenticated competitors collect first in the early morning window
From 10 March 2025, Registered Mandate replaced RMS and moved unauthenticated collections into the evening window. Authenticated DebiCheck stays first in the early morning run. Delayed DebiCheck migration now costs even more against the same book.
What DebiCheck Migration Actually Does
Mandate audit → TT1/TT2 authentication → parallel run → cutover. Collection rates recover without a cliff-edge switch.
Audit the Book
Every active NAEDO-origin mandate classified: ready, repair, or re-contract
Authenticate Mandates
TT1 real-time and TT2 batch waves convert the book onto DebiCheck
Parallel Run
Authenticated DebiCheck collects beside the legacy path until rates hold
Cut Over
Legacy fallback stops. Early-window authenticated collections become the default
Everything You Need for a Safe DebiCheck Migration
Mandate Book Audit
We inventory every active NAEDO-origin mandate: bank details, amounts, frequencies, tracking flags, and authentication status, so you know exactly what must convert.
TT1 and TT2 Authentication Waves
Real-time TT1 for high-value or engaged customers, overnight TT2 batches for the long tail. Expired requests are flagged and re-queued before they go cold.
Parallel Run Before Cutover
Authenticated DebiCheck collections run alongside the legacy path until success rates prove out. Cutover happens when the numbers, not a calendar date, say it is safe.
Collection-Rate Rescue
Failed and disputed post-NAEDO collections are routed into recovery: re-authentication, amount amendments, or early-window DebiCheck presentment.
CRM and Billing Sync
Mandate status (pending, authenticated, expired, suspended) flows back into your CRM and billing system so collections, finance, and customer service share one picture.
Migration Dashboards
Week-by-week views of authentication rate, early-window success, dispute volume, and Rand recovered so the CFO can see the DebiCheck migration pay for itself.
Platforms We Migrate DebiCheck Mandates Across
From 61% Success to 79% After DebiCheck Migration
How a Gauteng microlender converted a 4,200-mandate post-NAEDO book onto authenticated DebiCheck and recovered R1.14 million in year one.
The Post-NAEDO Book
- 4,200 live mandates still presenting on evening EFT and Registered Mandate after the NAEDO sunset
- No reliable view of which customers had ever bank-authenticated a DebiCheck mandate
- Collection success stuck around 61%, roughly 16 points below authenticated DebiCheck benchmarks
- Disputes and reversals ate recovered instalments weeks after presentment
- Collections team spent Fridays reworking unpaid batches by hand
The Migrated DebiCheck Book
- Mandate audit cleaned bank details, amounts, and frequencies before any authentication wave
- TT1 for high-value accounts, TT2 overnight batches for the long tail, with retries on expired requests
- Authentication reached 88% of the migratable book within six weeks
- Two-week parallel run proved early-window success before cutover
- Dispute volume dropped sharply once collections matched bank-held mandates
Before vs After DebiCheck Migration
How DebiCheck Migration Works
From mandate audit to live authenticated collections in 6 to 10 weeks.
Audit the Mandate Book
Export and classify every active NAEDO-origin mandate: ready for DebiCheck, needs data repair, or must be re-contracted.
Free Scoping Call
30-minute call to size the book, pick TT1 vs TT2 waves, and design the parallel-run and cutover plan with your collections lead.
Authenticate & Parallel Run
We run authentication campaigns, fix mismatches, and present authenticated DebiCheck collections beside the legacy path until rates hold.
Cut Over & Monitor
Legacy NAEDO fallback stops. Authenticated early-window collections become the default, with monitoring on auth rate and success.
Frequently Asked Questions About DebiCheck Migration
NAEDO officially ended in 2021. Why does migration still matter?
PASA and the SARB sunset AEDO and NAEDO processing on 31 October 2021. Mandates that were never converted to authenticated DebiCheck fell onto EFT debit or Registered Mandate rails. Those rails process later in the day, stay fully disputable, and underperform authenticated DebiCheck by roughly 16 percentage points on collection success. If your book still behaves like a post-NAEDO fallback, you are leaving recovered revenue on the table every month.
How does DebiCheck migration differ from a greenfield DebiCheck setup?
Greenfield setup configures templates and authentication for new contracts. NAEDO to DebiCheck migration starts with an existing book: data audit, mandate repair, TT1 and TT2 authentication waves against customers who already pay you, a parallel run so cash flow does not drop during cutover, and only then a full switch. The risk is converting thousands of live mandates without losing collections mid-flight.
What are TT1 and TT2, and which should we use for migration?
TT1 is real-time DebiCheck authentication: the customer typically has about 120 seconds (or until end of day for delayed TT1) to approve via banking app or USSD. TT2 is overnight batch authentication with up to two days to respond. Migration programmes usually mix both: TT1 for high-value or contactable customers, TT2 for volume waves across the rest of the book.
How long does a NAEDO to DebiCheck migration take?
A typical book of a few thousand mandates takes 6 to 10 weeks: audit and data repair (1 to 2 weeks), authentication waves (3 to 5 weeks), parallel run (2 weeks), then cutover. Larger or messier books take longer. We stage by segment so high-value collections move first and cash flow stays protected.
Will customers actually authenticate during migration?
Industry-wide, only about 62% of DebiCheck mandate requests were authorised in 2024 when timing and messaging were weak. Migration programmes that fire TT1 while the customer is engaged, send clear SMS and email briefings before TT2 batches, and retry expired requests typically lift authentication into the mid-80% range on a cleaned book. That authentication rate is what unlocks early-window collection success.
How much does NAEDO to DebiCheck migration cost?
Mandate audits and authentication campaign setup typically start from around R25,000. Full migrations covering data repair, TT1/TT2 waves, CRM status sync, parallel run, and cutover usually range from R40,000 to R85,000 depending on book size and system complexity. Most collections teams recovering even a few percentage points of monthly debit volume see ROI within one to three months.
Stop Losing Collections on Post-NAEDO Rails
If your mandate book still behaves like a NAEDO hangover, every unpaid cycle is revenue you could already be recovering on authenticated DebiCheck.
Tell us how large the book is, which processor you use, and what your current collection success looks like. We will map a DebiCheck migration plan with authentication waves, parallel run, and a cutover your CFO can defend.