AI uses for records
Travel supplier settlement data: how a dispute becomes a graded task
By SourceX Editorial · Reviewed by Noah Loul ·
8 sections
Short answer
A travel supplier settlement dispute becomes a traceable reasoning task when you package one disputed invoice line, memo or statement entry with the booking scope, the rule in force at purchase, dependent bookings, the change timeline, the decision and a later record proving the outcome, such as a credit note. A grader can then check the decision against evidence, not against a status field.
Agent run
Travel supplier settlement
Key takeaways
- Settlement disputes are about which version of a booking counts, which makes them strong reasoning tasks.
- The rule in force when the booking was sold, not today's policy, decides most disputes.
- Dependent bookings and disruptions explain why billed and delivered versions differ, but rarely decide the billing alone.
- Prove outcomes with credit notes, settled memos or corrected invoices, never with a dispute status.
- Every record enters the packet only after a documented permission check covering agreements and traveler data.
How does a supplier settlement dispute become a traceable reasoning task?
A settlement dispute becomes a reasoning task when you freeze the starting state, attach the rule that applied when the booking was bought, link every dependent booking and record the decision together with the record that proves how it ended. The task is then: given these records, should this invoice line, debit memo or adjustment be accepted, disputed or corrected, and why?
Travel settlement is a good source of these tasks because the disagreement is rarely about arithmetic. It is about which version of a booking counts. A hotel invoice line reflects the reservation the distributor holds, the property's folio reflects what the guest actually stayed and paid for, and a flight cancellation or rebooking in between explains why the two drifted apart.
Travel supplier settlement data, for this article, means the records that reconcile what a supplier (a hotel, airline or other travel provider) and a seller or distributor (an agency, online travel agency or travel management company) owe each other: invoices, statements, debit and credit memos, dispute entries and the booking records behind them. The packet below turns one disputed line into one gradable task.
The test of a good packet is simple. A reviewer who has never seen the case should be able to read the starting records, apply the stated rule and reach the same decision, then check that decision against an outcome record rather than against a status label.
Where travel settlement disputes leave records
Most disputes come from a handful of settlement channels, and each leaves its own trail. Knowing which channel a dispute came through tells you which records exist and which deadline governed it.
For air tickets sold by accredited agents outside the United States, IATA describes its Billing and Settlement Plan as a system that simplifies selling, reporting and remitting for accredited agents, with the agent making one net remittance across participating airlines. In the United States, ARC runs Interactive Agent Reporting, which ARC says handles reporting and settlement of sales, refunds, exchanges and memos and provides back-office data files that agencies use for reconciliation.
Airline audits reach agencies as agency debit memos. IATA's BSP manual for agents describes a latency period after an ADM is issued, configured by each BSP and up to 15 days, during which the agent can register a dispute in BSPlink, and IATA Resolution 850m says the airline should settle a dispute within 60 days of receiving it. ARC's 2023 debit memo best practices recommend that agencies dispute within 30 calendar days of issuance and that airlines respond within 30 calendar days of a dispute. Market rules and airline policies vary, so the packet records the rule version that actually applied rather than assuming one.
Hotels meet the same problem from the other side. Booking.com's partner help describes a reservation statement that lists the reservations on an issued invoice and lets a property dispute the commission on individual reservations, and its dispute page says an approved dispute produces a credit note while a rejected one leaves the invoice payable in full. Other distributors, wholesalers and travel management companies have their own statement formats; the packet does not depend on any one of them.
| Channel | Typical dispute | Records it leaves | Where the outcome shows |
|---|---|---|---|
| Airline to agency debit memo (BSP or ARC) | Fare, waiver or ticketing rule not followed on issue or exchange | Memo with reason, ticket and exchange history, fare rule, waiver code, dispute text | Memo status plus the settled or reversed amount in a later billing or sales report |
| Distributor invoice to hotel | Stay shortened, no-show or cancellation not reflected before invoicing | Invoice line, reservation statement entry, property folio, cancellation policy | Credit note or unchanged invoice paid in full |
| Hotel invoice to agency or company | Rate, room nights or incidentals billed differently from the booking | Booking confirmation, negotiated rate record, folio, invoice, correspondence | Corrected invoice, credit or written acceptance |
| Wholesaler or bed bank statement | Allotment, release or rate-load mismatch | Rate load history, allotment release log, statement line | Adjusted statement in a later period |
| Agency back office reconciliation | Settlement report and agency ledger disagree | Settlement file, back-office ledger, ticket record, memo record | Matched or written-off entry with reviewer note |
What the permitted invoice, booking and dispute evidence packet should include
The packet should hold one disputed line and everything needed to judge it, and nothing a reviewer would have to take on trust. Each field group below names the record it comes from, so a team can fill it from its own systems and leave a group empty only when the record genuinely does not exist.
The word permitted matters. Each record goes into the packet only after someone confirms the company may use it for this purpose: distributor agreements often treat statements and rate terms as confidential, traveler names and contact details are personal data, and payment card numbers should never enter the packet at all. Record that decision in the packet itself.
| Field group | What it holds | Source record | Why a grader needs it |
|---|---|---|---|
| Case header | Packet ID, channel, dispute type, period, rule version date, real or illustrative label | Created by the reviewer | Keeps each task self-describing and separates real from illustrative cases |
| Permission record | Who approved use, which agreement and data categories were checked, what was removed | Data owner sign-off, agreement review notes | Shows the packet may be used at all before anyone grades it |
| Booking and traveler scope | Booking reference, segments or nights, party size, traveler pseudonyms, booking channel | Reservation system or PMS export | Defines exactly which services the disputed line covers |
| Purchase-time rule | Fare rule, rate plan, cancellation or no-show policy as sold, waiver in force | Rate load or fare rule snapshot, policy text dated at sale | The decision depends on the rule at purchase, not the rule today |
| Dependencies | Linked flights, connecting bookings, group or package membership, prior exchanges | Itinerary record, ticket exchange history, package record | A change to one booking can be valid only because of another |
| Disruption and change timeline | Each change with timestamp and actor: cancellation, rebooking, early departure, extension | Reservation history log, carrier schedule change notice, front desk notes | Explains why the billed version differs from the delivered one |
| Billed claim | The invoice line, memo or statement entry as issued, with reason code | Distributor invoice, ADM, statement file | The claim the task asks the solver to accept or dispute |
| Delivered evidence | Folio nights and charges, flown coupons, refund or exchange records | PMS folio, coupon status, refund record | The facts the claim should have matched |
| Decision and rationale | Accept, dispute or correct, the rule applied and the reviewer's written reason | Dispute form text, internal approval | The answer the task is graded against |
| Verified outcome | Credit note, reversed or settled memo, corrected invoice, or unchanged payable | Later invoice, settlement report, credit note | Proves what actually happened, not what was requested |
Which dependent booking or purchase-time condition limits the proposed change?
The condition that most often defeats an obvious conclusion is the rule that applied when the booking was sold. A guest who left early looks like an easy dispute until the rate plan turns out to have been non-refundable and the folio shows every night charged.
Dependencies cause the second most common mistake. A hotel stay shortened because a connecting flight was canceled, an exchange that carried value from an earlier ticket or a room that belonged to a group block can each change what the right answer is, and none of them shows up on the disputed line itself.
Agent benchmarks treat these rules the same way. The airline policy used in the tau-bench benchmark states that basic economy flights cannot be modified and notes that the API does not check such rules for the agent, so the agent must confirm them before acting. A settlement packet should make the rule just as explicit, because the system that issued the invoice usually did not check it either.
| Tempting conclusion | Condition that can invalidate it | Record that settles it |
|---|---|---|
| Guest left early, so dispute the extra nights | Non-refundable or prepaid rate, with all nights charged on the folio | Rate plan snapshot at sale and the folio |
| Reservation shows a no-show, so no charge is due | Guest arrived late or was moved to a sister property and the stay was charged | Folio, walk or relocation log |
| Debit memo cites the wrong fare, so dispute it | Exchange used a waiver that had expired on the reissue date | Waiver notice with dates and the exchange record |
| Rebooking was free because the airline canceled | The traveler chose a different date not covered by the schedule change | Schedule change notice and the rebooking history |
| Invoice rate is wrong, so request a correction | A negotiated rate applied only to bookings through a specific channel or code | Negotiated rate agreement and booking channel field |
| Dispute deadline has passed, so accept the charge | The channel allows exceptional disputes or a later correction cycle | The channel's dispute rule version and the correspondence |
Which record proves a settlement dispute was actually won or lost?
Only a record created after the dispute, by the party that had to act on it, proves the outcome. A dispute flagged as submitted, a memo marked disputed or a hopeful email reply shows only that someone asked.
For distributor invoices, that record is the credit note or the invoice paid unchanged; Booking.com, for example, says it issues a credit note when it approves a reservation dispute. For debit memos, it is the memo's final state and the amount that appears, or disappears, in a later billing or sales report. For hotel and agency invoices, it is the corrected invoice or written acceptance.
This mirrors how agent benchmarks score work. In tau-bench, the reward compares a hash of the database state the agent produced with the state produced by replaying the ground-truth actions, and checks required outputs separately. A settlement packet gives a grader the same footing: the solver's decision is compared with the decision the reviewer made, and the packet's verified outcome shows whether that decision held up.
Keep the two checks apart. A correct decision can still fail at the counterparty because of a missed deadline, and a wrong decision can succeed because nobody checked. The packet should record both, so a model is never rewarded for an outcome its reasoning did not earn.
Worked case: a stay cut short by a canceled flight (illustrative)
The following case is illustrative. The property, the guest and the counts are invented to show how a packet is filled, and no real booking is described.
Starting state: a guest books three nights at a city hotel through an online travel agency on a flexible rate that allows changes until the day of arrival. On the second morning the guest's onward flight is canceled and rebooked for the same evening, so the guest checks out after one night. The front desk closes the folio at one night but does not update the reservation in the distributor's extranet before that month's change window closes. The next invoice bills the property for three nights.
Linked evidence: the distributor reservation (three nights), the rate plan snapshot dated at booking (flexible), the folio (one night charged), the front desk note and checkout timestamp, and the airline's cancellation notice that the guest showed at the desk, kept as a note rather than a copy of the traveler's documents.
Decision: dispute the line for the two nights not stayed, because the folio shows one night charged and the rate in force at purchase did not make the other nights payable. The reviewer's rationale cites the folio and the rate snapshot, not the flight cancellation, which explains the early departure but does not by itself decide the billing.
Verified outcome: a credit note for the two nights in the following period. The packet stores the credit note reference, not the dispute confirmation screen.
Counterexample: the same story on a non-refundable rate, with all three nights charged to the guest's card at booking. The early departure and the canceled flight are identical, but the right decision is to accept the invoice line, because the property was paid for three nights. A model that disputes this line has learned to react to the disruption instead of reading the rule and the folio, which is exactly the error the packet is built to catch.
- Starting state recorded: three nights booked, flexible rate, invoice for three nights
- Evidence linked: reservation, rate snapshot, folio, checkout time, disruption note
- Rule applied: billing follows nights charged under the rate in force at purchase
- Decision: dispute two nights; counterexample decision: accept
- Outcome check: credit note reference, not the dispute flag
Gaps that make a settlement packet unusable
A packet without the purchase-time rule should be narrowed or dropped. Rules change by season, by contract renewal and by waiver, and a packet that pairs today's policy with last year's booking teaches the wrong lesson.
The same goes for packets without an outcome record. Teams often have the dispute but not the result, because credit notes arrive in a later period or a separate finance system. Linking them is usually the main preparation work, and it is worth doing before anything else.
Watch for disputes resolved by negotiation rather than by rule. If a distributor waived a charge as a goodwill gesture, label the case that way; otherwise a model learns that the rule allowed something it did not.
Finally, check permissions line by line. Access to a statement does not mean the company may share it, privacy permission for traveler data is separate from the right to license the records, and removing names does not by itself create that right. Distributor and agency agreements may restrict how statements, rates and memo content are used, and counsel should review those terms before any record leaves the company.
- Missing rate or fare rule snapshot dated at sale: drop or narrow the case
- No credit note, settled memo or corrected invoice: hold until linked
- Goodwill waiver recorded as a rule-based win: relabel
- Card numbers or traveler documents present: remove before review
- Confidential rate terms without clearance: exclude the field group
Licensing settlement and dispute history for AI
Linked dispute histories of this kind are useful to AI developers building finance and servicing agents, because each case has a starting state, a rule, a decision and a checkable result. The packet is also a practical way to show a prospective licensee what a record contains before anything is shared.
For hotels, agencies and distributors that want to license settlement histories, SourceX takes care of sourcing, rights review, contracting, preparation, delivery and payment. Its general guide on volume is that buyers want history that stays consistent for roughly two years or longer and runs to tens of thousands of records in one system; rarer kinds of dispute work can qualify on less, and SourceX judges each deal individually.
Settlement files stay put until the company has approved scope and terms and signed; eligibility is checked beforehand through a short assessment with nothing uploaded.
Frequently asked questions
What is travel supplier settlement data?
It is the set of records that reconcile what travel suppliers and the agencies or distributors selling their services owe each other: invoices, statements, debit and credit memos, dispute entries and the booking records behind them. Linked together, these records show not only what was billed but why a line was challenged and how it was resolved.
Why are settlement disputes useful for training or testing AI agents?
Each dispute has a fixed starting state, a rule that applied at the time of sale, a decision and an outcome that a later record confirms. That makes it possible to grade a model's decision against evidence instead of against a plausible-sounding explanation.
What should the evidence packet include?
At minimum: the booking scope, the rule in force at purchase, any dependent bookings, the change timeline, the billed claim, the delivered evidence such as the folio or coupon status, the decision with its rationale and the verified outcome. A permission record showing who approved use of each record should sit at the top.
Is a dispute status of submitted or accepted enough to prove the outcome?
No. A status shows that a request was made or acknowledged. The outcome is proven by a later record from the party that acted, such as a credit note, a reversed memo in a settlement report or a corrected invoice.
Can a hotel or agency share distributor statements with an AI developer?
It depends on the agreements behind them and on the personal data inside them. Many distribution agreements treat statements and rates as confidential, so counsel should review the specific terms, and traveler data needs its own privacy review before any sharing is considered.
Sources
- IATA describes the Billing and Settlement Plan as a system that simplifies selling, reporting and remitting for accredited agents, with one net remittance across participating airlines. Source
- IATA's BSP manual for agents describes a latency period after an ADM is issued, set by each BSP up to 15 days, during which the agent can register a dispute in BSPlink. Source
- IATA Resolution 850m says disputed ADMs are to be settled by the airline within 60 days of receipt of the dispute. Source
- ARC's Interactive Agent Reporting handles reporting and settlement of sales, refunds, exchanges and memos and provides back-office data files for agency reconciliation. Source
- ARC's 2023 debit memo best practices recommend agencies dispute within 30 calendar days of issuance and airlines respond within 30 calendar days of a dispute. Source
- Booking.com's partner help describes the reservation statement as an overview of the reservations on an issued invoice, used to check and dispute individual reservations. Source
- Booking.com says an approved reservation dispute results in a credit note and a rejected one leaves the invoice to be paid in full by its due date. Source
- The tau-bench airline agent policy says basic economy flights cannot be modified and that the API does not check such rules, so the agent must confirm them before acting. Source
- tau-bench scores a task by comparing the database state the agent produced with the state from replaying the ground-truth actions, and checks required outputs separately. Source
See if your company qualifies
A short company assessment. No data uploads are needed.