Collecting money from a customer’s bank account
Three tabs under Payments deal with money pulled from a customer’s bank. They look alike and do different jobs. Confusing them is the usual reason a collection cannot be explained.
This article is the depth behind those three tabs. For the whole Payments group, see payments on an account.
The three, side by side
| Tab | What it holds | Who creates it | What it does on its own |
|---|---|---|---|
| Collection Authorities | The customer’s permission to collect at all | Someone requests it; the payer’s bank answers | Nothing moves money. It permits or blocks everything that does |
| Debit Orders | A repeating arrangement to collect a set amount | You, on the tab | Produces one collection each time its schedule falls due |
| Direct Debits | One individual collection | The platform, when something falls due | Goes out to the clearing scheme, then settles or comes back |
Read it as permission, then intention, then attempt.
flowchart TD
A["Collection authority<br/>the payer's permission"] --> B{"Does it permit<br/>this collection?"}
C["Debit order<br/>a repeating arrangement"] --> B
D["Instalment schedule<br/>on a collecting account"] --> B
B --> E["Direct debit<br/>one collection"]
E -- "Permits it when sent" --> G["Submitted, then settled"]
E -- "Refuses it when sent" --> F["Refused, with its reason"]
G --> H["Returned unpaid"]
Two things feed a collection, not one. A debit order is the arrangement you set up by hand. An account that collects its instalments does so straight off its own schedule, with no debit order row at all — see the repayment schedule.
What a collection authority is
A collection authority is the payer’s mandate for a named creditor to collect one agreement’s instalments from one named bank account. Banks call it a mandate, and the tab shows the scheme’s reference for it once there is one.
The mandate belongs to the agreement, not to the person. The paying bank account, the payer, and the creditor are recorded on it. That is what lets Jordan pay Alex’s loan: the payer is an attribute of the mandate, not what identifies it.
One live mandate governs one agreement on one collection scheme. Requesting a second while one is live is refused.
The terms the payer agrees to
| Term | What it means |
|---|---|
| Amount | Either a fixed amount, or a ceiling the collection may not exceed |
| Frequency | How often collection is expected |
| First collection date | The earliest date the mandate covers |
| Tracking days | How long the scheme may keep trying after the due date |
| Signed on | The day the payer signed, if it is known |
The ceiling is the term the platform enforces. A collection above it is refused when it is sent.
Leave the amount blank and the ceiling defaults to the highest instalment in the account’s schedule. An escalating loan whose mandate was pegged to the opening instalment would breach its own mandate partway through the term.
Signed on is optional everywhere except SEPA. A SEPA direct debit carries the signature
date in the file as DtOfSgntr, so a collection under a mandate with no signed-on date
stops the whole file rather than sending half of it. Fill it in before the first SEPA
collection; on every other scheme it is a record, not a requirement. It is the day the
payer signed, not the day the bank proved the mandate, so it cannot be a future date.
Alex’s loan runs three monthly instalments of 2,000.00, 2,200.00 and 2,420.00, in the account’s currency. Requested with no stated amount, the mandate reads up to 2,420.00 — the highest row, so no instalment in the term breaches it.
What each state means
| State | What it means | Can you collect? |
|---|---|---|
| Requested | Captured, not yet sent to the payer’s bank | No |
| Authentication Pending | With the payer’s bank, waiting for an answer | No |
| Authenticated | The payer’s bank holds proof of it | Yes |
| Registered | Lodged but unconfirmed | Yes, but every collection is disputable |
| Declined | The payer’s bank refused it | No |
| Cancelled | Withdrawn | No |
| Disputed | A collection under it came back as unauthorised | No |
The difference between Authenticated and Registered is dispute protection, not speed. Under an authenticated mandate the payer’s bank can be shown the proof. Under a registered one the customer can dispute any collection, and it will succeed.
Where each action lives
- Request a mandate from the payer’s bank account page. The mandate is granted by a payer over an account they bank with, so that is where you ask for it.
- Record the answer — authenticated, registered, or declined — from the Collection Authorities tab on the account or the counterparty.
- Amend or Cancel from the same tab.
There is no live connection to the collection scheme yet. Every answer from the payer’s bank is recorded by a person, from what the bank told them.
The mandate lifecycle follows South Africa’s authenticated-collection scheme rules.
See the standards register row for
PASA / DebiCheck authenticated collections (South Africa) — mandate lifecycle.
Which accounts need one
A mandate is only required where the collection scheme authenticates mandates. Your organisation decides which of its collection rails do. On the ones that do:
- An account that collects over that scheme cannot be activated without a live mandate. Requested is enough to activate, so a signed agreement is not stranded while the bank authenticates.
- Collecting needs more than that. The mandate must be authenticated or registered.
Your organisation can also permit collecting with no mandate at all on a given scheme. That is a deliberate trade: the instalment is collected rather than missed, and every such collection is fully disputable.
What a debit order is
A debit order is a repeating arrangement you set up on the account. Select Schedule on the Debit Orders tab and give it three things: an amount, a schedule, and the bank account to collect from.
The schedule must use a business-day convention, so a collection never falls on a day the banks are shut. See business day conventions.
Your organisation sets a minimum collection amount for each currency. A debit order below it is refused when you save it.
Where the minimum is 50.00, a debit order for 10.00 is refused and the reason names the minimum.
What the tab lists
One row per arrangement, with the schedule in words, the amount, the bank account it collects from, and the next date it is due. An arrangement that is no longer active shows its state instead of the actions menu.
While it is active you can change the amount, reschedule it, point it at a different bank account, or cancel it.
When each collection is raised
A collection is raised before the day it clears, not on it. The scheme needs warning, so the platform works backwards from the clearing date and raises the collection on the right day for that lead.
A monthly debit order of 500.00 due on 15 January is raised on 12 January and clears on 15 January. The tab then shows 15 February as the next due date.
The account is credited on the clearing date, not the raise date. See value dating.
The account moves only once the collection is sent
A raised collection shows on the account as pending. It credits nothing until it is sent to the clearing scheme. If it is never sent, the account is never credited.
If the clearing date passes before the collection is sent, it stays pending. The account shows it as Awaiting submission since the date it was due. A collection of 1,500.00 due yesterday and not yet sent credits nothing today.
If a late collection is sent, it clears on the day it is sent. The scheme never back-dates. A collection of 1,500.00 due on 2 June and sent at end of day on 3 June clears on 3 June. The end-of-day report names it, with both dates.
The warning on a pending collection
A pending collection shows what its mandate would do with it now. The warning sits under the pending line on the account. It is checked each time you open the account, so it is never out of date.
| The mandate now | The warning says |
|---|---|
| Live, and covers the amount | Nothing |
| Live, but the amount is over its ceiling | The amount and the ceiling |
| The payer is under a hold | Nothing is presented while the hold runs |
| None, and the scheme collects without one | It goes out unauthenticated, and the payer can dispute it |
| None, and the scheme needs one | The payer has granted no mandate |
Alex’s vehicle finance account has a pending deposit of 30,000.00 and a mandate with a 25,000.00 ceiling. The warning reads: the collection of 30,000.00 exceeds the 25,000.00 the payer’s collection authority permits.
Fix the cause before the collection is sent, and the warning clears. Amend the mandate to 30,000.00, and the bank proves it, and the same deposit goes out.
When a debit order replaces the instalment
Your organisation decides, for each lending product, whether a debit order replaces the instalment collection. If it does, an active repeating debit order is how the instalment is paid. The platform raises no separate instalment collection for that period.
- Each instalment period is judged on its own. A period runs from one due date to the next. If the debit order collects in that period, it replaces that instalment.
- A once-off debit order never replaces. It is an extra payment on top.
- A suspended or cancelled debit order stops replacing. The instalment collection resumes from the next instalment that has not yet been raised.
- Arrears built up meanwhile stay. They are not pulled when collection resumes. They go through your usual arrears process.
The Instalments panel shows each replaced instalment as Replaced by debit order. See the repayment schedule.
The warnings in the debit order dialogs
When you schedule, reschedule or change the amount of a debit order, the dialog checks it against the instalment. The warning does not stop you saving.
Alex’s loan has an instalment of 2,522.03 due on the 10th. You add a monthly debit order of 1,000.00 collected on the 14th. The dialog says the order replaces the instalment and is 1,522.03 short each month. That shortfall goes into arrears.
The check uses the leanest period, not the average. A weekly order of 600.00 collects 2,400.00 in a month with four collections, so it is 122.03 short. A weekly order of 700.00 collects at least 2,800.00, so it raises no shortfall warning.
If the order collects after the due date, the dialog says by how many days. The account shows arrears in between. A collection on the 14th against a due date on the 10th is usually 4 days late. A weekend can push it further. With the order on the next-business-day convention, November 2026 is 6 days late. The dialog shows the longest gap over the next twelve instalments.
If the customer wants to pay extra each month, raise the debit order amount. Do not add a second repeating order expecting it to be extra.
What a direct debit is
A direct debit is one collection: one amount, one date, one attempt. The Direct Debits tab is the record of every attempt on this account.
| Column | What it tells you |
|---|---|
| Trading Date | The day the collection was raised |
| Settlement Date | The day it clears |
| External Account | The customer’s bank account it collects from |
| Amount | What is being collected |
| Trace Number | The reference it went out under, once sent |
| Payment File | Open file opens the payment file it went out in. Blank until it is sent |
| Status | How far it got |
A collection waiting for a decision offers Approve and Reject on its row.
| Status | What happened |
|---|---|
| Requested | Raised, waiting for a decision |
| Approved | Cleared to go, not yet sent |
| Rejected | Someone stopped it before it went |
| Refused | The mandate did not permit it when it was sent. The reason shows under the status |
| Submitted | Sent to the clearing scheme |
| Returned | It came back unpaid. The status names the reason |
Use the status filter to list only Refused collections.
When a collection is refused
The mandate is checked when the collection is sent, not when it is raised. A mandate can be cancelled, amended, or put under a hold in between. So the check that counts is the last one.
If the mandate refuses, the collection becomes Refused. It never reaches the bank, and the account is not credited. Nothing needs reversing. The amount it was collecting stays due, and arrears follow your usual policy.
Alex’s debit order of 30,000.00 is refused because the payer is under a debt-review hold. The row shows Refused, and under it: the payer is under a hold, so nothing is presented for collection.
A collection of 30,000.00 over a 25,000.00 ceiling stays refused while an amendment to 30,000.00 waits for the bank. The reason names the pending mandate, not the ceiling.
Only you see a refusal. The customer is not told. If they need to know, tell them.
Collecting again after a refusal
A refused collection is final. It is never sent again.
- Fix the cause the reason names. Amend the mandate, chase its proof from the payer’s bank, or wait for the hold to lift.
- Select Deposit, and collect the refused amount by direct debit.
The new collection is checked when it is sent, like any other. If the refused amount was an instalment, it stays due until a collection clears it.
What the mandate tab shows about collections
The Collection Authorities tab counts the collections that went out under each mandate, with the latest amount and date.
Three collections of 900.00, 1,000.00 and 1,100.00 under a mandate with a 1,500.00 ceiling read as 3 collected, showing 1,100.00 as the latest. None breaches the ceiling.
A mandate later amended below a collection that already went out is flagged over ceiling. The collection is history; the breach is worth seeing.
When a collection does not go out
A collection that never leaves is invisible unless someone says so. A quiet loan looks exactly like a delinquent customer, and the two need opposite actions.
A collection is raised whatever its mandate says. The pending line warns you first. If the mandate still refuses when it is sent, the collection is Refused with the reason.
That refusal is also recorded on the account. The Collection Authorities tab shows the count and the latest reason, and the Blocked Collections page lists every account in that state.
One case cannot raise a collection at all. If the account names no bank account to collect from, nothing is raised, and the account records that day instead.
| Reason | What to do |
|---|---|
| The account names no bank account to collect from | Nominate one on the account |
| The payer has granted no mandate | Request one from the payer’s bank account page |
| The mandate does not permit collection | Chase the answer from the payer’s bank |
| The instalment is above the mandate’s ceiling | Amend the mandate |
| The customer is held | Nothing is presented while the hold runs |
A hold does not cancel the mandate. Collection resumes when the hold is lifted. See hold.
The first two reasons are ordinary onboarding failures, and they are the most common. A customer who never completed the authentication at their bank fails the first collection and then goes quiet. See chasing arrears.
When a collection comes back
A collection can settle and still be reversed later. The clearing schemes allow a window, and an unpaid return arrives inside it.
| Reason it came back | What it means |
|---|---|
| Insufficient funds | The money was not there |
| Account closed | The customer’s bank account no longer exists |
| Invalid account | The account details are wrong |
| Not authorised | The payer’s bank says no mandate covers this collection |
Whatever the reason, the collection is reversed on the account.
The reversal is dated at the original collection’s value date, not the day the return arrived. So interest on a balance that never really cleared is corrected, rather than left overstated for the days in between. Both entries show on the transaction list — see reading the transaction list.
A not-authorised return is different
If a collection under an authenticated mandate comes back as not authorised, the two facts contradict each other. The payer’s bank confirmed the mandate, then said it does not cover the collection. The mandate is marked Disputed and stops collecting until someone investigates.
Under a Registered mandate, the same return is absorbed normally and the mandate keeps its state. That stream is disputable by design, so the return is expected behaviour rather than a contradiction.
Returns are not yet fed in from the clearing scheme. Like authentication answers, they are recorded from what the bank reports.
How a customer’s instruction to stop is recorded
A customer can ask you to stop two different things, and the difference matters.
| They say | You do | Effect |
|---|---|---|
| “Stop this monthly payment” | Cancel the debit order | The arrangement ends. No further collections are raised from it |
| “I withdraw my permission” | Cancel the mandate | Nothing collects on that agreement at all, from any source |
Cancelling the mandate also stops collections already in flight. An approved collection that has not been sent is Refused when it is sent, naming the missing permission. That matters: without it, a payer who withdrew permission on Monday would still be collected from on Tuesday.
Both cancellations are recorded with the reason and the person who did it, so the trail says why collection stopped.
Changes that need the payer’s bank to agree again
Some changes mean the payer’s bank no longer holds proof of what you are collecting. The mandate then goes back to Authentication Pending. Nothing is collected under it until the bank answers. A collection sent meanwhile is Refused.
- The paying bank account is changed, or its account number changes.
- A term the payer authenticated is changed — typically the payment schedule or the collection account.
Which changes count is your organisation’s configuration. It marks the inputs on each operation that a payer authenticated, so re-authentication follows the terms the payer actually agreed to, rather than every edit.
An amendment works the same way. The new terms are parked and shown as Awaiting Re-authentication. Nothing collects until the bank proves them. The old terms are kept on the mandate meanwhile, as a record of what was last proven.
When a tab is not there
Each of these three capabilities is licensed separately, and a tab you do not license does not appear. A product also names which tabs its accounts carry, so a deposit that is never collected on shows no debit order.
The Collection Authorities tab is the exception. It also appears when one of your collection rails authenticates mandates, licensed or not — otherwise the account would refuse to activate for a reason with no screen behind it. See switching features on and off.
Related: paying money in, how a repayment is recorded, how a payment picks its rail, choosing which account money moves through.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.