Skip to content
Dhiti Services
← All articles
Travel operations6 min read

The refund queue: where travel companies quietly lose trust

How travel companies can track every refund from request to payout, keep clients informed and stop money and goodwill leaking out of the refund queue.

A travel operations specialist tracking refunds on a status dashboard and ticking off a checklist

A travel manager sends her third email in three weeks. Her company's sales team cancelled a trip to Singapore, and she is still waiting for the refund. Each time, the reply is polite and vague: it is being processed.

Inside the travel company, nobody is sure where it stands. Was the airline refund requested? Has it arrived? Was the hotel deposit refundable at all? The money might already be sitting in the bank account, unmatched, while the client gets more frustrated by the day.

Clients rarely remember how a booking went. They always remember how a refund went.

The good news is that a calm, reliable refund process is not complicated to build.

Why refunds matter more than ever

Expectations have shifted. Travellers and corporate clients now expect refunds to move as quickly as bookings do.

Regulators have pushed in the same direction. In the United States, Department of Transportation rules introduced in 2024 require airlines to refund cancelled or significantly changed flights automatically, within seven business days for card payments and 20 days for other methods. The details continue to be adjusted, but the direction is clear: slow refunds are no longer accepted as normal.

When an airline refunds quickly but the travel company passing it on does not, the client sees only one name on the delay. Yours.

Where refunds get stuck

A refund is not one task. It is a chain of small steps, and each one is a place where it can stall:

  • The request is never logged properly, so nobody owns it.
  • Eligibility is unclear: fare rules, hotel cancellation terms and supplier policies all differ.
  • The supplier claim is late or incomplete, missing a booking reference or document.
  • The money arrives unmatched, mixed in with other payments and impossible to trace.
  • The client payout waits for approval, because nobody knows the funds have landed.
  • Credits and vouchers are forgotten, and expire before anyone uses them.

Each step looks small. Together, they turn a two-week refund into a two-month complaint.

The real cost of a slow refund

The obvious cost is an unhappy client. The hidden costs are larger.

Money owed to clients sits on the balance sheet without a clear owner. Unmatched receipts make reconciliation harder at every month-end. Card-paying clients who run out of patience may dispute the charge with their bank, which adds fees and paperwork. And account managers spend their time chasing refunds instead of selling.

For corporate clients, a slow refund also becomes a renewal conversation. A travel manager who chased refunds all year will mention it when the contract comes up.

Build a refund pipeline, not a pile

The travel companies that handle refunds well treat them as a pipeline with clear stages. Every refund sits in exactly one stage, with an owner and a date:

1. Requested: the client's request is logged with the booking reference and reason.

2. Checked: fare rules and supplier terms confirm what can be refunded, and the client is told.

3. Claimed: the refund is submitted to the airline, hotel or other supplier.

4. Received: the supplier's payment is matched to the original booking.

5. Paid out: the client is refunded and receives a confirmation.

6. Closed: the records are reconciled and the case is archived.

A simple shared tracker is enough to begin. What matters is that nothing lives only in someone's inbox. Our guide to building a better exception queue shows how to keep stuck items visible until they are resolved.

Watch the ageing, not just the total

A list of open refunds tells you very little. How long each one has been open tells you almost everything.

Group open refunds into simple age bands, such as under 7 days, 8 to 30 days and over 30 days. Review the oldest band every week, one case at a time. Most of the long-running cases will share a cause: a supplier that never responds, a missing document, or money that arrived but was never matched.

As an illustration, a travel company with 200 open refunds might find that only 30 are older than a month, and that 20 of those are waiting on the same two suppliers. That turns an overwhelming backlog into two phone calls and a short list. It also tells you which supplier relationships need a firmer conversation, and which internal step keeps slowing things down.

Prepare for the surge

Refund volume is not steady. It spikes after weather disruption, schedule changes, strikes and the end of every peak season. If the process only works on quiet weeks, it will fail when it matters most.

Write the steps down so anyone trained can follow them. Our guide to writing an SOP someone can actually work from helps, and our article on peak season operations explains how to line up extra hands before the rush arrives.

Tell the client before they ask

Most refund complaints are not about speed alone. They are about silence.

Send a short update at each key stage: when the refund is confirmed, when it has been claimed and when it has been paid. For corporate clients, a simple monthly list of open refunds, with expected dates, is often welcomed by their finance teams too. Give a realistic timeframe, and say so early if a supplier is slower than usual. A client who knows what is happening is far more patient than one who has to ask.

Our customer support playbook covers how to set response standards so updates go out consistently, even when the team is busy.

Measure what clients feel

Track a few numbers every month:

  • Average days to refund: from request to client payout.
  • Refunds older than 30 days: the number and the value.
  • Unmatched supplier receipts: money received but not yet linked to a booking.
  • Refund-related complaints: how often clients have to chase.

Review them alongside your month-end close, because refunds and reconciliation affect each other every month.

Who should run the refund queue?

Deciding on exceptions, such as goodwill refunds for a key account, belongs with your management. The daily work is different: logging requests, checking fare rules, filing supplier claims, matching receipts and sending updates. That is careful, steady work that a trained back-office team can run every day, so refunds keep moving even when your front office is busy.

Dhiti supports corporate travel and hotel businesses with back-office operations, accounts and finance, reporting and sales support, with more than 200 trained specialists. If your refund queue keeps growing, we would be glad to help you clear it and keep it moving.

A note on this guide

Examples and suggested targets are illustrative, not Dhiti client results or contractual commitments. Adapt the approach to your process, risk and team.

A practical next step

Let’s make your everyday work run better.

Start with a conversation. Prove the fit with a pilot.

Discuss your process