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 924 Loss or Damage Claim - Motor Vehicle

The X12 document used to file a legal claim with a carrier for loss of, or damage to, a motor vehicle.

Sent by
Vehicle manufacturer or owner
Received by
Rail or motor carrier that transported the vehicle
Standard
ANSI ASC X12

What is an EDI 924?

The EDI 924 Loss or Damage Claim - Motor Vehicle is the ANSI X12 transaction set used to file a legal claim with a carrier for loss of, or damage to, a motor vehicle. It identifies the vehicle by its vehicle identification number, the shipment, the damage and the repair costs claimed.

Finished vehicles move from plants by rail and truck to dealers, and damage found at inspection is claimed against the carrier responsible. The 924 carries vehicle-specific detail, such as damage area and type codes, that the general commodities claim (920) does not.

How the EDI 924 worksDiagram of the EDI 924 Loss or Damage Claim - Motor Vehicle. Vehicle manufacturer or owner sends it to rail or motor carrier that transported the vehicle. It usually follows 928. 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)), F6X (Identification (Automotive)) and F07 (Auto Claim Detail). 0 optional loops are listed by their first segment.How the EDI 924 worksLoss or Damage Claim - Motor Vehicle: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS928Automotive InspectionDetailEDI 924SENDERVehicle manufactureror ownerRECEIVERRail or motor carrierthat transported thevehicle997 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 groupGS … GETransaction set 924ST … SEHEADINGF01Identification of Claim (Claimant Originated)F6XIdentification (Automotive)F07Auto Claim 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 924. Your trading partner's implementation guide adds its own requirements.
How the EDI 924 worksDiagram of the EDI 924 Loss or Damage Claim - Motor Vehicle. Vehicle manufacturer or owner sends it to rail or motor carrier that transported the vehicle. It usually follows 928. 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)), F6X (Identification (Automotive)) and F07 (Auto Claim Detail). 0 optional loops are listed by their first segment.How the EDI 924 worksLoss or Damage Claim - Motor Vehicle: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWS928Automotive Inspection DetailEDI 924SENDERVehiclemanufacturer orownerRECEIVERRail or motorcarrier thattransported thevehicle997 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 (GS … GE)Transaction set 924 (ST … SE)HEADINGF01Identification of Claim(Claimant Originated)F6XIdentification (Automotive)F07Auto Claim 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 924. Your trading partner'simplementation guide adds its own requirements.

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

  • Claiming repair costs for vehicles damaged in transit
  • Claiming for vehicles lost or destroyed
  • Supporting claims with inspection results

Where it fits in the document flow

Usually follows 928 Automotive Inspection Detail
This document 924 Loss or Damage Claim - Motor Vehicle
Usually followed by 925 Claim Tracer926 Claim Status Report and Tracer Reply997 Functional Acknowledgment

Structure

Mandatory segments in the 924 (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
  • F6X
  • F07
  • SE

Practical example

The 924 in practice

A dealer's inspection finds a scratched door on a new vehicle delivered by truck. The manufacturer files a 924 with the carrier, giving the vehicle identification number, the shipment, the damage area and type codes from the inspection and the repair cost. The carrier reviews the claim against its delivery records and pays the repair cost.

Implementation

Implementation considerations for the 924

  • Use the vehicle identification number and standard damage codes.
  • Link claims to the inspection reports (928) that found the damage.
  • File within the time limits set by contract.
  • Track claim status with the carrier through to settlement.

How ECOM helps

Automate the 924 with ECOM

Industry

Automotive

Schedules, ship notices, labels, self-billing and multi-plant routing for automotive suppliers.

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.

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

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

Request a Demo Contact us