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 362 Cargo Insurance Advice of Shipment

The X12 document shippers use to notify their cargo insurer of shipments insured under their cargo policy.

Sent by
Shipper or freight forwarder
Received by
Cargo insurance company
Standard
ANSI ASC X12

What is an EDI 362?

The EDI 362 Cargo Insurance Advice of Shipment is the ANSI X12 transaction set shippers use to notify their cargo insurance company of shipments of merchandise insured under their cargo policy.

Under an open cargo policy, the shipper declares each shipment to the insurer, which calculates the premium and may issue insurance certificates. Declaring shipments electronically ensures coverage is recorded for each one and simplifies premium billing and claims. It also gives the shipper an audit trail of what was insured and when.

How the EDI 362 worksDiagram of the EDI 362 Cargo Insurance Advice of Shipment. Shipper or freight forwarder sends it to cargo insurance company. 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: BGN (Beginning Segment), CUR (Currency), REF (Reference Information) and N1 (Party Identification) and detail: the required L5 loop with L5 (Description, Marks and Numbers), REF (Reference Information), DTP (Date or Time or Period), V1 (Vessel Identification), the required R4 loop with R4 (Port or Terminal) and the required AMT loop with AMT (Monetary Amount Information). 1 optional loops are listed by their first segment.How the EDI 362 worksCargo Insurance Advice of Shipment: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 362SENDERShipper or freightforwarderRECEIVERCargo insurancecompany997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code OCGS … GETransaction set 362ST … SEHEADINGBGNBeginning SegmentCURCurrencyREFReference InformationN1Party IdentificationDETAILRequired loop L5 · repeats many timesL5Description, Marks and NumbersREFReference InformationDTPDate or Time or PeriodV1Vessel IdentificationRequired loop R4 · repeats up to 5R4Port or TerminalRequired loop AMT · repeats up to 9AMTMonetary Amount Information+ 1 optional loop, starting with:LQBlue 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 362. Your trading partner's implementation guide adds its own requirements.
How the EDI 362 worksDiagram of the EDI 362 Cargo Insurance Advice of Shipment. Shipper or freight forwarder sends it to cargo insurance company. 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: BGN (Beginning Segment), CUR (Currency), REF (Reference Information) and N1 (Party Identification) and detail: the required L5 loop with L5 (Description, Marks and Numbers), REF (Reference Information), DTP (Date or Time or Period), V1 (Vessel Identification), the required R4 loop with R4 (Port or Terminal) and the required AMT loop with AMT (Monetary Amount Information). 1 optional loops are listed by their first segment.How the EDI 362 worksCargo Insurance Advice of Shipment: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 362SENDERShipper orfreightforwarderRECEIVERCargo insurancecompany997 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 OC (GS … GE)Transaction set 362 (ST … SE)HEADINGBGNBeginning SegmentCURCurrencyREFReference InformationN1Party IdentificationDETAILRequired loop L5 · repeats manytimesL5Description, Marks andNumbersREFReference InformationDTPDate or Time or PeriodV1Vessel IdentificationRequired loop R4 · repeats upto 5R4Port or TerminalRequired loop AMT · repeatsup to 9AMTMonetary AmountInformation+ 1 optional loop, starting with:LQBlue 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 362. Your trading partner'simplementation guide adds its own requirements.

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

  • Declaring shipments under an open cargo policy
  • Requesting insurance certificates for shipments
  • Reporting insured values and routes

Where it fits in the document flow

This document 362 Cargo Insurance Advice of Shipment
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 362 (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
  • BGN
  • CUR
  • REF
  • N1
  • L5
  • DTP
  • V1
  • R4
  • AMT
  • LQ
  • SE

Practical example

The 362 in practice

An exporter of industrial equipment holds an open cargo policy. For each shipment, its system sends the insurer a 362 with the insured value, the goods, the route, the vessel and the sailing date. The insurer records the declaration, bills the premium monthly and issues a certificate where the letter of credit requires one.

Implementation

Implementation considerations for the 362

  • Declare shipments within the time the policy requires.
  • Report insured values and currencies accurately.
  • Link declarations to bills of lading for any later claim.
  • Confirm which shipments the policy covers before automating declarations.

How ECOM helps

Automate the 362 with ECOM

Industry

Trucking and Transportation

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

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

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

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

Request a Demo Contact us