Definition
The Interline Service Charge — universally abbreviated ISC in airline revenue accounting — is one of the core economic mechanics that allocates revenue between two airlines when one airline (the marketing carrier) sells a ticket that includes carriage on another airline (the operating carrier). The headline question revenue accounting must answer on every interline coupon is: when Airline A sold a $1,200 multi-segment ticket that included a segment flown by Airline B, how much of that $1,200 does Airline B receive, and how much does Airline A keep as compensation for the sale itself? The Interline Service Charge is the second half of that answer.
The revenue allocation between marketing and operating carrier happens in two steps. First, the gross prorate is calculated — the share of the ticket fare attributable to the operating carrier's segment under the applicable prorate agreement. The most common prorate methodology is the IATA Multilateral Prorate Agreement (MPA), which applies published Prorate Factors specific to each city-pair and class of service to allocate fare across segments; bilateral Special Prorate Agreements (SPAs) override the MPA between specific carrier pairs where the carriers have negotiated different allocations; and Special Prorate values in industry pricing publications govern certain through-fare combinations. Second, the operating carrier's prorate amount is reduced by the Interline Service Charge, which the marketing carrier retains as compensation for its sales and distribution function. The ISC therefore flows from the operating carrier to the marketing carrier; it is a discount that the marketing carrier takes off the prorate amount it forwards to the operating carrier.
The standard ISC rate under the IATA MPA framework is 9% of the prorate amount, established as the industry default through resolutions of the IATA Passenger Agency Conference. Bilateral SPAs commonly negotiate different ISC rates — 5%, 7%, sometimes 0% in joint-venture arrangements where the carriers are pooling revenue rather than transacting at arms length. In code-share arrangements, the ISC mechanic is typically replaced or supplemented by a code-share-specific revenue-share formula defined in the code-share agreement; the underlying interline relationship still exists as the legal foundation, but the code-share revenue allocation is the operative mechanic for the joint-flight-number traffic.
The operational consequence is that on a multi-segment interline ticket, every segment generates a prorate calculation, an ISC deduction, and a net amount due to the operating carrier. For Airline B that operated one segment of Airline A's $1,200 ticket with a prorate of $400 and an ISC of 9%, the net amount Airline B receives from Airline A is $400 × (1 − 0.09) = $364. Airline A retains $36 as its Interline Service Charge for handling the ticket sale, the credit card processing, the customer service interaction, and the documentation. Across the global interline traffic the calculation runs millions of times per month, requiring the standardized clearing infrastructure that the IATA Clearing House provides.
The IATA Clearing House (ICH) is the multilateral settlement infrastructure through which these interline payments are netted and settled monthly. Each member airline submits its receivables (amounts it is owed by other airlines for interline traffic it operated) and its payables (amounts it owes to other airlines for interline traffic it sold). The ICH computes the net position for each member — the algebraic sum of all its bilateral receivables and payables across all member counterparties — and produces a single net settlement amount that either flows into or out of the member each month. This netting eliminates billions of dollars of gross-position payment flows that would otherwise require bilateral settlement between every pair of members. The ICH currently operates from London and settles in multiple currencies; SITA's BSP (Billing and Settlement Plan) infrastructure handles the related clearing of travel-agent sales between agents and ticketing airlines through the same monthly settlement cycle.
The documentary substrate for all of this is the IATA Revenue Accounting Manual (RAM), which is the industry reference for interline billing standards. RAM defines the file formats (the SIS standard — Simplified Interline Settlement — has replaced the older IDEC paper-based format), the dispute resolution procedures (interline billing rejection codes and the rejection-memo workflow), the timing windows (typically billing must be issued within 6 months of the flight date for the billing to be valid), and the data-exchange protocols between revenue accounting systems. Airlines that participate in IATA interline traffic operate revenue accounting systems — Sabre Revenue Accounting, Mercator, Hitit, Accelya Skies, and a handful of in-house implementations — that produce and consume the standardized SIS files and integrate with the ICH for monthly settlement.
Why It Matters for Flight Schools
For aviation training organizations, the ISC mechanic is rarely directly relevant to flight training operations. Training flights are not interline traffic; they are internal operations conducted under the school's own AOC or operating certificate, and the revenue is internal training revenue rather than ticketed passenger revenue. ISC becomes operationally relevant in two specific contexts. First, for combined ATO/AOC operations where the AOC side of the operation conducts revenue passenger flights under a code-share with a regional airline partner — the ATO captures cadet training revenue while the AOC settles passenger revenue through the standard interline channels including ICH and ISC. Second, for cadet programs operated jointly with an airline sponsor, the financial flows between the training organization and the sponsoring airline are sometimes structured to mirror interline mechanics (the airline pays the school a per-cadet rate net of an administrative deduction conceptually similar to ISC), even though these are not literally interline transactions under IATA RAM.
The wider context — that ISC is one element of the revenue accounting and settlement infrastructure built up over 80 years to allow airlines from different legal jurisdictions, different currencies, and different revenue-management cultures to honor each other's tickets and settle the resulting financial obligations — is illustrative of how the global aviation industry has solved coordination problems at scale. The same logic applies in miniature to flight schools that operate combined training-and-charter operations, where the financial flows between training operations and charter operations require an internal accounting discipline that mirrors the interline approach without invoking the full ICH/RAM apparatus.
How Aviatize Handles This
Aviatize is not an airline revenue accounting system, and it does not interface with the IATA Clearing House. For combined ATO/AOC operators whose AOC side participates in interline traffic, the airline revenue accounting infrastructure remains a separate system of record. What Aviatize does provide is the operational substrate that an airline revenue accounting system requires from the operational side: clean flight records with operator-of-record and aircraft tail-number documentation, crew composition, departure and arrival timestamps, and any code-share marketing-carrier designation associated with the flight. These data points are what the revenue accounting system needs to match against the SIS file the marketing carrier submits to the ICH; without that operational substrate the interline billing cannot be validated.
For training operations that conceptually mirror interline mechanics — cadet program sponsorship from an airline partner, with per-cadet rates net of administrative deductions, monthly settlement, and multi-currency exposure — the billing and payments module accommodates the multi-party structure without requiring an external accounting overlay. Per-cadet rates can be configured with the administrative deduction mechanics, monthly settlement statements can be produced for the airline partner, and the audit trail required to support invoicing disputes is captured natively. The conceptual mechanic is the same as ISC even if the regulatory framework and the settlement infrastructure are entirely different.