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 252 Insurance Producer Administration

The X12 document used to transmit insurance producer information, such as licensing and appointments, among insurers and distributors.

Sent by
Insurance company or distributor
Received by
Distributor or insurance company
Standard
ANSI ASC X12

What is an EDI 252?

The EDI 252 Insurance Producer Administration is the ANSI X12 transaction set used to transmit insurance producer information, such as licensing and appointment data and background information, among insurance companies and distributors, such as agents and brokers.

Producers must be licensed in each state and appointed by each insurer whose products they sell. Insurers must check licenses and maintain appointments before paying commissions. Exchanging producer data electronically keeps both sides' records aligned and supports regulatory compliance. Terminations should be reported as promptly as new appointments.

How the EDI 252 worksDiagram of the EDI 252 Insurance Producer Administration. Insurance company or distributor sends it to distributor or insurance company. It usually starts the exchange. It is usually followed by 256 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required N1 loop with N1 (Party Identification) and the required ENT loop with ENT (Entity) and ASI (Action or Status Indicator). 7 optional loops are listed by their first segment.How the EDI 252 worksInsurance Producer Administration: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 252SENDERInsurance company ordistributorRECEIVERDistributor orinsurance company997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY256Periodic Compensation997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code IEGS … GETransaction set 252ST … SEHEADINGBGNBeginning Segment+ 1 optional loop, starting with:NM1DETAILRequired loop N1 · repeats many timesN1Party IdentificationRequired loop ENT · repeats many timesENTEntityASIAction or Status Indicator+ 6 optional loops, starting with:NM1LXUCLICACTPWKBlue 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 252. Your trading partner's implementation guide adds its own requirements.
How the EDI 252 worksDiagram of the EDI 252 Insurance Producer Administration. Insurance company or distributor sends it to distributor or insurance company. It usually starts the exchange. It is usually followed by 256 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required N1 loop with N1 (Party Identification) and the required ENT loop with ENT (Entity) and ASI (Action or Status Indicator). 7 optional loops are listed by their first segment.How the EDI 252 worksInsurance Producer Administration: who sendsit, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 252SENDERInsurancecompany ordistributorRECEIVERDistributor orinsurancecompany997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY256Periodic Compensation997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code IE (GS … GE)Transaction set 252 (ST … SE)HEADINGBGNBeginning Segment+ 1 optional loop, starting with:NM1DETAILRequired loop N1 · repeats manytimesN1Party IdentificationRequired loop ENT · repeatsmany timesENTEntityASIAction or StatusIndicator+ 6 optional loops, starting with:NM1LXUCLICACTPWKBlue 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 252. Your trading partner'simplementation guide adds its own requirements.

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

  • Requesting producer appointments with insurers
  • Sharing license information
  • Terminating appointments

Where it fits in the document flow

This document 252 Insurance Producer Administration
Usually followed by 256 Periodic Compensation997 Functional Acknowledgment

Structure

Mandatory segments in the 252 (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
  • NM1
  • N1
  • ENT
  • ASI
  • N9
  • N3
  • LX
  • REF
  • UC
  • LIC
  • LIN
  • ACT
  • SPA
  • PWK
  • EFI
  • BIN
  • SE

Practical example

The 252 in practice

A brokerage hires an agent licensed in three states and asks an insurer to appoint her. It sends a 252 with her licenses, background information and the products she will sell. The insurer verifies the licenses, files the appointments and confirms that she can submit business.

Implementation

Implementation considerations for the 252

  • Verify licenses before appointments take effect.
  • Keep appointment records current, including terminations.
  • Protect producers' personal data under applicable law.
  • Follow each state's appointment filing rules.

How ECOM helps

Automate the 252 with ECOM

Industry

Financial Services

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

Solution

Trading Partner Onboarding

EDI certification and automation onboarding for customers, suppliers and carriers, by whichever method each partner can support.

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

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

Request a Demo Contact us