Debit Order Mandate Authorisation Process in South Africa

Most guides to the debit order mandate authorisation process are written for bankers. They talk about creditors, debtors and originators. You just want to know how to get permission to collect, and how to avoid chasing members, tenants or parents every month.

This guide uses plain roles. You are the business collecting. Your customer is the person paying. Each of you has a bank, and both banks play a part.

What a debit order mandate actually is

A mandate is your customer's permission for you to collect money from their bank account. That's all it is. It records who agreed, to what, and how often.

The debit order is something different. It is the collection itself, the actual pull of money on a given date. Every debit order runs under a mandate, and a mandate with no collections attached is just paperwork. You'll also see the same idea called a "direct debit", which is the search term many people use for the same thing.

Here is who is who:

• You: the business that collects.
• Your customer: the person who gives permission and pays.
• Your bank or payment provider: the party that submits your collections.
• The customer's bank: the party that holds their account and, under DebiCheck, checks the mandate first.

If you keep one distinction in mind, make it this one: the mandate is the permission, the debit order is the use of it.

Mandate types: fixed, variable and once-off

The mandate type controls how much you can collect, and whether a changed amount needs the customer's approval again. Pick the wrong one and you create re-approval work for yourself.

A fixed mandate collects the same amount each time. A variable mandate collects an amount that can change, up to a ceiling your customer approved at the start. A once-off mandate covers a single collection and then ends.

One rule matters more than the rest: if you want to collect above the approved ceiling, you need a fresh approval from the customer.

Matching each mandate type to membership dues, levies and rent

Match the type to how your charges behave, not to how your spreadsheet happens to look.

Membership dues usually suit a fixed mandate. The fee is the same each month, so the customer approves once and you collect. A golf club moving dues out of a spreadsheet is a typical case, and our guide to automated membership fee collection for golf clubs shows how that looks day to day.

Levies often change. An estate that adjusts its levy every year is better off with a variable mandate and a ceiling the homeowner has approved, because a fixed mandate would need fresh approval every time the amount moves. The same logic runs through our piece on levy collection software for estates. Set the ceiling with some headroom, but keep it realistic, since the customer sees that number when they approve.

Rent is typically a fixed monthly amount, so a fixed mandate works well. Landlords and managers can read more in our rent collection app for property managers. If rent escalates each year, treat that like a levy and think about a variable mandate from the start.

Subscriptions follow the same rule. Steady price, fixed mandate. Usage-based or changing price, variable mandate with a ceiling.

Use a once-off mandate for a joining fee, a deposit or a catch-up payment. It doesn't suit anything that repeats.

DebiCheck basics: why the customer's bank approves first

DebiCheck is the best-known authenticated collections process in South Africa. The customer's own bank validates the mandate, and the customer approves it, before the first debit. PASA administers the clearing rules behind it, and the SARB oversees the national payment system.

The reason is simple. Someone other than you confirms the customer actually agreed to these terms.

What DebiCheck changed for businesses that collect

Before DebiCheck, a signed form was enough to start debiting. The customer often found out about the arrangement on their bank statement, and disputes followed.

That gap cost operators real time. Collections were returned, customers disputed amounts they didn't remember agreeing to, and somebody had to sort it out by hand.

DebiCheck closes the gap by putting the check before money moves. If the customer approves, you collect against a mandate you can rely on. If they don't, you find out before the first debit rather than after a returned one.

Authenticated collections: what changes on the first debit

Under an authenticated collections mandate, your customer sees the terms in their own banking channel and confirms them. Those terms include who is collecting, the amount or ceiling, and the frequency. Nothing is collected until that approval is in.

DebiCheck is one industry process. Every bank follows the same steps, even though each bank's approval screens look different. Your customer may approve in a banking app, while someone at another bank sees a different layout. The process underneath is the same, so you don't need to design a separate flow per bank.

How authorising a debit order mandate works, step by step

The authorisation sequence is short. The trouble usually comes from skipping a step or from capturing a detail wrongly, because the customer's bank checks what you submit against what the customer sees.

Mandate setup in South Africa: capture, submit and request approval

1. Capture. Collect your customer's details and the mandate terms: amount type, amount or ceiling, frequency and start date.
2. Submit. Send the mandate through your bank or payment provider.
3. Request approval. The customer's bank sends the request to the customer, who approves it in their banking channel.
4. Collect. Only collect against a mandate that has been approved.

The fourth step is the one that protects you. An unapproved mandate is not a mandate you can collect on.

Does your customer need to visit their bank? No. They approve in their own banking channel, such as their app, so they don't need to queue at a branch. They only contact their bank if the request never appears. In that case, check your captured details first, because a wrong account or phone number is the usual cause. Then resubmit.

Parents face the same process when schools collect fees, and our school fee collection guide shows how that capture step works for them.

Customer approval, declines and stops

A customer can decline the request. A request that goes unanswered also doesn't become an approved mandate. In both cases you have no authority to collect, so don't schedule debits and hope.

