Ticketing Fees and Carrier-Imposed Fees Reference Maual Customer/rm... · Ticketing and Carrier-Imposed Fees Reference Manual Table of Contents iii December 2015 Table of Contents

Ticketing and Carrier-Imposed Fees Reference Manual Version 7

Ticketing and Carrier-Imposed Fees Reference Manual

Version 7 August 2017

2005 Airline Tariff Publishing Company. All rights reserved.

Ticketing and Carrier-Imposed Fees Reference Manual Table of Contents

iii December 2015

Table of Contents Ticketing Fees

Introduction to Ticketing Fees .................................................................................................. 1 Ticketing Fee Data .................................................................................................................... 2

Service Sub Code .................................................................................................................. 2 Sequencing ............................................................................................................................ 4 Effective/Discontinue Dates ................................................................................................. 5

Ticketing Fee Organization ....................................................................................................... 6 Ticketing Fees ....................................................................................................................... 7 Ticket Dates .......................................................................................................................... 8 Fare Basis and Frequent Flyer Status .................................................................................... 9 Journey Geographic Location ............................................................................................. 12 Bank Identifier (Form of Payment) ..................................................................................... 15 Pricing/Ticketing Input Request ......................................................................................... 16 Security ............................................................................................................................... 18

Ticketing Fees Examples ......................................................................................................... 21

Example 1. Ticket Dates, Amount, and Public Distribution ................................................... 21 Example 2. Free, Location, and Private Distribution .............................................................. 21 Example 3. “F” Type Sub Code, Locations 1 and 2 and Percent ............................................ 22 Example 4. “T” Type Sub Code, Amount and Account Code ................................................ 22 Example 5a. Identifying Credit Card Types ............................................................................ 23 Example 5b. Identifying Credit Card Types ............................................................................ 23 Example 6. Multiple Credit Card Types .................................................................................. 24 Example 7. Multiple Form of Payments within a Single Transaction ..................................... 25 Example 8. Multiple Sequences with Various Data ................................................................ 26 Figure 1: Order of Sequences .................................................................................................... 4

Ticketing and Carrier-Imposed Fees Reference Manual Table of Contents

iv 21 August 2017

Carrier-Imposed Fees Introduction to Carrier-Imposed Fees ...................................................................................... 1

Data Organization ................................................................................................................. 1 Service Record Key Data .......................................................................................................... 3

Service Type Code ................................................................................................................ 3 Sequencing ............................................................................................................................ 3 Effective/Discontinue Dates ................................................................................................. 3

Carrier-Imposed Fees Record S1 Provisions ............................................................................. 5 Fees/Journey ......................................................................................................................... 5 Sector/Portion of Travel ...................................................................................................... 11

Note Text Table 196 ................................................................................................................ 18 Carrier-Imposed Fees Examples.............................................................................................. 19 Validating Carrier Concurrence Table .................................................................................... 27

Validating Carrier ............................................................................................................... 27 Effective and Discontinue Dates ......................................................................................... 27 Marketing Carrier Table ..................................................................................................... 27 Fee Collection and Marketing Carrier Table ...................................................................... 28

Example 1. Travel Dates/Ticket Dates/Point of Ticket ........................................................... 19 Example 2. Journey Locations/Return To Origin .................................................................... 19 Example 3. Journey Locations With Via Point ....................................................................... 20 Example 4. Journey Locations/Sector Locations (Without Directionality) ............................. 20 Example 5. Journey Locations/Sector Locations (With Directionality) .................................. 21 Example 6. Portion of Travel Locations/Stopover Exception Time (Without Directionality) 21 Example 7. Portion of Travel Locations with International/Domestic Tag............................. 22 Example 8. Carrier Flight Restrictions/Passenger type/No charge ......................................... 22 Example 9. Sector Locations/Domestic/International Tag/No charge .................................... 23 Example 10. Portion of Travel Locations/RBD ...................................................................... 23 Example 11. Portion of Travel Locations/Fare Basis .............................................................. 24 Example 12. Percent Fee/International/Domestic Tag ............................................................ 24 Example 13. Itinerary Sector Counts For Fee Application Using Stopover/Connection Points ....................................................................................................................................... 25 Figure 1 ................................................................................................................................... 30 Figure 2 ................................................................................................................................... 30 Figure 3 ................................................................................................................................... 30 Figure 4 ................................................................................................................................... 31

Ticketing and Carrier-Imposed Fees Reference Manual Frequently Asked Questions

FAQ-1 1 April 2015

Table of Frequently Asked Questions

This table is organized by topic discussed within this document. A page reference is provided to navigate you to the answer for your query.

Ticketing Fees — First Steps What is Ticketing Fees? ........................................................................................................ T-1

What are Sub Codes? ............................................................................................................ T-2

Can I specify that data is private?........................................................................................ T-18

Are there any coding examples for Ticketing Fees? ........................................................... T-21

Ticketing Fees — Specific Fields and Processing What is the system assumption for Ticketing Fees?.............................................................. T-1

Are ticketing fees refundable? ............................................................................................... T-2

How can fees be expressed? .................................................................................................. T-7

How are Ticket Dates used? .................................................................................................. T-8

Can I specify that Ticketing Fees are based on a Frequent Flyer Status? ........................... T-10

Why is concurrence needed? ............................................................................................... T-11

How are the Journey Geo Locs used? ................................................................................. T-12

What is the Ticket Designator Table for? ............................................................................ T-16

What is Private Distribution? .............................................................................................. T-18

Do I need to include myself in the security table if I am the owning carrier? ..................... T-18

Ticketing and Carrier-Imposed Fees Reference Manual Ticketing Fees

T-1 28 March 2009

Introduction to Ticketing Fees ATPCO is leading the industry in automating the collection, distribution, and pricing of service fees. The latest addition to this suite of tools is Ticketing Fees. The ticketing fee product is used for instructing pricing systems how to collect ticketing/credit card service fees on a carriers’ behalf when they are the ticketing or “validating” carrier. Ticketing Fees supports both public and private distribution needs and is controlled by the validating carrier for each original ticket. Ticketing Fees uses an ATPCO Service Fees S4 record to control the application of the ticketing/credit card fees based on Travel Dates, Ticket Issue Date, Ticketing Channel, Journey Locations, Account Code, Ticket Designator, Passenger Type, and Fare Basis/Fare Basis Owner, and Frequent Flyer Status. These fees are not interlineable; however, marketing carrier interline travel is permitted on the tickets that are validated against this record.

If processing cannot resolve to an applicable Record S4 for the validating carrier on the ticket being processed, then the assumption is that there are no Ticketing Fees applicable to that ticket. Once processing resolves to an applicable Record S4 (within each unique Sub Code), the fee specified applies to the ticket. Currently, Ticketing Fees data only applies for initial ticket issuance (except for T-type sub codes T90–T99 that apply to voluntary reissue tickets only) and does not apply to revalidated, reissued, or exchanged tickets.

What is Ticketing Fees?

What is the system assumption for Ticketing Fees?


T-2 28 March 2009

Ticketing Fee Data

Service Sub Code Sub Codes are defined by the industry and can be descriptive in their naming standard. The first character of the Sub Code identifies the type of fee applicable for the record. An “F” indicates a Form of Payment fee, a “T” indicates a Ticketing Process fee, and an “R” indicates a Requested Service Fee. Use the Sub Code appropriate for the type of service to which you want Ticketing Fees applied. For example, for paper tickets, you will use R05 which is defined as Paper Ticket.

All Ticketing Fees are considered consumed at the time of ticket purchase and therefore are not refundable.

For Form of Payment (F-type code), the second character is a letter C, which means credit card or charge card, and the third character is a letter A or a numeric number. The letter A indicates any credit card, and a specific number indicates that the credit card must begin with that number. For example, Sub Code FCA indicates any credit card is used, but Sub Code FC5 indicates that only credit cards beginning with the number 5 can be used (for example, 5555 7800 1234 5678).

Note: There is no plan initially to have any other code but C (credit) in the second character, and the numbers established represent all known initial digits of credit card numbers. If there is a business need to have a different second character or additional number, this will not be a quick change. Processing logic for the new Sub Code will have to be analyzed and reviewed by the industry. Upon approval, GDS systems will be given at least 2 months from issuance of bulletin to institute logic for a new Sub Code. Debit cards are not included in this phase because they are frequently only recognized in country of issuance.

For the Requested Service Type Sub Code (R-type code), the combination of the second and third character uniquely defines the Sub Code and can be numeric, numeric/alpha, or alphanumeric. The second and third characters have no ATPCO-defined meaning; however, you should use each Sub Code for the purpose it is intended, as described in this reference manual. For example, if you need to assess Ticketing Fees for courier charge, use the applicable Sub Code defined for courier charge (R02).

When you have a Ticketing Fee that is not a credit card fee or a requested service fee and that applies to original ticket issuance, use the T01–T20 values. T01–T20 fees apply only when a ticket is originally issued and are ignored when a ticket is reissued.

When you need to apply a Ticketing Fee to a ticket that is a reissue transaction, either from Category 31 (Voluntary Reissues) or otherwise indicated as a reissue transaction by your GDS, use the Sub Codes T90–T99. The Sub Codes T90–T99 apply when a ticket is reissued. Fees that applied to original transactions are not applied when a ticket is reissued; therefore, T01–T20 Sub Codes are ignored when processing a reissue transaction.

What are Sub Codes?

Are ticketing fees refundable?


T-3 28 March 2009

When you have Ticketing Fees that apply when the passenger makes certain requests, such as requesting a paper ticket, use the R- type Ticketing Codes to identify the specific request. The valid R- types are shown below.

Sub code Definition R01 Overnight Delivery Charge R02 Courier Charge R03 Tour Package Delivery R04 Travel Visa Acquisition Charge R05 Paper Ticket R07 Unaccompanied Minor (UMR) R08 Private Jet Ticketing 1 R09 Private Jet Ticketing 2


T-4 28 March 2009

Sequencing Within each unique Service Fees Sub Code, you should organize your Ticketing Fees data from most specific to least specific for the purpose of matching the itinerary being priced. Examine locations and other qualifying data to ensure you have the data positioned in the appropriate place to achieve the expected pricing results.

Among the sequences within a Service Fees Sub Code, the relationship is OR. The relationship of the data within a sequence is AND, meaning that all the conditions must be qualified to apply the fee.

Once a Sub Code sequence is matched, the system will not check the rest of the sequences for the same Service Fees Sub Code, but it will check the next unique Service Fees Sub Code for data to apply. Multiple unique Service Fees Sub Codes sequences may be applied to the ticket being validated.

Sub Code Travel Effective

Travel Discontinue

LOC 1 Journey Origin

Journey LOC1 LOC2 BIII

Amount/ Percent

CUR

Sequence Number

FC1 01AUG06 X LAX 10.00 USD 0010000 FC1 01AUG06 X NYC 10.00 USD 0020000 FC1 01AUG06 5.00 USD 0030000

Figure 1: Order of Sequences

Figure 1 illustrates the sequencing concept. The following is an explanation of the data.

• The first sequence is for journeys originating in LAX on/after 1 August 2006, apply a USD 10.00 charge for all credit cards starting with 1.

• The second sequence is for journeys originating NYC for on/after 1 August 2006, apply a USD 10.00 charge for all credit cards starting with 1.

• The third sequence is for all locations that are not previously addressed, on/after 1 August 2006, apply a USD 5.00 charge for all credit cards starting with 1.

