DI and Remark lines for NDC bookings

NDC bookings create the following lines:

These lines contain information about the booking, such as price, flight information, confirmation, ticketing time limits, fees, and form of payment. Lines display in sequential order with the oldest entries at the top and the most recent entries at the bottom of the list.

The main difference among the GDSs is the indicator on the first line only. Some spacing and punctuation differences occur among the GDSs. The differences are highlighted in the examples below.

Travelport+ Example

Apollo Example

Worldspan Example

DOCI-FREE TEXT-#TAS01#REFXX/NUQFMK/USD/NDC
  2. FREE TEXT-#TAS01#OIDXX/XX001H1Y9BXA2/USD/NDC
  3. FREE TEXT-#TAS01...
TRMK-#TAS01#REFXX/NUQFMK/USD/NDC
  2 #TAS01#OIDXX/XX001H1Y9BXA2/USD/NDC
  3 #TAS01...
MZ-  1./TAS01/REFXX/PAWABK/USD/NDC¬
  2./TAS01/OIDXX/XX001H6X4W4A2/USD/NDC¬
  3./TAS01...

Select a link below to view information about those lines.

Note: Apollo and Worldspan do not currently support modify or schedule change. This functionality is coming soon.

Note: Canceled DI lines are available in booking file history.

Airline record locator and NDC identifier

The NDC identifier in DI remarks differentiates NDC PNRs from LCC or GDS ones.

Travelport+ and Apollo:  TAS01#REFaa/QUP2X5/AUD/NDC  

Worldspan:  TAS01/REFaa/QUP2X5/AUD/NDC   

Code Description

DOCI-FREE TEXT-#

Travelport+ only

Document itinerary remark used for all entries

TRMK-#

Apollo only

Ticketing free text remark used for all entries

MZ- /

Worldspan only

Remark line used for all entries

TAS

Identifier used on each line

nn

Fare number, 2 numeric (nn), used on each line

  • nn# is used for Travelport+ and Apollo

  • nn/ is used for Worldspan

REFaa

NDC airline reference (REF)

aa – NDC airline code

/{text}

 

Separator (/) followed by NDC airline record locator

/aaa

Separator (/) followed by three-alpha currency code

/NDC NDC identifies this booking as an NDC booking.

Order ID

When an NDC booking is created by a new booking or an order divide operation, the OID identifies the Order ID for all airlines. NDC deals with Offers (shop/price) and Orders (bookings), so Order ID is recognized by NDC carriers more than booking reference/vendor locator.

Format after TASnn:

OIDcc/xxxxxxxxxx/aaa/NDC

Code Description Mandatory/Optional

OID

Identifier for the Order ID (OID)

M

cc

Two-character airline code for the booking

M

/xxxxxxxxxx/

Denotes the Order ID for the booking

M

aaa

Defines the currency used by the PCC for the booking

M

/NDC

Identifies an NDC booking

M

Examples:

  • Travelport+ and Apollo: #TAS01#OIDQF/QF081BE30BED4/AUD/NDC

  • Worldspan: /TAS01/OIDSQ/SQ_5VNW8B/SGD/NDC

Passenger fare and tax breakdown information

Format after TASnn:

P01ADT/168.75/37.81/188.86
Code Description

Pnn

Passenger identifier (P) followed by 2 numeric (nn)

XXX

Passenger Type Code

/nn.nn

Separator, 1 literal followed by Base fare, decimal (nn.nn)

/nn.nn

Separator, 1 literal followed by Tax, decimal (nn.nn)

/nn.nn

Separator, 1 literal followed by Total, decimal (nn.nn)

Format after TASnn:

P01ADT/QR20.75/UO6.00/WG11.06
Code Description

Pnn

Passenger identifier (P) followed by 2 numeric (nn)

XXX

Passenger Type Code

/XXnn.nn

Separator, 2 alpha tax code followed by tam amount, decimal (nn.nn)

Will repeat

Flight details for a segment

Format after TASnn:

S01FLTaannnn/Q/24APR2019/SYDMEL/08000935
Code Description

Snn

Segment identifier (S) followed by 1 or 2 numeric (nn) which is from the PNR segment number for this flight

