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 920 Loss or Damage Claim - General Commodities

The X12 document used to file a legal claim with a transportation carrier for loss of, or damage to, general commodities.

Sent by
Claimant (shipper, consignee or owner of the goods)
Received by
Transportation carrier
Standard
ANSI ASC X12

What is an EDI 920?

The EDI 920 Loss or Damage Claim - General Commodities is the ANSI X12 transaction set used to file a legal claim with a transportation carrier for loss or damage. It identifies the shipment, the claimant, the goods lost or damaged, and the amount claimed with its supporting details.

Freight claims have legal requirements and time limits; in the United States, claims against carriers generally must be filed in writing within the period set by the contract or bill of lading. Filing electronically gives both sides a structured record and speeds up investigation. Status is followed up with the 925 and 926.

How the EDI 920 worksDiagram of the EDI 920 Loss or Damage Claim - General Commodities. Claimant (shipper, consignee or owner of the goods) sends it to transportation carrier. It usually follows 854. It is usually followed by 925, 926 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: F01 (Identification of Claim (Claimant Originated)) and the required F02 loop with F02 (Identification of Shipment). 2 optional loops are listed by their first segment.How the EDI 920 worksLoss or Damage Claim - General Commodities: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS854Shipment DeliveryDiscrepancy InformationEDI 920SENDERClaimant (shipper,consignee or owner ofthe goods)RECEIVERTransportation carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY925Claim Tracer926Claim Status Report andTracer Reply997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code GCGS … GETransaction set 920ST … SEHEADINGF01Identification of Claim (Claimant Originated)Required loop F02 · repeats up to 9,999F02Identification of Shipment+ 2 optional loops, starting with:N1F09Blue 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 920. Your trading partner's implementation guide adds its own requirements.
How the EDI 920 worksDiagram of the EDI 920 Loss or Damage Claim - General Commodities. Claimant (shipper, consignee or owner of the goods) sends it to transportation carrier. It usually follows 854. It is usually followed by 925, 926 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: F01 (Identification of Claim (Claimant Originated)) and the required F02 loop with F02 (Identification of Shipment). 2 optional loops are listed by their first segment.How the EDI 920 worksLoss or Damage Claim - General Commodities:who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWS854Shipment Delivery DiscrepancyInformationEDI 920SENDERClaimant(shipper,consignee orowner of thegoods)RECEIVERTransportationcarrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY925Claim Tracer926Claim Status Report and Tracer Reply997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code GC (GS … GE)Transaction set 920 (ST … SE)HEADINGF01Identification of Claim(Claimant Originated)Required loop F02 · repeats up to9,999F02Identification of Shipment+ 2 optional loops, starting with:N1F09Blue 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 920. Your trading partner'simplementation guide adds its own requirements.

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

  • Filing a claim for goods lost in transit
  • Filing a claim for damaged freight
  • Supporting claims with shipment and value details

Where it fits in the document flow

Usually follows 854 Shipment Delivery Discrepancy Information
This document 920 Loss or Damage Claim - General Commodities
Usually followed by 925 Claim Tracer926 Claim Status Report and Tracer Reply997 Functional Acknowledgment

Structure

Mandatory segments in the 920 (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
  • F01
  • N1
  • F02
  • F09
  • SE

Practical example

The 920 in practice

A pallet of electronics is delivered crushed, and the consignee notes the damage on the delivery receipt. The shipper files a 920 with the carrier referencing the bill of lading and pro number, describing the damaged items, their invoice value and the amount claimed. The carrier opens a claim file and later reports its decision with a 926.

Implementation

Implementation considerations for the 920

  • File within the time limits in the contract or bill of lading.
  • Reference the shipment exactly and document the loss or damage.
  • Support the amount claimed with invoice values.
  • Track each claim until it is paid or declined.

How ECOM helps

Automate the 920 with ECOM

Industry

Trucking and Transportation

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

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

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

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

Request a Demo Contact us