DebiCheck Mandates vs Collections: What Is the Difference?
DebiCheck has two distinct halves that are easy to confuse: the mandate and the collection. The mandate is the permission — the debit order terms the consumer approves with their bank at the start of a contract. The collection is the actual payment instruction that debits the consumer's account on a given day.
Understanding the split matters because each half has its own messages, statuses and failure modes. A mandate can be perfectly authenticated while a collection against it still fails, and a collection can only ever succeed if a valid mandate exists first.
What is a DebiCheck mandate?
A DebiCheck mandate is the electronic record of the consumer's approval. When a new contract is signed, the consumer receives a request from their bank to approve the debit order information — typically the instalment amount, any maximum collection amount, the frequency, the collection day and the service provider's details.
Once the consumer authenticates the request, the bank stores an electronic copy of the mandate in its mandate register. From that point on, the bank will not allow a collection outside the approved terms.
A mandate is created once per contract and then lives on through amendments, suspensions and eventually cancellation. See the mandate lifecycle for the full journey.
What is a DebiCheck collection?
A collection is the payment instruction the service provider submits to actually debit the consumer's account — usually monthly, on the agreed collection day. Before processing a collection, the consumer's bank verifies it against the stored mandate:
- If the collection matches the mandate (right account, right amount within the approved limits, right frequency), it is processed.
- If the collection does not match, it is rejected and no money moves.
DebiCheck collections are processed as first priority in the early morning processing window, after credits, which improves the chance of collecting before other debit orders reach the account.
How do mandates and collections compare?
| Aspect | Mandate | Collection |
|---|---|---|
| What it is | The consumer's bank-authenticated permission | The instruction that debits the account |
| How often | Once per contract, plus amendments | Every collection cycle (e.g. monthly) |
| Who approves it | The consumer, via their bank's channels | No approval needed — verified against the mandate |
| Typical statuses | Pending authentication, authenticated, rejected, expired, suspended, cancelled | Successful, unpaid/declined, tracking |
| Common failures | Consumer does not respond in time, or rejects the request | Insufficient funds, account closed, mandate suspended |
Why does the distinction matter in practice?
- A failed authentication is not an unpaid. If a consumer never approves the mandate, no collections can be submitted at all. Fix the mandate first — see troubleshooting.
- An unpaid collection does not invalidate the mandate. If a collection fails for insufficient funds, the mandate remains authenticated and you can track or retry — see collections, tracking and retries.
- Amendments apply to the mandate, not the collection. If the instalment amount changes beyond what the mandate allows, the mandate must be amended (and may require re-authentication) before collections at the new amount will pass verification.
- Suspension blocks collections but not the contract. A consumer can suspend a mandate at their bank, which stops future collections, but the underlying agreement must still be cancelled with the service provider.
Kwik's platform manages both halves — initiating and maintaining mandates, and submitting and reconciling collections — so businesses see one consistent view of each payer.
Related topics
DebiCheck for Business
DebiCheck gives businesses collection certainty, early processing priority, tracking, dispute protection and suspension notifications. See how to participate.
TT1, TT2 and TT3
Compare DebiCheck TT1 real-time, TT2 delayed and TT3 card-and-PIN authentication, including timeouts, use cases and when each transaction type applies.