Skip to content

Privacy and preparation

Travel refund fare rule dataset: keep the rule that applied at purchase

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Snapshot the fare rules when the fare is priced and ticketed, key them to each segment's fare basis, and judge later refund requests against that snapshot rather than today's rules. A travel refund fare rule dataset then labels events that override the fare rule, such as a significant schedule change, links hotels and other dependent bookings with their own deadlines, and proves each outcome with a settlement record.

License terms

Travel refund fare rule

This page covers travel refund fare rule dataset: keep the rule that applied at purchase.Illustrative

Key takeaways

  • Refunds are decided under the rule attached to the ticketed fare, so store a dated rule snapshot, not a link to the current rule table.
  • Keep empty rule categories: under ATPCO's structure, missing refund data can mean unrestricted, not nonrefundable.
  • Label carrier cancellations and significant changes separately; they can create refund rights the fare rule never granted.
  • Store hotel deadlines in the property's local time with its offset and compare in the same zone.
  • Prove outcomes with settlement records and timestamps, not a status field or the agent's reply.

How should a travel task preserve the fare rules that applied at purchase?

Capture the fare rules as a dated snapshot when the fare is priced and ticketed, key the snapshot to each segment's fare basis, and judge every later refund or change request against that snapshot, not against the rules the airline files today. Then layer on the events that override fare rules, such as a carrier cancellation or significant schedule change, because those can create a refund right the fare rule never granted.

A travel refund fare rule dataset built this way lets a model learn the real decision: which rule governed, which event, if any, overrode it, and what the records show happened to the traveler's money and reservation. A dataset that stores only the request, the agent's reply and a status field teaches the model to sound right, which is not the same as being right.

This page focuses on that dating and linkage problem. For the broader shape of servicing records, see the related pages linked below.

Why does the rule at purchase, not today's rule, decide the refund?

Because the traveler bought a fare with specific conditions, and airlines revise their filed rules over time. A refund request three months after purchase is decided under the rules attached to the ticketed fare, so a dataset that joins requests to the current rule table will mislabel every case where the rule changed in between.

The rule structure makes dating essential. ATPCO describes Category 31 as defining when voluntary changes are permitted and what they cost, and Category 33 as doing the same for voluntary refunds; in both, when no data or no matching provision exists, the change or refund is permitted with no charge and no restriction for that fare. ATPCO describes Category 16 penalties as display text for manual processing. So a missing Category 33 record does not mean nonrefundable, and a snapshot that drops empty categories silently flips the answer.

Booking APIs expose the fields to snapshot. In the Amadeus Flight Offers Price specification, fare details are given per segment with a fare basis, described as specifying the rules of a fare, and a branded fare name; a detailed-fare-rules option returns terms and conditions by category (REFUND, EXCHANGE, REVALIDATION, REISSUE, REBOOK, CANCELLATION) with a notApplicable flag and descriptive text. Store all of it with the pricing timestamp.

Which events override the fare rule entirely?

Some events give the traveler a refund right regardless of what the fare rule says, and the dataset must label them separately or a model will learn to deny refunds that were owed. The table summarizes the main ones from official sources; it is a labeling guide, not a statement of anyone's legal obligations.

Which events override the fare rule entirely?
EventWhat governs (per the cited source)Evidence to linkDataset label
Traveler cancels voluntarilyThe purchase-time fare rule (for example ATPCO Category 33 where filed)Rule snapshot, request timestamp, fare basis per segmentvoluntary_refund
Cancellation within 24 hours of a U.S. booking made a week or more before departureDOT 24-hour requirement: the carrier either holds the fare without payment or allows cancellation without penaltyBooking and ticketing timestamps, departure date, which option the carrier offers24h_window
Carrier cancels or significantly changes a U.S. flight and the traveler declines alternativesDOT refund rules: refund owed; significant change includes large time shifts (over 3 hours domestic, 6 hours international), airport changes and added connectionsSchedule change event with original and new times and airports, traveler's responseinvoluntary_refund_us
Cancellation of a flight covered by EU Regulation 261/2004Article 8: reimbursement within seven days of the full cost of the ticket at the price at which it was bought, among the options offeredCancellation event, flight scope under the regulation, choice offeredinvoluntary_refund_eu
Carrier waiver during disruptionThe waiver's own text and datesWaiver identifier and text snapshot, eligibility dateswaiver_applied

The dated rule and booking evidence linkage example

