Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D93A Messages page.


This message is available for formal trial in the present version for a period of at least twelve months from the date of approval by the UN/ECE/TRADE/WP.4.

Organisations are invited to trial this message and are requested to notify their Rapporteur Team Secretariat of their intention. Comments on the results from the trial should also be forwarded to the Secretariat as soon as they are available. Based on the results of the trials, a UNSM will be issued.

It should be noted that this material is contained in a Trial Directory; however, it may differ from that in the UN Directories (UNTDID) having the same identfying tags. Any differences will be reconciled prior to the message becoming a UNSM.

Message Type:PAXLST
Contr. Agency:UN
SOURCE:Australia/New Zealand EDIFACT Board

  1. Introduction
  2. Scope
    1. Functional Definition
    2. Field of Application
    3. Principles
  3. References
  4. Message Definition
  5. Message Definition
    1. Data Segment Clarification
    2. Message structure
      1. Branching Diagram
      2. Segment Table
    3. Data Segment Index (Alphabetic Sequence)

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.5, UN/ECE UNSM General Introduction.

This message also occurs in the following versions of this standard:
D93A, D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B

0. Introduction

This specification provides the definition of the Passenger List Message (PAXLST) to be used in Electronic Data Interchange (EDI) between partners involved in administration, commerce and transport.

1. Scope

1.1. Functional Definition

This Passenger List Message (PAXLST) permits the transfer of passenger/crew data from a Customs, Immigration or other designated authority in the country of departure to the appropriate authorities in the country of arrival of the means of transport.

Where national privacy legislation permits, and with the agreement of all parties involved, this message may also be exchanged between carriers and Customs, Immigration, Police or any designated authorities.

This transfer of data may occur upon departure from the sending agency and prior to arrival of the vessel/ flight at the receiving agency. This is to permit the designated authority at the place of destination to screen this data and take timely decisions related to the clearance of passengers and crew.

The transfer of data may also occur prior to departure, carriers may transmit passenger listings to customs and immigration for pre-arrival clearance.

Endorsement of this message by the Customs Cooperation Council does not necessarily mean endorsement by national Immigration or Police authorities, nor does it place any obligations on parties to apply the message.

1.2. Field of Application

This message may be applied for international passenger movement and is not dependent on the mode of transport.

1.3. Principles

It is envisaged that the message will:

(a) facilitate the clearance of low risk passengers/crew.

(b) allow Customs, Immigration or police authorities to more

effectively and efficiently concentrate resources on areas of highest risk.

2. References

See UNTDID, Part 4 Section 2.5 UN/ECE UNSM - General Introduction, Section 1.

3. Terms and Definitions

See UNTDID, Part 4, Section 2.5 UN/ECE UNSM - General Introduction, Section 2.

4. Message Definition

4.1. Data Segment Clarification

This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.

0010 UNH, Message header

A service segment starting and uniquely identifying a message.

Note: Passenger List messages conforming to this document must contain the following data in UNH, composite S009:

Data element0065PAXLST

0020 BGM, Beginning of message

A segment to indicate the type and function of the message.

0030 RFF, Reference

A segment to specify message reference.

0040 DTM, Date/time/period

A segment to specify associated dates/times as required related to the message.

0050 Segment Group 1: NAD-CTA-COM

A group of segments to specify name/address, person or department in the originating administration who can provide further information about the data in the message.

0060 NAD, Name and address

A segment to identify the name, address and related function.

0070 CTA, Contact information

A segment to identify a person or department in the sending administration to contact.

0080 COM, Communication contact

A segment to identify communication numbers of departments or persons to whom communication should be directed (e.g. telephone/fax number).

0090 Segment Group 2: TDT-DTM-SG3

A group of segments to indicate information related to each leg of the mode of transport.

0100 TDT, Details of transport

A segment to specify details of transport related to each leg, including means of transport, mode of transport name/number of vessel/vehicle/flight.

0110 DTM, Date/time/period

A segment to specify associated dates/times as required related to details of transport.