• The LAX and NYC sequence must be positioned above the more general sequence (0030000) because it applies to all locations and is for the same Sub Code. If the LAX and NYC provisions are positioned after the generic sequence, subscribers will apply the USD 5.00 in sequence 30000 and never apply the USD 10.00 in the LAX and NYC sequence. This is because once the system finds a match within a Sub Code, it will not look for additional matches within the same Sub Code, only in different Sub Codes.


T-5 28 March 2009

Effective/Discontinue Dates When Ticketing Fees data is distributed, it becomes available for pricing immediately after being received and loaded by subscribers. The Effective and Discontinue Dates control the application of provisions that will apply based on the travel date of the passenger. The travel date is considered the departure date from the journey origin.

The journey’s departure date must be on or between the range defined by the Effective and Discontinue date in order for the fee to be applied.

Additionally, you can further control the application of the provision based on itinerary ticket issuance requirements (First and Last Ticket Dates). See the Ticket Dates section for more information.


T-6 28 March 2009

Ticketing Fee Organization The Ticketing Fee data is organized in this manner:

• Ticketing Fees

– Fees – Commercial Name

• Ticket Dates

• Fare Basis and Frequent Flyer Status

– Fare Basis and Frequent Flyer Status – Apply When Specified Fare Basis Appears – Carrier

• Journey Locations

– Journey Origin – Location 1/Location 2 – Via Location – Travel Wholly Within Location

• Bank Identifier

• Pricing/Ticketing Input Request

– Passenger Type – Ticket Designator Table – Account Code Table

• Security

– Private – Private Distribution – Security Table


T-7 28 March 2009

Ticketing Fees

Fees The ticketing fee can be expressed as free, as a specified amount, as a percentage of the total amount charge to a credit card, or as the base fare depending on the type fee. When specifying an amount or percentage, you can indicate whether the charge includes tax.

When specifying a percentage, you can further define that the fee collected will not exceed a maximum amount. When specifying the service is free, you can indicate whether or not this should be shown on the passenger’s receipt.

Percentages are applied differently according to the type of Sub Code they are used with. When a percentage is specified with a Form of Payment (F-type) Sub Code, it is a percentage of the total amount charged on the credit card.

When a percentage is specified with a Ticketing (T-type) or a Requested Service (R-type) Sub Code, it is a percentage of the converted base amount (as displayed in the Equivalent Fare Paid field in the e-ticket record). If there is no converted base amount, then it is a percentage of the Base Fare amount. For the Reissue Ticketing Fees Sub Codes T90–T99, the converted base amount and base fare amount information will be obtained from the new ticket.

Commercial Name You can use this field to indicate a commercial name for the Service Type Code used in the record. This is used for display purposes only and has no impact how Ticketing Fees are applied.

How can fees be expressed?


T-8 28 March 2009

Ticket Dates You can use Ticket Dates to further control the application of the fee based on the current dates in which the passenger ticket is being issued. You can define that the Ticketing Fees provision applies for tickets issued

• “on/after” a specific date (first ticket date) or

• “on/before” a specific date (last ticket date) or

• during a specific date range (first and last ticket dates)

The Ticket Dates can be earlier than the Effective and Discontinue Travel Dates of the segment because the fare can be ticketed before travel begins. See the Effective/Discontinue Date section for more information.

How are Ticket Dates used?


T-9 28 March 2009

Fare Basis and Frequent Flyer Status These fields are used to identify a Fare Basis and the associated significant (primary) carrier(s) required on the ticket or the Frequent Flyer Status for which the provision applies. The relationship among these fields is AND, meaning that all conditions must be met simultaneously.

When this group of fields is used for Frequent Flyer Status, the Carrier (Fare Basis) has no application.

Fare Basis You can restrict the application of the fee based on the value coded in the Fare Basis Box of the ticket. You must know how this data is displayed on the ticket in order to achieve the right results. In addition to alphanumeric characters, you can also use the special characters slash (/), hyphen (-), and asterisk (*). These characters can be used together to achieve different results. See the chart on the next page for examples.

Slash (/): A slash is used to separate the fare class from the ticket designator. Up to two slashes (/) may be present in order to identify a first and second ticket designator. Anything preceding the slash (or the left-most slash if two are present) represents the fare class; anything after the slash represents the ticket designator.

Hyphen (-): A hyphen is used as a wildcard to represent any alphanumeric characters in the fare class portion of the Fare Basis Code. Use this if you want to qualify multiple fare classes. This is the same type of concept that is used in Automated Rules. The hyphen can never be used to match a slash entry (ticket designator). When a hyphen is present with no slash, the Fare Basis Code on the ticket cannot have a ticket designator. The hyphen cannot be used to replace a number when immediately following or preceding character is also a number. For example, QH-12 matches QHAB12, QH33Z12, and QH12, but does not match QH312, QHAB123 or QH123M

Asterisk (*): An asterisk is used as a wildcard to represent any alphanumeric characters in the ticket designator portion of the fare basis. Up to 2 asterisks are permitted. Edits only permit an asterisk wildcard when preceded (directly or indirectly) by a slash (/). An asterisk is never used to match the fare class portion of the Fare Basis. Use this if you want to qualify multiple ticket designators.

Note: It is important that you verify that your GDS can handle ticket designators and can process wildcards.

The following chart illustrates how a Fare Basis entry in Service Fees matches to a corresponding entry in Fare Basis Box of the ticket:

Ticketing Record Entry Ticket Fare Basis Box Entry

Match (Yes/No)

QHXAP/CH QHXAP/CH YES (exactly as entered) QHXAPCH NO (fare class doesn’t match and no ticket designator) QHX/APCH NO (fare class doesn’t match and ticket designator doesn’t match)

QHXAP/ID/CH QHXAP/ID/CH YES (exactly as entered)


T-10 28 March 2009

Ticketing Record Entry Ticket Fare Basis Box Entry

Match (Yes/No)

QHXAPID/CH NO (fare class doesn’t match) QHXAP/IDCH NO (ticket designator doesn’t match)

QA7-CH QA7CH YES (hyphen does not require a character to be present) QA7ECH YES (hyphen allows E) QA70CH NO (hyphen cannot replace a number; 7 does not match to 70)

K/CH/ID* K/CH/ID5 YES (fare class and ticket designator match and asterisk matches other characters)

K/CN NO (ticket designator doesn’t match) K/CH9 NO (fare class matches but ticket designator doesn’t match)

