ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 186 — Insurance Underwriting Requirements Reporting

The 186 documents the underwriting requirements for an insurance policy: medical attachments, inspections, third-party reports requested by the carrier before issuance.

Purpose

The 186 carries the list of attachments and examinations the carrier (life, health, P&C) expects to finalize underwriting: medical exam, residential inspection report, Motor Vehicle Records, financial worksheet. It is typically issued by the underwriter to the distributor (agent, broker), who forwards to the proposed insured and drives the collection.

It is part of the ACORD / NAIC EDI underwriting cycle: 186 (requirements request), responses as documents (PDF, lab results), then policy issuance or decline. The 186 is acknowledged by 997 and has no dedicated business response — the response is the delivery of the requirements themselves.

Envelope structure

The 186 travels within the three X12 envelope levels (ISA/IEA, GS/GE with functional group UR, and ST/SE). Didactic example in release 004010:

x12 example-186.x12 
ISA*00*          *00*          *ZZ*ACMEINSCO     *ZZ*ACMEBROKER    *260514*1015*U*00401*000000186*0*P*>~
GS*UR*ACMEINSCO*ACMEBROKER*20260514*1015*1*X*004010~
ST*186*0001~
BGN*00*UR-2026-0019*20260514~
NM1*IL*1*DOE*JANE****SY*123-45-6789~
NM1*PR*2*ACME LIFE INSURANCE CO*****46*INS-9087~
LX*1~
REF*0F*POLICY-PROPOSED-7711~
LQ*BB*PARAMED EXAM*~
DTM*002*20260601~
LX*2~
REF*0F*POLICY-PROPOSED-7711~
LQ*BB*ATTENDING PHYSICIAN STATEMENT*~
DTM*002*20260615~
SE*12*0001~
GE*1*1~
IEA*1*000000186~

Common segments

  • Header — ST, BGN (Beginning Segment), DTM (request date).
  • Parties — NM1*IL (Insured Party), NM1*PR (Provider / Underwriter), NM1*1P (Producer / Agent).
  • Requirements — LX loop with REF*0F (policy ID), LQ (Requirement Type), DTM*002 (due date).
  • Details — MSG for free-text notes, PWK for non-EDI attachments expected.
  • Summary — SE.

Common pitfalls

  • PHI and HIPAA: if the 186 documents a US health policy, it becomes PHI (Protected Health Information) and triggers HIPAA — in-transit encryption (AS2 or SFTP), Business Associate Agreement with the broker.
  • Requirement code: the LQ02 code list is governed by ACORD; inventing a value breaks downstream broker automation. Always align with the ACORD AL3 or XML equivalent.
  • Due date vs issue date: DTM*002 is the expected delivery date of the requirement, not the 186 issue date. Mixing them up causes premature underwriting timeouts.

Documentation

The code 186 and the name Insurance Underwriting Requirements Reporting 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.