Practitioner analysis · 13 October 2026 · 9-minute read
ONE Order Accounting: Why Invoices and Financial Controls Still Matter
Removing e-tickets and EMDs from the target architecture does not remove an airline's obligation to document transactions. The harder engineering challenge is to turn Order and Service Item events into controlled financial records without confusing customer entitlements with invoices, receipts or revenue recognition.
Source and status: This analysis draws on the IATA Airline Retailing for Finance working-group paper Considerations for Accounting and Accountable Documents in Order-based Airline Retailing. IATA's Reference Business Architecture page links it as a June 2026 release; the paper itself credits the working group with publication in November 2025. It is a non-prescriptive discussion document, not a new binding IATA standard, regulatory requirement or vendor implementation announcement. The scenarios and control checklist below are independent practitioner interpretations.
Two document concepts that should not be confused
The paper distinguishes an accountable document from an accounting document. In legacy ticket-based operations, the same e-ticket may establish a service entitlement and support accounting processes. This coupling creates a familiar assumption that removing the ticket also removes the document burden. It does not.
| Concept | Purpose | In an Order-centric model |
|---|---|---|
| Accountability / entitlement | Evidence of contractual value, customer rights and delivery obligations | Controlled Order and Service Item records, with unique references, history and status |
| Accounting document | Formal evidence for bookkeeping, tax, reconciliation and audit | Invoices, receipts, credit notes and other documents generated from order events when applicable |
| Financial event | A change in amount receivable, deferred liability, earned revenue or payable | Traceable journal or subledger postings tied to Order and Service Item events |
These are different responsibilities. An Order can be the operational record of what was bought, modified, delivered or refunded, while external financial documents remain necessary under relevant accounting, customer and jurisdictional rules. IATA's paper discusses this separation in its definitions and conclusion (pages 3–4 and 12–13).
A booking does not necessarily mean revenue is earned
Consider a hypothetical customer who purchases a flight and checked baggage. The sale creates rights and obligations. Cash receipt or a promise to pay is not the same event as the airline delivering the flight or baggage. The working-group model connects recognition to the status of the relevant Order or Service Item, while acknowledging that actual accounting treatment depends on applicable rules.
- Order created: Record the customer commitment and services owed. Produce an invoice or receipt when required by applicable policy or law.
- Baggage added later: Record the incremental item, its commercial terms, payment or receivable change, and any required new financial document.
- Flight cancelled before delivery: Preserve the history, determine contractual refund obligations and create a credit note or adjustment where required.
- Service delivered: Emit a verifiable delivery event capable of supporting the appropriate revenue-recognition process.
- Order completed: Reconcile remaining liabilities, receivables, payments and supplier obligations before final closure.
The example intentionally avoids tax amounts, accounting-entry formulas and definitive timing claims. Such treatment requires jurisdiction-specific analysis and the actual contract, tax and accounting policies. The IATA paper's retailer Order-to-Cash sequence is on pages 6–8.
Five engineering controls an Order accounting design should test
- Event-to-document lineage. Every invoice or credit note should be traceable to the Order version, affected Service Items, event type and applicable effective time. A customer-service amendment should not silently overwrite the record that supported an earlier invoice.
- Idempotent financial processing. If a delivery or refund event is replayed during recovery, financial posting logic should identify the duplicate. This is a recommended design control, not an IATA-mandated implementation mechanism.
- Independent entitlement and cash states. An unpaid order may still represent a conditional commitment; a captured payment may precede the service. Do not collapse payment, ticketing replacement, fulfilment and revenue recognition into a single boolean flag.
- Exception reconciliation. Identify Service Items whose delivery status conflicts with an invoice, refund, settlement record or ledger posting. Track exceptions by age, financial exposure and the partner responsible for resolution.
- Audit-ready evidence. Maintain reference identifiers, timestamps, revision provenance and immutable or tamper-evident agreement history. The IATA paper explicitly discusses uniqueness, traceability, entitlement and immutable agreement records in its controls section (page 12).
Retailer and supplier do not share one financial perspective
An airline retailer may be the customer-facing seller while another airline or service partner actually delivers a product. IATA's discussion models separate Retailer-to-Customer Order-to-Cash, Supplier-to-Retailer Order-to-Cash and Retailer-to-Supplier Procure-to-Pay perspectives. This matters because a customer's payment, a supplier invoice, service consumption and inter-party settlement can occur at different times.
For a modular architecture, the interface contract should make each role explicit: who owes the customer a service, who performs delivery, who has the receivable or payable, which commercial agreement determines the settlement obligation and which status changes initiate financial processing. SRSIA principles provide further context for retailer and supplier relationships, but an interline agreement does not itself settle every accounting or tax question.
A practical event contract to review with finance
Before selecting products or a technology provider, finance and engineering teams could review whether each financial event carries enough information for controlled downstream processing. Suggested fields include:
| Field | Why it matters |
|---|---|
orderId, orderVersion | Links a document to the order state it represents |
serviceItemId | Attributes obligation and delivery at the correct level |
eventId, eventTime | Supports duplicate detection, sequence and audit evidence |
financialAction | Distinguishes purchase, amendment, refund, delivery or correction |
sellerRole, supplierRole | Clarifies responsibilities across the value chain |
currency, amounts, taxContext | Preserves commercial values and information needed for applicable treatment |
correlationId | Links order, payment, document and reconciliation workflows |
Important: This is a conceptual review checklist created for this article. These field names are not presented as an official IATA schema, API contract or complete fiscal-document data set. For standardized messages consult the IATA passenger developer resources.
Three migration traps worth designing around
Trap 1: treating ticket retirement as revenue-accounting retirement. The ticket or EMD may leave the target customer journey, but invoicing, reconciliation, reporting and retention requirements still exist. Their execution may move to an ERP, an order-management platform or a hybrid.
Trap 2: assuming every change is a new sale. Reshopping can add, remove, exchange or reprice items. The original and revised financial obligations should remain reconstructable and the correct debit, credit or tax document generated when required.
Trap 3: assuming delivery implies successful settlement. Supplier delivery evidence, retailer obligation and the movement of money are distinct. Test delayed settlement, failed payment, involuntary non-delivery, partial delivery and partner disagreement explicitly.
How to measure readiness
The following are proposed operational KPIs, not IATA benchmark values: (1) percentage of eligible Order events with a traceable accounting document; (2) unreconciled Service Item value and ageing; (3) duplicate-posting incidence; (4) time from delivery event to financial recognition, where applicable; (5) supplier invoice matching accuracy; and (6) customer document retrieval success. Define each denominator and financial materiality threshold before using the figures as programme targets.
What this means for Modern Airline Retailing
ONE Order shifts the design centre from a collection of travel documents toward Order and Service Item information. It does not imply that accounting documents cease to exist. The useful architectural question is whether an airline can demonstrate an unbroken chain from customer agreement, through service delivery and partner interactions, to every required financial statement and receipt.
The IATA discussion paper makes a useful distinction without prescribing a one-size-fits-all implementation. Translating that distinction into testable controls is where product, engineering and finance teams can make progress today.
Authoritative sources and further reading
- IATA / Industry Financial Advisory Council: Considerations for Accounting and Accountable Documents in Order-based Airline Retailing. Original document credits November 2025; listed on IATA's reference architecture page as a June 2026 release. See pages 2–3, 4, 6–12 and the conclusion.
- IATA: Modern Airline Retailing Reference Business Architecture. Official overview of PSC Recommended Practice 1786a, business capabilities and the working-group paper.
- IATA: Fulfilment with Orders (ONE Order). Standard context for Order-based fulfilment and service delivery.
- Modern Airline Retailing: Settlement and revenue accounting in an Offer and Order world.
- Modern Airline Retailing: Payment orchestration for airline retailing.
- Modern Airline Retailing: Offer and Order explained.
Editorial disclosure: Independent practitioner analysis based solely on publicly available material. The operational controls, data-field suggestions and examples above are original interpretation. This article does not give legal, financial, tax or accounting advice, does not represent IATA and makes no claim about any airline's internal technology or financial practices.
By Neerej Sasikumar · Updated 13 October 2026