FLTaannnn

FLT – Flight Identifier

Carrier Code – 2 literals (aa)

Flight Number – 4 numeric (nnnn)

/aa

Separator, 1 literal followed by Class Code – up to 2 literals (aa)

/DDMMMYYYY

Separator, 1 literal followed by DDMMMYYY – Date format (e.g. 17JUN2011)

/aaaaaa

Separator, 1 literal followed by Origin and Destination – 6 literals (aaaaaa)

/hhmmhhmm

Separator, 1 literal followed by Departure and Arrival times in hhmm, hhmm format

Hold Booking remarks

When an NDC airline supports Hold Bookings, an itinerary remark is added to indicate that the booking was initially completed without payment and that payment must be added within a set time limit to prevent the booking being auto-cancelled by the NDC airline.

Format after TASnn:

RESERVATION CONFIRMED 04APR19 1938Z
Code Description

RESERVATION CONFIRMED DDMMMYY HHMMZ

Standard text for confirmed reservation

Where DDMMMYY HHMMZ to be replaced with booking date and time (Zulu)

Format after TASnn:

TICKET TIME LIMIT 05APR19 2359Z
Code Description

TICKET TIME LIMIT

DDMMMYY HHMMZ

Standard text for HOLD Booking

Where DDMMMYY HHMMZ to be replaced with ticket time limit (Zulu)

Transaction total

NDC booking total. Format after TASnn:

TOT566.56
Code Description

TOTnnn.nn

TOT – Total amount identifier

Total amount, decimal (nn.nn)

Ticket numbers

Ticket Numbers as received from the NDC airline. Ticket Numbers are per passenger.

Format after TASnn:

TKT/P01/S01-02/08157476215350
Code Description

TKT

Identifies ticketing information (TKT)

/P01

Separator (/) followed by P (passenger identifier) and the passenger number

/S

Separator (/) followed by S to indicate segments

nn-nn

or

nn.nn

01-02 indicates a segment range (both segments 1 and 2). To specify segments 1 through 3, enter 01-03.

To indicate specific segments, use a period (e.g., to specify only segments 1 and 3, enter 01.03).

/aaaaaaaaaaaaaaa

Separator (/) followed by the ticket number.

When a fee is collected and an EMD is issued the following lines will be added to capture the transaction.

Format after TASnn:

EMD-S/P01/08157476215350
Code Description

EMD-S

EMD identifier (EMD), 3 literals – A or S

/P

Separator, 1 literal (/)

P – Passenger Identifier, 1 literal

nn

Passenger number

/aaaaaaaaaaaaaaa

Separator, 1 literal (/) followed by String of ticket number.

Fees

Fees applied on each traveler in the booking.

Format after TASnn:

P01ADT/FEE6.00/UO1.73
Code Description
P01ADT Indicates passenger 1 is an adult

FEEnn.nn

Separator (/) followed by FEE, which indicates the total charge for OB fees associated to the traveler (e.g., credit card, seats, change fee). In this example, the fee is 6.00.

Any amount following the fee indicates the tax associated to the fee.The two-letter tax code is followed by the tax amount.

DI line format for fee and any associated taxes associated to the fee:  FEE<BaseFee>/<TaxCode><TaxAmount>

Form of payment

Format after TASnn:

FOPCC/AXXXXXXXXXXXX1002/566.55/04APR19 1941Z
FOPCA/566.55/04APR19 1941Z
Code Description

FOP

FOP is the form of payment identifier

Type

The two letters following FOP indicate the type of payment.

  • CC indicates credit card.

    • Followed by a separator (/), the two-letter credit card code, and the masked credit card number.

    • Credit card information is followed by a separator (/) and the amount charged

  • CA indicates cash. It is followed by a separator (/) and the payment total (nn.nn).

/DDMMMYY HHMMZ

Separator (/) followed by the ticket issuance date (DDMMMYY) and time (HHMMZ) Zulu (Z).

Format after TASnn:

FOPTKT/08157476215350/04APR19 1941Z
Code Description

FOP

FOP- Form of Payment identifier

Type

For Ticket as form of payment TKT

/aaaaaaaaaaaaaaa

