The Registered Mandate Lifecycle Explained
A registered mandate is not a once-off event. From the moment it is registered at the payer's bank, the mandate is a living record that can be amended when contract terms change, suspended when collections must pause, and cancelled when the agreement ends. Each of these operations is communicated between your sponsoring bank and the payer's bank using ISO 20022 messages.
Understanding the lifecycle helps you keep your own records in sync with the bank-side record — mismatches between the two are a common cause of failed collections and avoidable disputes.
What are the stages of the registered mandate lifecycle?
| Stage | What happens | Resulting status |
|---|---|---|
| Initiation | Mandate details are registered at the payer's bank; payer is notified | Registered (or rejected) |
| Amendment | Changed terms — such as amount, frequency or collection date — are submitted and recorded | Amended (or rejected) |
| Suspension | Collections against the mandate are paused without ending the mandate | Suspended |
| Cancellation | The mandate is ended; no further collections may be submitted | Cancelled |
Statuses are described generically here; the exact codes and message formats depend on your bank's API or host-to-host file specification. See API vs Host-to-Host Integration.
How is a mandate initiated?
Initiation is the registration step: you submit the mandate details, the payer's bank validates and records them, and the payer is notified of the registration. A successful initiation returns a registered status; a failed one returns a rejection, for example where account details are invalid or the account cannot accept mandate registration. The full flow is covered in Registration and Payer Notification.
Only collect against mandates in a registered (or validly amended) state. Collecting against a rejected or cancelled mandate exposes you to unpaids and disputes.
When and how do you amend a mandate?
Amend the registered mandate whenever the collection terms change — a new instalment amount, a different collection day, a changed frequency. The amendment is sent to the payer's bank, which updates the registered record.
Keep two principles in mind:
- The bank record must match what you collect. If you increase the instalment in your billing system but never amend the registered mandate, the bank-side record no longer supports your collections, weakening your position in any dispute.
- The payer must have agreed to the change. An amendment message updates the bank record, but your authority still comes from the underlying contract. Changes the payer never agreed to remain disputable regardless of the registered record.
What does suspension do?
Suspension pauses the mandate without ending it. The registered record remains at the payer's bank, but collections should not be submitted while the mandate is suspended. Typical uses include payment holidays, account queries under investigation, or a payer instruction routed through their bank.
A suspended mandate can later be reactivated or cancelled, depending on how the situation resolves. Track suspended mandates carefully so collections resume only when the mandate is active again.
How is a mandate cancelled?
Cancellation ends the mandate permanently. It can originate from your side — the contract has ended or been settled — or from the payer's side via their bank, for example after a dispute or a payer instruction. Once cancelled:
- No further collections may be submitted against the mandate.
- A new agreement with the payer requires a new mandate and a new registration.
If the payer cancels the registered mandate but your underlying contract is still in force, the contractual debt does not disappear — but you no longer have a mandate to collect it by debit order. Resolve the contractual position with the payer before attempting any further collection.
How do you keep lifecycle state in sync?
- Process every response and status message from the bank, not just successes.
- Reconcile your mandate register against bank responses regularly.
- Block collection submission automatically for suspended, cancelled or rejected mandates.
- Keep an audit trail of every lifecycle event alongside the underlying contract.
Kwik manages this synchronisation for you when you run registered mandate collections through the Kwik platform, exposing current mandate status so your billing only collects against active mandates.
Related topics
Juristic Accounts
How registered mandates handle business, juristic and multi-signatory bank accounts that DebiCheck cannot authenticate in real time.
Collections and Settlement
How collections against registered mandates are submitted, how tracking re-presents unpaid collections, and when settled funds reflect in your account.