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 · Healthcare and insurance

EDI 124 Vehicle Damage

The X12 document used to exchange vehicle damage estimates and repair cost details between insurers, agents, repairers and others.

Sent by
Repairer, appraiser or insurer
Received by
Insurer, agent, repairer or financial institution
Standard
ANSI ASC X12

What is an EDI 124?

The EDI 124 Vehicle Damage is the ANSI X12 transaction set that provides a flow of vehicle damage information between property and casualty insurance companies, independent agents, service providers, information providers, self-insurers and financial institutions. Its business functions are estimating vehicle damage and reporting in detail the parts and labor costs of repairing it.

After an accident, an appraiser or body shop estimates the damage and the insurer approves the repair. Exchanging the estimate in structured form lets insurers check parts prices and labor times automatically and process claims faster.

How the EDI 124 worksDiagram of the EDI 124 Vehicle Damage. Repairer, appraiser or insurer sends it to insurer, agent, repairer or financial institution. 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) and the required 2000 loop with NM1 (Individual or Organizational Name) and detail: the required 3000 loop with LX (Transaction Set Line Number), the required 3200 loop with LM (Code Source Information) and LQ (Industry Code Identification) and the required 3300 loop with VEH (Vehicle Information) and the required 3330 loop with N9 (Extended Reference Information). 6 optional loops are listed by their first segment.How the EDI 124 worksVehicle Damage: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 124SENDERRepairer, appraiser orinsurerRECEIVERInsurer, agent,repairer or financialinstitution997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code VDGS … GETransaction set 124ST … SEHEADINGBGNBeginning SegmentRequired loop 2000 · repeats many timesNM1Individual or Organizational Name+ 1 optional loop, starting with:SUPDETAILRequired loop 3000 · repeats many timesLXTransaction Set Line NumberRequired loop 3200 · repeats many timesLMCode Source InformationLQIndustry Code IdentificationRequired loop 3300 · repeats many timesVEHVehicle InformationRequired loop 3330 · repeats many timesN9Extended Reference Information+ 5 optional loops, starting with:SUPVATNM1LMDLBlue 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 124. Your trading partner's implementation guide adds its own requirements.
How the EDI 124 worksDiagram of the EDI 124 Vehicle Damage. Repairer, appraiser or insurer sends it to insurer, agent, repairer or financial institution. 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) and the required 2000 loop with NM1 (Individual or Organizational Name) and detail: the required 3000 loop with LX (Transaction Set Line Number), the required 3200 loop with LM (Code Source Information) and LQ (Industry Code Identification) and the required 3300 loop with VEH (Vehicle Information) and the required 3330 loop with N9 (Extended Reference Information). 6 optional loops are listed by their first segment.How the EDI 124 worksVehicle Damage: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 124SENDERRepairer,appraiser orinsurerRECEIVERInsurer, agent,repairer orfinancialinstitution997 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 VD (GS … GE)Transaction set 124 (ST … SE)HEADINGBGNBeginning SegmentRequired loop 2000 · repeatsmany timesNM1Individual orOrganizational Name+ 1 optional loop, starting with:SUPDETAILRequired loop 3000 · repeatsmany timesLXTransaction Set LineNumberRequired loop 3200 · repeatsmany timesLMCode SourceInformationLQIndustry CodeIdentificationRequired loop 3300 · repeatsmany timesVEHVehicle InformationRequired loop 3330 ·repeats many timesN9Extended ReferenceInformation+ 5 optional loops, starting with:SUPVATNM1LMDLBlue 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 124. Your trading partner'simplementation guide adds its own requirements.

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

  • Sending a damage estimate to an insurer
  • Reporting parts and labor for a repair
  • Supplementing an estimate after hidden damage is found

Where it fits in the document flow

This document 124 Vehicle Damage
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 124 (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
  • SUP
  • NM1
  • LX
  • LM
  • LQ
  • VEH
  • VAT
  • AMT
  • N9
  • DL
  • SE

Practical example

The 124 in practice

A body shop assesses a car after a collision. It sends the insurer a 124 with the vehicle identification number, the damaged areas, the parts to replace with prices, the labor hours and paint costs. The insurer's claims system checks the estimate against its guidelines and authorizes the repair.

Implementation

Implementation considerations for the 124

  • Use the parts and labor references insurers rely on.
  • Identify the vehicle by its vehicle identification number.
  • Send supplements for damage found during repair.
  • Protect claimants' personal data under applicable law.

How ECOM helps

Automate the 124 with ECOM

Industry

Financial Services

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

Industry

Automotive

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

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related healthcare and insurance documents

All 31 healthcare and insurance documents

Need help with the EDI 124?

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

Request a Demo Contact us