Separator (/) followed by ticket number.

/DDMMMYY HHMMZ

Separator, ticket issuance Zulu day and time DDMMMYY HHMMZ

Remarks after cancel for un-ticketed itinerary

Remarks indicating if the cancel yield to a void, refund, or credit on hold will be added.

Format after TASnn:

NDC RES CXL 21JAN 1651Z
Code Description

NDC RES CXL

Indicates reservation has been cancelled

DDMMMYY HHMMZ

Separator, ticket issuance zulu day and time DDMMMYY HHMMZ

Remarks after cancel for ticketed itinerary

Remarks indicating if the cancel yield to a void or credit on hold will be added.

Format after TASnn:

NDC RES CXL TKT VOID 21JAN 1651Z
NDC RES CXL TKT RFND 21JAN 1651Z
NDC RES CXL CREDIT ON HOLD 21JAN 1651Z
Code Description

NDC RES CXL

Indicates reservation has been cancelled

Status

TKT VOID when the cancellation is within the void window

TKT RFND when cancelled outside the void window and a refund applies

CREDIT ON HOLD when the user requested the unused ticket to be placed on hold for future use

DDMMMYY HHMMZ

Separator, ticket issuance zulu day and time DDMMMYY HHMMZ

Credit on hold details

The flow for a Credit on Hold (COH partially used) itinerary:

Original booking

  • Fare for segment 1: AUD 200.15; fare for segment 2: AUD 582.12; total price of the booking: AUD 782.27

  • Segment 1 was used and the booking was canceled with remaining funds (retained as credits).

  • In the current PNR, the retained credits display the total value of the booking (e.g., AUD 782.27), including the fare of the used segment.

When using the credits against a new booking:

  • New booking example for a new date with a higher cabin type; total fare of new booking is AUD 957.77

  • During reshop, the value of the used segment is added to this new fare.

    E.g., new fare = AUD 957.77 + AUD 200.15 (used) = AUD 1157.92.

  • Since the original fare = AUD 782.27, the differential = 375.65.

  • This is the same as the new fare = AUD 957.77. Original fare excluding used segment = AUD 582.12, so the differential = 375.65.

Remarks after modify

Remarks indicating that the original itinerary has been modified.

NEW/ indicates the newly modified flight segment.

ORIGINAL/ indicates the previous flight segment.

Format after TASnn:

ITINERARY MODIFIED 09APR19 1938Z
NEW/S01FLTAA1805/Q/25JAN2022/DFWOKC/10401138
ORIGINAL/S01FLTAA1805/Q/25JAN2022/DFWOKC/08400938
Code Description

ITINERARY MODIFIED

ITINERARY MODIFIED text

DDMMMYY HHMMZ

Itinerary modify zulu day and time DDMMMYY HHMMZ

When the itinerary is modified after PNR Sync due to an involuntary schedule change, an extra label is added in the header:

Format after TASnn:

ITINERARY MODIFIED INVOL SCHED CHNG 05MAY21 0453Z
NEW/S01FLTAA1805/Q/25JAN2022/DFWOKC/10401138
ORIGINAL/S01FLTAA1805/Q/25JAN2022/DFWOKC/08400938

Itinerary remarks when a refund was applied to original form of payment

Remarks indicating if a cancel or an exchange yield to a refund.

Format after TASnn:

REFUND111.56
Code Description

REFUND

Refund as the result of a cancellation or an exchange

nnn.nn

Refund Amount

Itinerary remarks when a refund/charge was applied to EMD

Remarks indicating if an exchange yield to a refund or charge.

Format after TASnn:

EMD/P01/08122234567666/Refund/GBP/14.90
EMD/P01/08122234567666/ChangeFee/GBP/14.90
Code Description

EMD

EMD

Pn

Traveler Number

EMD#

EMD Number

EMD Type Text

Type text as returned by carrier such Refund, ChangeFee, ReBookingFee etc.

EMD Currency Code

Currency code

EMD Amount

Amount

Remarks when an ancillary-related EMD is issued by carrier

Remarks indicating ancillary type, traveler sequence number, segment sequence number, EMD number with the amount charged against the EMD for the ancillary.

