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

X12 transaction guide · Transportation

EDI 353 Customs Events Advisory Details

The X12 document carriers use to notify customs of events for cargo moving in bond, and of conveyance arrivals and departures.

Sent by
Carrier
Received by
Customs authority
Standard
ANSI ASC X12

What is an EDI 353?

The EDI 353 Customs Events Advisory Details is the ANSI X12 transaction set carriers use to notify customs of events concerning cargo moving in bond, or of conveyance arrivals and departures. Events include the arrival at an inland destination of containers or bills of lading that moved in bond, and the export of in-bond cargo.

In-bond movements let imported goods travel to another port or inland point before customs entry. Customs must know when they arrive or leave the country to close the bond, so timely event reporting is a compliance requirement for the carrier.

How the EDI 353 worksDiagram of the EDI 353 Customs Events Advisory Details. Carrier sends it to customs authority. It usually follows 357. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required M15 loop with M15 (Customs Events Advisory Details). 0 optional loops are listed by their first segment.How the EDI 353 worksCustoms Events Advisory Details: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS357Customs In-BondInformationEDI 353SENDERCarrierRECEIVERCustoms authority997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code AXGS … GETransaction set 353ST … SEHEADINGRequired loop M15 · repeats up to 9,999M15Customs Events Advisory DetailsBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 353. Your trading partner's implementation guide adds its own requirements.
How the EDI 353 worksDiagram of the EDI 353 Customs Events Advisory Details. Carrier sends it to customs authority. It usually follows 357. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required M15 loop with M15 (Customs Events Advisory Details). 0 optional loops are listed by their first segment.How the EDI 353 worksCustoms Events Advisory Details: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS357Customs In-Bond InformationEDI 353SENDERCarrierRECEIVERCustomsauthority997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code AX (GS … GE)Transaction set 353 (ST … SE)HEADINGRequired loop M15 · repeats up to9,999M15Customs Events AdvisoryDetailsBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 353. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 353, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 353 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Reporting the arrival of in-bond cargo at its destination
  • Reporting the export of in-bond cargo
  • Reporting arrivals and departures of conveyances

Where it fits in the document flow

Usually follows 357 Customs In-Bond Information
This document 353 Customs Events Advisory Details
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 353 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • M15
  • SE

Practical example

The 353 in practice

Containers discharged in Seattle move in bond by rail to Chicago for entry there. When the train arrives, the rail carrier sends customs a 353 reporting the arrival of each in-bond shipment at the destination. Customs updates the in-bond records, and brokers in Chicago can file entries for the goods.

Implementation

Implementation considerations for the 353

  • Report events within the time limits set by customs.
  • Use the in-bond numbers and bill of lading references exactly as filed.
  • Monitor open in-bonds that have no arrival or export event.
  • Follow the customs authority's implementation guide for event codes.

How ECOM helps

Automate the 353 with ECOM

Industry

Trucking and Transportation

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

Solution

Logistics Automation

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

Solution

EDI Integration

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

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 353?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us