BAP/*/30 BAP//30 NO (asterisk directly following a slash requires a character to be present)

BA/SR/30 NO (fare class does not match) BAP/37/ID NO (ticket designator does not match)

-/* YAP/CH YES (contains a slash, hyphen allows characters before slash, and the asterisk allows the characters after the slash)

YAP NO (entry does not contain a ticket designator) YAP/ID/CH YES (contains a slash, hyphen allows characters in front of slash,

and asterisk allows slash and characters at the end) -//* YAP/ID NO (does not contain two ticket designators)

Q//CN YES (hyphen allows characters before slashes, contains both slashes as entered, and asterisk allows characters after the slashes)

Q/ID/CH NO (slashes are not adjacent)

Frequent Flyer Status Frequent Flyer Status is used to specify that the Ticketing Fees data applies based on the passenger’s status within your Frequent Flyer Program. If this field is blank, then no Frequent Flyer Status restrictions apply.

Use 1 to indicate the highest ranking or level for your program (such as the most elite), 2 as the second highest, and so forth, with 9 being the lowest level (a general member of your Frequent Flyer Program). This number represents the minimum status required for the Ticketing Fee data to apply. For example, if you indicate level 4, the record applies to anyone who has at least a level 4 or greater status (1, 2, 3, or 4). If you indicate level 9 then the record applies to all levels (1–9).

Note: It is your responsibility to ensure that the subscriber and all parties involved know how the status numbers equate to your organization’s Frequent Flyer programs. This may require messaging between the parties involved to define the status number accurately.

Can I specify that Ticketing Fees are based on a Frequent Flyer Status?


T-11 28 March 2009

Apply When Specified Fare Basis Appears The values in this field are used for either the Fare Basis or Frequent Flyer Status.

When used for Fare Basis, this field specifies whether the data in the Carrier and the Fare Basis field are required on every sector of the ticket or at least one sector of the ticket.

When used for Frequent Flyer Status, this field indicates that the value specified in the Fare Basis/Status field is a Frequent Flyer Status.

Carrier (Fare Basis) This field is used in combination with a fare basis and only when the fare basis is not associated to the significant carrier or validating carrier (the owner of the Ticketing Fees Record) but is the fare basis of another carrier as indicated herein.

Note: The Carrier field cannot be used in combination with a Frequent Flyer Status, and edits are in place to prevent this.

To indicate that another carrier’s fare must be on the ticket to qualify as a match to this sequence, ATPCO requires prior written concurrence from that carrier. Concurrence data is maintained by ATPCO only, and edits are in place to prevent carriers being specified if concurrence is not authorized.

When the fare basis is a joint fare, the carrier indicated will apply to either carrier of the joint fare.

When the following data is used in combination with the Fare Basis field, it is applied as in this manner:

Carrier Apply When the Specified Fare Basis Appears on Result

Blank At least one coupon At least one coupon of the ticket must be on the Specified Fare Basis and the significant (primary) carrier of the Fare Basis is the Validating Carrier (Ticketing Fees owner)

Blank All coupons Every coupon of the ticket must be on the Specified Fare Basis and the significant (primary) carrier of the Fare Basis must be the Validating Carrier (Ticketing Fees owner)

XX At least one coupon At least one coupon of the ticket must be on the Specified Fare Basis and the Specified Carrier (XX).

XX All coupons Every coupon of the ticket must be on the Specified Fare Basis and the Specified Carrier (XX).

Note: The Ticketing Fees owner is not assumed to be a possible significant primary carrier when another carrier is specified; therefore, the ticketing fee owner must also be specified in another record if the intent is to allow itself as a primary carrier.

Why is concurrence needed?


T-12 28 March 2009

Journey Geographic Location The Journey Geographic Location fields are used to identify specific geographic restrictions for the journey. The relationship among the journey geographic provisions is AND. Location 1/Location 2 may be defined as an Area, Zone, Nation, State, City, or a User Zone Table.

Zone Table (178) provides the ability to define a group of geographic points based on your individual business needs. This is commonly referred to as a user-defined zone. A geographic location can be indicated as a City, State, Nation, Zone, or Area.

Data providers creating their own zone tables is not a new concept. At times, customers have specific business needs to identify groups of markets that all share the same application and thus should be established in a single set that is different from the standard ATPCO zones. When these situations occur, the customer may either create multiple records to identify each market or consolidate multiple markets that will have similar conditions into a unique zone.

Locations can be specified between two user-defined zones, between a user-defined zone and a standard geographic specification, or between two standard geographic specifications. When both locations are coded, the journey must match a location in each field.

There is not a one-to-one relationship but a one-to-many for the locations specified. For example, if Zone Table 1 contains BOS/CHI/NYC and Zone Table 2 contains IE/FR/IT, the resulting location matches are BOS—IE/FR/IT, CHI—IE/FR/IT, and NYC—IE/FR/IT.

It is not necessary to create a Zone Table if current ATPCO-defined zones are equivalent to the geographical locations needed. Zone Table 178 can be used instead of or in combination with the current geographic location fields. You can identify the journey as follows:

• Location 1 Journey Origin allows you to specify that the data in the Location 1 field identifies a journey origin or turnaround/destination point.

• Location 1/Location 2 allows you to target specific journeys

• Via Location allows you to specify the via location points on the journey

• Travel Wholly Within allows you to restrict the journey to travel wholly within a specified location

Location 1 and Location 2 Use Location 1 and Location 2 to restrict the origin and turnaround point or destination point of your journey. The term turnaround point applies to round-trip journeys, while the term destination point applies to one-way journeys. If you want to be specific on which location is the journey origin or the journey turnaround point/destination point, indicate your preference by selecting the Location 1 is Journey Origin indicator. If nothing is specified in Location 2, then all journeys that originate from Location 1 would apply.

Location 1 Journey Origin Select the Location 1 Is Journey Origin provision to indicate that Location 1 is the Journey Origin, or leave it blank to indicate that Location 1 is either the journey origin or the Journey Turnaround/Journey Destination.

How are the Journey Geo Locs used?


T-13 28 March 2009

When you indicate that Location 1 is the journey origin point, then it follows that Location 2, if present, is the turnaround point/destination point. When you leave this provision blank, then Location 1 can be either origin or turnaround point or destination point.

The following charts provide an explanation on how to use the location fields in conjunction with the indicator Location 1 Journey Origin. The round-trip journey chart is separate from the one-way journey chart.

For Round-Trip Journeys

Location 1 Location 2 Is Origin Indicated? Result

TPE LAX Yes Specifies a RT journey that originates in TPE with a turnaround point in LAX

TPE Blank Yes Specifies a RT journey that originates in TPE with no restriction on turnaround point

TPE LAX No

Specifies a RT journey that originates in TPE with turnaround point of LAX, or the reverse, origin LAX and turnaround point TPE

LAX TPE No The above result can also be achieved when locations are swapped

TPE Blank No Specifies a RT journey where TPE can be the origin or the turnaround point

For One-Way Journeys


TPE LAX Yes Specifies a OW journey that originates in Location TPE with a destination point in LAX

TPE Blank Yes Specifies a OW journey that originates in Location TPE with no restriction on destination point

TPE LAX No Specifies a OW journey that originates in TPE with a destination point of LAX, or the reverse, origin LAX and destination TPE


TPE Blank No Specifies a OW journey where the origin or destination is TPE

Travel Via Location Use the Travel Via Location if you require the passenger to travel via a specific location. The Via Location refers to a ticketed point on the journey that is neither a journey origin, a journey turnaround, nor a journey destination. The via point can on the inbound or outbound only or be on both outbound and inbound portion. The via location may be a connection or a stopover and must exist between Journey Location 1 and Location 2 when present.


T-14 28 March 2009

Travel Wholly Within Location Use Travel Wholly Within Location to indicate that all ticketed points of the journey must be within the location specified including the journey origin, journey turnaround, and journey destination points.


T-15 28 March 2009

Bank Identifier (Form of Payment) The Form of Payment Bank Identifier Bin Number further defines the specific credit card fee such as MasterCard or Bank of America Visa. This field cannot be used with Ticketing or Requested Sub Code types, because it has no application.

The first six characters of all credit card forms of payment can be used to identify the category of the entity that issued the credit card, the card brand (such as VISA), and the card issuer (such as Bank of America).

You can use an asterisk (*) as a wildcard value in the second through sixth characters in order to specify any number in its place. For example, value 12**** may be entered to indicate that at least one form of payment must be a card with a Bin Number starting with 12, value 1234** to indicate any card starting with 1234, or value 1***** to indicate any card starting with 1.

When used in combination with a Form of Payment type Sub Code, there is no cross-edit in place to require that a BIN number must begin with the same number as the Form of Payment number. For example, if you specify FC4 and BIN number 6*****, then your provisions will never be applied because they contradict each other.

When the Sub Code does not specify a form of payment and the Bank Number Identifier Bin Number is blank, there are no form of payment requirements and any form of payment can be applied.


T-16 28 March 2009

Pricing/Ticketing Input Request The following provisions are applied against the input command that priced the ticket (the requested passenger type, ticket designator, and account code) and are not applied against the actual fare selected.

Passenger Type This field is used to specify that the Ticketing Fees data applies based on the passenger type used in the input request; this does apply to the passenger type of the fare. Passenger Type mapping also applies, meaning that if passenger type CNN (accompanied child), it will “map” (apply) to any child/infant passenger type used in the request. When the Passenger Type is Blank there are no passenger type requirements for the Ticketing Fees; the fee will apply to all passenger types used in the input command.

Note: ADT (Adult) passenger type can not be used in the Passenger Type field in Ticketing Fees and an edit prevents this coding.

Ticket Designator Table Use this table to specify the Ticket Designator(s) that must be used in the pricing or combined pricing/ticketing input command. Ticket Designators are made up of 1 to 10 alphanumeric characters. Additionally, an asterisk (*) wildcard value can also be used to represent any alphanumeric set of characters in the Ticket Designator. If the Ticket Designator Table has no data, there are no restrictions on the Ticket Designator input command.

The following rules apply for the asterisk wildcard value:

• If used, the asterisk may appear only once, anywhere in the Ticket Designator The asterisk cannot be used to replace a number when the immediately following or preceding character in the Ticket Designator is also a number. Example: DE*16 matches DEC16, DEC33Z16, and DE3C16, but does not match DEC316, or DEC163

• When the asterisk is in the beginning or the middle, there is an assumed asterisk at the end. Example: *Q15 matches ABQ15XX and ABQ15XX50

• When the asterisk is in the beginning it must be replaced with at least one character and cannot be left blank. When it is in the middle or the end, it does not have to be replaced by a character. Example: *ZZ33 does not match ZZ33AB but does match to QZZ33A; QZZ*3 matches to QZZ3, QZZA3X; and QXZ7* matches to QXZ7, QXZ7YQ

• An asterisk may be present alone, with no other alphanumeric characters. When used alone, this indicates that at least one Ticket Designator must be in the input command (any ticket designator) in order to apply the data. Example: * matches ABCD, QZZ45, or any ticket designator used, but does not match to blank on the input command

What is the Ticket Designator Table for?


T-17 28 March 2009

Account Code Table This table provides the ability to positively specify Account Codes that should be compared to the Account Codes in a pricing or combined pricing/ticketed command. Account Codes are made to up of 1 to 20 characters (alphanumeric plus asterisk). If used, the asterisk acts as a wildcard (see below) and may appear only once, anywhere in the Account Code. When no Account Code Table exists, there are no restrictions on the account Code. The relationship among the different account codes within the table is OR.

When an asterisk (*) wildcard is used to represent any alphanumeric string of characters in the Account Code, the following rules apply for the asterisk wildcard value:

• The asterisk cannot be used to replace a number when the immediately following or preceding character in the Account Code is also a number. Example: AB*12 matches ABC12, ABC33Z12, and AB3C12, but does not match ABC312, AB312, AB123, or ABC123

• When the asterisk is in the beginning or the middle there is an assumed asterisk at the end. Example: *C21 matches ABC21XX and ABC21XX50; AB*ZZ matches ABCZZ21, AB123ZZQ, and ABCZZQ1

• When the asterisk is in the beginning it must be replaced with at least one character and cannot be left blank. When it is in the middle or the end, it does not have to be replaced by a character. Example: *AB12 does not match AB123; AB*ZZ matches ABZZ and ABCZZ; ABC* matches ABC and ABCDE12

• An asterisk may be present alone, with no other alphanumeric characters. This

indicates that at least one Account Code must be in the input command in order for the data to apply. If the input command does not contain an Account Code, then the data will not apply. Example: * matches ABCD and QZZ45


T-18 28 March 2009

Security

Public/Private You can indicate that the data in each sequence is public data or private data for the purposes of ATPCO distribution, subscriber (GDS) display, and security within the ATPCO application. It is assumed that the validating carrier can display its own private data.

If this field is blank, the record is public and available to all subscribers. Subscribers can permit anyone with access to their system to display the data.

When this field is specified, the record is private and will only be distributed subscribers you authorize. For private records, you must include a security table indicating who the data is available for sell. Subscribers will only make the data available to the locations/entities specified in the Security Table.

Private Distribution In many other applications, you must send an instruction to ATPCO to specify private distribution information, which is maintained by ATPCO in the ATPCO Data Distribution Control Directory (G30). With Ticketing Fees, ATPCO is providing you the capability within each segment to enter your own distribution information. Ticketing Fees does not use the ATPCO Data Distribution Control G30 Directory to hold this information. You have control over your distribution needs without having to instruct ATPCO. You also have the ability to specify the same or different private distribution information in each segment. Use this field to specify which subscribers can receive the private data. GDSs and carriers (including owning carrier) must be current subscribers and have a valid entry in the ATPCO G30 directory in order to be specified. If a carrier is specified, a GDS must also be specified. It is not necessary to specify yourself (the owning carrier) in the Private Distribution field to receive the data, but you must be a subscriber in order to receive it.

Security Table For private data, a Security Table (183) is required. The Security Table specifies the only entities that can display and sell the Ticketing Fee data (point of sale). It is assumed the Ticketing Fees owning carrier can always display its own data, however; you must include yourself in the Security Table in order to use the Ticketing Fee data in the market place.

For public data, a security table is not required and there are no restrictions on where and to whom the Ticketing Fees data applies when the Security Table is blank. When a security table is present, then the Ticketing fee data applies only to the entities specified.

The relationship of the data within a single row is AND, meaning all conditions must be applied together. The relationship of data across rows is OR, meaning conditions across rows are independent (apply this or apply this).

Within the security table you can specify the following:

• Travel Agencies • Carriers

Can I specify that data is private?

What is Private Distribution?

Do I need to include myself in the security table if I am the owning carrier?


T-19 28 March 2009

• GDS (Global Distribution System) • Duty/Function Codes • Geographic Locations • Airline Specific Codes • ERSP Numbers (Electronic Reservation Services Provider) • IATA Travel Agency Numbers • LNIATA (Line IATA Number/CRT Address) • Pseudo/Travel Agency Codes • Carrier/GDS Department Codes • Department Identifier

When Travel Agency is specified, Ticketing Fee data applies to any travel agency (including online agencies and traditional “brick and mortar” agencies).

The Carrier field in the Security Table is used to further define other security data. The fees are controlled by and accrue to the validating carrier (owning carrier of the record); therefore, you cannot specify a carrier other than the owning carrier of the record.

When you specify a GDS, it applies to anyone using the specified GDS system. This includes all travel agencies and owning carrier with access to the GDS system. If the intent is to apply this information to only travel agencies with access to the GDS system, then you must specify Travel Agency in combination with the GDS (within the same row of data).

The Duty/Function code specifies that the ticketing agent must be signed in using the specified duty/function code of the Carrier/GDS indicated. You must specify a carrier or GDS when Duty/Function contains data because the Duty/Function codes definition is GDS/carrier–specific. Examples of Duty Function codes are GS (General Sells) and SU (Supervisor).

You can indicate that the Ticketing Fees apply to specific locations by specifying geographic points (Area, Zone, Country, or State). When used in combination with other security data (within the same row), then geographic points apply only to the specified ticketing entity in that location.

Airline-Specific Security Type codes are a generic specification used to identify a large group of airline locations. The definition of these locations is dependent upon the data in the Carrier and GDS fields, as follows:

• If a carrier or GDS is not specified, the airline locations apply to locations of the Ticketing Fees Record owner:

– RES = All reservation centers for the Ticketing Fees Record owner – ATO = All airline ticket offices for the Ticketing Fees Record owner – CTO = All city ticket offices for the Ticketing Fees Record owner – WEB = Web site for the Ticketing Fees Record owner

• If a carrier is specified, the airline locations apply to locations of the carrier specified (only the Ticketing Fees Record owner can be specified):

– RES = All reservation centers for the specified carrier – ATO = All airline ticket offices for the specified carrier


T-20 28 March 2009

– CTO = All city ticket offices for the specified carrier – WEB = Web site for the specified carrier

• If a GDS is specified, the airline locations apply to locations of the Ticketing Fees Record owner using the specified GDS:

– RES = All reservation centers for the Ticketing Fees Record owner on the specified GDS

– ATO = All airline ticket offices for the Ticketing Fees Record owner on the specified GDS

– CTO = All city ticket offices for the Ticketing Fees Record owner on the specified GDS

– WEB = Web site for the Ticketing Fees Record owner on the specified GDS

Note: It is up to each subscriber to determine how to identify the locations indicated by the

RES, ATO, CTO, and WEB codes. Before using any of the above codes in Security Table 183, you should verify with subscribers that they are able to identify the locations.

The following are other Security Type codes used to who/where the Ticketing Fees data is applicable for:

Security Types Values Pseudo City Code – Travel Agency Up to six-character alphanumeric code IATA Travel Agency Number Eight-digit numeric IATA-assigned agency code Department/Identifier (requires an applicable carrier/GDS code)

Up to a seven-digit code indicating the airline department or CRS agency/department with leading zeros. If you type 123, the system will automatically add lead in zeros (0000123)

Carrier/GDS Department Code (requires an applicable carrier/GDS code)

Up to six alphanumeric characters

Electronic Reservation Service Provider (ERSP)

The eight-digit IATA-assigned ERSP code.

LNIATA Number (Line IATA Number, CRT/Terminal Address)

Up to eight alphanumeric characters.

Note: The IATA Travel Agency Code requires an eight-digit number in which the eighth

digit is a check digit. If only seven digits are provided, the system will automatically place a 9 at the end of the number (for example, if ‘0002345’ is entered, it will become ‘00023459’)


T-21 28 March 2009

Ticketing Fees Examples These examples illustrate different types of Ticketing Fee data entry intent. Assume that the following applies when carrier XX is the validating carrier (Ticketing Fees Record owner), unless otherwise specified.

It is assumed the Ticketing Fees owning carrier can always display its own data, however; you must remember to include yourself in the Security Table in order to utilize the Ticketing Fee data in the market place.

Example 1. Ticket Dates, Amount, and Public Distribution

Sub Code

First Ticket

Last Ticket

Amount/ Percent

CUR

Private

Private Distribution

FC1 01JUL06 01FEB07 5.00 USD FC1 02FEB07 01FEB07 5.00 USD

Result: A credit card fee of USD 5.00 applies for credit card numbers starting with 1, and when the departure from the priced/ticketed journey origin is on/after 01JUL06 and on/before 01FEB07. There is no restriction on distribution, so all subscribers are eligible to receive the data and there is no restriction on who can display and sell the data.

Example 2. Free, Location, and Private Distribution

Sub Code


Journey LOC1 L OC2

Security Table No Charge

Amount/ Percent CUR Private


FC1 LAX 123 Free Shown on receipt X 1A

Security Table 123

GDS Security Type Code Number

1A Department Identifier 1234567

Result: For Department/Identifier 1234567 using the Amadeus (1A) GDS system, no credit card fee applies for credit card numbers starting with 1. The data is allowed to be distributed to 1A. The data is available for display and sell by Department Identifier 1234567 using the 1A GDS system. The data owner XX can display the data, but is not eligible to use the data in the market place because they did not include themselves in the security table.

Are there any coding examples for Ticketing Fees?


T-22 28 March 2009

Example 3. “F” Type Sub Code, Locations 1 and 2 and Percent

Result: Apply a credit card fee of 5 percent of the total amount charged to credit card numbers starting with 5 when the priced/ticketed journey origin is LON and the journey turnaround/destination is Area 3. There is no restriction on distribution, so all subscribers are eligible to receive the data and there is no restriction on who can display and sell the data.

In this example, if the amount charged to the credit card was EUR 500.00, the fee would be EUR 25.00.

Example 4. “T” Type Sub Code, Amount and Account Code

Sub Code Amount/ Percent CUR

Account Code Table Private


T01 5.00 USD 1789

Account Code Table 1789

Account Code Table AB6789 AB123 12356BB

Result: A ticket issuance fee of USD 5.00 applies for account codes AB6789, AB123, or 12356BB. There is no restriction on distribution, so all subscribers are eligible to receive the data and there is no restriction on who can display and sell the data.

Sub Code


Journey LOC1 L OC2

Amount/ Percent Private


FC5 X LON Area 3 005.0000


T-23 28 March 2009

Example 5a. Identifying Credit Card Types

Sub Code


Journey LOC1 L OC2 BIN



FCA 4023** 5.00 USD

Result: A credit card fee of USD 5.00 applies for credit card BIN numbers starting with 4023. There is no restriction on distribution, so all subscribers are eligible to receive the data and there is no restriction on who can display and sell the data.

In this case, if a customer uses a Visa credit card with number 4023 4567 8901 2345, as a form of payment, then a USD 5.00 fee will be applied.

Example 5b. Identifying Credit Card Types

Sub Code





FC4 5.00 USD

Result: A credit card fee of USD 5.00 applies for credit card numbers starting with 4. There is no restriction on distribution, so all subscribers are eligible to receive the data.

In this case, if a customer uses a Visa credit card number 4023 4567 8901 2345 then a USD 5.00 fee will be applied.

If both the FCA and FC4 Sub Codes are present together, then the customer will be charged a total of 10.00 because the Sub Codes are unique and both identify that the charge applies for the type of credit card being used. If your intent is to apply only one charge for the same type of credit card then you should only specify this using the generic FCA code and BIN number, or use the FC number specific Sub Code, but not both. An example using FCA with a BIN number is shown in Example 7.


T-24 28 March 2009

Example 6. Multiple Credit Card Types

Sub Code





FCA 40**** 5.00 USD FC5 3.00 USD FC6 7.00 USD

Result: The FCA sequence states that a credit card fee of USD 5.00 applies for credit card BIN numbers starting with 40. There is no restriction on distribution, so all subscribers are eligible to receive the data.

The FC5 sequence states that a credit card fee of USD 3.00 applies for credit cards starting with 5. There is no restriction on distribution, so all subscribers are eligible to receive the data.

The FC6 sequence states that a credit card fee of USD 7.00 applies for credit cards starting with 6. There is no restriction on distribution, so all subscribers are eligible to receive the data.

In this case if a Visa credit card number 4023 4567 8901 2345 and another card that starts with 5 and a third card that starts with 6 is used. All three credit card charges will be applied for a total of USD 15.00.

If your intent is to apply only one charge for the same type of credit card, use only the generic FCA code and BIN number so you can organize the credit card fees in the order they should be applied (highest or lowest). An example using the FCA with a BIN number is shown in Example 7.


T-25 28 March 2009

Example 7. Multiple Form of Payments within a Single Transaction

Sub Code





FCA 40**** 5.00 USD FCA 5***** 3.00 USD FCA 6***** 7.00 USD

Result: The first FCA sequence states that a credit card fee of USD 5.00 applies for credit card BIN numbers starting with 40. There is no restriction on distribution, so all subscribers are eligible to receive the data.

The second FCA sequence states that a credit card fee of USD 3.00 applies for credit card BIN numbers starting with 5. There is no restriction on distribution, so all subscribers are eligible to receive the data.

The third FCA sequence states that a credit card fee of USD 7.00 applies for credit card BIN numbers starting with 6. There is no restriction on distribution, so all subscribers are eligible to receive the data.

If three different credit cards are used (matching BIN numbers 40, 5, and 6) within a single transaction, only one credit card fee will be applied because they are all within the same Sub Code. In the case above, the USD 5.00 fee would be applied.

If your intent is to charge the highest fee of the three, then you need to position the sequence with the highest fee before the other fees. For example, in the above situation, you would need to position the USD 7.00 for BIN numbers starting with 6 above the other fees and BIN numbers in order to apply the highest fee.


T-26 28 March 2009

Example 8. Multiple Sequences with Various Data

Rows Sub Code





Account Code Table

Security Table

Fare Basis/ Status

When Fare Basis Appears on

1 FCA Free, Not Shown on Receipt F- All Coupons 2 FCA Free, Shown on Receipt 3 Frequent Flyer Status 3 FCA 41**** 8.00 USD X XS/IA 558 123 4 FCA 4***** 10.00 USD X XS/1A 558 123 5 FCA 41**** 6.00 USD 6 FCA 4***** 8.00 USD 7 FCA 5.00 USD 8 R05 50.00 USD 9 T06 X US 5.00 USD 10 T06 7.00 USD 11 T90 10.00 USD

Account Code Table 558 AB*12

Security Table 123 Row Travel

Agency Carrier

GDS Duty Function

Type Location Security Type

Code Number

1 1A N US 2 X XS 3 XX Airline Specific Code RES

Security Table 234 Row Travel

Agency Carrier

GDS Duty Function

Type Location Security Type

Code Number

1 XX Airline Specific Code RES


T-27 28 March 2009

Result: (For this example, assume XX is the validating carrier). The row number below refers to the row number of the main data, not the additional tables.

Row 1 When all coupons on the ticket contain an XX fare basis beginning with F, there is no credit card fee and this is not shown on the receipt.

Row 2 When the passenger’s Frequent Flyer Status is at least 3 (passengers with frequent flyer levels 1, 2, or 3), there are no credit card fees and this is shown on the receipt.

Row 3 For points of sale located in the US using the 1A GDS system, a credit card fee of USD 8.00 applies for credit card BIN numbers starting with 41 for account code AB6789.

For account codes matching AB*12 (the asterisk is a wildcard and can replaced by one or more characters), a credit card fee of USD 8.00 applies for credit cards starting with BIN number 41, for points of sale located in the US using the Amadeus (1A) GDS system. The data is allowed to be distributed to 1A and XS. The data is available for display and sale by US locations using the 1A GDS system, for travel agencies only using the XS GDS system, and for carrier XX (data owner) reservation (RES) centers.

Row 4 For points of sale located in the US using the 1A GDS system, a credit card fee of USD 10.00 applies for credit card BIN numbers starting with 4 for account code AB*12. The data is allowed to be distributed to 1A and XS. The data is available for display and sale by US locations using the 1A GDS system, for travel agencies only using the XS GDS system, and for carrier XX (data owner) reservation (RES) centers.

Note: Positioning of data is very important. The data in Rows 2 and 3 are the same except for the BIN number and the fee. If the provision for BIN number 4 is positioned ahead of the provision for Bin number 41, the GDS would match any credit card starting with 4 (including 41) and apply the USD 10.00 fee instead of the fee that should be charged for cards starting with 41.

Row 5 A credit card fee of USD 6.00 applies for credit cards starting with BIN number 41. There is no restriction on distribution, so all subscribers are eligible to receive the data.

Row 6 A credit card fee of USD 8.00 applies for credit cards starting with BIN number 4. There is no restriction on distribution, so all subscribers are eligible to receive the data.

Note: Just as in Rows 2 and 3, positioning of the data is very important. Ensure you position the data in order of most specific to least specific. In this case, 41 is more specific than 4 and so appears first.

Row 7 A credit card fee of USD 5.00 applies for any credit card. There is no restriction on distribution, so all subscribers are eligible to receive the data.


T-28 28 March 2009

Row 8 A ticketing issuance fee of USD 50.00 applies for paper tickets. There is no restriction on distribution, so all subscribers are eligible to receive the data.

Row 9 A ticketing issuance fee of USD 5.00 applies for XX reservation (RES) centers when the ticketed journey origin is US. There is no restriction on distribution, so all subscribers are eligible to receive the data.

Row 10 A ticketing issuance fee of USD 7.00 applies for XX reservation (RES) centers. There is no restriction on distribution, so all subscribers are eligible to receive the data.

Row 11 A reissue ticketing fee of USD 10.00 applies. There is no restriction on distribution, so all subscribers are eligible to receive the data.

Ticketing and Carrier-Imposed Fees Reference Manual Carrier-Imposed Fees

F-1 21 August 2017

Introduction to Carrier-Imposed Fees ATPCO is leading the industry in automating the collection, distribution, and pricing of fuel and carrier-imposed fees. These fees are commonly identified as “YQ” and/or “YR” fees.

The primary data that is collected in the Carrier-Imposed Fees product is as follows:

1. Fuel and Carrier-Imposed fees —Marketing carriers can control the application of fuel and carrier-imposed miscellaneous fees at either sector (coupon) or a portion of travel (multiple sectors) with the capability to identify journey control.

2. Validating Carrier Concurrence Table—Validating carriers can express their concurrence or non-concurrence to the collection of fees on other marketing carriers participating on their ticket and to themselves when they are the marketing carrier. In the absence of this data for a validating carrier, the assumption is that all validating carriers concur to collecting their own fuel and carrier-imposed fees but non-concur to collecting other marketing carrier fees.

The Validating Carrier Concurrence Table can only be coded by ATPCO (free of charge), therefore you must instruct ATPCO with your Validating Carrier Concurrence information. ATPCO is also available to code your Carrier-Imposed Fees data for you at regular data input cost. Instruction Templates for Services/Concurring data are available on the ATPCO Web site in the Reference Library under Forms.

All data in Carrier-Imposed Fees is public data and available for distribution. Once the data has been released in subscriptions, any data provider or subscriber can view the data.

The Carrier-Imposed Fee Record S1 is based on and controlled by the marketing carrier of each segment, unlike the fuel/security/Q surcharge found in Surcharges (Category 12) in Automated Rules, which is based on the fare component and controlled by the fare owner. Carrier-Imposed Fees are marketing carrier–based regardless of who owns the fare, including YY fares.

Data Organization The main organizational key is the marketing carrier, and for each marketing carrier the data is grouped by the Service Type Code. At most, you will have two sets of Service Type Codes: one for or carrier-imposed fees (YQI or YRI), and one for fuel (YQF or YRF). (See the Service Type Code section for more information.)

The Service Type Codes are held at a sequence level, similar to Automated Rules. The provisions for Carrier-Imposed Fees are applied based on the effective and discontinue dates of the segment(s) within that Service Type Code sequence. Any information that cannot be accommodated within the automated fields provided can be included in a Note Text Table, for display purposes only.

https://applications.atpco.net/extranet/library/office/yqyr_template.xls


F-2 21 August 2017

The data is organized in this manner:

• Service Record Key Data

Service Type Code Sequencing Effective/Discontinue Dates

• Service Record Provisions

Fees and Journey Sector and Portion of Travel

• Note Text Table 196


F-3 21 August 2017

Service Record Key Data

Service Type Code Carrier-Imposed Fees are identified by a Service Type Code. The Service Type Code consists of a Fee Type and a Sub Code. You will need to determine which Fee Type to use for your fuel and/or carrier-imposed fees.

The Fee Type can either be “YQ” or “YR” (service fee).

The Sub Code is either “I” (carrier-imposed miscellaneous fee) or “F” (fuel).

For example, Carrier XX may use YQ for a fuel fee (that is, Service Type Code YQF), whereas carrier ZZ may use YQ for its carrier-imposed fee (that is, Service Type Code YQI).

The relationship of provisions within the different Service Type Codes (YQF, YQI, YRF, YRI) is AND. Normally you would have a fee for fuel or a carrier-imposed miscellaneous fee, and then further identify them using YQ or YR (YQF/YQI or YRF/YRI), or a combination thereof (YQF/YRI or YRF/YQI), but not all four for the same information. YQF and YRF are defined the same; therefore, the use of YQF or YRF is based on your preference. Likewise YQI and YRI are defined the same; therefore, the use of YQI or YRI is based on your preference or the preference of your GDS.

Note: Verify with your GDS any pricing and ticketing constraints they may have on the usage of YQ and YR service types; for example, if they require you to only use YR for fuel (YRF) and YQ for carrier-imposed fees (YQI), or if they require YQ for both carrier-imposed fees and fuel fees.

Sequencing Within each unique Service Type Code, use the sequence number to organize your Carrier-Imposed fee data from most specific to least specific. Examine your journey provisions and sector/portion of travel provisions and assign higher sequence numbers to more general data. Exceptions to these provisions are assigned lower sequence numbers so that they precede more general fee conditions.

Among the sequences within a Service Type Code, the relationship is OR. The relationship of the data within a sequence is AND, meaning that all the conditions must be qualified to apply the fee. Once a sequence identifies the carrier’s intent for the fuel or carrier-imposed fee on a sector, the fee in the sequence will be applied for that sector.

The system will not check the rest of the sequences for the same Service Type Code for that sector, but it will check the next unique Service Type Code. For example, you can have a YQF (fuel) sequence applying a USD 2.50 fee on a sector and a YQI (carrier-imposed) sequence applying a USD 9.00 fee on the same sector.

Effective/Discontinue Dates When the data is distributed, it immediately becomes available for use. The Effective/Discontinue dates control the application of provisions (segments) will apply based on the travel date of the passenger. The travel date is determined by the departure date from the journey origin.


F-4 21 August 2017

The journey’s departure date must be on or between the range defined by the Effective and Discontinue date in order for the fee to be applied.

Additionally, you can further control the application of the provision based on itinerary ticket issuance requirements (First and Last Ticket Dates). See the Ticket Dates section for more information.

Fee Type

Sub Code

Sequence Number

Travel Effective

Travel Discontinue

Sector Locations

Fee Application

Amount and Currency

YQ F 0030000 01JUL05 31JUL05 MNL LAX Per Sector 2.50USD YQ F 0030000 01AUG05 --------- MNL LAX Per Sector 3.00USD YQ F 0040000 01JUL05 31JUL05 PH US Per Sector 2.00USD YQ F 0040000 01AUG05 --------- PH US Per Sector 2.50USD YQ I 0030000 01JUL05 31JUL05 MNL LAX Per Sector 2.50USD YQ I 0030000 01AUG05 --------- MNL LAX Per Sector 3.00USD YQ I 0040000 01JUL05 31JUL05 PH US Per Sector 2.00USD YQ I 0040000 01AUG05 --------- PH US Per Sector 2.50USD YR I 0030000 01AUG05 ---------- PH US Per Sector 2.50USD

The chart above illustrates the sequencing and segment concept. The following explanation focuses on the first two sequences to clarify the concept of segments and sequencing of data.

• Carrier XX uses Fee Type YQ for their fuel fee and carrier-imposed fee.

• Sector MNL—LAX is more specific than sector PH—US, so MNL—LAX was assigned a lower sequence number 0030000.

• Within each sequence, two segments are defined to control the effective period of the fuel or carrier-imposed fee. In this example, the data in sequence 0030000 indicates that for XX sectors with departure from journey origin on or within 01JUL05 to 31JUL05, a fuel fee of USD 2.50 applies to the MNL—LAX sector, and for departure from journey origin on/after 01AUG05, a fuel fee of USD 3.00 applies.

• The first segment of sequence 0040000 indicates that for XX sectors with departure from journey origin on or within 01JUL05 to 31JUL05, a fuel fee of USD 2.00 applies to PH—US sector. The data in the second segment of this sequence indicates that for XX sectors with departure from journey origin on/after 01AUG05, a fuel fee of USD 2.50 applies to the PH—US sector


F-5 21 August 2017

Carrier-Imposed Fees Record S1 Provisions Fee/Journey

• Carrier-Imposed Fees

• Ticket Level

• Point of Sale

• Point of Ticket

• Journey Geographic Location

Sector/Portion of Travel

• Geographic Location

• Connection Point Exception

• Stopovers/Connections

• Carrier Flight Table

• Reservation Booking Designators (RBD)

• Equipment

• Fare Basis

Note Text Table 196

Fees/Journey

Carrier-Imposed Fees

Fees Fuel and carrier-imposed fees can be expressed as free, as a specified amount, or as a percentage of the base fare. When specifying an amount or percent, you can indicate whether the charge includes tax or not. There are no constraints on currency or geography.

Note: If you specify a percentage of the base fare, it applies to wholly online tickets only.

Fee Application You must specify how you want the fee applied:

• Per Sector: Apply per sector (the fee can be applied to multiple sectors as defined in the Sector/Portion of Travel section

• Per Direction: Apply once for each direction of travel on the journey (outbound/inbound)

• Per Journey: Apply once for the journey


F-6 21 August 2017

Return to Journey Origin This is used to specify whether travel must or must not return to the journey origin (indicating the journey is “one-way” or “round-trip”). This relates to the type of journey, not the type of fare.

When you specify “must return to journey origin,” this means to apply the fee to a roundtrip journey. When you specify “must not return to journey origin,” this means to apply the fee to a one-way journey.

This field is used in combination with the Fee Application. Return to Journey Origin specifies the type of journey, while the Fee Application indicates how often to apply the fee for that journey. The following chart shows the valid combinations and results when used together.

Fee Application Must Return to Journey Origin Result Sector YES (round-trip) Apply fee for each sector on a round-trip journey Sector NO (one-way) Apply fee for each sector on a one-way journey Direction YES (round-trip) Apply fee by direction (once outbound and once

inbound) on a round-trip journey Direction NO (one-way) Apply fee by direction on a one-way journey Journey YES (round-trip) Apply fee once on a round-trip journey Journey NO (one-way) Apply fee once on a one-way journey

The following defines the concept of round-trip for a wholly domestic journey versus an international journey:

• For a journey that is wholly domestic, the destination point of the journey must be the same city as the origin city to qualify as a return to origin.

• For a journey that is international, the destination point of the journey must be the same country as the origin city to qualify as a return to origin.

Ticket Level

Ticket Dates You can use Ticket Dates to further control the application of the fee based on the current dates in which the ticket is being issued or reissued. The Ticket Dates define that the fee applies when tickets are issued or reissued:

• “on/after” a specific date (first ticket date) or

• “on/before” a specific date (last ticket date) or

• during a specific date range (first and last ticket dates)

The Ticket Dates can be earlier than the Effective and Discontinue Travel Dates of the segment because the fare can be ticketed before travel begins. See the Effective/Discontinue Date section for more information.


F-7 21 August 2017

Validating Carrier Table As the assumption for these fees requires that the validating carrier be the same as the marketing carrier, indicating otherwise requires data in both the Carrier-Imposed Fees Record S1 and in the Concurrence Record S2. The Concurrence Record S2 validating carrier must be instructed to ATPCO by that carrier and must be aligned to the information in your Carrier-Imposed Fees Record S1. If the information is not aligned, the GDS will not be able to apply the data.

The absence of a Validating Carrier Table assumes that fees can be collected by any validating carrier, subject to the existence of a corresponding Concurrence Record S2.

The Validating Carrier table can express a positive application or a negative application. When you express a negative application, you must follow it with a positive application, indicating that the validating carrier is any carrier ($$) except the negative carrier (shown in the example below).

Example

(Must be validating carrier XX or ZZ)

Application Carrier Blank XX Blank ZZ

Note: GDS processing will have applied the Concurrence Record S2 (validating record)

before this process. If you indicate that you, the marketing carrier, want to apply the fee when XX is the validating carrier, then XX validating carrier has to indicate in its Concurring record that they have agreed to collect your fees. See the Concurrence Table section for further explanation.

(Any validating carrier except carrier XX or ZZ)

Application Carrier Not Permitted XX

Not Permitted ZZ

Blank $$

It is an ATPCO standard coding practice that, when there are no carrier restrictions, the Validating Carrier Table is left blank. You should not code a Validating Carrier Table where the only entry is $$. A $$ should only be coded following a negative application.

Passenger Type If you want the fee to apply only to a specific passenger type, list the passenger type here; otherwise, leave it blank to apply to all passenger types. The Passenger Type Code here refers to the passenger type in the pricing request command that drove the ticket.


F-8 21 August 2017

Note: Passenger Type “ADT” is not a valid entry in the Passenger Type field and edits will prevent it.

Point of Sale Use the Point of Sale provision to specify that the fee applies only when the ticket is sold at a specific location and/or by a specific agency.

The location may be defined as an Area, Zone, Country, State, City, Airport, or with a User Zone Table Number, which permits grouping of multiple locations into a user-defined zone.*

When providing the Agency Code, you must also provide the appropriate Agency type, which can be a Pseudo City Code/Travel Agency or an IATA-assigned travel agency code.

• Pseudo City Code/Travel Agency: Up to six alphanumeric character code

• IATA Travel Agency Code: Eight-digit numeric IATA-assigned agency code

Note: The IATA Travel Agency Code requires an eight-digit number in which the eighth digit is a check digit. If only seven digits are provided, the system will automatically assign a “9” at the end of the number (for example, if “002345” is entered, it will become “0023459”)

Point of Ticket Use the Point of Ticket provision to specify that the fee only applies when ticketed at a specific geographic location. This provision allows the ticketing location to be different from the point of sale. The actual point of ticketing is defined as the geographic location (point) determined by the GDS that is actually generating a ticket for the fare. The geographic location may be defined as an Area, Zone, Country, State, City, Airport, or with a User Zone Table Number, which permits grouping of multiple locations into a user-defined zone.*

Journey Geographic Location The Journey Geographic Location fields are used to identify specific geographic restrictions for the journey. The relationship among the journey geographic provisions is AND. Location 1/Location 2 may be defined as an Area, Zone, Country, State, City, Airport, or a User Zone Table, which permits grouping of multiple locations into a user-defined zone.*

Data providers creating their own zone tables is not a new concept. At times, customers have specific business needs to identify groups of markets that all share the same application and thus should be established in a single set that is different from the standard ATPCO zones. When these situations occur, the customer has the option of either creating multiple records to identify each market or consolidating multiple markets that will have similar conditions into a unique zone.

* Zone Table (178) provides the ability to define a group of geographic points based on your individual business needs. This is commonly referred to as a user-defined zone. A geographic location can be indicated as a city, state, nation, zone, or area.


F-9 21 August 2017

Locations can be specified between two user-defined zones, between a user-defined zone and a standard geographic specification, or between two standard geographic specifications. When both locations are coded, the journey must match a location in each field.

There is not a one-to-one relationship but a one-to-many for the locations specified. For example, if Zone Table 1 contains BOS/CHI/NYC and Zone Table 2 contains IE/FR/IT, the resulting location matches are BOS—IE/FR/IT, CHI—IE/FR/IT, and NYC—IE/FR/IT.

It is not necessary to create a Zone Table if current ATPCO-defined zones are equivalent to the geographical locations needed. Zone Table 178 can be used instead of or in combination with the current geographic location fields. You can identify the journey as follows:

• Location 1 and Location 2 allows you to target specific journeys

• Location 1 Is Journey Origin allows you to specify directionality on Location 1 and Location 2

• Via Location allows you to specify the via location points on the journey

• Travel Wholly Within allows you to restrict the journey to travel wholly within a specified Location

Location 1 and Location 2 Use Location 1 and Location 2 to restrict the origin and turnaround point or destination point of your journey. The term turnaround point applies to round-trip journeys while the term destination point applies to one-way journeys. If you want to be specific on which location is the origin or the turnaround point/destination point, indicate your preference through the indicator Location 1 is Journey Origin. If nothing is specified in Location 2, then all journeys that originate from Location 1 would apply.

Location 1 Is Journey Origin Use the Location 1 Is Journey Origin provision to indicate that Location 1 is the Journey Origin, or the Journey Turnaround/Journey Destination.

When you indicate that Location 1 is the journey origin point, then it follows that Location 2, if present, is the turnaround point/destination point.

When you leave this provision blank, then Location 1 can be either a turnaround point or a destination point.

The following charts provide an explanation on how to use the location fields in conjunction with the indicator Location 1 Is Journey Origin. The round-trip journey chart is separate from the one-way journey chart.


F-10 21 August 2017

For round-trip journeys


TPE LAX Yes Specifies a RT journey that originates in TPE with a turn around point in LAX

TPE Blank Yes Specifies a RT journey that originates in TPE and no restriction on turn around point

TPE LAX No

Specifies a RT journey that originates in TPE with turn around point of LAX or the reverse, origin LAX and turn around point TPE


TPE Blank No Specifies a RT journey where TPE can be the origin or the turn around point

For one-way journeys


TPE LAX Yes Specifies a OW journey that originates in Location TPE with a destination point in Location LAX

TPE Blank Yes Specifies a OW journey that originates in Location TPE and no restriction on destination point

TPE LAX No Specifies a OW journey that originates in TPE with a destination point of LAX or the reverse, origin LAX and destination TPE


TPE Blank No Specifies a OW journey where the origin or destination is TPE

Journey Via Point Use Journey Via Point if you require the passenger to travel via a specific location. The Via Location refers to a ticketed point on the journey that is neither a journey origin, a journey turnaround, nor a journey destination, and does not have to be between Journey Location 1 and Location 2, when present. The Via Point may be a connection or a stopover and must exist between Journey Location 1 and Location 2, when present.

Travel Wholly Within Location Use Travel Wholly Within Location to indicate that all ticketed points of the journey must be within the location specified. All ticketed points include the journey origin, journey turnaround, and journey destination points.


F-11 21 August 2017

Sector/Portion of Travel The relationship of the data within this section is AND, and the relationship between this section and the Fee/Journey section is AND. All conditions in both sections must be met and qualified to apply the fee.

Geographic Specifications This section allows you to specify how locations or points on the tickets shall be used for applying the fee. Locations may be defined as an Area, Zone, Country, State, City, Airport, or with a User Zone Table Number, which permits grouping of multiple locations into a user-defined zone.

Sector/Portion of Travel Indicator The Sector/Portion indicator further defines how the locations in this section are to be used during the qualification process. You can specify whether the location applies to a sector or multiple sectors, known as portion of travel.

Specify “Locations Apply Per Sector” if you want to control the application of the fee on a single sector.

Specify “Locations Apply as a Portions of Travel” if you want to control the application of the fee on more than one consecutive sector. It is possible, however, that the portion of travel will match a single sector within the itinerary; it does not have to match more than one sector.

Within the Sector/Portion of Travel section of data, some fields can be used with both indicators (Sector or Portion of Travel) and some can only be used with the Portion of Travel. These are listed in the chart below.

Sector and Portion of Travel Portion Of Travel Only

Location 1 and 2 Via Location

From/To Stopovers/Connections

International/Domestic Stopover Exception

Carrier Flight Restrictions Connection Points Do Not Determine Sector Breaks

RBD

Equipment

Fare Basis

Note Text Table 196

Location 1/Location 2 Use the Location fields to specify that the fee applies to the sector/portion of travel from/to/between specific locations. Leave these blank if your intent is to apply the fee on any sector within the itinerary, unless otherwise defined by portion or fee application.


F-12 21 August 2017

From/To Use From/To to indicate directionality of the sector/portion of travel points specified in Location 1 and Location 2, for qualification purposes. Directionality is journey-based, not fare selection–based.

From/To Selection Location 1 Location 2 Result From Location 1 TPE LAX From TPE To LAX

TPE Blank From TPE To any location

To Location 1 LAX TPE From TPE To LAX

LAX Blank From any location To LAX

Blank TPE LAX Between TPE and LAX LAX TPE TPE Blank Between TPE and any point

Via Location Use Via Location in combination with the “Applies to All Portions of Travel” indicator to define a specific via point location on the ticket within the portion of travel.

You can specify that a specific via point location must be

• between two specific locations by specifying both Location 1 and 2, or

• between any two location by leaving Location 1 and 2 blank.

Note: When Portion of Travel Locations are used in combination with the Via Point and locations are specified, both locations are required.

You may also define whether the via point must be a Stopover or a Connection by using the stopover/connection indicator.

International/Domestic Use this to indicate if a sector/portion of travel must be international or domestic.

• “International” indicates that sector end points must be in different countries.

• “Domestic” indicates that sector end points must be in the same country.

The following are exceptions/clarification to these definitions:

• Travel between countries Russia—East of Urals (country code XU) and Russia (country code RU) is domestic.

• Travel between the countries the United States and Canada is international.

• Travel between countries in Scandinavia is international.

• Travel between a nation and its territory possessing its own Country Code is international (for example, the United States and Guam).

• Travel between a nation and its territory not possessing its own Country Code is considered part of the sovereign state and is domestic.


F-13 21 August 2017

Connection Point Exemption The Connection Point Exemption is used to indicate whether connection points determine sector breaks. It allows you to control how the fee is applied to a portion of travel and may only be used when the Sector/Portion of Travel indicator is specified as “Applies to All Portions of Travel.”

Fees will be applied to each sector within the portion of travel unless you indicate otherwise in this field. Leaving the “Connection Points Do Not Determine Sector Breaks” field blank results in a fee applied to each sector, even if the intermediate ticketed point is a connection.

If you want to indicate that the intermediate ticketed points are to be disregarded in applying the fee when they are connections, address it by setting this indicator. Such coding means that two sectors via a connection point will be considered one sector and two sectors via a stopover will be considered two sectors. For example, LON connecting PAR to FRA would be considered one sector, however if PAR is a stopover it is considered two sectors LON—PAR and PAR—FRA.

You can further define where this does or does not occur by using the Location fields. The following chart provides an overview of how the Location data works when connection points are exempted.

Exempt Connection Via Location Location 1 Location 2 Result Yes Blank Blank Blank Exempt all connection points

between any portions of travel Yes Blank TPE LAX Exempt all connection points

between TPE and LAX Yes HKG Blank Blank Exempt connection point HKG

between any portions of travel Yes HKG TPE LAX Exempt connection point HKG

between TPE and LAX

Stopovers/Connections Use Stopovers/Connections in combination with the Portion of Travel indicator to define that a via point between the sector locations must be either a connection or a stopover point as determined by the data in this field. If ticketed via points can be both a stopover and a connection, leave this field blank.

Select the “Connection” option to require that the via point(s) must be a connection. Select the “Stopover” option to require that the via point(s) must be a stopover.


F-14 21 August 2017

The following chart provides an overview of Location and Stopovers/ Connection combinations.

Stopovers/ Connections Via Location Location 1 Location 2 Result Connection HKG TPE LAX There must be a connection HKG between

portions of travel TPE and LAX Stopover HKG Blank Blank There must be a stopover HKG between

two sectors Connection Blank TPE LAX All ticketed points between TPE and LAX

must be connection points Stopover Blank Blank Blank There must be a stopover point between

two sectors

Stopover Exception (Time and Unit) When a Stopover Exception Time and Unit are not specified, the following assumption applies:

• A stopover occurs when an arrival at a ticketed point (including fare break points) is scheduled to depart more than 24 hours after the arrival time (local time).

• A connection occurs when an arrival at a ticketed point (including fare break points) is scheduled to depart 24 hours or earlier after the arrival time (local time).

You only need to use these fields when you want to override this assumption. Once you indicate a time and unit, you must tell the subscriber how this information is to be applied by indicating that it refers to either a stopover or a connection or by indicating that Connection Points Do Not Determine Sector Breaks.

Time defines the maximum amount of time at a ticketed point before that point becomes a stopover. Unit defines how the time is measured (minutes, hours, days, or months).

Note: When entering “000” in the Time field and “Day” as the Unit this signifies “same day.” A stopover occurs when there is an arrival at a ticketed point that is scheduled to depart later than the day of arrival. A connection occurs when there is an arrival at a ticketed point that is scheduled to depart on the same day (local time). Day in this case is defined as the calendar date of arrival.

See the examples below.

Time Unit Result 010 Hours When departure from a ticketed point is scheduled more than 10 hours after arrival (local

time), this point is a stopover When departure from a ticketed point is scheduled 10 hours or less after arrival (local time), this point is a connection

000 Days When departure at a ticketed point is scheduled later than the day of arrival, this point is a stopover. When departure is scheduled for the same day of arrival, this point is a connection.


F-15 21 August 2017

Carrier Flight Restrictions This is used to restrict the fee to specific carrier/flight requirements of a sector or portion of travel, based on what is defined in the Sector/Portion of Travel Indicator and Location fields.

The Marketing Carrier is always identified as the owner of a Carrier/Flight Table. The Carrier/Flight table allows you to enter multiple flights within a single table. The relationship among the different flights is OR. For example, the fee applies on flights 1000 through 1999 operated by carrier XX, or on flight 7115 operated by carrier XX.

The Carrier/Flight Table is used to define the following:

• Operating Carrier: Carrier that provides the flight service which can be the marketing carrier itself or a different carrier. When this field is blank, it is assumed that the operating carrier can be any carrier.

• Flight Number 1: A specific flight number (single or first number within a flight range) or any flight number of the marketing carrier.

• Flight Number 2: The second flight number within a flight range (for example, 1000–1999) of the marketing carrier.

Reservation Booking Designators (RBD) Use RBD to restrict the fee to specific Reservation Booking Designators (RBD) of a sector or portion of travel, based on what is defined in the Sector/Portion of Travel Indicator and Location fields.

A maximum of three RBD(s) can be entered and the relationship between these is OR (for example, B or BN or Y). The RBD can be entered as 1 or 2 alpha characters.

If you need to specify more than three RBDs, you can create additional sequences with the same provisions but different RBDs.

Equipment Use Equipment to restrict the fee to a specific type of equipment for a sector or portion of travel, based on what is defined in the Sector/Portion of Travel Indicator and Location fields. The valid codes for equipment are easily accessible through the online Help.

Fare Basis Use Fare Basis to restrict the fee to the value coded in the Fare Basis Box on a sector or portion of travel, based on what is defined in the Sector/Portion of Travel Indicator and Location fields. You must know how this data is displayed on the ticket in order to achieve the right results. In addition to alphanumeric characters, you can also use the special characters slash (/), hyphen (-), and asterisk (*). These characters can be used together to achieve different results. See the chart on the next page for examples.

Slash (/): A slash is used to separate the fare class from the ticket designator. Up to two slashes (/) may be present in order to identify a first and second ticket designator. Anything preceding the slash (or the left-most slash if two are present) represents the fare class; anything after the slash represents the ticketing designator.


F-16 21 August 2017

Hyphen (-): A hyphen is used as a wildcard to represent any alphanumeric characters in the fare class portion of the Fare Basis Code. Use this if you want to qualify multiple fare classes. This is the same type of concept that is used in Automated Rules. The hyphen can never be used to match a slash entry (ticket designator). When a hyphen is present with no slash, the Fare Basis Code on the ticket cannot have a ticket designator. A number is a single unit; therefore, a hyphen cannot represent part of a number.

Asterisk (*): An asterisk is used as a wildcard to represent any alphanumeric characters in the ticket designator portion of the fare basis. It must follow the slash and only one asterisk is allowed between slashes (for example, /*/). Use this if you want to qualify multiple ticket designators. Up to two asterisks are permitted, but only when the second asterisk is directly or indirectly preceded by a slash (that is, */*)

Note: It is important that you verify with your GDS that they can handle ticket designators and can process wildcards.


F-17 21 August 2017

The following illustrates how the Fare Basis entry in Service Fees matches to the entry in Fare Basis Box of the ticket:

Service Record Entry Ticket Fare Basis Box Entry

Match (Yes/No)

QHXAP/CH QHXAP/CH YES (exactly as entered) QHXAPCH NO (fare class doesn’t match and no ticket designator) QHX/APCH NO (fare class doesn’t match and ticket designator

doesn’t match) QHXAP/ID/CH QHXAP/ID/CH YES (exactly as entered)

QHXAPID/CH NO (fare class doesn’t match) QHXAP/IDCH NO (ticket designator doesn’t match)

QA7-CH QA7CH YES (hyphen does not require a character to be present)

QA7ECH YES (hyphen allows E) QA70CH NO (hyphen cannot replace a number; 7 does not

match to 70) K/CH/ID* K/CH/ID5 YES (fare class and ticket designator match and asterisk

matches other characters) K/CN NO (ticket designator doesn’t match) K/CH9 NO (fare class matches but ticket designator doesn’t

match) BAP/*/30 BAP//30 NO (asterisk directly following a slash requires a

character to be present) BA/SR/30 NO (fare class does not match) BAP/37/ID NO (ticket designator does not match)

