Debit order mandate requirements: what to include (checklist)
A practical debit order mandate checklist for South African businesses: required fields, cancellation and assignment clauses, electronic mandates and storage.
- Published
- Reading time
- 6 min read
- By
- CentraPoint Team
On this page
A debit order mandate must clearly identify your business and the account holder, state the bank account to be debited, the amount (or how it is calculated), the collection date and frequency, the start date and contract reference, and include cancellation and assignment terms, all accepted by the account holder in writing, by voice recording or through a proper electronic process. If a customer disputes a debit order, that mandate is the evidence you rely on.
Rules come from the banking industry's debit order standards (managed through PASA) and from your sponsoring bank or provider, who may add their own requirements. Always use your provider's template or have yours approved by them. This checklist gives you the practical baseline.
Why the mandate matters more than ever
From 13 April 2026, disputes on EFT debit orders raised within 60 days are reversed automatically by the customer's bank. Outside that window, a bank will only look at a dispute in exceptional circumstances after investigating. In both cases your ability to produce a clear, signed mandate decides whether you can recover the money from the customer, and whether your provider keeps trusting your book. See debit order disputes and the 60-day rule.
The mandate checklist
About your business
- Registered business name (and trading name if different)
- Abbreviated short name exactly as it will appear on the customer's bank statement (Netcash, for example, allows 10 characters including spaces)
- Contact details: phone and email for queries
- Physical address
About the account holder
- Full name of the account holder (and the customer, if different: for example a parent paying a learner's fees)
- ID number or company registration number
- Contact details
About the bank account
- Bank name
- Branch code (or universal branch code)
- Account number
- Account type (cheque/current, savings, transmission)
About the collections
- Amount per collection, or a clear rule for calculating it (for example "monthly fee per the attached price schedule")
- Frequency (monthly, quarterly, annually)
- Collection day (for example the 1st or the 25th)
- Commencement date and, if applicable, end date or number of instalments
- Contract or customer reference that will appear on the debit
- What happens when the collection day falls on a weekend or public holiday (see action dates and public holidays)
- How and when amounts may change, and how much notice the customer will get
The legal clauses
- Authority: the account holder authorises you (and your provider) to debit the account
- Cancellation: the customer may cancel the mandate by giving notice, and cancellation doesn't cancel the underlying agreement or amounts owing
- Assignment: whether you may cede or assign the mandate (for example if the business is sold)
- Acknowledgement that the debit will appear under your abbreviated name
- Signature (or electronic acceptance) and date, with place signed if on paper
Netcash's debit order service guide specifically calls out the abbreviated name and the cancellation and assignment clauses as compliance essentials.
Paper, voice and electronic mandates
| Format | How it works | Evidence to keep |
|---|---|---|
| Paper | Customer completes and signs a form | Signed original or a clear scan |
| Voice | Call agent reads the mandate terms, customer agrees on a recorded line | Full recording, linked to the customer record |
| Electronic | Customer completes an online form and accepts with an authentication step | Mandate content, timestamp, IP address, authentication record (for example OTP), audit trail |
A tick-box on a web page on its own is not accepted as valid authorisation by providers such as Netcash. A good electronic mandate shows the full terms, captures the bank details, authenticates the person (usually a one-time PIN sent to their mobile number or email), and produces a record you can export if challenged.
DebiCheck mandates are different again: the customer approves the mandate with their own bank, and the bank holds it. See DebiCheck explained.
Price increases and amount changes
If your mandate says "R450 per month" and you increase to R495, you're collecting outside the mandate unless it allows changes. Build flexibility in from the start:
- State that fees may change annually (or on notice) and how much notice you'll give (for example 30 days in writing).
- Link the amount to a fee schedule or invoice rather than a fixed figure, where your provider allows it.
- For variable amounts (usage billing), say so explicitly, and send an invoice or statement before each collection.
Storing mandates
- Keep the mandate for as long as you collect under it, and afterwards for as long as a dispute or legal claim could arise. Your provider and lawyer can advise a period; many businesses align it with their financial record retention (see invoice record keeping requirements).
- Store mandates securely: they contain bank details and ID numbers, which is personal information under POPIA. Limit access and log it. See POPIA and customer payment data.
- Make them retrievable in minutes, not days. When your provider asks for proof, speed matters.
Common mandate mistakes
- Account holder isn't the customer. A parent pays for a child, an employer for an employee. The account holder must sign, not the customer.
- Missing branch code or account type. Leads to unpaids with codes like 26 (no such account).
- No start date. Customers dispute the first debit because they didn't expect it.
- Statement name mismatch. The mandate says one name; the bank statement shows another.
- Changing the debit date without consent. Always get written agreement for a new collection day.
- Lost mandates. A mandate you can't find is as good as no mandate.
How CentraPoint helps
CentraPoint includes online mandate signing for Netcash debit orders: customers complete the mandate themselves, accept it electronically, and the signed record is stored against their customer profile with the collection schedule. Mandates, collection history and unpaids are visible in one place, and access is controlled by roles and permissions. See the debit order docs for the sign-up flow.
Frequently asked questions
Is an email or WhatsApp message a valid debit order mandate?
Generally no. An informal message usually lacks the required details and a reliable authentication record. Use a proper paper, voice or electronic mandate that your provider accepts.
Does the customer have to sign a new mandate if they change banks?
Yes. The mandate authorises debits from a specific account, so new bank details need a new or updated mandate authorised by the account holder.
Can I use one mandate for multiple products?
You can if the mandate clearly covers them (for example "all amounts due under account 12345"). Many businesses prefer one mandate per contract, which makes disputes easier to handle.
How long must I keep a debit order mandate?
For the life of the collections and afterwards for as long as a dispute or claim may arise. Check your provider's rules and align with your record-retention policy.
- #debit orders
- #mandates
- #compliance
- #collections