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 354 Customs Automated Manifest Archive Status

The X12 document customs uses to tell carriers and terminals that the manifest for a vessel or voyage will be removed from the system.

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

What is an EDI 354?

The EDI 354 Customs Automated Manifest Archive Status is the ANSI X12 transaction set customs uses to inform carriers, terminal operators, port authorities and service centers that the manifest for a specific vessel or voyage is going to be removed from the system.

Archiving means either that every bill of lading on the manifest has been reconciled or closed, or that some remain open and will be reconciled manually. For carriers, the notice is a prompt to check for open bills before the manifest leaves the automated system.

How the EDI 354 worksDiagram of the EDI 354 Customs Automated Manifest Archive Status. Customs authority sends it to carrier, terminal operator, port authority or service center. 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) and X01 (Automated Manifest Archive Status Details). 0 optional loops are listed by their first segment.How the EDI 354 worksCustoms Automated Manifest Archive Status: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS309Customs ManifestEDI 354SENDERCustoms authorityRECEIVERCarrier, terminaloperator, port authorityor service center997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code AYGS … GETransaction set 354ST … SEHEADINGM10Manifest Identifying InformationRequired loop P4 · repeats up to 20P4Port InformationX01Automated Manifest Archive Status 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 354. Your trading partner's implementation guide adds its own requirements.
How the EDI 354 worksDiagram of the EDI 354 Customs Automated Manifest Archive Status. Customs authority sends it to carrier, terminal operator, port authority or service center. 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) and X01 (Automated Manifest Archive Status Details). 0 optional loops are listed by their first segment.How the EDI 354 worksCustoms Automated Manifest Archive Status:who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWS309Customs ManifestEDI 354SENDERCustomsauthorityRECEIVERCarrier, terminaloperator, portauthority orservice center997 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 AY (GS … GE)Transaction set 354 (ST … SE)HEADINGM10Manifest IdentifyingInformationRequired loop P4 · repeats up to20P4Port InformationX01Automated ManifestArchive Status DetailsBlue 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 354. Your trading partner'simplementation guide adds its own requirements.

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

  • Notifying that a voyage manifest will be archived
  • Signaling that open bills will be reconciled manually
  • Prompting carriers to review unreconciled bills

Where it fits in the document flow

Usually follows 309 Customs Manifest
This document 354 Customs Automated Manifest Archive Status
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 354 (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
  • X01
  • SE

Practical example

The 354 in practice

Customs prepares to archive the manifest for a voyage that arrived months earlier. It sends the carrier a 354 for the voyage, indicating that two bills of lading remain open. The carrier's documentation team reviews the two bills and works with customs to reconcile them manually.

Implementation

Implementation considerations for the 354

  • Review open bills of lading when an archive notice arrives.
  • Match the notice to the vessel and voyage as originally filed.
  • Keep records of manual reconciliation for audits.
  • Follow the customs authority's implementation guide.

How ECOM helps

Automate the 354 with ECOM

Industry

Trucking and Transportation

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

Solution

EDI Integration

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

Solution

Logistics Automation

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

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

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

Request a Demo Contact us