972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Customs and regulatory

PAXLST Passenger list

The UN/EDIFACT message that transfers passenger and crew data to border authorities, for example as advance passenger information.

Sent by
Carrier, or authority in the country of departure
Received by
Authorities in the country of arrival
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT PAXLST message?

PAXLST is the UN/EDIFACT passenger list message. The directory defines it as a message that transfers passenger and crew data from customs, immigration or another designated authority in the country of departure to the appropriate authorities in the country of arrival. Where national rules require it, carriers send the data directly.

PAXLST is the standard format for advance passenger information (API), used by airlines and other carriers to report travelers' identity and travel document data before arrival. Formats are set out in joint guidelines of the WCO, IATA and ICAO.

How the EDIFACT PAXLST message worksDiagram of the UN/EDIFACT PAXLST Passenger list message. Carrier, or authority in the country of departure sends it to authorities in the country of arrival. It usually starts the exchange. It is usually followed by CUSRES. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG2 loop with TDT (Transport information). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT PAXLST message worksPassenger list: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangePAXLSTSENDERCarrier, or authority inthe country ofdepartureRECEIVERAuthorities in thecountry of arrivalCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage PAXLSTUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 10TDTTransport information+ 3 conditional groups, starting with:NADLOCBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for PAXLST. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT PAXLST message worksDiagram of the UN/EDIFACT PAXLST Passenger list message. Carrier, or authority in the country of departure sends it to authorities in the country of arrival. It usually starts the exchange. It is usually followed by CUSRES. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG2 loop with TDT (Transport information). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT PAXLSTmessage worksPassenger list: who sends it, where it fits andwhat the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangePAXLSTSENDERCarrier, orauthority in thecountry ofdepartureRECEIVERAuthorities inthe country ofarrivalCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message PAXLST (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 10TDTTransport information+ 3 conditional groups, starting with:NADLOCBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for PAXLST.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends PAXLST, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around PAXLST and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Sending advance passenger information before a flight arrives
  • Reporting crew lists to border authorities
  • Reporting passengers on ships or trains where required

Where it fits in the message flow

This message PAXLST Passenger list
Usually followed by CUSRES Customs response

Structure

Mandatory segments in PAXLST (directory D.21A)

In UN/EDIFACT directory D.21A, the PAXLST message has 38 segment positions arranged in 7 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • SG2 (TDT)
  • UNT

Practical example

PAXLST in practice

At flight close, an airline's departure control system sends a PAXLST to the border authority of the destination country with each passenger's name, date of birth, nationality and travel document number. The authority screens the list before arrival and returns responses for any travelers requiring attention.

Implementation

Implementation considerations for PAXLST

  • Follow the destination's API requirements and the WCO/IATA/ICAO guidelines.
  • Protect personal data in line with data protection laws.
  • Send data at the times the authority requires, such as at departure.
  • Validate travel document data at check-in.

How ECOM helps

Automate PAXLST with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Industry

Hospitality

Procurement, invoicing and supplier integration for hotels, restaurant groups and foodservice suppliers.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related customs and regulatory messages

All 14 customs and regulatory messages

Need help with PAXLST?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us