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

CUSEXP Customs express consignment declaration

The UN/EDIFACT message express carriers use to give customs the conveyance report, cargo report and declaration for express consignments in one message.

Sent by
Express carrier or courier
Received by
Customs administration
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT CUSEXP message?

CUSEXP is the UN/EDIFACT customs express consignment declaration. The directory defines it as a message that transfers express consignment data to a customs administration, combining all three types of customs reporting, the conveyance report, the cargo report and the customs declaration, in a single message.

Express and courier operators move very large numbers of low-value shipments overnight. Combining the three reports lets customs assess and clear them quickly, often before the aircraft lands, so parcels can be delivered the next morning.

How the EDIFACT CUSEXP message worksDiagram of the UN/EDIFACT CUSEXP Customs express consignment declaration message. Express carrier or courier sends it to customs administration. 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 SG1 loop with NAD (Name and address) and the required SG3 loop with TDT (Transport information). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT CUSEXP message worksCustoms express consignment declaration: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCUSEXPSENDERExpress carrier orcourierRECEIVERCustomsadministrationCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CUSEXPUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 1NADName and addressMandatory group SG3 · repeats up to 1TDTTransport information+ 5 conditional groups, starting with:CTALOCEQDRFFAUTBlue 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 CUSEXP. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CUSEXP message worksDiagram of the UN/EDIFACT CUSEXP Customs express consignment declaration message. Express carrier or courier sends it to customs administration. 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 SG1 loop with NAD (Name and address) and the required SG3 loop with TDT (Transport information). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT CUSEXPmessage worksCustoms express consignment declaration: whosends it, where it fits and what the directorymarks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCUSEXPSENDERExpress carrieror courierRECEIVERCustomsadministrationCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CUSEXP (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 1NADName and addressMandatory group SG3 · repeats upto 1TDTTransport information+ 5 conditional groups, starting with:CTALOCEQDRFFAUTBlue 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 CUSEXP.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends CUSEXP, 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 CUSEXP 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

  • Declaring express consignments before arrival
  • Reporting conveyance, cargo and declaration data together
  • Clearing high volumes of low-value shipments

Where it fits in the message flow

This message CUSEXP Customs express consignment declaration
Usually followed by CUSRES Customs response

Structure

Mandatory segments in CUSEXP (directory D.21A)

In UN/EDIFACT directory D.21A, the CUSEXP message has 49 segment positions arranged in 17 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
  • SG1 (NAD)
  • SG3 (TDT)
  • UNT

Practical example

CUSEXP in practice

An express carrier's overnight flight carries 6,000 parcels into Brussels. Before departure from the hub, its customs system sends a CUSEXP for each consignment with the flight, the consignor and consignee, the goods, value and weight. Customs clears most parcels before landing and flags a few for inspection with CUSRES.

Implementation

Implementation considerations for CUSEXP

  • Check the value thresholds and procedures customs allows for express consignments.
  • Send data early enough for pre-arrival clearance.
  • Validate consignee and goods data at the point of booking.
  • Process inspection selections before parcels go out for delivery.

How ECOM helps

Automate CUSEXP with ECOM

Industry

Trucking and Transportation

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

Industry

eCommerce

Marketplace, storefront, drop-ship and 3PL integration for online sellers.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

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 CUSEXP?

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

Request a Demo Contact us