Is a cancellation email proof that my travel refund arrived?

No. It proves the reservation was cancelled or a refund was promised. Check the original payment method or issued voucher for completion.

How should I record a flight that crosses time zones?

Keep departure and arrival in their stated local times with explicit time zones. You may add UTC for ordering, but do not replace the local values used at the airport.

Back to guides

Guides 8 min read

Published August 19, 2026

How to Build One Trip Itinerary from Confirmation Emails

A versioned itinerary method for reconciling provider references, local times, schedule changes, cancellations, and travel payments.

A single trip may have one airline record locator, a separate agency booking ID, several ticket numbers, a hotel confirmation, and later change notices that replace only part of the original itinerary. Filing all messages under a destination does not tell you which version is current.

Build the itinerary as a set of versioned reservations. Each segment keeps its provider reference, local date and time, time zone, traveler, status, and source message. Payments and refunds stay linked to the reservation but do not determine whether the itinerary itself is current.

Key takeaways

Use provider references and travelers to group reservations; destination alone is too broad.
Store departure and arrival in local time with explicit time zones.
Apply change notices to affected segments instead of replacing the whole trip blindly.
Verify the operational itinerary with each provider before travel.

Create a trip key, then add reservations

Name the trip with a broad date range and destination, but identify each reservation using its provider and reference. For air travel, retain the record locator and ticket number separately; an agency reference may not work on the carrier's site.

Add travelers to each reservation rather than assuming every booking covers the whole group. Two people on the same trip can have different tickets, rooms, or change histories.

newer_than:1y (itinerary OR "booking confirmation" OR reservation)
newer_than:1y "booking reference" "ABC123" for one reservation.
newer_than:1y (flight OR hotel OR rail OR rental) destination-name
newer_than:1y (changed OR cancelled OR refunded OR voucher) provider-name

Use a fixed schema for every segment

For each flight or rail segment, record service number, origin, destination, departure local time and zone, arrival local time and zone, traveler, seat when known, status, and source. For lodging, record property, local check-in and check-out dates, guest, room or rate reference, cancellation deadline, and source.

Never sort cross-zone segments by the displayed clock alone. Keep the source time zone and, when useful, a normalized UTC value for ordering. Do not convert the local time and then discard the original value travelers must follow.

Identity: provider, provider reference, agency reference, traveler.
Schedule: local date, local time, named time zone, origin, destination.
State: confirmed, changed, cancelled, completed, or unknown.
Provenance: source message and the time that version was received.

Apply revisions field by field

When a change message arrives, compare reference, traveler, service number, dates, route, and status with the current version. Update only the fields and segments the notice actually changes. A reissued outbound flight does not automatically change the return flight or hotel.

Keep the old version with a superseded marker and received timestamp. If two providers disagree, mark the field conflicting and verify directly instead of selecting whichever email arrived last.

1Match the notice to a reservation using provider references and traveler.
2Identify exactly which segment and fields changed.
3Mark the prior version superseded without deleting it.
4Verify conflicts and critical departure details with the operating provider.

Maintain a separate travel money ledger

A confirmed reservation, ticket issuance, payment, cancellation, voucher, and refund are different events. Give every charge its amount, currency, payment reference, and purpose, then link it to the relevant reservation or segment.

After cancellation, record whether the expected outcome is a refund, voucher, fee, or no refund under the stated terms. A cancellation confirmation closes the reservation state, not the financial state.

Base fare or room charge and its payment reference.
Taxes, seat, baggage, resort, rental, and change fees as separate rows.
Cancellation terms and the promised refund or voucher amount.
Posted refund, issued voucher, or unresolved outcome.

What Numero supports today

Numero can extract and organize authorized travel booking, payment, change, cancellation, and refund records into searchable Financial Memory. It remains a record of source-backed financial activity, not a replacement for a carrier, hotel, or live operations app.

Automatic travel cancellation-deadline and balance-due Moments are still planned. Verify live schedules and cancellation terms with the provider, and do not rely on Numero today for real-time disruption alerts or every travel deadline.

Explore Numero's travel booking tracker

See how Numero connects bookings, schedule changes, payments, cancellations, and refunds into one timeline.

Frequently asked questions

Keep the agency reference, carrier record locator, and ticket number separately. They identify different systems and may be needed for different support or check-in workflows.