Format after TASnn:

EMD/P01/S02/1234567890/SEAT/USD/25.00
EMD/P02/S02/1234567890/SEAT/USD/35.00
Code Description

EMD

EMD

/Pnn

Separator (/) followed by P (passenger identifier) and the passenger number.

/Snn

Separator (/) followed by S (segment identifier) and the segment number.

EMD#

Separator (/) followed by the EMD number

Ancillary Type Text

Separator (/) followed by the type, such as SEATS

EMD Currency Code

Separator (/) followed by currency code such as SGD, USD, etc.

EMD Amount

Separator (/) followed by amount in 0.00 format

Itinerary Remarks when a ticketed itinerary has been modified resulting in an even exchange

Remarks indicating even exchange.

Format after TASnn:

EVEN EXCHANGE
Code Description

EVEN EXCHANGE

Even exchange text

Ancillaries

Seat

Seats can only be assigned by passenger and by segment (i.e.,) ranges not permitted. Only confirmed seats will be written in the lines.

Free seat format after TASnn:

DAS/P01/S01/SEAT/23A
DAS/P01/S02/SEAT/24A

Paid seat format after TASnn:

DAS/P01/S01/SEAT/23A/USD/25.00
DAS/P01/S02/SEAT/23B/USD/28.00

Free and paid seat format after TASnn:

DAS/P01/S01/SEAT/23A
DAS/P01/S02/SEAT/23B/USD/28.00
Code Description

DAS

Optional Services identifier (DAS)

/P01 

 

Separator (/) followed by P (passenger identifier) and the passenger number.

/S02

Separator (/) followed by S (segment identifier) and the segment number.

/aaaaaaaaaaaaaaa

 

Separator (/) followed by the optional service name, such as SEAT

/aaa

Separator (/) followed by the seat number

/aaa Separator (/) followed by the currency code

/n.nn

Separator (/) followed by the unit cost

Other Ancillaries

Other Ancillaries will be stored in Itinerary Remarks and referenced to a passenger segment. The Ancillary name will be displayed along with the applicable 4-6 letter NDC code.

Format after TASnn:

DAS/P01-03/S01-02/AIRPORT CHECKIN-TSCI/6.00/6
DAS/P01/S01-02/HOLDBAGS-BGPP/10.00/2
DAS/P01.03/S01-02/GOLF CLUBS-BGSPGF/10.00/4
Code Description

DAS

Optional Services identifier (DAS)

/P01

Separator (/) followed by P (passenger identifier) and the passenger number.

  • 01 indicates only passenger 1.

  • 01-03 indicates passengers 1, 2, and 3.

  • 01.03 indicates only passengers 1 and 3.

/S01-02

Separator (/) followed by S (segment identifier) and the segment number.

  • 01 indicates only segment 1.

  • 01-03 indicates segment 1, 2, and 3.

  • 01.03 indicates only segment 1 and 3.

/aaaaaaaaaaaaaaa

Separator, 1 literal (/)

String of Optional Service item name. The name should be similar to the name Optional Services screen with Optional Service code concatenated.

/n.nn

Separator, 1 literal (/) followed by unit cost, decimal (n.nn)

/n

Separator, 1 literal (/) followed by number of units, 1 numeric (n) (total number of units of all passengers)

Reissue of Tickets - Schedule change - Reason and/or Waiver Code

When a booking has a schedule change resulting in disassociation of the tickets for the passengers in the PNR, the agent must manually reissue the tickets for the passengers in the booking using reason and/or waiver code. This ensures that the passengers do not incur any fees or charges during reissue of the tickets on the flights with the schedule change. This same information is updated in the DI lines for the GDS booking detailing that the tickets generated for the passengers do not use any known FOP but is an even exchange. The reason and/or waiver codes are used for the same.

Format after TASnn:

EVEN EXCHANGE-WAIVER XXXXXXXX REASON YY
Code Description

Mandatory/

Optional

EVEN EXCHANGE-

Constant literal – defines that the tickets generated are an even exchange

M

WAIVER XXXXXXXX

 

Optional

If waiver code is used then this would display within the DI line.

WAIVER – Constant literal

