X12 100 — Insurance Plan Description
The 100 transmits the description of an insurance plan — life, annuity, health, disability — from an insurer to a partner (reinsurer, broker, employer).
Purpose
The 100 documents the structure of an insurance plan: contract type (term life, whole life, universal, annuity), covered amounts, premiums, exclusions, riders. It supports product catalog transfer between a risk carrier and a distributor, or feeds an enrollment system.
It is used upstream of the underwriting cycle: before a 252 (producer admin) or 267 (individual application) is exchanged, the carrier broadcasts the 100 to align distributors on the plan being sold. Acknowledged by 997.
Envelope structure
The 100 travels within the three X12 envelope levels (ISA/IEA,
GS/GE with functional group IP, and ST/SE).
Didactic example in release 004010:
ISA*00* *00* *ZZ*LIFECARRIER *ZZ*BROKERFIRM *260515*0900*U*00401*000000100*0*P*>~
GS*IP*LIFECARRIER*BROKERFIRM*20260515*0900*1*X*004010~
ST*100*0001~
BGN*00*PLAN-2026-TLIFE-1099*20260515~
N1*IN*ACME LIFE INSURANCE*24*EIN-CARRIER~
REF*ZZ*PRODUCT-CODE-TLIFE-20Y~
DTM*090*20260601~
LX*1~
NTE*ZZ*TERM 20 YEARS - LEVEL PREMIUM~
SE*8*0001~
GE*1*1~
IEA*1*000000100~ Common segments
- Header —
ST,BGN(Beginning Segment). - Carrier —
N1*IN(Insurer),REF*ZZfor internal product code. - Effective date —
DTM*090(plan effective date). - Plan details — repeated
LXloop:NTEorMSGfor features,AMTfor premiums,QTYfor coverage limits. - Summary —
SE.
Common pitfalls
- Versioning: an insurance plan evolves — always carry a version in
REF; otherwise distributors sell a stale state. - State-by-state compliance: in the US, each state regulates its products; a plan filed in NY does not sell in CA without a dedicated 100.
- ACA vs non-ACA: for health, do not mix ACA-compliant plans with others in the same 100 — the enrollment system gets subsidies wrong.
Related transactions
Documentation
The code 100 and the name Insurance Plan Description are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.