X12 273 — Insurance/Annuity Application Status
The 273 responds to a 267 application: underwriting status (received, in underwriting, approved, rated, declined, withdrawn) and reasons if applicable.
Purpose
The 273 documents the progress of a 267 application through the carrier underwriting pipeline. It carries status, change date, reasons (medical, financial, occupation), outstanding requirements (paramedical exam, APS).
It is exchanged periodically between 267 issue and final policy issue (a 111). Acknowledged by 997. Multiple 273s may pace a single application across stages.
Envelope structure
The 273 travels within the three X12 envelope levels (ISA/IEA,
GS/GE with functional group IS, and ST/SE).
Didactic example in release 004010:
ISA*00* *00* *ZZ*LIFECARRIER *ZZ*BROKERFIRM *260515*1500*U*00401*000000273*0*P*>~
GS*IS*LIFECARRIER*BROKERFIRM*20260515*1500*1*X*004010~
ST*273*0001~
BGN*00*STATUS-APP-7799*20260515~
NM1*IL*1*SMITH*JOHN*A***34*SSN-LAST4-5678~
N1*IN*ACME LIFE INSURANCE*24*EIN-CARRIER~
REF*ZZ*APPLICATION-7799~
DTM*090*20260515~
MSG*UNDERWRITING - PARAMEDICAL EXAM REQUIRED~
SE*8*0001~
GE*1*1~
IEA*1*000000273~ Common segments
- Header —
ST,BGN. - Applicant —
NM1*IL. - Carrier —
N1*IN. - Application —
REF*ZZ(267 application reference). - Status —
DTM*090(status date),MSGorSTC(status code),REF*ZZfor outstanding requirement. - Summary —
SE.
Common pitfalls
- Stable reference:
REF*ZZmust echo theBGN02of the 267; otherwise the producer cannot correlate statuses. - Decline reason: a decline must name the reason (medical, financial, occupation) to enable product redirection; an opaque decline damages the relationship.
- Multiple status updates: several 273s per application is normal — the producer automation must derive current state from latest date, not first received.
Related transactions
Documentation
The code 273 and the name Insurance/Annuity Application Status 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.