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 361 Carrier Interchange Agreement (Ocean)

The X12 document an ocean carrier uses to tell a terminal operator which motor carriers are authorized to carry its cargo.

Sent by
Ocean carrier
Received by
Marine terminal operator
Standard
ANSI ASC X12

What is an EDI 361?

The EDI 361 Carrier Interchange Agreement (Ocean) is the ANSI X12 transaction set that gives an ocean carrier the means to tell a terminal operator whether motor carriers are authorized to carry its cargo and equipment.

Truckers need an interchange agreement with an ocean carrier before they can take its containers out of a terminal. The 361 keeps the terminal's list of authorized truckers current, so gate staff can release equipment to approved companies and refuse others. Without it, drivers can be turned away at the terminal gate.

How the EDI 361 worksDiagram of the EDI 361 Carrier Interchange Agreement (Ocean). Ocean carrier sends it to marine terminal operator. 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: N1 (Party Identification) and the required CI loop with CI (Carrier Interchange Agreement). 0 optional loops are listed by their first segment.How the EDI 361 worksCarrier Interchange Agreement (Ocean): who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 361SENDEROcean carrierRECEIVERMarine terminaloperator997 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 361ST … SEHEADINGN1Party IdentificationRequired loop CI · repeats up to 9,999CICarrier Interchange AgreementBlue 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 361. Your trading partner's implementation guide adds its own requirements.
How the EDI 361 worksDiagram of the EDI 361 Carrier Interchange Agreement (Ocean). Ocean carrier sends it to marine terminal operator. 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: N1 (Party Identification) and the required CI loop with CI (Carrier Interchange Agreement). 0 optional loops are listed by their first segment.How the EDI 361 worksCarrier Interchange Agreement (Ocean): whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 361SENDEROcean carrierRECEIVERMarine terminaloperator997 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 361 (ST … SE)HEADINGN1Party IdentificationRequired loop CI · repeats up to9,999CICarrier InterchangeAgreementBlue 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 361. Your trading partner'simplementation guide adds its own requirements.

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

  • Authorizing a motor carrier to handle an ocean carrier's equipment
  • Withdrawing a trucker's authorization
  • Synchronizing authorized trucker lists with terminals

Where it fits in the document flow

This document 361 Carrier Interchange Agreement (Ocean)
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 361 (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
  • N1
  • CI
  • SE

Practical example

The 361 in practice

An ocean carrier signs an interchange agreement with a new drayage company. It sends each terminal it uses a 361 adding the trucker's identifiers to its authorized list. When the trucker's drivers arrive to pick up the carrier's containers, the terminal gates recognize the company as authorized.

Implementation

Implementation considerations for the 361

  • Send updates before truckers start using the agreement.
  • Remove authorizations promptly when agreements end.
  • Use the trucker identifiers terminals use at the gate, such as SCACs.
  • Keep all terminals in the network synchronized.

How ECOM helps

Automate the 361 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.

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

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

Request a Demo Contact us