How are refunds and chargebacks matched when they arrive days later?
They are matched as related movements. A refund or chargeback appears in a settlement file days after the original payment, often with a different reference. Automated matching pairs it with the transaction it belongs to, using references, amounts and dates. Anything that cannot be paired becomes an exception with the context the finance team needs to resolve it.
In detail
They are matched as related movements. A refund or chargeback appears in a settlement file days after the original payment, often with a different reference. Automated matching pairs it with the transaction it belongs to, using references, amounts and dates. Anything that cannot be paired becomes an exception with the context the finance team needs to resolve it.
Related movements
A refund or a chargeback is a new money movement linked to an old transaction. It appears in a settlement file days or weeks after the original payment, often with its own reference and sometimes with a different amount, for partial refunds or chargebacks with fees. Matching it means finding the original transaction and attaching the movement to it.
How matching works
- By reference: the provider's transaction identifier or acquirer reference number, when the file carries it.
- By amount and date: the refund amount against the original, within a window.
- By card data: the last four digits and expiry, as a last resort.
Exceptions
A movement that cannot be paired becomes an exception, presented with its context: the file it came from, the candidate transactions, the amount difference. The finance team resolves it, and the decision is logged. Over time, exception rates per provider show which settlement files lack references, which is a conversation to have with that provider. The result is a transaction record that holds the payment, its refunds, its chargeback and the related fees, so a merchant statement can be explained line by line.