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 272 Property and Casualty Loss Notification

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

Sent by
Agent, policyholder service or insurer
Received by
Insurer, service provider or industry bureau
Standard
ANSI ASC X12

What is an EDI 272?

The EDI 272 Property and Casualty Loss Notification is the ANSI X12 transaction set used to provide a flow of loss information between property and casualty insurance companies, agents, service providers and industry bureaus.

The first notice of loss starts the claim: who was involved, what happened, when and where, and what was damaged. Agents report losses for their clients, and insurers share loss data with bureaus for statistics and fraud detection. Electronic notification lets the insurer assign an adjuster immediately.

How the EDI 272 worksDiagram of the EDI 272 Property and Casualty Loss Notification. Agent, policyholder service or insurer sends it to insurer, service provider or industry bureau. It usually starts the exchange. It is usually followed by 112 and 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 LID (Loss Information Description). 7 optional loops are listed by their first segment.How the EDI 272 worksProperty and Casualty Loss Notification: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 272SENDERAgent, policyholderservice or insurerRECEIVERInsurer, serviceprovider or industrybureau997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY112Property Damage Report997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code LNGS … GETransaction set 272ST … SEHEADINGBGNBeginning Segment+ 2 optional loops, starting with:N9NM1DETAILRequired loop 2000 · repeats many timesLIDLoss Information Description+ 5 optional loops, starting with:LIEN9PWKNM1REFBlue 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 272. Your trading partner's implementation guide adds its own requirements.
How the EDI 272 worksDiagram of the EDI 272 Property and Casualty Loss Notification. Agent, policyholder service or insurer sends it to insurer, service provider or industry bureau. It usually starts the exchange. It is usually followed by 112 and 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 LID (Loss Information Description). 7 optional loops are listed by their first segment.How the EDI 272 worksProperty and Casualty Loss Notification: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 272SENDERAgent,policyholderservice orinsurerRECEIVERInsurer, serviceprovider orindustry bureau997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY112Property Damage Report997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code LN (GS … GE)Transaction set 272 (ST … SE)HEADINGBGNBeginning Segment+ 2 optional loops, starting with:N9NM1DETAILRequired loop 2000 · repeatsmany timesLIDLoss InformationDescription+ 5 optional loops, starting with:LIEN9PWKNM1REFBlue 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 272. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 272, 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 272 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 a first notice of loss to an insurer
  • Sharing loss data with industry bureaus
  • Updating loss details

Where it fits in the document flow

This document 272 Property and Casualty Loss Notification
Usually followed by 112 Property Damage Report997 Functional Acknowledgment

Structure

Mandatory segments in the 272 (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
  • N9
  • NM1
  • LID
  • LIE
  • PWK
  • REF
  • VEH
  • LX
  • K2
  • NX1
  • LQ
  • III
  • PIN
  • BCI
  • SE

Practical example

The 272 in practice

A client calls an independent agent after a kitchen fire. The agent's system sends the insurer a 272 with the policy, the date and cause of loss, a description of the damage and contact details. The insurer opens a claim and assigns an adjuster within the hour.

Implementation

Implementation considerations for the 272

  • Report losses promptly, as policies require.
  • Include contact details so adjusters can reach the client.
  • Protect claimants' personal data under applicable law.
  • Use loss cause codes the insurer recognizes.

How ECOM helps

Automate the 272 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

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 healthcare and insurance documents

All 31 healthcare and insurance documents

Need help with the EDI 272?

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

Request a Demo Contact us