0120 Segment Group 3: LOC-DTM

A group of segments indicating associated locations and dates.

0130 LOC, Place/location identification

A segment to specify locations such as place of departure, place of destination, country of ultimate destination, country/place of transit, country of transit termination, etc. of a passenger/crew.

0140 DTM, Date/time/period

A segment to specify associated dates/times as required related to locations.

0150 Segment Group 4: NAD-ATT-DTM-MEA-GIS-FTX-LOC-SG5

A group of segments to indicate if passenger or crew member, personal details (name, title, sex and marital status), date of birth, attributes such as height, hair and eye colour, and other related details.

0160 NAD, Name and address

A segment specifying name of the passenger or crew member

0170 ATT, Attribute

A segment specifying passenger's/crew attributes such as complexion and build.

0180 DTM, Date/time/period

A segment to specify date of birth.

0190 MEA, Measurements

To specify physical measurements, (e.g. height).

0200 GIS, General indicator

A segment to specify indicators such as risk assessment.

0210 FTX, Free text

A segment specifying other related passenger/crew information e.g. ticketing information.)

0220 LOC, Place/location identification

A segment indicating country of nationality, country of birth and port/place of origin (embarkation), transit and destination (disembarkation) of a passenger/crew.

0230 Segment Group 5: DOC-DTM-GIS-RFF-LOC

A group of segments to indicate the travel document details, date and time, reference, place/location identification.

0240 DOC, Document/message details

A segment identifying passenger/crew travel documents, such as passports, visas etc.

0250 DTM, Date/time/period

A segment to specify associated dates/times related to documents.

0260 GIS, General indicator

A segment to specify processing indicators, such as document holder, alias, endorsee etc.

0270 RFF, Reference

A segment to specify document reference.

0280 LOC, Place/location identification

A segment indicating the country that issued the document.

0290 CNT, Control total

A segment specifying control totals such as the total number of passengers/ crew members in the message.

0300 AUT, Authentication result

A segment to specify the results of the application of an authentication procedure, including the authenticity of sender to ensure integrity of data.

0310 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.

4.2. Message Structure

4.2.1. Branching Diagram

4.2.2. Segment Table

├─UNH Message header ×1 (M)
├─BGM Beginning of message ×1 (M)
├─RFF Reference ×1 (C)
├─DTM Date/time/period ×9 (C)
├─Segment Group 1 ×5 (C)
├─NAD Name and address ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×9 (C)
├─Segment Group 2 ×10 (M)
├─TDT Details of transport ×1 (M)
├─DTM Date/time/period ×1 (M)
└─Segment Group 3 ×99 (C)
──├─LOC Place/location identification ×1 (M)
──└─DTM Date/time/period ×5 (C)
├─Segment Group 4 ×99999 (M)
├─NAD Name and address ×1 (M)
├─ATT Attribute ×9 (C)
├─DTM Date/time/period ×9 (C)
├─MEA Measurements ×9 (C)
├─GIS General indicator ×5 (C)
├─FTX Free text ×5 (C)
├─LOC Place/location identification ×25 (C)
└─Segment Group 5 ×5 (C)
──├─DOC Document/message details ×1 (M)
──├─DTM Date/time/period ×5 (C)
──├─GIS General indicator ×1 (C)
──├─RFF Reference ×1 (C)
──└─LOC Place/location identification ×1 (C)
├─CNT Control total ×1 (C)
├─AUT Authentication result ×1 (C)
└─UNT Message trailer ×1 (M)

4.3. Data Segment Index (Alphabetic Sequence)

ATT Attribute
AUT Authentication result
BGM Beginning of message
CNT Control total
COM Communication contact
CTA Contact information
DOC Document/message details
DTM Date/time/period
FTX Free text
GIS General indicator
LOC Place/location identification
MEA Measurements
NAD Name and address
RFF Reference
TDT Details of transport
UNH Message header
UNT Message trailer

Return to Stylus Studio EDIFACT D93A Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.