A debit order is a standing instruction that lets a business pull an agreed amount from a customer's bank account on an agreed date. South Africa runs three collection rails — DebiCheck, Registered Mandate (RM) and EFT — and each one differs in how the mandate is authorised, when it is processed, and how easily it can be reversed. Since 13 April 2026, customers have 60 calendar days to dispute a collection on any of them.
If your business bills the same customers every month — a gym, an ISP, a security firm, a managed services provider, a subscription product — your revenue is only as reliable as your collections. And collections in South Africa are not a single, uniform thing. They are three different rails with different rules, different processing windows, and very different dispute risk.
Most owners discover this the hard way: a month where 12% of collections come back unpaid, a customer who reverses six months of debits at once, or a billing run that quietly skipped forty accounts because a mandate detail changed. This guide explains how the system actually works, so you can choose the right rail and build the right process around it.
How does a debit order work in South Africa?
Every debit order rests on a mandate — the customer's permission for you to collect a specified amount, on a specified date, at a specified frequency. What differs between the three rails is who holds and verifies that mandate.
The mechanics are consistent:
- You capture a mandate when the customer signs up.
- You submit a collection instruction to your bank or third-party payment provider before the cut-off for your action date.
- The instruction is presented against the customer's account in a specific processing window.
- If it fails, you may re-present it during a tracking window of up to 10 days, depending on the rail.
- The customer can dispute the collection with their own bank within the dispute window.
Volumes here are enormous. PASA's 2023 Integrated Report recorded 443 million EFT debit transactions and 180 million DebiCheck transactions in a single year. Debit orders are not a niche mechanism in South Africa — they are the default way recurring revenue moves.
Note the direction of travel. A debit order pulls money on a schedule you control, which makes it a different instrument from the once-off card or EFT payment a customer pushes at checkout. If that is the problem you are actually solving, start with how to choose a payment gateway instead.
What is the difference between DebiCheck, Registered Mandate and EFT?
This is the decision most businesses get wrong, usually by defaulting to whatever their provider set up first.
DebiCheck is South Africa's authenticated rail. Before you can collect, the customer confirms the mandate directly with their own bank — via their banking app, USSD, ATM or a card terminal. The bank stores the authenticated mandate and checks every subsequent collection against it. Collections are presented in the earliest morning window, directly after bulk credits land. That timing matters enormously on payday.
Registered Mandate (RM) replaced the interim Registered Mandate Service (RMS) on 12 May 2025. RM does not require real-time customer authentication. Instead, you register the mandate against the customer's account and their bank notifies them, sharing your business details and the contract reference. RM collections are processed in the evening window, ahead of EFT, and support tracking for up to 10 days.
EFT debit orders are the legacy rail. The mandate lives with you — a signed form, a voice recording, an online tick-box. The bank does not verify it before processing. EFT is presented last, in the late evening window, and does not carry credit tracking.
| DebiCheck | Registered Mandate (RM) | EFT debit order | |
|---|---|---|---|
| Who verifies the mandate | The customer's bank, before first collection | Bank registers and notifies the customer | Nobody — you hold the evidence |
| Customer authentication | Required (app, USSD, ATM or card + PIN) | Not required | Not required |
| Processing window | Earliest morning, after bulk credits | Evening, before EFT | Late evening, after RM |
| Credit tracking | Up to 10 days | Up to 10 days | None |
| Dispute risk | Very low — valid collections matching the mandate are effectively irreversible | Moderate | Highest |
| Typical cost | Highest per transaction | Mid | Lowest |
| Best suited to | High-value, long-term contracts: lending, insurance, education, telecoms | Subscriptions, memberships, rentals, legacy mandates | Low-value, low-risk, established customers |
The trade-off is straightforward: DebiCheck costs more per transaction and buys you priority timing and near-immunity from disputes. For a R199/month subscription with a loyal base, that premium may not pay for itself. For a R4,500/month instalment agreement, it almost certainly does.
What changed on 13 April 2026?
The dispute window changed — and it changed in the customer's favour.
Previously, a customer could dispute a debit order for up to 365 days, with disputes raised within 40 days reversed automatically. Following an industry initiative led by PASA with the South African Reserve Bank and the Financial Sector Conduct Authority, from 13 April 2026 the automatic dispute window is 60 calendar days across EFT, Registered Mandate and DebiCheck. Disputes raised after 60 days will generally not be accepted.
Two practical consequences:
- Your exposure period is 50% longer. Revenue you recognised in March can still walk back out the door in May. If you were treating a collected debit as final after 40 days, that assumption is now wrong.
- The case for DebiCheck strengthened. Valid DebiCheck collections that match the authenticated mandate remain effectively irreversible, because the bank can compare the debit against the mandate it holds. On EFT, a longer window simply means more time for a dispute to land.
If you have never reconciled reversals against original invoices, this is the moment to start. You cannot manage a risk you are not measuring — which is exactly the kind of thing a connected finance and invoicing module should surface without anyone exporting a spreadsheet.
Why do debit orders fail, and what can you actually control?
Some failures are genuine — the money isn't there. Many are not. The controllable ones cluster into four areas.
Mandate authentication drop-off. DebiCheck mandates come in three flavours. TT1 sends a real-time request to the customer's banking channel, valid until roughly 8pm the same day. TT2 goes out in an overnight batch and gives the customer about two days. TT3 is authenticated in person at a card terminal, with the customer's card and PIN. Altron FinTech has reported that a substantial share of TT1 and TT2 requests — in the region of 35–40% — go unauthenticated each month, largely because customers miss the prompt rather than refuse it. Every failed attempt still carries a fee. Where you onboard face-to-face, TT3 removes the problem entirely.
Collection date. Salaries land at different times across employers. Collecting on the 1st puts you in a queue with everyone else; collecting on the 25th or 26th, in the early DebiCheck window, often puts you ahead of it. Let customers choose from a small set of dates and store that choice properly.
Date adjustment settings. If your action date falls on a Sunday or a public holiday and your date adjustment indicator is set to "no", the collection simply doesn't happen. Setting it to "yes" lets the transaction present on the nearest valid day. It is a one-line configuration that quietly costs businesses real money.
Not using the tracking window. Both DebiCheck and RM allow re-presentment for up to 10 days after a failed action date, without re-authorisation. Many businesses present once, mark the account unpaid, and move to collections. Tracking recovers a meaningful slice of that automatically.
Mandate drift. DebiCheck mandates are bound to their parameters. Change the amount, the date or the frequency materially and the customer must re-authenticate before you collect again. Some providers automatically set a maximum collection value at a multiple of the instalment (often 1.5×) to give usage-based billing headroom. Your annual price increase is a mandate event, not just an invoice change — and if your systems don't know that, your April run breaks.
Not sure where your collections are leaking? Book a no-obligation discovery call and we'll map your billing flow end to end — mandate capture, collection run, reconciliation and reversals.
What does debit order collection cost in South Africa?
Pricing is quoted per business rather than published, and it varies with volume, risk profile and rail. Rather than chase a headline rand figure, understand the components you will be charged for:
| Cost component | What it covers | Why it bites |
|---|---|---|
| Monthly platform fee | Access to the provider's collection service | Fixed, regardless of volume |
| Per-transaction fee | Each collection presented | DebiCheck > RM > EFT |
| Mandate authentication fee | Each TT1/TT2 request sent | Charged whether or not the customer authenticates |
| Unpaid / rejection fee | Each failed collection | Scales with your failure rate, not your revenue |
| Tracking fee | Each re-presentment attempt | Worth it if recovery rates justify it |
| Bank charges | Your own bank's fees | Separate from your provider's fees |
Treat these as indicative categories, not a quote — your actual rates depend on your volumes and industry. The number that matters is not the per-transaction fee in isolation; it is cost per successfully collected rand, which is where authentication drop-off and unpaid fees do their damage.
What should your billing system actually do?
Whether you buy a platform or build one, the requirements are the same. A recurring billing setup that works in South Africa needs to:
- Store mandates as first-class records, with rail, mandate type, authentication status, maximum collection amount and date adjustment setting — not as a note on a customer record.
- Generate the collection file automatically from active contracts, so nobody rebuilds a CSV by hand each month.
- Reconcile the return file back to invoices, marking paid, unpaid and reversed without manual matching.
- Trigger re-authentication when an amount, date or frequency changes materially.
- Drive dunning — a defined sequence of reminders, retries and escalation when a collection fails.
- Report on collection health: success rate by rail, by date, by cohort; unpaid ratio; dispute ratio; recovery from tracking.
- Handle personal information lawfully. Bank details and contract records are personal information under POPIA, which means purpose limitation, access control and retention rules apply. Our approach to POPIA sets out what that looks like in practice.
Most off-the-shelf accounting packages do the first two adequately and the rest poorly. That gap — between "we can send a batch" and "we can see and manage collection health" — is where the spreadsheets breed.
Should you buy a platform or build custom collections logic?
Buy when your billing is standard: fixed monthly amounts, one or two plans, a single rail. A connected operations platform that already ties invoicing to CRM, support and reporting will beat a bespoke build on both cost and time. You can see how that's packaged on our pricing page.
Build when the billing logic itself is the complication — usage-based or metered charges, split billing across parties, pro-rating mid-cycle changes, tiered commissions, or a provider integration nobody has plugged into your stack before. In those cases the mandate rules aren't the hard part; your pricing model is. That's custom software territory, and it's the kind of work our Cape Town team does in-house, with weekly demos so you see the collection run working before it touches a real bank account.
The honest test: if you can describe your billing rules on one page, buy. If it takes three pages and a diagram, build — or build the pricing engine and let a platform handle the rest.
Frequently asked questions
What is the difference between DebiCheck and a normal debit order? With DebiCheck, the customer authenticates the mandate with their own bank before the first collection, and the bank checks every subsequent debit against it. With a standard EFT debit order, the mandate stays with the business and the bank does not verify it before processing.
Can a customer reverse a DebiCheck debit order? Only in limited circumstances — typically where the collection does not match the authenticated mandate, or was processed in error. A valid DebiCheck collection that matches the mandate on record is effectively irreversible, which is the main reason businesses accept its higher cost.
How long does a customer have to dispute a debit order in South Africa? From 13 April 2026, the automatic dispute window is 60 calendar days across EFT, Registered Mandate and DebiCheck. This replaced the previous 40-day automatic window. Disputes raised after 60 days will generally not be accepted.
Did the Registered Mandate replace RMS? Yes. The Registered Mandate (RM) replaced the interim Registered Mandate Service (RMS) on 12 May 2025. RM is a permanent rail rather than a transitional one, is processed in the evening window before EFT, and supports tracking for up to 10 days.
Do I need my own software to run debit orders? No — you collect through a bank or a registered third-party payment provider. What you need software for is everything around the collection: generating the batch from live contracts, reconciling returns to invoices, managing re-authentication, and running dunning when a collection fails.
How can I reduce failed debit orders? Use TT3 point-of-sale authentication where you onboard in person, let customers choose a collection date that matches their payday, enable date adjustment so collections still present on Sundays and public holidays, and use the full 10-day tracking window before writing an account off as unpaid.
Get your collections working properly
Reliable recurring revenue is an engineering problem before it is a finance problem. The rail you choose, the date you collect, the way your system reacts to a failure — each one moves your cash flow by percentage points, every single month.
If your billing currently lives across a bank portal, an accounting package and a spreadsheet, book a no-obligation discovery call. We'll look at your actual collection data, show you where the leakage is, and tell you plainly whether Syniq Business OS covers it or whether you need something built.
Written by Mikhail for Syniq (Pty) Ltd. Syniq is a Cape Town software company building Business OS and custom software for growing South African businesses. This article is general guidance, not legal or financial advice — confirm your own obligations with a qualified advisor. Rules and pricing are indicative for August 2026 and move with scheme and vendor changes.