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 319 Terminal Information

The X12 document terminal operators use to report shipment arrival, availability for pickup and actual pickup to authorized parties.

Sent by
Terminal operator
Received by
Customs broker, forwarder or consignee
Standard
ANSI ASC X12

What is an EDI 319?

The EDI 319 Terminal Information is the ANSI X12 transaction set terminal operators use to give authorized parties shipment arrival event information. It can report the arrival of the shipment, its availability for pickup and the actual pickup.

Brokers, forwarders and consignees use the events to time customs filing, dispatch truckers and track free time at the terminal. The 319 reports from the terminal's own records, which can differ from the carrier's view of the shipment. It is common at ports and air cargo terminals.

How the EDI 319 worksDiagram of the EDI 319 Terminal Information. Terminal operator sends it to customs broker, forwarder or consignee. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BA2 (Beginning Segment for Cargo Terminal Information) and CD1 (Cargo Detail). 0 optional loops are listed by their first segment.How the EDI 319 worksTerminal Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 319SENDERTerminal operatorRECEIVERCustoms broker,forwarder or consignee997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SOGS … GETransaction set 319ST … SEHEADINGBA2Beginning Segment for Cargo Terminal InformationCD1Cargo DetailBlue 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 319. Your trading partner's implementation guide adds its own requirements.
How the EDI 319 worksDiagram of the EDI 319 Terminal Information. Terminal operator sends it to customs broker, forwarder or consignee. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BA2 (Beginning Segment for Cargo Terminal Information) and CD1 (Cargo Detail). 0 optional loops are listed by their first segment.How the EDI 319 worksTerminal Information: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 319SENDERTerminaloperatorRECEIVERCustoms broker,forwarder orconsignee997 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 SO (GS … GE)Transaction set 319 (ST … SE)HEADINGBA2Beginning Segment for CargoTerminal InformationCD1Cargo DetailBlue 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 319. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 319, 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 319 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 arrival of cargo at a terminal
  • Advising that cargo is available for pickup
  • Confirming that cargo has been picked up

Where it fits in the document flow

This document 319 Terminal Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 319 (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
  • BA2
  • CD1
  • SE

Practical example

The 319 in practice

An air-and-ocean forwarder handles import cargo through a terminal. The terminal sends the forwarder a 319 when the shipment arrives, another when customs releases it and it becomes available, and a third when the trucker collects it. The forwarder uses the availability event to dispatch the trucker and the pickup event to close the shipment.

Implementation

Implementation considerations for the 319

  • Map terminal event codes to your own shipment milestones.
  • Use availability events to trigger dispatch and track free time.
  • Reconcile terminal events with carrier status (315) when they differ.
  • Confirm the shipment references the terminal uses.

How ECOM helps

Automate the 319 with ECOM

Industry

Trucking and Transportation

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

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Industry

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

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

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

Request a Demo Contact us