Why Do DebiCheck Collections Get Returned or Disputed?

Even with an authenticated mandate, DebiCheck collections can still come back unpaid — most commonly because the account simply does not have the funds. What DebiCheck changes fundamentally is the dispute picture: because the consumer's bank holds an electronic copy of the approved mandate, collections that match the mandate cannot be unfairly disputed and reversed the way ordinary debit orders can.

This page separates the two concepts — unpaids (the money was never collected) and disputes (the payer challenges a collection) — and explains how to handle each.

Why do DebiCheck collections come back unpaid?

Common unpaid and rejection reasons include:

• Insufficient funds — the most frequent reason; the account could not cover the collection, and any tracking window closed without funds arriving.
• Account closed, dormant or frozen — the account can no longer be debited; new account details are needed.
• Payment stopped — the payer instructed their bank to stop the payment.
• Mandate suspended or cancelled — the payer acted on the mandate at their bank, blocking collections.
• Mandate mismatch — the collection did not match the registered mandate's amount, frequency or timing, and was rejected before reaching the account.

Each failure carries a reason code that tells you whether to retry, track, amend the mandate or contact the payer — see statuses and reason codes and collections, tracking and retries.

How do disputes work on DebiCheck collections?

With ordinary EFT debit orders, a payer can dispute a debit at their bank and often have it reversed, even when the underlying mandate was valid. DebiCheck was designed specifically to close this gap:

• The bank verified the collection against the mandate the consumer personally authenticated, so a matching collection is treated as authorised.
• As a result, not all DebiCheck transactions can be reversed on dispute. A payer cannot simply claim the debit was unauthorised when their own bank holds their electronic approval.

Consumers who believe a DebiCheck debit is wrong should first approach the service provider to resolve the issue, and then their bank if it cannot be resolved. This ordering matters: most issues (a contract already cancelled, an amount queried) are contractual questions that the service provider can fix directly, often faster than a formal dispute.

What can a payer still do at their bank?

A payer who wants to stop DebiCheck collections can suspend the mandate at their bank. This blocks all future collections, and the service provider is notified at the time of suspension so it can engage the payer. Two important caveats for consumers:

• Suspension does not reverse past collections.
• Suspension does not cancel the underlying contract — the agreement must be cancelled with the service provider, and amounts owed remain owing.

For the broader dispute landscape across debit order types, see debit order disputes and stop payments.

Unpaids vs disputes at a glance

How should businesses manage unpaids and disputes?

• Use tracking windows to convert insufficient-funds failures into successful collections.
• Keep mandate data accurate so collections never fail on a mismatch.
• Respond quickly to suspension notifications — early contact usually resolves the payer's concern.
• Keep clean records of contracts and mandates; in the rare dispute that does proceed, the authenticated mandate is your evidence.

Kwik handles unpaid processing, tracking and suspension notifications as part of its DebiCheck collections service, surfacing exceptions with clear next actions.

Related topics

• DebiCheck hub
• Collections, tracking and retries
• Statuses and reason codes
• Debit order disputes and stop payments