Direct Debit indemnity claims: what merchants should do when a payer gets a Guarantee refund

When a payer claims that a Direct Debit was collected incorrectly, their bank can refund them under the Direct Debit Guarantee. The merchant or service user can then see the amount recovered through the Direct Debit system. A Guarantee refund does not automatically prove that the underlying customer never owed the money.

The Guarantee protects errors in setup or collection

Direct Debit guidance says the payer is entitled to a full and immediate refund from their bank if an error is made in setting up or collecting a Direct Debit, for example the wrong amount or date. The payer goes to their bank, not directly to the merchant, for the Guarantee refund.

The merchant should therefore expect a scheme-level debit after a successful historical collection where the payer's bank accepts an indemnity claim.

A Guarantee refund does not automatically cancel the commercial debt

Direct Debit guidance is clear that the Guarantee covers payment errors, not ordinary disputes about goods or services. If the customer receives a refund but still contractually owes the merchant, the merchant can pursue the underlying debt through the appropriate customer process.

Do not simply re-collect by Direct Debit without checking whether authority remains and whether the original collection problem has been corrected. The payment and the commercial contract are separate issues.

Keep mandate, advance notice and collection history

A service user should be able to show when the mandate was created, what advance notice was sent, the amount and collection date, any amendments and cancellation status. These records help the merchant understand whether the refund appears valid.

If the merchant believes a claim was made incorrectly, follow its sponsoring bank or Direct Debit provider's challenge process and provide the requested evidence. Do not argue directly with the customer's bank without using the scheme route.

Investigate patterns rather than one claim at a time

Several indemnity claims with the same reason can indicate a merchant error in billing dates, mandate migration or customer communication. Review the affected billing batch and system changes.

High claim levels can also affect the merchant's relationship with its sponsoring bank. Direct Debit access relies on the service user meeting scheme and sponsor standards, so operational quality matters beyond the value of individual refunds.

Contact the customer about the service balance, not to pressure them over the bank refund

If money remains legitimately owed, send a normal invoice or account statement explaining the balance and why. Offer another payment method or a corrected Direct Debit where appropriate.

Do not tell the customer they were not allowed to use the Guarantee merely because the merchant disagrees. Handle any challenge through the bank or provider and handle the commercial debt through ordinary credit control.

Separate indemnity debits from refunds issued by the merchant

A Direct Debit indemnity claim is not the same accounting event as a voluntary merchant refund. Identify the original invoice and collection, record the scheme debit and reopen the receivable if the customer still owes money under the contract.

Track claim amount, date, reason and outcome. This gives management a view of Guarantee exposure and prevents chargebacks, card refunds and Direct Debit indemnities from being mixed into one generic "refunds" account.

Maintain a DDIC register with original collection date, claim date, reason, amount, customer, evidence status and commercial debt outcome. This lets finance see whether claims are isolated or concentrated around one billing migration or operational change.

Worked example: a customer receives a £900 Guarantee refund because the merchant collected on the wrong date. The merchant should correct the process first. If the £900 service charge is still contractually due, it can invoice the customer or agree a new authorised collection, but it should not simply re-present the same debit without fixing the notice failure.

Challenge only claims the evidence genuinely supports. A service user that disputes every indemnity regardless of facts wastes sponsor-bank time and can weaken confidence in its controls. Good records make selective, evidence-based challenges possible.

Set a materiality threshold for management review. A £20 claim can follow the normal operational route, while a £20,000 claim from a major B2B customer should trigger immediate review of mandate, contract, notice and account status. Large claims can create settlement and liquidity pressure as well as a customer dispute.

Where the customer relationship continues, consider changing the collection model after a disputed claim. A variable or complex invoice might be better suited to bank transfer or Request to Pay if repeated Direct Debit misunderstandings are damaging trust. Payment method should support the commercial relationship rather than create recurring disputes.