Implement the ACORD XML Reference Architecture message envelope for inter-system policy data exchange
domain: acord.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Download the ACORD XML schema package for the applicable line of business (P&C, Life, Surety) from the ACORD standards library
Construct the outer SignonRq/SignonRs envelope with the required MsgUID, SignonPswd, and ClientApp blocks
Embed the business transaction payload (e.g., PolicyAddRq, PolicyChgRq) inside the ACORD envelope following the namespace conventions
Validate the composed XML against the ACORD XSD using a schema-aware validator before transmission
Configure mutual TLS or WS-Security headers as required by the receiving system's security profile
Parse the response envelope, extract status codes and error messages, and map them to your application error handling
Known gotchas
ACORD XML schemas have versioned namespaces; mixing schema versions in a single document causes validation failures that are difficult to trace
The ACORD Reference Architecture does not mandate a transport protocol; confirm whether the partner uses HTTPS REST, SOAP, or AS2 before building the client
MsgUID must be globally unique per message; reusing IDs can cause idempotency issues on the receiving system
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?