data application negotiated fares – … · 3.2.4 net remit and credit card forms of ... the...

DATA APPLICATION NEGOTIATED FARES – TICKETING AND REPORTING

The information contained in this document is the property of ATPCO. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form, or by any means; mechanical, photocopying,

recording, or otherwise, without the prior written permission of ATPCO. Under the law, copying includes translating into another language or format. Legal action will be taken against any infringement

Copyright ©2007 by Airline Tariff Publishing Company

All rights reserved.

DATA APPLICATION FOR TICKETING AND REPORTING NEGOTIATED FARES

Page E.03.35.02 Revised October 2015 Effective 11 June 2017

Contents 1.0 Introduction ...................................................................................................................................................................................... 4 2.0 Ticketing .......................................................................................................................................................................................... 7

2.1 An Introduction to Net Reporting, Net Remit, and Net Ticketing ............................................................................................... 7 2.2 The Ticket ‘Face’ ......................................................................................................................................................................... 9

2.2.1 Tour Code Box .................................................................................................................................................................... 11 2.2.2 Fare Basis/ Ticket Designator Box ..................................................................................................................................... 14 2.2.3 FARE/ Equiv. Fare/ Total Boxes ........................................................................................................................................ 15 2.2.4 Fare Calculation Area ......................................................................................................................................................... 18 2.2.5 The Remittance Area .......................................................................................................................................................... 19

2.3 Ticketing System Reporting of Sales Data ................................................................................................................................ 21 2.3.1 Reporting Tape of Accounting and Settlement Information ............................................................................................... 21 2.3.2 TCN File Reporting ............................................................................................................................................................ 25 2.3.3 Electronic Ticket Data Reporting ....................................................................................................................................... 27 2.3.4 Summary of Ticketing Issues .............................................................................................................................................. 32

3.0 Settlement Processing .................................................................................................................................................................... 33 3.1 ARC Net Ticket Processing ....................................................................................................................................................... 33 3.2 BSP Net Remit Processing ......................................................................................................................................................... 34

3.2.1 Net Remit Methods ............................................................................................................................................................. 35 3.2.2 Net Remit Calculations ....................................................................................................................................................... 36 3.2.3 Net Remit Methods in Use .................................................................................................................................................. 38 3.2.4 Net Remit and Credit Card Forms of Payment ................................................................................................................... 42 3.2.5 Settlement Issues ................................................................................................................................................................. 45

4.0 Revenue Accounting ...................................................................................................................................................................... 46 4.1 Accounting for Sales .................................................................................................................................................................. 46 4.2 Fare Audit ................................................................................................................................................................................... 47 4.3 Interline Billing .......................................................................................................................................................................... 48 4.4 Revenue Accounting Issues ....................................................................................................................................................... 49

5.0 Post Ticket Processing ................................................................................................................................................................... 50



5.1 Net Ticket Reissues .................................................................................................................................................................... 51 5.2 Net Ticket Refunds..................................................................................................................................................................... 52 5.3 Issuance of Fees for a Net Ticket ............................................................................................................................................... 53 5.4 Post Ticket Processing Issues ..................................................................................................................................................... 54

6.0 Glossary of Terms .......................................................................................................................................................................... 55 Appendix A Rules for Combining Net Fares ....................................................................................................................................... 58



1.0 Introduction This Data Application is written in relation to the Ticketing, Settlement, and Revenue Accounting for Category 35 Negotiated Fares transactions. Note that Category 35 can also be used for security purposes only to create a non-negotiated fare. Many of the terms found within this document can be referenced from the following sources:

(1) Passenger Services Conference Resolutions Manual (2) IATA Data Interchange Standards Handbook

Once the appropriate price or discount has been selected for the transaction and the fare solution has been built by the pricing system, the transaction will be ticketed. This process provides the accountable document showing that the passenger has paid for the fare product. Ticketing data is primarily driven to three destinations when the ticket has been issued:

(1) The Electronic Ticket message will be sent to the Validating (also known as ‘Issuing’ or ‘Plating’) Carrier who controls the ticket and remitted funds throughout the life of the transaction

(2) The agency Reporting Tape files will be sent to the IATA Billing Settlement Plan (BSP) for non-US Travel Agency Sales, or Airlines Reporting Corporation (ARC) for US Travel Agency sales, so that settlement of funds between the airline and the travel agency can take place (for hosted airline reservations, the file will be sent directly to the airline to initiate funds settlement).

(3) The ISR/TCN file will be sent to the Validating and/or Marketing and/or Operating Carriers in the itinerary (note that Electronic Ticket messaging also fulfills this need to some extent).

In all of these cases, sufficient detail must be presented in relation to ticket pricing to enable reliant down-line processes to accurately re-assess and audit the ticket, and to generate interline billings as necessary. The diagram over the page illustrates the processes which are outlined in this document.



CATEGORY 35/ TICKET DISCOUNT

PRICINGINSTRUCTIONS

AIRLINEDIRECTPRICING

IATA BSP

ARC

DirectReservations

VALIDATINGCARRIER

ATPCO OPERATINGCARRIER

Agency and Airline ET Issuance Message

InterlineBilling

BSP HOT File

ARC CAT File

Direct Reservations File

ET Issuance

ET Issuance(some period prior to flight)

TCN Data

ATPCO

FAREOWNER

TRAVEL AGENCYPRICING

TRAVELAGENCY

TICKETING

RET FILE

RET FILE

AIRLINETICKETING

TCN Data

TCN/ISR File The following section outlines various ticketing and revenue accounting scenarios which may result from pricing a ticket with a Category 35 fare, and the implication on each of the above data sources.



The following processes require accurate net remittance information to be reported with the ticket for agency settlement in order to function correctly in an automated environment:

(1) Settlement a. ARC processing of Net Tickets b. BSP calculation of supplementary commissions based on the Value Code, Contract Code or Tour Code reported with

the ticket (2) Revenue Accounting

a. Accounting for a Net Ticket sale b. Ticket audit of a Net Ticket involving the reconstruction of the net fare c. Interline billing and settlement of a Net Ticket for both agency and airline sales

(3) Post-Ticket Processing a. Automated reissue of a Net Ticket b. Automated refund of a Net Ticket c. Issuance of fees (ticketing, optional or baggage) after the time of initial pricing

These will be discussed in order later in this document.



2.0 Ticketing 2.1 An Introduction to Net Reporting, Net Remit, and Net Ticketing Net Reporting is an agreement between an airline and a Travel Agency to report a ticket transaction at a value other than the published fare. In order to enable this process, a number of net remit methods have been designed so that airlines can differentiate the fare products offered in the marketplace by point of sale (travel agency), and to provide a standard methodology for calculation of the funds settlement between the airline and the ticketing travel agency. There are three fundamental ways in which such a transaction may be ticketed and reported to an airline:

(1) Using Value Coding (Net Remit Method 1) or Contract Coding (Net Remit Method 5), such that the BSP is required to calculate the supplementary commission values from a code reported in the ‘TOUR CODE’ box of the ticket.

(2) As a direct pass-through from the ticketing system which has already calculated the standard and supplementary commissions but the transaction is still identified as a Net Remit ticket (Methods 2, 3 and 4). Note that there are still calculations on the part of the BSP, but they are performed on amounts and percentages which have already been reported by the ticketing system. The onus for correctly reporting the net is on the pricing and ticketing application.

(3) As a ‘Net Ticketing’ transaction where the transaction will not be identified as ‘Net Remit’ and thus is treated as a published fare transaction for the purposes of the BSP. Any supplementary commissions due to the Travel Agency will be passed through directly from the ticketing system.

The fundamental concept of ‘Net Remit’ is as follows (note that ‘selling fare’ as such is not directly relevant to the BSP):

Published Fare Less Standard Commission Less Supplementary Commission

= Net Fare Amount (may be calculated or may have been agreed and entered by Agent) Note that the concept of Net Remit is not a feature of ARC US Travel Agency sales reporting.



It should also be noted that the Category 35 data has the concept of three fare levels – namely:

(1) ‘gross’ or published fare – the fare component value prior to the agency incentive being applied (2) ‘selling’ fare – the ‘markup’ fare level at which the agency is allowed to sell the fare component to the passenger (3) ‘net’ fare – the fare component value after all agency incentives have been applied

For example: Gross or Published Fare = GBP 1000.00 Selling Fare = GBP 600.00 (may or may not be instructed by the carrier) Net Fare = GBP 500.00 So for airline accounting purposes, the agency incentive is 1000.00 – 500.00 = GBP 500.00 (published gross fare less net fare) The passenger buys the fare for GBP 600.00 The agency ‘markup’ is GBP 100.00 In practice, for reporting purposes, the selling fare is not a reported factor– it has no bearing on airline accounts – but there are some implications on credit card sales where the airline is the merchant for the sale and therefore bills the Credit Card, when the selling fare is different to the published fare. These are explained later in this document when the BSP process is documented.



2.2 The Ticket ‘Face’ When pricing a ticket using a Category 35 pricing entry, the following fields are used for the accurate settlement and/or revenue accounting for the net fare data in the transaction (applies to both Electronic Ticket data elements and to paper tickets):

Reproduced by permission of IATA from ‘Passenger Services Conference Resolutions Manual, 26th Edition’

