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.
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.
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.
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.
Parse the TXLifeResponse: check OLifE/TransResult/ResultCode for success (1) or error (4); extract the carrier's application reference number from ActivityStatus for tracking.
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
ACORD 103 XML schema versions are not backward compatible; carriers often implement a specific schema version (e.g., 2.20.01) — submitting a payload built against a different version causes schema validation failures even if the data is logically correct.
Carriers extend the ACORD standard with proprietary OLifE extensions for their specific products; a compliant ACORD 103 document may still be rejected if carrier-specific required extensions are missing.
Life insurance applications involve sensitive health and financial data; ensure all transmission is over TLS 1.2 or higher and that PII fields (SSN, date of birth, medical history) are handled in compliance with applicable state privacy regulations.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp