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 358 Customs Consist Information

The X12 document carriers use to list the bills of lading on a specific conveyance and trip for which a manifest was already filed.

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

What is an EDI 358?

The EDI 358 Customs Consist Information is the ANSI X12 transaction set transportation carriers, terminal operators, port authorities and service centers use to provide a list of bills of lading to be carried on a specific conveyance and trip number for which an electronic manifest was previously filed.

A consist ties manifested cargo to the actual train or truck carrying it. Rail carriers in particular send consists so customs knows which bills of lading are on each train arriving at the border, which supports advance targeting and faster crossing.

How the EDI 358 worksDiagram of the EDI 358 Customs Consist Information. Carrier, terminal operator, port authority or service center sends it to customs authority. It usually follows 309. It is usually followed by 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). 2 optional loops are listed by their first segment.How the EDI 358 worksCustoms Consist Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS309Customs ManifestEDI 358SENDERCarrier, terminaloperator, port authorityor service centerRECEIVERCustoms authority997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code BDGS … GETransaction set 358ST … SEHEADINGM10Manifest Identifying InformationRequired loop P4 · repeats up to 20P4Port Information+ 2 optional loops, starting with:NM1VIDBlue 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 358. Your trading partner's implementation guide adds its own requirements.
How the EDI 358 worksDiagram of the EDI 358 Customs Consist Information. Carrier, terminal operator, port authority or service center sends it to customs authority. It usually follows 309. It is usually followed by 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). 2 optional loops are listed by their first segment.How the EDI 358 worksCustoms Consist Information: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS309Customs ManifestEDI 358SENDERCarrier, terminaloperator, portauthority orservice centerRECEIVERCustomsauthority997 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 BD (GS … GE)Transaction set 358 (ST … SE)HEADINGM10Manifest IdentifyingInformationRequired loop P4 · repeats up to20P4Port Information+ 2 optional loops, starting with:NM1VIDBlue 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 358. Your trading partner'simplementation guide adds its own requirements.

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

  • Listing the bills of lading on a train arriving at the border
  • Linking previously filed manifests to a specific trip
  • Updating a consist after cars are added or removed

Where it fits in the document flow

Usually follows 309 Customs Manifest
This document 358 Customs Consist Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 358 (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
  • NM1
  • P4
  • VID
  • MBL
  • SE

Practical example

The 358 in practice

A rail carrier has filed manifests for cargo moving from Canada into the United States. Before the train reaches the border, it sends customs a 358 listing the train and trip number and the bills of lading on each car. Customs matches the consist to the filed manifests and completes its review before the train arrives.

Implementation

Implementation considerations for the 358

  • Send the consist after the manifests it refers to are on file.
  • Update the consist when equipment is added or dropped.
  • Use trip and conveyance identifiers exactly as customs expects.
  • Follow the customs authority's implementation guide.

How ECOM helps

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

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

Request a Demo Contact us