A practical guide to refund management in travel — why travel refunds are harder than other industries, customer-side discipline, supplier-side recovery, the regulatory floor under PTR/ATOL/EU261, refunds as chargeback prevention, and the audit trail behind every decision.
In most industries, a refund is a single decision: the merchant pays the customer back, the books are updated, the conversation ends. In travel, a single refund touches the customer, one or more suppliers, an acquiring bank, an ATOL or trust arrangement and a regulator - often all at the same time, often with different timing on each side.
The customer has paid for travel; the operator has paid suppliers for the components. A refund to the customer almost always has to be matched by a recovery from the supplier - and the supplier timeline rarely aligns with the customer deadline.
A booking made twelve months in advance can be refunded at any point in that window. Each refund moment carries different regulatory framing, different supplier exposure and different operational urgency.
Travel businesses with poor refund discipline produce chargeback waves. Customers who cannot get a refund through the operator go to their card issuer, and the operator pays the cost twice - the refund and the chargeback fees on top.
The customer side of a refund is mostly communication and timing discipline. Done well, the customer feels treated fairly even when the answer is no; done badly, the customer becomes a chargeback regardless of whether the operator was right.
Customers escalating to their card issuer almost always do so because the operator went silent or vague. A fast, specific response - even one that declines the refund - keeps the dispute inside the operator relationship rather than handing it to the bank.
A refund response that quotes a specific clause of a specific contract against a specific booking is much harder to chargeback than one that cites a generic policy. The customer is being shown that the operator knows their booking and is applying the right framework to it.
Refunding to a different rail than the original payment confuses the audit trail and is often a chargeback trigger. The discipline is to reverse the original payment rail wherever possible - card refund to the original card, A2A payment refunded by bank transfer to the customer's account, BACS reversal by BACS.
For every customer refund, there is usually a supplier the operator has already paid. The supplier-side recovery is where most refund losses actually happen, because suppliers operate on their own timelines and their own contractual frameworks.
Every supplier deposit attached to the booking it relates to, with the cancellation policy that supplier offers visible alongside.
Where a supplier refunds part of a deposit, the recovery should sit against the same booking that triggered it - so the net position per booking is always visible.
Supplier recoveries that drift past 30 days rarely recover at all. Early, written recovery requests against contractual terms are the discipline that works.
UK travel refunds sit inside the Package Travel Regulations, with overlays for ATOL holders, ABTA members and various scheme rules. The regulatory floor sets what the operator must do; commercial discretion sits above that.
For packages cancelled by the operator, PTR generally requires a refund within 14 days of cancellation. For unavoidable and extraordinary circumstances, the operator may not owe compensation, but the refund obligation usually stands. The 14-day clock is the rule that matters operationally.
For ATOL holders, the refund obligation is in the first instance the operator's. If the operator becomes insolvent, the ATOL trust (funded through APC contributions) picks up the customer side - which is why the trust evidence and APC reporting discipline matter so much during ordinary refund operations.
Whichever scheme the business operates under - ABTOT bond, CAA-approved trust account, or insurance-backed protection - the refund mechanics during normal operations remain the operator's responsibility, with the scheme providing the customer backstop in the event of operator failure. Day-to-day refunds still need to be evidenced cleanly so the scheme is not called on unnecessarily.
Most chargebacks against travel operators are refund disputes that the operator could have prevented. Treating refund operations as chargeback prevention reframes the work - and changes the economics of the team running it.
A chargeback typically carries a fee (£15-£25 from most acquirers), the original transaction amount and a quality-score hit on the merchant relationship. A clean refund costs only the refund.
At the margins - the £150 dispute, the £400 partial refund - a fast refund beats a slow win every time. The cost of a chargeback investigation often exceeds the disputed amount.
Operators with a "default to refund" culture for borderline cases run materially lower chargeback ratios than operators who fight every dispute. Lower chargeback ratios drive lower MDR at the next acquirer review.
Refund evidence has multiple audiences - the customer, the acquirer (if a chargeback follows), the auditor at year-end, the trustee on a review cycle. Building the evidence trail once, at the moment of the refund, means it serves all of them.
Every refund movement should reference the original payment it reverses - the transaction ID, the booking reference, the rail. That single chain is what defends a chargeback, satisfies an auditor and proves to the trustee that the trust account movement matched a real customer payment.
A refund record that just shows "issued £300" is brittle. A refund record that shows "issued £300, customer cancellation within free-cancel window per terms at time of sale, decided by [name] on [date]" defends itself. The decision evidence is what makes the trail audit-ready.
The net refund position per booking - customer refunded, supplier recovered, net to the operator - should be visible against the booking. Refund losses that hide across separate ledgers are exactly the kind of structural drain that finance teams discover at year-end audit.
felloh keeps every refund attached to the booking, the original payment and the supplier movement behind it - so the audit, regulator, trustee and chargeback responses share one evidence trail.
Every refund records the original transaction, the booking, the decision and the supplier-side movement against the booking that produced it.
See financial controlWhen a card chargeback lands, the refund record - and the evidence behind the refund decision - is already attached to the booking. Representment becomes a query, not an investigation.
See payment optimisationAuditors and trustees reviewing the operation see refund movements as connected events against bookings, not as orphan ledger entries that need explaining.
For ATOL holdersBring the workflow or rail you want to improve and we will show how felloh keeps the booking-level evidence connected end to end.
