How to track travel refunds, insurance claims and vouchers without double counting

Tidy Cents · Guide — How to track travel refunds, insurance claims and vouchers without double counting

To track travel refunds, insurance claims and vouchers without double counting, keep one ledger for the whole trip: one line per affected booking and per extra expense, one record per request, offer and payment, and an allocation of every confirmed payment to the line it actually covers. Requests and offers are never money received, a voucher counts at the value you can really use, and what is left open is simply each line's basis minus what was confirmed against it.

The steps below use fictional numbers you can replace with your own.

Map every booking

Begin with bookings. Record each airline, accommodation, rail, car or activity supplier separately with its paid amount, traveller and service date. A single trip can contain several contracts and several recovery paths.

A package booked through one agency is still a set of services: if the flight is cancelled but the hotel is used, those two parts end differently. Note the booking reference and the cancellation terms as written.

Keep extra expenses separate

Map the disruption to affected services. Keep the value of a cancelled service separate from additional meals, accommodation or transport. Extra expenses need their own dates, currency, receipt and explanation. Do not merge them into the ticket price.

For each affected booking, the lost-service basis is what you paid minus the value of the service you still received. A flight not flown at all has its full price as the basis; a hotel stay cut short by two of five nights has only the unused part. Extra expenses — a taxi home, meals while waiting, toiletries after a delayed bag — are separate lines with their own basis.

A request is not an offer, and an offer is not a payment

Create one request record per receiving party and loss basis. Store submitted date, entered deadline, requested amount and status. A request is not a recovery. An offer is also not a payment. If a 500 ticket receives 200 cash, the remaining service-loss basis is 300. A further 200 offer does not change confirmed recovery until accepted and paid under the chosen rules.

Keep three totals apart: what you asked for, what was offered and what you actually received. Adding them together makes a trip look recovered on paper while money is still missing.

Treat vouchers honestly

Treat vouchers honestly. A voucher with face value 300 may be worth only 180 to a traveller who can use it under its restrictions; retain both values. Expiry should remove current usable value only when the voucher actually expires, while history preserves what was offered.

The practical value is your own judgement of what the voucher is worth to you, so it can be lower than the face value but never higher. Record the expiry date and the restrictions next to it.

Allocate insurance and other recoveries

Allocate recoveries. An insurer payment cannot reimburse the same hotel line and flight line in full. Use a matrix that limits allocations to the confirmed payment and limits each loss line to its eligible basis. Keep compensation for inconvenience separate from reimbursement of expenses so that legitimate different payments are not falsely marked duplicates.

If a policy has a limit and a deductible, the most a request to that insurer can produce is the requested amount capped at the limit, minus the deductible — as you read it in your policy. If you do not know the limit, the honest answer is "unknown", not zero and not the full amount.

Preserve currencies and entered deadlines

Preserve currencies. A supplier may refund the original foreign amount while the base-currency value differs because the rate changed. Show the FX difference instead of automatically claiming the supplier underpaid. Deadlines also depend on entered rules; do not apply one jurisdiction globally.

A deadline is the event date plus the window you were given. Count calendar days unless the rule you were given says business days; then skip weekends and the holidays you enter yourself.

Worked example in one trip ledger

The fictional cancelled-trip demo uses a USD base. Three bookings were paid: a flight of 500, a hotel of 360 and a rail ticket of 80 — 940 in total. After the cancellation the traveller also paid 45 for meals and 38 for a taxi, so the claim basis is 940 + 83 = 1,023.

  • The airline refunded 200 in cash. The flight line still has 500 − 200 = 300 open.
  • The airline also offered another 200 in cash and a voucher with face value 300 and a practical value of 180. Neither has been accepted, so the open offers total 380 and confirmed recovery does not move.
  • The hotel refunded the full 360, so that line is closed.
  • Rail (80) and the two extra expenses (83) are still open.

Confirmed received is 200 + 360 = 560. Remaining is 300 + 80 + 45 + 38 = 463. Requested is 1,023, but that is a request, not money.

The delayed-baggage demo shows the second rule. The airline paid 100 as compensation for the inconvenience and 80 as reimbursement of receipts; the insurer reimbursed 120 against the clothes line. The policy limit entered is 200 with no deductible, so the insurer request of 250 can produce at most 200. The card benefit has no entered limit, so its potential is unknown. Of the 250 of extra expenses, 50 is still open, and the 100 of compensation is shown on its own, not as a duplicate of the reimbursement.

The vouchers demo shows currency. A flight of 500 EUR was booked at 1.10 (550 USD). The airline refunded the full 500 EUR, converted at 1.05 on the payment date (525 USD). The flight line is fully recovered in euros — nothing is open — and the 25 USD gap is an FX difference, not an underpayment.

Checklist before you send or chase anything

  • Every booking has its own record: supplier, reference, traveller, date, currency, amount.
  • Each affected booking has a loss line; each extra expense has its own line with a receipt note.
  • One request per party and basis, with the submitted date and the deadline you were given.
  • Offers stay offers until you accept them; cash offers count only when the money arrives.
  • Vouchers carry both face and practical value, an expiry date and their restrictions.
  • Every confirmed payment is allocated, no allocation exceeds the payment, and no line is recovered above its basis.
  • Compensation is recorded as compensation, not as reimbursement of a line.
  • Foreign payments keep their own currency and the rate on the day you received them.
  • A reversed payment or an expired voucher is marked as such, so the open amount comes back.

What this does not decide

A ledger organises evidence, deadlines and arithmetic. It does not tell you which rights apply to your journey, which law governs a booking, what an insurer will accept or how long a supplier really has to answer. Those depend on the contract, the policy wording and the rules where you travelled. Enter the basis, windows and limits you have read or been told, and check them yourself or with someone qualified when a large amount is at stake.

Travel Refund & Disruption Desk combines bookings, evidence, requests, offers, vouchers, insurance and confirmed recovery in one trip ledger. It does not submit claims, contact suppliers or negotiate. No AI guesses. Every result shows its working. Open the fictional cancelled-trip demo to see how 500 paid, 200 refunded, an unaccepted offer and a restricted voucher remain distinct.

Related reading: How to create a home inventory for an insurance claim.

Explore the fictional demo · See the full tool

Tools mentioned in this guide

More guides