Manage Debit Order Mandates and Customer Authorisations
Lost or expired mandates mean bounced debit orders. If your bounced book looks like an affordability problem, check the debit order mandate first: without a mandate management register tied to the CRM, renewals are missed, DebiCheck authorisations lapse, and recovery cost piles up.
We build the mandate register that keeps every authorisation alive and visible.
Sound Familiar?
These are the exact issues finance ops and collections leads face without mandate management:
- Collections blames affordability when the real failure is a lost, expired, or cancelled debit order mandate
- Finance keeps mandates in a spreadsheet that never matches what the payment bureau or bank actually holds
- TT1 and TT2 authentication requests time out (120 seconds for real-time TT1, until 19h00 on Day 2 for TT2) and nobody retries before the mandate expires
- CRM shows the customer as "active" while the DebiCheck mandate is suspended, amended, or already cancelled at the bank
- Every bounced collection burns R100 to R250 in fees and recovery cost before anyone checks authorisation status
DebiCheck only protects collections that still match an active, bank-held mandate. Banks reject presentments that fall outside authenticated terms. If your direct debit authorisation lapsed and nobody noticed, the unpaid is a mandate failure, not an affordability story.
What Mandate Management Actually Does
Authorisation tracked → renewal before expiry → CRM status synced → fewer mandate-driven bounces.
Mandate Register
Every active debit order mandate is inventoried with bank status and CRM link
Expiry Watch
TT1 and TT2 windows, pending amendments, and contract renewals raise alerts before lapse
CRM Sync-Back
Authorised, pending, expired, or cancelled writes to the contact your collections team already uses
Cleaner Collections
Mandate failures route to re-auth; NSF failures route to affordability, so recovery spend is not wasted
Everything You Need for Direct Debit Authorisation Control
Central Mandate Register
Every debit order mandate lives in one register: status, bank, amount ceiling, frequency, authentication type (TT1, TT2, or RM), and last collection date.
Expiry and Renewal Alerts
Pending TT1 and TT2 requests are watched until the bank cut-off. Expired authorisations and soon-to-lapse contracts trigger renewal before the next presentment.
CRM Mandate Status Sync
Authorised, pending, expired, suspended, and cancelled statuses write back to the CRM contact so collections, CS, and finance share one picture.
Bounce Root-Cause Routing
Unpaid reason codes are split into mandate problems versus insufficient funds. Mandate failures go to re-authentication, not another useless affordability chase.
Amount and Amendment Control
When contract amounts change, the mandate amendment is queued and confirmed before the next DebiCheck presentment, so the bank does not reject a mismatched debit.
Collections Dashboards
Live views of mandate coverage, auth pending, expiry risk, and Rand at risk so the collections manager acts before the unpaid batch lands.
Platforms We've Connected for Mandate Management
From 12 Hours/Week Chasing Mandates to 2
How a Gauteng credit provider stopped treating mandate failures as affordability problems and recovered R840,000 in year one.
The Spreadsheet Process
- 4,200 active debit customers tracked in a shared Excel file that lagged the bureau by days
- ~180 unpaid presentments a month; collections treated almost all as NSF
- Audit showed ~40% of those unpaids were expired, cancelled, or never-authenticated mandates
- Finance ops spent 12 hours a week chasing banks and the bureau for authorisation status
- TT2 timeouts sat unnoticed until the next bounce fee landed
The Mandate Register
- Every DebiCheck mandate status syncs into HubSpot on the customer record
- Expiry and pending TT1/TT2 alerts fire before the bank cut-off
- Unpaid reason codes split mandate failures from true NSF automatically
- Mandate-related unpaids dropped 78% within two collection cycles
- Collections only phones affordability cases; re-auth runs on a separate queue
Before vs After Mandate Management
How It Works
From first conversation to a live mandate register in 3 to 5 weeks.
Map Your Mandate Book
How many active debit customers you have, where mandates live today, and which bounces are really authorisation failures.
Free Scoping Call
30-minute call with your finance ops or collections lead to design the register, CRM fields, and renewal alert rules.
Build & Parallel Run
We wire the mandate register to your bureau and CRM, backfill status, and run alerts in parallel until the numbers prove out.
Go Live & Monitor
Renewals and status sync become the default. Dashboards track coverage, expiry risk, and mandate-related unpaid rates.
Frequently Asked Questions
What is debit order mandate management, and how is it different from setting up DebiCheck?
Setup creates templates and first-time authentication. Mandate management is the ongoing lifecycle: tracking every customer authorisation, catching TT1 and TT2 timeouts before they expire, syncing status into the CRM, amending amounts when contracts change, and routing bounced collections to the right fix. Most bounced books we see already have DebiCheck, but no register tied to the CRM.
Why do DebiCheck mandates expire, and what are TT1 and TT2?
TT1 is real-time DebiCheck authentication: the customer typically has about 120 seconds (or until roughly 20h00 for delayed TT1) to approve via banking app or USSD. TT2 is overnight batch authentication; the customer usually has until 19h00 on the second business day. Miss those windows and the request expires. Without alerts and retries, those customers stay "active" in the CRM while collections quietly fail.
How much of our unpaid debit orders are actually mandate problems?
Industry-wide, PASA figures cited by Netcash put roughly 1.2 million of 31 million monthly debit orders as unpaid. Separately, DebiCheck mandate authorisation averaged only 62% in 2024 (SARB NPS report), so nearly four in ten initiation requests never complete. On books without a mandate register, we routinely find a large share of "affordability" unpaids are expired, cancelled, mismatched, or never-authenticated mandates.
Will this disrupt our current Netcash or bureau collections?
No. The register sits alongside your existing bureau and CRM. We backfill status from the payment provider, add renewal and expiry alerts, and write mandate fields back to the CRM. Presentments keep running while we prove the parallel alerts. Only then do you rely on the register for day-to-day collections decisions.
Which systems can you connect for mandate management?
We have wired mandate registers to Netcash, Stitch, and GoCardless on the collections side, and HubSpot, Pipedrive, Salesforce, Zoho CRM, plus Xero or Sage on the business side. Custom billing platforms with an API work too. The goal is one mandate status visible wherever your team already works.
How much does a mandate management integration cost?
A CRM-tied mandate register with expiry alerts and unpaid routing typically starts from around R25,000. Bidirectional setups with amendment workflows, multi-bureau status, and collections dashboards usually range from R40,000 to R75,000. Most teams recovering even a few dozen mandate-related unpaids a month see ROI within two to three months.
Stop Losing Collections to Lost Authorisations
If your unpaid book is full of "NSF" labels that never get checked against DebiCheck mandate status, you are spending recovery budget on the wrong problem.
Tell us how many active debit customers you have, which bureau you use, and where mandate status lives today. We will show you what a CRM-tied mandate management register would recover for your book.