-/* YAP/CH YES (contains a slash, hyphen allows characters before slash, and the asterisk allows the characters after the slash)

YAP NO (entry does not contain a ticket designator) YAP/ID/CH YES (contains a slash, hyphen allows characters in front

of slash, and asterisk allows slash and characters at the end)

-//* YAP/ID NO (does not contain two ticket designators) Q//CN YES (hyphen allows characters before slashes, contains

both slashes as entered, and asterisk allows characters after the slashes)

Q/ID/CH NO (slashes are not adjacent)


F-18 21 August 2017

Note Text Table 196 There is a single Note Text Table per segment, which is easily accessible when you are updating Service Fees/Journey and Sector/Portion of Travel data.

It is important to know that the Note Text Table 196 is not used in the automated pricing process because it is included as free-form text data without the explicit guidelines that are needed for the automation process. The only special characters that can be used in the Text Table 196 are the period (.), slash (/), and dash (-). This table is used to relay information in a non-automated form for display purposes.

The Note Text Table 196 cannot be the only data provided in a Carrier-Imposed Fees record sequence.


F-19 21 August 2017

Carrier-Imposed Fees Examples These examples illustrate individual fuel and carrier-imposed fee data entry intent, not the combined collection during processing. Some are listed as I (Carrier-Imposed) and some as F (Fuel) to show the two different types of fee collections.

Example 1. Travel Dates/Ticket Dates/Point of Ticket Marketing Carrier = XX

Service Type Code = YQI

Fee Fee Application

Travel Dates Ticket Dates Point of Ticket Result Effective Discontinue Effective Discontinue

2.50 USD Per Sector 15MAR05 Blank 01JAN05 15MAR05 GB For XX sectors, a YQI fee of 2.50 USD applies per sector, when the departure from the journey origin is on/after 15MAR05, and the ticket is issued on/after 01JAN05 and on/before 15MAR05, and the ticket is issued by anyone in GB.

Example 2. Journey Locations/Return To Origin Marketing Carrier = XX


Fee Fee Application Journey Returns to Origin

Journey Geographic Specification Result Location 1 is Journey Origin

Location 1 Location 2

5.00 USD Per Journey Yes Yes GB Blank For XX sectors, a YQI fee of 5.00 USD applies once per journey, when journey originates in GB, provided that travel on the journey returns to origin. Note: For international tickets, it must return to same country as journey origin. For domestic tickets, it must return to the same city as journey origin.


F-20 21 August 2017

Example 3. Journey Locations With Via Point Marketing Carrier = XX


Fee

Fee Application

Journey Geographic Specification Result Location 1 is

Journey Origin Location 1 Location 2 Via Point Travel

Wholly Within

2.50 USD Per Sector Yes LON AU DXB Blank For XX sectors, a YQI fee of 2.50 USD applies per sector when the journey origin is LON, the journey turnaround/destination is AU, and travel is via DXB

Example 4. Journey Locations/Sector Locations (Without Directionality) Marketing Carrier = XX


Fee

Fee Application

Journey Geographic Specification Sector/Portion of Travel Geographic Specification

Result

Location 1 is Journey Origin

Location 1 Location 2 From/To Location 1 Location 2

2.50 USD Per Sector Yes AU Blank Blank NZ AU For XX sectors, a YQI fee of 2.50 USD applies for sectors between NZ and AU when the journey origin is AU.


F-21 21 August 2017

Example 5. Journey Locations/Sector Locations (With Directionality) Marketing Carrier = XX


Fee

Fee Application

Journey Geographic Specification Sector Geographic Specification Result Location

1 is Journey Origin

Location 1 Location 2 From/To Location 1 Location 2

2.50 USD Per Sector Yes AU Blank From NZ AU For XX sectors, a YQI fee of 2.50 USD applies for sectors from NZ to AU when the journey origin is AU.

Example 6. Portion of Travel Locations/Stopover Exception Time (Without Directionality) Marketing Carrier = XX

Service Type Code = YQF

Fee

Fee Application

Sector/Portion Indicator

Sector/Portion of Travel Geographic Specification Result

From/To Location 1

Location 2

Via Location

Stopover/ Connections

Exception Stopover Time and Unit

3.00 USD Per Sector Applies to all portions of travel

Blank Z 210 Area 3 Z 210 Stopover 10 Hours For XX sectors, a YQF fee of 3.00 USD applies per sector on a portion of travel between Europe and Area 3 via a stopover in Europe. A stopover in Europe is defined as a point where departure from the point is scheduled more than 10 hours after arrival (local time).


F-22 21 August 2017

Example 7. Portion of Travel Locations with International/Domestic Tag Marketing Carrier = XX


Fee

Fee Application


Sector/Portion of Travel Geographic Specification Result

From/To Location 1

Location 2

International /Domestic

3.00 USD

Per Sector Applies to all portions of travel

Blank Z 210 Area 3 I For XX sectors, a YQF fee of 3.00 USD applies per sector on a portion of travel between Europe and Area 3 where every sector on the portion of travel is international.

Example 8. Carrier Flight Restrictions/Passenger type/No charge Marketing Carrier = XX


Fee

Fee Application

Passenger Type Code

Point of Ticket

Sector/ Portion Indicator

Carrier Flight Restriction Result

Operating Carrier

Flight Number 1

Flight Number 2

FREE Per Sector INF AU Applies per sector

XX 4000 4999 For XX sectors, there is no YQF charge for infant passengers ticketed in AU and on flights 4000 through 4999 operated by XX.


F-23 21 August 2017

Example 9. Sector Locations/Domestic/International Tag/No charge Marketing Carrier = XX


Fee

Fee Application


Sector/Portion of Travel Geographic Provision Result

From/To Location 1 Location 2 Domestic/International

FREE Per Sector Applies per sector

Blank SYD Blank Domestic For XX sectors, there is no YQF charge for XX domestic sectors from/to SYD

Example 10. Portion of Travel Locations/RBD Marketing Carrier = XX


Fee

Fee Application


Sector/Portion of Travel Geographic Specification

Result

From/To Location 1 Location 2 RBD 1 RBD 2 RBD 3 3.00 USD Per Sector Applies to

all portions of travel

Blank Z 210 Area 3 Y M B For XX sectors, a YQF fee of 3.00 USD applies per sector on a portion of travel between Europe and Area 3 where the RBD for each sector within the portion of travel is Y or M or B.


F-24 21 August 2017

Example 11. Portion of Travel Locations/Fare Basis Marketing Carrier = XX


Fee

Fee Application


Sector/Portion of Travel Geographic Specification

Result

From/To Location 1 Location 2 Fare Basis 2.00 USD Per Sector Applies to

all portions of travel

Blank Z 210 Area 3 Y- For XX sectors, a YQF fee of 2.00 USD applies per sector on a portion of travel between Europe and Area 3 where the Fare Basis for each sector within the portion of travel is fare family Y-.

Example 12. Percent Fee/International/Domestic Tag Marketing Carrier = XX


Fee

Tax Included

Fee Application


International/Domestic Result

10% Yes Per Sector Applies per sector

International For XX sectors, a YQF fee of 10% of the Base Fare applies to XX international sectors. The fee includes tax. Note: When a percent fee is provided, XX (you) must be the marketing carrier on all sectors of the ticket for the fee to apply.


F-25 21 August 2017

Example 13. Itinerary Sector Counts For Fee Application Using Stopover/Connection Points This example illustrates how the sectors are counted for fee application based on various data input for Connection/Stopover and whether Connection Points are exempt when determining fare breaks. (Entry samples are shown in different rows.)

Sample Itinerary = LON—FRA—SIN—BKK The fee will apply to this itinerary because a portion of travel originates in LON which is in Z 210, the turnaround BKK is in Area 3, and there is a via point of FRA in Area 2, matching the Service Fee requirements.

Fee

Fee Application


Sector/Portion of Travel Geographic Specification Result From/To

Location 1

Location 2

Via Location

Via must be a Stopover/ Connections

Connections Exempt

3.00 USD Per Sector Sector geography applies as a portion of travel

Blank Z 210 Area 3 Z 210 Blank YES (If FRA is a stopover) The ticket geography matches; because SIN is the first point in Area 3 it qualifies as the terminal point to be used to match the portion of travel. The fee is applied to two sectors, LON—FRA and FRA—SIN for the LON—SIN portion of travel. Total USD 6.00 because FRA is a stopover.


Blank Z 210 Area 3 Z 210 Connection NO (If FRA is a stopover) As the Via location had to be a connection and FRA was a stopover processing would continue to the next sequence and attempt to match again.


Blank Z 210 Area 3 Z 210 Stopover YES (If FRA is a stopover) The fee is applied to two sectors, LON—FRA and FRA—SIN for the LON—SIN portion of travel. Total USD 6.00 even though the connection is exempt because there are no connections in Europe.


F-26 21 August 2017

Fee

Fee Application


Sector/Portion of Travel Geographic Specification Result From/To

Location 1

Location 2

Via Location

Via must be a Stopover/ Connections

Connections Exempt


Blank Z 210 Area 3 Z 210 Blank Yes (If FRA is a connection) LON—SIN is the portion of travel that matches this sequence as the Via point FRA is in Europe. The fee is applied once as the connection exempt is set and FRA is a connection making the two segments a single segment. Total USD 3.00.


F-27 21 August 2017

Validating Carrier Concurrence Table The Concurrence Record S2 allows you, the validating carrier, to state your concurrence and/or non-concurrence to the collection of the fuel and carrier-imposed fees assessed by the marketing carriers participating on your ticket.

You, the validating carrier, can also specify whether you concur or non-concur to collecting your own fees when you are also the marketing carrier on your ticket.

Note: When you do not have a Concurrence Record S2, the assumption is that you concur to collecting your own fees but you non-concur to collecting other marketing carriers’ fees on your ticket.

Only ATPCO can update this data. ATPCO will create and maintain your concurrence data free of charge. Please use the Instruction Templates for Carrier-Imposed Fees when instructing ATPCO.

Once Concurrence provisions have been distributed in subscriptions, they are considered public information and are viewable online by anyone who has access to the application.

Validating Carrier This defines the validating carrier who owns and controls the record.

Effective and Discontinue Dates The Effective and Discontinue dates are maintenance dates that specify when this record is in effect. The dates must be “tomorrow” or later. When there is no specified discontinue date, record remains in effect.

Once this record is distributed in subscriptions it is available to be loaded by a subscriber immediately but the data cannot be applied until the effective date of the record. Unlike the Service Fee record, these are not travel dates.

The information contained within this record applies based on when tickets are being issued or reissued. The information in a record with a future effective date will not be applied unless ticket issuance/re-issuance is on or after the effective date of that record and on/before the discontinue date, if one exists.

Marketing Carrier Table The Marketing Carrier table is used to identify specific marketing carriers to which the validating carrier concurs. In the absence of this table, the validating carrier concurs to all marketing carriers and will collect as allowed by the marketing carriers’ in the Carrier-Imposed Fees Record S1.


F-28 21 August 2017

Fee Collection and Marketing Carrier Table For you, as the validating carrier, there are four basic scenarios for collecting fuel and carrier-imposed fees:

1. Collecting your own fees on your tickets The assumption for the product is that you can collect your own fees on your own tickets. No Concurrence Record S2 is required. The presence of the Carrier-Imposed Fees Record S1 with your carrier code means that, for sectors with your carrier code as the marketing carrier and where you are the ticketing carrier, the fees will be collected.

2. Not collecting any fees If you do not want any fuel or carrier-imposed fees collected on your tickets, then do not create any Concurrence Record S2 and do not create any Carrier-Imposed Fee Record S1.

3. Collecting another carrier’s fees in addition to your own For you to collect another marketing carriers fees, two things need to be in place:

• You, as the validating carrier collecting the fees, must have a Concurrence Record S2 created by ATPCO that states positively that you collect for yourself and the other marketing carriers. You must either name the marketing carrier in the Marketing Carrier Table or have a blanket positive agreement to collect on behalf of all carriers.

• The other marketing carrier must have a Carrier-Imposed Fees Record S1, and they must give permission for you to collect the fees, either by indicating this in a validating carrier table or by the absence of the validating carrier table.

4. Collecting another carrier’s fees but not your own To collect another marketing carrier’s fees but not your own, the following conditions must exist:

• You, the validating carrier, must have a Concurrence Record S2 created by ATPCO that states positively that you are collecting the other marketing carrier fees. This record must name the marketing carrier in the Marketing Carrier Table or have a blanket positive agreement to collect on behalf of all carriers. Additionally, the “Self” indicator must be set stating that the collection of fuel and carrier-imposed fees excludes your own fees.

• The other marketing carrier must have a Carrier-Imposed Fees Record S1 and they must give permission for you to collect the fees, either by indicating this in a validating carrier table or by the absence of the validating carrier table.

When you are the marketing carrier, for another validating carrier to collect your fees, two things need to be in place:

• You, the marketing carrier, must have Carrier-Imposed Fee Record S1 and must include a Validating Carrier table giving positive permission for the other carrier to collect the fees.


F-29 21 August 2017

• The other carrier, who is to collect the fees, must have a Concurrence Record S2 created by ATPCO that states positively that they are collecting your marketing carrier fees. This record must name you as the marketing carrier in the Marketing Carrier Table or have a blanket positive agreement to collect on behalf of all carriers.

The following chart describes the resulting Validating Carrier fee collection activity based on Concurrence Table data coding.

• S1 refers to the Carrier-Imposed Fees Record S1

• S2 refers to the Carrier-Imposed Fees Concurrence Record S2

Validating Carrier

S1 S2

If S2 exists, does Carrier Collect for Itself?

Marketing Carrier Table Result

NO NO N/A N/A Does not participate in Carrier-Imposed Fees. No fees are collected by the validating carrier for itself or other carriers.

YES NO N/A N/A Fees are collected by the validating carrier for itself only.

NO YES YES NO Fees can be collected by the validating carrier for any marketing carrier.

NO YES YES YES Fees are collected by the validating carrier for itself and for marketing carriers permitted in the Marketing Carrier Table.

NO YES NO NO Fees are collected by the validating carrier for any marketing carrier.

NO YES NO YES Fees are collected by the validating carrier for marketing carriers permitted in Marketing Carrier Table.

YES YES YES NO Fees are collected by the validating carrier for itself and any Marketing carrier.

YES YES YES YES Fees are collected by the validating carrier for itself and marketing carriers permitted in the Marketing Carrier Table.

YES YES NO NO Fees are collected by the validating carrier for any marketing carrier other than itself.

YES YES NO YES Fees are collected by the validating carrier for marketing carriers permitted in Marketing Carrier Table, but not for itself.


F-30 21 August 2017

The following illustrates how the instruction template should be completed to convey some common intentions.

Figure 1 XX concurs to collecting its own fees and for marketing carriers YY and ZZ only

Figure 2 XX concurs to collecting its own fees and for all other marketing carriers except for carriers YY and ZZ

Figure 3 XX non-concurs to collecting its own fees but it concurs to collect the fees for marketing carriers YY and ZZ


F-31 21 August 2017

Figure 4 XX concurs to collecting its own fees and all other marketing carriers’ fees

Ticketing and Carrier-Imposed Fees Reference Manual Glossary

G-1 April 2008

Service Fees Glossary This glossary defines terms as used in relation to ATPCO Service Fees.

international

At least two ticketed points are in different sovereign states.

journey turnaround point

The farthest stopover or fare break point, measured from the origin of the journey.

one-way journey

When the journey is wholly domestic (all ticketed points on the journey are in the same sovereign state), then a one-way (OW) journey is a journey where the destination point of the journey is not in the same point as the origin point of the journey.

When the journey is international (at least two ticketed points are in different sovereign states), then a OW journey is a journey where the destination point of the journey is not in the same country as the origin point of the journey.

portion of travel

A single sector or more than one consecutive sector of the same marketing carrier.

round-trip journey

When the journey is wholly domestic (all ticketed points on the journey are in the same country), then a round-trip (RT) journey is a journey where the destination point of the journey is the same point as the origin point of the journey.

When the journey is international (at least two ticketed points are in different countries), then a RT journey is a journey where the destination point of the journey is in the same country as the origin point of the journey.

Note: A ticket consisting of a circle pacific or Round the World fare component is considered a Round Trip journey when the fare component destination is in the same country as the fare component origin.

sector

A portion of journey covered by a single flight coupon.

ticketed point

A connection, stopover, or a fare break point.

validating carrier

The carrier whose ticket stock was used to issue the ticket (plating carrier). This carrier is commonly the holder of the money for the ticket.

wholly domestic

All ticketed points of the journey are in the same sovereign state.

Documents

Ticketing Fees and Carrier-Imposed Fees Reference Maual Customer/rm... · Ticketing and Carrier-Imposed Fees Reference Manual Table of Contents iii December 2015 Table of Contents