BEFORE THE

DEPARTMENT OF TRANSPORTATION

WASHINGTON, D.C.

Notice of IATA Traffic Conference

Actions Tentatively Exempted 

From Filing for Approval

Docket OST-2012-0058

SUPPLEMENTAL

NOTICE OF TIER 1 AGREEMENTS FILING

BY THE

INTERNATIONAL AIR TRANSPORT ASSOCIATION

11 May 2015

Communications with respect to this

Document should be sent to 

Douglas Lavin 

Regional Vice President – North America 

International Air Transport Association

1201 F Street, NW, Suite 650 

Washington, DC 20004 

(202) 628-9292
Summary DOCKET: DOT-OST-2012-0058 DOT ORDER: None Requested

Date: 11 May 2015

Filing fee/IATA Acct: Waived by Order 2012-4-18, Appendix 

A, Section D

US/UST involved Yes

Intended effective date: 1 June 2015 / procedural effective date 12 

June 2015

Meeting site, date: 36th Passenger Services Conference 

(PSC), San Diego, 13-14 October 2014

Agreement(s)/Minutes PSC/RESO/164 dated 11 May 2015

Resolutions 003, 720a, 722, 722f, 722g, 

722h, 725a, 725f, 725g, 725h, 725i, 728, 

743a, 754, 762, 765, 767, 780, 780e, 783, 

798a

Recommended Practices 1701h, 1706c, 

1707a, 1707b, 1708, 1719, 1719b, 1719c, 

1719d, 1719e, 1720a, 1743d, 1743e, 

1745, 1754, 1790b, 1791d, 1797
NOTICE OF TIER 1 AGREEMENTS FILING

Pursuant to statements submitted by Member airlines of the International Air Transport 

Association (IATA), the undersigned has been constituted to be their attorney-in-fact for filing 

with the Department of Transportation copies of agreements adopted by the IATA Traffic 

Conferences.

On their behalf, and pursuant to the procedures specified in Order 2012-4-18 (13 April 

2012), I am filing with the Department, in Docket OST-2012-0058, this Notice, the subject 

agreements and supporting documentation. These agreements are Tier 1 agreements tentatively 

exempted by Order 2012-4-18 from Condition #2 to the Department’s approval of the Provisions 

for the Conduct of the IATA Traffic Conferences, which condition requires pre-implementation 

Department review. The intended effective date of the agreements is 1 June 2015. 

The subject agreements amend or establish Resolutions and/or Recommended Practices 

that do not address subject areas which the Department has indicated it still chooses to review 

under Condition #2. The text of the agreements and other conference documentation sent to 

airline Members of IATA accompany this Notice. The cover pages of the documentation clearly 

identify each affected Resolution and/or Recommended Practice and show whether the subject 

agreements are amendments or new agreements. Other pages provide the text of each subject 

agreement. Where an affected Resolution or Recommended Practice has previously been 

exempted from Condition #2 by Department action, the cover pages include the appropriate 

docket and order number. The cover pages include a summary to explain the nature and purpose 

of the subject amendments and/or agreements.
Respectfully submitted,

 /s/ Douglas Lavin

Douglas Lavin

Regional Vice President – North America

International Air Transport Association

Attorney-In-Fact

- 2 -
CERTIFICATE OF SERVICE

A copy of this notice has been served this day by first class or priority mail on the 

following person:

Chief, Transportation, Energy & Agriculture Section

Antitrust Division

Department of Justice 

Washington, D.C. 20530

A copy of this notice has been sent this day by email to Esta Rosenberg

(Esta.Rosenberg@dot.gov) and to Della Davis (Della.Davis@dot.gov) of the Department of 

Transportation. 

 /s/ Douglas Lavin

Douglas Lavin

11 May 2015

Date Served

- 3 -
M E M O R A N D U M

PSC/RESO/164

To: All Members, Passenger Services Conference - Accredited 

Representatives

Copy: IATA Strategic Partners

From: Head, Airline Distribution Standards

Date: 11 May 2015

Subject: BOOK OF FINALLY ADOPTED RESOLUTIONS & RPs

36th IATA Passenger Services Conference (PSC)

San Diego, 13 – 14 October 2014

Attached are the resolutions & recommended practices (RPs) which were adopted at the abovementioned Conference.

The filing period is established as 11 May 2015 - 11 June 2015. To ensure timely approval, 

Members are requested to file these agreements, where required, with their Governments upon 

receipt of this document and to advise this office (email: mcewend@iata.org) of their Government’s 

action by the end of the filing period.

Filing formalities with the Canadian Transportation Agency on behalf of Canadian Members will be 

accomplished by this office.

Filing formalities with the United States Department of Transportation (DoT) on behalf of IATA 

Members will be accomplished by IATA’s Regional Vice President, North America. 

The intended effective date being 1 June 2015 due to late submission the actual intended 

effectiveness date will procedurally be exceptionally 12 June 2015.

David McEwen

International Air Transport Association

Route de l'Aeroport 33

PO Box 416

CH - 1215 Geneva 15 Airport

Switzerland

Tel: +41 22 770 2086

Fax: +41 22 770 2896

OUTLINE OF CONTENTS

RESOLUTIONS & RECOMMENDED PRACTICES

ADOPTED AT:

36th PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE: 1 June 2015

(procedural effectiveness date 12 June 2015)

Resolution/RP Title

PSC(36)003 STANDARD RECISSION RESOLUTION

PSC(36)720a

[OST-2012-0058]

PASSENGER TICKET AND BAGGAGE CHECK –

ISSUANCE AND HONOURING PROCEDURES

(amending)

PSC(36)722

[OST-2012-0058]

TRANSITIONAL AUTOMATED TICKET (TAT)

(amending)

PSC(36)722f

[OST-2012-0058]

ELECTRONIC TICKET – AIRLINE

(amending)

PSC(36)722g

[OST-2012-0058]

ELECTRONIC TICKET – NEUTRAL

(amending)

PSC(36)722h

[OST-2012-0058]

ELECTRONIC TICKET – GROUND HANDLING

(amending)

PSC(36)725a

[OST-2012-0058]

MISCELLANEOUS CHARGES ORDER (MCO) –

ISSUANCE AND HONOURING PROCEDURES BY 

MEMBERS

(amending)

PSC(36)725f

[OST-2012-0058]

ELECTRONIC MISCELLANEOUS DOCUMENT –

AIRLINE

(amending)

PSC(36)725g

[OST-2012-0058]

ELECTRONIC MISCELLANEOUS DOCUMENT –

NEUTRAL

(amending)
PSC(36)725h

[OST-2012-0058]

ELECTRONIC MISCELLANEOUS DOCUMENT –

GROUND HANDLING

(amending)

PSC(36)725i THROUGH/CHANGE OF GAUGE FLIGHT FOR EMD-A

(new)

PSC(36)728

[OST-2012-0058]

CODE DESIGNATORS FOR PASSENGER TICKET 

AND BAGGAGE CHECK

(amending)

PSC(36)743a

[OST-2012-0058]

FORWARDING MISHANDLED BAGGAGE

(amending)

PSC(36)754 PROFILES OF INTERLINE BAGGAGE CLAIMS AND 

PROOF OF FAULT FOR BAGGAGE PRORATES

(new)

PSC(36)762

[OST-2012-0058]

AIRLINE DESIGNATORS

(amending)

PSC(36)765 INTERLINE CONNECTING TIME INTERVALS—

PASSENGER AND CHECKED BAGGAGE

(amending)

PSC(36)767

[OST-2012-0058]

ASSIGNMENT OF AIRLINE ACCOUNTING CODES 

AND AIRLINE PREFIXES

(amending)

PSC(36)780

[OST-2012-0058]

IATA INTERLINE TRAFFIC AGREEMENT -

PASSENGER

(amending)

PSC(36)780e

[OST-2012-0058]

IATA INTERLINE TRAFFIC PARTICIPATION 

AGREEMENT - PASSENGER

(amending)

PSC(36)783 PASSENGER AND DATA INTERCHANGE 

STANDARDS BOARD

(amending)

PSC(36)798a HANDLING DISRUPTIVE/UNRULY PASSENGERS

(new)

PSC(36)1701h

[OST-2012-0058]

SECURITY CHECKPOINT ACCESS AND EGRESS

(amending)

PSC(36)1706c

[OST-2012-0058]

COMMON USE SELF-SERVICE

(amending)
PSC(36)1707a

[OST-01-9575]

DATA FIELD DIRECTORY FOR DCS PASSENGER 

MESSAGES

(amending)

PSC(36)1707b

[OST-01-9575]

DATA ELEMENT DIRECTORY FOR DCS PASSENGER 

MESSAGES

(amending)

PSC(36)1708

[OST-02-13807]

PASSENGER NAME LIST (PNL) AND ADDITIONS AND 

DELETIONS LIST (ADL)

(amending)

PSC(36)1719

[OST-01-9575]

PASSENGER FINAL SALES MESSAGE (PFS)

(amending)

PSC(36)1719b

[OST-02-13807]

PASSENGER RECONCILE LIST (PRL)

(amending)

PSC(36)1719c ELECTRONIC TICKET LIST (ETL)

(amending)

PSC(36)1719d TICKETLESS PRODUCT LIST (TPL)

(amending)

PSC(36)1719e ADDITIONAL SERVICES LIST (ASL)

(amending)

PSC(36)1720a

[OST-2012-0058]

STANDARD THIRTEEN-DIGIT NUMBERING SYSTEM 

FOR TRAFFIC DOCUMENT

(amending)

PSC(36)1743d BAGGAGE THEFT, PILFERAGE AND FRAUDULENT 

CLAIM PREVENTION

(amending)

PSC(36)1743e BAGGAGE IRREGUARITY REPORT

(amending)

PSC(36)1745

[OST-2012-0058]

BAGGAGE INFORMATION MESSAGES

(amending)

PSC(36)1754 ELECTRONIC BAGGAGE TAG

(new)

PSC(36)1790b RESERVATIONS PROCEDURES FOR CHARGEABLE 

ANCILLARY SERVICES (BILATERAL)

(new)
PSC(36)1791d

[OST-2012-0058]

PAYMENT CARD INDUSTRY DATA SECURITY 

STANDARDS (PCI DSS) COMPLIANCE

(amending)

PSC(36)1797

[OST-2012-0058]

COMMON USE PASSENGER PROCESSING 

SYSTEMS (CUPPS)

(amending)
SUMMARY OF CHANGES

RESOLUTIONS/RECOMMENDED PRACTICES ADOPTED AT:

36th PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE: 1 June 2015

Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 003

STANDARD 

RECISSION 

RESOLUTION

Resolution rescinds a 

previously adopted Resolution.

RP 1724 regarding Special Meal 

Codes and RP1798a regarding the 

Handling Disruptive/Unruly 

Passengers rescinded, the latter 

replaced by a new Resolution.

RESOLUTION 720a

PASSENGER TICKET 

AND BAGGAGE 

CHECK – ISSUANCE 

AND HONOURING 

PROCEDURES

Provides governing rules on 

how to issue a ticket, and 

applicable conditions for the 

honoring and re-issuance of 

tickets.

Added elements missed previously to 

help ensure compliance with the DoT 

Baggage Disclosure mandate.

RESOLUTION 722

TRANSITIONAL 

AUTOMATED TICKET 

(TAT)

Provides governing rules on 

how to produce an 

“automated” ticket issued by 

airlines. It also provides the 

technical specifications and 

applicable conditions for the 

honoring of such tickets.

Clarified with examples the 

procedures for how to ticket a 

stopover charge preceding a carrier 

with an A/N designator.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 722f

ELECTRONIC 

TICKET – AIRLINE

Provides governing rules and 

technical specifications on how 

to produce an Electronic Ticket 

(ET) issued by airlines. This 

allows ticketing to be 

performed without the 

issuance of paper tickets. Also 

included are the applicable 

conditions for the issuance 

and honoring of such tickets.

Added elements missed previously to 

help ensure compliance with the DoT 

Baggage Disclosure mandate.

Added a new data element for 

‘Booking Office IATA Number’.

Clarified what should be included in the 

ticket/document number character 

count.

Clean-up of elements and values 

defined which should never appear on 

an EMD

Added the ‘Billing Carrier Indicator’ 

back into the matrix.

Clarified the Reissued Flown Flight 

elements.

Added data elements ‘Tax Type’ to 

further qualify the tax code.

More accurately describe the usage of 

Reason For Issuance Sub-Codes 

(RFISC) at industry level.

RESOLUTION 722g

ELECTRONIC

TICKET – NEUTRAL

Provides governing rules and 

technical specifications on how 

to produce an Electronic Ticket 

(ET) issued by travel agents. 

This allows ticketing to be 

performed without the 

issuance of paper tickets. Also 

included are the applicable 

conditions for the issuance 

and honoring of such tickets.

Added elements missed previously to 

help ensure compliance with the DoT 

Baggage Disclosure mandate.

Added a new data element for 

‘Booking Office IATA Number’.

Clarified the Reissued Flown Flight 

elements.

Added data elements ‘Tax Type’ to 

further qualify the tax code.

RESOLUTION 722h

ELECTRONIC 

TICKET – GROUND 

HANDLING

Provides governing rules and 

technical specifications to be 

followed for the third party 

ground-handling of electronic 

tickets (ETs). This allows 

airlines to have their electronic 

tickets handled by third party 

ground handlers.

Added elements missed previously to 

help ensure compliance with the DoT 

Baggage Disclosure mandate.

Added a new data element for 

‘Booking Office IATA Number’.

Clarified the Reissued Flown Flight 

elements.

Added data elements ‘Tax Type’ to 

further qualify the tax code.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 725a

MISCELLANEOUS 

CHARGES ORDER 

(MCO) – ISSUANCE 

AND HONOURING 

PROCEDURES BY 

MEMBERS

Provides governing rules on 

how to issue and honor a 

Miscellaneous Charges Order 

(MCO) issued be airlines.

Clarified which currency is refunded 

when only part of the document has 

been utilized.

RESOLUTION 725f

ELECTRONIC 

MISCELLANEOUS 

DOCUMENT –

AIRLINE

Provides governing rules for 

the issuance and use of 

Electronic Miscellaneous 

Documents (EMD) by airlines.

The EMD is an electronic 

method to document the sale 

and usage of charges 

associated to various usage, 

e.g. excess baggage charges.

Added a new data element for 

‘Booking Office IATA Number’.

Corrected a number of anomalies.

Outlined two methods of creating a 

Group Name Field in a PNR.

Changed from mandatory to optional

the requirement to issue a separate 

EMD when multiple EMD coupons are 

required for the same ET flight 

coupon.

Clarified the Reissued Flown Flight 

elements.

Added data elements ‘Tax Type’ to 

further qualify the tax code.

RESOLUTION 725g

ELECTRONIC 

MISCELLANEOUS 

DOCUMENT –

NEUTRAL

Provides governing rules for 

the issuance and use of 

Electronic Miscellaneous 

Documents (EMD) by agents.

Added a new data element for 

‘Booking Office IATA Number’.

Outlined two methods of creating a 

Group Name Field in a PNR.

Additional details and rules added to 

appropriately apply the GDS ‘System 

Update to EMD’ when adding EMD-A 

association to an ET.

Changed from mandatory to optional

the requirement to issue a separate 

EMD when multiple EMD coupons are 

required for the same ET flight 

coupon.

Clarified the Reissued Flown Flight 

elements.

Added data elements ‘Tax Type’ to 

further qualify the tax code.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 725h

ELECTRONIC 

MISCELLANEOUS 

DOCUMENT –

GROUND HANDLING

Provides governing rules and 

technical specifications to be 

followed for the third party 

ground-handling of electronic 

miscellaneous documents 

(EMDs). This allows airlines to 

have their EMDs handled by 

third party ground handlers.

Added a new data element for 

‘Booking Office IATA Number’.

Clarified the Reissued Flown Flight 

elements.

Added data elements ‘Tax Type’ to 

further qualify the tax code.

RESOLUTION 725i

THROUGH/CHANGE 

OF GAUGE FLIGHT 

FOR EMD-A

Provides to facilitate the 

handling of EMD-A(s) when 

associated through/change of 

gauge flight(s).

Added a new Industry Standard 

outlining the handling of EMD-A(s) 

when associated through/change of 

gauge flight(s).

RESOLUTION 728

CODE 

DESIGNATORS FOR 

PASSENGER TICKET 

AND BAGGAGE 

CHECK

Provides various coding 

structures in order to identify 

the type of fare and other 

conditions of travel for tickets 

and other documents.

Clarified which form of payment 

should be entered when no collection 

is made for travel agent sales only.

Clarified only one service fee tax code 

is allocated per country.

Recognized the expansion of the 

Cabal card to a regional card and 

added editorials for Korea.

RESOLUTION 743a

FORWARDING 

MISHANDLED 

BAGGAGE

Outlines the procedure for the 

forwarding of mishandled 

baggage

Made numerous editorial changes for 

baggage

RESOLUTION 754

PROFILES OF 

INTERLINE 

BAGGAGE CLAIMS 

AND PROOF OF 

FAULT FOR 

BAGGAGE 

PRORATES

Provides to assist baggage 

claims personnel in 

determining the cases when 

an interline baggage claim can 

result in 100% prorate

Introduced a new resolutions to assist 

baggage claims personnel in 

determining the cases when an 

interline baggage claim can result in 

100% prorate

RESOLUTION 762

AIRLINE 

DESIGNATORS

Provides the governing rules 

for the assignment and use of 

airline designators for the 

entire airline and travel and 

tourism industry.

Made amendment to clarify CRS 

should not be allowed to perform the 

same actions that should be limited to 

airlines only (issuing and operating air 

services). The ticket issuance must 

still be done by a legitimate air carrier 

with a two-letter IATA airline code.

RESOLUTION 765

INTERLINE 

CONNECTING TIME 

INTERVALS –

PASSENGER AND 

CHECKED 

BAGGAGE

Provides for the establishment 

of minimum connecting time 

interval required in order to 

transfer a passenger and his 

luggage from one flight to a 

connecting flight.

Clarified that concurrence by the 

receiving carrier will not be required 

when the delivering carrier submits a 

proposed MCT exception where the 

only data elements to change is the 

delivering carrier’s flight number or 

flight range
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 767

ASSIGNMENT OF 

AIRLINE 

ACCOUNTING 

CODES AND AIRLINE 

PREFIXES

Provides governing rules for 

the assignment and use of 

airline accounting codes and 

airline prefixes.

Provided provisional assignments of 

accounting codes for testing.

Cleaned up the resolution.

RESOLUTION 780

FORM OF INTERLINE 

TRAFFIC 

AGREEMENT –

PASSENGER

Provides the standard text for 

multi-lateral interline traffic 

agreements.

Made numerous editorial changes for 

baggage

RESOLUTION 780e

IATA INTERLINE

TRAFFIC

PARTICIPATION 

AGREEMENT –

PASSENGER

Provides the standard text for 

multi-lateral interline traffic 

agreements where only one 

airline is able to issue tickets.

Made numerous editorial changes for 

baggage

RESOLUTION 783

PASSENGER AND 

DATA 

INTERCHANGE 

STANDARDS BOARD

Establishes the terms of 

reference for the Passenger 

and Airport Data Interchange 

Standards Board (PADIS)

Modified to reflect the evolution of the 

technology as well as the new role of 

PADIS Board in relation to Data 

Model and associated methodology. 

RESOLUTION 798a

HANDLING 

DISTRUPTIVE/

UNRULY 

PASSENGERS

Establishes how airlines 

should create and implement a 

method for handling disruptive 

and unruly passenger

Upgraded recommended practice into 

a resolution

RP 1701h

SECURITY 

CHECKPOINT 

ACCESS AND 

EGRESS

One of the “passenger 

experience standards” that 

provides best practice 

suggestions for airports 

regarding procedures at 

security checkpoints

Revised Security Checkpoint Diagram 

showing best practice infrastructure, 

equipment and layout and the best 

practice dimensions.

RP 1706c

COMMON USE SELF 

SERVICE

Provides a recommended 

practice outlining specification 

and standard for members 

who plan to operate shared 

self-service devices in a 

common environment.

Added a reference regarding 

accessibility

RP 1707a

DATA FIELD 

DIRECTORY FOR 

DCS PASSENGER 

MESSAGES

Provides definitions and 

formats for the automatic 

creation, transmission, receipt 

and interpretation of this group 

of messages.

Amended to allow boarding pass 

delivery from SSR ACKI to be 

included on PNL/ADL.

Removed old references to 6 digit 

alpha/numeric format, and modified 

example bag formats to the 10 digit 

format.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RP 1707b

DATA ELEMENT 

DIRECTORY FOR 

DCS PASSENGER 

MESSAGES

Provides specifications and 

rules governing the use of 

DCS Passenger Messages. 

These messages are used to 

provide various pieces of 

information that support the 

“seamless” interline 

transportation of passengers.

Amended so that Party/Group 

identifiers uniquely identify a single 

group of passengers and be 

consistent across messages.

Removed old references to 6 digit 

alpha/numeric format, and modified 

example bag formats to the 10 digit 

format.

RP 1708

PASSENGER NAME 

LIST (PNL) AND 

ADDITIONS AND 

DELETIONS LIST 

(ADL)

Provides the definitions, 

formats and procedures for the 

creation, transmission and 

interpretation of Passenger 

Name Lists Messages and 

Additions/Deletion Lists 

Messages associated with the 

passenger data produced by 

an airline reservations system.

Deleted “IROP” and replaced it with 

“operational notifications”.

Introduced a format to allow a dash (-) 

entry for email addresses.

Added new SSR ACKI and SSR INAD 

on PNL/ADL.

Amended so that Party/Group 

identifiers uniquely identify a single 

group of passengers and be 

consistent across messages.

RP 1719

PASSENGER FINAL 

SALES MESSAGE 

(PFS)

The PFS message gives 

information to reservations 

systems about the final counts 

loaded on an aircraft at the 

departure station. List 

contains a numeric summary 

of passenger counts and may 

contain passenger names

GOSHN added to the list of categories 

Automated PNR Addresses not 

applicable.

RP 1719b

PASSENGER 

RECONCILE LIST 

(PRL)

The PRL is a list containing all 

passenger check-in details for 

actual boarded passengers of 

a flight departure.

Removed old references to 6 digit

alpha/numeric format, and modified

example bag formats to the 10 digit 

format.

RP 1719c

ELECTRONIC 

TICKET LIST 

(ETL)

The ETL is a list of all locally 

boarded passengers who 

checked in with an electronic 

ticket

The Seat Configuration Element in be 

corrected.

Removed old references to 6 digit 

alpha/numeric format, and modified

example bag formats to the 10 digit 

format.

RP 1719d

TICKETLESS 

PRODUCT LIST

(TPL)

The TPL is a list of all locally 

boarded passengers who 

checked in with a ticketless 

product 

The Seat Configuration Element in be 

corrected.

Removed old references to 6 digit 

alpha/numeric format, and modified

example bag formats to the 10 digit 

format.

RP 1719e

ADDITIONAL 

SERVICES LIST

(ASL)

The ASL is a list of all locally 

boarded passengers who 

checked in with an Additional 

Service(s)

The Seat Configuration Element in be 

corrected.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RP 1720a

STANDARD 

THIRTEEN-DIGIT 

NUMBERING 

SYSTEM FOR 

TRAFFIC 

DOCUMENTS

Provides guidelines regarding 

the numbering systems for 

airline and travel agent traffic 

documents

an overview of form code recycling 

methodology included for effect 01 

July 2015

RP 1743d

BAGGAGE THEFT, 

PILFERAGE AND 

FRADULENT CLAIM 

PREVENTION

Provides guidelines to prevent 

and reduce baggage theft, 

pilferage and fraudulent 

claims.

A best practice added for addressing 

fraud and also to improve back-office 

fraud detection process.

RP 1743e

BAGGAGE 

IRREGULARITY 

REPORT

Provides guidelines on how 

the mishandled baggage 

should be reported to reduce 

baggage mishandlings

Code RL81 added.

RP 1745

BAGGAGE 

INFORMATION 

MESSAGES

Provides the definitions, 

formats and specifications for 

all of the messages used in 

the baggage handling process

Updated the codes that are used .X 

element of the BSM to support TSA 

procedures.

The pax status amended to be a 

mandatory field in the .S element, and

a comment added to state that 

exception bags such CREW or RUSH 

can still be loaded if the Authority to 

Load is ‘Y’ and the pax status is ‘N’ as 

you would expect.

Added two additional location 

identifier codes to the Bag Check-in 

Code Set

RP 1754

ELECTRONIC 

BAGGAGE TAG

Guidelines for electronic 

baggage tags to more 

effectively facilitate the 

acceptance and subsequent 

processing of baggage

In order that these tags may be used 

in an interline environment, a common 

standard is established for the 

technology components of the 

electronic baggage tag.

RP 1790b

RESERVATIONS 

PROCEDURES FOR 

CHARGEABLE 

ANCILLARY 

SERVICES 

(BILATERAL)

Guidelines for the reservations 

of chargeable ancillary 

services using an EMD

Established new guidelines for the 

reservations of chargeable ancillary 

services using an EMD
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

1791d

PAYMENT CARD 

INDUSTRY DATA 

SECURITY 

STANDARDS (PCI 

DSS) COMPLIANCE

Guidelines to enable 

compliance with the 

requirements of the Payment 

Card Industry Data Security 

Standards (PCI DSS) 

Numerous editorial amendments 

made.

Updated the BSP Peru-specific 

process.

Added a specification instruction that 

sending full credit card information in 

unstructured format text is strictly 

forbidden

RP 1797

COMMON USE 

PASSENGER 

PROCESSING

SYSTEMS (CUPPS)

Provides guidelines for 

CUPPS systems that enable 

airlines to share check-in 

desks or gate podiums for 

boarding processes

Removed reference to Common Use 

Terminal Equipment (CUTE).
RESOLUTION 003

STANDARD RECISSION RESOLUTION

PSC(36)003 Expiry: 12 June 2015

Type: B

Resolved that, effective 6June 2015, the following Recommended Practice are 

rescinded:

RP 1773 – Special Meal Codes P11

RP 1798a – Handling Disruptive/Unruly Passengers P6

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015

RESOLUTION 720a

PASSENGER TICKET AND BAGGAGE CHECK – ISSUANCE AND HONOURING 

PROCEDURES

(amending)

PSC(34 36)720a Expiry: Indefinite

Type: B

RESOLVED that,

.....

T2.2/P

22. “BAGGAGE” BOXES

.....

22.3 Additional Baggage Information

.....

22.3.5 Carry-on charge amount may be stored for each flight coupon. 

22.3.6 Free Carry-on dimension and/or weight may be stored for each flight coupon. 

22.3.7 Embargo information may be stored for each flight coupon. 

22.3.8 Chargeable baggage dimension and/or weight may be stored for each flight 

coupon. 

22.3.9 Chargeable Carry-on dimension and/or weight may be stored for each flight 

coupon.

.....

Filing Period: Effective Date:

11May 2015 12 June 2015

11 June 2015

RESOLUTION 722 

TRANSITIONAL AUTOMATED TICKET (TAT)

(amending)

PSC(35 36)722 Expiry: Indefinite

Type: A

RESOLVED that,

.....

T2.5/P

...

Section 3 – Issuing and Honouring Procedures

...

3.16 FARE CALCULATION

...

3.16.16 Spacing

Items shall be separated by spaces except where alphabetic characters are followed by 

numerics or signs or vice versa. A space shall, however, be maintained between a 

location identifier and an airline designator whether or not the airline designator is a 

numeric-alpha designator. At such time as three-letter airline designators are 

implemented, the space preceding these designators shall be replaced by a period. 

Consecutive location codes are considered as one item

Examples:

MAN_BB_LON_5S_DKR M583.20NUC583.20. 

TYO_CC DEL_S70.14_4Z_BOM_M576.19NUC646.33

.....

(Editor’s note: note underbar ‘_’ for the space in the examples)

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015

RESOLUTION 722f

ELECTRONIC TICKET—AIRLINE

(amending)

PSC(35 36)722f Expiry: Indefinite

 Type: B

RESOLVED that,

.....
Attachment ‘A’

ELECTRONIC TICKET AND MISCELLANEOUS DOCUMENTS

DATA ELEMENTS GLOSSARY

(amending)

PSC(36)722f Expiry: Indefinite

Type: B

...

Glossary Applicability Reference Table

The table represents the resolutions matrices in which the data elements are applicable

...

T2.3/P

RESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

....

BOOKING OFFICE IATA NUMBER N Y N N Y N

GLOSSARY

T2.11/P

ADDITIONAL SERVICES SERVICE TYPE 1 ALPHANUMERIC

A value which specifies the type of additional service or baggage for which an EMD is 

being issued. The value will correspond to the value filed in ATPCO’s Optional Services 

data for the additional service being sold. whether the service is for baggage allowance, 

baggage charges, flight, merchandise, reissue/refund or ticket.

A = Baggage Allowance

C = Baggage Charges

F = Flight

M = Merchandise

R = Reissue/Refund

T = Ticket

Blank = no application

T2.3/P

BOOKING OFFICE IATA NUMBER – 8 NUMERIC

IATA number of the office where the PNR from which the document is issued has been 

booked. 

...
T2.9/P

...

NUMBER OF TICKET/DOCUMENT NUMBERS - 2 NUMERIC

The total number of ticket/document numbers sent in a single PADIS message. Does 

not include count in fare component and reissue flown flight coupon or ‘In Connection 

With’ data. Count shall only include documents that are being processed/created.

TOTAL NUMBER OF FLIGHT/VALUE COUPONS – 2 NUMERIC

The total number of flight or value coupons include in this transaction. See 

Segment/Coupon identifier. The total of flight or value coupons shall only include the 

count of flight or value coupons being processed/created. It is a coupon count as 

opposed to a segment count. The ‘In Connection With’ data is not included in the count.

T5

TAX/FEE/CHARGE TYPE 3 ALPHANUMERIC

A qualifier to the Tax/Fee/Charge Code to distinguish taxes/fees/charges with the same 

tax/fee/charge code but with different business uses. This data element is set at the 

time of pricing for the itinerary or service. This data element supports tax at the ticket 

level.

CARRIER FEE DATA 

Carrier Fee Tax Type 3 ALPHANUMERIC

A qualifier to the Carrier Fee Tax Code to distinguish taxes/fees/charges applied to a 

carrier fee, with the same tax/fee/charge code but with different business uses. This 

data element is set at the time of pricing for the itinerary or service. This data element 

supports taxes on carrier fees.

Carrier Fee Tax on Tax Type 3 ALPHANUMERIC

A qualifier to the Carrier Fee Tax on Tax Code to distinguish taxes/fees/charges applied 

to a tax on a tax on a carrier fee, with the same tax/fee/charge code but with different 

business uses. This data element is set at the time of pricing for the itinerary or service. 

This data element supports taxes on carrier fees.

TAX/FEE/CHARGE DETAILS

Tax/Fee/Charge Type 3 ALPHANUMERIC

A qualifier to the Tax/Fee/Charge Code to distinguish taxes/fees/charges with the same 

tax/fee/charge code but with different business uses. This data element is set at the 

time of pricing for the itinerary or service. This data element supports tax/fee/charge 

details.
TAX/FEE/CHARGE DATA AT THE TICKET COUPON LEVEL

Tax/Fee/Charge Tax Type 3 ALPHANUMERIC

A qualifier to the Tax/Fee/Charge Tax Code to distinguish taxes/fees/charges with the 

same tax/fee/charge code but with different business uses. This data element is set at 

the time of pricing for the itinerary or service. This data element supports tax at the 

coupon level.

Tax/Fee/Charge Filed Type 3 ALPHANUMERIC

A qualifier to the Tax/Fee/Charge Filed Code to distinguish taxes/fees/charges with the 

same tax/fee/charge code but with different business uses. This data element is set at 

the time of pricing for the itinerary or service. This data element supports tax at the 

coupon level.
T8

REASON FOR ISSUANCE SUB CODE—3 ALPHANUMERIC

(Applicable to 725f, 725g and 725h only), 

A secondary three-character code which qualifies the Reason for Issuance Code as 

sourced from ATPCO for the ATPCO optional services product.

IATA Standard Codes

The following codes are IATA standard codes to be used in accordance with the 

associated definitions.
Sub Code Definition 

999 UNDER COLLECTIONS FARES (including net fare difference)

998 UNDER COLLECTIONS TAX FEES CHARGES 

997 DEPOSITS DOWN PAYMENTS 

996 REFUNDABLE BALANCES (shall be used when a residual value as a result of an exchange/reissue 

transaction cannot be used for further air transportation (E.g. in IATA BSPs))

995 CANCELLATION FEE 

994 REBOOKING FEE DOMESTIC WITH TAXES EG VAT WHERE APPLICABLE

993 REBOOKING RESERVATIONS CHANGE FEE INTERNATIONAL

992 DOCUMENT AMENDMENT FEE 

991 TICKET DOCUMENT HANDLING FEE 

990 BOOKING FEE 

99K INVOLUNTARY DOWNGRADING (airline use only)

99J DISCOUNT CARD (e.g. season tickets)

99I RESIDUAL VALUE (used for further air transportation which may also be refunded (not applicable to 

IATA BSP agents))

99H UPGRADE AIRPORT TAX 

980 LAND SERVICE 

981 CABIN BAGGAGE 

982 CARGO 1 to 25 POUNDS 

983 CARGO 26 to 50 POUNDS 

984 CARGO 51 to 75 POUNDS 

985 CARGO AIRWAY BILL 

986 CARGO MAIL ENVELOPE 

987 CARGO SMALL PACKAGE 

988 CREDIT CARD CHARGE 

98A NON REVENUE INTERNATIONAL SERVICE FEE 

98B TRANSPORTATION CREDIT VOUCHER (may be used for customer service recovery and 

compensation)

98C UNSPECIFIED TRANSPORTATION (not applicable to IATA BSP agents)

98D FOR REFUND ONLY 