Your next move is practical. Contact the customer, find out whether the terms were wrong or the request was missed, and resubmit with corrected details if needed. If they decline because they don't want the arrangement, agree another payment method.

Customers can also stop a mandate later. They do this through their own bank, not through you. When that happens, cancel your own schedule for that customer as well, so you don't keep trying to collect on a mandate that no longer exists.

One honest limit: an approved mandate is permission, not a guarantee. If the customer's account has no funds on collection day, the debit can still fail.

NAEDO vs DebiCheck mandate: which route your collections use

NAEDO is the older route. Under it, you hold the signed mandate, and the bank processes the debits without first checking with the customer's bank. The customer may only see it when the money moves.

DebiCheck adds the upfront check. The customer's bank validates the mandate, and the customer approves it, before the first debit.

That is the practical difference between the two. NAEDO leans on your paperwork. DebiCheck leans on the customer's confirmation.

Confirming the route with your bank or provider before go-live

Which rules apply depends on how each collection is set up, so don't assume. Ask your bank or provider which rules apply to each type of collection you run. Ask, too, whether any legacy mandates you already hold need re-authentication before you keep collecting on them.

You'll know you're on the DebiCheck route when your customers receive approval requests in their banking channel. If nobody is being asked to approve anything, find out why before you go live.

Do this check once, early, and write down the answer. It is far cheaper than discovering the answer through a batch of returned debits.

Mandate requirements and compliance: what to capture and protect

A mandate is only as good as the details behind it. If one detail is wrong, the customer's bank can't match what you submitted to what the customer is asked to approve.

Debit order mandate requirements: what every mandate must capture

A valid mandate holds:

• Customer identity: so the bank can tie the mandate to the right person.
• Account details: so the request reaches the correct bank and account.
• Your business details and reference: so the customer recognises who is collecting and why.
• Amount type and ceiling: fixed or variable, and the limit the customer approved.
• Frequency: so the customer knows how often you'll collect.
• Start date: so the first collection lines up with what they agreed.
• A record of consent: your proof that the customer said yes.

Each item shows up at approval. The customer reads your name, the amount and the frequency, and decides. Vague references like a bare account number lead to declines, because customers don't approve what they don't recognise.

SARB mandate rules and POPIA: what you are responsible for

The layers differ, so keep them apart. The SARB oversees the national payment system. PASA's clearing rules set the mandate process, and they mostly bind banks and clearing participants rather than you directly.

POPIA does put direct duties on you. You are responsible for how you store and use your customers' banking details. Collect only what you need, protect it, and use it for collections.

PCI DSS applies only where you handle card data. If you only collect by debit order from bank accounts, it isn't your obligation in the same way. Recurv is built for the South African market with PCI DSS and SARB compliance, so you don't carry that load alone.

This is general information, not legal advice. Check your own obligations with a qualified adviser.

What happens once a mandate is approved, and where Recurv automates it

Once a mandate is approved, it should drive everything else. The amount, the frequency and the start date become your schedule and your collection rule. Nobody re-keys them.

Manual setups fall apart at exactly this point. Someone copies mandate terms into a spreadsheet, someone else updates the schedule, and the figures drift. Then reconciliation turns into a monthly hunt for what was paid, what bounced and why.

Recurv runs mandate authorisation as the first step of one automated cycle: authorise, schedule, collect, reconcile. An approved mandate feeds scheduling and collection directly, with no separate spreadsheet in between. Reconciliation closes the loop, so you see what came in against what you expected.

Recurv also keeps its holding balance very small. That matters if you're a smaller business that assumed a debit order system was out of reach because of large holding balance requirements. Our guide to debit order setup for a small business covers what that looks like in practice.

Stop chasing payments. Start running your business. If you'd like to watch the whole flow from mandate request to reconciled payment, see the full flow in a live demo.

Frequently asked questions

How do I stop a debit order mandate?

The customer stops it through their own bank. If you are the business, cancel your own schedule for that customer at the same time so you don't keep trying to collect. Then agree another way to pay.

Do I need to contact my bank to set up a direct debit?

As a business, you submit mandates through your bank or payment provider. Your customer doesn't have to visit a branch, because they approve the request in their own banking channel, such as an app. They only contact their bank if the approval request never appears.

What is a DebiCheck mandate?

It is a debit order mandate that the customer's bank validates, and the customer approves, before the first debit. This replaced the old habit of debiting on a signed form alone. You can only collect once the customer has approved.

Is DebiCheck a Nedbank product?

No. DebiCheck is one industry-wide process that every bank follows. Nedbank customers approve in Nedbank's channels, and customers at other banks use their own bank's screens. The steps behind them are the same.

What happens if a customer ignores or declines the approval request?

The mandate isn't approved, so you can't collect against it. Contact the customer, find out whether the terms were wrong or the request was missed, and resubmit with corrected details if needed. If they simply don't want the arrangement, agree another payment method.