Submit life insurance applications using ACORD 103 XML standard

domain: insurance-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Obtain the ACORD Life and Annuity (LA) 103 New Business Submission specification from the ACORD member portal at acord.org; the ACORD 103 transaction is an XML-based standard for submitting proposed life insurance policy data from a distribution system to a carrier.
  2. Construct the ACORD 103 XML document using the TXLife wrapper: populate TXLifeRequest with OLifE (the life object hierarchy), including Party (proposed insured, owner, beneficiary), Holding (policy structure), and Coverage (face amount, plan code, rider list) elements.
  3. Map application question responses (including reflexive/knock-out questions) to the ACORD XML QuestionInfo elements; use the ACORD-standardized eLabels to tag each question for carrier interoperability.
  4. POST the XML payload to the carrier's new business submission endpoint (each carrier implements its own endpoint; obtain the URL, auth method, and any carrier extensions from the carrier's implementation guide) with Content-Type: application/xml.
  5. Parse the TXLifeResponse: check OLifE/TransResult/ResultCode for success (1) or error (4); extract the carrier's application reference number from ActivityStatus for tracking.
  6. Monitor the application status by submitting periodic 228 (status inquiry) transactions or by subscribing to the carrier's status callback webhook until the application reaches an underwriting decision.

Known gotchas

Related routes

Implement an ACORD txlife XML new business application submission for term life insurance
acord.org · 6 steps · unrated
Map a new-business insurance submission into ACORD's P&C XML standard for transmission to a carrier.
acord.org · 6 steps · unrated
Implement an ACORD 25 Certificate of Insurance issuance API integration with dynamic certificate holder handling
insurance-general · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans