Which GDS produces which file
| File | GDS | What it carries |
|---|---|---|
| AIR | Amadeus | Ticket number, passenger, itinerary, fare breakdown, taxes and commission |
| MIR | Travelport (Galileo, Apollo) | Ticket and booking details, fare, taxes and agency data |
| IUR | Sabre | Ticket and itinerary details, fare, taxes and accounting lines |
How the back office uses them
When a ticket is issued, voided, refunded or exchanged, the GDS writes an interface record and delivers it to the agency, often to a folder or server the back-office system watches. The accounting system reads the record and creates the matching entry: an invoice for a new ticket, a cancellation for a void or a credit note for a refund.
Because the record comes from the same source as the BSP billing, entries created from interface files reconcile cleanly against the BSP statement.
Keeping the feed complete
- Make sure every issuing office and pseudo city code is set to deliver interface records
- Watch for records that arrive but fail to process, and resolve them daily
- Check that voids, refunds and exchanges flow as well as new issues
- Compare ticket counts in the GDS with entries in the books for each day
Interface files in SYSTACC
SYSTACC accepts AIR, MIR and IUR records and can pick them up on a schedule through FTP sync, so a new file does not wait for someone to download it. Each record posts as an accounting-ready entry, and refunds and exchanges in later files meet the original ticket.
