Registered Mandate Returns and Disputes Explained

Even with a mandate registered at the payer's bank, not every collection succeeds and not every payer accepts every debit. Returns (unpaid collections) and disputes are a normal part of running a collections book — what changes with registered mandates is the strength of your position when they happen.

This page covers why registered mandate collections come back unpaid, how disputes work, and where registration does and does not protect you.

Why are registered mandate collections returned unpaid?

Common reasons a collection is returned include:

• Insufficient funds — the account did not hold enough money, and either tracking was not used or the tracking period expired without funds becoming available.
• Account issues — the account is closed, frozen or otherwise unable to accept debits.
• Mandate issues — the referenced mandate is suspended, cancelled or does not match the collection terms.
• Payer instructions — the payer has instructed their bank to stop or block the debit.

Banks report the reason with each return. Reason codes vary by bank and integration, so treat them generically in your processes and map your bank's specific codes during implementation. For handling strategies common to all debit orders, see Unpaids, Returns and Resubmissions.

Can a payer dispute a registered mandate collection?

Yes. Registration does not remove the payer's right to dispute. A payer who does not recognise or does not accept a debit can approach their bank, and the dispute is then handled between the payer, the banks and you as the collector.

What registration changes is the evidence. When a dispute is raised:

• The payer's bank holds the registered mandate details on record.
• The payer was notified when the mandate was registered, so they were aware of it before collections began.
• You hold the underlying signed or electronically accepted mandate.

Together, this makes a "I never authorised this" claim much harder to sustain than against a plain EFT debit order, where the bank has no record at all.

How does dispute protection compare across collection types?

The gap between RM and DebiCheck matters: because the payer never approved the registered mandate, a dispute cannot be answered with "the payer authenticated these exact terms". Your defence rests on the registered record plus the quality of your underlying mandate. See RM vs DebiCheck vs EFT for the full comparison.

What should you do when a dispute is raised?

1. Retrieve your evidence — the underlying mandate, proof of the payer's acceptance, the registration record and the collection history.
2. Respond within the required timeframe. Dispute processes run on deadlines; a strong mandate produced late is worth little.
3. Contact the payer. Many disputes are recognition or affordability problems that a conversation resolves faster than the formal process.
4. Check the mandate status afterwards. A dispute can result in the registered mandate being suspended or cancelled — do not keep collecting against it until the position is clear.
5. Track dispute rates. Persistent disputes on a segment of your book usually signal a sales, communication or affordability problem worth fixing at the source.

How do you keep returns and disputes low?

• Meet the minimum mandate requirements on every mandate, with clear amount and date terms.
• Use a statement name payers recognise.
• Tell payers at sign-up that their bank will notify them of the registration, so the notification confirms rather than surprises.
• Amend the registered mandate whenever contract terms change, so collections always match the bank-side record.
• Use tracking to convert insufficient-funds returns into successful collections.

Kwik reports returns and dispute outcomes against each registered mandate collection, so you can act on them quickly and keep your book healthy.

Related topics

• Registered Mandates hub
• Registered Mandate Collections, Tracking and Settlement
• Debit Order Disputes and Stop Payments
• DebiCheck Unpaids, Returns and Disputes