BLANK – Literal space delimiter

XXXXXXXX – Waiver code used by agent (free form text – no length restriction)

BLANK – Literal space delimiter

O

REASON YY

Reason code is currently mandatory for all implemented carriers

REASON – Constant literal

BLANK – Literal space delimiter

YY – Reason code used by agent – numeric (possible values 1,2,3,4,5,14)

M

Fare Type, Account and Corporate Code

When a booking is created or modified for an NDC, the Offer used is clearly identified and cross referenced. This creates an audit trail for back office providers, attained by the Fare Type and Account Code/Corporate Deal that was used to generate the offer, to be captured as a new invoice remark once the Order has been created or modified.

Format after TASnn:

PccAAA/FARETYPE/XXXXXXXXXXX/YYYYYY
Code Description

Mandatory/

Optional

P Denotes that this Remark line is for a passenger

M

cc Denotes the passenger number in the booking

M

AAA Denotes the three character Passenger Type Code (PTC)

M

/FARETYPE/

Constant Literal – defines that followup details are the fare type

M

XXXXXXXXXXX

This text is updated based on the different Fare Type returned by the carrier and the prevalent mapping for the same.

Possible Values (PUBLICFARE, AIRLINEPRIVATEFARE, etc.)

M

/YYYYY

Denotes the account code or Corporate code as used by the agent or passenger during booking or modification

O

Examples after TASnn:

P01ADT/FARETYPE/PUBLICFARE
P01ADT/FARETYPE/AIRLINEPRIVATEFARE/FLX50
P01ADT/FARETYPE/AIRLINEPRIVATEFARE

Fare Basis Code

An additional DI line is included when a new itinerary is booked or when an update is made to the existing NDC offer. This DI line provides the fare basis code(s) used for the booking, indicating which fare basis was used for which segments and which passenger.

Format for the DI line for one fare basis, one passenger, one segment booking after TASnn:

FAREBASIS/<FareBasis>//<Segments>/<Passenger>

When using a multi-fare basis code itinerary, the lowest segment number is added in the first line, the next highest is in the next line, etc.

Code Description

Mandatory/

Optional

FAREBASIS

Constant literal – defines that followup details are the fare Basis

M

/XXXXXXXXXXX/

Denotes the fare basis code

M

/<Segments>/

Denotes the segments details

Example: /S01.04-05/

"-" represents the continuity and "." represents the continuity break.

M

<Passenger>

Denotes the three-character Passenger Type Code PCC

M

Example of a one fare basis itinerary, if continuity in the segments after TASnn:

FAREBASIS/B1N0C4S1IN//S01.04-05/INF
FAREBASIS/B1N0C4S1IN//S01-02.04-05/INF

Note: "." represents the continuity break and "-" represents the continuity.

Example of an itinerary using more than one fare basis code after TASnn:

FAREBASIS/ESQW1//S01/ADT
FAREBASIS/ESQW1CH//S01/CHD
FAREBASIS/SDQW//S02/ADT
FAREBASIS/SDQWCH//S02/CHD

Involuntary PNR Cancel

This line represents the involuntary PNR cancel information of an original itinerary.

Format after TASnn:

NDC RES CXL INVOL CXL 05MAY22 1938Z
ORIGINAL/S01FLTAA1805/Q/04MAY2022/DFWOKC/08400938
Code Description

NDC RES CXL INVOL CXL

Standard text for involuntary cancel

DDMMMYY HHMMZ

Itinerary modify Zulu day and time

Segment Type

Original indicates the original flight segment

S{nn}

Segment identifier (S) followed by 1 or 2 numeric (nn) which is from the PNR segment number for this flight

FLTaannnn

Flight Identifier (FLT) Carrier Code – 2 literals (aa) Flight Number – 4 numeric (nnnn)

/aa

Separator, 1 literal(/) Class Code – up to 2 literals (aa)

/DDMMMYYYY

Separator, 1 literal(/) Date format (e.g. 17JUN2011)

/aaaaaa

Separator, 1 literal(/) Origin and Destination – 6 literals (aaaaaa)

/hhmmhhmm

Separator, 1 literal(/) Departure and Arrival times