The asset is a linkage example: one record per artifact, each carrying the timestamp that matters and the keys that join it to the rest. Real records are referenced by tokens; the example values in the next section are illustrative. Use it as a column map for the export and as the check an annotator runs before accepting a case.

Two rules keep the map honest. First, every decision points to exactly one rule snapshot or one override event, never to a rule table by name. Second, a record created after the decision can be an outcome but never evidence for the decision; if a later rule revision or a later schedule change is linked as the reason, the case is mislabeled.

The dated rule and booking evidence linkage example
RecordFields to keepTimestamp that mattersLinks to
Priced offerFare basis and booking class per segment, branded fare, fare component boundariesPricing timeRule snapshot, ticket
Rule snapshotCategory records or terms and conditions as returned, including empty categories and notApplicable flags; a content hashCapture time, at or before ticketingPriced offer, every later decision
Ticket or orderTokenized ticket and order IDs, issue date, coupons per segment, form-of-payment type (not the card)Issue timeRule snapshot, refund record
Schedule change or cancellation eventOriginal and new times and airports, connection count, cabin, change sourceEvent time and notification timeTicket, involuntary label
Traveler requestChannel, stated reason, segments affected, request text or transcriptRequest time and hours to departureTicket, decision
Dependent bookingsHotel or ground reservations with their own cancellation deadline and policyDeadline in the property's local timeRequest, decision
DecisionRefund, credit, change, denial or referral; the rule or event cited; approver if anyDecision timeRule snapshot or event, outcome
OutcomeRefund issued and method, coupon status after action, credit created, recontactSettlement timeDecision, ticket

Worked case (illustrative): a nonrefundable fare, a later rule change and a schedule change

Everything in this case is invented to show the linkage; it describes no real traveler, airline or agency, and the counts and durations are illustrative. A traveler books a two-segment domestic round trip and a two-night hotel stay through an agency, 40 days before departure. The fare basis on both segments is a basic nonrefundable fare; the rule snapshot captured at ticketing shows the refund category as not permitted, with credit for a change fee.

Twelve days later the airline revises its rules for that fare family to allow refunds less a fee on new tickets. On day 30 the traveler asks to cancel everything. A model that reads the current rule table approves a refund. The correct decision, from the snapshot, is a credit under the change terms, not a refund. The hotel's free cancellation deadline, 48 hours before arrival in the hotel's local time, has not passed, so the hotel cancels without penalty.

The counterexample changes one fact. Five days before departure the airline moves the outbound flight by 4 hours and the traveler declines the new time. That is a significant change for a domestic flight under DOT's definition, so a refund is owed despite the nonrefundable fare, and the label becomes involuntary_refund_us.

  • Starting state: ticket issued on day 0 with rule snapshot hash recorded; hotel booked the same day with its cancellation deadline stored in local time.
  • Rule event: carrier rule revision on day 12, stored as a new snapshot that applies only to tickets issued after it.
  • Request: day 30, cancel all; decision under the day-0 snapshot is a credit; hotel canceled inside its deadline.
  • Counterexample: schedule change of 4 hours notified on day 35; traveler declines; refund to the original form of payment; label involuntary_refund_us.
  • Outcome check: refund or credit record, coupon status, hotel cancellation confirmation, and no recontact within the agency's follow-up window.

Which dependent booking, deadline or approval limits the change?

Treat the itinerary as a set of linked bookings, because one component's rule or deadline often limits what can be done with another. A fare component that spans both segments of a round trip may not allow refunding one direction alone; a hotel or tour attached to the trip has its own deadline; and a corporate booking may need an approver before any change.

At a glance

Which dependent booking, deadline or approval limits the change

Hotel deadlines need careful time handling. The Amadeus Hotel Search specification describes a cancellation policy deadline as the time after which the penalty applies, expressed in the hotel's local time zone with the time zone difference added, and gives the penalty as an amount, a number of nights or a percentage. Store the deadline exactly as returned and compare it with the request time in the same zone; converting to the agency's zone without the offset produces cases that look late when they were on time.

Intermediaries add a timing link. DOT's small business compliance guidance for its refund rule says the merchant of record issues the refund, and a ticket agent's deadline runs from the airline's confirmation that a refund is due, even before the agent has the funds. Record which party sold the ticket and when the airline confirmed the refund.

  • Fare component scope: which segments share a fare basis and rule snapshot.
  • Dependent bookings: every hotel, car or tour tied to the trip, each with its own deadline and penalty form.
  • Approvals: corporate travel policy or supervisor approvals with approver role and time.
  • Merchant of record: airline or agency, plus the time the airline confirmed any refund to the agency.

