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 357 Customs In-Bond Information

The X12 document carriers and terminals use to request authorization for in-bond movements and to add legs to existing ones.

Sent by
Carrier, terminal operator, port authority or service center
Received by
Customs authority
Standard
ANSI ASC X12

What is an EDI 357?

The EDI 357 Customs In-Bond Information is the ANSI X12 transaction set transportation carriers, terminal operators, port authorities and service centers use to request authorization for in-bond movements and to add legs to existing in-bond movements.

An in-bond movement lets imported goods travel under bond to another port or inland point before entry, or through the country for export. The 357 starts the movement in customs systems; arrival or export is later reported with a 353 to close it. Each authorization is identified by an in-bond number used in later messages.

How the EDI 357 worksDiagram of the EDI 357 Customs In-Bond Information. Carrier, terminal operator, port authority or service center sends it to customs authority. It usually starts the exchange. It is usually followed by 353 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: M10 (Manifest Identifying Information) and the required P4 loop with P4 (Port Information) and the required LX loop with LX (Transaction Set Line Number). 0 optional loops are listed by their first segment.How the EDI 357 worksCustoms In-Bond Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 357SENDERCarrier, terminaloperator, port authorityor service centerRECEIVERCustoms authority997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY353Customs Events AdvisoryDetails997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code BBGS … GETransaction set 357ST … SEHEADINGM10Manifest Identifying InformationRequired loop P4 · repeats up to 1P4Port InformationRequired loop LX · repeats up to 999LXTransaction Set Line NumberBlue 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 357. Your trading partner's implementation guide adds its own requirements.
How the EDI 357 worksDiagram of the EDI 357 Customs In-Bond Information. Carrier, terminal operator, port authority or service center sends it to customs authority. It usually starts the exchange. It is usually followed by 353 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: M10 (Manifest Identifying Information) and the required P4 loop with P4 (Port Information) and the required LX loop with LX (Transaction Set Line Number). 0 optional loops are listed by their first segment.How the EDI 357 worksCustoms In-Bond Information: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 357SENDERCarrier, terminaloperator, portauthority orservice centerRECEIVERCustomsauthority997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY353Customs Events Advisory Details997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code BB (GS … GE)Transaction set 357 (ST … SE)HEADINGM10Manifest IdentifyingInformationRequired loop P4 · repeats up to 1P4Port InformationRequired loop LX · repeats upto 999LXTransaction Set LineNumberBlue 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 357. Your trading partner'simplementation guide adds its own requirements.

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

  • Requesting authorization to move cargo in bond
  • Adding a leg to an existing in-bond movement
  • Moving goods in transit through the country for export

Where it fits in the document flow

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

Structure

Mandatory segments in the 357 (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
  • M10
  • P4
  • LX
  • SE

Practical example

The 357 in practice

An importer wants containers arriving in Los Angeles cleared in Dallas, near its distribution center. The carrier sends customs a 357 requesting an in-bond movement from Los Angeles to Dallas for the bills of lading concerned. Once authorized, the containers move by rail, and the carrier reports their arrival in Dallas with a 353.

Implementation

Implementation considerations for the 357

  • Request authorization before the cargo moves.
  • Track every in-bond movement until arrival or export is reported.
  • Use in-bond numbers consistently across requests and events.
  • Follow the customs authority's implementation guide.

How ECOM helps

Automate the 357 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 357?

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

Request a Demo Contact us