1. TOUR CODE : The code specified in the CAT35 to indicate a ‘deal’ or incentive fare 2. FARE BASIS (also known as Fare Class)/ TICKET DESIGNATOR : Instructed in the CAT35 3. FARE/EQUIVALENT FARE/TOTAL : May be an amount or may be ‘IT’, ‘BT’, or ‘BULK’ 4. AIRLINE CODE : Validating Carrier restricted by ‘Carrier Restriction’ field 5. REMITTANCE AREA: Optional area showing net remit indicator, commission amount, percentage, and net fare

amount as required by the Net Remit Method

1

2

3 4 5



These fields are further referenced to the Category 35 pricing data application as follows (shaded areas relate to the actual ticket face): Byte Location Match / Action Definition / Processing METHOD TYPE Byte 33

Action Identifies the type of Net Remit Reporting scheme that applies for the RET Process.

TICKETING CARRIER RESTRICTION Bytes 98-102

Action These fields indicate which carrier’s (publishing carrier or other specified carrier) plate and/or the stock on which tickets must be issued.

AUDIT/PASSENGER COUPON Byte 104

Action Indicates whether the ticketing information specified should be placed on the audit coupon and/or the passenger coupon (note that with the advent of Electronic Tickets, the passenger coupon no longer exists).

TYPE Byte 105

Action Indicates which type of code is located in the following fields: Tour Code, CAR Code/Value Code, CAR Code only, or Value Code only.

TOUR/VALUE/CAR CODE Bytes 106-120

Action This field specifies one of the following to be placed in the Tour Code Box on the ticket: Tour Code, CAR Code/Value Code, CAR Code only, or Value Code only.

TICKET DESIGNATOR Bytes 121-130

Action This field specifies the ticket designator to be appended to the end of the fare class, which is placed in the Fare Basis/Ticket Designator Box on the ticket.

TICKETED FARE DATA INDICATOR Byte 136

Action Indicates what information to retrieve and place on the ticket: the fare basis only, the fare basis and the fare amount, or as specified in the category.

FARE CLASS/FARE FAMILY Bytes 150-157

Action/Match Action – Identifies the fare class or generic fare class for the fare to be retrieved. It is also used to identify the fare class to be placed in the Fare Basis/Ticket Designator Box on the ticket. Match – Fare class/fare family specified is used as match criteria to the fare class on the Fare Record and/or Record 1 of the fare to be retrieved.

FARE BOX Bytes 173-194

Action These fields specify either a ‘Text’ message (e.g., IT, BT) or a specified amount to place in the Fare Box on the ticket.



2.2.1 Tour Code Box The Tour Code Box has emerged as a key tool in specifying a code required for net remit processing, to identify that a specific ‘deal’ applies to the fare, and thus can allow for further calculations and processing down line. IATA Resolution 720a described the Tour Code Box as follows:

In practice in reference to Category 35 Method 1 and Method 5 net fares, the Tour Code box (or element) will always show either the value code or the commercial agreement reference required for net remit processing by the BSP. Settlement processing based on the tour code by the time the ticket reaches the BSP will be for Method 1 (Value Coding) and Method 5 (Contract Coding) net remit. The element in Category 35 which refers to the Tour Code is as follows: Byte Location Match / Action Definition / Processing TYPE Byte 105

Action Indicates which type of code is located in the following fields: Tour Code, CAR Code/Value Code, CAR Code only, or Value Code only.

TOUR/VALUE/CAR CODE Bytes 106-120

Action This field specifies one of the following to be placed in the Tour Code Box on the ticket: Tour Code, CAR Code/Value Code, CAR Code only, or Value Code only.



Bytes 106-120 directly instruct the ticketing system what code to place in the Tour Code box at the fare component level. When conflicting information is found, for example when there is a combination of fares allowed by Category 10, then the following hierarchy should be used:

(1) Use the Tour/Value/CAR Code specified in the matched fare component where the fare owner = Validating Carrier (2) Where more than one such fare component exists, take the Tour Code from the first Validating Carrier-owned Category 35

matched fare component in the itinerary. (3) Where no such fare component exists (i.e. the Validating Carrier does not own any fare components in the itinerary), take the

Tour Code from the first Category 35 matched fare component in the itinerary. The above are subject to combination rules included in Appendix A. In March 2007, the Joint Passenger Ticketing Committee (JPTC) approved a paper to include a repeatable Tour Code element at the Fare Component level for Electronic Tickets. This would not replace the existing tour code box as it is used in crucial settlement processes today. The values as defined by ‘Type’ above can be defined as: Value Code A carrier specified and agreed code which can be interpreted by the data processing

center at the BSP to calculate the net submit amount or the net fare. Commercial Agreement Reference (CAR) A carrier specific code which is used for tracking agency sales. This value cannot be

used to calculate the net submit amount. Tour Code (Contract Code) A carrier specified and agreed code which is used by the data processing center to

perform a series of calculations which may be based on the itinerary, agency code, dates and other transaction attributes to apply specific incentive payments from the airline to the travel agency.



Tour Code The Tour Code box may also hold any carrier specified code in keeping with IATA Resolution 728 which may be unrelated to net remit processing. This can also be the vehicle to demonstrate a Net Ticketing (Private Fare) agreement.



2.2.2 Fare Basis/ Ticket Designator Box The Fare Basis/ Ticket Designator Box or Element is set at coupon level (although it must be the same for all coupons relating to one fare component). In the application of CAT35, this field is populated on the instruction of two data filed data elements: Byte Location Match / Action Definition / Processing FARE CLASS/FARE FAMILY Bytes 150-157

Action/Match Action – Identifies the fare class or generic fare class for the fare to be retrieved. It is also used to identify the fare class to be placed in the Fare Basis/Ticket Designator Box on the ticket. Match – Fare class/fare family specified is used as match criteria to the fare class on the Fare Record and/or Record 1 of the fare to be retrieved.

TICKET DESIGNATOR Bytes 121-130

Action This field specifies the ticket designator to be appended to the end of the fare class, which is placed in the Fare Basis/Ticket Designator Box on the ticket.

There is nothing exceptional about the processing of the Fare Basis Ticket Designator element for net remit, except that it may be used as an element for calculating net remit amounts in certain non-standard Contract Coding scenarios. Otherwise this field is passed on the ticket, and as facsimile elements with the transaction, unaltered from the original instruction.



2.2.3 FARE/ Equiv. Fare/ Total Boxes For a true Net Remit transaction – in other words when the published fare is reported, and is subsequently discounted by a ‘net’ commission or incentive amount – the fare, equivalent fare, and total boxes should show the amount of the published fare. In the case of true Net Ticketing, the fare box, equivalent fare box, and the total box will all contain ‘IT’ to mask the true selling fare. This is defined by the following element in the Category 35: Byte Location Match / Action Definition / Processing FARE BOX Bytes 173-194

Action These fields specify either a ‘Text’ message (e.g., IT, BT) or a specified amount to place in the Fare Box on the ticket.

If the instruction in the Category 35 is to place a text value (i.e. ‘IT’) in the Fare Box, this masks the true selling fare value to all except the airline involved in settlement of the transaction with the travel agency. All ticket copies except the audit coupon (which is now obsolete in paper form, but may be stored by the travel agency at the point of sale) are masked. The reporting of the ticket in BSP and ARC is only sent to the Validating Carrier. All other masking of TCN/ISR and Electronic Ticket messaging is by programmatic specification of the issuing system. There is also the facility to state an amount, currency, and decimal in the Category 35 instruction. The relevant references in IATA Resolution 722 are as follows for these three fields: The Fare:



The Equivalent Fare Paid:

The Total Amount:

Finally to make clear that Taxes, Fees, and Charges are unaffected by this instruction:

This instruction drives the fare (FARE) value for all further reporting of ticketing information to downline processes.



As a general rule, the fare for which the agency ‘sells’ the ticket is not known by the settlement system (BSP or ARC). In practice only the concept of the ‘gross’ fare and the ‘net’ fare are known (and these are derived from calculations), although the ‘selling’ fare is assumed to be equal to the gross or published fare for the purposes of airline to travel agency settlement. In practice, for Credit Card sales, the gross fare and the selling fare must be equal, because the settlement system is responsible for billing the customer credit card and as such can only bill based on the reported amount. Where these are not equal, some adjustment is required in the settlement process in order to reconcile fund remittance between the Airline and the Travel Agency, as described in the section ‘Settlement’ below. In cases where fare components are combined and one or more components instruct that a text value should be placed in the fare box, and one or more fare components are for a published fare or for a fare amount to be in the fare box, the matrices included in Appendix A are to be followed in determining whether or not the fare should be combined at all, and if so what the ticket result should be.



2.2.4 Fare Calculation Area Based on the above information in the ‘FARE BOX’ field in the Category 35, the Fare Calculation Area will also use the text value (e.g. ‘M/IT’) to block out any values presented in the fare calculation area at fare component level. The instructions for this process are well defined within IATA PSC Resolution 722:

In cases where fare components are combined and one or more components instruct that a text value should be placed in the fare box, and one or more fare components are for a published fare or for a fare amount to be in the fare box, the matrices included in Appendix A are to be followed in determining whether or not the fare should be combined at all, and if so what the ticket result should be for the fare calculation area.



2.2.5 The Remittance Area Certain net remit information which is taken from instructions in the Category 35 can be placed (optionally) on the audit and agency coupons of the ticket for use in the BSP environment. There is no defined standard for the remittance area as the information included depends entirely upon the needs of the BSP processing country. The following reference is the only current definition of the ‘Remittance Area’ in IATA standards: From Resolution 726e – Multiple Purpose Document (MPD) - Neutral, Carbonized, Manual