Which linked record proves the refund actually happened?

A status field that says refunded is not proof. The outcome needs a settlement record: the refund or credit actually created, its method, the date, and the ticket coupons' status after the action. Without it, a case where the agent promised a refund that was never processed looks identical to one that was handled correctly.

DOT's consumer guidance says refunds owed for a canceled or significantly changed flight are to be automatic and made to the original form of payment, within seven business days for credit card purchases and 20 calendar days for other payment methods. Those deadlines make settlement timestamps useful labels in their own right: a case settled outside them is a servicing failure even if the decision was correct.

  • Decision correct and settled within the applicable window: positive example.
  • Decision correct, settlement late or missing: label as a process failure, not a decision failure.
  • Decision wrong under the snapshot or override event: negative example, whatever the traveler's reaction.
  • Traveler recontacts about the same booking within the follow-up window: review the case before labeling it resolved.

What must be removed or reviewed before booking records are licensed?

Booking records hold names, contact details, travel document numbers and payment references, so remove travel documents and payment card data entirely and tokenize travelers, record locators and tickets consistently across every table. Free-text transcripts need their own scrub, because travelers read out confirmation codes and card digits.

Fare and schedule content an agency received through a global distribution system or an airline connection can be governed by distribution agreements, and filed fare rules come from the airlines. Holding a copy of a rule does not mean you may license it, and a privacy permission is not a licensing right. Counsel should review distribution and supplier agreements before rule text or fare basis codes leave the company. Nothing here is legal advice on refund obligations.

Licensing servicing histories with SourceX

Agencies and travel operators whose servicing histories keep the rule snapshot, the event and the settlement together can license selected records through SourceX, which manages the rights review, contracting, preparation and delivery. No booking record is handed over until the agency or operator approves scope and terms and signs. Buyers usually want a few years of consistent history in one system, though uncommon case types can qualify with less. Eligibility is checked through a short assessment, without any booking data being uploaded.

Frequently asked questions

Is a fare basis code enough to reconstruct the refund rule later?

No. The fare basis identifies the fare, but the rules attached to it can be revised. Store the rule text or category records returned at pricing or ticketing, with a capture timestamp and a hash, so later decisions can be checked against what applied at purchase.

Does a missing refund category mean the ticket is nonrefundable?

Not necessarily. ATPCO describes Category 33 as permitting a refund with no charge and no restriction when no voluntary refund data or matching provision exists. Keep empty categories in the snapshot instead of dropping them, and have a fare expert confirm how your source represents them.

How should schedule-change refunds be labeled?

Separately from voluntary refunds, with the event record attached: original and new times, airports and connections, and the traveler's response. Under DOT's definition, a significant change can create a refund right that the fare rule does not, so mixing the two teaches a model to deny refunds that were owed.

Should hotel and car bookings be part of the same task?

Yes, when they were booked as part of the trip, because their deadlines limit the valid action. Store each deadline in the property's local time with its offset and compare it with the request time in the same zone.

What proves the task outcome?

A settlement record: the refund or credit created, its method and date, and the coupon status after the action. A status field or the agent's closing message is not enough; promised but unprocessed refunds look identical without settlement data.

Sources

  • ATPCO describes Category 31 and Category 33 as defining voluntary change and refund conditions, permitted without charge or restriction when no data or matching provision exists, and Category 16 as display text. Source
  • The Amadeus Flight Offers Price specification gives fare basis and branded fare per segment and returns detailed fare rules by category with a notApplicable flag. Source
  • The Amadeus Hotel Search specification describes a cancellation deadline after which the penalty applies, expressed in the hotel's local time with the time zone difference. Source
  • DOT's refund guidance says a refund is owed when an airline cancels or significantly changes a flight and the consumer declines alternatives, defines significant change, and sets refund timing. Source
  • DOT's 24-hour reservation guidance requires carriers to hold a fare without payment or allow cancellation without penalty for 24 hours on bookings made a week or more before departure. Source
  • EU Regulation 261/2004 Article 8 provides reimbursement within seven days of the full cost of the ticket at the price at which it was bought. Source
  • DOT's refund rule compliance guidance says the merchant of record issues the refund and a ticket agent's refund deadline runs from the airline's confirmation that a refund is due. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies