Returns Under the Microscope: Building a Refund-Liability File That Satisfies Offshore Acquirers

When a UK merchant approaches an offshore acquirer, the onboarding pack is often heavy on fraud controls and chargeback evidence. That is understandable: disputed transactions are the risk everyone talks about. But the acquirer is also asking a quieter question — what happens when customers send goods back? Refund liability can be large, seasonal and cash-intensive. If it is not measured, it looks uncontrolled. A well-built refund-liability file reframes returns as a bounded operational exposure rather than an open-ended guess.

Why refund exposure sits alongside fraud in acquirer models

Chargebacks and refunds are different animals. A chargeback is a disputed transaction that may be reversed through card scheme rules. A refund is a contractual or statutory outflow that the merchant chooses or is obliged to make. Both affect cash flow after settlement, and both can justify a reserve. An offshore acquirer, with less local visibility than a UK high-street bank, relies on evidence. If a merchant cannot quantify refunds, the acquirer will assume a worst case. That assumption usually appears as a larger holdback, a longer reserve period or a more cautious onboarding decision.

The commercial point is simple: refunds are not a customer-service footnote. They are a liability on the balance sheet and a timing risk in the settlement account. Treating them that way is the first step to a credible pack.

Start with the policy, but make it operational

A written refund policy is the baseline. The acquirer will want to see more than a webpage. It will want evidence that the policy is applied consistently. That means a documented process: how a return is authorised, how goods are received and inspected, who triggers the refund, how the refund is paid and how exceptions are approved.

For UK distance sales, the Consumer Contracts Regulations 2013 give consumers a 14-day cancellation right in most cases, with refunds due within 14 days of the trader receiving the goods or evidence of return. A merchant’s own policy may be more generous. Both need to be visible. Show the customer-facing wording, the version date and the internal controls that stop refunds being discretionary favours. If the business sells to consumers and businesses, separate the policies. If it sells cross-border, note where local rules differ and how the process adapts.

The ratios that matter: refunds as a percentage of sales, not a footnote

Acquirers think in ratios and trends. Pull 24 to 36 months of data and calculate refund value as a percentage of gross sales value, refund count as a percentage of order count, average refund value, and the time from return receipt to refund. Add an outstanding refund liability figure at each period end — the value of returns received but not yet refunded, plus expected refunds on goods still in transit.

Segment the numbers by product line, sales channel, customer type and destination. A stable ratio is evidence of control. A volatile ratio is not automatically a problem, but it needs an explanation: a product recall, a change in returns window, a shift in customer mix. Reconcile refund totals to processor settlements and bank receipts. Acquirers warm to reconciliation because it shows the numbers are not cherry-picked.

Fulfilment proof: the link between delivery and refunds

A refund file without fulfilment evidence is incomplete. The acquirer wants to know that goods were delivered and that returns are genuine. Provide delivery confirmation rates, carrier tracking data, proof-of-delivery capture for higher-value items, dispatch logs and, for services or digital goods, access or usage records. If the merchant refunds without requiring the goods back — common for low-value items — state that policy clearly and show the fraud checks around it.

This evidence supports a simple narrative: refunds are triggered by customer returns, not by weak fulfilment or unchecked discretion. That distinction matters when an acquirer is deciding whether a high refund ratio reflects a generous policy or a broken operation.

Seasonal spikes: modelling the Christmas and January effect

UK retail has a pronounced returns season. Black Friday, Christmas gifting and January sales create a refund tail that can run well into the new year. An acquirer reviewing a merchant in November 2026 will want to know how the business handled previous peaks and how it will fund the next one. Provide prior peak data: refund volumes in December and January relative to the annual average, staffing levels, carrier cut-off dates and stock availability. Explain any extended festive returns policy and separate the statutory element from the voluntary element.

Then show a stress test. Model a base case and a stressed case — for example, a 25 per cent increase in returns — and show how the liability would be funded. That might be a reserve, a credit facility, a cash buffer or a combination. The acquirer is not expecting returns to disappear. It is testing whether the merchant has measured them.

Building the pack: a practical sequence

A useful refund-liability pack can be assembled in a defined order. First, pull refund data from the payment gateway, processor reports and accounting system. Second, reconcile refunds to orders and settlements. Third, write a one-page policy summary with the relevant legal references and version control. Fourth, build a monthly ratio table and chart. Fifth, add fulfilment proof metrics. Sixth, add seasonal analysis and a stress scenario. Seventh, include a process map and control description: who approves refunds, what limits apply, what fraud checks run. Eighth, add a short narrative explaining changes in product mix or customer behaviour. Ninth, have a finance director or equivalent sign it off. Tenth, diarise a quarterly update.

The pack should be plain, indexed and consistent. Acquirers read many files; a clear contents page and a one-page summary of the key ratios will do more than a glossy brochure.

Using the pack in onboarding and reserve talks

At onboarding, submit the refund-liability pack alongside the KYC file and chargeback evidence. At reserve renegotiation, lead with the current liability and the trend. If the acquirer proposes a larger reserve than the merchant expects, the pack can support a counter-argument: stable ratios, strong fulfilment evidence and a funded peak plan. It can also support a release schedule tied to the refund tail rather than an arbitrary date.

Be honest about gaps. If historical data is incomplete, say so and explain the remediation. An acquirer will trust a measured uncertainty more than a claim that refunds are immaterial. The objective is not to prove that returns never happen. It is to show that they are understood, monitored and funded.

Refund liability deserves the same discipline as fraud and chargebacks. For UK merchants trading across borders, a documented refund file is not just an onboarding artefact. It is a working tool for treasury, operations and acquirer relationships — and a credible answer to the question many merchants forget to prepare for.