It should be noted that as per Resolution 722f Section 6.2.1.1, that the agency coupon and the charge form are optional (although the audit coupon must be produced and stored by the travel agency in paper or electronic form), and as such a formal ‘remittance area’ may not be available in reporting the electronic ticket to the BSP. All of the information commonly provided in this area is available in data element form both in the Electronic Ticket Record and in the RET (Reporting Tape) sent by the ticketing system to the BSP. For the purposes of the Category 35 Data Application, it is assumed that the following uses are made of the “Remittance Area” of the Agency (Audit) Coupon (if printed). Method Name Remittance Area Entry

1 Value Coding None required 2 Using the Fare Area of the Remittance Area Net Fare will be entered – e.g. NR1000 3 Using the Commission Percentage of the Remittance Area Standard commission rate will be entered e.g. 9 4 Using the Commission Amount of the Remittance Area Standard commission amount will be entered e.g. 90.00 5 Contract None required



In terms of Electronic Tickets, or in fact any ticket which has printing suppressed for the Audit and/or Agency Coupons, the following fields are used by the BSP for calculating the correct net submission amounts: Method Name Field Use for Net Submission Calculation

1 Value Coding None required (tour code used) 2 Using the Fare Area of the Remittance Area Net Fare is entered in ‘Amount Entered by Agent’ field 3 Using the Commission Percentage of the Remittance Area A total commission amount and commensurate percentage

is calculated from the ‘Commission Amount’ and ‘Commission Rate’ fields

4 Using the Commission Amount of the Remittance Area A total commission amount and commensurate percentage is calculated from the ‘Commission Amount’ and ‘Commission Rate’ fields

5 Contract None required (tour code used) In such cases, even where an electronic version of the Agency and/or Audit Coupon exists, the Remittance Area will only be used for reference purposes and not for any vital processing by the BSP in the settlement process. In other words, the remittance area is not checked at all by automated processing for settlement.



2.3 Ticketing System Reporting of Sales Data

2.3.1 Reporting Tape of Accounting and Settlement Information The Ticketing System will create a file which is known as a ‘RET’ file (Reporting Tape) which is sent both to ARC (US Travel Agency Sales) and IATA BSP (non-US Travel Agency Sales). Within the transaction reported on the RET file, there should be sufficient data to allow either:

(1) The BSP to calculate the Net Fare Amount and Net Remit Effective Commission Amount from a Value Code/ Commercial Agreement Reference (note not applicable to ARC)

(2) ARC or the BSP to pass through data elements without failing normal reconciliation validation processing used for any transaction:

(a) Sum of all Form of Payment Amounts (FPAM) = Ticket Document Amount (TDAM)1 (b) Net Fare Amount (AEBA) is no greater than the Ticket Document Amount (TDAM) less Taxes (TMFA) (c) Commission Amount (COAM) takes precedence over Commission Rates (CORT) if there is contention (d) Commission Rate (CORT) is calculated from the Commission Amount (COAM) if not reported (e) Net Fare Amount (AEBA/NTFA) is only reported when Net Remit Indicator (NRID) is set to ‘NR’

The RET file is sent on a period basis (generally daily) to the Data Processing Center (DPC) so that further validation and billing settlement can occur. In light of the above ticketing fields discussed, the following fields reported in the RET file relate to Category 35-generated fares: Field Definition NRID Net Remit Indicator, denoting that the transaction involved Net Remit processing using specified Methods TOUR The tour code exactly as it would have been generated on the ‘face’ of the ticket

1 With the exception of some net remit schemes, for example where credit card form of payment is allowed for Net Remit transactions



Field Definition AEBA For method 2 net remit, the Amount Entered by Agent is passed in the RET file as the net fare amount. Note that

where a Category 12 Q surcharge, Category 8 Stopover, or Differential are calculated on the same fare, they will2 be added to the net fare to create the Amount Entered by Agent

COAM (x2) The Commission Amount, first occurrence will be standard commission or total commission, if there is a second occurrence it will be supplementary commission broken out by the Ticketing System

CORT (x2) The Commission Rate, which is the Commission Amount divided by the base fare (Ticket Document Amount minus taxes)

FARE The ‘fare box’ exactly as it would have been generated on the ‘face’ of the ticket EQFR The ‘equivalent fare’ box exactly as it would have been generated on the ‘face’ of the ticket TOTL The ‘total’ box exactly as it would have been generated on the ‘face’ of the ticket FRCA (x4) The Fare Calculation Area exactly as it would have been generated on the ‘face’ of the ticket Note that many of these fields are intended to be ‘facsimile’ information, which is becoming a redundant term as paper tickets become obsolete. The purpose of these fields is to allow the airline to rebuild a facsimile copy (or image) of the ticket as it would have looked to the passenger, in order to assist with any queries and without needing to retain the original paper documents for legal records. For Net Ticketing and Net Remit Methods 2, 3, and 4, the net calculations have already occurred in the generation of the ticketing record by the Ticketing System, and as such the BSP does not need to derive net values from the tour code field, although for these Net Remit schemes the BSP will perform calculations to ensure that the standard and supplementary commission fields are correctly populated. For Net Remit Methods 1 (Value Coding) and 5 (Contract Coding), the net submit amount will not be calculated by the Ticketing System, and the BSP must perform further calculations to arrive at the correct net amount of the transaction. All fields reported must be appropriate to the Net Remit Method Code and Calculation Type which has been selected by the Validating Carrier from the list of available Net Remit Schemes for the country of ticket issuance. These are described in greater detail in Section 3.

2 Subject to confirmation with the issuing ticketing system



2.3.1.1 Reporting Net Tickets filed in CAT35 The reporting of Private Fares filed through Category 35 assumes the reporting of financial amounts as instructed in the Category 35 by the ticketing system (note that commission calculations are not performed by the ticketing system). There will be no further calculation performed on these transactions as they pass through the BSP or ARC settlement processes other than the translation of a commission rate into an amount if only a rate has been reported. These are characterized by the Method Type (byte 17) being blank. There are three types of net ticketing Display Category Types in the Category 35, namely: L = Selling Fare with Optional Net Amount C = Net Fare with Selling Fare Range which can be updated by the Travel Agency T = Net Fare with Selling Fare fixed Current reporting standards are as follows for these three transaction types: Cat

Display Type in

Record 1

Form of Payment

Published or

Selling Fare

Net Fare CAT35 COMM

COBL on HOT

COAM

Net to Airline

Agency Markup

Agency COMM

Agency TOTAL

L All $200.00 - 5% $200.00 $10.00 $190.00 $0.00 $10.00 $10.00 C Cash $200.00 $150.00 5% $150.00 $7.50 $142.50 $50.00 $7.50 $57.50 C Credit $200.00 $150.00 5% $200.00 $60.00 $140.00 $0.00 $60.00 $60.00 T Cash $200.00 $150.00 5% $150.00 $7.50 $142.50 $50.00 $7.50 $57.50 T Credit $200.00 $150.00 5% $200.00 $60.00 $140.00 $0.00 $60.00 $60.00 T All $200.00 $200.00 5% $200.00 $10.00 $190.00 $0.00 $10.00 $10.00



The following general observations apply to these Net Ticketing scenarios: (1) Credit Card sales are always reported to the airline at the selling or gross fare (2) Cash sales allow the agency to report the ‘Net’ amount to the airline and retain a ‘mark-up’ (3) Credit Card sales where the Net Fare is filed with a fixed Selling fare allow the agency commission to be calculated as a

supplementary amount, in a similar manner to Net Remit Calculation E (Commission applies on the Gross less the Supplementary amount)



2.3.2 TCN File Reporting Ticketing systems also generate a file called ‘TCN’ (Transmission Control Number) which is a proprietary product to each Ticketing System and is used for the following purposes:

(1) Reporting sales information to the Validating Carrier in advance of Accountable Sales (see 2.3.1) which are often reported periodically rather than daily. This allows better management information for the purposes of Sales, Marketing, and Revenue Management.

(2) Reporting marketing information to the Validating Carrier which is not available in the Accountable Sales information. The Accountable Sales information in the RET is used for the purposes of settlement and accounting and so is not rich in marketing data which may be used in network planning and analysis.

(3) Sharing sales data with Marketing and Operating Carriers in the itinerary to enable automated interline billing from the Operating Carrier(s) to the Validating Carrier.

This file is reported, generally on a daily basis, to the above named airlines who subscribe to this service. This may be sent directly to the airline, or more commonly through the ATPCO Sales Data Exchange service. Reliable net information cannot be processed from TCN files, simply because there are different standards in the marketplace for reporting such data. While the Net Remit Indicator will reliably indicate that the transaction has been generated using one of the five standard BSP Net Remit methods, the net fare and the supplementary amounts are not reliably shown (and in fact for Methods 1 and 5 can never be accurate in this format, because BSP processing has not yet taken place to calculate the net). The following general rules apply to reporting of Net Remit tickets in TCN files:

(1) For transactions sold using Net Remit Method 2, the true net fare should be displayed in the Amount Entered By Agent (AEBA) field, in combination with the Net Remit Indicator being set to ‘NR’.

(2) For all other Net Remit Methods (1, 3, 4, 5), the Fare Numeric (FNUM) field and the Fare Calculation Area (FRCA) are likely to show the gross or published fare amount (i.e. before commission has been deducted). Commission Amount fields (COAM) may be used by the subscriber to attempt to calculate the true net fare (FNUM-COAM) but Commission Amount fields are not 100% reliable in this data source and may be zero-filled.

