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 112 Property Damage Report

The X12 document used to provide property damage information between property and casualty insurers, agents and service providers.

Sent by
Adjuster, contractor, agent or service provider
Received by
Property and casualty insurer or agent
Standard
ANSI ASC X12

What is an EDI 112?

The EDI 112 Property Damage Report is the ANSI X12 transaction set used to provide property damage information between property and casualty insurance companies, independent agents, and service and information providers. The information includes the damage found, the repairs needed and their costs.

After a loss such as a storm or fire, insurers rely on adjusters and contractors to assess the damage. Receiving the assessment as structured data lets the insurer compare it with policy coverage and pricing guidelines automatically and settle claims faster, especially after catastrophes with many claims.

How the EDI 112 worksDiagram of the EDI 112 Property Damage Report. Adjuster, contractor, agent or service provider sends it to property and casualty insurer or agent. It usually follows 272. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required 2000 loop with HL (Hierarchical Level). 5 optional loops are listed by their first segment.How the EDI 112 worksProperty Damage Report: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS272Property and CasualtyLoss NotificationEDI 112SENDERAdjuster, contractor,agent or serviceproviderRECEIVERProperty and casualtyinsurer or agent997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code PQGS … GETransaction set 112ST … SEHEADINGBGNBeginning Segment+ 1 optional loop, starting with:SUPDETAILRequired loop 2000 · repeats many timesHLHierarchical Level+ 4 optional loops, starting with:LMIIINM1CIDBlue 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 112. Your trading partner's implementation guide adds its own requirements.
How the EDI 112 worksDiagram of the EDI 112 Property Damage Report. Adjuster, contractor, agent or service provider sends it to property and casualty insurer or agent. It usually follows 272. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required 2000 loop with HL (Hierarchical Level). 5 optional loops are listed by their first segment.How the EDI 112 worksProperty Damage Report: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS272Property and Casualty Loss NotificationEDI 112SENDERAdjuster,contractor,agent or serviceproviderRECEIVERProperty andcasualty insureror agent997 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 PQ (GS … GE)Transaction set 112 (ST … SE)HEADINGBGNBeginning Segment+ 1 optional loop, starting with:SUPDETAILRequired loop 2000 · repeatsmany timesHLHierarchical Level+ 4 optional loops, starting with:LMIIINM1CIDBlue 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 112. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting property damage assessments
  • Sending repair estimates to insurers
  • Supplementing reports after further damage is found

Where it fits in the document flow

Usually follows 272 Property and Casualty Loss Notification
This document 112 Property Damage Report
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 112 (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
  • HL
  • LM
  • SLN
  • III
  • CID
  • SE

Practical example

The 112 in practice

After a hailstorm, an independent adjuster inspects a damaged roof. The adjuster's software sends the insurer a 112 with the damaged areas, the materials and labor required and the estimated cost. The insurer checks the estimate against its pricing database and pays the claim.

Implementation

Implementation considerations for the 112

  • Use the damage and repair codes insurers expect.
  • Support reports with photographs where required.
  • Send supplements when additional damage is found.
  • Link reports to the claim number from the loss notification.

How ECOM helps

Automate the 112 with ECOM

Industry

Financial Services

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

Solution

B2B Integration

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

Solution

Intelligent Document Processing

Automate data capture from PDFs, emails and spreadsheets with validation and human review.

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

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

Request a Demo Contact us