98E NON REFUNDABLE AMOUNT (may be used for amounts for non-refundable balances (not applicable 

to IATA BSP agents)

98F PENALTY FEE 

98G BOOKING CODE DISCREPANCY 

98H STOPOVER/TRANSFER and TRANSIT CHARGE 

98I SERVICE CHARGE 

98J MISCELLANEOUS CHARGE (to be used for other miscellaneous charges as determined by the carrier 

only when no other code exists and when not filed with ATPCO)

98K NET FARE DIFFERENCE 
T2.14/P

REISSUED FLOWN FLIGHT COUPON DATA

(Repeatable field) 

A series of data elements representing sold data for coupons that have been flown from a previously 

reissued ticket. This data set is repeated for every flown coupon and carried forward for every reissue 

transaction and is comprised of the following data elements:

 ... 

• Reissued Flown Fare Calculation Coupon/Itinerary Sequence Number 

 2 ALPHANUMERIC

The number representing the order in which this coupon was used or is to be used. 

 ... 

• Reissued Flown Ticket/Document Number 14 ALPHANUMERIC

‘Ticket/Document Number’ that represents sold data for coupons that have been flown from a previously 

reissued ticket. See glossary definition for ‘TICKET/DOCUMENT NUMBER’.

• Reissued Flown Ticket Date of Issue 7 ALPHANUMERIC

‘Date of issue’ of a ticket that represents sold data for coupons that have been flown from a previously 

reissued ticket. Format DDMMMYY.

• Reissued Flown Waiver Code 15 ALPHANUMERIC

A Validating Carrier assigned code allowing a fare rule modification or override applied to a flown 

coupon from the ticket being reissued. 

• Reissued Ticket Date of Issue 7 ALPHANUMERIC

The issue date of a ticket that was reissued in the format DDMMMYY.

• Reissued Ticket Number 14 ALPHANUMERIC

A document number assigned to a ticket previously issued. See glossary definition for 

'TICKET/DOCUMENT NUMBER'.

(End of Reissued Flown Flight Coupon Data)

REISSUED TICKET/DOCUMENT DATE OF ISSUE 7 ALPHANUMERIC

The issue date of a ticket that was reissued in the format DDMMMYY.

REISSUED TICKET/DOCUMENT NUMBER 14 ALPHANUMERIC

A document number assigned to a ticket previously issued. See glossary definition for 

'TICKET/DOCUMENT NUMBER'.

Note: No other changes to 722f/20.60, 722g/20.61, 722h/20.62, 725f/20.63, 725g/20.64, 

725h/20.66 Resolution text.
Matrix Changes

Glossary Applicability Reference Table

T5

Row 

No.

2014 A4A / IATA Resolutions Glossary Applicability Reference Table (GART)

Data Element

No. Char. 

A, N or

A/N

722f / 

20.60

722g / 

20.61

722h / 

20.62

725f / 

20.63

725g / 

20.64

725h / 

20.66

59 Carrier Fee Tax Code 2 A/N Y Y

Carrier Fee Tax Type 3 A/N Y Y

63 Carrier Fee Tax on Tax Code 2 A/N Y Y

Carrier Fee Tax on Tax Type 3 A/N Y Y

393 TAX/FEE/CHARGE CODE 2 A/N Y

TAX/FEE/CHARGE TYPE 3 A/N Y

405 Tax/Fee/Charge Code 2 A/N Y Y Y Y

Tax/Fee/Charge Type 3 A/N Y Y Y Y

417 Tax/Fee/Charge Tax Code 2 A/N Y Y

Tax/Fee/Charge Tax Type 3 A/N Y Y

420 Tax/Fee/Charge Filed Code 2 A/N Y Y

Tax/Fee/Charge Filed Type 3 A/N Y Y
T5

T2.14/P

Resolution 722f/20.60

RESOLUTION 20.60 / 722f – 2014 2015 MANUAL – ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – AIRLINE MESSAGES

Row

No.

Data Element

Transaction Action Code

No.

Char.

A, N, 

or

A/N

Display

D, J

History

Display

H

Request

Airport

Control

B

Change 

of

Status

C

Redirect

Airport

Control

N

Reservatio

n

Change

A

Emergency

Lock

M

System

Update

U

Unsolicited

Airport

Control

T, I 3

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

59 Carrier Fee Tax Code (not Applicable) 2 A/N

Carrier Fee Tax Type (not Applicable) 3 A/N

63 Carrier Fee Tax on Tax Code (not Applicable) 2 A/N

Carrier Fee Tax on Tax Type (not Applicable) 3 A/N

393 TAX/FEE/CHARGE CODE 2 A/N C C C

TAX/FEE/CHARGE TYPE 3 A/N C C C

405 Tax/Fee/Charge Code 2 A/N C C C

Tax/Fee Charge Type 3 A/N C C C

417 Tax/Fee/Charge Tax Code 2 A/N C C C

Tax/Fee/Charge Tax Type 3 A/N C C C

420 Tax/Fee/Charge Filed Code 2 A/N C C C

Tax/Fee/Charge Filed Type 3 A/N C C C

319© ©REISSUED FLOWN FLIGHT COUPON DATA – Begin: -

 ... 

324 ® Reissued Flown Fare Calculation Coupon/Itinerary 

Sequence Number

2 A/N C C C

 ... 

340 Reissued Flown Ticket Designator 15 A/N C C C

341 Reissued Flown Ticket/Document Number 14 A/N C C C

342 Reissued Flown Ticket Date of Issue 7 A/N C C C

343 Reissued Flown Waiver Code 15 A/N C C C

344® ® Reissued Ticket Date of Issue 7 A/N C C C

345® ® Reissued Ticket Number 14 A/N C C C

346 REISSUED FLOWN FLIGHT COUPON DATA – End. -

347 REISSUED TICKET/DOCUMENT DATE OF ISSUE (Not 

Applicable)

7 A/N C C C

348 REISSUED TICKET/DOCUMENT NUMBER (Not Applicable) 14 A/N C C C
Attachment ‘B’

MESSAGE CONSTRUCTION MATRIX – AIRLINE MESSAGES

(amending)

T2.3/P

ELEMENT 

DESCRIPTION

Transaction NO 

CHAR.

A, N 

OR 

A/N

DISPLAY

UNSOLICITED 

AIRPORT 

CONTROL 

(INFORMATION 

- A4A ONLY)

HISTORY 

DISPLAY

REQUEST 

AIRPORT 

CONTROL

CHANGE 

OF 

STATUS

REDIRECT 

AIRPORT 

CONTROL

RESERVATION 

CHANGE

EMERGENCY 

LOCK

SYSTEM 

UPDATE

Action code -> D, J T (I-A4A only) H B C N A M U

RESOLUTION 

722f/20.60

REQRESP REQ RESP REQ RESP REQRESPREQRESP REQ RESP REQ RESP REQ RESP REQRESP

...

Booking 

Office IATA 

Number

(Not 

Applicable)

8N

...

T2.13/P

......

Row

No.

Data Element

Transaction Action Code

No.

Char.

A, N, or

A/N

Request

Airport

Control

B

Change of

Status

C

Unsolicited

Airport

Control

T, I 3

REQ RESP REQ RESP REQ RESP

...

42 BILLING CARRIER INDICATOR (Not Applicable) 1 A/N C 1

...

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015
RESOLUTION 722g

ELECTRONIC TICKET—NEUTRAL

(amending)

PSC(35 36)722g Expiry: Indefinite

 Type: B

RESOLVED that,

.....

T2.2
T2.14/P

T5

Attachment ‘B’

RESOLUTION A4A 20.61 / IATA 722g – 2014 2015 – ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – NEUTRAL MESSAGES

Row 

No.

Data Element

Transaction Action Code

No. 

Char. 

A, N or

A/N

Issuance –

Information

S, I 7

Display

D

History

Display

H

Exchange/

Reissue

E

Refund

R

Reservation

Change

A

System 

Cancel

X,Y

Refund 

Cancel

Z

Void

V,W

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

319 REISSUED FLOWN FLIGHT COUPON DATA –

Begin:

-

323 ... 

324 ® Reissued Flown Fare Calculation Coupon/Itinerary 

Sequence Number

2 A/N C C C

339 ... 

340 Reissued Flown Ticket Designator 15 A/N C C C

341 Reissued Flown Ticket/Document Number 14 A/N C C C

342 Reissued Flown Ticket Date of Issue 7 A/N C C C

343 Reissued Flown Waiver Code 15 A/N C C C

344 ® Reissued Ticket Date of Issue 7 A/N C C C

345 ® Reissued Ticket Number 14 A/N C C C

346 REISSUED FLOWN FLIGHT COUPON DATA – End. -

347 REISSUED TICKET/DOCUMENT DATE OF ISSUE 

(Not Applicable)

7 A/N C C C

348 REISSUED TICKET/DOCUMENT NUMBER (Not 

Applicable)

14 A/N C C C

59 Carrier Fee Tax Code 2 A/N C C C

Carrier Fee Tax Type 3 A/N C C C

63 Carrier Fee Tax on Tax Code 2 A/N C C C

Carrier Fee Tax on Tax Type 3 A/N C C C

393 TAX/FEE/CHARGE CODE (Not Applicable) 2 A/N

TAX/FEE/CHARGE TYPE (Not Applicable) 3 A/N

405 Tax/Fee/Charge Code 2 A/N C C C

Tax/Fee/Charge Type 3 A/N C C C

417© © Tax/Fee/Charge Tax Code 2 A/N C C C C C

Tax/Fee/Charge Tax Type 3 A/N C C C C C

420© © Tax/Fee/Charge Filed Code 2 A/N C C C C C

Tax/Fee/Charge Filed Type 3 A/N C C C C C
T2.2/P

T2.3/P

Attachment ‘B’

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – NEUTRAL MESSAGES

ELEMENT DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

ISSUANCE

(INFORMATION 

– ATA ONLY)

DISPLAY HISTORY 

DISPLAY

EXCHANGE/

REISSUE

REFUND RESERVATIONS 

CHANGE

SYSTEM 

CANCEL

REFUND 

CANCEL

VOID

Action Code ---> S(I-ATA ONLY) D H E R A X,Y Z V,W

RESOLUTION 722 G REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Booking Office IATA Number 8N O O O O O O O

...

Carry-on Charge Types 3 A/N O O O O

Carry-on Charge Amount 9N O O O O

Carry-on Charge Amount 

Currency Code

3A/N O O O O

Maximum Free carry-on 

Dimensions

4 A/N O O O O

Maximum Free carry-on 

Weight

3 A/N O O O O

Embargo 70 A/N O O O O

Maximum Chargeable 

Baggage Dimensions

4 A/N O O O O

Maximum Chargeable 

Baggage Weight

3 A/N O O O O

Maximum Chargeable carryon Dimensions4 A/N O O O O

Maximum Chargeable carryon Weight3 A/N O O O O

...

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015
RESOLUTION 722h

ELECTRONIC TICKET—GROUND HANDLING

(amending)

PSC(35 36)722h Expiry: Indefinite

Type: B

T2.3/P

Attachment B

ELEMENT DESCRIPTION

Transaction NO CHAR.

A, N OR A/N DISPLAY AIRPORT CONTROL REQUEST 

– GROUD HANDLING CHANGE OF STATUS REDIRECT AIRPORT 

CONTROL

EMERGENCY LOCK UNSOLICITED AIRPORT 

CONTROL – GROUND 

HANDLING

Action code -> D B C N M K

RESOLUTION 722h/20.62 REQ RESP REQ RESP REQ RESP REQ RESP

REQ RESP REQ RESP

...

Booking Office IATA Number

(Not Applicable) 8N

...
T2.2/P

T2.14/P

RESOLUTION A4A 20.62 / IATA 722h – 2014 2015 – ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – GROUND HANDLING MESSAGES

Row 

No.

Data Element

Transaction Action Code

No. 

Char. 

A, N 

or A/N

Display

D

Airport 

Control

Request –

Ground 

Handling

G

Change of 

Status

C

Redirect 

Airport Control

N

Emergency 

Lock

M

Unsolicited

Airport 

Control –

Ground 

Handling

K

System 

Update

U

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

319© © REISSUED FLOWN FLIGHT COUPON DATA – Begin: (Not 

Applicable)

-

323 ... 

324 ® Reissued Flown Fare Calculation Coupon/Itinerary Sequence 

Number (Not Applicable)

2 A/N

325 ... 

341 Reissued Flown Ticket/Document Number (Not Applicable) 14 A/N

342 Reissued Flown Ticket Date Of Issue (Not Applicable) 7 A/N

343 Reissued Flown Waiver Code (Not Applicable) 15 A/N

344 Reissued Ticket Date Of Issue (Not Applicable) 7 A/N

345 Reissued Ticket Number (Not Applicable) 14 A/N

346 REISSUED FLOWN FLIGHT COUPON DATA – End. -

347 REISSUED TICKET/DOCUMENT DATE OF ISSUE (Not 

Applicable)

7 A/N

348 REISSUED TICKET/DOCUMENT NUMBER (Not Applicable) 14 A/N

Carry-on Charge Types 3 A/N O O O

Carry-on Charge Amount 9N O O O

Carry-on Charge Amount Currency Code 3A/N O O O

Maximum Free carry-on Dimensions 4 A/N O O O

Maximum Free carry-on Weight 3 A/N O O O

Embargo 70 

A/N

O O O

Maximum Chargeable Baggage Dimensions 4 A/N O O O

Maximum Chargeable Baggage Weight 3 A/N O O O

Maximum Chargeable carry-on Dimensions 4 A/N O O O

Maximum Chargeable carry-on Weight 3 A/N O O O
T5

RESOLUTION A4A 20.62 / IATA 722h – 2014 2015 – ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – GROUND HANDLING MESSAGES

Row 

No.

Data Element

Transaction Action Code

No. 

Char. 

A, N 

or A/N

Display

D

Airport 

Control

Request –

Ground 

Handling

G

Change of 

Status

C

Redirect 

Airport Control

N

Emergency 

Lock

M

Unsolicited

Airport 

Control –

Ground 

Handling

K

System 

Update

U

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

59 Carrier Fee Tax Code (not Applicable) 2 A/N

Carrier Fee Tax Type (not Applicable) 3 A/N

63 Carrier Fee Tax on Tax Code (Not Applicable) 2 A/N

Carrier Fee Tax on Tax Type (Not Applicable) 3 A/N

393 TAX/FEE/CHARGE CODE (Not Applicable) 2 A/N

TAX/FEE/CHARGE TYPE (Not Applicable) 3 A/N

405 Tax/Fee/Charge Code (Not Applicable) 2 A/N

Tax/Fee/Charge Type (Not Applicable) 3 A/N

417 Tax/Fee/Charge Tax Code (Not Applicable) 2 A/N

Tax/Fee/Charge Tax Type (Not Applicable) 3 A/N

420 Tax/Fee/Charge Filed Code (Not Applicable) 2 A/N

Tax/Fee/Charge Filed Type (Not Applicable) 3 A/N

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June2015
RESOLUTION 725a

MISCELLANEOUS CHARGES ORDER (MCO) – ISSUANCE AND HONOURING 

PROCEDURES BY MEMBERS

(amending)

PSC(34 36)725a Expiry: Indefinite

Type: B

RESOLVED that:

....

T2.6/P

Section 4—Refunds 

When an MCO or portion thereof, is to be refunded, such refund shall be made, 

subject to any restrictions appearing on the MCO and/or in applicable currency 

regulations and refund Resolution(s). 

When an MCO is issued to cover a refundable balance, the carrier whose 

accountable form was originally issued shall be entered in the “To . . . At” box. 

The MCO shall be issued in the currency originally tendered. 

Enter the words “For Refund Only” in the “Type of Service for Which Issued” box. 

Such refundable balance may exceed US$750 (or equivalent) 

(determined in accordance with the IATA rate of Exchange)

....

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015

RESOLUTION 725f

ELECTRONIC MISCELLANEOUS DOCUMENT—AIRLINE

(amending)

PSC(35 36)725f Expiry: Indefinite 

 Type: B

RESOLVED that,

....

T2.4/P

Section 3 - Definitions

....

3.3 DATA ELEMENTS—The components of PADIS messages. The following 

messages are defined in this Resolution:

Change of Status Message;

Display Message;

Request Airport Control Message;

System Update Message.;

Unsolicited Billing Message.

.....

Section 6 – Procedures

T2.12/P

.....

6.1.10.5 A separate EMD-A shall may be issued when multiple EMD coupons are 

required for the same ET flight coupon.

T2.8/P

...

6.2.2.1 An EMD-S shall be limited to one passenger or group name only. When 

the EMD-S is issued for passengers whose names are unknown (e.g. group 

deposit) use the name of the group leader or sponsor. If the group leader or 

sponsor name has one or more obliques separating portions of the group name; 

the name field will be considered in one of two ways:

Name field: SKITRIP/SENIORCLASS

1) Regardless of whether the Group Name has obliques or not, send only the 

‘Surname’ and nothing else, i.e. SKITRIP.

2) Or, if the Group Name has obliques, send the name as the Surname, i.e.

SKITRIPSENIORCLASS. Such an EMD-S can then be exchanged into individual 

passenger tickets or EMDs with specific passenger names.

.....
Attachment ‘B’

ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION 

MATRIX – AIRLINE

(amending)

T2.4/P T2.14/P

319 REISSUED FLOWN FLIGHT 

COUPON DATA – Begin:

-

320 ... 

324 ® Reissued Flown Fare 

Calculation Coupon/Itinerary 

Sequence Number

2 A/N C C C

325 ... 

340 Reissued Flown Ticket Designator 

(Not Applicable)

15 

A/N

341 Reissued Flown Ticket/Document 

Number

14 

A/N

C C

342 Reissued Flown Ticket Date of 

Issue

7 A/N C C

343 Reissued Flown Waiver Code 15 

A/N

C C C

344 ® Reissued Ticket Date of Issue 7 A/N C C C

345 ® Reissued Ticket Number 14 

A/N

C C C

346 REISSUED FLOWN FLIGHT 

COUPON DATA – End.

-

347 REISSUED TICKET/DOCUMENT 

DATE OF ISSUE (Not Applicable)

7 A/N C C

348 REISSUED TICKET/DOCUMENT 

NUMBER (Not Applicable)

14 

A/N

C C

Element Description

Data 

Element 

Sequence

Data element No. 

Char,

A, N, 

or A/N

Display Request 

Airport Control 

Change of Status System Update Unsolicited Billing

Req Res Req Res Req Res Req Res Req Res

...

30 Associated Fare Basis 15 A/N C M C M C

? Associated Fare Basis/Ticket 

Designator

15 A/N C C C

...

89 Coupon/Itinerary Sequence 

Number

2 A/N C C C

...

183 Total Base Construction Amount 12 A/N C C C

...

388.9 TAX/FEE/CHARGE DETAILS –

Begin:

389 Tax/Fee/Charge Amount 

Paid/New/To Be Refunded 

Qualifier

1 A C C C

390 Tax/Fee/Charge Amount 11 9

A/N

C C C

391 Tax/Fee/Charge Amount Currency 

Code

3 A C C C

...

416 Transaction Action 1 A M M M M M

417 Transaction Agent I.D. 11 A/N M M M M M
T5, T2.3/P

Row 

No.

Data Element

Transaction Action Code

No. Char. 

A, N, or 

A/N

Display

D

Request Airport

Control

B

Change of 

Status

C

System Update

U

Unsolicited 

Billing

L

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

59 Carrier Fee Tax Code (Not Applicable) 2 A/N

Carrier Fee Tax Type (not Applicable) 3 A/N

63 Carrier Fee Tax on Tax Code (Not 

Applicable)

2 A/N

Carrier Fee Tax Type (Not Applicable) 3 A/N

393 TAX/FEE/CHARGE CODE (Not 

Applicable)

2 A/N

TAX/FEE/CHARGE TYPE (Not 

Applicable)

3 A/N

405 Tax/Fee/Charge Code 2 A/N C C C

Tax/Fee/Charge Type 3 A/N C C C

417 Tax/Fee/Charge Tax Code (Not 

Applicable)

2 A/N

Tax/Fee/Charge Tax Type (Not 

Applicable)

3 A/N

420 Tax/Fee/Charge Filed Code (Not 

Applicable)

2 A/N

Tax/Fee/Charge Filed Type (Not 

Applicable)

3 A/N

...

Booking Office IATA Number

(Not Applicable) 8N

...

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015

RESOLUTION 725g

ELECTRONIC MISCELLANEOUS DOCUMENT—NEUTRAL

(amending)

PSC(35 36)725g Expiry: Indefinite

Type: B

RESOLVED that,

.....

Section 6 - Procedures

...

T2.10/P

6.1.9.1 CRS/System Providers shall ensure EMD eligibility before generating the 'Issuance',

and/or 'Exchange/Reissue' message or ‘System Update’ message, by verifying an EMD 

agreement exists between the Validating Carrier and both the Marketing Carrier and 

Operating Carrier of the EMD. When any segment in the itinerary is not EMD eligible, an 

alternative document may be issued.

T2.12/P

6.1.9.2 A separate EMD-A shall may be issued when multiple EMD coupons are 

required for the same ET flight coupon.

...

T2.8/P

6.2.2.1 An EMD-S shall be limited to one passenger or group name only. When the 

EMD-S is issued for passengers whose names are unknown (e.g. group deposit) use the 

name of the group leader or sponsor. If the group leader or sponsor name has one or 

more obliques separating portions of the group name; the name field will be considered in 

one of two ways:

Name field: SKITRIP/SENIORCLASS

1) Regardless of whether the Group Name has obliques or not,

send only the ‘Surname’ and nothing else, i.e. SKITRIP.

2) Or, if the Group Name has obliques, send the name as the Surname, i.e.

SKITRIPSENIORCLASS. Such an EMD-S can then be exchanged into individual 

passenger tickets or EMDs with specific passenger names.

....

6.10.1 Association initiated by the CRS/System Provider of EMD-A

T2.10/P

6.10.1.1 An agency may associate an EMD-A issued by the issuing agency or an accredited 

branch if authorized by the Validating Carrier. An EMD-A may be associated to an ET by the 

original issuing agency or accredited branch if authorized by the Validating Carrier. This action 

allows an agency to send an association request when a transaction has been performed 

which caused the EMD to become disassociated from the ET, thereby requiring the need for 

the EMD-A to be re-associated to the applicable ET coupon.

6.10.1.2 Prior to initiating a "System Update" message for association the CRS/System 

Provider shall verify that the EMD-A value coupons to be associated are not in final status, the 
operating carrier is the same and the same board and off points including multi-airports within 

the same metropolitan area are present in the same order as in the ET record to which the 

EMD-A will be associated and that the name of the passenger matches that of the passenger 

in the associated ET and that the EMD-A which has been previously issued, is used for the 

identical service.

6.10.1.3 The Validating Carrier of the EMD-A and each of the Operating Carrier shall be the 

same. 

6.10.1.4 

6.10.1.3 Upon receipt of the System Update message from the CRS/System Provider of the 

EMD-A, the validating carrier of the ET shall update the ET record with the in connection with 

Document number and the in the connection Coupon number and amend the in Connection 

With Qualifier to indicate that the EMD-A is associated.
Attachment ‘B’

ELECTRONIC MISCELLANEOUS DOCUMENT

MESSAGE CONSTRUCTION MATRIX

– NEUTRAL MESSAGES

T2.3/P, T2.14/P

RESOLUTION A4A 20.64 / IATA 725g – 2014 2015 – ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX – NEUTRAL 

MESSAGES

Row 

No.

Data Element

Transaction Action Code

No. 

Char. 

A, N or 

A/N

Issuance –

Information

S, I

Display

D

History 

Display

H

Exchange/ 

Reissue

E

Refund

R

System 

Cancel

X, Y

Refund 

Cancel

Z

Void

V, W

System 

Update

U

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

319© © REISSUED FLOWN FLIGHT COUPON DATA – Begin: -

320 ... 

324 ® Reissued Flown Fare Calculation Coupon/Itinerary 

Sequence Number

2 A/N C C C

339 ... 

340 Reissued Flown Ticket Designator 15 A/N C C C

341@ Reissued Flown Ticket/Document Number 14 A/N C C C

342@ Reissued Flown Ticket Date of Issue 7 A/N C C C

343 Reissued Flown Waiver Code 15 A/N C C C

344 ® Reissued Ticket Date of Issue 7 A/N C C C

345 ® Reissued Ticket Number 14 AN C C C

346 REISSUED FLOWN FLIGHT COUPON DATA – End. -

347 REISSUED TICKET/DOCUMENT DATE OF ISSUE (Not 

Applicable)

7 A/N C C C

348 REISSUED TICKET/DOCUMENT NUMBER (Not Applicable) 14 A/N C C C

....

Booking Office IATA Number

(Not Applicable) 8N

....
T5

RESOLUTION A4A 20.64 / IATA 725g – 2015 – ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX – NEUTRAL MESSAGES

Row 

No.

Data Element

Transaction Action Code

No. 

Char. 

A, N or 

A/N

Issuance –

Information

S, I

Display

D

History 

Display

H

Exchange/ 

Reissue

E

Refund

R

System 

Cancel

X, Y

Refund 

Cancel

Z

Void

V, W

System 

Update

U

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

59© Carrier Fee Tax Code 2 A/N C C C

Carrier Fee Tax Type 3 A/N C C C

63 Carrier Fee Tax on Tax Code 2 A/N C C C

Carrier Fee Tax on Tax Type 3 A/N C C C

393 TAX/FEE/CHARGE CODE (Not Applicable) 2 A/N

TAX/FEE/CHARGE TYPE (Not Applicable) 3 A/N

405 Tax/Fee/Charge Code 2 A/N C C C

Tax/Fee/Charge Type 3 A/N C C C

417© Tax/Fee/Charge Tax Code (Not Applicable) 2 A/N

Tax/Fee/Charge Tax Type (Not Applicable) 3 A/N

420 Tax/Fee/Charge Filed Code (Not Applicable) 2 A/N

Tax/Fee/Charge Filed Type (Not Applicable) 3 A/N

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015
RESOLUTION 725h

ELECTRONIC MISCELLANEOUS DOCUMENT—GROUND HANDLING

(amending)

PSC(35 36)725h Expiry: Indefinite

Type: B

Attachment ‘B’

ELECTRONIC MISCELLANEOUS DOCUMENTS MESSAGE CONSTRUCTION 

MATRIX – GROUND HANDLING

(amending)

T2.3/P, T2.14/P, T5

RESOLUTION 20.66 / 725h – 2014 2015 MANUAL - ELECTRONIC MISCELLANEOUS DOCUMENT 

MESSAGE CONSTRUCTION MATRIX

GROUND HANDLING MESSAGES

Row

No.

Data Element

Transaction Action Code

No.

Char.

A, N, or

A/N

Display

D

Airport Control 

Request – Ground 

Handling

G

Change of Status

C

System Update

U

REQ RESP REQ RESP REQ RESP REQ RESP

319 REISSUED FLOWN FLIGHT 

COUPON DATA – Begin:

-

320 ... 

324 ® Reissued Flown Fare Calculation 

Coupon/Itinerary Sequence Number

2 A/N C C

340 ... 

341@ @ Reissued Flown Ticket/Document 

Number (Not Applicable)

14 A/N

342@ @ Reissued Flown Ticket Date of 

Issue (Not Applicable)

7 A/N

343 Reissued Flown Waiver Code 15 A/N C C

344 ® Reissued Ticket Date of Issue 7 AN C C

345 ® Reissued Ticket Number 14 AN C C

346 REISSUED FLOWN FLIGHT 

COUPON DATA – End.

-

347 REISSUED TICKET/DOCUMENT 

DATE OF ISSUE (Not Applicable)

7 A/N

348 REISSUED TICKET/DOCUMENT 

NUMBER (Not Applicable)

14 A/N

...

Booking Office IATA Number

(Not Applicable) 8N

...

59 Carrier Fee Tax Code (not 

Applicable)

2 A/N

Carrier Fee Tax Type (not Applicable) 3 A/N

63 Carrier Fee Tax on Tax Code (Not 

Applicable)

2 A/N

Carrier Fee Tax on Tax Type (Not 

Applicable)

3 A/N
RESOLUTION 20.66 / 725h – 2014 2015 MANUAL - ELECTRONIC MISCELLANEOUS DOCUMENT 

MESSAGE CONSTRUCTION MATRIX

GROUND HANDLING MESSAGES

Row

No.

Data Element

Transaction Action Code

No.

Char.

A, N, or

A/N

Display

D

Airport Control 

Request – Ground 

Handling

G

Change of Status

C

System Update

U

REQ RESP REQ RESP REQ RESP REQ RESP

393 TAX/FEE/CHARGE CODE (Not 

Applicable)

2 A/N

TAX/FEE/CHARGE TYPE (Not 

Applicable)

3 A/N

405 Tax/Fee/Charge Code (Not 

Applicable)

2 A/N

Tax/Fee/Charge Type (Not 

Applicable)

3 A/N

417 Tax/Fee/Charge Tax Code (Not 

Applicable)

2 A/N

Tax/Fee/Charge Tax Type (Not 

Applicable)

3 A/N

420 Tax/Fee/Charge Filed Code (Not 

Applicable)

2 A/N

Tax/Fee/Charge Filed Type (Not 

Applicable)

3 A/N

Filing Period: Effective Date:

11 May 2015 12 June 2015

12 June 2015
INDUSTRY STANDARD 2725i*

THROUGH/CHANGE OF GAUGE FLIGHT for EMD-A

(new)

PSC(36)725i Expiry: Indefinite

Type: B

RESOLVED that:

.

* An Industry Standard sets forth procedures where uniformity among all Members is 

considered necessary or interline service but because of their developmental, technological or 

operational nature not all carriers follow these procedures. As a Member needs to be aware

whether its interline partner is using the procedure, Members keep their interline partners 

advised through the Secretary of the Conference.

At time of writing the following Members have advised they will not be bound by this Industry 

Standard: 

British Airways (BA);

Virgin Australia (VA)

1. SCOPE

The provisions of this Resolution shall apply to procedures for EMD-A(s) when the ancillary 

service is impacted by a through/change of gauge flight.

Requirements:

• The airline or travel agency shall issue a single ET flight coupon for the flight number 

even though there are one or more actual leg(s) on the flight;

• Each EMD-A shall be issued with only one Reason for Issuance Code.

The business need being addressed is to provide the opportunity to sell one or more EMD-A(s) 

to/from the intermediate point(s) whilst being associated to the ET flight coupon(s) from origin to 

destination. The EMD-A value coupon(s) may have a different board and/or off point to the ET 

flight coupon. 

2. DEFINITIONS

Change of Gauge - Flight which is published by an airline as a direct flight between two points 

but which involves one or more changes of aircraft type en route. Typically this would involve a 

short-haul service feeding to, or continuing from, a long-haul flight.

Flight Segment Number - When used in the PNR Data Exchange, the flight segment number 

is used for change of gauge flights to indicate the segment within an origin and destination 

where the flight changes aircraft. For example, assuming a flight operates SFO DEN ORD IAH 

MSY and there is an aircraft change in IAH and a passenger is booked DEN MSY, segment one 

would be DEN IAH and segment two would be IAH MSY. This method is used to identify such 

information as global route, etc.
Itinerary - The part of the PNR describing the flight segments booked for the passengers 

named in the name field of the PNR.

Journey - Travel between an airport/city where travel commences and an airport/city where

travel ultimately terminates. A journey is one or more segments.

Leg - Two consecutive airports/cities on any given flight.

Through Flight – A flight that makes one or more intermediate stop(s) en route to destination.

3. TECHNICAL SPECIFICATION

3.1. PROCEDURES

3.1.1. GENERAL

Resolution 105.70, Schedule Change Action, is the guiding principle for schedule change 

practices along with applicable AIRIMP/SIPP procedures.

When a schedule change occurs on an ET flight that adds or deletes an intermediate stop(s), 

making a non-stop a through/change of gauge flight or vice versa, the procedures for handling 

an associated EMD-A are as follows: 

When a schedule change occurs that creates a Through/Change of Gauge Flight, disassociate 

the EMD-A value coupon(s) from the ET and update the Through/Change of Gauge Flight 

Indicator on the ET Flight Coupon to indicate the ET Flight Coupon is a Through/Change of 

Gauge Flight. 

Or

When a schedule change occurs that causes a flight to be non-stop, disassociate the EMD-A 

value coupon(s) and update the Through/Change of Gauge Flight Indicator on the ET Flight 

Coupon to indicate the ET Flight Coupon is not a Through/Change of Gauge Flight. 

In either case, re-association of the EMD-A value coupon to the ET flight coupon will require a 

System Update. 
3.2. ISSUANCE INFORMATION

3.2.1. Validating Carrier

3.2.1.1 Prior to issuing an EMD-A, the Validating Carrier shall verify the following:

• the same board and off points shall be present in the same order as in the ET record 

to which the EMD-A will be associated 

• the Operating Carrier of the EMD-A value coupon matches the Operating Carrier of the 

ET flight coupon 

• the passenger name matches that of the passenger name in the associated ET.

When the Through/Change of Gauge Flight Indicator is present on the ET flight coupon, the 

association of EMD-A value coupon(s) may occur if the board and off points of the EMD-A value 

coupon(s) do not match that of the ET record.

3.2.1.2. Prior to initiating a ‘System Update’ message for association the Validating Carrier shall 

verify the following:

• the EMD-A value coupons to be associated are not in final status 

• the same board and off points shall be present in the same order as in the ET record 

to which the EMD-A will be associated 

• the Operating Carrier of the EMD-A value coupon matches the Operating Carrier of the 

ET flight coupon 

• the passenger name in the EMD-A matches that of the passenger name in the 

associated ET. 

When the Through/Change of Gauge Flight indicator is present on the ET flight coupon, the 

association of EMD-A value coupon(s) may occur if the board and off points of the EMD-A value 

coupon(s) do not match that of the ET record.

3.2.2. Agency/neutral

3.2.2.1. Prior to issuing an EMD-A, CRS/System Provider shall verify the following by using a 

‘Display’ message:

• the same board and off points of the EMD-A value coupon are present and in the 

same order as in the ET record to which the EMD-A will be associated, 

• the Operating Carrier of the EMD-A value coupon matches the Operating Carrier of the 

ET flight coupon 

• the passenger name matches that of the passenger name in the associated ET. 

When the Through/Change of Gauge Flight Indicator is present on the ET flight coupon, the 

association of EMD-A value coupon(s) may occur if the board and off points of the EMD-A value 

coupon(s) do not match that of the ET record.
3.2.2.2 Prior to initiating a ‘System Update’ message for association the CRS/System Provider shall 

verify the following:

• the EMD-A value coupon(s) to be associated are not in final status 

• the same board and off points shall be present in the same order as in the ET record 

to which the EMD-A will be associated 

• the Operating Carrier of the EMD-A value coupon matches the Operating Carrier of the 

ET flight coupon 

• the passenger name in the EMD-A matches that of the passenger name in the 

associated ET.

• the EMD-A which has been previously issued, is used for the identical service 

When the Through/Change of Gauge Flight Indicator is present on the ET flight coupon, the 

association of EMD-A value coupon(s) may occur if the board and off points of the EMD-A value 

coupon(s) do not match that of the ET record.

3.2.3. Ground Handling

Prior to initiating a system update message for association, the CRS/System Provider shall verify 

the following:

• the EMD-A value coupon(s) to be associated are not in final status 

• the same board and off points shall be present in the same order as in the ET record 

to which the EMD-A will be associated 

• the Operating Carrier of the EMD-A value coupon matches the Operating Carrier of the 

ET flight coupon 

• the passenger name matches that of the passenger name in the associated ET.

When the Through/Change of Gauge Flight Indicator is present on the ET flight coupon, the 

association of EMD-A value coupon(s) may occur if the board and off points of the EMD-A value 

coupon(s) do not match that of the ET record.

4. EXAMPLES

Scenario 1: LAXLON operated by DL as a Through Flight over ATL

ET sold as LAXLON DL 123 

LAXATL no ancillary services purchased on this leg; 

ATLLON passenger purchases emergency exit seat on this leg;

EMD sold as ATLLON DL

Note: Reference AIRIMP paragraph 3.19.11. 

Scenario 2: LAXLON operated by DL as a Through Flight over ATL

ET sold as LAXLON DL 123

LAXATL passenger purchases a Pre-Reserved Seat on this leg;

ATLLON passenger purchases emergency exit seat on this leg;
2 EMD coupons are to be associated and lifted with the one ET flight coupon; 

EMD sold as LAXATL DL 

EMD sold as ATLLON DL

The indicator allows an EMD-A value coupon with a different origin and destination to be 

associated to the ET flight coupon. Both EMD-A value coupon(s) are to be lifted in 

synchronization with the ET flight coupon lift. 

Scenario 3: LAXLON operated by DL as a COG over ATL

ET sold as LAXLON DL 123 

LAXATL operated by A320, no ancillary services available on this leg; 

ATLLON operated by 777, passenger purchases emergency exit seat on this leg;

EMD sold as ATLLON DL
722f

ELECTRONIC TICKET AND MISCELLANEOUS DOCUMENTS DATA ELEMENTS 

GLOSSARY

(amending)

THROUGH/CHANGE OF GAUGE FLIGHT INDICATOR – 1 ALPHA

(Applicable to 722f/20.60, 722g/20.61, 722h/20.62 and 2725i/20.67) (Applicable to 

IATA: Not adopted as a Resolution. Adopted as an Industry Standard only. Carriers BA 

and VA are not bound by this Industry Standard).

An ET flight coupon indicator that identifies the flight has one or more intermediate 

stop(s).

Y = Through/Change of Gauge flight

N (or blank) = Not a Through/Change of Gauge flight

Attachment ‘B’

Data Element No. 

Characters

A, N 

OR A/N

Display

Transaction

Action Code

D

Unsolicited 

Airport 

Control

Transaction 

Action Code

T (I-A4A 

ONLY)

Information -

A4A Only)

History

Display

Transaction 

Action Code

H

Request 

Airport 

Control

Transaction 

Action Code

B

Change of 

Status

Transaction

Action Code

C

Redirect 

Airport

Control

Transaction

Action Code

N

Reservation 

Change

Transaction

Action 

Code

A

Emergency

Lock

Transaction

Action 

Code

M

System 

Update

Transaction

Action Code

U

20.60/722f - REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

THROUGH/ 

CHANGE OF 

GAUGE 

FLIGHT 

INDICATOR15

1 A C C C C C

15 Not adopted as a Resolution. Adopted as an Industry Standard only. Carriers BA and VA are not bound by this 

Industry Standard

Row 

No.

First

Use

2014 A4A / IATA Resolutions Glossary Applicability 

Reference Table (GART) 

Effective 01 June 2015 – 31 May 2016

Data Element (or Data Group) 

No. 

Ch

ar. 

A, 

N 

or

A/

N

722f / 

20.60

722g 

/ 

20.6

1

722h / 

20.62

725f 

/ 

20.6

3

725g / 

20.64

725h / 

20.66

445 15:1 THROUGH/CHANGE OF GAUGE FLIGHT INDICATOR 15 1 A Y Y Y
RESOLUTION 722g

ELECTRONIC TICKET — NEUTRAL

(amending)

Attachment ‘B

Data Element No. 

Characters

A, N 

OR A/N

Issuance – 

Information

Transaction

Action Code

S AND I

(I applicable 

to A4A only)

Display

Transaction

Action Code

D

History

Display

Transaction 

Action Code

H

Exchange/

Reissue

Transaction

Action Code

E

Reservation

Change

Transaction

Action Code

A

Refund

Transaction

Action Code

R

Refund 

Cancel

Transaction 

Action Code

Z

System 

Cancel

Transaction

Action 

Codes

X And Y

Void

Transaction

Action Codes

V And W

20.61/722g - REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

THROUGH/CH

ANGE OF 

GAUGE 

FLIGHT 

INDICATOR15

1 A C C C C C

15. Not adopted as a Resolution. Adopted as an Industry Standard only. Carriers BA and VA are not bound by this 

Industry Standard

A4A Resolution 722h

ELECTRONIC TICKET — GROUND HANDLING

(amending)

Attachment ‘B’ 

Data Element No. Characters

A, N OR A/N

Display

Transaction

Action Code

D

Request 

Airport 

Control

Ground 

Handling

Transaction 

Action Code

B

Change of 

Status

Transaction

Action Code

C

Redirect 

Airport 

Control

Transaction

Action Code

N

Emergency 

Lock

Transaction

Action Code

M

Unsolicited 

Airport 

Control

Ground 

Handling

Transaction

Action Code

K

System 

Update

 

Transaction

Action Code

U

20.62/722H REQ RESP REQ RESP REQ RESP REQ REQ RESP REQ REQ RESP REQ RESP

THROUGH/CH

ANGE OF 

GAUGE 

FLIGHT 

INDICATOR15

1 A C C C C C

15. Not adopted as a Resolution. Adopted as an Industry Standard only. Carriers BA and VA are not bound by this Industry 

Standard
RESOLUTION 725f

ELECTRONIC MISCELLANEOUS DOCUMENT — AIRLINE

(amending)

Data Element No. 

Characters

A, N 

OR A/N

Display

Transaction

Action Code

D

Request 

Airport 

Control

Transaction 

Action Code

B

Change of 

Status

Transaction

Action Code

C

System 

Update

Transaction

Action Code

U

Unsolicited 

Billing

Transaction

Action Code

L

20.63/725f REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

THROUGH/CHANGE 

OF GAUGE FLIGHT 

INDICATOR15 (Not 

Applicable)

1 A

15. Not adopted as a Resolution. Adopted as an Industry Standard only. Carriers BA and VA are not bound by this Industry 

Standard

RESOLUTION 725g

ELECTRONIC MISCELLANEOUS DOCUMENT — NEUTRAL

(amending)

Data 

Element 

No. 

Char

acte

rs

A, N 

OR 

A/N

Issuance – 

Information

Transaction

Action Code

S AND I

(I applicable 

to A4A only)

Display

Transaction

Action Code

D

History

Display

Transaction 

Action Code

H

Exchange/

Reissue

Transaction

Action Code

E

Refund

Transaction

Action Code

R

Refund 

Cancel

Transaction 

Action Code

Z

Void

Transaction

Action Codes

V And W

System 

Cancel

Transaction

Action 

Codes

X And Y 

System 

Update

Transaction

Action Codes

U

20.64/725g REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP RESP RESP REQ RESP REQ RESP REQ RESP

THROUGH

/ CHANGE 

OF GAUGE 

FLIGHT 

INDICATO

R15 (Not 

Applicable)

1 A

15. Not adopted as a Resolution. Adopted as an Industry Standard only. Carriers BA and VA are not bound by this 

Industry Standard
RESOLUTION 725h

ELECTRONIC MISCELLANEOUS DOCUMENT — GROUND HANDLING

(amending)

Attachment ‘B’

Data Element No. Characters

A, N OR A/N

Display

Transaction

Action Code

D

Request Airport Control

Ground Handling

Transaction Action Code

B

Change of Status

Transaction

Action Code

C

System Update

Transaction

Action Code

U

20.66/725H REQ RESP REQ RESP REQ RESP REQ RESP

THROUGH/CHA

NGE OF GAUGE 

FLIGHT 

INDICATOR15

(Not Applicable)

1 A

15. Not adopted as a Resolution. Adopted as an Industry Standard only. Carriers BA and VA are not bound by this 

Industry Standard

Filing Period: Effective Date:

11 May 2015 11 June 2015

11 June 2015

RESOLUTION 722f

ELECTRONIC TICKET—AIRLINE

(amending)

The provisions outlined in these updates will apply with effect from 01 June 2020

Section 1—Introduction/Scope

...

1.6. The same document number shall not be re-assigned for a minimum of 2 years.

...

6.1 GENERAL

...

6.1.7 All Marketing carriers participating in the itinerary including the Validating Carrier 

shall be notified by the Validating Carrier that a ticket has been issued electronically. 

This notification shall be sent at the time of ET issuance or exchange/reissue and shall 

take the form of an SSR TKNE message which includes the ET document number and 

Ticketing Date of Issue as defined in AIRIMP.

...

6.1.12 The document date of issue along with the document number identifies the 

record uniquely. 

The inclusion of the Ticketing Date of Issue does not require a new data element. The 

existing data elements, Ticket/Document Number along with the Ticketing Date of 

Issue, are used together.

...

6.3 DISPLAY

...

6.3.3 Alternate search criteria to display an ET are:

Ticket/Document Number & Ticketing Date of Issue

--OR--

Date of Flight, Origin Airport/City Code, Destination Airport/City Code, Passenger Name

Note: This data shall be “current” or all “sold as” data.

—OR—

Airline Designator (Marketing Carrier) Flight Number, Date of Flight, Origin Airport/City 

Code, Destination Airport/City Code, Passenger Name

Note: This data shall be “current” or all “sold as” data.

—OR—

Frequent Flyer Reference, Date of Flight

—OR—

Credit Card Number, Date of Flight, Passenger Name

—OR—

Airline Confirmation Number
—OR—

Passenger Telephone Number, Passenger Name & Date of Flight

—OR—

Passenger Check-in Identification Type (FOID) — Optional.1

...

6.4.6 Change of Status

...

6.4.6.1.3 When the Carrier holding control is notifying the Validating Carrier of final 

Coupon Status of Exchange/ Reissue as a result of an E-ticket being exchanged to 

another E-ticket or EMD, the new reissue ticket number or EMD number issued by that 

carrier shall be included in the “Change of Status” request message. The Ticketing Date 

of Issue shall be included for the exchanged document number(s) and the new e-ticket 

number or EMD-S number(s).

When the exchange transaction results in a residual value and the carrier initiating the 

exchange elects to issue an EMD for this residual value, an EMD-S shall be issued. 

When an EMD-S is issued for residual value, the carrier shall generate a single change 

of status message to the validating carrier including the new e-ticket number and the 

EMD-S number(s) issued for the residual value. The Ticketing Date of Issue shall be 

included for the exchanged document number(s) and the new e-ticket number and the 

EMD-S number(s).

...

6.7 PASSENGER PROCESSING

6.7.1 When printing a Boarding Pass against an Electronic Ticket, the following data 

shall be imprinted, in addition to the normal entries:

the code “ETKT”; 

the words “Passenger Ticket & Baggage Check” (optional);

the ET document number and Ticketing Date of Issue (optional).

...

6.10 EXCHANGE/REISSUE

...

6.10.4 When the exchange/reissue transaction results in a residual value and the carrier 

initiating the exchange/ reissue elects to issue an EMD for residual value, an EMD-S 

shall be issued. When an EMD-S is issued for residual value, the carrier shall generate 

a single change of status message to the validating carrier including the new e-ticket 

number and the EMD-S number(s) issued for the residual value. The Ticketing Date of 

Issue shall be included for the exchanged document number(s) and the new e-ticket 

number and the EMD-S number(s)
...

6.13 HISTORY DISPLAY

...

6.13.3 The search criterion to display “History” is the Ticket/Document Number and 

Ticketing Date of Issue.

...

6.16 TICKET HANDLER PROCESS

...

6.16.3.1 Upon receipt of the Change of Status Message from the Ticket Handler, the 

Operating Carrier shall initiate an even Exchange/Reissue transaction against the 

Ticket/Coupon numbers(s) received from the Ticket Handler for the passenger's original 

itinerary and send Change of Status message, which shall include the exchanged 

document number(s) and Ticketing Date of Issue for the exchanged document(s) and 

the new reissue ticket number and Ticketing Date of Issue for the new reissue ticket, to 

the Validating Carrier to set coupon status to Exchanged/Reissued, or deny the request.

6.16.3.2 If a positive response is received from the Validating Carrier to the Change of 

Status Message, the Operating Carrier shall send a positive response to the Ticket 

Handler including the new reissued Ticket Number(s) and Ticketing Date of Issue for 

the new reissued ticket. No SAC shall be sent. If a negative response is received from 

the Validating Carrier, the Operating Carrier shall void the new reissued Ticket 

Number(s) and deny the request to the Ticket Handler.

6.16.3.3 Upon receipt of a positive response from the Operating Carrier the Ticket 

Handler shall perform a further exchange transaction against the new reissued Ticket 

Number(s) and Ticketing Date of Issue, for the passenger’s new itinerary and send a 

Change of Status message to the Operating Carrier to set coupon status to 

Exchanged/Reissued

6.17 SYSTEM UPDATE

...

6.17.5 Upon receipt of a System Update message to associate, the receiving system 

shall update the ET record with the In Connection With Document Number, the In 

Connection with Document Ticketing Date of Issue and the In Connection With Coupon 

Number and amend the In Connection With Qualifier to indicate that the EMD-A is 

associated.
722f/20.60, Attachment ‘A’

ELECTRONIC TICKET AND MISCELLANEOUS DOCUMENTS DATA

ELEMENTS GLOSSARY

...

IN CONNECTION WITH DOCUMENT NUMBER TICKETING DATE OF ISSUE - 7 

ALPHANUMERIC

The date a document was issued in the format DDMMMYY for the In Connection with 

Document Number.

...

ISSUED IN EXCHANGE FOR—24 32 ALPHANUMERIC

(Repeatable field)

The 14 digit document number followed by an oblique (/), followed by the associated 

coupon number(s) being exchanged followed by an oblique (/) and the Ticketing Date of 

Issue, followed by an oblique (/) and the corresponding exchange coupon media (P = 

paper, E = Electronic); (i.e. 00000000000000/234/DDMMMYY/EEE).The Ticketing Date 

of Issue is not required for paper media.

...

TAX/FEE/CHARGE DATA TICKET/DOCUMENT NUMBER TICKETING DATE OF 

ISSUE – 7 ALPHANUMERIC

The date a document was issued in the format DDMMMYY for the Tax/Fee/Charge Data 

Ticket/Document Number.
Attachment ‘B’ MESSAGE CONSTRUCTION MATRIX—AIRLINE MESSAGES

RESOLUTION 20.60 / 722f – 2014 MANUAL – ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – AIRLINE MESSAGES

Row

No.

Data Element

Transaction Action Code

No.

Char.

A, N, or

A/N

Display

D, J

History

Display

H

Request

Airport

Control

B

Change of

Status

C

Redirect

Airport

Control

N

Reservation

Change

A

Emergency

Lock

M

System

Update

U

Unsolicited

Airport

Control

T, I 3

REQ RESP REQ RESP REQ RES

P

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

NEW IN CONNECTION WITH 

DOCUMENT NUMBER 

TICKETING DATE OF ISSUE

7A/N C13 C13 M C13

...

231 ISSUED IN EXCHANGE FOR 24 32 A/N C C C C

...

274 ORIGINAL ISSUE DATE 

(DDMMMYY)

7A/N C13 C13 C13

...

NEW TAX/FEE/CHARGE DATA 

TICKET/DOCUMENT NUMBER 

TICKETING DATE OF ISSUE

7 A/N C13 C13 C13

...

430 TICKET/DOCUMENT NUMBER 14 A/N O CM M C M M M C 5 M O M O M M M

431 TICKETING DATE OF ISSUE 

(DDMMMYY)

7 A/N O CM M C13 M M M C 5, 13 M C13 M C13 M M M

New footnote 13 – If the Ticket/Document Number is included in the response, the Ticketing Date of Issue shall be included. 
RESOLUTION 722g

ELECTRONIC TICKET—NEUTRAL

(amending

Section 1—Introduction/Scope

...

1.5 The same document number shall not be re-assigned for a minimum of 2 years.

...

6.1 GENERAL

...

6.1.7 All carriers participating in the itinerary including the Validating Carrier shall be 

notified by the CRS/System Provider that a ticket has been issued electronically. This 

notification shall be sent at the time of ET issuance or exchange/reissue and shall take 

the form of an SSR TKNE message which includes the ET document number and 

Ticketing Date of Issue as defined in AIRIMP.

...

6.1.10 Date of issue along with document number identifies the record uniquely. 

The inclusion of the ticketing date of issue does not require a new element, existing 

ticket/document number along with the ticketing date of issue are used together.

...

6.3 DISPLAY

...

6.3.5 Alternate search criteria to display an ET are:

Ticket/Document Number & Ticketing Date of Issue

--OR--

Date of Flight, Origin Airport/City Code, Destination Airport/City Code, Passenger Name

—OR—

Airline Designator (Marketing Carrier) Flight Number, Date of Flight, Origin Airport/City 

Code, Destination Airport/City Code, Passenger Name

—OR—

Frequent Flyer Reference, Date of Flight

—OR—

Credit Card Number, Date of Flight, Passenger Name

—OR—

Airline Confirmation Number

—OR—
Passenger Telephone Number, Passenger Name & Date of Flight

—OR—

Passenger Check-In Identification Type (FOID)—

Optional1

...

6.6 EXCHANGE/REISSUE

...

6.6.8 When the exchange/reissue transaction results in a new administration value 

document(s) e.g. refundable balance, non-refundable balance or penalty fee, and where 

the GDS/System Provider has been directed by the Validating Carrier to issue an EMD, 

the GDS/System Provider shall issue an EMD-S for that balance. When an EMD-S is 

issued for a refundable balance, non-refundable balance and/or penalty fee, the 

GDS/System Provider shall generate a single exchange/reissue request message to the 

Validating Carrier including the new ET number(s) or EMD number(s) and the EMD-S 

number(s) issued for the refundable balance, non-refundable balance or penalty fee as 

applicable. The Ticketing Date of Issue shall be included for the exchanged document 

number(s) and the new E-Ticket number(s) or EMD number(s) and the EMD-S 

number(s).

...

6.9.3 Void Exchange/Reissue

...

6.9.3.3 When the Void message is sent to cancel an Exchange/Reissue transaction and 

the new document is either ET or EMD, the Validating Carrier shall update the coupon 

status of the new ET or EMD coupon(s) to ‘V’ for ‘Void’, update the Coupon Status of 

the coupon(s) being exchanged/reissued to ‘O’ for ‘Open For Use’, and transmit a 

Settlement Authorisation Code, or deny the request. The document number(s) being 

exchanged and the new ET or EMD document number(s) will be included in the 

request. The Ticketing Date of Issue shall be included for the exchanged document 

number(s) and the new e-ticket number or the EMD-S number(s).

When the exchange/reissue transaction included an EMD-S(s) for a refundable balance, 

non-refundable balance or penalty fee, the Validating Carrier shall also update the 

coupon status of the EMD-S(s) to ‘V’ for ‘Void’ and transmit a separate Settlement 

Authorization Code for the EMD-S(s)....
6.12 HISTORY DISPLAY

...

6.12.3 The search criterion to display “History” is the Ticket Number and Ticketing Date 

of Issue.
Attachment ‘B’ ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX—NEUTRAL MESSAGES

RESOLUTION A4A 20.61 / IATA 722g – 2014 – ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – NEUTRAL MESSAGES

Row 

No.

Data Element

Transaction Action Code

No. Char. A, 

N or A/N

Issuance –

Information

S, I 7

Display

D

History

Display

H

Exchange/

Reissue

E

Refund

R

Reservation

Change

A

System 

Cancel

X,Y

Refund 

Cancel

Z

Void

V,W

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RES

P

...

NEW IN CONNECTION WITH DOCUMENT 

NUMBER TICKETING DATE OF 

ISSUE

7A/N C8 C8 C8 C8 C8

231 ISSUED IN EXCHANGE FOR 24 32 A/N C 3 C C M 3 C C C 1 C 1

...

274 ORIGINAL ISSUE DATE 

(DDMMMYY)

7A/N C8 C8 C8 C8 C8

...

NEW TAX/FEE/CHARGE DATA 

TICKET/DOCUMENT NUMBER 

TICKETING DATE OF ISSUE

7 A/N C8 C8 C8

...

430 TICKET/DOCUMENT NUMBER 14 A/N M O O CM M C M C M C M O M O M O M O

431 TICKETING DATE OF ISSUE 

(DDMMMYY)

7 A/N M C8 O CM M C8 M C8 OM C OM C8 OM C8 M C8 OM C8

8 – if the Ticket/Document number is included in the response, the Ticketing Date of Issue shall be included.
RESOLUTION 722h

ELECTRONIC TICKET—GROUND HANDLING

(amending)

...

Section 1—Introduction/Scope

...

1.5 The same document number shall not be re-assigned for a minimum of 2 years ...

6.1 GENERAL

...

6.1.5The document date of issue along with the document number identifies the record 

uniquely. 

The inclusion of the Ticketing Date of Issue does not require a new data element. The 

existing data elements, Ticket/Document Number along with the Ticketing Date of 

Issue, are used together.

...

6.2 Display

...

6.2.4 Alternate search criteria to display an ET are:

Ticket/Document Number & Ticketing Date of Issue

--OR--

Airline Confirmation Number

—OR—

Date of Flight, Origin Airport/City Code, Destination Airport/City Code, Passenger Name

(Note: This data shall be all “current” or all “sold as” data)

—OR—

Airline Designator (Marketing Carrier) Flight Number, Date of Flight, Origin Airport/City 

Code, Destination Airport/City Code, Passenger Name

(Note: This data shall be all “current” or all “sold as” data)

—OR—

Frequent Flyer Reference, Date of Flight

—OR—

Credit Card Number, Date of Flight, Passenger

Name

—OR—

Passenger Telephone Number, Passenger Name & Date of Flight

—OR—
Passenger check-in identification (FOID) (optional)1

...

6.3.11 System Update

...

6.3.11.7 Upon receipt of a System Update message to associate, the receiving system 

shall update the ET record with the In Connection With Document Number, In 

Connection with Document Ticketjng Date of Issue and the In Connection With Coupon 

Number.

...

6.5 PASSENGER PROCESSING

6.5.1 When printing a Boarding Pass against an Electronic Ticket, the following data 

shall be imprinted, in addition to the normal entries:

the code “ETKT”; 

the words “Passenger Ticket & Baggage Check” (optional);

the ET document number and Ticketing Date of Issue (optional).

...
Attachment ‘B’ MESSAGE CONSTRUCTION MATRIX—GROUND HANDLING

RESOLUTION A4A 20.62 / IATA 722h – 2014 – ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – GROUND HANDLING MESSAGES

Row 

No.

Data Element

Transaction Action Code

No. 

Char. 

A, N or 

A/N

Display

D

Airport 

Control

Request –

Ground 

Handling

G

Change 

of Status

C

Redirect 

Airport 

Control

N

Emergen

cy Lock

M

Unsolicite

d

Airport 

Control –

Ground 

Handling

K

System 

Update

U

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

NEW IN CONNECTION WITH DOCUMENT NUMBER TICKETING 

DATE OF ISSUE

7 A/N C 12 C 12 C 12 M

...

231 ISSUED IN EXCHANGE FOR 24 32 A/N C C C

...

274 ORIGINAL ISSUE DATE (DDMMMYY) 7 A/N C 12 C 12 C 12

...

276 ORIGINAL ISSUE TICKET/DOCUMENT NUMBER 14 A/N C C C

NEW TAX/FEE/CHARGE DATA TICKET/DOCUMENT NUMBER 

TICKETING DATE OF ISSUE (NOT APPLICABLE)

7 A/N

...

430 TICKET/DOCUMENT NUMBER 14 A/N O CM M M M C M O M M M

431 TICKETING DATE OF ISSUE (DDMMMYY) 7 A/N O CM M M M C 5, 12 M C 12 M M M

12 – if the Ticket/Document number is included in the response, the Ticketing Date of Issue shall be included.
RESOLUTION 725f

ELECTRONIC MISCELLANEOUS DOCUMENT—AIRLINE

(amending)

Section 1—Introduction/Scope

...

1.14 The same document number shall not be re-assigned for a minimum of 2 years.

...

6.1 GENERAL

...

6.1.9 All Operating Carriers participating in the itinerary including the Validating Carrier 

shall be notified by the Validating Carrier that an EMD has been issued. This 

notification shall be sent at the time of EMD issuance or exchange/reissue and shall 

take the form of an SSR ASVC message or an auxiliary service element SVC 

message which includes the EMD document number and Ticketing Date of Issue as 

defined in AIRIMP.

6.1.10 The document date of issue along with the document number identifies the 

record uniquely. 

The inclusion of the Ticketing Date of Issue does not require a new data element. The 

existing data elements, Ticket/Document Number along with the Ticketing Date of 

Issue, are used together.

...

6.2 ISSUANCE

...

6.2.2.3 When an EMD-S is issued for residual value, the original issue document 

number and the issued in exchange for document numbers shall be included in the 

EMD-S message. The Ticketing Date of Issue shall be included for the original issue 

document number(s) and the issued in Exchange for Document numbers.

...
6.3 SYSTEM UPDATE

...

6.3.6.3 Upon receipt of the System Update message from the Validating Carrier of the 

EMD-A, the Validating Carrier of the ET shall update the ET record with the In 

Connection With Document Number and Ticketing Date of Issue and the In Connection 

With Coupon Number and amend the In Connection With Qualifier to indicate that the 

EMD-A is associated.

6.3.6.4 Upon receipt of the System Update message from the Validating Carrier of 

the EMD-A, the Operating Carrier of the ET, when holding control of the corresponding 

ET flight coupon(s), shall update its ET record with the In Connection With Document 

Number, In Connection with Document Number Ticketing Date of Issue and the In 

Connection With Coupon Number. The Operating Carrier shall then request control of 

the corresponding EMD-A value coupon(s) in accordance with ‘Request Airport Control’ 

procedures.

...

6.3.7.2 Upon receipt of the System Update message from the Operating Carrier, 

the Validating Carrier of the EMD-A shall update the EMD-A with the new ‘In 

Connection with Document Number’, the In Connection with Document Number 

Ticketing Date of Issue and the new ‘In Connection With Coupon Number’ and 

amend the ‘In Connection With Qualifier’ to indicate the EMD-A is associated.

...

6.3.7.5 Upon receipt of System Update Message from the Validating Carrier of the 

EMD-A, the Validating Carrier of the ET and the Operating Carrier(s), when holding 

control of the corresponding ET flight coupon(s), of the ET, and the Operating Carrier(s) 

shall update its ET record with the new In Connection With Document Number, the In 

Connection with Document Number Ticketing Date of Issue and the new In Connection 

With Coupon Number and amend the In Connection With Qualifier to indicate the EMDA is associated.

...

6.4 DISPLAY

...

6.4.3 Alternate search criteria to display an EMD are:

Ticket/Document Number & Ticketing Date of Issue

--OR--

Frequent Flyer Reference

—OR—

Credit Card Number, Passenger Name

—OR—

Passenger Check-In Identification Type (FOID)—

(Optional) 1
6.5 CONTROL

...

6.5.8.5.1 When the Carrier holding control is notifying the Validating Carrier of final 

Coupon Status of Exchange/Reissue as a result of an EMD being exchanged to another 

EMD or E-ticket, the new EMD number or new ticket number shall be included in the 

‘Change of Status’ request message. The Ticketing Date of Issue shall be included for 

the new EMD number(s) or the new ticket number.

...

6.7 EXCHANGE/REISSUE

...

6.7.4 When an exchange/reissue transaction results in a residual value and the Carrier 

initiating the exchange/reissue elects to issue an EMD for the residual value an EMD-S 

shall be issued. When an EMD-S is issued for residual value, the carrier shall generate 

a single change of status message to the validating carrier including the new e-ticket 

number and the EMD-S number(s) issued for the residual value. The Ticketing Date of 

Issue shall be included for new E-Ticket number and the new EMD-S number(s). ...

6.10 TICKET HANDLER PROCESS

...

6.10.3.2 If a positive response is received from the Validating Carrier to the Change of 

Status Message, the Operating Carrier shall send a positive response to the Ticket 

Handler including the new reissued EMD Number(s) and the Ticketing Date(s) of Issue.

No SAC shall be sent. If a negative response is received from the Validating Carrier, the 

Operating Carrier shall void the new reissued EMD Number(s) and deny the request to 

the Ticket Handler.
Attachment ‘B’ ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX— AIRLINE 

MESSAGES

RESOLUTION A4A 20.63 / IATA 725f – 2015 – ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX – AIRLINE MESSAGES

Data Element

Transaction Action Code

No. Char. A, N, 

or A/N

Display

D

Request Airport

Control

B

Change of Status

C

System Update

U

Unsolicited 

Billing

L

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

NEW IN CONNECTION WITH DOCUMENT NUMBER 

TICKETING DATE OF ISSUE

7 A/N C14 C14 M C14

231 ISSUED IN EXCHANGE FOR 24 32A/N C C C

...

274 ORIGINAL ISSUE DATE (DDMMMYY) 7 A/N C14 C14 M C14

...

NEW TAX/FEE/CHARGE DATA TICKET/DOCUMENT NUMBER 

TICKETING DATE OF ISSUE

7 A/N C14 C14 C14

430 TICKET/DOCUMENT NUMBER 14 A/N O CM M M M C M M

431 TICKETING DATE OF ISSUE (DDMMMYY) 7 A/N O CM M M M C14 M M

14 – if the Ticket/Document number is included in the response, the Ticketing Date of Issue shall be included.
RESOLUTION 725g

ELECTRONIC MISCELLANEOUS DOCUMENT—NEUTRAL

(amending)

Section 1—Introduction/Scope

...

1.11 The same document number shall not be re-assigned for a minimum of 2 years.

...

6.1 GENERAL

...

6.1.8 All Operating Carriers participating in the itinerary including the Validating Carrier 

shall be notified by the CRS/System Provider that an EMD has been issued. This 

notification shall be sent at the time of EMD issuance or exchange/reissue and shall 

take the form of an SSR ASVC message or an auxiliary service element SVC message 

which includes the EMD document number and Ticketing Date of Issue as defined in 

AIRIMP.

6.1.9 The document date of issue along with the document number identifies the record 

uniquely. 

The inclusion of the Ticketing Date of Issue does not require a new data element. The 

existing data elements, Ticket/Document Number along with the Ticketing Date of 

Issue, are used together.

Editorial Note: Renumber existing 6.1.9 and 6.1.10 sections

...

6.2 ISSUANCE

...

6.2.2.3 When an EMD-S is issued for a refundable balance the original issue document 

number and the issued in exchange for document numbers shall be included in the 

EMD-S message. The Ticketing Date of Issue shall be included for the original issue 

document number(s) and the issued in Exchange for Document numbers.

...
6.3 DISPLAY

6.3.5 Alternate search criteria to display an EMD are:

Ticket/Document Number & Ticketing Date of Issue

--OR--

Frequent Flyer Reference

—OR—

Credit Card Number, Passenger Name

—OR—

Passenger Check-in Identification Type (FOID)—

(Optional)1

...

6.4 EXCHANGE/REISSUE

...

6.4.14 When initiating the exchange/reissue transaction, the new reissue EMD number 

or ticket number issued by the GDS shall be included in the exchange/reissue request 

message to the validating carrier to close out the EMD being exchanged. The Ticketing 

Date of Issue shall be included for the exchanged document number(s) and the new 

EMD number or ticket number issued by the GDS.

...

6.9 HISTORY DISPLAY

...

6.9.3 The search criterion for the ‘History Display’ EMD message is the Document 

Number and Ticketing Date of Issue.

...

6.10 SYSTEM UPDATE

...

6.10.1.4 Upon receipt of the System Update message from the CRS/System Provider of 

the EMD-A, the validating carrier of the ET shall update the ET record with the In 

Connection With Document Number, the In Connection with Document Number 

Ticketing Date of Issue and the In the Connection With Coupon Number and amend the 

In Connection With Qualifier to indicate that the EMD-A is associated.
Attachment ‘B’ ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION 

MATRIX— NEUTRAL MESSAGES

RESOLUTION A4A 20.64 / IATA 725g – 2014 – ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX – NEUTRAL 

MESSAGES

Row 

No.

Data Element

Transaction Action Code

No. 

Char. A, 

N or A/N

Issuance –

Information

S, I

Display

D

History 

Display

H

Exchange/ 

Reissue

E

Refund

R

System 

Cancel

X, Y

Refund 

Cancel

Z

Void

V, W

System 

Update

U

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

NEW IN CONNECTION WITH DOCUMENT 

NUMBER TICKETING DATE OF ISSUE

7 A/N C14 C14 C14 C14 C14 M

...

231 ISSUED IN EXCHANGE FOR 24 

32A/N

C3 C C M3 C C C1 C1

...

274 ORIGINAL ISSUE DATE (DDMMMYY) 7 A/N C14 C14 C14 C14 C14

...

NEW TAX/FEE/CHARGE DATA 

TICKET/DOCUMENT NUMBER 

TICKETING DATE OF ISSUE

7 A/N C14 C14 C14

...

430 © TICKET/DOCUMENT NUMBER 14 A/N M O O CM M C M C M C M O M O M O M

431 TICKETING DATE OF ISSUE 

(DDMMMYY)

7 A/N M C14 O CM M C14 M C14 O C14 OM C14 M C14 OM C14 M

14 – if the Ticket/Document number is included in the response, the Ticketing Date of Issue shall be included.
RESOLUTION 725h

ELECTRONIC MISCELLANEOUS DOCUMENT—GROUND HANDLING

(amending)

Section 1—Introduction/Scope

...

1. 7 The same document number shall not be re-assigned for a minimum of 2 years. ...

6.1 GENERAL

...

6.1.11The document date of issue along with the document number identifies the record 

uniquely. 

The inclusion of the Ticketing Date of Issue does not require a new data element. The 

existing data elements, Ticket/Document Number along with the Ticketing Date of 

Issue, are used together.

...

6.2 DISPLAY

...

6.2.4 Alternate search criteria to display an EMD are:

Ticket/Document Number & Ticketing Date of Issue

--OR--

Frequent Flyer Reference

—OR—

Credit Card Number, Passenger Name

—OR—

Passenger Check-In Identification Type (FOID)—

(Optional) 1

...
6.3.9 SYSTEM UPDATE

...

6.3.9.8 Upon receipt of a System Update message to associate, the receiving system 

shall update the ET

record with the ‘In Connection with Document Number, In Connection with Document 

Number Ticketing Date of Issue’ and the ‘In Connection with Coupon Number’.

...
Attachment ‘B’ ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX— GROUND 

HANDLING

RESOLUTION 20.66 / 725h – 2015 MANUAL - ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX

Ground Handling MESSAGES

Row

No.

Data Element

Transaction Action Code

No.

Char.

A, N, or

A/N

Display

D

Airport Control 

Request –

Ground Handling

G

Change of 

Status

C

System Update

U

REQ RESP REQ RESP REQ RESP REQ RESP

...

NEW IN CONNECTION WITH DOCUMENT NUMBER TICKETING DATE OF ISSUE 7 A/N C13 C13 M

...

231 ISSUED IN EXCHANGE FOR 24 32 A/N C C

...

274 ORIGINAL ISSUE DATE (DDMMMYY) 7 A/N C13 C13

NEW TAX/FEE/CHARGE DATA TICKET/DOCUMENT NUMBER TICKETING DATE OF ISSUE (NOT APPLICABLE) 7 A/N

430 TICKET/DOCUMENT NUMBER 14 A/N O C M M M M C M

431 TICKETING DATE OF ISSUE (DDMMMYY) 7 A/N O C M M M M C13 M

13 – if the Ticket/Document number is included in the response, the Ticketing Date of Issue shall be included.
Glossary Applicability Reference Table

The table represents the resolutions matrices in which the data elements are 

applicable

Y = This data element is used in at least one message in the Resolution listed.

For data element groups (e.g. CARRIER FEE DATA) a Y = At least one data 

element of this group is used in at least one message in the Resolution listed. 

Blank = This data element is not used in any message in the Resolution listed. 

2014 A4A / IATA Resolutions Glossary Applicability Reference Table (GART)

Data Element

No. Char. 

A, N or

A/N

722f / 

20.60

722g / 

20.61

722h / 

20.62

725f / 

20.63

725g / 

20.64

725h / 

20.66

IN CONNECTION WITH DOCUMENT NUMBER TICKETING DATE OF ISSUE 7 A/N Y Y Y Y Y Y

ISSUED IN EXCHANGE FOR 2432 A/N Y Y Y Y Y Y

TAX/FEE/CHARGE DATA TICKET/DOCUMENT NUMBER TICKETING DATE OF ISSUE 7 A/N Y Y Y Y

Filing Period: Effective Date:

11 May 2015 01 June 2020

11 June 2015
RESOLUTION 728

CODE DESIGNATORS FOR PASSENGER TICKET AND BAGGAGE CHECK

(amending)

PSC(35 36)728 Expiry: 

Indefinite

Type: B

RESOLVED that:

T3

.....

4.2. Special Fees and Charges Codes 

4.2.1 Passenger Tickets for Air Transportation.

Special Fees and Charges Codes are assigned to identify taxes, fees and 

charges which are collected at the time of ticket issuance, entered in the 

“TAX/FEE/CHARGE” box, and are paid or payable to government agencies and 

airport authorities. When applying to IATA for a new Special fees and Charges 

Code or applying to use an ISO code, or advising IATA about amendments to an 

existing code, the Application Form supplied separately by the IATA Ticket Tax 

Box Service (TTBS) shall be used. Only one code will be assigned for the same 

type Special Fee or Charge for multiple airports within a country. If the same type 

of Special Fee or Charge has different rules for domestic/international, separate 

Special Fees or Charges Codes may be assigned by IATA. For a full listing of 

ticket codes, refer to the IATA Airline Coding Directory.

4.2.2 Creation of Special Fees and Charges Codes for Electronic 

Miscellaneous Documents.

Except as provided for under paragraph 4.2.1 for the assignment of Special Fees 

and Charges Codes for Air Transportation published by the IATA Ticket Tax Box 

Service (TTBS), in order to identify special fees and charges that are to be applied 

to an EMD, the IATA Head, Airline Distribution Standards will assign codes to be 

applied separately to an Electronic Miscellaneous Document in accordance with 

the following criteria:-
4.2.2.1 Before submitting a request for a new Special Fees and Charges Code to be 

applied to Electronic Miscellaneous Documents, an airline shall check with TTBS 

whether any of the existing codes could be suitable. If that is not the case the new 

code requested must not duplicate any of the codes already published. Applications 

should be submitted to the TTBS using the Application Form supplied separately by 

TTBS;

4.2.2.2 A code will only be assigned provided there is no existing code published 

by TTBS that will apply for this purpose, for example, existing codes for sales tax;

4.2.2.3 Only one code will be assigned within a country irrespective of the 

application of such code;

4.2.2.4 This code will only be confirmed upon satisfactory verification that no other 

code is assigned to identify the applicable taxes, fees or charges;

4.2.2.5 This code will only be published in the Airline Coding Directory;

4.2.2.6 The code will be identified as “not to be used for taxes on air 

transportation”.

...

T2.1/P

7. FORM OF PAYMENT CODE

(mandatory)

To be entered in the “Form of Payment” box. If the ticket is being issued in 

exchange for another ticket, enter the form of payment indicated on the original 

ticket. Where no fare has been collected, an authorisation number or other 

pertinent data may be entered.

CASH—paid cash or by travellers cheque. (applicable to travel agents: in case of 

a ticket issued with a zero value, cash should be used as the acceptable form of 

payment) 

...

P2.2

Payment instruments. domestic usage only

....

Cards issued by BC Bank Card BC BSP Korea specific2

Cabal CL BSP Argentina, domestic card

Cards issued by Kookmin KB CN BSP Korea specific2

....

Card issued by Hyundai Card HD BSP Korea specific2

Reserved for future use KA BSP Korea specific2

Cards issued by Woori bank KA BSP Korea specific2
....

Cards issued by Nonghyubp NH BSP Korea specific2

....

Cards issued by HANA Hana SK BSP Korea specific2

....

Payment instruments, regional usage 

Cabal CL BSP Argentina, Uruguay, Paraguay and 

Brazil only

Filing Period: Effective Date:

11 May 2015 12 June 2015

11June 2015

RESOLUTION 743a

FORWARDING MISHANDLED BAGGAGE

(amending)

PSC (34 36)743a Expiry: Indefinite

Type: B

.....

B4.3

2. The forwarding carrier shall advise the airline and station to which the baggage 

has been addressed on the Expedite Baggage Tag, by teletype message, using 

the standard office function designator “LL”, or directly through the automated 

baggage tracing systems.

.....If more than one carrier...

The Member shall include an email address in the standard format, e.g. 

baggageprorates@ba.com, in the baggage tracing system. The Member shall 

also provide the email address to IATA who will keep a database of all generic 

baggage prorates emails on its extranet pages. The contact email address for 

IATA is baggageservices@iata.org.

.....

4.1.2 in case that Member should not be represented at such place, by the 

Member on whose flight the expedite baggage arrived at such airport.

There is no prorating on delivery expenses. Delivery costs from such airport to the 

passenger may only be recharged by the delivering carrier (not the delivering 

vendor) to the member responsible for the mishandling. if they are in excess of 

US$25 or its equivalent per delivery.

In the case of 4.1.2, the Member responsible for mishandling may be indicated in 

the box “Expense Of” on the expedite baggage tag.

When a Member delivers the baggage as handling agent for another Member 

(principal) any recharging of delivery costs by the handling agent to the principal 

shall not be governed by this resolution.

The amount recharged shall be supported by proof of the cost incurred, and by 

copy of the PIR, or in the case of 4.1.2, by the original or a copy of the expedite 

bag.

.....

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015

B4.3

RESOLUTION 754

PROFILES OF INTERLINE BAGGAGE CLAIMS AND PROOF OF FAULT FOR 

BAGGAGE PRORATES

(new)

PSC(36)754 Expiry: Indefinite

Type: B

RESOLVED that:

The Profiles of typical interline baggage claims and suggestions for supporting 

proof of the fault evidence are intended to assist baggage claims personnel in 

determining the cases when an interline baggage claim can result in 100% 

prorate, thus avoiding disputes and unnecessary correspondence between 

carriers. 

When it is not established which airline is responsible for the mishandling 

(meaning damage, delay, loss or pilferage), each Carrying Airline that participated 

in the carriage of the passenger shall share the claim settlement on the basis of 

the flown mileage between all ticketed points of each carrying airline (Resolution 

780 5.4.3).

In the following profiles, it is assumed that the last carrier is the airline that 

received the claim. However, any claim receiving airline will handle the claim 

according to Article 5.4.1 of Resolution 780.

Baggage profile 1 – Tag less baggage

Passenger travels: 

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Problem: 

Baggage is identified as tag less and/or there is an OHD (On-hand) and/or FWD 

(Forwarding advice message) from the airport of origin (Station 1).

Solution: Airline A is responsible for the mishandling. Airline B prorates Airline A 

100%.

Proof of the fault of mishandling: OHD and/or FWD from the airport of origin 

(Station 1).

Problem:

Baggage is identified as tag less and/or there is an OHD (On-hand) and/or FWD 

(Forwarding advice message) from the transfer airport (Station 2).
Solution: Each Carrying Airline that participated in the carriage of the passenger 

shall share the claim settlement on the basis of flown mileage between all ticketed 

points of each carrying airline as per Article 5.4.3 of Resolution 780, unless other 

proof of fault of the mishandling can be obtained.

Proof of the fault of mishandling: baggage tracking records - BRS (Baggage 

Reconciliation System) and/or BHS (Baggage Handling System).

Baggage profile 2 – Delayed delivery

Passenger travels: 

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Problem: Airline B never receives the baggage from Airline A.

Solution: The responsibility for baggage by the delivering carrier is relieved only 

when the baggage has been delivered to the receiving carrier.

Where a handling agent is involved, the handling agent acts on behalf of the 

delivering carrier until the point at which the baggage has been delivered to the 

receiving carrier, even if the receiving carrier is handled by the same handling 

agent.

Airline B prorates Airline A 100%.

Proof of the fault of mishandling: 

FWD from Airline A from the airport of origin (Station 1) and/or 

FWD from any other station apart Station 2 and/or

Expedite tag and/or

Old tag on the baggage which has not been removed and/or

PNR and/or check-in records and/or

Baggage tracking records – BRS and/or BHS and/or local tracking system record.

Baggage profile 3 – Baggage misrouted by originating Carrier

Passenger travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Problem: Airline A misroutes the baggage to a wrong destination than Station 2.

Solution: Airline B prorates Airline A 100%.

Proof of the fault of mishandling: 

OHD tag less and/or FWD from Airline A from the airport of origin (Station 1) 

and/or 

FWD from any other station apart Station 2 and/or

OHD tag less
Original tag with a wrong destination (in case the baggage got miss tagged) on it 

and/or

Expedite tag and/or

Old tag on the baggage which has not been removed and/or

PNR and/or check-in records and/or

Check-in error - wrong name tag on the baggage and/or

Baggage tracking records - BRS and/or BHS and/or local tracking system record.

Baggage profile 4 – Transfer within Minimum Connecting time (definition of 

MCT as per Resolution 765)

For the purpose of this Resolution, 

Passenger travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Problem: Airline A delivers the baggage within the MCT of the transfer airport 

(Station 2) but Airline B misleads it and the baggage doesn’t arrive to Station 3.

Solution: Airline B is 100% responsible for the mishandling. No prorate applicable.

Proof of the fault:

Baggage tracking records - BRS and/or BHS and/or Flight records.

It is the responsibility of the Local Minimum Connecting Time Group at respective 

airport to establish local MCTs as set in Resolution 765. MCTs (including 

exceptional bilateral MCT) are outlined in the IATA Standard Schedules 

Information Manual (SSIM).

Baggage profile 5 – Transfer not within Minimum Connecting time (MCT)

Passenger travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Problem: Airline A flight to the transfer airport (Station 2) is delayed and MCT is 

not kept. Consequently, Airline B misleads the baggage.

Airline A is responsible for the mishandling. Airline B prorates Airline A 100%.

Proof of the fault of mishandling: 

Baggage tracking records - BRS and/or BHS and/or Flight records.

It is the responsibility of the Local Minimum Connecting Time Group at respective 

airport to establish local MCTs as set in Resolution 765. MCTs (including 

exceptional bilateral MCT) are outlined in the IATA Standard Schedules 

Information Manual (SSIM).
Baggage profile 6 – Early departure (not respecting MCT)

Passenger travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Problem: Airline A delivers the baggage within the MCT of the transfer airport 

(Station 2) but Airline B does not respect the MCT and the flight leaves. 

Consequently, the baggage is misled and doesn’t arrive to Station 3.

Solution: Airline B is 100% responsible for the mishandling. No prorate applicable.

Proof of the fault:

Baggage tracking records - BRS and/or BHS and/or Flight records.

It is the responsibility of the Local Minimum Connecting Time Group at respective 

airport to establish local MCTs as set in Resolution 765. MCTs (including 

exceptional bilateral MCT) are outlined in the IATA Standard Schedules 

Information Manual (SSIM).

Baggage profile 7 – Delayed delivery by a third party at the transfer airport

Passenger travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Problem: Airline A flight arrives to the transfer airport (Station 2) on time (within 

the MCT), however the baggage is delivered to Airline B with a delay caused by a 

third party (not the handling agent) involved in the baggage delivery process at 

respective airport, e.g. local authority.

Solution: 

Each Carrying Airline that participated in the carriage of the passenger shall share 

the claim settlement on the basis of flown mileage between all ticketed points of 

each carrying airline as per Article 5.4.3 of Resolution 780, unless other proof of 

fault of the mishandling can be obtained.

Proof of the fault:

Baggage tracking records - BRS and/or BHS and/or Flight records.
Baggage profile 8 – Short tagging

Passenger travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Problem: Airline A issues the bag tag only to Station 2, however the final 

destination on passenger ticket is Station 3.

Solution: Airline A is responsible for the mishandling. Airline B prorates Airline A 

100%.

Proof of the fault of mishandling: 

Copy of the ticket and/or PNR and/or check-in records and/or

Original or copy of bag tag and/or baggage claim receipt and/or

FWD from Airline A at Station 2.

Baggage profile 9 – Through check-in on separate tickets

Passenger travels:

with Airline A from Station 1 to Station 2

and on a separate ticket with Airline B from Station 2 to Station 3

Problem: Airline A tags the baggage as far as Station 3. Baggage never arrives to 

Station 3.

Solution: Airline B prorates Airline A 100%. When originating carrier accepts 

through check-in on separate tickets, it will be considered as the proof of fault and 

will result in 100% prorate, unless a specific agreement between carriers exists.

Proof of the fault of mishandling: 

Copy of the ticket and/or PNR and/or check-in records and/or

Original or copy of bag tag and/or baggage claim receipt and/or

FWD from Airline A at Station 2.

Baggage profile 10 – Through check-in – no Interline agreement between 

Carriers

Passenger travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

There is no interline agreement between Airline A and Airline B.
Problem: Airline A tags the baggage as far as Station 3. Baggage never arrives to 

Station 3.

Solution: Airline B prorates Airline A 100%. When originating carrier accepts 

through check-in and no Interline agreement exists between the carrier, it will be 

considered as the proof of fault and will result in 100% prorate.

Proof of the fault of mishandling: 

Copy of the ticket and/or PNR and/or check-in records and/or

Original or copy of bag tag and/or baggage claim receipt and/or

FWD from Airline A at Station 2.

Baggage profile 11 – Passenger does not collect the baggage for Customs 

Clearance

Passenger travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Customs Clearance is required at the transfer airport.

Problem: At the final destination (Station 3) when making the claim, the passenger 

admits that he forgot to collect the bag for Customs Clearance at the transfer 

airport.

Solution: No prorate applicable.

Proof of fault:

Baggage tracing system record (PIR) and/or

PNR and/or check-in records and/or booking records and/or

FWD from Airline A at Station 2 and/or

OHD from Station 2 to advise that bag was not collected by passenger.

Baggage profile 12 – Passenger re-routed or involuntary re-routed

Passenger routed:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Passenger actually travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 4

with Airline C from Station 4 to Station 3
Problem: Airline B re-routes the passenger but not the baggage. Baggage is 

subsequently lost.

Solution: Airline C prorates Airline B 100%.

Proof of the fault of mishandling: 

Baggage tracing system record (PIR) and/or

PNR and/or check-in records and/or booking records and/or

FWD from Airline A at Station 2 and/or

OHD from Station 2 to advise that bag is not tagged to final destination due to 

flight changes and/or

Original or copy of bag tag and/or baggage claim receipt (with different 

information to PNR).

Baggage profile 13 – Damage or Pilferage

Passenger travels:

with Airline A from Station 1 to Station 2

with Airline B from Station 2 to Station 3

Problem: 

At the final destination (Station 3) passenger makes the claim for damage or 

pilferage

Solution:

Each Carrying Airline that participated in the carriage of the passenger shall share 

the claim settlement on the basis of flown mileage between all ticketed points of 

each carrying airline as per Article 5.4.3 of Resolution 780.

Proof of fault:

Both airlines handled the baggage and/or

Baggage tracking records - BRS and/or BHS and/or

PNR and/or check-in records and/or

Original or copy of bag tag and/or

Baggage tracing system record (PIR).

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015

P4

RESOLUTION 762

AIRLINE DESIGNATORS

(amending)

PSC(33 36)762 Expiry: Indefinite

Type: B

....

4. ASSIGNMENT CRITERIA

4.4 Computer Reservation Systems (CRS) suppliers with a requirement for 

participation in airline industry shared telecommunication facilities shall only be 

assigned two-character numeric-alpha or alpha-numeric designators using the 

figure “1” and letters “A-Z”. Such designators can be used in interline reservations 

messages. They shall not be used to publish and operate air services, nor shall 

they be used for the interline transmission of PTAs nor shall they be used for any 

other ticketing purpose, (except for the optional identification of the CRS 

controlling the PNR. This identification should be shown in the “Airline 

Data/Booking Reference/ PNR” box on the ticket). These codes shall not be 

duplicated (see paragraph 5).

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015

M10

RESOLUTION 765

CONNECTING TIME INTERVALS—PASSENGER AND CHECKED BAGGAGE

(amending)

PSC(30 36)765 Expiry: indefinite

Type: B

RESOLVED that:

...

6. Nothing in this Resolution shall preclude LMCTG Members from making 

bilateral agreements with other airlines or railways for shorter or longer intermodal 

MCT intervals in those cases where particular circumstances of their special 

arrangements/situations make this possible or necessary. Exceptional bilateral 

MCT exception filing practices are outlined in the IATA Standard Schedules 

Information Manual (SSIM). 

Each MCT coordinator is responsible for communicating and distributing those 

exceptional MCTs according to recognised industry practices. In case of 

disagreement between the two parties in respect of any such exceptional MCT 

values, the receiving Member's point of view shall govern, and be recognised by 

the industry as the exceptional MCT value. In those cases where MCT values 

and/or significant MCT data elements are not being altered, agreement by the 

receiving Member’s point of view is not needed. Currently, only carrier flight 

number ranges are considered non-significant MCT data elements.

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015

RESOLUTION 767

ASSIGNMENT OF AIRLINE ACCOUNTING CODES AND AIRLINE PREFIXES

(amending)

PSC(33 36)767 Expiry: indefinite

Type: B

....

1. USE OF AIRLINE ACCOUNTING CODES AND AIRLINE PREFIXES...

P15

...

1.6 In order to qualify for assignment of an airline accounting code or airline prefix, 

an enterprise must be fully licensed to perform commercial air transport services. 

Airline accounting codes and airline prefixes shall not be assigned on a 

provisional basis.

1.7 a new entrant which does not yet meet the definition of “airline” for the 

purposes of this Resolution may be granted a provisional airline accounting code 

assignment when written notification is received from the civil aviation authority of 

the state in which it is established advising that the enterprise is substantially 

meeting the state’s requirements for the issuance of a license to operate 

commercial air transport services.

1.8 such provisional assignment shall be valid for a non-renewable period of six

(6) months. Failure of the enterprise to meet the definition of “ airline” for the 

purposes of this Resolution within six (6) months of provisional assignment of the 

airline accounting code will result in the formal recall of the code.

1.9. such provisional assignment may only be used for the purposes of systems 

testing and may not be used within any distribution channel until the enterprise 

has received the license to perform commercial air transport services.

...

5. AIRLINE ACCOUNTING CODES AND AIRLINE PREFIXES NOT AVAILABLE 

FOR ASSIGNMENT

P16

5.1....

....

Code Assignee

719 International Air Transport Association

721 International Air Transport Association

726 International Air Transport Association

736 International Air Transport Association

748 International Air Transport Association
....

777 BSP – Tour Operators/Hotels/Courier Companies/Insuance 

Companies IATA – Default Insurance Program

792 BSP- Car Rentals IATA E& F

793 BSP – Ships HoverCraft International Air Transport 

Association

794 BSP-Bus Lines International Air Transport Association

799 BSP – Railways International Air Transport Association

...

952 BSP – IATA Remittance and Settlement Adjustments

International Air Transport Association

...

956 BSPlink agent International Air Transport Association

....

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015
B4.3

RESOLUTION 780

IATA INTERLINE TRAFFIC AGREEMENT - PASSENGER

(amending)

PSC (35 36)780 Expiry: Indefinite

Type: B

.....

Attachment ‘A’

.....

1.11 “CLAIM” is a paper or electronic written demand for compensation, prepared 

and/or acknowledged and signed by or on behalf of the passenger, and .In the 

case of baggage, containing an the claim shall contain an itemized list and value 

of goods for which compensation is being requested.

.....

4.1.5.2 in case that Member should not be represented at such place, by the 

Member on whose flight the expedite baggage arrived at such airport. 

4.1.6 

There is no prorating on delivery expenses. Delivery costs from such airport to the 

passenger may only be recharged by the delivering carrier (not the delivering 

vendor) to the member responsible for the mishandling. if they are in excess of 

US$25 or its equivalent per delivery.

In the case of 4.1.5.2...

.....

5.4.4 Full claim settlement (excluding the delivery costs as noted in 4.1.6) or its 

pro-rata share amounting to US$50 (or equivalent) or less shall not be recharged.

.....

5.4.6 Within sixty (60) days of the date of the claim settlement the claim receiving 

airline will send a request for payment to the other participating or responsible 

airline(s) at their headquarters central baggage claims office baggage prorate 

office, providing them with relevant settlement documents. The IATA currency 

exchange rate on the date of flight should be applied in the calculation of the 

amount to prorate.

When any type of marketing/commercial partner or code share agreement exists, 

the request for payment will be sent to the carrier whose airline designator 

appears in the carrier box of the ticketed flight coupon involved in the claim. The 

marketing carrier may recharge the operating carrier depending on their 

established agreements. If such notice is not given in time by the claim receiving 
carrier, acceptance of any claim payment will be at the discretion of the 

participating or responsible airline(s).

.....

5.4.8 Requests for prorate and provision of supporting documentation shall be 

made directly to the headquarters central baggage claims office baggage prorate 

office, not through the interline billing and settlement process, using the format 

shown on Appendix “C” “PRORATE NOTICE” (published separately) as a cover 

sheet for the following documents which are required to support any claim under 

this agreement including requests for 100%.

.....

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015
B4.3

RESOLUTION 780e

IATA INTERLINE TRAFFIC PARTICIPATION AGREEMENT - PASSENGER

(amending)

PSC (35 36)780e Expiry: Indefinite

Type: B

RESOLVED THAT,

.....

1.12 “CLAIM” is a paper or electronic written demand for compensation, prepared 

and/or acknowledged and signed by or on behalf of the passenger, and .In the 

case of baggage, containing an the claim shall contain an itemized list and value 

of goods for which compensation is being requested.

.....

4.1.5.2 in case that Member should not be represented at such place, by the 

Member on whose flight the expedite baggage arrived at such airport. 

4.1.6 

There is no prorating on delivery expenses. Delivery costs from such airport to the 

passenger may only be recharged by the delivering carrier (not the delivering 

vendor) to the member responsible for the mishandling. if they are in excess of 

US$25 or its equivalent per delivery.

In the case of 4.1.5.2...

.....

4.1.7 Each party hereto...

.....

5.4.4 Full claim settlement (excluding the delivery costs as noted in 4.1.6) or its 

pro-rata share amounting to US$50 (or equivalent) or less shall not be recharged.

5.4.54.....

5.4.65 Within sixty (60) days of the date of the claim settlement the claim 

receiving airline will send a request for payment to the other participating or 

responsible airline(s) at their headquarters central baggage claims office baggage 

prorate office, providing them with relevant settlement documents. The IATA 

currency exchange rate on the date of flight should be applied in the calculation of 

the amount to prorate.

When any type of marketing/commercial partner or code share agreement exists, 

the request for payment will be sent to the carrier whose airline designator 

appears in the carrier box of the ticketed flight coupon involved in the claim. The 

marketing carrier may recharge the operating carrier depending on their 

established agreements. If such notice is not given in time by the claim receiving 
carrier, acceptance of any claim payment will be at the discretion of the 

participating or responsible airline(s).

5.4.76 .....

5.4.87 Requests for prorate and provision of supporting documentation shall be 

made directly to the headquarters central baggage claims office baggage prorate 

office, not through the interline billing and settlement process, using the format 

shown on Appendix “C” “STANDARD PRORATE NOTICE” (published separately) 

as a cover sheet for the following documents which are required to support any 

claim under this agreement including requests for 100%.

Editor’s Note: Renumber subsequent paragraphs

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015
M2.3

RESOLUTION 783

PASSENGER AND DATA INTERCHANGE STANDARDS BOARD

(amending)

PSC(30 36)783 Expiry: Indefinite

Type: B

RESOLVED that:

....

2. FUNCTIONS OF THE BOARD 

Recognising that Members: 

use the United Nations/Electronic Data Interchange for Administration, Commerce 

and Transport (UN/EDIFACT) standards, and the United Nations Centre for Trade 

Facilitation and Electronic Business (UN/CEFACT) standards for the automated 

exchange of passenger services data between themselves and other parties; 

and/or 

use Electronic Data Interchange (EDI) techniques and eXtensible Markup 

Language (XML) specifications techniques for developing messages between 

themselves; and/or

use internet technology to exchange messages between themselves and other 

parties and desire to achieve maximum interoperability.

The main functions of the Board are:

2.1 to use the UN/EDIFACT standards (such as UN/EDIFACT Syntax Rules (ISO 

9735), UN/EDIFACT Message Design Guidelines, UNTDID), use the UN Trade 

Data Element Dictionary UNTDED (ISO 7372) and generally accepted internet 

technology standards to develop Passenger and Airport Data Interchange 

Standards (hereinafter referred to as the PADIS Standards) related to airline 

passenger travel and airport related passenger service activity such as 

Reservations, Ticketing, Pricing/ Fare Calculation, Revenue Accounting/Ticket 

Data, Customs/Immigrations, Departure Control, Weight and Balance, Baggage 

Services, Airport Handling Procedures and Airport/Airline Interface; 

2.2 to guide the maintenance of a Data Model that will serve as the single source 

of data definitions used to develop interoperable PADIS standards;

2. 23 to propose additions, changes and deletions to the PADIS Standards 

published in the Passenger and Airport Data Interchange Standards Manual 

(hereinafter referred to as the PADIS Manual); 
2.4 to manage the development and maintenance of a methodology and 

associated templates to be followed by working groups or other parties requesting 

new messages or message modifications;

2.35 to be guided by the following principles in developing and amending the 

PADIS Standards: 

2. 35.1 compatible with the UN/EDIFACT standards, 

2. 35.2 compatible with generally adopted internet technology standards such as 

the standards published by the IETF or the W3C,compatible with the 

UN/UNTDED standards, and other adopted industry standards, 

2. 35.3 comprehensive and practical, 

2. 35.4 generally acceptable to all users, 

2. 35.5 incorporate existing codes, formats and standards to the extent possible, 

2. 35.6 ensure that the PADIS Standards are not in conflict with existing industry 

standards and conform with established principles and procedures, 

2. 35.7 able to be the basis for future development of passenger processing and 

information exchange; 

2. 35.8 facilitate the interoperability with similar standards published by adjacent 

industries.

2.56 to liaise closely with other A4A and IATA Committees dealing with the 

development of passenger services standards.

.....

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015
P6

RESOLUTION 798a

HANDLING DISRUPTIVE/UNRULY PASSENGERS

(new)

PSC(36)798a Expiry: Indefinite

Type: B

RESOLVED that a method is adopted by Members for handling disruptive and unruly 

passengers in a manner which is consistent worldwide whilst being sensitive to issues of 

culture and custom within individual carriers.

1. Members shall create and implement a policy, actively involving all relevant 

departments which provides for consistent monitoring and handling of incidents by all 

staff at all times.

1.1 Members shall ensure the full endorsement and involvement of their Senior Executive 

Officer when implementing this policy within the airline.

1.2 Members shall ensure responsibility and coordination is agreed within their 

organization in advance. It is important that all relevant departments of the carrier 

recognize their ownership of the policy, for example:

Human Resources: for issues such as staff welfare, duty-time for court appearances;

Legal: for the decision on prosecution of offences and advice to staff;

Marketing/Commercial: for communication programs internally and externally;

Safety: for training and communication with flight crew and cabin crew

Security: to act as the single point of contact and for the interface with police authorities.

1.3 Members shall have a Single Point of Contact who takes responsibility for incidents 

and who reports directly to the Senior Executive Officer on these matters.

2. The Policy shall address the issues of:

Prevention,

Training,

Periodic re-training,

Handling problem passengers,

Categorizing of incidents,

Reporting of incidents,

Pilot in command's responsibility,

Prosecutions, 

Communication,

Procedures to be followed for: -

—boarding

—inflight

—underage passenger issues (e.g. alcohol service)

—situations involving alcohol/smoking

—physical/verbal assaults

—harassment

—dealing with authorities
2.1 Regular and consistent communication of the Policy, both internally and externally, 

shall be carried out to ensure that it is clear that the carrier will act to identify, defuse, 

respond and prevent incidents where possible.

3. Members shall develop and maintain a close relationship with the relevant national law 

enforcement and airport security authorities.

3.1 Members shall encourage States to prosecute unruly passengers.

4. Published separately, attachments to this Resolution are:-

Guidelines for policy creation,

Categorization of incidents,

Sample passenger warnings,

Sample incident reporting document,

Sample company policy.

For copies of the above-mentioned attachments, contact IATA Cabin Safety 

(cabin_safety@iata.org) or IATA Security and Facilitation (secfal@iata.org).

Filing Period: Effective Date:

11 May 2015 12 June 2015

11 June 2015
P8.5

RECOMMENDED PRACTICE 1701h

SECURITY CHECKPOINT ACCESS AND EGRESS

(amending)

PSC(33 36) 1701h

All the content of this document is intended to be used as guidance material, to be 

considered by airports when applicable, subject to local requirements:

1. INTRODUCTION

• The recommendations that appear on this document are intended to be a useful 

reference for airport terminal design and management of the passenger flow 

around security checkpoint.

• The information provided comes from airports where the mentioned bestpractices have been implemented successfully.

• This document is not intended to be part of any regulation or mandate 

• This document is a joint effort of ACI and IATA.

2. SCOPE

The main focus of this best- practice guidance will be for security checkpoint access 

and egress.

2.1 Security checkpoint access:

• Pre- screening preparation zone and queuing space

• Divest tables and zones

• Tray feeding systems

2.2 Security checkpoint egress:

• Composure tables and zones

• Egress seating area

• Tray recovering systems
3. GEOGRAPHICAL CONFIGURATION

3.1 Assumption

Default security checkpoint configuration:

• Configuration “2 X- RAYS to 1 WTMD” (Walk-Through Metal Detector)

• Centralized screening area

• The standard “2 X- RAYS to 1 WTMD” security checkpoint configuration has 

been selected as best practice configuration is one of the most common 

deployments as it is widely used in average centralized airport screening 

areas all around the world, providing great efficiency and flexibility. However 

there are many passenger screening combinations that an airport or a 

regulator may require. It should be noted that a number of regulators are 

currently considering alternative passenger screening technologies such as 

passenger security scanners.

• Airports that have implemented other Security checkpoint configurations (i.e. 

gate screening) may use the following information as an overall reference 

benchmark, depending on their local arrangements.

• It is important to mention that, for airports developing the one stop security 

concept for connecting passengers, the centralized security checkpoint area 

is the most efficient way to implement that concept.

3.2 Diagram

The following exhibits provide a typical layout of a screening lane pair, with what can be 

considered the minimum recommended dimensions for each area and function.
Secretary Note: Replace Old Diagram above with the one below.

3.3 Dimensions

Following the previous schema, the ‘best practice‘ participant airports have the following 

dimensions – in centimeters (cm):
Secretary Note: Replace old table above with the one below.

Security checkpoint dimensions Recommended Minimum

A Pre-screening and queuing 700

B In feed lengths (Divest) 400

C Out feed lengths (Composure) 600

D Egress Seating 400

E Space between lanes for passenger movement 450

F Lane width 200

* Note the above recommended minimum measurements do not include X-ray machine measurements. These 

measurements should be obtained from the manufacturer and incorporated into calculations.

3.4 Alternative Passenger Screening Configurations

Below are simply a few examples to illustrate that the recommended minimum space between 

lanes of 4.5m will not be sufficient if more than one walk-through metal detector or security 

scanners are to be installed.

It is recommended that all commissioning airports, airlines and government authorities select 

experienced professionals to assist them.
4. ACCESS

4.1 Pre-Screening and Queuing

• Sufficient space should be allocated for passenger preparation so that airport security 

managers have the space required to install signage, bins and other infrastructure to support 

passengers preparation for the screening process. 

• It is recommended to have a centralized queueing system, where one queue feeds a number 

of lanes and passengers are screened on a first come first screened basis. Airports with 

more than 6 screening lanes may seek to implement two single queues serving multiple 

screening lanes provided that physical space permits two queues.

4.1.1 2D Bar code scanning to provide access

2D bar code scanning is recommended to be conducted before entering the queue to determine 

passenger eligibility to access restricted area and/or segregated line.

4.1.2 Information on screening procedures

Information point, containing:

• Poster on regulation,

• Video explaining the process,

• Information flyers available for passengers,

• 1 officer supervising the information procedures.

4.1.3 Segregation Segmentation of lines

Segregation of lines in at least two groups 

Passenger segmentation describes a process which assigns search lanes to different 

passenger groups based on different processing needs, processing throughput, or queuing 

standards. Typical segmentation policies include at least two groups:

• Premium passengers / Frequent travelers

• Occasional travelers / Families with children

4.1.4 Queuing arrangements

• Provide tensa-barrier flexible queuing system

• 1 supervisor / queuing manager on duty during peak times

4.1.5 Staff allocated to help passenger in pre-screening

• Customer Service ambassador to help and advise passengers

4.2 Divest Tables and Zones

4.2.1 Rectangular roller beds aligned with X-RAY feeding

• Roller beds could accommodate at least 3 passengers

4.2.2 Roller beds overlapped with tensa-barrier queuing

• Enable passenger divesting while moving along the queue
4.2.3 Staff allocated to control divesting and X-RAY feeding

• 1 loader per X-RAY in-feed.

4.3 Tray feeding

Provide a mechanical system, integrated in the checkpoint infrastructure, for trays to be rolled 

back efficiently.

5 EGRESS

5.1 Composure Tables and Zones

5.1.1 Rectangular roller beds aligned with X-RAY out belt

• Provide roller beds and tables aligned – to accommodate at least 5 Passengers 

• Secondary search table at 90° not to interfere with the flow 

5.1.2 Staff allocated to assist passengers

• 2 Searchers – opposite sex – right behind the WTMD

• Private booths available for secondary search 

5.2 Egress seating area

• Tables for passengers to repack their hand luggage

• Seating possibilities to accommodate at least 2 passengers per X-RAY

5.3 Tray recovery

Provide a mechanical system, integrated in the checkpoint infrastructure, for trays to be rolled 

back efficiently.

6 OTHER CONSIDERATIONS

6.1 Ambience

It is very important to provide a good ambience, focusing at least on the following aspects:

• Cleanliness

• Light

• Temperature

6.2 Recommendations When Shoe inspection is Required

• Plastic slippers

• Soft floor covering
6. 3 Courtesy and Friendliness of Staff

• Customer Service Training

• Language training

• Basic greetings: ”Good morning.. have a good flight”

6.4 Information on Processing Time

• It is very useful to inform the passenger about a standard waiting time, to gain 

predictability and reduce stress/hassle

7 MEASUREMENT OF PASSENGER PERCEPTION

It is highly recommended to measure the passenger perception of the security screening 

process, covering at least these two aspects:

• Courtesy of security staff and perceived time at security

8 MEASUREMENT OF QUEUING TIME PERFORMANCE

It is highly recommended to have a performance indicator measurement process, to measure at 

least security checkpoint waiting tinmes and throughput, for security management to be able to 

allocate staff efficiently, according to the flow distribution. 

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015

P8.4

RECOMMENDED PRACTICE 1706c

COMMON USE SELF SERVICE (CUSS)

(amending)

PSC(35 36)1706c

.....

5.3 Accessibility

Passengers might not be able to use shared self-service devices at airports due to a 

disability. Consequently, legislation on accessibility should be adhered to when 

applicable at the site where the shared self-service devices are deployed and 

maintained.

.....

REFERENCES

Recommended Practices

IATA A4A

1797 -- Common Use Terminal Equipment (CUTE) systems

 Common Use Passenger Processing Systems (CUPPS)

.....

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015

RECOMMENDED PRACTICE 1707a

DATA FIELD DICTIONARY FOR DCS PASSENGER MESSAGES

(amending)

PSC(35 36)1707a

.....

B7.2/P, B7.7/P

Data Field Name Example Format/Reference 

.....

baggage tag ID: Alpha-Numeric KL123456 mm(a)f[6]

.....

blocking seat, reason CBBG see code-word or free text 

boarding pass delivery method 

boarding pass format preference

boarding point 

CTCM

PDF

MSP 

aaaa

aaa

see airport code 

.....

.....

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015
RECOMMENDED PRACTICE 1707b

DATA ELEMENT DIRECTORY FOR DCS PASSENGER MESSAGES

(amending)

PSC(35 36)1707b

B7.7/P

.....

3.20 .N/ BAGGAGE TAG DETAILS ELEMENT

This element is used to record consecutive bag tag numbers. When a Name

Element has multiple bags with nonconsecutive bag tag numbers, use multiple

.N/ elements. As bilaterally agreed, the information will be provided using either

the numeric or alphanumeric formats of the baggage tag as described in IATA 

Resolution 740.

3.20.1 Numeric version

Construction Example Data Field Name

3.20.1.1 element ID .N/ element ID

3.20.1.2 baggage tag number 0074123456 baggage tag ID:

licence plate number

3.20.1.3 number of consecutive tags 005 number/three

3.20.1.4 oblique (/) / information separator

3.20.1.5 final destination to which bag(s) are checked SFO airport code

Example:

.N/0074123456005/SFO

3.20.2 Alpha Numeric version

Construction Example Data Field Name

3.20.2.1 element ID .N/ element ID

3.20.2.2 baggage tag ID number

KL123456

baggage tag ID: 

Alpha/Numeric

3.20.2.3 oblique / information separator

3.20.2.4 number of consecutive tags 5 number of bags

3.20.2.5 oblique / information separator

3.20.2.6 final destination to which bag(s) are checked SFO airport code

Example:

.N/KL123456/5/SFO

...... 
B7.5/P

.....

4.12 A Party/Group Identification (See RP 1707, 2.9.2) is assigned uniquely for one 

DCS message, for one use group of passengers on the flight. The Identification

party/group identifier for a “set” of names can be different must be the same on 

each subsequent list (such as first D2, then M2, then A2). The Identification's 

purpose is to keep names associated for their appearance on just one message. 

Furthermore, if a “set of names” appears more than once on one message, each 

appearance of the “set of names” is to have a unique Party/Group Identification

must use the party/group identifier associated with the group. Example: when a 

“set of names” appears on one ADL in the section for Deletes and then again for 

Adds, such as:

ADL

....

DEL

1JONES/ARTHUR-D3 .L/382U22

1MILLER/JON-D3

1SMITH/ANN-D3

.....

ADD

1MILLER/JON-ED2 .L/382U22

1SMITH/ANN-ED2

....

This example shows clearly that a PNR of three (D3) are associated for the 

Delete, and that a PNR of two (ED2) remains for the Add.

.....

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015
RECOMMENDED PRACTICE 1708

PASSENGER NAME LIST (PNL) AND ADDITIONS AND DELETIONS LIST (ADL)

(amending)

PSC(35 36)1708

B7.5/P

.....

2.6.4.2 Example of a PNR confirmed from waitlist:

 The PNL showed Mr. Mackie waitlisted in F-class, and confirmed in Y-class:

-MSP12F

1MACKIE/IANMR-D2 .L/CDE1RY/BA .WL/PD1

....

-MSP207Y

1MACKIE/IANMR-D2 .L/CDE1RY/BA .R/RQST HK1 17D

....

Subsequently in RES, Mr. Mackie is confirmed into F-class from his Y-class waitlist. His 

PNR has of class and status, so the ADL shows....

....

-MSP13F

ADD

1MACKIE/IANMR .L/CDE1RY/BA .R/RQST HK1 2A 

-MSP206Y

DEL

1MACKIE/IANMR .L/CDE1RY/BA

2.6.4.3 Example of a cancellation in RES of one/some (but not all) of the passengers, in a PNR:

The PNL showed the PNR for the Gajve family as:

....

-IAD15F

....

3GAJVE/DEVENDRAMR/YOGIMRS/CLARAMS-M6 .L/HEX123

.R/INFT HK1 07DEC07-1GAJVE/CLARAMS

....

Mrs. Gajve cancels her booking in this PNR, so the ADL shows:

....

-IAD14F

DEL

3GAJVE/DEVENDRAMR/YOGIMRS/CLARAMS-M6 .L/HEX123

ADD

2GAJVE/DEVENDRAMR/CLARAMS-M5 .L/HEX123

.R/INFT HK1 07DEC07-1GAJVE/CLARAMS

2.6.4.4 Example of a cancellation in RES of one/some (but not all) of the passengers in a PNR 

when the PNR has multiple surnames.

The PNL showed the PNR for Smith, Wong and Jones as:

....

-JMS12F

....

1JONES/ROBERTMR-R3 .L/T5G246

1SMITH/ANNAMRS-R3

....

1WONG/SANDRAMS-R3

....

-JMS 23Y

....
Later, after the PNL has been sent, SMITH cancels her booking in RES. An ADL is sent 

showing:

Note: The Party/Group Identification is different on the DEL (A3) and the ADD (B2), 

allowing the proper re-association in DCS of the new set of active names in the PNR.

DEL

1JONES/ROBERTMR-R3 .L/T5G246

1SMITH/ANNAMRS-R3

1WONG/SANDRAMS-R3

ADD

1JONES/ROBERTMR-R2 .L/T5G246

1WONG/SANDRAMS-R2

...

2.12.6.1(d) Examples of Seat Information

.....

Specific seat requests with change of gauge flight 2YU/MIKEMR/JUNMRS .R/NSST HN2 DELHKG

.RN/7A7B .R/NSST HK2 HKGNRT

.RN/20/A30/A

..... 

B7.1/P

.....

2.12.6.4 Remarks Element for Passenger IROPS Contact Information

2.12.6.4(a) The Remarks Element for passenger IROPS contact mobile phone information uses the IATA 

AIRIMP standard code for passenger provided contact: CTCM.

2.12.6.4(b) Construction rules

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

SSR code for psgr provided contact CTCM SSR/OSI code

space –> information 

separator

phone number (mobile phone) 12185251234 n

(includes country, area, and local number)

oblique (if preferred language follows) / information 

separator

(optional) preferred language EN aa

passenger ID -1ODOM/TOM passenger ID

Examples:

1GALLERY/ROGERMR

.R/CTCM 15074261812

2CUSACK/GREGG/JENNIFER

.R/CTCM 31206490123-1CUSACK/GREGG

2.12.6.4(a) The Remarks Element for passenger IROPS email information uses the IATA AIRIMP standard

code for passenger provided contact: CTCE.
2.12.6.4(b) Construction rules

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

SSR code for psgr provided contact CTCE SSR/OSI code

space –> information separator

e-mail address HOD.MAR//MSN.COM free flow text

2 obliques are used for the change symbol (@)

2 periods are used for an underscore (_)

1 period and 1 oblique are used for a dash (-)

oblique (if preferred language follows) / information separator

(optional) preferred language NL aa

passenger ID -1HOD/MAR passenger ID

Examples:

1RIVERA/JAMES

.R/CTCE JAMES1.RIVERA//GMAIL.COM

2KLEIN/DAVID/ANNE

.R/CTCE DAVID.VAN..KLEIN//YAHOO.COM-1KLEIN/DAVID

.....

B7.2/P

2.12.6.14 Remarks Element for Automated Check-in 

2.12.6.14(a) The Remarks Element for Automated Check-in uses the IATA AIRIMP standard code for 

automated check-in to receive the boarding pass information via email or mobile phone number. 

2.12.6.14(b) Construction rules

Field Example Data Field Name 

(see RP 1707a/b) 

element ID .R/ element ID 

SSR code ACKI SSR/OSI code

space –> information separator

boarding pass

delivery method CTCM aaaa

oblique / information separator 

boarding pass format

preference MBP aaa 

passenger ID -SATO/ALBANMR passenger ID 

Examples: 

1JACOBS/RICKMR 

.R/ACKI CTCM/MBP 

2KELLOGG/TOM/AMY 

.R/ACKI CTCE/PDF-1KELLOGG/TOM

B7.2/P, B7.3/P

2.12.7 Table of SSR Codes 

The following SSR codes from the IATA AIRIMP are used in DCS messages in .R/ Remarks Elements. They are 

shown in this table in alphabetical order by code.

SSR Code See Note Number Description 

.....

ACKI

...

INAD

.....

 

 Automated Check-in

 Inadmissable Passenger
.....

3.1.1 PNL Message Example (Part 1)

......

-AGP80Y-PAD05 

1ALLEN/SANDRAMSMISS .R/CKIN HK1 NURSE ESCORT MR BRYAN 

.RN/STRETCHER ADVISE NURSE ALLEN OF OXYGEN LOCATION 

3BALMAN/PETERMR/MARYMRS/MARTINMR 

3BROWN/ALANMR/BRENDAMRS/CLAUDIAMISS 

1BRYAN/GARYMR .L/342315 .R/STCR HK1 BROKEN 

.RN/HIP IN PLASTER ESCORTED BY MISS ALLEN 

.RN/NURSE 

3FERRARI/GEORGEMR/VICTORIAMRS/LINDAMISS-D4 

1GEORGE/LEAH .L/C5AR63

.R/ACKI CTCE/PDF

.R/CTCE LEAH.GEORGE//GMAIL.COM

ENDPART1

......

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015
RECOMMENDED PRACTICE 1719

PASSENGER FINAL SALES MESSAGE (PFS)

(amending)

PSC(35 36)1719

B7.4/P

.....

2.10 AUTOMATED PNR ADDRESS ELEMENT

......

2.10.2 Automated PNR Addresses are applicable only for passenger names that were 

shown on the PNL/ADL. They are not applicable to categories GOSHO, 

GOSHN, NOREC, and OFFLN.

......

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015

RECOMMENDED PRACTICE 1719b

PASSENGER RECONCILE LIST (PRL)

(amending)

PSC(35 36)1719b

B7.7/P

.....

1.4 COMPONENTS

The PRL contains the following components:

.....

Baggage Pooling Element

Baggage Tag Details Element

.....

.....

.BG/001

.N/0074123456003/SFO

.N/NW234567/1/RST

......

2.15 BAGGAGE TAG DETAILS ELEMENT

2.15.1 This element is conditional.

2.15.2 It is used when baggage tag number(s) exist in the DCS for the passenger.

2.15.3 For pooled baggage it appears only with the Name Element for the “head of pooled baggage”.

2.15.4 For construction rules, see RP 1707b, Baggage Tag Details Element. This element uses element ID “.N/”.

2.15.5 Examples:

.N/NW234567/1/RST

.N/0012234567001/RST

......

Section 3—Examples

3.1 EXAMPLE OF A PRL; PART ONE OF A MULTI-PART PRL

. . .

1BROWN/RICHARDF

.L/3QH6G2

.W/K/1/14

.N/AF252062/1/DTW .N/0057252062001/DTW

.R/DOCS HK1/P/USA/208765112/USA/17FEB47/M/17JUL13/BROWN/RICHARDFOSS

.R/DOCA HK1/R/USA

.R/FQTV NW061570401 .R/TKNE HK1 0742465129100/1

.R/SEAT HK1 04H

1FRANKLIN/KAREN

.L/37NQ6Z

.W/K/1/18

.N/AF176486/1/MBS .N/0057176486001/MBS

.I/AF5101C24ZRH

.O/NW5822Y24MBS

.R/DOCS HK1/P/CAN/JU177101/CAN/15OCT66/F/15DEC10/FRANKLIN/KARENLYN

.R/DOCA HK1/R/CAN

.R/DOCA HK1/D//2775 NORTH WASKEICH/MIDLAND/MI/48642

.R/TKNE HK1 0127639293068/1

.R/SEAT HK1 05B

1RAMASAMUDRA/MANJUNATHA

.L/7QP87X
.W/K/2/39

.N/AF290669/1/DFW .N/0057290669001/DFW

.N/AF290682/1/DFW .N/0057290682001/DFW

.I/AF191J24BLR

.O/NW695W24DFW

.R/DOCS HK1/P/USA/133707400/USA/20JUL64/M/26MAR11/RAMASAMUDRA/MANJU

.RN/NATHA

.R/DOCA HK1/R/USA

.R/TKNE HK1 0062177448959/2

.R/SEAT HK1 02J

 ......

-DTW265Y

1BOOT/RICHARDJ

.L/NQUF8O

.W/K/1/20

.N/AF214975/1/NRT .N/0057214975001/NRT

.O/NW347Y24DTWSFO15551810

.O2/NW015Y24SFONRT19202210/1HK

.R/DOCS HK1/P/GBR/706013638/GBR/12APR74/M/13APR16/BOOT/RICHARDJOHN

.R/DOCO HK1//V/011905166

.R/DOCA HK1/R/USA

.R/DOCA HK1/D/USA/471 38TH STREET AVE APT C/SANTA CRUZ/CALIFORNIA

.R/FQTV NW100203546936 .R/TKNE HK1 0122134872230/1

.R/SEAT HK1 18C

.R/ASVC HI1 H/S23/SEAT/CHARGEABLE SEAT/A/1/251234567890C1

1FACON/ARNAUDMR

.L/OPP2DH

.W/K/2/41

.N/AF240630/2/DTW .N/0057240630002/DTW

.R/DOCS HK1/P/FRA/00PF15887/FRA/21JAN75/M/22MAR11/FACON/ARNAUD

.R/DOCA HK1/R/FRA

.R/DOCA HK1/D//MARIOTT 123 AIRPORT/DETROIT

.R/FQTV NW518101113 .R/TKNE HK1 0575225640011/1

.R/SEAT HK1 11A

ENDPART1

=

NNNN

...

3.3 MULTI-PART PRL SORTED BY FARE CLASS (Part 1 and 2)

. . .

1ASSAF/CHARBELMR

.L/3HYQVM

.W/K/1/17

.N/ME622996/1/DTW .N/4076622996001/DTW 

.I/AZ302Y04MXP

.R/DOCS HK1/P/LBN/2091689/LBN/25FEB79/M/24JUL07/ASSAF/CHARBEL

.R/DOCO HK1//V/20053626370002

.R/DOCA HK1/R/USA

.R/DOCA HK1/D//1135 NIELSEN CT/ANN ARBOR/MICHIGAN/MI48105

.R/FQTV NW506965001/1 .R/TKNE HK1 0122132396518/2

.R/SEAT HK1 01C

1ASSELIN/BRUNO

.L/L3584R

.W/K/2/41

.N/AF687130/1/DTW .N/0057687130001/DTW

.N/AF687404/1/DTW .N/0057687404001/DTW

.R/DOCS HK1/P/FRA/03XH03261/FRA/13AUG62/M/23FEB13/1ASSELIN/BRUNO

.R/DOCO HK1/V/20061655670001

.R/DOCA HK1/R/USA

.R/DOCA HK1/D//5835 SUTTERS LANE/BLOOMFIELDS HILLS/MI/48301
.R/FQTV AF1001226795/2 .R/TKNE HK1 0127768914455/1

.R/SEAT HK1 05G

1GRANDATI/FREDERIC

.L/4682Z6

.W/K/1/22

.N/AF692326/1/MSP .N/0057692326001/MSP 

.O/NW1101R04MSP

.R/DOCS HK1/P/FRA/05TP81396/FRA/27AUG71/M/14APR10/GRANDATI/FREDERIC

.R/DOCA HK1/R/FRA

.R/DOCA HK1/D/USA/HOTEL HAMPTON INN/SHOREWIEW/MINESOTA

.R/FQTV AF1485175995/1 .R/TKNE HK1 0575201385421/1

.R/SEAT HK1 02G

1HALLMARK/ADRIAN

.L/NC9Z2Y

.W/K/1/7

.N/AF672618/1/DTW .N/0057672618001/DTW

.I/AF1743Y04GVA

.R/DOCS HK1/P/GBR/040438407/GBR/07JUL62/M/18SEP12/HALLMARK/ADRIANMIC

.RN/HAEL

.R/DOCO HK1/V/2O052852030O01

.R/DOCA HK1/R/USA

.R/DOCA HK1/D//1052 CHESTER STREET/BIRMINGHAM/MI/48009

.R/FQTV NW100803512040/1 .R/TKNE HK1 0122134383802/2

.R/SEAT HK1 03H

. . .

-DTW004B

1ARYANI/NOVITA

.L/3YEGE6

.W/K/1/21

.N/AF693604/1/DTW .N/0057693604001/DTW

.R/DOCS HK1/P/IDN/K281224/IDN/24NOV79/F/13SEP07/1ARYANI/NOVITA

.R/DOCS HK1/A/USA/A098845540/IDN/24NOV79/F

.R/DOCA HK1/R/USA

.R/FQTV NW853640491/1 .R/TKNE HK1 0121308314611/4

.R/SEAT HK1 23A

. . .

PRL

NW0067/04JUL AMS PART2

-DTW004B

1SCARABELLI/TIZIA

.L/775YIY

.W/K/2/40

.N/XH272584/2/DTW .N/0074272584002/DTW

.I/AF5551Y04VRN

.R/DOCS HK1/P/ITA/316781U/ITA/11AUG63/M/11JAN09/SCARABELLI/TIZIA

.R/DOCS HK1/C/USA/055135584/ITA/11AUG63/M/13JAN13

.R/DOCA HK1/R/USA

.R/FQTV NW523982292

.R/SEAT HK1 41H

1SUPANWATTANACHAI/SAVITREE

.L/NGCVW9

.W/K/2/24

.N/AF684855/1/DTW .N/0057684855001/DTW

.N/AF685318/1/DTW .N/0057685318001/DTW 

.O/NW3228V04TOL

.R/DOCS HK1/P/THA/N533945/THA/19APR81/F/23FEB09/1SUPANWATTANACHAI/SA

.RN/VITREE

.R/DOCA HK1/R/THA

.R/DOCA HK1/D//210 0 S GROVE STREET/BOWLING GREEN/OH/43402

.R/SEAT HK1 21C

. . .
Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015
RECOMMENDE PRACTICE 1719c

ELECTRONIC TICKET LIST (ETL)

(amending)

PSC(30 36)1719c

B7.6/P

.....

1.4 COMPONENTS

The ETL contains the following components:

Address Element HDQRMNW

Communications Reference Element .AMSKMKL 131313

Message Identifier Element ETL

Flight Element NW0055/13MAR AMS PART1

Seat Configuration Element CFG/F22C33Y222 CFG/22F33C222Y

Actual Time of Departure Element ATD/1427

Totals By Destination Element -MSP010C

Name Element 1VERVAAT/JILLMRS

Automated PNR Address Element .L/ABC123/NW

Marketing Flight Information Element .M/CX3322F22HKGNRT1230HK

Remarks Element .R/TKNE HK1 0188765434567/2

Remarks Continuation Element .RN/CO TRAVEL PERMITTED

Pieces/Weight Data Element .W/P/5

Baggage Pooling Element .BG/003

Baggage Tag Details Element .N/0074123456003/SFO

Header for Not Boarded Passengers NOT BOARDED

End Element ENDPART1

.....

B7.7/P

2.14 BAGGAGE TAG DETAILS ELEMENT

2.14.1 This element is conditional.

2.14.2 It is used when baggage tag number(s) exist in the DCS for the passenger.

2.14.3 For pooled baggage it appears only with the Name Element for the “head of pooled baggage”.

2.14.4 For construction rules, see RP 1707b, Baggage Tag Details Element.

2.14.5 Examples:

.N/0074123456003/SFO

.N/NW234567/1/RST

......

Filing Period: Effective Date:

11 June 2015 12 June 2015

11June 2015

RECOMMENDED PRACTICE 1719d

TICKETLESS PRODUCT LIST (TPL)

(amending)

PSC(32 36)1719d

B7.6/P

.....

1.4 COMPONENTS

The TPL contains the following components:

Address Element HDQRMQI

Communications Reference Element .CPHKMQI 131313

Message Identifier Element TPL

Flight Element QI0055/13MAR CPH PART1

Seat Configuration Element CFG/F22C33Y222 CFG/22F33C222Y

Actual Time of Departure Element ATD/1427

Totals By Destination Element -CPH010C

Name Element 1BASSET/AMYMRS

Automated PNR Address Element .L/ABC123/QI

Remarks Element .R/ETLP HK1 188765AN4567

Remarks Continuation Element .RN/CO TRAVEL PERMITTED

Pieces/Weight Data Element .W/P/5

Baggage Pooling Element .BG/003

Baggage Tag Details Element .N/0046123456003/SFO

End Element ENDPART1

.....

B7.7/P

2.13 BAGGAGE TAG DETAILS ELEMENT

2.13.1 This element is conditional.

2.13.2 It is used when baggage tag number(s) exist in the DCS for the passenger.

2.13.3 For pooled baggage it appears only with the Name Element for the “head of pooled baggage”.

2.13.4 For construction rules, see RP 1707b, Baggage Tag Details Element.

2.13.5 Examples:

.N/0074123456003/SFO

.N/NW234567/1/RST

.....

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015

RECOMMENDED PRACTICE 1719e

ADDITIONAL SERVICE LIST (ASL)

(amending)

PSC(34 36)1719d

B7.6/P

.....

1.4 COMPONENTS

The ASL contains the following components:

Address Element HDQRMDL

Communications Reference Element .AMSKMKL 131313

Message Identifier Element ASL

Flight Element DL0055/13MAR AMS PART1

Seat Configuration Element CFG/F22C33Y222 CFG/22F33C222Y

Actual Time of Departure Element ATD/1427

Totals By Destination Element -MSP010C

Name Element 1KLINE/GREGG

Automated PNR Address Element .L/ABC123/AF

Marketing Flight Information Element .M/CX3322F22HKGNRT1230HK

Remarks Element TKNE (conditional) .R/TKNE HK1 0188765434567/2

Remarks Element ASVC .R/ASVC HI1 H/S23/SEAT/CHARGEABLE SEAT/A/

Remarks Continuation Element .RN/1251234567890C1

End Element ENDPART1

.....

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015

RECOMMENDED PRACTICE 1720a/A4A 20.04

STANDARD THIRTEEN-DIGIT NUMBERING SYSTEM FOR TRAFFIC DOCUMENTS

(amending)

PSC(33 36)1720a

RECOMMENDED that:

P3.2

....

9. DOCUMENT NUMBER RECYCLING

The provisions of this paragraph apply only in respect of document number allocation 

within the IATA BSP.

In order to efficiently recycle standard traffic document numbers distributed by IATA for 

use within the BSPs the following procedure will apply:-

1. From the date of allocation from IATA, system providers and their agents will have 

twelve months to sub-allocate ranges and report sales, respectively; 

2 Upon expiry of the twelve months period IATA will systematically retrieve all the 

unreported ranges

3 Once all the numbers for a specific form code have been retrieved IATA will invoke a 

latency period of 24 months.

4 Upon expiry of the latency period the number ranges will be released for recycling, 

effectively introducing a standard 3 year form code recycling process. 
P3

Attachment ‘A’ – Effective July 2, 2015

....

Stock Provider 

Party

Type of Form

No. of 

Coupons

IATA 

Resolution / 

Recommended 

Practice

A4A

Resolution

Airline 

Code

1 2 3

Form Code

4 5 6

Serial Number

7 8 9 10 11 

12 13

Number 

of 

Digits in

Serial 

Number

Method of

Check Digit 

Calculation

(see below)

...

Agency BSP 1,2 Virtual Muti 

Purpose 

Document 

(VMPD) OffPremise 

Electronic 

Miscellaneous 

Document 

(OPEMD)

Paperless

-

725g _ - - - 180 - - - - - - - - 7 2 3

1 Computer generated ticket serial number. All other Passenger Traffic Documents have a preprinted ticket serial number 2 Standard neutral ticket. Airline name and code are not preprinted

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015

Commercial / 

Government1

Airline

Automated 

Ticket/Boarding Pass 

(ATB) & Electronic 

Ticket (A4A Only)

Electronic 

Miscellaneous 

Document

Coupon-byCoupon

- - - - -

- - -

725f

20.12

20.51

20.60

20.63

- - - 1 8 3 - - - - - - - - - 7 3

CATO

Airline

Automated 

Ticket/Boarding Pass

(ATB) & Electronic 

Ticket

Electronic 

Miscellaneous 

Document

Coupon-byCoupon

- - - - -

- - -

725f

20.54

20.61

20.63

- - - 1 8 7 - - - - - - - - - 7 3

Airline

Airline

Write Your Own Ticket

Electronic 

Miscellaneous 

Document

- - - - - - - -

725f

- - -

20.63

- - - 4 0 8 - - - - - - - - - 7 1

3

Airline

Airline

Customer Self Ticket

Electronic 

Miscellaneous 

Document

- - - - - - - -

725f

- - -

20.63

- - - 4 0 9 - - - - - - - - - 7 1

3

Agency (US ASP)

Airline

Miscellaneous Charges 

Order

Electronic 

Miscellaneous 

Document

1 coupon 

- - - - -

- - -

725f

20.96

20.63

- - - 8 0 1 - - - - - - - - - 7 1

3

Agency (US ASP)

Airline

Miscellaneous Charges 

Order

Electronic 

Miscellaneous 

Document

1 coupon 

- - - - -

- - -

725f

20.96

20.63

- - - 8 0 3 - - - - - - - - - 7 1

3
RECOMMENDED PRACTICE 1743d

BAGGAGE THEFT, PILFERAGE AND FRAUDULENT CLAIM PREVENTION

(amending)

PSC(23 36)1743d

RECOMMENDED that:

P4.1

....

7 FRAUDULENT CLAIM PREVENTION

7.1 Maintain a close working relation between claim and security personnel

7.2 Analyze all claims for signs that fraudulent claims may be coming from a certain area.

7.3 Take full advantage of co-operative schemes, by which data on baggage claims is compiled 

and filed by computer, and is available to all participating airlines.

Members are recommended to submit all baggage claims (Lost/Delayed, Damaged, Pilfered) 

into a Baggage Fraud Detection System(s) (BFDS) to provide fraud detection and prevention 

analysis services.

PURPOSE

BFDS exists to analyze baggage claims for the purpose of detecting indicators of fraudulent 

or duplicated baggage claims and reducing the possibility of airlines being exposed to 

fraudulent claims. Users would utilize this information as a part of their standard baggage 

claim evaluation process.

CRITERIA

BFDS should have the following criteria:

When data is input should inform users in real-time of indicators of fraudulent or duplicated 

baggage claims.

Should allow for each airline to configure data retention and configure data sharing policies 

to comply with applicable passenger privacy laws on data processing, retention and sharing.

Should allow for communication between airlines without additional messaging costs.

If multiple BFDS exist, then the systems should work together to maximize the value of fraud 

detection to the industry.
MEMBER RESPONSIBILITY

Members are recommended to enter claims data into the BFDS by either: 

a. Manually entering the data into the BFDS; 

b. Automatically integrating from a claims management system through web 

 services;

c. Automatically integrating from a baggage tracing or management solution 

 through web services.

Where law permits, members are encouraged to submit historic fraudulent baggage claims 

data into the BFDS from the previous 3 years to build the BFDS database. This data will be 

used for analysis purposes and will not be shared with the passenger. 

7.4 Institute an intensive training program for all baggage handling personnel. As a minimum, 

the slide presentation “A Study in Baggage Loss Prevention” produced by the New York Airport 

Security Council, should be used.

7.5 Security surveys of airports should include recommendations for improving the security 

environment of baggage claim areas, e.g. more frequent law enforcement presence in claim 

areas and access to available security camera footage throughout the airport upon request.

7.6 Members should use the IATA Profile of a Fraudulent Baggage Claim, available on request 

from the Assistant Director, Airport Services being ever mindful that the appearance of profiled 

items on a claim represents warning flags for a claims supervisor, not that the claim is 

automatically fraudulent and not to be considered as conclusive. Track baggage on arrival 

delivery, per Resolution 753, Baggage Tracking 

7.7 When processing a claim the airline should only accept photo identification and request 

original receipts. If receipts are electronic, they should include the shipping address as further 

proof of purchase. All identification and receipts copies should be kept on file.

The file of receipts should include genuine and fraudulent receipts to help the fraudulent 

identification process. 

7.8 When validating photo identification, consider the use of social networking and other media 

sites.

7.9 Within the constraints of applicable local laws and the obligations these create in relation to 

data collection, its processing and the protection of individual privacy rights, consider the legality 

of maintaining a sharable data base with other airlines of known and suspected fraudulent 

claims, with a view to the prevention, investigation, detection, report and prosecution of criminal 

activity. Where appropriate or necessary, consider adapting General Conditions of Carriage to 

allow such data to be legitimately obtained, processed and shared. In addition work with other 

fraud departments within the airline to capitalize on synergies and sharing of information

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015
P4.2

RECOMMENDED PRACTICE 1743e

BAGGAGE IRREGULARITY REPORT

(amending)

PSC(29 36)1743e

RECOMMENDED that:

....

Attachment ‘A’

IRREGULARITY CODES

...

P 80 Damage

S 81 Damage

S 83 Damage to security inspected baggage

.....

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015

RECOMMENDED PRACTICE 1745

 BAGGAGE INFORMATION MESSAGES

 (amending)

PSC(34 36)1745

RECOMMENDED that:

....

B4.6

2.3.22 .S Reconciliation Data; 6 to 26 characters

....

Construction Example Format

2.3.22.7 Passenger Status C a

B = Boarded; C = Checked-in;

N = Not checked-in; S = Stand-by

Passenger Status can be ignored for Reconciliation purposes for exception bags such as 

CREW and RUSH.

B4.6

....

4.8 CONSTRUCTION OF ELEMENTS AND DATA ITEMS IN THE BAGGAGE SOURCE 

MESSAGE

....

(C) RECONCILIATION DATA

(M) Element Identifier .S

(M) Authority To Load /Y

(OM) Seat number /10A

(OM) Passenger Status /N

(OM) Sequence Number /098

(OM) Security Number /888

(OM) Passenger Profile Status /Y

(OM) Authority to Transport /Y

(C) Baggage Tag Status /A

....
B4.5

Attachment ‘A’

....

2. CODE SET FOR BAGGAGE SECURITY SCREENING 

2.1 Additional Recommended Codes for Baggage Security Screening

Codes are used to enable risk based security screening for baggage. These are set in 

accordance with the security status of the passenger communicated from a risk based security 

system and reflected in the security information in the passengers boarding pass. The following 

codes are used

DEF – Default level of screening applies

SEL – Selected for increased level of screening

PRE – Selected for TSA PreCheck

NON – No screening required conditional to applicable regulations (e.g. ‘one stop screening’ for 

transfer baggage from an airport classified as safe or for baggage screened prior to check-in)

Translations from Boarding Pass (BCBP) to .X element

ERC Value Position RBS System Status Boarding Pass 

Indicator

.X Element

0 CLEAR None DEF

2 SELECTEE SSSS SEL

3 KNOWN TSA, PRE, TSA 

PRECHK**

PRE

• The TSA PRE indicator is available from your TSA Representatives

** Boarding Pass Indicator may vary based on individual airline processes

When baggage is pooled then the highest security status (i.e. invoking the highest level of 

security screening) for any member of the group traveling will be applied to the pooled 

baggage. Alternatively, a separate BSM may be sent for each bag reflecting the security status 

for the passenger.

Note that KNOWN is a status set as a result of carriers registering for the TSA PRE CHECK 

Program. If an airline is not participating in the TSA PRE CHECK Program then this status will 

not apply.

....
....

B4.7

3. CODE SET FOR BAG CHECK-IN LOCATION IDENTIFIER

3.1 Additional Recommended Codes for Check in Location Identifier

BUST = Bus Station

CKIN = Airport check in desk

CONV = Convention Centre

CRPK = Car Park

CRRT = Car Rental

CURB = Curbside

HOME = Home

HOTC = Hotel

OFFC = Office Building

PORT = Sea Port

SELF = Self Service Check In

TRST = Train Station

BAGM = Airport Manned Bag Drop

BAGD = Airport Self Service Bag Drop

....

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015

B4.4

RECOMMENDED PRACTICE 1754 ELECTRONIC BAGGAGE TAG

(new)

PSC(36)1754

RECOMMENDED that:

The following specifications be followed as the community develops electronic baggage tags to 

more effectively facilitate the acceptance and subsequent processing of baggage, utilizing the 

license plate concept as described in Resolution 740. The community shall ensure compatibility 

of electronic baggage tags with airline and airport systems and the ability of electronic tags to be 

used in the interline environment. 

Throughout this Recommended Practice there are example images of the tag. These are 

examples only. Actual storage of data is specified in the relevant referenced Recommended 

Practices (e.g. 1740C and 1745)

General Electronic Tag Principles

1. Any party may make tags. Airlines will not be the sole point of distribution for electronic 

baggage tags.

2. The GUID (Globally Unique IDentification) and a locked object in memory block 3 (binary 

11) will be the primary identifiers for an electronic baggage tag.

3. Airline applications will read and write to the RFID tag memory area (UHF ISO 18000-

6c) 

4. Other users may also read and write to the tag display for their uses, such as cruise 

applications.

5. The .M shall be used in the BSM to transmit the GUID for the tags.

6. Airline applications will check that GUID in the DCS (or messages) matches the T-ID

GUID of the tag and then update the display. Key ISO parts – 18000-6c, 14443 mode 3 A 

and ISO 15961 for encoding. Key IATA – RP1740C for object identifiers.

Mandatory Components of an electronic tag – for details see the appropriate section of this 

Recommended Practice.

• RFID

• QR Code containing the GUID for the tag

• Bluetooth LE

• Updatable Display – showing the license plate in Interleaved 2 of 5 format and other 

journey information. The display shall show programmed information without the need 

for power.

• Mechanism to manually blank any tag that is permanently affixed to the bag.
Optional 

• NFC

• Any other technologies as developed and appropriate for the application.

Figure 1 –An electronic tag display and a printed 2-D barcode representing the GUID of 

the tag.

An electronic baggage tag shall have the following general format:

RFID

RFID inlays that are used in electronic baggage tags shall have a unique tag identifier (known 

as the GUID). The manufacturer and/or the provider of the RFID inlays shall be responsible for 

ensuring that all RFID inlays provided for use in electronic tags have a unique GUID.

GUID

The GUID is a version 4 (totally random) GUID as specified in RFC 4122 available at: 

http://www.ietf.org/rfc/rfc4122.txt

Manufacturer and Model identification

In order to retrieve the manufacturer and model of the electronic tag, objects are included in the 

QR Code and the RFID tag memory block 3 to identify the manufacturer and model. These are 

defined in the data dictionary in RP 1740c
QR Code

The QR Code shall have the following data format:

http://www.baggageservices.org/tag?GUID=<<guid>>&MAN=<<manufacturer>>&MOD=<<model>>&ORIG=<<airlin

e

For example:

http://www.guidlookup.com/tag?GUID=<<5f50474a-a767-4b14-b7fb87cadb7a1ab7>>&MAN=<<PRICEINC>>&MOD=<<EBT5000>>&ORIG=<<SkyFliersInc>>

>>

The GUID, MAN, MOD and ORIG codes are mandatory, others may be added by the 

manufacturer. When a generic tag (non-airline issued) is produced, the airline code 000 will be 

used.

Display

Handle attached tags that are capable of flipping over must have displays on both the front and 

backside of the tag. Tags that are built into the bag, or are attached such that they present 1 

side constantly may have a display only on the side presented to the barcode reading arrays. 

The display(s) shall be of a size and resolution that allows a complete set of data, as shown 

below, to be displayed. The barcode displayed on the tag shall be shown in such a resolution 

that reading by bar code scanners - both automatic and manual- will be possible without any 

degradation in read rates compared to the paper-tag read rate at the airport in which the 

electronic tags are being used.

The display of data on the tag should be as shown below and comprise of the following 

elements:
Example – not to scale or accurate in dimensions. 

EU Borders

When used in the EU, a distinctive shaded boarder measuring 5mm will be shown. This is a 

single black stripe interrupted by the letters EU. The letters are 4.1mm high (minimum) in Arial 

Rounded MT Bold or similar font. The EU lettering should be evenly spaced along the black 

marker line.

Final Destination

Shown as Brussels in the example, is the final destination airport for the journey. 

Routing Information

Shown as SAN - JFK - BRU in the example. This routing area shows the final destination and 

any transfer points in the journey. Alongside each airport 3-letter code the airline code, flight 

number and date are to be shown. Optionally, a short code for each sector can be included after 

the flight number and date, indicating an exceptional status for the bag

For example:

Note SHORT to read SCON in the picture

Indicates that for the connection at FRA the bag was to be processed with a short connection 

status. The electronic tag shall be capable of showing a minimum of 3 via points in the routing 

information. The lettering is a minimum of 4.1mm as per RESO 740 in the Arial Rounded MT 

Bold or similar.
Passenger Name and PNR

The passenger last name, first initial and title are to be displayed, along with the PNR shown in 

the example as PRICE/ANDREWMR and “AQ23SD”. The font is 3mm high (minimum) as per 

RESO 740.

Standard Baggage Licence Plate Barcode in T-BAR format

This is an interleaved 2 of 5 barcode that represents the 10-digit licence plate for the bag. The 

full 10 digit licence plate is to be shown in human readable form below the barcode. 

T-Bar format to facilitate read rate

Permanent Printing

The electronic baggage tag shall have displayed on the tag a QR Code that represents the 

GUID of the RFID Inlay that is included in the electronic baggage tag. This is included to allow 

optical identification of the electronic tag (rather than optical identification of the journey details 

stored on the tag). This barcode is to allow a passenger to identify the bag to the airline when 

BlueTooth LE is not available on the phone / device that the passenger is using. The GUID is 

wrapped in a URL as follows:

http://www.baggageservices.org/tag?GUID=<<guid>>&MAN=<<manufacturer>>&MOD=<<model>>&ORIG=<<airlin

e>>

Bluetooth LE

Electronic baggage tags shall have a Bluetooth LE interface, allowing the majority of the current 

mobile phones to work with the tag. Bluetooth interfaces shall be as described by the SIG 

group. This group produces open standards for use by any party. The standards are currently 

under development and a reference will be added once they are publicly available. 

Airline Interfaces

The airline shall interface with the electronic baggage tag through any of the available 

interfaces. The airline shall be responsible for ensuring that the electronic memory data and 

information displayed are aligned. 

Passenger Interface

The passenger shall, as a minimum, be able to identify the tag to the airline via the optical 

recognition QR Code.
Messaging

When baggage information messages are sent regarding electronic tags, the airline may include 

the GUID of the tag in the baggage information message. The .M field of the baggage 

information messages is to be used for this purpose. This field is optional. See RP 1745 for 

details.

.M element will be used to include the GUID (without the hyphens) plus include the LPC to 

ensure the relationship is maintained. The Julian date can be included between the LPC and the 

GUID if used. The .M element should be conditional. 

.M/0792019274//414F7E29507B4F2E9904F6583677C6FD

BSM with 1 LPC or non sequential LPCs will have the .M following the .N: 

.V/1LCDG

.F/7S1098/10JUN/LHR/Y

.N/0792019274001

.M/0792019274//414F7E29507B4F2E9904F6583677C6FD

.D/CKIN//10JUN/143328Z

.S/Y/07A/C/001/001//N

.W/K/1/10

.P/YOUNG/ROBMR

.L/6GEFS9

ENDBSM 

.V/1LCDG

.F/7S1098/10JUN/LHR/Y

.N/0792019274001

.M/0792019274//414F7E29507B4F2E9904F6583677C6FD

.N/0792019280001

.M/0792019280//C1BE7A51F9354D2ABBAC368F109D4085

.D/CKIN//10JUN/143328Z

.S/Y/07A/C/001/001//N

.W/K/2/20

.P/YOUNG/ROBMR

.L/6GEFS9

ENDBSM

BSM with multiple LPCs that are sequential will have the .M elements in the correct order 

following the .N element: 
.V/1LCDG

.F/7S1098/10JUN/LHR/Y

.N/0792019274002

.M/0792019274//414F7E29507B4F2E9904F6583677C6FD

.M/0792019275//C1BE7A51F9354D2ABBAC368F109D4085

.D/CKIN//10JUN/143328Z

.S/Y/07A/C/001/001//N

.W/K/1/10

.P/YOUNG/ROBMR

.L/6GEFS9

ENDBSM 

Enhanced Capabilities

Electronic baggage tags may feature advanced capabilities such as HF RFID interfaces (to 

allow programming of the tag by the passenger’s phone), GSM (to allow remote programming 

and tracking), or other features. The HF RFID interface is specified below, other interfaces are 

beyond the scope of the current recommended practice. 

The HF RFID interface to the electronic baggage tag shall comply with the following ISO/IEC 

standards:

ISO 14443-1 - Physical Characteristics

ISO 14443-2 - Radio Frequency Power and Signal Interface

ISO 14443-3 - Initialisation and anti-collision

ISO 14443-4 - Transmission Protocol

18092, 15693 14443 Type A, B

FAA Transmission Compliance

Any tag that has an active transmission capability must be compliant with FAA Advisory Circular 

91-21.1B on the use of electronic devices onboard aircraft. 

Tag Communication

Applications shall use the baggage XML Schema in the Business Requirements Document 

Baggage and Passenger Conformance Services. Communication with the tag is by the 

appropriate interface protocol. (Note, this document is being updated to include missing 

elements needed when working with an electronic baggage tag, please ensure you have the 

latest version).

Tag Programming

When a tag is updated by an airline application the tag shall confirm that the update was 

successful to the application. 

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015

R6

RECOMMENDED PRACTICE 1790b

RESERVATIONS PROCEDURES FOR CHARGEABLE ANCILLARY 

SERVICES (BILATERAL)

(new)

PSC(36)1790b

RECOMMENDED that, Member and/or CRSs use the following guidelines for the reservations 

of Chargeable Ancillary Services:

1. OBJECTIVES

This Recommended Practice recognizes that a standardized reservation process for

Chargeable Ancillary Services is required. This recommended practice aims at describing the 

end to end process for chargeable ancillary services with a focus on the reservation standards 

and procedures. 

Complimentary services will continue to be requested using standard SSRs. Standard SSRs 

are those services defined in AIRIMP which can be requested and fulfilled without payment.

1.1 Terms and Definitions

For the purpose of this Recommended Practice, the following definitions will apply;

Additional Services means those services, other than passenger air transportation, provided to 

a passenger for which there may or may not be a charge.

Codeshare

CODE SHARE: A flight segment that has one or more Marketing Carriers and one Operating 

Carrier.

MARKETING CARRIER: is the airline whose designator and flight number are used for the 

distribution of a product that is actually operated by another carrier (Operating Carrier).

OPERATING CARRIER: is the airline operating the flight.

Concurrence means an agreement from one carrier to permit the assessment of another 

carrier's optional service in which the concurring carrier participates.

Electronic Miscellaneous Document (EMD) means an electronic record issued by a Member 

or its authorized agent, in accordance with applicable tariffs, for residual value or for the 

collection of miscellaneous charges. An EMD must be either an EMD-A or an EMD-S.

Electronic Miscellaneous Document Associated—EMD-A means an EMD issued for the 

collection of miscellaneous and excess baggage charges that are to be lifted with an ET flight 

coupon(s). The intent of the association between the ET flight coupon(s) and the EMD-A value 

coupon(s) is to ensure the usage of the coupon is synchronized.

Electronic Miscellaneous Document Stand Alone—EMD-S means an EMD issued for 

residual value or the collection of miscellaneous charges that are not to be lifted with an ET 

flight coupon(s).
Optional Services means a data source provided by ATPCO for additional services an airline 

offers the customer for which the customer has a choice regarding whether to accept and/or 

purchase the service. 

A fee may or may not be charged for the service. The ATPCO Optional Services product can 

include data for required services such as unaccompanied minor services or oxygen onboard a 

flight.

Special Service Request (SSR) – Standard is a special service to be provided to the 

passenger, or a service information of a reservations procedural nature which, in the opinion of 

the sender, requires an immediate action by and/or a reply from the receiver.

Special Service Request (SSR) – Chargeable, based on a bilateral agreement, is a special 

service to be provided at a fee to the passenger, or a service information of a reservations 

procedural nature which, in the opinion of the sender, requires an immediate action by and/or a 

reply from the receiver.

Types of Service:

• Flight Related Services means those services ticketed by means of an EMD-A or 

EMD-S, booked via a Special Services Request (SSR) and related to a specific flight 

segment (e.g. products that enhance the in-flight experience such as, but not limited to, 

seat selection, meals, blankets and drinks).

• Non Flight Related Services means those services ticketed by means of an EMD-S, 

booked via a SVC element and not related to a specific flight segment (e.g. logo T-shirts 

and other merchandise). 

1.2 SSR ASVC and SVC Action/Reply/Advice/Status Codes

Action Codes

NN – Service Requested

HS – EMD issued for confirmed service

XX – Service cancelled

Reply/Advice codes

UN – Unable – special service not provided

UC – Unable to confirm/unable to waitlist

KD – Service Confirmed subject to receipt of EMD issue or reissue

KK – Confirmed No EMD required for service

NO – No action taken plus free text

HX – Have cancelled

SD – Schedule change/rebooking; EMD already issued. Document number must be included in 

the SSR (SSR ASVC only)

Status Codes

HK – Holding confirmed, no EMD required

HD – Holding confirmed; EMD required

HI – Holding confirmed; EMD issued (EMD can only be issued in the Ticket is issued)

HN – Holding Need
2. INITIAL BOOKING PROCESS

Ancillary services can be booked using either an itinerary SVC element when the requested 

service is not related to a flight or as an SSR ASVC when the services is flight related. This is in 

accordance with the provisions of AIRIMP chapter 3.21 “Additional Services” and subject to 

bilateral agreement.

When the request is associated to a flight, three SSR format options have been standardized to 

accommodate variations in airport departure control systems and/or member contracts with third 

party service vendors. It is an individual carrier decision which method is chosen. All three 

methods are described in the examples.

For the construction rules of SSR ASVC, refer to AIRIMP 2.11.6.8.

2.1. Flight related services

When the service is associated to flight segment(s), different booking methods can be used by 

the member. The three methods are:

• SSR ASVC in Conjunction with a Standard SSR Code

This may be used when the member system requires the standard SSR (e.g. VGML) 

code to deliver the service. The booking source may send a standard SSR with or 

without an ASVC as it is not always known whether or not the service is chargeable. 

• SSR ASVC in Conjunction with Chargeable SSR Family

This format may be used when the member system does not require the standard SSR 

code but does need the chargeable SSR family code (e.g. PDML)

• Stand-alone SSR ASVC

This may be used when the member system can support a single SSR (ASVC) and 

collect for the service

2.1.1. SSR ASVC in Conjunction with a Standard SSR Code

The standard SSR code (e.g. BIKE) is used to request the service. SSR ASVC is used in 

conjunction with the standard SSR code to convey Electronic Miscellaneous Document (EMD) 

information.

It is recommended to include the SSR ASVC in the original request from the booking source to 

the Member (refer to AIRIMP 3.21.1). If a Member receives a standard SSR code without an 

SSR ASVC in conjunction with the standard SSR, the Member has two options;

1. Deny the service request; in the reply message from the member to the booking source 

the standard SSR in included with an NO reply code and free text explaining why no 

action was taken.

2. Confirm the service request. In the reply message from the member to the booking 

source the standard SSR is included with a KK reply code. An SSR ASVC in included in 

conjunction with the standard SSR. The SSR ASVC should only be sent with a KD reply 

code (EMD required). If no EMD is required because the passenger is exempted for 

payment for this chargeable service, no SSR ASVC should be included with a KK reply 

code (No EMD required)
Example 1 – Message from booking source to the Member requesting a vegetarian meal 

without a SSR ASVC in conjunction with the SSR VGML. 

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR

Example 1(a) – Message from the Member to the booking source denying the service indicating 

ASVC required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB NO1 MADJFK6253Y20JUN-1JACOBS/RICKMR.CHARGEABLE SERVICE 

SSR VGML IB ///SSR ASVC REQUIRED

Example 1(b) – Message from the Member to the booking source confirming the service 

including an unsolicited SSR ASVC. The KD reply code in the ASVC denotes an EMD is 

required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB KD1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///MEAL

Example 1(c) – Message from the member to the booking source confirming the service. No 

EMD required; the SSR ASVC shall not be included with a KK reply code.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR
Example 2– Message from booking source to the Member requesting a vegetarian meal. The 

SSR ASVC in conjunction with the SSR VGML is included in the request message 

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///MEAL

Example 2(a) – Message from the Member to the booking source confirming the service. The 

KK reply code in the ASVC denotes no EMD is required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///MEAL

Example 2(b) – Message from the Member to the booking source confirming the service. The 

KD reply code in the ASVC denotes an EMD is required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB KD1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER

When the booking source issues the EMD, only the SSR ASVC is transmitted to the member. 

Example 3– Message from the booking source to the Member advising the EMD number and 

type of EMD issued (EMD-A). The HS action code in the ASVC denotes EMD issued for 

confirmed service.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HS1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER/A/1290123412987C1
2.1.2. SSR ASVC in Conjunction with Chargeable SSR Family

When no standard SSR code exist, or when the Member choses to distinguish between 

products, a chargeable SSR family code can be used to request services as an alternative to 

creating a new SSR for a chargeable service. These bilateral SSR codes identify a family of 

products or services such as PDBG, which stands for “paid baggage” (refer to AIRIMP 

2.11.6.6). SSR ASVC is used in conjunction with the chargeable SSR family to convey EMD 

information. 

List of Chargeable SSR Family codes

SSR Code Definition

PDBG Pre-Paid Baggage (chargeable)

PDCO Carbon Offset (chargeable)

PDFF Frequent Flyer (chargeable)

PDGT Ground Transportation and Non-Air Services (chargeable)

PDIE In-Flight Entertainment (chargeable)

PDLG Lounge (chargeable)

PDML Meal/Beverage (chargeable)

PDPT Pets (chargeable)

PDRO Rule Override (chargeable)

PDSB Standby (chargeable)

PDST Store (chargeable)

PDTS Travel Services (chargeable)

PDUM Unaccompanied Minor (chargeable)

PDUG Upgrades (chargeable)

When a standard SSR is sent from the booking source to the member, the booking source may 

not always be aware the service is chargeable. Therefore standard SSR codes may be sent 

without an SSR ASVC in conjunction with the standard SSR. The PDxx SSR codes are always 

chargeable. Therefore the SSR ASVC is a mandatory element and is to be included in the 

original request from the booking source and as part of the reply from the member (refer to 

AIRIMP 3.21.1) with the reference to the chargeable SSR family code used. If a member 

receives a chargeable SSR family code without the accompanied SSR ASVC the request 

should be denied.

Example 1(a) – Message from booking source to Member using a Chargeable SSR Family 

code. No SSR ASVC in conjunction with the Chargeable SSR Family code is included.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDML IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR//RAW VEGETARIAN

SSR PDML IB ///LUNCH
Example 1(b) –Message from the Member to the booking source denying the service. The 

Chargeable SSR Family code is included with an NO reply code. The free text explains why no 

action was taken.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDML IB NO1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR//RAW VEGETARIAN

SSR PDML IB ///LUNCH.CHARGEABLE SERVICE SSR ASVC REQUIRED 

Example 2(a) – Message from booking source to the Member requesting a raw vegetarian 

lunch. An SSR ASVC in conjunction with the SSR PDML is included. 

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDML IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR//RAW VEGETARIAN 

SSR PDML IB ///LUNCH

SSR ASVC IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR/PDML/RAW 

SSR ASVC IB ///VEGETARIAN LUNCH

Example 2(b) – Message from the Member to the booking source confirming the service. The 

SSR ASVC is included with a KK reply code; no EMD required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDML IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR//RAW VEGETARIAN

SSR PDML IB ///LUNCH

SSR ASVC IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR/PDML/RAW 

SSR ASVC IB ///VEGETARIAN LUNCH

Example 2(c) – Message from the Member to the booking source confirming the service. The 

SSR ASVC is included with a KD reply code; EMD required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDML IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR//RAW VEGETARIAN

SSR PDML ///LUNCH

SSR ASVC IB KD1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR/PDML/RAW 

SSR ASVC IB ///VEGETARIAN LUNCH

When the EMD is issued by the booking source only the SSR ASVC (with reference to the 

chargeable SSR family in the formatted text) is sent with an HS action code including the EMD 

number and type. 
Example 3 – message from the booking source advising the EMD number and (EMD-A).

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HS1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR/PDML/RAW 

SSR ASVC IB ///VEGETARIAN LUNCH/A/1250241234567C1

2.1.3. Stand-alone SSR ASVC

If no standard SSR or chargeable family SSR code is available for requesting a service, 

Members may use an SSR ASVC for both requesting the service and advising the EMD number 

and type.

If available, it is recommended that a standard SSR or a chargeable family SSR be used. 

However, a Member may still decide to use a stand-alone SSR ASVC for services for which a 

standard or Family SSR exists.

Example 1(a) – Message from booking source to the Member requesting internet access using 

the stand-alone SSR ASVC.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB NN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.G/0CL//INTERNET 

SSR ASVC IB ///ACCESS

Example 1(b) – Message from the Member to the booking source confirming the service; no 

EMD required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB KK1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.G/0CL//INTERNET 

SSR ASVC IB ///ACCESS

Example 1(c) – Message from the Member to the booking source confirming the service; EMD 

required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB KD1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.G/0CL//INTERNET 

SSR ASVC IB ///ACCESS
Example 1(d) – Message from the booking source to the Member advising the EMD number 

and type (EMD-A).

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HS1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.G/0CL//INTERNET 

SSR ASVC IB ///ACCESS/A/175122312897C1

2.2. Non flight related services

For non-flight related services the auxiliary segment SVC shall be used. These services can be 

requested in addition to airline space specified in the segment element of the message or 

independently. For construction rules refer to AIRIMP 2.10.6.

Example 1(a) – Message from the booking source to the Member requesting a gift card.

MUCRM1A

.HDQRM1S 

HDQ1S G4ITY6/XF63/19973465/ATL/1S/T/US

1BAHAR/DONNAMS

SVC LY NN1 TLV 30MAY/F/0LA/GIFT CARD/NM-1BAHAR/DONNAMS 

Example 1(b) – Message from the Member to the booking source confirming the service; EMD 

required.

HDQRM1S

.MUCRM1A

HDQ1S G4ITY6

1BAHAR/DONNAMS

SVC LY KD1 TLV 30MAY/F/0LA/GIFT CARD/NM-1BAHAR/DONNAMS

Example 1(c) – Message from the booking source to the Member advising the EMD number. 

MUCRM1A

.HDQRM1S 

HDQ1S G4ITY6/XF63/19973465/ATL/1S/T/US

1BAHAR/DONNAMS

SVC LY HS1 TLV 30MAY/F/0LA/GIFT CARD/NM-1BAHAR/DONNAMS/0061234567890C1 

Example 1(d) – Message from the booking source to the member requesting a limousine 

service. Two location codes are used.

MUCRM1A

.HDQRMAA

HDQAA QWERTY/ATL//ATL/AA/A/US

1DRAKE/STEVEMR

SVC BA NN1 LHRLGW 10JUN/B/0BR/LIMOUSINE SERVICE/NM-1DRAKE/STEVEMR
3. ANCILLARY SERVICE CHANGE

3.1 Voluntary change

Voluntary changes refer to service changes requested by the passenger. A change means 

cancelling a service and requesting a new service. Flight related services are either cancelled 

because the flight to which the services are associated is cancelled or the service is no longer 

required on the current flight. Both the cancellation and the request are sent in one message.

3.1.1 Where no EMD was issued

3.1.1.1 Flight related services

PNR is as follows:

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB HK1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB HD1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER

Example 1(a) – Message from the booking source to the Member cancelling the vegetarian 

meal originally requested using the standard SSR VGML and an SSR ASVC in conjunction with 

the SSR VGML for which no EMD had been issued yet. At the same time in-flight entertainment

is requested using the Family SSR PDIE and an SSR ASVC in conjunction with the SSR PDIE.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER

SSR PDIE IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0B1//IN FLIGHT 

SSR PDIE IB ///ENTERTAINMENT

SSR ASVC IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0B1/PDIE/IN FLIGHT 

SSR ASVC IB ///ENTERTAINMENT

Example 1(b) – Message from the Member to the booking source confirming the service; EMD 

required. 

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDIE IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0B1//IN FLIGHT 

SSR PDIE IB ///ENTERTAINMENT

SSR ASVC IB KD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0B1/PDIE/IN FLIGHT 

SSR ASVC IB ///ENTERTAINMENT
Example 1(c) – Message from the booking source to the member advising the EMD number 

and type (EMD-A).

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HS1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0B1/PDIE/IN FLIGHT 

SSR ASVC IB ///ENTERTAINMENT/A/1290456738123C1

3.1.1.2 Non flight related services

Example 1(a) - Message from the booking source to the member cancelling the gift card for 

which no EMD had been issued yet and requesting lounge access.

MUCRM1A

.HDQRM1S 

HDQ1S G4ITY6/XF63/19973465/ATL/1S/T/US

1BAHAR/DONNAMS

SVC LY XX1 TLV 30MAY/F/0LA/GIFT CARD/NM-1BAHAR/DONNAMS

SVC LY NN1 TLV 30MAY/E/0BX/LOUNGE ACCESS/NM-1BAHAR/DONNAMS

Example 1(b) – Message from the Member to the booking source confirming the service; EMD 

required.

HDQRM1S

.MUCRM1A

HDQ1S G4ITY6

1BAHAR/DONNAMS

SVC LY KD1 TLV 30MAY/E/0BX/LOUNGE ACESS/NM-1BAHAR/DONNAMS 

Example 1(c) – Message from the booking source to the Member advising the EMD number. 

MUCRM1A

.HDQRM1S

HDQ1S G4ITY6/XF63/19973465/ATL/1S/T/US

1BAHAR/DONNAMS

SVC LY HS1 TLV 30MAY/E/0BX/LOUNGE ACESS/NM-1BAHAR/DONNAMS/0061234567890C1 

3.1.2 Where an EMD was issued

3.1.2.1 Flight related services

Depending on the ticketing conditions the booking source either advises the EMD number of the 

cancelled service for the new service, or a new EMD number is advised. Whether the new EMD 

has been exchanged or not for the old EMD cannot be read from the reservation message.
PNR is as follows:

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HI1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER/A/1290123412987C1

3.1.2.1.1 Previously issued EMD is advised for the new service

Example 1(a) – Message from the booking source to the Member cancelling/rebooking the flight 

and requesting the same services on the new flight.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK XX2

IB6253Y21JUN MADJFK SS2/1300 1945

SSR VGML IB NN1 MADJFK6253Y21JUN-1JACOBS/RICKMR

SSR ASVC IB NN1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER

Example 1(b) – Message from the Member to the booking source confirming the service; EMD 

required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y21JUN MADJFK HK2

SSR VGML IB KK1 MADJFK6253Y21JUN-1JACOBS/RICKMR

SSR ASVC IB KD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER

Example 1(c) – Message from the booking source to the Member advising the EMD number for 

the new service which was previously issued for the cancelled service.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y21JUN MADJFK HK2

SSR ASVC IB HS1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER/A/1290123412987C1
3.1.2.1.2 New EMD is advised for the new service

Example 1(a) – Message from the booking source to the Member cancelling the vegetarian 

meal for which an EMD had already been issued and requesting in-flight entertainment.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER/A/1290123412987C1

SSR PDIE IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0B1//IN FLIGHT 

SSR PDIE IB ///ENTERTAINMENT

SSR ASVC IB NN1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0B1/PDIE/IN FLIGHT 

SSR ASVC IB ///ENTERTAINMENT

Example 1(b) – Message from the Member to the booking source confirming the service; EMD 

required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDIE IB KK1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0B1//IN FLIGHT 

SSR PDIE IB ///ENTERTAINMENT

SSR ASVC IB KD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0B1/PDIE/IN FLIGHT 

SSR ASVC IB ///ENTERTAINMENT

Example 1(c) – Message from the booking source to the member advising a new EMD number.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HS1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0B1/PDIE/IN FLIGHT 

SSR ASVC IB ///ENTERTAINMENT/A/1290456738123C1
3.2 Involuntary Change

Involuntary changes refer to service changes made by the airline without influence of the 

passenger.

In the event of an involuntary change, the Member shall advise when the service is reaccommodated. For services where an EMD had been issued, a Member may take action on 

the EMD and inform the booking source the document type and number associated to this new 

service. 

3.2.1 Flight related Services

3.2.1.1 Schedule Changes

During a schedule change a Member may rebook the services if available on the alternative 

flight. If an EMD had already been issued, the Member may re-use the same EMD or exchange 

the EMD if applicable. Alternatively, the Member may let the booking source take action on the 

EMD.

The Member may send either one or multiple messages:

1. ASC message including the rebooked services. An EMD number is included in the SSR 

ASVC with advice code SD. No further action required by the booking source.

2. ASC message including the rebooked services. An EMD number is not included in the 

SSR ASVC. The advice code is KD; EMD required.

a. Followed by an advice message including the SSR ASVC only. An EMD number 

is included. The advice code SD. No further action required by the booking 

source

b. No follow-up message. Action required on the EMD by the booking source

3. ASC message. The rebooked services are not included.

a. Followed by an advice message including the rebooked services. An EMD 

number is included in the SSR ASVC. The advice code SD. No further action 

required by the booking source.

4. ASC message. The rebooked services are not included.

a. Followed by an advice message including the rebooked services. An EMD 

number is not included in the SSR ASVC. The advice code is KD; EMD required.

i. Followed by an advice message including the SSR ASVC only. An EMD 

number is included. The advice code SD. No further action required by 

the booking source

ii. No follow-up message. Action required on the EMD by the booking 

source

5. ASC message. The rebooked services are not included. No follow-up messages: action 

required on the services and EMD if applicable by the booking source.
3.2.1.2 Equipment Changes

During an equipment change, services may no longer be available or the service may be 

rebooked by the Member. Rebooking a service applies to seats in particular since not only the 

seat number could have changed but also the type of seat; the passenger is re-seated to a seat 

with a different seat number but with the same seat characteristics or the passenger is reseated 

to a seat with different seat characteristics. The cancelled service is advised with an UN advice 

code for standard SSR, the family SSR and SSR ASVC. The alternative service, if applicable, is 

advised with a KK reply code for the standard SSR and family SSR. The Advice code of the 

alternative SSR ASVC depends on whether an EMD is required (KD), not required (KK) or was 

already issued and used for the new service (SD).

The Member may send either one or multiple messages:

1. Advice message including cancelled and rebooked services. An EMD number is 

included in both the cancelled and the alternative SSR ASVC. The advice code of the 

alternative SSR ASVC is SD. No further action required by the booking source.

2. Advice message including cancelled and rebooked services. An EMD number is 

included in the cancelled SSR ASVC, but not in the alternative SSR ASVC. The advice 

code is KD; EMD required.

a. Followed by an advice message including the SSR ASVC only. An EMD number 

is included. The advice code SD. No further action required by the booking 

source

b. No follow-up message. Action required on the EMD by the booking source.

3. Advice message including cancelled and rebooked services. An EMD number is neither 

included in the cancelled SSR ASVC nor in the alternative SSR ASVC; no EMD had 

been issued yet. The advice code of the alternative SSR ASVC is either KD: EMD 

required or KK; no EMD required.

4. Advice message including cancelled services only. Whether an EMD number is included 

in the cancelled SSR ASVC is not relevant. The booking source should take action on 

the services and on the EMD if already issued.

For involuntary changes as a result of an equipment change refer to section 9.2.

3.2.1.3 When no EMD was issued

PNR booking source:

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB HK1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB HD1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER
Example 1 - Message from the Member to the booking source advising the flight reaccommodation and the rebooked services on the alternative flight; EMD required. 

MUCRM1A

.MADRMIB

ASC

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK UN2

IB6253Y21JUN MADJFK TK2/1300 1945

SSR VGML IB KK1 MADJFK6253Y21JUN-1JACOBS/RICKMR

SSR ASVC IB KD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER

Example 1(a) - Message from the member to the booking source advising the flight reaccommodation only.

MUCRM1A

.MADRMIB

ASC

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK UN2

IB6253Y21JUN MADJFK TK2/1300 1945

Example 1(b) – Message from the Member to the booking source advising the rebooked 

services on the alternative flight; EMD required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y21JUN MADJFK HK2

SSR VGML IB KK1 MADJFK6253Y21JUN-1JACOBS/RICKMR

SSR ASVC IB KD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER

3.2.1.4 When an EMD was issued

PNR booking source:

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB HK1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB HI1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER/A/1290123412987C1
Example 1 - Message from the Member to the booking source advising the flight reaccommodation and the rebooked services on the alternative flight. The previously issued EMD 

is used for the service on the alternative flight; no action required by the booking source.

MUCRM1A

.MADRMIB

ASC

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK UN2

IB6253Y21JUN MADJFK TK2/1300 1945

SSR VGML IB KK1 MADJFK6253Y21JUN-1JACOBS/RICKMR

SSR ASVC IB SD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER//1290123412987C1

Example 2(a) - Message from the member to the booking source advising the flight reaccommodation and the rebooked services on the alternative flight; EMD required.

MUCRM1A

.MADRMIB

ASC

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK UN2

IB6253Y21JUN MADJFK TK2/1300 1945

SSR VGML IB KK1 MADJFK6253Y21JUN-1JACOBS/RICKMR

SSR ASVC IB KD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN

SSR ASVC IB ///DINNER

Example 2(b) – Message from the Member to the booking source advising the previously 

issued EMD is used for the service on the alternative flight; no action required by the booking 

source

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y21JUN MADJFK HK2

SSR ASVC IB SD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER//1290123412987C1

Example 3(a) – Message from the Member to the booking source advising the flight reaccommodation only.

MUCRM1A

.MADRMIB

ASC

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK UN2

IB6253Y21JUN MADJFK TK2/1300 1945
Example 3(b) – Message from the Member to the booking source advising the rebooked 

services on the alternative flight; EMD required.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y21JUN MADJFK HK2

SSR VGML IB KK1 MADJFK6253Y21JUN-1JACOBS/RICKMR

SSR ASVC IB KD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN

SSR ASVC IB ///DINNER

Example 3(c) – Message from the Member to the booking source advising the previously 

issued EMD is used for the service on the alternative flight; no action required by the booking 

source.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y21JUN MADJFK HK2

SSR ASVC IB SD1 MADJFK6253Y21JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER//1290123412987C1

4 CANCELLATION PROCESS

4.1Cancellation by the Booking Source

Cancellation of services follows the standard process of cancelling SSR Elements or Auxiliary 

Segments by the booking source. When the service was requested using a standard SSR or a 

Family SSR also the SSR ASVC in conjunction with those SSR’s should be included in the 

message to the member using an XX action code. 

When an EMD has already been issued, the EMD number must be included in the cancellation 

message to the Member as part of the SSR ASVC or auxiliary segment SVC.

4.1.1 Where no EMD was issued 

4.1.1.1 Flight related services

PNR booking source:

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB HK1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB HD1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER
Example 1 – Message from the booking source to the Member cancelling the service. Both the 

standard SSR and the SSR ASVC are included in the message.

MADRMIB

.MUCRM1A

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB///DINNER

PNR booking source:

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDML IB HK1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR//VEGETARIAN LUNCH

SSR ASVC IB HD1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR/PDML/VEGETARIAN 

SSR ASVC IB///LUNCH

Example 2 – Message from the booking source to the Member cancelling the service. Both the 

Family SSR and the SSR ASVC are included in the message.

MADRMIB

.MUCRM1A

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDML IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR//VEGETARIAN LUNCH

SSR ASVC IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR/PDML/VEGETARIAN 

SSR ASVC IB///LUNCH

PNR booking source:

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HD1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.G/0CL//INTERNET ACCESS

Example 3 – Message from the booking source to the member cancelling the service. Only the 

stand-alone SSR ASVC is included in the message.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB XX1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.G/0CL//INTERNET ACCESS
4.1.1.2 Non flight related services

PNR booking source:

1BAHAR/DONNAMS

SVC LY HD1 TLV 30MAY/F/0LA/GIFT CARD/NM-1BAHAR/DONNAMS

Example 1 – Message from the booking source to the Member cancelling the service. The 

auxiliary segment SVC is included in the message.

MUCRM1A

.HDQRM1S

HDQ1S G4ITY6/XF63/19973465/ATL/1S/T/US

1BAHAR/DONNAMS

SVC LY XX1 TLV 30MAY/F/0LA/GIFT CARD/NM-1BAHAR/DONNAMS

4.1.2 Where an EMD was issued

4.1.2.1 Flight related services

PNR booking source:

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB HK1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB HI1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER/A/1290123412987C1

Example 1 – Message from the booking source to the Member cancelling the service. Both the 

standard SSR and the SSR ASVC are included in the message. The EMD number is included in 

the SSR ASVC.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR VGML IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR

SSR ASVC IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB///DINNER/A/1290123412987C1

PNR booking source:

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDML IB HK1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR//VEGETARIAN LUNCH

SSR ASVC IB HI1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR/PDML/VEGETARIAN 

SSR ASVC IB ///LUNCH/A/1250241234567C1
Example 2 – Message from the booking source to the Member cancelling the service. Both the 

Family SSR and the SSR ASVC are included in the message. The EMD number is included in 

the message.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR PDML IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR//VEGETARIAN LUNCH

SSR ASVC IB XX1 MADJFK6253Y20JUN-1JACOBS/RICKMR.G/0AR/PDML/VEGETARIAN 

SSR ASVC IB///LUNCH/A/1250241234567C1

PNR booking source:

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HI1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.G/0CL//INTERNET ACCESS/A

SSR ASVC IB ///175122312897C1

Example 3 – Message from the booking source to the Member cancelling the service. The 

stand-alone SSR ASVC is included in the message including the EMD number.

MADRMIB

.MUCRM1A

MUC1A XAG5TY/MADAT2001/37465683/MAD/1A/T/ES

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB XX1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.G/0CL//INTERNET ACCESS/A

SSR ASVC IB ////175122312897C1

4.1.2.2 Non flight related services

PNR booking source:

1BAHAR/DONNAMS

SVC LY HI1 TLV 30MAY/F/0LA/GIFT CARD/NM-1BAHAR/DONNAMS/0061234567890C1

Example 4 – Message from the booking source to the Member cancelling the service. The 

auxiliary segment SVC is included in the message including the EMD number.

HDQRMBA

.MUCRM1A 

MUC1A G4ITY6

1BAHAR/DONNAMS

SVC LY XX1 TLV 30MAY/F/0LA/GIFT CARD/NM-1BAHAR/DONNAMS/0061234567890C1
4.2 Cancellation by the Member

When a flight related service is cancelled by the member, the booking source is advised about 

the cancellation using an HX advice code for the standard SSR, the family SSR, and the SSR 

ASVC either in conjunction with the standard and family SSR or as a standalone SSR. For nonflight related services the SVC auxiliary segment is sent with an HX advice code. 

When an EMD was already issued, the EMD number is included in the SSR ASVC for a flight 

related service and in the SVC element for a non-flight related service. It is recommended to 

include an SSR OTHS advising why the service was cancelled.

4.2.1 Flight Related Services

Example 1(a) – Message from the member to the booking source advising the service has 

been cancelled. The booking method of an SSR ASVC in conjunction with a standard SSR was 

used. No EMD had been issued yet.

HDQRM1P

.MUCRM1A

HDQ1P G4ITY6

1BAHAR/DONNAMS

LY001Y20JUN TLVJFK HK1

SSR BIKE LY HX1 TLVJFK001Y20JUN

SSR ASVC LY HX1 TLVJFK001Y20JUN.H/S57/BIKE/BICYCLE

SSR OTHS 1P SERVICE CANCELLED DUE TO EQP CHANGE

Example 1(b) – Message from the member to the booking source advising the service has 

been cancelled. The booking method of an SSR ASVC in conjunction with a family SSR was 

used. The EMD had already been issued; EMD number is included in the SSR ASVC.

HDQRM1P

.MUCRM1A

HDQ1P G4ITY6

1BAHAR/DONNAMS

LY001Y20JUN TLVJFK HK1

SSR PDBG LY HX1 TLVJFK001Y20JUN.H/S57//BICYCLE

SSR ASVC LY HX1 TLVJFK001Y20JUN.H/S57/PDBG/BICYCLE/A/1290123414027C1

SSR OTHS 1P SERVICE CANCELLED DUE TO EQP CHANGE

Example 1(c) – Message from the member to the booking source advising the service has been 

cancelled. The booking method of a standalone SSR ASVC was used. The EMD had already 

been issued; EMD number is included in the SSR ASVC.

HDQRM1P

.MUCRM1A

HDQ1P G4ITY6

1BAHAR/DONNAMS

LY001Y20JUN TLVJFK HK1

SSR ASVC LY HX1 TLVJFK001Y20JUN.H/S57//BICYCLE/A/1290123414027C1

SSR OTHS 1P SERVICE CANCELLED DUE TO EQP CHANGE
4.2.2 Non-Flight Related Services

Example 2(a) – Message from the member to the booking source advising the service has been 

cancelled. The auxiliary segment SVC was used. No EMD had been issued yet.

HDQRM1P

.MUCRM1A

HDQ1P G4ITY6

1BAHAR/DONNAMS

SVC LY HX1 TLV 30MAY/F/0LA/GIFT CARD/NM1BAHAR/DONNAMS

SSR OTHS 1P SERVICE CANCELLED AS NO LONGER AVAILABLE

Example 2(b) – Message from the member to the booking source advising the service has 

been cancelled. The auxiliary segment SVC was used. The EMD had already been issued; 

EMD number is included in the SVC element.

HDQRM1P

.MUCRM1A

HDQ1P G4ITY6

1BAHAR/DONNAMS

SVC LY HX1 TLV 30MAY/F/0LA/GIFT CARD/NM1BAHAR/DONNAMS/0061234567890C1 

SSR OTHS 1P SERVICE CANCELLED AS NO LONGER AVAILABLE

5. INTERLINE ITINERARIES

In an interline itinerary the same service may be requested for different members of the 

itinerary. The booking source shall use the applicable booking method of each member.

PNR Booking source:

HDQ1P BDG5TG

1DRAKE/STEVEMR 1JACOBS/RICKMR

BA 5678Y20JUL JFKLHR 

IB 2539Y21JUL LHRMAD 

A vegetarian meal is requested for both segments. BA uses a stand-alone SSR ASVC as a 

booking method while IB uses the standard SSR VGML and the SSR ASVC in conjunction with 

the SSR VGML. Services are requested in separate transactions.

Example 1(a) – Message from the booking source to Member BA requesting the service using 

the stand-alone SSR ASVC.

MUCRM1A

.HDQRM1P

HDQ1P BDG5TG/98SR/12734768/NYC/1P/T/US

1DRAKE/STEVEMR 1JACOBS/RICKMR

BA5678Y20JUL JFKLHR HK2

IB2539Y21JUL LHRMAD HK2

SSR ASVC BA NN1 JFKLHR5678Y20JUL-1JACOBS/RICKMR/G/0AN//VEGETARIAN 

SSR ASVC BA ///DINNER
Example 1(b) – Message from the booking source to the Member IB requesting the service 

using the standard SSR VGML and the SSR ASVC in conjunction with the SSR VGML.

MUCRM1A

.HDQRM1P

HDQ1P BDG5TG/98SR/12734768/NYC/1P/T/US

1DRAKE/STEVEMR 1JACOBS/RICKMR

BA5678Y20JUL JFKLHR HK2

IB2539Y21JUL LHRMAD HK2

SSR VGML IB NN1 LHRMAD2539Y21JUL-1JACOBS/RICKMR

SSR ASVC IB NN1 LHRMAD2539Y21JUL-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER

Example 2(a) – Message from the Member BA confirming the service; EMD required.

HDQRM1P

.MUCRM1A

HDQ1P BDG5TG

1DRAKE/STEVEMR 1JACOBS/RICKMR

BA5678Y20JUL JFKLHR HK2

SSR ASVC BA KD1 JFKLHR5678Y20JUL-1JACOBS/RICKMR/G/0AN//VEGETARIAN 

SSR ASVC BA ///DINNER

Example 2(b) – Message from the Member IB confirming the service; EMD required.

HDQRM1P

.MUCRM1A

HDQ1P BDG5TG

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB2539Y21JUL LHRMAD HK2

SSR VGML IB KK1 LHRMAD2539Y21JUL-1JACOBS/RICKMR

SSR ASVC IB KD1 LHRMAD2539Y21JUL-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER

Example 3 – Message from the booking source to the Members BA and IB advising the EMD 

number. Members BA and IB have an interline agreement. One EMD has been issued with BA 

being the validating carrier.

MUCRM1A

.HDQRM1P

HDQ1P BDG5TG/98SR/12734768/NYC/1P/T/US

1DRAKE/STEVEMR 1JACOBS/RICKMR

BA5678Y20JUL JFKLHR HK2

IB2539Y21JUL LHRMAD HK2

SSR ASVC BA HS1 JFKLHR5678Y20JUL-1JACOBS/RICKMR/G/0AN//VEGETARIAN 

SSR ASVC BA ///DINNER/A/1251298657489C1

SSR ASVC IB HS1 LHRMAD2539Y21JUL-1JACOBS/RICKMR.G/0AN/VGML/VEGETARIAN 

SSR ASVC IB ///DINNER/A/1251298657489C2
6. CODESHARE PROCESS

In a Code Share scenario two parties are involved when the Marketing Carrier is also the 

booking source and three parties when another party than the Marketing Carrier is the booking 

source.

For Additional Services the message structure of the various Code Share Options are 

applicable like for all other SSR Elements. It is recommended using the same booking method 

by the Marketing Carrier and Operating Carrier(s). When agreements are extended for selling 

additional services with other Code Share partners it may no longer be possible using the same 

booking method. The Marketing Carrier may decide filing:

1. the different booking method(s) of the Operating Carrier(s).

2. its own booking method for all flights and translates the applicable booking method in the 

Code Share Request message to the Operating Carrier and reply to the booking source 

using the booking method as originally received.

In the following scenarios carriers XX, YY and ZZ offer a chargeable vegetarian meal on their 

prime flights. All carriers want to offer a chargeable vegetarian meal when they are marketed by 

another carrier. In all examples Carrier XX is the Marketing Carrier and carriers YY and ZZ are 

the Operating Carriers. 

Booking Methods:

Carrier XX: Standard SSR VGML and an SSR ASVC in conjunction with the SSR VGML.

Carrier YY: Family SSR PDML and an SSR ASVC in conjunction with the SSR PDML.

Carrier ZZ: Standalone SSR ASVC

6.1 Marketing Carrier and Operating Carrier use the same booking method

All carriers agreed using the Standard SSR VGML and an SSR ASVC in conjunction with the 

SSR VGML.

PNR Booking Source (System Provider 1T):

RLOC: QWERTY

1TRAVELLER/AMR

1. XX001 Y 10JUN FRALHR 1000 1100

2. XX002 Y 10JUN LHRJFK 1230 1700

 OPERATED BY YY

3. XX003 Y 20JUN JFKFRA 1800 0730/1

 OPERATED BY ZZ

1. SSRVGML XX HN1 FRALHR0001Y10JUN

2. SSRASVC XX HN1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

3. SSRVGML XX HN1 LHRJFK0002Y10JUN

4. SSRASVC XX HN1 LHRJFK0456Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

5. SSRVGML XX HN1 JFKFRA0003Y20JUN

6. SSRASVC XX HN1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGERATIAN MEAL
Example 1 – Message from the booking source to the member XX requesting the service for all 

segments.

HDQRMXX

.HDQRM1T

HDQ1T QWERTY/ABC/56736467/PAR/1T/T/FR

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX NN1 FRALHR0001Y10JUN

SSRASVC XX NN1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

SSRVGML XX NN1 LHRJFK0002Y10JUN

SSRASVC XX NN1 LHRJFK0002Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

SSRVGML XX NN1 JFKFRA0003Y20JUN

SSRASVC XX NN1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGETARIAN MEAL

Example 1(a) – Message from the member XX to the booking source confirming the service on 

the XX Prime Flight; EMD required.

HDQRM1T

.HDQRMXX

HDQ1T QWERTY

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX KK1 FRALHR0001Y10JUN

SSRASVC XX KD1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

Example 1(b) – Message from member XX to member YY requesting the service (Code Share 

Option 5).

HDQRMYY

.HDQRMXX

HDQXX 6BDFH8

HDQ1T QWERTY/ABC/56736467/PAR/1T/T/FR

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1/1000 1100

YY0456 Y 10JUN LHRJFK HK1-XX002Y

SSRVGML YY NN1 LHRJFK0456Y10JUN

SSRASVC YY NN1 LHRJFK0456Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

Example 1(c) – Message from member XX to member ZZ requesting the service (Code Share 

Option 2).

HDQRMZZ

.HDQRMXX

HDQ1T QWERTY/ABC/56736467/PAR/1T/T/FR

HDQXX 6BDFH8

1TRAVELLER/AMR

XX0002 Y 10JUN LHRJFK HK1/1230 1700

XX0003 Y 20JUN JFKFRA CH1

SSRVGML XX NN1 JFKFRA0003Y20JUN

SSRASVC XX NN1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGETARIAN MEAL
Example 1(d) - Message from member YY to member XX confirming the service; no EMD 

required.

HDQRMXX

.HDQRMYY

HDQXX 6BDFH8

1TRAVELLER/AMR

YY0456 Y 10JUN LHRJFK HK1-XX002Y

SSRVGML YY KK1 LHRJFK0456Y10JUN

SSRASVC YY KK1 LHRJFK0456Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

Example 1(e) – Message from member ZZ to member XX denying the request.

HDQRMXX

.HDQRMZZ

HDQXX 6BDFH8

1TRAVELLER/AMR

XX0003 Y 20JUN JFKFRA CH1

SSRVGML XX NO1 JFKFRA0003Y20JUN

SSRASVC XX NO1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGETARIAN MEAL

SSROTHS XX SERVICE NOT AVAILABLE

Example 1(f) – Message from the member XX to the booking source, confirming the service for 

XX operated by YY; No EMD required.

HDQRMIT

.HDQRMXX

HDQ1T QWERTY

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX KK1 LHRJFK0002Y10JUN

SSRASVC XX KK1 LHRJFK0002Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

Example 1(g) – Message from the member XX to the booking source, denying the request for 

XX operated by ZZ.

HDQRMIT

.HDQRMXX

HDQ1T QWERTY

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX NO1 JFKFRA0003Y20JUN

SSRASVC XX NO1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGETARIAN MEAL

SSROTHS IT SERVICE NOT AVAILABLE
PNR Booking Source

Message processed:

RLOC: QWERTY

1TRAVELLER/AMR

1. XX001 Y 10JUN FRALHR 1000 1100

2. XX002 Y 10JUN LHRJFK 1230 1700

 OPERATED BY YY

3. XX003 Y 20JUN JFKFRA 1800 0730/1

 OPERATED BY ZZ

1. SSRVGML XX KK1 FRALHR0001Y10JUN

2. SSRASVC XX KD1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

3. SSRVGML XX KK1 LHRJFK0002Y10JUN

4. SSRASVC YY KK1 LHRJFK0456Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

5. SSRVGML XX NO1 JFKFRA0003Y20JUN

6. SSRASVC XX NO1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGERATIAN MEAL

7. SSROTHS IT SERVICE NOT AVAILABLE

PNR Updated:

RLOC: QWERTY

1TRAVELLER/AMR

1. XX001 Y 10JUN FRALHR 1000 1100

2. XX002 Y 10JUN LHRJFK 1230 1700

 OPERATED BY YY

3. XX003 Y 20JUN JFKFRA 1800 0730/1

 OPERATED BY ZZ

1. SSRVGML XX HK1 FRALHR0001Y10JUN

2. SSRASVC XX HD1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

3. SSRVGML XX HK1 LHRJFK0002Y10JUN

4. SSRASVC XX HK1 LHRJFK0456Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

6.2 Marketing Carrier uses different booking methods 

A Marketing Carrier may decide using different booking methods for the same type of service; 

one booking method for its Prime Flights and one booking method for those flights operated by 

another carrier. In the following examples member XX filed its own booking method for Prime 

Flights only, the booking method of member YY for XX Flights operated by YY and the booking 

method of member ZZ for XX Flights operated by ZZ.

PNR Booking Source (System Provider 1T):

RLOC: QWERTY

1TRAVELLER/AMR

1. XX001 Y 10JUN FRALHR 1000 1100

2. XX002 Y 10JUN LHRJFK 1230 1700

 OPERATED BY YY

3. XX003 Y 20JUN JFKFRA 1800 0730/1

 OPERATED BY ZZ

1. SSRVGML XX HN1 FRALHR0001Y10JUN

2. SSRASVC XX HN1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

3. SSRPDML XX HN1 LHRJFK0002Y10JUN.G/0AN//VEGETARIAN MEAL

4. SSRASVC XX HN1 LHRJFK0456Y10JUN.G/0AN/PDML/VEGETARIAN MEAL

5. SSRASVC XX HN1 JFKFRA0003Y20JUN.G/0AN//VEGERATIAN MEAL
Example 2 – Message from the booking source to the member XX requesting the service for all 

segments using different booking methods for the same member.

HDQRMXX

.HDQRM1T

HDQ1T QWERTY/ABC/56736467/PAR/1T/T/FR

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX NN1 FRALHR0001Y10JUN

SSRASVC XX NN1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

SSRPDML XX NN1 LHRJFK0002Y10JUN.G/0AN//VEGETARIAN MEAL

SSRASVC XX NN1 LHRJFK0002Y10JUN.G/0AN/PDML/VEGETARIAN MEAL

SSRASVC XX NN1 JFKFRA0003Y20JUN.G/0AN//VEGETARIAN MEAL

Example 2(a) – Message from the member XX to the booking source confirming the service on 

the XX Prime Flight; EMD required.

HDQRM1T

.HDQRMXX

HDQ1T QWERTY

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX KK1 FRALHR0001Y10JUN

SSRASVC XX KD1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

Example 2(b) – Message from member XX to member YY requesting the service (Code Share 

Option 5). The booking method of member YY is applicable.

HDQRMYY

.HDQRMXX

HDQXX 6BDFH8

HDQ1T QWERTY/ABC/56736467/PAR/1T/T/FR

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1/1000 1100

YY0456 Y 10JUN LHRJFK HK1-XX002Y

SSRPDML YY NN1 LHRJFK0456Y10JUN.G/0AN//VEGETARIAN MEAL

SSRASVC YY NN1 LHRJFK0456Y10JUN.G/0AN/PDML/VEGETARIAN MEAL

Example 2(c) – Message from member XX to member ZZ requesting the service (Code Share 

Option 2). The booking method of member ZZ is applicable.

HDQRMZZ

.HDQRMXX

HDQ1T QWERTY/ABC/56736467/PAR/1T/T/FR

HDQXX 6BDFH8

1TRAVELLER/AMR

XX0002 Y 10JUN LHRJFK HK1/1230 1700

XX0003 Y 20JUN JFKFRA CH1

SSRASVC XX NN1 JFKFRA0003Y20JUN.G/0AN//VEGETARIAN MEAL
Example 2(d) - Message from member YY to member XX confirming the service; no EMD 

required.

HDQRMXX

.HDQRMYY

HDQXX 6BDFH8

1TRAVELLER/AMR

YY0456 Y 10JUN LHRJFK HK1-XX002Y

SSRPDML YY KK1 LHRJFK0456Y10JUN.G/0AN//VEGETARIAN MEAL

SSRASVC YY KK1 LHRJFK0456Y10JUN.G/0AN/PDML/VEGETARIAN MEAL

Example 2(e) – Message from member ZZ to member XX denying the request.

HDQRMXX

.HDQRMZZ

HDQXX 6BDFH8

1TRAVELLER/AMR

XX0003 Y 20JUN JFKFRA CH1

SSRASVC XX NO1 JFKFRA0003Y20JUN.G/0AN//VEGETARIAN MEAL

SSROTHS XX SERVICE NOT AVAILABLE

Example 2(f) – Message from the member XX to the booking source, confirming the service for 

XX operated by YY; no EMD required.

HDQRMIT

.HDQRMXX

HDQ1T QWERTY

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRPDML XX KK1 LHRJFK0002Y10JUN.G/0AN//VEGETARIAN MEAL

SSRASVC XX KK1 LHRJFK0002Y10JUN.G/0AN/PDML/VEGETARIAN MEAL

Example 2(g) – Message from the member XX to the booking source, denying the request for 

XX operated by ZZ.

HDQRMIT

.HDQRMXX

HDQ1T QWERTY

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRASVC XX NO1 JFKFRA0003Y20JUN.G/0AN//VEGETARIAN MEAL

SSROTHS IT SERVICE NOT AVAILABLE
PNR Booking Source

Message processed:

RLOC: QWERTY

1TRAVELLER/AMR

1. XX001 Y 10JUN FRALHR 1000 1100

2. XX002 Y 10JUN LHRJFK 1230 1700

 OPERATED BY YY

3. XX003 Y 20JUN JFKFRA 1800 0730/1

 OPERATED BY ZZ

1. SSRVGML XX KK1 FRALHR0001Y10JUN

2. SSRASVC XX KD1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

3. SSRPDML XX KK1 LHRJFK0002Y10JUN.G/0AN//VEGETARIAN MEAL

4. SSRASVC XX KK1 LHRJFK0456Y10JUN.G/0AN/PDML/VEGETARIAN MEAL

5. SSRASVC XX NO1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGERATIAN MEAL

6. SSROTHS IT SERVICE NOT AVAILABLE

PNR updated:

RLOC: QWERTY

1TRAVELLER/AMR

1. XX001 Y 10JUN FRALHR 1000 1100

2. XX002 Y 10JUN LHRJFK 1230 1700

 OPERATED BY YY

3. XX003 Y 20JUN JFKFRA 1800 0730/1

 OPERATED BY ZZ

1. SSRVGML XX HK1 FRALHR0001Y10JUN

2. SSRASVC XX HD1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

3. SSRPDML XX HK1 LHRJFK0002Y10JUN.G/0AN//VEGETARIAN MEAL

4. SSRASVC XX HK1 LHRJFK0456Y10JUN.G/0AN/PDML/VEGETARIAN MEAL

6.3 Marketing Carrier uses a single booking method

A Marketing Carrier may decide using a single booking method for all its flights no matter who 

the Operating Carrier is. The Operating Carrier(s) may have a different booking method than the 

Marketing Carrier. It is the responsibility of the Marketing Carrier to forward the applicable 

booking method to the Operating Carrier although a different booking method was received from 

the booking source.

PNR Booking Source (System Provider 1T):

RLOC: QWERTY

1TRAVELLER/AMR

1. XX001 Y 10JUN FRALHR 1000 1100

2. XX002 Y 10JUN LHRJFK 1230 1700

 OPERATED BY YY

3. XX003 Y 20JUN JFKFRA 1800 0730/1

 OPERATED BY ZZ

1. SSRVGML XX NN1 FRALHR0001Y10JUN

2. SSRASVC XX NN1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

3. SSRVGML XX NN1 LHRJFK0002Y10JUN

4. SSRASVC XX NN1 LHRJFK0456Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

5. SSRVGML XX NN1 JFKFRA0003Y20JUN

6. SSRASVC XX NN1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGERATIAN MEAL
Example 3 – Message from the booking source to the member XX requesting the service for all 

segments; a single booking method for all segments.

HDQRMXX

.HDQRM1T

HDQ1T QWERTY/ABC/56736467/PAR/1T/T/FR

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX NN1 FRALHR0001Y10JUN

SSRASVC XX NN1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

SSRVGML XX NN1 LHRJFK0002Y10JUN

SSRASVC XX NN1 LHRJFK0002Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

SSRVGML XX NN1 JFKFRA0003Y20JUN

SSRASVC XX NN1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGETARIAN MEAL

Example 3(a) – Message from the member XX to the booking source confirming the service on 

the XX Prime Flight; EMD required.

HDQRM1T

.HDQRMXX

HDQ1T QWERTY

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX KK1 FRALHR0001Y10JUN

SSRASVC XX KD1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

Example 3(b) – Message from member XX to member YY requesting the service (Code Share 

Option 5). The SSR VGML as received from the booking source is replaced by an SSR PDML. 

The VGML reference of the SSR ASVC is replaced by PDML.

HDQRMYY

.HDQRMXX

HDQXX 6BDFH8

HDQ1T QWERTY/ABC/56736467/PAR/1T/T/FR

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1/1000 1100

YY0456 Y 10JUN LHRJFK HK1-XX002Y

SSRPDML YY NN1 LHRJFK0456Y10JUN.G/0AN//VEGETARIAN MEAL

SSRASVC YY NN1 LHRJFK0456Y10JUN.G/0AN/PDML/VEGETARIAN MEAL

Example 3(c) – Message from member XX to member ZZ requesting the service (Code Share 

Option 2). The SSR VGML as received from the booking source is not included. The VGML 

reference of the SSR ASVC is removed.

HDQRMZZ

.HDQRMXX

HDQ1T QWERTY/ABC/56736467/PAR/1T/T/FR

HDQXX 6BDFH8

1TRAVELLER/AMR

XX0002 Y 10JUN LHRJFK HK1/1230 1700

XX0003 Y 20JUN JFKFRA CH1

SSRASVC XX NN1 JFKFRA0003Y20JUN.G/0AN//VEGETARIAN MEAL
Example 3(d) - Message from member YY to member XX confirming the service; no EMD 

required.

HDQRMXX

.HDQRMYY

HDQXX 6BDFH8

1TRAVELLER/AMR

YY0456 Y 10JUN LHRJFK HK1-XX002Y

SSRPDML YY KK1 LHRJFK0456Y10JUN.G/0AN//VEGETARIAN MEAL

SSRASVC YY KK1 LHRJFK0456Y10JUN.G/0AN/PDML/VEGETARIAN MEAL

Example 3(e) – Message from member ZZ to member XX denying the request.

HDQRMXX

.HDQRMZZ

HDQXX 6BDFH8

1TRAVELLER/AMR

XX0003 Y 20JUN JFKFRA CH1

SSRASVC XX NO1 JFKFRA0003Y20JUN.G/0AN//VEGETARIAN MEAL

SSROTHS XX SERVICE NOT AVAILABLE

Example 3(f) – Message from the member XX to the booking source, confirming the service for 

XX operated by YY. The SSR PDML as received from member YY is replaced by an SSR 

VGML as originally received from the booking source, the PDML reference of the SSR ASVC is 

replaced by VGML.

HDQRMIT

.HDQRMXX

HDQ1T QWERTY

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX KK1 LHRJFK0002Y10JUN

SSRASVC XX KK1 LHRJFK0002Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

Example 3(g) – Message from the member XX to the booking source, denying the request for 

XX operated by ZZ. The SSR VGML is included in the message as originally received from the 

booking source. The VGML reference of the SSR ASVC is added.

HDQRMIT

.HDQRMXX

HDQ1T QWERTY

1TRAVELLER/AMR

XX0001 Y 10JUN FRALHR HK1

XX0002 Y 10JUN LHRJFK HK1

XX0003 Y 20JUN JFKFRA HK1

SSRVGML XX NO1 JFKFRA0003Y20JUN

SSRASVC XX NO1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGETARIAN MEAL

SSROTHS IT SERVICE NOT AVAILABLE
PNR Booking Source

Message processed:

RLOC: QWERTY

1TRAVELLER/AMR

1. XX001 Y 10JUN FRALHR 1000 1100

2. XX002 Y 10JUN LHRJFK 1230 1700

 OPERATED BY YY

3. XX003 Y 20JUN JFKFRA 1800 0730/1

 OPERATED BY ZZ

1. SSRVGML XX KK1 FRALHR0001Y10JUN

2. SSRASVC XX KD1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

3. SSRVGML XX KK1 LHRJFK0002Y10JUN

4. SSRASVC XX KK1 LHRJFK0456Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

5. SSRVGML XX NO1 JFKFRA0003Y20JUN

6. SSRASVC XX NO1 JFKFRA0003Y20JUN.G/0AN/VGML/VEGERATIAN MEAL

7. SSROTHS IT SERVICE NOT AVAILABLE

PNR updated:

RLOC: QWERTY

1TRAVELLER/AMR

1. XX001 Y 10JUN FRALHR 1000 1100

2. XX002 Y 10JUN LHRJFK 1230 1700

 OPERATED BY YY

3. XX003 Y 20JUN JFKFRA 1800 0730/1

 OPERATED BY ZZ

1. SSRVGML XX HK1 FRALHR0001Y10JUN

2. SSRASVC XX HD1 FRALHR0001Y10JUN.G/0AN/VGML/VEGETARIAN MEAL

3. SSRVGML XX HK1 LHRJFK0002Y10JUN

4. SSRASVC XX HK1 LHRJFK0456Y10JUN.G/0AN/VGML/VEGETARIAN MEAL
7. CHANGE OF GAUGE FLIGHTS (CHANGE OF EQUIPMENT EN ROUTE)

Change of Gauge means a scheduled change of aircraft, occurring one or more times en route, 

but identified by one airline designator/flight number between the station of origin and the station 

of destination. 

The passenger’s itinerary will reflect one flight segment for two actual legs of travel; two seat 

assignments, etc. for one flight number. Some RES/DCS may print the multiple flight 

information on a single boarding pass due to the single flight number. 

Requests on Change of Gauge (CoG) flights may be shown as single or multiple SSR elements 

depending on the requester’s knowledge of the flight routing and aircraft used.

7.1 SSR ASVC in Conjunction with a Standard SSR Code

Example 1 - Message from booking source to the Member requesting a vegetarian meal for 

segment MIA-NRT. 

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

2STARK/ARYA/SANSA

AA0061Y20JUN MIANRT HK2

SSR VGML AA NN1 MIANRT0061Y20JUN-1STARK/ARYA

SSR ASVC AA NN1 MIANRT0061Y20JUN-1STARK/ARYA.G/0AN/VGML/VEGETARIAN 

SSR ASVC AA ///MEAL

Example 1(a) - Message from the Member to the booking source confirming the service for both 

legs MIA-DFW and DFW-NRT; no EMD required.

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

2STARK/ARYA/SANSA

AA61Y20JUN MIANRT HK2

SSR VGML AA KK1 MIADFW0061Y20JUN-1STARK/ARYA

SSR ASVC AA KK1 MIADFW0061Y20JUN-1STARK.ARYA.G/0AN/VGML/VEGETARIAN

SSR ASVC AA ///MEAL

SSR VGML AA KK1 DFWNRT0061Y20JUN-1STARK/ARYA

SSR ASVC AA KK1 DFWNRT0061Y20JUN-1STARK/ARYA.G/0AN/VGML/VEGEATRIAN

SSR ASVC AA ///MEAL

Example 1(b) - Message from the Member to the booking source confirming the service for 

both legs MIA-DFW and DFW-NRT; EMD required.

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

2STARK/ARYA/SANSA

AA0061Y20JUN MIANRT HK2

SSR VGML AA KK1 MIADFW0061Y20JUN-1STARK/ARYA

SSR ASVC AA KD1 MIADFW0061Y20JUN-1STARK/ARYA.G/0AN/VGML/VEGETARIAN 

SSR ASVC AA ///MEAL

SSR VGML AA KK1 DFWNRT0061Y20JUN-1STARK/ARYA

SSR ASVC AA KD1 DFWNRT0061Y20JUN-1STARK/ARYA.G/0AN/VGML/VEGETARIAN 

SSR ASVC AA ///MEAL
Example 2 - Message from the booking source to the Member requesting different types of 

seats for legs MIA-DFW and DFW-NRT.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1CUMBERBATCH/BENEDICT

AA0061Y20JUN MIANRT HK1

SSR NSSA AA NN1 MIADFW0061Y20JUN.CA

SSR ASVC AA NN1 MIADFW0061Y20JUN.H/S23/NSSA/CHARGEABLE SEAT

SSR NSSW AA NN1 DFWNRT0061Y20JUN.CW

SSR ASVC AA NN1 DFWNRT0061Y20JUN.H/S23/NSSW/CHARGEABLE SEAT

Example 2(a) – Message from the Member to the booking source confirming the seats for both 

legs MIA-DFW and DFW-NRT; EMD required.

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

1CUMBERBATCH/BENEDICT

AA0061Y20JUN MIANRT HK1

SSR NSSA AA KK1 MIADFW0061Y20JUN.15FNCA

SSR ASVC AA KD1 MIADFW0061Y20JUN.H/S23/NSSA/CHARGEABLE SEAT

SSR NSSW AA KK1 DFWNRT0061Y20JUN.30ANCW

SSR ASVC AA KD1 DFWNRT0061Y20JUN.H/S23/NSSW/CHARGEABLE SEAT

Example 2(b) – Message from the booking source to the Member advising the EMD number for 

both legs MIA-DFW and DFW-NRT; a multi coupon EMD was issued.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1CUMBERBATCH/BENEDICT

AA0061Y20JUN MIANRT HK1

SSR ASVC AA HS1 MIADFW0061Y20JUN.H/S23/SEAT/CHARGEABLE/

SSR ASVC AA ///SEAT/A/001012345678C1

SSR ASVC AA HS1 DFWNRT0061Y20JUN.H/S23/SEAT/CHARGEABLE/

SSR ASVC AA ///SEAT/A/001012345678C2

Example 3 – Message from the booking source to the Member requesting a pet in cabin for leg 

MIA-DFW only.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1DELRAY/LANA 

AA0061Y20JUN MIANRT HK1

SSR PETC AA NN1 MIADFW0061Y20JUN

SSR ASVC AA NN1 MIADFW0061Y20JUN.C/OMN/PETC/PET IN CABIN
Example 3(a) – Message from the member to the bookings source confirming the service for 

leg MIA-DFW; EMD required.

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

1DELRAY/LANA

AA0061Y20JUN MIANRT HK1

SSR PETC AA KK1 MIADFW0061Y20JUN

SSR ASVC AA KD1 MIADFW0061Y20JUN.C/OMN/PETC/PET IN CABIN

7.2 SSR ASVC in conjunction with a Chargeable Family SSR

When no standard SSR code exist, or when the Member choses to distinguish between 

products, a chargeable SSR family code can be used to request services as an alternative to 

creating a new SSR for a chargeable service.

When a standard SSR is sent from the booking source to the member, the booking source may 

not always be aware the service is chargeable. Therefore standard SSR codes may be sent 

without an SSR ASVC in conjunction with the standard SSR. The PDxx SSR codes are always 

chargeable.

Example 1 – Message from the booking source to the Member requesting a vegetarian meal for 

segment MIA-NRT

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1TENNANT/DAVID

AA0061B20JUN MIANRT HK1

SSR PDML AA NN1 MIANRT0061B20JUN.G/0AN//VEGETARIAN DINNER

SSR ASVC AA NN1 MIANRT0061B20JUN.G/0AN/PDML/VEGETARIAN DINNER

Example 1(a) – Message from the member to the booking source confirming the service for 

segment MIA-NRT; EMD required.

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

1TENNANT/DAVID

AA0061B20JUN MIANRT HK1

SSR PDML AA KK1 MIANRT0061B20JUN.G/0AN//VEGETARIAN DINNER

SSR ASVC AA KD1 MIANRT0061B20JUN.G/0AN/PDML/VEGETARIAN DINNER

Example 1(b) – Message from the booking source to the Member advising the EMD number for 

segment MIA-NRT.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1TENNANT/DAVID

AA0061B20JUN MIANRT HK1

SSR ASVC AA HS1 MIANRT0061B20JUN.G/0AN/PDML/VEGETARIAN/

SSR ASVC AA ///DINNER/A/0010716875309C1
Example 2 – Message from the booking source to the Member requesting in-flight 

entertainment for leg MIA-DFW and lounge access for leg DFW-NRT.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1CUMBERBATCH/BENEDICT 1WATSON/EMMA

AA0061Y20JUN MIANRT HK2

SSR PDIE AA NN2 MIADFW0061Y20JUN.G/020//INFLIGHT ENTERTAINMENT

SSR ASVC AA NN2 MIADFW0061Y20JUN.G/020/PDIE/INFLIGHT ENTERTAINMENT

SSR PDLG AA NN2 DFWNRT0061Y20JUN.E/0BX//LOUNGE ACCESS

SSR ASVC AA NN2 DFWNRT0061Y20JUN.E/0BX/PDLG/LOUNGE ACCESS

Example 2(a) – Message from the Member to the booking source confirming the services on 

both legs; EMD required.

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

1CUMBERBATCH/BENEDICT 1WATSON/EMMA

AA0061Y20JUN MIANRT HK2

SSR PDIE AA KK2 MIADFW0061Y20JUN.G/020//INFLIGHT ENTERTAINMENT

SSR ASVC AA KD2 MIADFW0061Y20JUN.G/020/PDIE/INFLIGHT ENTERTAINMENT

SSR PDLG AA KK2 DFWNRT0061Y20JUN.E/0BX//LOUNGE ACCESS

SSR ASVC AA KD2 DFWNRT0061Y20JUN.E/0BX/PDLG/LOUNGE ACCESS

Example 2(b) – Message from the booking source to the Member advising the EMD numbers 

for both legs.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1CUMBERBATCH/BENEDICT 1WATSON/EMMA

AA0061Y20JUN MIANRT HK2

SSR ASVC AA HS1 MIADFW0061Y20JUN-1CUMBERBATCH/BENEDICT.G/020/PDIE/INFLIGHT

SSR ASVC AA ///ENTERTAINMENT/A/0010716875309C1

SSR ASVC AA HS1 MIADFW0061Y20JUN-1WATSON/EMMA.G/020/PDIE/INFLIGHT

SSR ASVC AA ///ENTERTAINMENT/A/0010716875310C1

SSR ASVC AA HS1 DFWNRT0061B20JUN-1CUMBERBATCH/BENEDICT.E/0BX/PDLG/

SSR ASVC AA ///LOUNGE ACCESS/A/0070716875309C2

SSR ASVC AA HS1 DFWNRT0061B20JUN-1WATSON/EMMA.E/0BX/PDLG/LOUNGE ACCESS

SSR ASVC AA ///A/0010716875310C2

Example 3 – Message from the booking source to the Member requesting a pet in cabin for leg 

MIA-DFW only.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1DELRAY/LANA

AA0061Y20JUN MIANRT HK1

SSR PDPC AA NN1 MIADFW0061Y20JUN.C/OBT//PET IN CABIN

SSR ASVC AA NN1 MIADFW0061Y20JUN.C/OBT/PDPC/PET IN CABIN
Example 3(a) – Message from the member to the booking source confirming the service; EMD 

required.

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

1DELRAY/LANA

AA0061Y20JUN MIANRT HK1

SSR PDPC AA KK1 MIADFW0061Y20JUN.C/OBT//PET IN CABIN

SSR ASVC AA KD1 MIADFW0061Y20JUN.C/OBT/PDPC/PET IN CABIN

7.3 Stand-Alone SSR ASVC

If no standard SSR or chargeable family SSR code is available for requesting a service, 

Member may use an SSR ASVC for both requesting the service and advising the EMD number 

and type.

Example 1 – Message from the booking source to the Member requesting internet access for 

segment MIA-NRT.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1FINCH/HOWARD

AA0061B20JUN MIANRT HK1

SSR ASVC AA NN1 MIANRT0061B20JUN.G/0CL//INTERNET ACCESS

Example 1(a) – Message from the Member to the booking source confirming the service for 

segment MIA-NRT.

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

1FINCH/HOWARD

AA0061B20JUN MIANRT HK1

SSR ASVC AA KD1 MIANRT0061B20JUN.G/0CL//INTERNET ACCESS

Example 2 – Message from the booking source to the Member requesting a seafood meal for 

leg MIA-DFW and a Japanese meal for leg DFW-NRT

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1REESE/JOHN

AA0061B20JUN MIANRT HK1

SSR ASVC AA NN1 MIADFW0061B20JUN.G/0LD//SEAFOOD MEAL

SSR ASVC AA NN1 DFWNRT0061B20JUN.G/01F//JAPANESE MEAL
Example 2(a) – Message from the Member to the booking source confirming the service for 

both legs; EMD required.

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

1REESE/JOHN

AA0061B20JUN MIANRT HK1

SSR ASVC AA KD1 MIADFW0061B20JUN.G/0LD//SEAFOOD MEAL

SSR ASVC AA KD1 DFWNRT0061B20JUN.G/01F//JAPANESE MEAL

Example 2(b) – Message from the booking source to the Member advising the EMD number for 

both legs.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1REESE/JOHN

AA0061B20JUN MIANRT HK1

SSR ASVC AA HS1 MIADFW0061B20JUN.G/0LD//SEAFOOD MEAL/

SSR ASVC AA ///A/0010797539541C1

SSR ASVC AA HS1 DFWNRT0061B20JUN.G/01F//JAPANESE MEAL/

SSR ASVC AA ///A/0010797539541C2

Example 3 – Message from the booking source to the member requesting lounge access for leg 

MIA-DFW only.

HDQRMAA

.HDQRM1S

HDQ1S QWERTY/ABC/12345678/MIA/1S/T/US

1MURS/OLIVER

AA0061Y20JUN MIANRT HK1

SSR ASVC AA NN1 MIADFW0061Y20JUN.E/013//EXECUTIVE

SSR ASVC AA ///LOUNGE UPON ARRIVAL

Example 3(a) – Message from the member to the booking source confirming the service; EMD 

required. 

HDQRM1S

.HDQRMAA

HDQ1S QWERTY

1MURS/OLIVER

AA0061B20JUN MIANRT HK1

SSR ASVC AA KD1 MIADFW0061B20JUN.G/013//EXECUTIVE

SSR ASVC AA ///LOUNGE UPON ARRIVAL
8. SEATING

8.1 Interactively Confirmed Seats

Seats can be requested/reserved though either Type B or Type A. A Service Provider may have 

an agreement with the member for Seat Map Display (SMPREQ/RES) only or also Advance 

Seat Assignment (SBPREQ/RES)

When no Advance Seat Assignment agreement exists, requesting and confirming seats follow 

the standard process where an SSR ASVC may or may not be included in the Request 

Message and where the member may include an SSR ASVC in the Reply Message although no 

SSR ASVC was included in the Request Message.

Seats are requested with an NN action code, like any other service. The member either 

confirms or denies the request. When a seat confirmation is sent by the member to the booking 

source the SSR ASVC is sent in conjunction with the seat element.

When an Advance Seat Assignment agreement does exist, the seat is interactively confirmed. 

The seat element is included in the Request Message with either a LK or DK action code. When 

the member returns an ASVC with a KD or KK advising an EMD is or is not required, the seat 

element is not included in the Reply Message.

Example 1(a) – Message from the booking source to the member requesting a seat. Both the 

SSR SEAT and the SSR ASVC in conjunction with the SSR SEAT are sent with an NN Action 

Code.

HDQRMUS

.HDQRM1S

BPR

HDQ1S QWERTY/ABC/12345678/NYC/1S/T/US

1SATO/ALBANMR

US0721Y11DEC EWRLAX HK1

US1782Y21DEC LAXEWR HK1

SSR SEAT US NN1 EWRLAX0721Y11DEC.24A/RS

SSR ASVC US NN1 EWRLAX0721Y11DEC.A/0B5/SEAT/CHARGEABLE SEAT

SSR SEAT US NN1 LAXEWR1782Y21DEC.21G/RS

SSR ASVC US NN1 LAXEWR1782Y21DEC.A/0B5/SEAT/CHARGEABLE SEAT

Example 1(b) – Message from the member to the booking source confirming the seats. An SSR 

ASVC with a KD Reply Code is sent in conjunction with the SSR SEAT; EMD required

HDQRM1S

.HDQRMUS

BPR

HDQ1S QWERTY/ABC/12345678/NYC/1S/T/US

1SATO/ALBANMR

US0721Y11DEC EWRLAX HK1

US1782Y21DEC LAXEWR HK1

SSR SEAT US KK1 EWRLAX0721Y11DEC.24AN/RS

SSR ASVC US KD1 EWRLAX0721Y11DEC.A/0B5/SEAT/CHARGEABLE SEAT

SSR SEAT US KK1 LAXEWR1782Y21DEC.21GN/RS

SSR ASVC US KD1 LAXEWR1782Y21DEC.A/0B5/SEAT/CHARGEABLE SEAT
Example 2(a) – Message from the booking source to the Member with interactively confirmed 

seats. The SSR SEAT is sent with an LK Action Code and an SSR ASVC in conjunction with the 

SSR SEAT with an NN Action Code.

HDQRMUS

.HDQRM1S

BPR

HDQ1S QWERTY/ABC/12345678/NYC/1S/T/US

1SATO/ALBANMR

US0721Y11DEC EWRLAX HK1

US1782Y21DEC LAXEWR HK1

SSR SEAT US LK1 EWRLAX0721Y11DEC.24A/RS

SSR ASVC US NN1 EWRLAX0721Y11DEC.A/0B5/SEAT/CHARGEABLE SEAT

SSR SEAT US LK1 LAXEWR1782Y21DEC.21G/RS

SSR ASVC US NN1 LAXEWR1782Y21DEC.A/0B5/SEAT/CHARGEABLE SEAT

Example 2(b) – Message from the member to the booking source advising an EMD is required. 

Since the seats are already confirmed, the SSR SEAT is not included in the Reply Message.

HDQRM1S

.HDQRMUS

BPR

HDQ1S QWERTY/ABC/12345678/NYC/1S/T/US

1SATO/ALBANMR

US0721Y11DEC EWRLAX HK1

US1782Y21DEC LAXEWR HK1

SSR ASVC US KD1 EWRLAX0721Y11DEC.A/0B5/SEAT/CHARGEABLE SEAT

SSR ASVC US KD1 LAXEWR1782Y21DEC.A/0B5/SEAT/CHARGEABLE SEAT

8.2 Involuntary Changes

During an involuntary change such as a schedule or equipment change different scenarios 

exist:

• New allocated seat is chargeable, no EMD was issued yet

• New allocated seat is chargeable, EMD was already issued

• New allocated seat is non-chargeable, no EMD was issued yet

• New allocated seat is non-chargeable, EMD was already issued

In the following examples the process as a result of an equipment change is described. The 

process as a result of a schedule change is the same with regard to the SSR elements.
8.2.1 New allocated seat is chargeable, no EMD was issued yet

In the following example Mr. Drake has a confirmed chargeable Leg Space seat. The member 

has returned an SSR ASVC with reply code KD, advising the booking source an EMD is 

required, but no EMD has been issued yet. The holding code is HD.

Booking Source PNR:

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR RQST IB HK1 MADJFK6253Y20JUN30ENWL-1DRAKE/STEVEMR

SSR ASVC IB HD1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT

Due to an equipment change, Mr. Drake is re-seated to a seat with the same facilities as the 

cancelled seat. Since no EMD was issued yet, the member advises the booking source an EMD 

is still required. Both the SSR RQST and the SSR ASVC for the cancelled seat are included in 

the Advice Message to the booking source with an UN advice code. The new allocated seat is 

advised using a KK Reply code, while the new SSR ASVC is included with a KD reply code.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR RQST IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.30ENWL

SSR ASVC IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT

SSR RQST IB KK1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.14ENWL

SSR ASVC IB KD1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT

8.2.2. New allocated seat is chargeable, EMD was already issued

In the following example Mr. Drake has a confirmed chargeable Leg Space seat. The booking 

source has already issued the EMD and advised the member the EMD number using the SSR 

ASVC with an HS action code. The holding code is HI.

Booking Source PNR:

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR RQST IB HK1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.30ENWL

SSR ASVC IB HI1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT/A/1291298123456C1

Due to an equipment change, Mr. Drake is re-seated to a seat with the same facilities as the 

cancelled seat. Since the EMD was already issued, members may respond differently.
8.2.2.1 SSR ASVC KD sent in conjunction with the seat element

The member advises the booking source an EMD is required and ignores the fact an EMD was 

already issued. The booking source may use the same EMD or issue a new EMD and resends 

the SSR ASVC with a HS action code with either the same or a different EMD number.

Example 1 – Message from the member to the booking source advising the passenger has 

been re-seated and an EMD is required for the new seat.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR RQST IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.30ENWL

SSR ASVC IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT

SSR RQST IB KK1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.14ENWL

SSR ASVC IB KD1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT

Example 1(a) – Message from the booking source to the member advising the EMD number. 

The booking source is capable of using the previous issued EMD and the same EMD number is 

included in the Request Message.

MADRMIB

. MUCRM1A

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HS1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT/A/1291298123456C1

Example 1(b) – Message from the booking source to the member advising the EMD number. 

The booking source is not capable of using the previous issued EMD and a new EMD is issued. 

The new EMD number is included in the Request Message.

MADRMIB

. MUCRM1A

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR ASVC IB HS1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT/A/1291298129831C1
8.2.2.2 SSR ASVC SD sent in conjunction with the seat element

The member advises the booking source the same EMD is used for the new allocated seat. The 

SSR ASVC is included in the Advice Message with an SD advice code, including the number of 

the previously issued EMD.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR RQST IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.30ENWL

SSR ASVC IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT/A/1291298123456C1

SSR RQST IB KK1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.14ENWL

SSR ASVC IB SD1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT//1291298123456C1

8.2.3 New allocated seat is non-chargeable, no EMD was issued yet

In the following example Mr. Drake has a confirmed chargeable Leg Space seat. The member 

has returned an SSR ASVC with reply code KD, advising the booking source an EMD is 

required, but no EMD has been issued yet. The holding code is HD.

Booking Source PNR:

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR RQST IB HK1 MADJFK6253Y20JUN30ENWL-1DRAKE/STEVEMR

SSR ASVC IB HD1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT

Due to an equipment change, Mr. Drake is re-seated to a non-chargeable seat with different 

facilities. Since the ASVC associated to the original seat is sent with an UN advice code, it is not 

necessary to include an ASVC with a KK reply code in conjunction with the new seat since the 

seat is no longer a chargeable service.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR RQST IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.30ENWL

SSR ASVC IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT/A/1291298123456C1

SSR RQST IB KK1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.21CNA
8.2.4 New allocated seat is non-chargeable, EMD was already issued

In the following example Mr. Drake has a confirmed chargeable Leg Space seat. The booking 

source has already issued the EMD and advised the member the EMD number using the SSR 

ASVC with an HS action code. The holding code is HI.

Booking Source PNR:

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR RQST IB HK1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.30ENWL

SSR ASVC IB HI1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT/A/1291298123456C1

Due to an equipment change, Mr. Drake is re-seated to a non-chargeable seat with different 

facilities. Although an EMD was already issued the message sent by the member to the booking 

source is the same message when no EMD had been issued.

MUCRM1A

.MADRMIB

MUC1A XAG5TY

1DRAKE/STEVEMR 1JACOBS/RICKMR

IB6253Y20JUN MADJFK HK2

SSR RQST IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.30ENWL

SSR ASVC IB UN1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.A/0B5/RQST/PRE-RESERVED

SSR ASVC IB ///SEAT ASSIGNMENT/A/1291298123456C1

SSR RQST IB KK1 MADJFK6253Y20JUN-1DRAKE/STEVEMR.21CNA

9. ADVISING THE EMD NUMBER WITHOUT REQUESTING A SERVICE

When a service does not need to be requested from the member, booking source can advise 

the EMD number that has been issued with the HS advice code. These services are mainly 

under RFIC D, Financial Impact, and are issued from an auxiliary service element (SVC). These 

are for example change fee and group deposit.

Example 1 - Message from the booking source to the Member advising an EMD has been 

issued for a Group Deposit for which no previous request was sent. 

HDQRMAY

.MUCRM1A

MUC1A 2GLYIP/HEL2T2087/5627364/HEL/1A/T/FI

20SANTASELVES

AY1234Y24DEC HELRVN HN20

AY1235Y25DEC RVNHEL HN20

SVC AY HS1 HEL 24DEC/D/997/GROUP DEPOSIT/NM-20SANTASELVES

/1058201141540C1.GROUP DEPOSIT EUR500

Filing Period: Effective Date:

11 June 2015 12 June 201511June 

2015
M5.1

RESOLUTION 1791d

Payment Card Industry Data Security Standards (PCI DSS) Compliance

(amending)

PSC(34 36) 1719d 1791d Expiry: Indefinite

Type: B

RECOMMENDED that:

Member Airlines and/or Ticket System Providers (TSPs) may use the following 

guidelines to enable compliance with the requirements of the Payment Card Industry 

Data Security Standards (PCI DSS) whenever a payment card number is present as a 

Form of Identification (FOID), Form of Payment (FOP) and/or Ttransmitted in industry 

messages. 

OBJECTIVES 

1. GENERAL 

The Ppayment Card Industry has mandated that since 2008, all entities that process, 

store or transmit payment card data shall comply with the PCI DSS. PCI DSS protects 

customer's personal data, reduces the risk of compromise of card for fraudulent usage, 

secures business reputation and removes the risk of fines and fees due to noncompliance in the event of a card data compromise. 

This Recommended Practice recognizes that full payment card data is used for a variety 

of functions, such as payment for air transport and associated services (e.g. excess 

baggage, upgrades). Payment cards are also used to facilitate check-in and other 

processes, whilst acknowledging that while the presence of this information in readable 

or coded format may not be PCI DSS compliant. This Recommended Practice details 

the recommendations to be followed to ensure PCI DSS compliance, whilst continuing 

to support business needs. 

1.1 Scope 

This Recommended Practice (RP) recognizes that a standardized method for 

processing, storing and transmitting of payment card data is required to enable the 

business processes and at the same time protect the integrity of payment card data. It is 

suggested that, to meet PCI DSS requirements, in non-payment-related messages, only 

truncated or masked card numbers should be used. 
Non-adherence to PCI DSS by one Member sending payment card data to another 

Member in a non PCI DSS compliant way will nullify the PCI DSS efforts undertaken by 

the latter. 

1.2 Guiding Principles 

When accepting cards as a method of payment, card numbers need to be handled in 

order to perform certain business processes. However, the following guiding principles 

should be integrated in these processes. Well documented and enforced handling 

procedures must be in place. 

Guiding principles are: 

•To remove altogether from an airline IT infrastructure the presence of full card numbers 

by outsourcing processing to a PCI DSS compliant Payment Service Provider (PSP), or 

to replace such card numbers with tokens that have no intrinsic value. The International 

Card Schemes publish lists of PCI DSS compliant PSPs on their websites. 

•To limit handling of card numbers as much as possible, by outsourcing processes to a 

PCI DSS compliant PSP. 

•To secure card numbers whenever stored or transmitted (PCI DSS provides guidelines 

on how to achieve this). 

•To limit access to card numbers on a ‘need to know’ basis and ensure proper access 

control are in place (e.g. accessible only with passwords). 

2. DEFINITIONS 

For the purpose of this Recommended Practice, the following definitions will apply:

Payment Card Industry means American Express, Discover/Diners, MasterCard 

Worldwide, Visa International and JCB(1). 

PCI DSS (Payment Card Industry Data Security Standards) means the requirements 

issued and periodically updated by the PCI SSC (Payment Card Industry Security 

Standard Council). They can be found at 

https://www.pcisecuritystandards.org/index.shtml. For the purposes of this 

Recommended Practice, PCI DSS includes also the requirements issued by the Council 

under PTS (PIN Transaction Security) and PA DSS (Payment Application DSS) if 

applicable. 
Payment Card Data means card data embossed or printed on the card and included in 

the magnetic stripe and/or in the chip. 

Primary Account Number (PAN) means is otherwise known as the card number. 

3. METHODOLOGIES FOR PCI DSS COMPLIANCE 

3.1 General 

In accordance with PCI DSS requirements, masking is demanded when the PAN is 

displayed. Truncation is one of several options specified to meet PCI DSS requirements 

to ‘render the PAN unreadable...’. Masking and truncation are both methods of 

rendering the full PAN unreadable by removing or replacing a segment of the full PAN. 

Note: PCI SSC states that: ‘This requirement does not apply to employees and other 

parties with a legitimate business need to see the full PAN.’

3.2 Masking :

3.2.1 Masking applies to PANs that are displayed (for example, on paper receipts, 

reports, or computer screens). 

3.2.2 Even if a PAN is masked when displayed, the full PAN may still be electronically 

stored and would need to be protected in accordance with PCI DSS requirements to be 

encrypted, truncated, or hashed. 

3.2.3 PCI DSS requirements specify that when card data is masked for display, a 

maximum of the first six and last four digits (1234 56XX XXXX 7890) can be displayed. 

3.3 Truncation:

Truncation applies to PANs that are electronically stored.

3.3.1 When truncating is used, a maximum of the first six and last four digits should be 

stored after truncation. If an entity cannot meet the ’first 6 last 4‘ rule, and needs to 

store, for example, 8+0 (1234 5678 XXXX XXXX), and therefore is not able to use 

truncation to meet the PCI DSS requirements, then it shall use encryption, hashing or 

compensating controls to protect that stored data. 
3.4 One-way hashing:

3.4.1 A hash is intended to be irreversible by taking a variable-length input and 

producing a fixed-length string of cipher text. 

3.4.2 As the PAN has been ‘replaced’, it should be considered out of scope in the same 

manner a receipt of truncated PANs is are out of scope for PCI compliance. 

3.4.3 PCI DSS requirements state that the hash must be strong and one-way. This 

implies that the algorithm must use strong cryptography (e.g. collisions would not occur 

frequently) and that the hash cannot be recovered or easily determined during an 

attack. 

4. RESERVATIONS 

To comply with PCI DSS specifications, whenever a credit card is used as a FOID, it 

must be truncated. Truncated means only the first 6 and last 4 digits may be transmitted 

in clear text and each of the remaining numbers is replaced by an ‘X’. 

Type A and B messages used to perform authorization traffic require the presence of 

the full card number and fall into the scope of the PCI DSS compliance of each eTSP.

5. TICKETING 

5.1 Form of Payment (FoP) 

Where a payment card is used as a Fform of Ppayment, ticketing resolutions stipulates 

that the ‘form of payment’ data entered on the ticket, miscellaneous documents, excess 

baggage tickets and/or the passenger itinerary receipt shall 

be replaced with the letter X with the exception of the last four digits in accordance with 

the provisions of Resolution 728 (i.e. XXXX XXXX XXXX 1234). 

Note: 

This exceeds the requirements of PCI DSS and in the United States the requirements of 

the Fair_and_ Accurate_ Credit_ Transactions_ Act (FACTA) which prohibits

businesses from printing more than 5 digits of any customer's card number or card 

expiration date on any receipt provided to the cardholder at the point of sale or 

transaction.
5.2 Form of Identification (FOID) 

Where a payment card is used as a Form of Identification (FOID) in electronic tickets, 

the FOID shall include only the first 6 and the last 4 digits of the payment card number. 

All remaining digits shall be replaced with an X. E.G. VI1234 56XX XXXX 7890. 

Messages related to FOID will no longer pollute airline systems with full card data. 

Airlines using card number as FOID will still be able to do so, since amasked/truncated 

number is not considered a “payment card” number for the purpose of PCI DSS 

compliance. 

5.3 Unstructured free-format text zone

It is strictly forbidden to enter a full card number in any unstructured free-format text 

zone of a message, as it is impossible for the message recipient to spot this and 

address this PCI DSS violation.

6. AIRPORT PROCESS 

6.1 All payment card data that is read and transmitted by Common Use Self Service 

kiosks (CUSS) and Common Use Passenger Processing Systems (CUPPS) when used 

for FOID purposes shall be truncated in accordance with the provisions of paragraph 

3.3. 

6.2 Applications that still need the complete PAN for payment shall be modified to 

access this data by requesting the card to be re-presented to a secure and certified card 

payment module. 

7. BSP (Billing and Settlement Plan) Processes 

7.1 Airline Billing Analysis reports are sent by default with masked card numbers (1234 

56XX XXXX 7890). Such reports are not meant to be used for card payment 

processing. 

7.2 Airline Accounting/Sales Data (formerly Hand Off Tapes, (HOT) files distributed to 

airlines, continue to be sent by default with card numbers shown in full in order to allow 

those airlines who process their card transactions in-house to continue do so. 
7.3 BSPlink consultation of transaction history does not allow accessing the full card 

number; only a masked version is displayed on screen. 

7.4 BSPlink refund requests initiated by Travel Agents have the card number data field 

‘auto-populated’ from the BSPlink database, thus removing the risk of typing mistake 

while guaranteeing the integrity of the link with the original purchase. This also removes 

the need for the Agent to conserve the original card number used to make the 

purchase. Only a masked version of the card number is visible on screen. 

7.5 Airline Impact Review 

7.5.1 Airlines are strongly advised to review their processes where the full payment 

card number needs to be present, since payment card numbers in full are only required 

for the remittance of the transactions to the acquirer. 

7.5.2 It is recommended that transaction reconciliation can be conducted with truncated 

card numbers which avoids polluting revenue accounting systems with full payment 

card numbers. Using truncated numbers will allow airlines to de-scope such system 

from the mandatory PCI DSS compliance. 

8. INTERLINING 

Airlines should ensure that payment card data, whether sent in interline ticketing or 

reservations messages for Fform of Ppayment or Fform of Iidentification, is either 

masked, truncated or hashed in order not to pollute their interline partners systems and 

thereby rendering such partners not compliant with PCI DSS. 

9. REVENUE ACCOUNTING 

Airlines should ensure that payment card data, when used in revenue accounting 

systems, is fully compliant with PCI DSS.

10. FINANCIAL SYSTEMS AND PROCESSES

Airlines should ensure that all other financial systems and processes are fully compliant 

with PCI DSS.
11. ACTION BY TRAVEL AGENTS 

Travel Agents shall ensure their full compliance with the Payment Card Industry (PCI)

Data Security Standards, as provided by the Card companies and made available to 

agents through IATA, and that all sensitive card data obtained during the process of 

completing a card sales transaction is handled, stored, and transmitted with due regard 

to the security of the data. I in accordance with the provisions of Resolution 890. 

12. ACTION BY TICKETING SYSTEM PROVIDERS (TSPs) 

In accordance with the provisions of Resolution 854 as amended at the Passenger 

Agency Conference (34) held October 2011, the following provisions shall apply: 

12.1 Provisions (The provisions of this section 12.1 become effective 01 January 

2014) as follows:-

12.1.1 That all equipment (software, hardware and transmission channels) installed and 

used in an Approved Location shall be PCI DSS compliant, 

12.1.2 That the Operation or Operations of the Electronic Ticketing Service Provider, its 

agents or service providers shall be PCI DSS compliant, 

12.1.3 That all transmission channels used by the Electronic Ticketing Service Provider, 

its agents or service providers to transmit files and reports including but not limited to 

Airlines, Data Processing Centers shall be PCI DSS compliant, 

12.1.4 That all Electronic Ticketing Systems Providers shall submit annually to IATA a 

Certificate of Compliance as described by the PCI Security Standards Council (SSC), 

13. ACTION BY GROUND HANDLERS 

Members should ensure that ground handlers, who when conducting payment card 

transactions on behalf of the airlines whose airport work stations they are manning,

should ensure that they are adequately covered by their internal PCI DSS compliance 

program. 

14. ADVANCED PASSENGER INFORMATION (API) 

Where it is required to transmit API information, the payment card number is currently 

not required.
15. Additional Information 

For additional information: 

https://www.pcisecuritystandards.org/index.php

or contact: 

pcidss@iata.org

16. SPECIFIC BSP COUNTRY ISSUES 

Italy

Italy has a local tax requirement that all sales be reported on paper. Consequently, a 

receipt of each BSP payment card transaction must be printed and forwarded to a 

service provider contracted by IATA, who sorts and dispatches the printed receipts to 

each relevant airline. The receipt printed from the ticketing system has a truncated 

payment card number in compliance with PCI DSS. 

Peru

Airlines are required to forward to tax authorities a report of their payment card sales. 

To comply with this requirement, the Data Processing Center produces a specific report 

which is forwarded to each airline or its contractor. Report R3087 has the information 

required for the declaration Sunat PDT3540. This report contains credit card numbers, 

which are partially masked/truncated (1234 56XX XXX7 8901- first 6 and last 5 are in 

the clear), and is therefore in scope for PCI DSS compliance, as PCI rules allows only 

first 6 and last 4 to be in the clear (1234 56XX XXXX 7890). This procedure falls under 

the individual PCI DSS compliance project of each airline, as the IATA BSP local office 

is not handling that procedure.

Airlines having BSP card sales in Peru are invited to ensure that this special BSP 

country activity is enclosed in their individual PCI DSS compliance project.

1: While airlines and other merchants also accept other card brands than the 5 major international card brands 

making the PCI Council, it is recommended to consider applying PCI DSS standards to all card transactions in order 

to provide a consistent level of protection to all card paying clients and not appear discriminating between them.

Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015
P8.4

RECOMMENDED PRACTICE 1797

COMMON USE PASSENGER PROCESSING SYSTEMS (CUPPS)

PSC(35 36)1797

.....

Table 1: CUPPS Foundational Principles

Principle Description

Platform Independence Differences in legacy CUTE Platforms lead to additional 

application complexities and CUTE vendor-specific 

versions that must be maintained over time. Allow airlines 

to have one application that works as expected on any 

supplier’s platform.

Business Process 

Facilitation 

CUPPS provides a flexible Platform that facilitates 

Application functionality that may be used for a variety of 

business functions.

“Minimum, Defined” CUPPS Platforms must provide the functionality defined as 

required in the CUPPS Technical Specification.

Affordability CUPPS provides the tools and technologies that may lead 

to additional economies of scale and economies of scope.

Predictability CUPPS provides enhanced predictability in terms of 

deployment and overall platform and application 

maintenance (duration, cost, etc.)

Serviceability CUPPS provides the tools and technologies to increase 

efficiencies of application upgrades and maintenance.

.....

1. Overview

This section provides an overview of the benefits of CUPPS, its strategy as a product 

and, the management oversight of the ongoing CUPPS activities, and migration 

strategies.

.....

1.3 CUPPS vs. CUTE Summary

There are many differences between the legacy CUTE environment and the new 

CUPPS forward-looking environment. Table 2 below provides a summary of the major 

differences. 
Table 2: CUTE vs. CUPPS Summary

CUTE CUPPS

Proprietary peripheral interfaces per supplier. Unified peripheral interface across suppliers.

Varying support for various peripherals and 

varying functionality provided.

Unified support for each device category with 

defined basic functionality.

Built-in AEA support including ATB-II with 

propriety supplier-specific extensions.

Elimination of proprietary device firmware in 

favor of current formats supporting barcodes; 

no ATB-II operations.

Proprietary management interfaces with 

varying levels of functionality.

Unified approach to system management, 

including remote administration capabilities.

Legacy CUTE may utilize a mixture of 

workstation operating systems and network 

protocols.

All CUPPS workstations will use a defined 

operating system and network protocol 

(including network services).

Legacy CUTE implementations provided a 

mixture of low- and high-level peripheral 

interface technologies that were largely 

incompatible and supplier-specific.

CUPPS defines a high-level interface standard 

between applications and the platform.

.....

1.4 3 CUPPS Platform Standards

.....

1.5 4 CUPPS Management Oversight

.....

1.6 CUTE to CUPPS Migration

With any next-generation standard or product, a mechanism must be provided to migrate from 

the previous standard or product to the next-generation standard.

This section provides the migration considerations for moving from CUTE to CUPPS.

Given the wide array of variations between CUTE implementations combined with the 

differences that exist due to the local business and operational scenarios at each CUTE 

location, there is no one migration strategy that is applicable across suppliers. Therefore, each 

platform provider and/or platform supplier that proposes a CUPPS solution must provide a 

reasonable and realistic migration strategy.

Table 3 shows the general considerations that each supplier’s migration strategy will likely 

address. Not every item will be applicable for a given situation nor will the list presented in 

Table 3 constitute the entire list of considerations that every site must contemplate. These 

reflect examples of major considerations.

Table 3: CUTE to CUPPS Migration Considerations

Consideration Impact

Potential operating 

system changes

For applications built on a non-supported operating system, applications 

must be ported or rewritten for the CUPPS supported operating systems.

Application changes Legacy CUTE applications must be adapted to work with the CUPPS 

platform.

Elimination of proprietary 

device firmware

Applications and business processes that rely on proprietary device firmware

must be adapted to E-Tickets and barcode technologies. Proprietary 

peripheral interfaces are eliminated in favor of a standard high-level 

interface.
CUPPS suppliers are not required to provide solutions to any or all of the considerations 

given in Table 3 nor are the suppliers prohibited from providing functionality that is 

outside of the CUPPS specification. It is understood that CUPPS suppliers will continue 

to offer solutions to customers based on mutually agreeable terms and conditions.

.....

2.1.3 Accessibility

Passengers might not be able to use shared devices at airports due to a disability. 

Consequently, legislation on accessibility should be adhered to when applicable at the 

site where the shared devices are deployed and maintained.

.....

Editor’s Note: renumber 2.1.3 to 2.1.9

.....

4. Applicable Industry Standards

CUPPS adheres to, references, and acknowledges the standards shown below.

Table 9: IATA Recommend Practices Reference

IATA A4A Title

1008 100.15 Glossary of Commonly Used Air Passenger Terms

1706 n/a Functional Specification for Standard Departure Control System

1706e 30.102 Paper Specifications Documents to be Printed by a General Purpose Printer 

(GPP) in a Common Use Self-Service (CUSS) Kiosk

1720 n/a Seat Assignment Parameters

1724 20.03 General Conditions of Carriage (Passenger and Baggage)

1740a 30.42 Form of Interline Baggage Tag

1796 30.76 Baggage System Interface

1774 n/a Protection of Privacy and Transborder Data Flows of Personal Data Used in 

International Air Transport of Passengers and Cargo

1778 n/a Corporate Client Identification Service

1784 * Electronic Reservation Services Providers (ERSPs)

1797 n/a Common Use Terminal Equipment Common Use Passenger Processing 

Systems (CUPPS)

* A4A Electronic Marketplace Committee RP

.....

5. Abbreviations and Glossary

.....

CUTE

Common Use Terminal Equipment

.....
Filing Period: Effective Date:

11May 2015 12 June 2015

11June 2015