An IAR Back Office (IAR BOS) Detail File is ...

An IAR Back Office (IAR BOS) Detail File is ...

• A. A file that is created for a single ticket transaction.
• B. A file that contains multiple ticket transactions.
• C. A summary of all BOS activities.
• D. A file with archiving.

Answer: (A)

In IAR BOS, a detail file is the granular data record created for one ticket transaction. It captures all the line‑item information needed to post and settle that single ticket—ticket number, passenger and flight details, fare, taxes, fees, issuing agent, and related settlement data. Because it contains data for one transaction only, it’s produced per ticket, not as a bundle of many tickets. A file that contains multiple ticket transactions would be a batch or multi-ticket file, not a detail file. A BOS summary file, by contrast, aggregates activity across many transactions, and archiving relates to long-term storage of records, not the per-ticket posting data. So the per-ticket, transaction-level nature makes the detail file exactly about a single ticket.

In IAR BOS, a detail file is the granular data record created for one ticket transaction. It captures all the line‑item information needed to post and settle that single ticket—ticket number, passenger and flight details, fare, taxes, fees, issuing agent, and related settlement data. Because it contains data for one transaction only, it’s produced per ticket, not as a bundle of many tickets. A file that contains multiple ticket transactions would be a batch or multi-ticket file, not a detail file. A BOS summary file, by contrast, aggregates activity across many transactions, and archiving relates to long-term storage of records, not the per-ticket posting data. So the per-ticket, transaction-level nature makes the detail file exactly about a single ticket.