(3) For Net Ticketing transactions (IT, BT, Bulk) which are not Net Remit, the Fare Numeric (FNUM) field is often zero-filled to disguise the true net fare. The Fare Calculation Area will also have amounts disguised with ‘M/IT’ as shown above.



In practice, there are also a number of fields which are ‘removed’ by ATPCO during processing when the airline to which the ticket is being sent is not the Validating Carrier. This is used as a default so that net data is not unwittingly sent to Marketing and Operating Carriers, when the net remittance is only related to settlement between the Travel Agency and the Validating Carrier. The Validating Carrier can, by choice, remove these restrictions and share such net data with their interline partners. The following fields are currently treated as ‘Net Remit Removal’ elements: AEBA Amount Entered by Agent True net fare for Method 2 Net Remit APBC Amount Paid by Customer True selling fare COAM Commission Amount Commission amount (x2) due to Agency CORT Commission Rate Commission rate (x2) due to Agency COTP Commission Type Indicator of the type of commission calculation EFRT Effective Commission Rate * Total commission rate due to Agency EFCO Effective Commission Amount * Total commission amount due to Agency FPAM Form of Payment Amount ` Payment amount reported by Agency NTFA Net Fare Amount * True Net Fare from BSP into ISR REMT Remittance Amount * Remittance Amount between Airline and Agency SPAM Supplementary Amount * Net commission (i.e. above Standard Commission) amount due to Agency SPRT Supplementary Rate * Net commission (i.e. above Standard Commission) rate due to Agency * Only present for ISR transactions which have been created using a BSP file input It should be noted that one of the benefits of the ISR product, which merged inbound BSP transactions from subscribers with the same inbound TCN transactions from providers, is that the true net fare is available for all transactions, whether gross, Net Remit, or Net Ticketing. This is an essential feature for those carriers who have bilaterally agreed net interline billing, and require the sharing of the true net fare with both the Validating and the Operating Carrier(s) of the transaction.



2.3.3 Electronic Ticket Data Reporting The current standard for IATA stock distribution is Electronic Ticketing. There is a sunset date for the distribution of paper ticket stock as of 31st December 2007, after which time any BSP settlement and interline billings must be electronic ticket based. ARC currently processes over 95% of US Travel Agency sales volume as Electronic Tickets. It is noted that there is no sunset date within the US Travel Agency market for the distribution of paper ticket stock. The process for issuance and reporting of electronic tickets is the same regardless of whether the ticket is priced using published fares, net ticketing, net remit, or a combination of the three. The elements within IATA Resolution 722f Appendix A which are transmitted to indicate that net data is present are given below. In recognition that Electronic Tickets allow for greater flexibility than some other sales data sources, the specifications reflect the requirements of carriers currently using or developing automated reissues and refunds, which require more net information than was available on the face of the paper ticket. The Electronic Ticket record is not the primary driver for any net processing for accounting or settlement purposes, as it is primarily used for the operational control of passenger movements during the lifecycle of the transaction. However these become vital when a passenger sales agent or a kiosk is confronted with a passenger requiring a ‘post-ticket’ transaction such as a reissue, refund, or to a lesser extent the issuance of a service fee. These issues are explained in more detail in Section 5.0 ‘Post Ticket Processing’. Note that many of the below elements are in the IATA and ATA resolutions as standard, but development of these elements will depend upon the EDIFACT version which the ticketing system is using.



2.3.3.1 ET Base Fare – Gross, Net, Sell The base fare amount is transmitted in messaging between the Travel Agency and the Airline, and also between Airlines for the purposes of establishing Airport Control for interline flights. The Net Amount is ‘Conditional’ (i.e. must be sent if available to the transmitting system), and the Sell Amount is only applicable to Travel Agency to Validating Carrier transactions.

As can be seen from the above description, the Net Fare Amount is described as the Net Submit amount from the Travel Agency to the Validating Carrier. The Sell Amount is described as the ‘applicable fare when different from the base fare amount’.



These same characteristics (i.e. base, net and sell amounts) apply to the following elements: (1) Base Fare Amount (2) Equivalent Fare Paid Amount (3) Exchanged Residual Fare Component Base Amount (4) Exchanged Residual Total Construction Amount (5) Exchanged Residual Total Amount (6) Fare Calculation Area Amount (7) Fare Component Base Amount (8) Total Construction Amount (9) Total Ticket Document Amount



2.3.3.2 ET Commission Amount, Rate, Type The Commission Amount and Rate are reported as for other sales data sources:

The Commission Type is simply a field indicating the basis upon which the standard commission amount was calculated. In general this will be the gross or published fare. However the standard commission uses a different basis for Net Remit transactions where calculations E, F, or G are used (see Settlement). See value ‘N’ below.

It should be noted that net remit application of this data element are only based on values blank or ‘N’.



2.3.3.3 ET Fare Rule Indicator (Repeatable) This data element shows the Category number for the fare components listed on the ticket. At the current time this element is flawed as it has no relation to the Fare Component Number. This will only be effective where only one fare component has been applied in the pricing solution, or all of the Fare Components in the itinerary use the same Tariff, Carrier, and Rule Category.

From the March 2007 Joint Passenger Ticketing Committee (JPTC), an indicator of the category number (repeatable) at the fare component level was approved for Electronic Tickets. This does not replace the above element, but will give carriers a more accurate view of which categories were used to come up with the ticketed pricing solution.

2.3.3.4 ET Other Data Elements The Tour Code and the Net Remit Indicator are presented with the Electronic Ticket, and are currently at ticket level, with one of each per ticket. The Tour Code, which can occur at Fare Component level, will be structured to be reported at this level effective 1st June 2008.



2.3.4 Summary of Ticketing Issues At high level, the following issues have been identified above with regard to ticketing Net Remit transactions in an automated environment:

(1) Multiple fare components containing multiple Net Remit Method codes – each Net Remit method specifies a different rule relating to the Remittance Area of the Agency Coupon – the ticket only has one Remittance Area (this has been addressed by the combination rules agreed by the meeting listed in Appendix A – whereby fares with different net remit method codes cannot be combined).

(2) Multiple fare components containing mixed published/ net ticketing and net remit fares – the ticket only has one net remittance indicator (addressed in Appendix A).

(3) Multiple fare components containing mixed published/ net remit and net ticketing (IT) fares – the ticket only has one instance each of fare, equivalent fare, and total amount elements (addressed in Appendix A).

(4) Multiple fare components containing different fare owners – which carrier rules apply to the net settlement (net submit amount) between the Validating Carrier and the Travel Agency if there is a conflict? (addressed in Appendix A).

(5) Some data elements currently reported in sales data feeds are presented at ticket level, and should be at fare component level. Specifically these are Tour Code, Net Remit Indicator, and Fare Rule Indicator (pending approval by JPSC in 2007, Ticketing Committee has approved the inclusion of Fare Component Fare Rule Indicator and Tour Code in the Electronic Ticket message. Multiple net remit indicators are not required as they cannot be combined).



3.0 Settlement Processing 3.1 ARC Net Ticket Processing US Travel Agency sales do not allow for net remit processing. There is no concept of supplementary commission reported for US Travel Agencies. Thus the only concept of Net Reporting is Net Ticketing as described above. This involves the following characteristics:

(1) The Fare Box, Equivalent Fare Box, and Total Box all reflect ‘IT’, ‘BT’, or ‘BULK’ (note BULK is not a standard value but is used in practice in the marketplace)

(2) The transaction will be reported as a published amount (as this is the amount to be billed to the credit card in the instance of a credit transaction) with appropriate commissions applied

(3) The transaction is billed to the customer credit card (for Credit Card Form of Payment) as:

Ticket Document Amount (Assumed to be Fare + Taxes)

= Amount billed to customer credit card

(4) The net remittance from the travel agency to the airline is calculated as (note may be a negative amount meaning balance is due to the Travel Agency):

Non-Credit Form of Payment Amount Less Commission Amount Plus Cancellation Penalty

= Remittance from Travel Agency to Airline All of the elements passed on the RET file from the ticketing system to ARC are passed through processing, and net ticketing is no different in this way to published fare ticketing.



3.2 BSP Net Remit Processing Net Reporting and Remittance through BSP will hereafter only refer to transactions strictly defined as ‘Net Remit’ (Net Remit Indicator NRID = ‘NR’). Any other net ticketing arrangement involving the reporting of private fares (e.g. IT, BT, BULK) does not involve any ‘special’ processing by the BSP, regardless of whether the transaction contains single or combined net fares or fare owners. These transactions are reported with a published and a net fare amount, and are all subject to the same validations that have been stated above in Section 2.3.1.



3.2.1 Net Remit Methods There are five Net Remit Methods which are referenced to Category 35 byte 33 in the Data Application (Method Code). If byte 33 is blank, the ticket is assumed to be either a published fare ticket or a net ticketing arrangement which does not involve a net remit scheme within the BSP (i.e. the Net Remit Indicator is blank on the reported ticket in the RET file). When the ‘Method Type’ (byte 33) is coded from 1-5, the data application references the following methods for indicating that a Net Remit transaction is being reported: Method Name Description

1 Value Coding A value code normally consists of one alphanumeric to denote the calculation type (see 3.2.2) followed by up to four numerics, which are an encrypted representation of the net fare, the commission percentage, or the commission amount.

2 Using the Fare Area of the Remittance Area When entered by the agent, the net fare is entered in the Fare Area of the Remittance Area (in practice the element AEBA is used).

3 Using the Commission Percentage of the Remittance Area The commission percentage is entered in the Commission Area of the Remittance Area (in practice the element CORT is used).

4 Using the Commission Amount of the Remittance Area The commission amount is entered in the Commission Amount Area of the Remittance Area (in practice the element COAM is used).

5 Contract A list of Commercial Agreement Reference numbers are maintained by the BSP and matched to itinerary details and/or the tour code on the RET. When applicable the CAR Code is printed in the Tour Code box and reported in the data element TOUR.

The Net Remit Method used is fundamentally linked to the calculation type which is explained below.



3.2.2 Net Remit Calculations The calculation denotes the way in which the rate and amount information either coded into the ticket or explicitly stated in the Remittance Area. There are 7 calculation types. Examples of each Method and Calculation combination can be found in the BSP Data Interchange Standards Handbook Chapter 12. The Calculation Types described below are linked to byte 34 (Gross/Net Indicator) which allows the carrier to specify in the Category 35 whether the Commission Rate should apply to the Gross (G) or the Net (N) fare value. If this byte is set to ‘G’, the fare must be reported in a country which supports Calculations A-D, and if this byte is set to ‘N’, the fare must be reported in a country which supports Calculations E-G (in practice E and F are not listed as in use today). Note also that the relationship of Category 35 to the Commission Type element discussed above is as follows: Category 35 byte 34 = ‘G’ (calculate commission on gross) translates to Commission Type = blank Category 35 byte 34 = ‘N’ (calculate commission on net) translates to Commission Type = ‘N’ Note that the below relates to BSP calculations in formulating the HOT file to airlines. Calculation Data Required

(Either Value Code, Contract Code, or Remittance Area)

Standard Commission

(COAM)

Supplementary Commission

(SPAM)

Net Fare Amount

(NTFA) A Net Fare Amount Based on Gross Fare COBL (Commissionable

Amount) -COAM-NTFA Agreed Amount

B Supplementary Rate Based on Gross Fare Calculated by applying Supplementary Rate to the

Gross Fare less COAM

COBL-COAM-SPAM

C Total (Effective) Rate Based on Gross Fare Based on Gross Fare COBL-COAM-SPAM D Supplementary Amount Based on Gross Fare Agreed Amount COBL-COAM-SPAM E Gross Fare less

Supplementary Amount Based on Agreed COBL-

SPAM Agreed Amount COBL-COAM-SPAM



In practice the Commission Calculation will be based on the Net Remit Calculation (A-E) which the carrier has selected in the particular BSP country of sale, and this will apply whether the Gross/Net Indicator is consistent on the ticket, or is mixed in the case of Category 10 allowed combinations. These remaining calculations are also available, but are not currently in use in the marketplace today. Calculation Data Required

(Either Value Code, Contract Code, or Remittance Area)

Standard Commission

(COAM)

Supplementary Commission

(SPAM)

Net Fare Amount

(NTFA)

F Gross Fare Less Supplementary Amount

Based on COBL-SPAM Based on Gross Fare COBL-COAM-SPAM

G Supplementary Amount Based on COBL-SPAM Agreed Amount COBL-COAM-SPAM All of the above calculations are related to the country of sale, and as such airlines do not have a free choice of Net Remit Method Type and Net Remit Calculation to use. Generally the BSP in the country of sale will offer a finite listing from which the validating carrier can select the preferred methodology for Net Remit processing.



3.2.3 Net Remit Methods in Use In practice, only the following methods are currently supported today by BSP Operations. These terms are widely used below and so are defined: Term Definition Description A.A. Agreed Amount Agreed amount constituting gross fare less supplementary commission COAM Commission Amount Financial amount of standard commission on the transaction COBL Commissionable Amount The financial amount to which standard commission rate will be applied CORT Commission Rate The rate of standard commission to be applied EFCO Effective Commission Total commission constituting standard plus supplementary amounts EFRT Effective Rate Total commission rate constituting total commission divided by commissionable amount NTFA Net Fare Amount The calculated Net Fare where Net Remit Method Type is non-blank SPAM Supplementary Amount Financial amount of supplementary commission on the transaction (over standard) SPRT Supplementary Rate The rate of supplementary commission to be applied TDAM Ticket Document Amount Fare amount plus taxes TMFA Tax Misc. Fee Amount Financial amount of each tax listed individually



The following table shows which methods are used, followed by a sample calculation with the relative impact upon the net fare amount due to the carrier. Once again the assumption is that this table represents BSP processing and so not all of the fields seen below are reported in the RET file, some are exclusively calculated by the BSP for inclusion on the airline HOT:

Net Remit Method

and Calculation

Number of Countries

Assumptions Step Amount Category 35 Assumptions

1A 28 Gross = 1,500.00 Net Fare is Agreed = 1,000.00 Value Code = D1000 Standard Commission = 9%

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Net Fare from Value Code (NTFA) Establish Standard Commission Rate from RET (CORT) Establish Commission Amount (COAM=COBL x CORT) Establish Effective Commission (EFCO=COBL-NTFA) Establish Supplementary Commission (SPAM=EFCO-COAM)

1500.00 1000.00

9% 135.00 500.00 365.00

Byte 33 Method Type = ‘1’ Byte 34 Net/Gross Ind = ‘G’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 105 Type = ‘V’ Bytes 106-120 Tour Code = ‘D1000’ Agreed Net = 1000

1B 21 Gross = 1,500.00 Supplementary Rate is Agreed = 20% Value Code = C20 Standard Commission = 9%

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Standard Commission Rate from RET (CORT) Establish Commission Amount (COAM=COBL x CORT) Establish Supp Rate from Value Code (SPRT) Establish Supp Commission (SPAM={COBL-COAM} x SPRT) Establish Effective Commission (EFCO=COAM+SPAM) Establish Net Fare Amount (NTFA=COBL-EFCO)

1500.00 9%

135.00 20%

273.00 408.00 1092.00

Byte 33 Method Type = ‘1’ Byte 34 Net/Gross Ind = ‘G’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 105 Type = ‘V’ Bytes 106-120 Tour Code = ‘C20’ Agreed Net = blank

1C 16 Gross = 1,500.00 Supplementary Rate is Agreed = 20% Value Code = Z20 Standard Commission = 9%

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Supplementary Rate from Value Code (SPRT) Establish Standard Commission Rate from RET (CORT) Establish Commission Amount (COAM=COBL x CORT) Establish Supp Commission (SPAM=COBL x SPRT) Establish Effective Commission (EFCO=COAM+SPAM) Establish Net Fare Amount (NTFA=COBL-EFCO)

1500.00 20% 9%

135.00 300.00 435.00 1065.00

Byte 33 Method Type = ‘1’ Byte 34 Net/Gross Ind = ‘G’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 105 Type = ‘V’ Bytes 106-120 Tour Code = ‘Z20’ Agreed Net = blank

1D 18 Gross = 1,500.00 Supplementary Amount is Agreed = 100.00 Value Code = K100 Standard Commission = 9%

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Standard Commission Rate from RET (CORT) Establish Commission Amount (COAM=COBL x CORT) Establish Supp Amount from Value Code (SPAM) Establish Effective Commission (EFCO=COAM+SPAM) Establish Net Fare Amount (NTFA=COBL-EFCO)

1500.00 9%

135.00 100.00 235.00 1265.00

Byte 33Method Type = ‘1’ Byte 34 Net/Gross Ind = ‘G’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 105 Type = ‘V’ Bytes 106-120 Tour Code = ‘K100’ Agreed Net = blank

1E 12 Gross = 1,500.00 Gross less Supplementary Amount is Agreed = 1,000.00 Value Code = Q1000 Standard Commission = 9% applicable to agreed amount

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Agreed Amount from Value Code Establish Supp Amount from Value Code (COBL-A.A.) Establish Standard Commission Rate from RET (CORT) Establish Commission Amount (COAM=A.A. x CORT) Establish Effective Commission (EFCO=COAM+SPAM) Establish Net Fare Amount (NTFA=COBL-EFCO)

1500.00 1000.00 500.00

9% 90.00 590.00 910.00

Byte 33 Method Type = ‘1’ Byte 34 Net/Gross Ind = ‘N’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 105 Type = ‘V’ Bytes 106-120 Tour Code = ‘Q1000’ Agreed Net = 1000



Net Remit Method

and Calculation

Number of Countries

Assumptions Step Amount Category 35 Assumptions

2A 25 Gross = 1,500.00 Amount Entered by Agent = 1,000.00 Standard Commission = 9%

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Standard Commission Rate from RET (CORT) Establish Commission Amount (COAM=COBL x CORT) Establish Gross Less Commission (COBL-COAM) Establish Net Fare from RET AEBA (NTFA) Establish Supplementary Commission (SPAM=EFCO-COAM) Establish Effective Commission (EFCO=COBL-NTFA)

1500.00 9%

135.00 1365.00 1000.00 365.00 500.00

Byte 33 Method Type = ‘2’ Byte 34 Net/Gross Ind = ‘G’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 105 Type = ‘T’ Bytes 106-120 Tour Code = ‘ABCD’ Agreed Net = 1000

2E 22 Gross = 1,500.00 Gross less Supplementary Amount is Agreed = 1,000.00 Standard Commission = 9% applicable to agreed amount

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Agreed Amount from RET (AEBA) Establish Supp Amount from Value Code (COBL-AEBA) Establish Standard Commission Rate from RET (CORT) Establish Commission Amount (COAM=A.A. x CORT) Establish Effective Commission (EFCO=COAM+SPAM) Establish Net Fare Amount (NTFA=COBL-EFCO)

1500.00 1000.00 500.00

9% 90.00 590.00 910.00

Byte 33 Method Type = ‘2’ Byte 34 Net/Gross Ind = ‘N’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 105 Type = ‘T’ Bytes 106-120 Tour Code = ‘XYZ’ Agreed Net = 1000

3C 11 Gross = 1,500.00 Effective Commission = 33.33% Standard Commission = 9%

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Effective Rate from RET (EFRT) Establish Effective Commission (EFCO) Set Standard Commission to 9% (CORT) Establish Commission Amount (COAM=COBL x CORT) Establish Supp Commission (SPAM=EFCO-COAM) Establish Net Fare Amount (NTFA=COBL-EFCO)

1500.00 33.33% 499.95

9% 135.00 364.95 1000.05

Byte 33Method Type = ‘3’ Byte 34 Net/Gross Ind = ‘G’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 105 Type = ‘T’ Bytes 106-120 Tour Code = ‘XYZ’ Agreed Net = blank

3E 2 Gross = 1,500.00 Supplementary Amount is Agreed = 500.00 Standard Commission = 9% applicable to agreed amount

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Supp Amount from RET (SPAM=COAM2) Establish Agreed Amount (COBL-SPAM) Establish Standard Commission Rate from RET (CORT) Establish Commission Amount (COAM=COBL x CORT) Establish Net Fare Amount (NTFA=COBL-COAM-SPAM)

1500.00 500.00 1000.00

9% 90.00 910.00

Byte 33 Method Type = ‘3’ Byte 34 Net/Gross Ind = ‘N’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 105 Type = ‘T’ Bytes 106-120 Tour Code = ‘XYZ’ Agreed Net = 1000

5A 26 Gross Fare = 1,500.00 Net Fare is agreed = 1,000.00 Contract Code = ABCDEF123 Standard Commission = 9%

Establish Commissionable Amount (COBL=TDAM-TMFA) Establish Net Fare from Contract Tables (CARF) (NTFA) Establish Standard Commission Rate from RET (CORT) Establish Commission Amount (COAM=COBL x CORT) Establish Effective Commission (EFCO=COBL-NTFA) Establish Supplementary Commission (SPAM=EFCO-COAM)

1500.00 1000.00

9% 135.00 500.00 365.00

Byte 33 Method Type = ‘5’ Byte 34 Net/Gross Ind = ‘G’ Bytes 35-41 Comm % = ‘090’ Bytes 42-52 Comm Amount = ‘00000000’ Byte 106 Type = ‘T’ Bytes 106-120 Tour Code = ‘ABCDEF123’ Agreed Net = 1000

The column on the number of countries and the methods which they use will change, as BSP Operations are dynamic over time, but gives an indicator on which methods are the most popular.



The one fundamental difference which should be highlighted between Calculations A-D and Calculation E, is that Standard Commission is based on the Gross Fare for Calculations A-D whereas it is based on the Gross less Supplementary Commission for Calculation E. Calculation E therefore leads to a ‘net net’ effect as shown by the following: Gross Fare 1,500.00 Supplementary Amount 500.00 Subtotal 1,000.00 Less Standard Commission 90.00 Net Fare Amount 910.00 In this case: Commission Rate (CORT) = 00900 Commission Type (COTP) = ‘N’ Category 35 Byte 34 = ‘N’ In practice, Net Ticketing Agreements (i.e. non Net Remit private fares) are calculated similarly under some circumstances, with the standard commission amount deducted from the Category 35 ‘net’ fare which means the Net Submit to the carrier is lower. For the above reasons, there are two current practices which make the processing of net fares simpler in the marketplace:

(1) generally the travel agency reports Net Ticketing transactions as cash (2) standard commission tends to be zero such that the selling fare less the net fare equals the total commission



3.2.4 Net Remit and Credit Card Forms of Payment In practice, net remit is generally prohibited for Credit Card forms of payment. It has however been implemented in some BSP countries to satisfy a local need. This is related to BSP reconciliation, which validates all transactions on the basis of the Form of Payment Amounts adding up to the Ticket Document Amount. Illustration 1 – Multiple Forms of Payment used for one ticket purchase Fare GBP 1,000.00 Taxes GBP 120.00 Ticket Document Amount GBP 1,120.00 Form of Payment 1 (CC) GBP 600.00 Form of Payment 2 (CA) GBP 520.00 Total Forms of Payment GBP 1,120.00 In the above example, assuming no commission or penalties, the airline expects to receive from the travel agency: Cash Form of Payment GBP 520.00 Either the BSP or the Airline will bill the Credit Card (assuming that the airline is the merchant) for the GBP 600.00 reported in the second form of payment field.



This established the fact that for the airline to correctly account for the transaction, the sum of the forms of payment must equal the ticket document amount. In reality the agency can report s fictitious ‘cash’ amount for any transaction as long as it sums to the total gross ticket document amount on the transaction. Illustration 2 – Selling Amount different to Gross and Net Amounts Agency sells ticket for cash (incl. tax) GBP 820.00 Net Fare Agreed GBP 400.00 Gross Published Fare (COBL) GBP 1,000.00 Taxes (TMFA) GBP 120.00 Ticket Document Amount (TDAM) GBP 1,120.00 Form of Payment Amount (FPAM) GBP 1,120.00 Commissionable Amount (COBL) GBP 1,000.00 Less Standard Commission (COAM) GBP 90.00 Less Supplementary Commission (SPAM) GBP 510.00 = Net Fare GBP 400.00 Plus Taxes (TMFA) GBP 120.00 Amount Remitted to Airline by Agency GBP 520.00 In the above example, the airline receives GBP 500.00, which was the agreed Category 35 filed net amount of GBP 400.00 plus taxes of 100.00 which the agency should remit to the passenger. Because the agency took payment from the customer in cash, or acted as the merchant in the credit card transaction and simply reported as cash, the agency was able to sell the fare for a markup of EUR 300.00 on the net fare.



The problem is related to Credit Cards, where the BSP or the Airline (where the Airline is the credit card merchant) must bill the Form of Payment Amount against the Credit Card form of payment. In the above example, without any adjustment, the customer would have been billed for the full form of payment amount – EUR 1,100.00 – when the fare was in fact purchased in good faith for EUR 800.00. To remedy this, as mentioned above, most BSP’s prohibit the use of credit cards in form of payment for net remit transactions. However, where this has been implemented as a local requirement, there is bespoke build within the Data Processing Center to create a ‘pseudo-cash’ form of payment to balance the difference for the airline. In this case, the agency would: Illustration 3 – Use of Credit Card to purchase Net Remit ticket Report FOP CC GBP 820.00 Ticket Document Amount GBP 1,120.00 The Credit Card would be billed for the GBP 820.00 The BSP then adds the following: Process FOP CC GBP 820.00 Add FOP CA (pseudo) GBP 300.00 Total FOP Amount GBP 1,120.00 Ticket Document Amount GBP 1,120.00 This is an ongoing restriction for carriers wishing to file a specified ‘selling’ fare with their Category 35, as in most markets it restricts the agency to a cash sale. Note that this issue also applies to Private Fares which have been filed with a selling and net amount. In practice the travel agency is required to report the selling fare such that it can be billed to the customer credit card.



3.2.5 Settlement Issues The following issues have been identified with settlement of net remit transactions between the Travel Agency and the Airline:

(1) When combined fares have been ticketed with multiple tour codes, only one tour code can be processed by the BSP to calculate the settlement amount. This is only an issue for Method 1 (Value Coding) and Method 5 (Contract Coding) Net Remit. Refer to Appendix A for ticketing rules relating to Category 35 combinations.

(2) When combined fares have been ticketed with multiple commission instructions, only one of these can actually be passed in the Remittance Area. The assumption is made that when commissions are different (i.e. combinations), the ticketing system will be able to calculate the applicable commission rate based on the calculated commission amounts, and report the correct commission and therefore net amounts to the airline will be correct. If this assumption is false, commission will either be under or overstated on the transaction depending upon which commission rate is reported, and depending upon the net remit calculation (agreed net amount will be unaffected). Refer to Appendix A for ticketing rules relating to Category 35 combinations.

(3) When combined fares have been ticketed with multiple fare owners, only one tour code can be used in the settlement process with the travel agency. Strictly speaking, the tour code should always be owned by the Validating Carrier (as they have the settlement relationship with the Travel Agency), but in practice this may not necessarily be the case. Refer to Appendix A for ticketing rules relating to Category 35 combinations.

(4) When combined fares have been ticketed which lead to conflicting instructions either for Net Remit Method Type or Net remit Calculation Type, the actual settlement of the ticket is driven purely by the Method Type and Calculation Type which the carrier has selected as supported by that particular BSP market. This is therefore driven by point of sale. Refer to Appendix A for ticketing rules relating to Category 35 combinations.

(5) When a selling fare has been specified in the Category 35, the agency is limited to reporting transactions as cash sales, which may be more of an issue when processing greater volumes of online transactions, which often require a credit card to be used as a form of payment. In practice this is an issue for all net remit transactions (whether a selling fare is specified or not) due to the prohibition of these form of payment types where the net remit indicator = ‘NR’.

(6) For net ticketing transactions, the travel agency must sell to the customer at the specified ‘gross’ fare if using the airline merchant agreement for credit card forms of payment, as this is the amount which will be billed to the customer credit card. Selling fare is not possible for such transactions unless reported using cash forms of payment.



4.0 Revenue Accounting

4.1 Accounting for Sales The process for accounting for sales data created from a Net Remit pricing instruction is no different to that for a published fare ticket, although the correct calculation of values may be more cumbersome. In terms of the feeds of sales data which have been mentioned above, the BSP and ARC settlement files are the only sales data sources which will give definitive net values for 100% of transactions. The ISR/TCN and Electronic Ticket data feeds give a certain amount of information to allow airlines to provision net values, and will vary in their accuracy. For this reason, airlines may attempt to re-calculate the net value of the ticket using the tour code field or other key itinerary data. As there is no indication in these sales data feeds of which Net Remit Method or Calculation was relevant to the ticket, this will also be merely an estimate until the net submission is received and accounted for. The BSP and ARC files are representative of the actual net submission and so must be accurate 100% of the time of the intent of the Travel Agency. For net remit tickets, airlines may account at net levels for their transactions, but more often will account for gross (published) values, standard commission and supplementary commission to coupon level in order to correctly gauge the cost of sales for these tickets. The cost of sale can be expressed as the published amount less the net submission amount. As all revenue accounting must be performed at the smallest possible unit of the fare product – namely the coupon – there are challenges to calculating net fare values when combined nets have been used. As there is only one tour code reported with the ticket, one published fare, and one net fare, establishing a correct discount per segment (unless contract coding has been set up based on the itinerary) can be problematic, and may involve some estimation based on balancing of the reported net submit value.



4.2 Fare Audit Net fares, as for any travel agency sold fares, are audited by airlines to determine whether the agency has stayed within the terms of the fare conditions sold with the product. Airlines will be required in this case to re-price the ticket including the relevant Category 35 used in pricing (i.e. assumes that the airline auditing system has the Category 35 data loaded). At this stage it should be noted that this will be made significantly easier to process if the development of Structured Fare Calculation takes place, to enable the fare auditing system to view the precise construction of the fare as ticketed, and to ensure that the correct rules and discounts were applied by the Travel Agency. Note that interpretation of tour codes will also be required in instances where Value Coding or Contract Coding determined the true net submission, again to ensure that the correct contracted rates were applied. If the net submit amount has not been correctly applied, or a higher net or published fare should apply to the fare product, the airline will issue an Agency Debit Memo through the BSP or through ARC to the Travel Agency in order to recoup these funds. Note that auditing issues will occur where combined fares are being audited, and some of the ticketing data has been lost. This may prevent the airline from referring back to the original instruction (e.g. missing tour code means that the airline may be unable to access the commission rates or true net intended for the fare).



4.3 Interline Billing Interline billing of net fares is widely practiced today. There is nothing different about the process of billing net fares and billing published fares (as the process is based around coupon billing rather than the fare product), and in fact the only complexity with nets is in the fact that airlines have bilateral net billing agreements which vary the calculation of which fare is used in the final coupon billing. This may also involve sharing net data with some carriers in the itinerary but not others (assuming that there is a third carrier in the itinerary). For this reason, carriers can specify a text field in the Fare, Equivalent Fare Paid, and Total Box – carrying forward into the Fare Calculation Area – to disguise the true net value from other carriers as required. As described above, the ISR/TCN process also strips out net information where the addressed carrier is not the Validating Carrier (and therefore by definition an interline partner), unless advised to share this data by the owning (Validating) carrier. The Validating Carrier is always assumed to be the party ‘owning’ the net information and the net submission with the Travel Agency.



4.4 Revenue Accounting Issues The following issues apply to Revenue Accounting for Category 35 priced transactions:

(1) Accounting for the transaction at coupon level cannot be accurately performed if there are combined net fares (i.e. more than one Category 35 in the itinerary). This can be resolved to transaction level today, but may require balancing at the coupon level.

(2) Auditing of the ticket is limited to the details which are included in the ticketing transaction, which without Structured Fare Calculation details are limited and do not include all of the necessary match fields required to accurately determine the applicable fare. For example, in combination fare examples a tour code will be missing from the reported ticket and as such reference back to the original Category 35 may not be possible without completely re-pricing the ticket.

(3) Interline billing and settlement of coupons in a transaction where the fare, equivalent fare, total, and fare calculation area have been replaced with a text value (e.g. ‘IT’) is problematic if:

a. There is more than one fare component b. There is only one fare component and the net information has been masked

In both such cases manual intervention is required to accurately price the coupon. (4) Interline billing of private fares and other nets is complicated by the fact that the end-user interline agreement dictates which

commission levels should be deducted from the reported fare in the billing process.



5.0 Post Ticket Processing For the purposes of this document, Post Ticket Processing involves any process which is performed based on a ticket transaction but removed from the time of the original pricing and ticketing. There are various processes which are explained below, namely:

(1) Ticket reissues (2) Ticket refunds (3) Ticket revalidation (4) Issuance of optional fees and baggage when performed away from the original ticket purchase

Any process which requires knowledge of an original transaction pricing detail is completely reliant on data elements included with the ticket (in general the Electronic Ticket Record, although some carriers are known to supplement this with ISR/TCN). Only by this method can the original ticket pricing solution, including match fields, be regenerated and applied to the subsequent transaction. The Category 35 does not contain specific rules relating to post-ticket pricing. Reissue and Refund rules would be held in the Category 31 and 33 respectively, and issuance of fees would be based on specific match criteria defined in the S5-S7 and B0-B4 records.



5.1 Net Ticket Reissues The reissue of a fare created using a Category 35 relies upon the reissuing system having access to the net fare level which was charged for the original ticket. In practice there are issues with both Net Ticketing and Net Remit transactions which need to be reissued, for the following reasons:

(1) The true selling fare is required to determine the form of payment amounts paid by the passenger for the original transaction. This may not be readily available for a Net Ticketing transaction, assuming that the fare has been disguised using a text entry in the fare box and the fare calculation area. This original selling fare at ticket level must be used to determine the additional collection or residual balance on the reissue. With the inclusion of ‘Base Fare Sell Amount’ in the Electronic Ticket record (for later versions of EDIFACT), this issue can be avoided. Without this information, the kiosk or agent performing the reissue transaction will be required to completely reconstruct the original fare. The ease of this process will depend upon whether the reissuing system is the same as the original ticket issuing system, as there will be inherently more original data present when the systems are the same.

(2) The selling fare is not known for Net Remit tickets. As such the reissue and calculations based on the reissue can only be performed on the Gross (ticketed) fare which will overstate the original amount paid by the passenger

Both of these scenarios can be prevented by adding an instruction in the Category 31 related to the same fare which does not allow any voluntary changes to the fare, or alternatively to only allow reissue at a specified location.



5.2 Net Ticket Refunds As stated above for reissues, the refund process also relies on perfect information based on the selling fare. In net ticketing scenarios, this may be available in the Electronic Ticket record, or at least in the Validating Carrier ticket database, but for Net Remit fares, refunding on one of the two amounts – Gross or Net – will either understate or overstate the refund to the passenger. Partial refunds present even more of an issue to the refunding entity, especially if the refund is attempted by a travel agency. For net tickets (IT) this may be possible in an automated environment as the selling fare is likely to be available, however for Net Remit tickets, where:

(1) The selling fare to the passenger is not known by the GDS system used by the agency (2) Refund may occur part-way through the itinerary requiring some re-calculation of the fare (3) Penalties must be applied based on rules filed manually or through Category 33

In these cases a fully automated refund is not possible, and as such these are likely to be either:

(1) Instructed in the Category 33 as ‘non-refundable’ (2) Referred to the Validating Carrier for a manual refund



5.3 Issuance of Fees for a Net Ticket The issuance of a fee against a net ticket is in practice no different to the issuance of fees against published fare tickets. All of the match criteria required for pricing of optional and baggage fees will be the same. However some consideration should be given to the fact that if the fee is percentage based, it needs to be priced on the basis of the correct fare.



5.4 Post Ticket Processing Issues In summary the following issues apply to the post ticket processes described above:

(1) When the true sell fare is not known by the system processing the transaction (e.g. for Net Remit transactions), reissues and refunds are completely reliant upon a manual calculation by the travel agency or referred to the Validating Carrier, or the prohibition of refunds and reissues in the automated rules instructed with those net fares.

(2) Net Ticketing was an issue in the days of paper tickets, where the fare was masked by the text entry on the passenger coupon, but the latest EDIFACT standards do allow for the net and sell fares to be retained in the Electronic Ticket Record, and as such should no longer be an issue for refunding or reissuing systems. In practice this depends upon the EDIFACT version which the original ticketing system and the reissuing or refunding system are using.

(3) In rare occurrences that a net remit transaction is issued in a market which allows credit card transactions on net remit, and a Ticketing Fee is charged, the fee (if percentage based) will bear no relation to the gross or the net fare reported to the Validating Carrier.



6.0 Glossary of Terms Term Definition Accountable Document A sold passenger document, such as a ticket or a Miscellaneous Charges Order. ACH Airlines Clearing House, the Air Transport Association (US) clearing house for interline funds for domestic

US journeys. ARC Airlines Reporting Corporation - entity responsible for managing travel agency ticketing, reporting, and

settlement for US Travel Agency sales. BDISG BSP Data Interchange Standards Group, the group reporting directly to JPSC which determines standards for

reporting of accountable sales transactions from ticketing system providers, through BSP, to airlines and credit card companies.

Billing and Settlement Financial completion of the transaction which ensures that the airline performing the service receives the funds for the airline selling the service.

BSP Billing Settlement Plan - the IATA entity responsible for settling funds and reporting accountable information between the travel agency and the airline, as well as controlling accountable ticket stock.

CAT Carrier Accounting Tape - file of accountable transactions sent from ARC to participating airlines. Coupon A portion of a ticket that is a record of a single flight transaction or segment for the customer. Generally, it

involves the point of boarding a single flight, to the point of disembarking that same flight. There are some exceptions, such as for unticketed points, where a single coupon may represent more than one physical flight. For revenue accounting purposes, this is the smallest unit to which the financial transaction can be broken down.

DISH Data Interchange Standards Handbook, the definitive guide of file standards and specifications for the BSP HOT file.

EDIFACT Electronic data interchange for administration, commerce and transport. The current standard used for messaging electronic ticketing information.

Fare Owner The fare of the marketing carrier for the "significant sector" of each fare component.

GDS Global Distribution System, a service provider that offers a distribution channel for fares and service products.



Term Definition HOT Hand Off Tape - file of accountable transactions sent from the BSP to participating airlines. Generally, a

HOT is structured by validating carrier, per country, per billing period, per currency and per agency.

Interline Any ticket which is sold by one airline, and has at least one sector operated by a different airline, is deemed to be 'interline'. The operating carrier bills the validating carrier for prorate shares of the journey.

ISR/TCN Industry Sales Record, sales data output by ATPCO to customer airlines containing inputs from airline reservation systems, GDSs (TCN), BSP HOT, and in the future ARC CAT information to create one blended output sales data file for customers.

JPSC Joint Passenger Services Council, the group that meets annually to approve the JPSC Resolutions changes that become effective on 1st June of the following year.

JPSC Resolutions Rules documented in the JPSC Resolutions Handbook which govern passenger service for airline–to-airline and airline-to-travel agency relationships.

JPTC Joint Passenger Ticketing Committee, which reports to the JPSC and determines resolution changes relating to ticketing practices.

Marketing Carrier At coupon level, the airline code used to brand the flight, as visible to the passenger.

Operating Carrier At coupon level, the airline code of the airline which is physically transporting the passenger from the coupon origin to the coupon destination.

PADIS Passenger and Airport Data Interchange Standards which lay out message structure and code content for various business messaging requirements.

RAM Revenue Accounting Manual, the specification which determines billing rules for interline transactions from airline to airline.

RET Reporting Tape - file of accountable transactions sent from ticketing systems to the BSP to be processed on to airlines.



Term Definition Revenue Accounting Processing sold and used airline ticketed data in order to produce sales and marketing analytical data, as well

as production of statutory accounts. Sales Reporting The data record of the accountable document sold which is passed to Revenue Accounting systems.

Ticketing The issuance of an accountable document, which serves as a record of the product purchased by the customer, and gives a record to all airlines involved in the itinerary of the services paid for and expected to be delivered.

Validating Carrier Validating Carrier means the issuing airline whose numeric airline code is reflected in the electronic transaction for the flight/value coupon(s).The Validating Carrier shall be the controlling and authorizing entity for Electronic Ticketing transactions.



Appendix A Rules for Combining Net Fares ATPCO has prepared the following tables to address combinations and ticketing. The tables provide guidelines for ticketing when presented with a possible combination of fares from the same or different carriers that have ticketing data in potential conflict. Those key ticketing data elements are Net Remit Method Type, Tour Code, Fare Box, and Fare Calculation. The tables below assume two fare components in the fare combinations. Carriers that do not want certain types of fare combinations to ticket can always prevent the combination itself using the restrictive capability in Category 10 (Combinations).

• Table 1 shows all possible combinations of ATPCO private fares (Category 15 or 35 fares) with other ATPCO private fares or public fares. For each combination, a decision is made on whether the transaction must auto-ticket.

• Table 2 shows a grid of net remit method types being the same or different with carriers in the combination being the same carrier or different. For each fares combination, a decision is made on whether the transaction must auto-ticket.

• Table 3 shows carriers on the combination as being same or different, Tour Codes being same or different. For each combination, a decision is made on whether the transaction must auto-ticket.

• Table 4 shows the fares on the combination with commissions being same or different. Fares shown are both ATPCO private fares (Category 15 or 35 fares) combined with other ATPCO private fares or public fares in all possible combinations. For each combination, a decision is made on whether the transaction must auto-ticket.

• Table 5 looks at the data used for Fare Calculation section of the ticket. Data presented here are carriers being the same or different, information in the fare box being text or fare amounts, and the results in the fare box and fare calculation area. For each combination, a decision is made on whether the transaction must auto-ticket.



The four tables are to be read in order. Each succeeding table assumes successful validation of data in the table above it. Scenarios involve same carrier and different carrier fares.

1. When looking at a possible combination of two fares, find types in Table 1. a. If Ticket = Yes, go to Table 2. b. If Ticket = No, then that fares combination will not auto-ticket.

2. In Table 2, take the fares that successfully passed ticketing in Table 1 and validate the BSP method types of those fares. (Blank is assumed for any public fare).

a. If Ticket = Yes, go to Table 3. b. If Ticket = No, then that fares combination will not auto-ticket.

3. In Table 3, take the fares that successfully passed ticketing in Table 2 and Validate Tour Codes for same or different carriers. a. If Ticket = Yes, go to table 4. b. If Ticket = No, then that fares combination will not auto-ticket.

4. In Table 4, take the fares that successfully passed ticketing in Table 3 and validate the Commissions for the two fares. a. If Ticket = Yes, go to Table 5. b. If Ticket = No, the fares combination will not auto-ticket.

All fares combinations taken to Table 5 will auto-ticket.

5. In Table 5 take the fares that successfully passed ticketing in Table 4 and Populate fare box and fare calculation as indicated. All fares combinations taken to Table 5 will auto-ticket.



TABLE 1: FARES IN COMBINATION

FARE 1 FARE 2 TICKET? IF YES, GO TO TABLE 2.

Cat 15 Public YES Cat 15 Cat 15 YES Cat 15 Cat 35 Security YES Cat 15 Cat 35 Net Remit NO Cat 15 Cat 35 Net Ticketing YES Cat 35 Security Public YES Cat 35 Security Cat 35 Security YES Cat 35 Security Cat 35 Net Remit NO Cat 35 Security Cat 35 Net Ticketing YES Cat 35 Net Remit Public NO Cat 35 Net Remit Cat 35 Net Remit YES Cat 35 Net Remit Cat 35 Net Ticketing NO Cat 35 Net Ticketing Public YES Cat 35 Net Ticketing Cat 35 Net Ticketing YES

Notes for Table 1 1. Cat 35 Security – Type L no 979 2. Cat 35 Net Remit – Method type 1-5 3. Cat 35 Net Ticketing – Method type blank



TABLE 2: NET REMIT METHOD TYPE

Carrier METHOD TYPE TICKET? IF YES, GO TO TABLE 3.

Same Same Yes Different Same Yes Same Different No Different Different No

Notes for Table 2 Method type for public fares=Blank



TABLE 3: TOUR CODE / VALUE CODE / CONTRACT CODE

Carrier Fare One Fare Two TICKET? IF YES, GO TO TABLE 4.

Same TC TC Yes Different TC TC Yes Same TC Blank Yes Different TC Blank Yes Same

TC-A TC-B

No

Different TC-A TC-B No Notes on Table 3 1. Agent input entry is considered the same tour code for all fare components (i.e. at time of pricing, agent enters a Tour Code and applies for all fare components). 2. Each Tour code is the resulting tour code for each fare component without regard to where it came from (Category 35 or 27). 3. Commission amounts from Cat 35 must match or no ticket. See Table 4.



TABLE 4: COMMISSION CHECK

Commission Reported from Carrier Data Fields in Category 35 or From Other Sources FARE 1 FARE 2 TICKET?

IF YES, GO TO TABLE 5 Public Cat 15 Private Yes (See NOTE 3) Public Cat 35 No Commission (Blank) Yes Public Cat 35 Commission No Cat 15 Private Cat 15 Private Yes Cat 15 Private Cat 35 No Commission (Blank) Yes Cat 15 Private Cat 35 Commission No Cat 35 Commission on Net Cat 35 Commission on Gross No Cat 35 Commission Cat 35 Same Commission Yes Cat 35 Commission Cat 35 Different Commission No NOTE:

1. Commission amounts are reported in the COAM and CORT data elements of the RET file.(See Section 2.3 of this document) 2. Category 35 Commission means a commission amount, including zero, is coded in the Category 35. 3. Public and Private Cat 15 assume same commission in this case.



TABLE 5: FARE CALCULATION

Carrier Fare One Fare Two TICKET? Fare box Fare Calc Same Text Text Yes Text Text Same Text IT Text BT Yes First Mixed Same Text Fare Yes Text Mixed Same Fare Fare Yes Total FC Same Fare Text Yes Text Mixed Different Text Text Yes Text Text Different Text IT Text BT Yes First Mixed Different Text Fare Yes Text Mixed Different Fare Fare Yes Total FC Different Fare Text Yes Text Mixed

data application negotiated fares – … · 3.2.4 net remit and credit card forms of ... the...

Documents