Implement an ACORD txlife XML new business application submission for term life insurance
domain: acord.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain the ACORD txlife schema for the applicable transaction (TXLife 103 New Business Application) from the ACORD standards library
Construct the TXLife XML payload: populate Party, Relation, Holding, Policy, Coverage, and LifeParticipant blocks with applicant and coverage data
Include the required underwriting data blocks: height, weight, tobacco use, existing coverage amounts, and medical question answers in the OLifE extension
Submit the XML to the carrier's life new business API endpoint or ACORD-compliant integration hub and capture the transaction ID
Parse the TXLife 104 response to determine whether the application was accepted, placed in underwriting review, or rejected with requirements
Handle outstanding requirements (labs, attending physician statements, inspection reports) by updating the application and resubmitting as a TXLife 105 change transaction
Known gotchas
txlife OLifE extensions are heavily vendor-customized; carriers frequently add proprietary elements outside the standard schema, and your XML parser must be tolerant of unknown elements
Life new business workflows are often stateful and multi-step; the transaction ID from the initial submission must be preserved and referenced in all subsequent change and status transactions
ACORD txlife schema versions (e.g., 2.x vs 3.x) are not backward-compatible; confirm the carrier's supported schema version before building the message structure
Give your agent this knowledge — and 15,600+ 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?