ACORD is the insurance industry's data standards body and the author of the formats that have moved insurance data since the 1970s — AL3 flat files, ACORD XML, and the newer ACORD Data Standards and NGDS programme. Inside the industry the standards are genuinely load-bearing. As machine-readable interfaces available to anyone outside it, they are close to invisible.
ACORD
ACORD is the oldest continuously-used data standard in this catalog, and the most instructive example of a standard that works commercially while failing as public infrastructure.
- AL3 - The fixed-format flat-file standard that still moves policy download, claims download and direct-bill commission between carriers and agency management systems.
- ACORD XML - The message-based generation, widely deployed in life and annuity through channels like CLIEDIS.
- NGDS and ACORD Data Standards - The modern programme, including work on APIs and the GRLC data standards used in the London Market.
- Membership-gated - The specifications are available to members. An application, or an agent, cannot simply fetch and implement them the way it can fetch FHIR or CAMARA.
- Forms, not endpoints - The industry’s shared mental model of ACORD is a form, which is why some vendors now treat an ACORD form as unstructured input to extract from rather than a contract to implement.
Scoring the sector for the insurance Sector Reports found ACORD live in a production contract at one US company — moving AL3 as batch files through IVANS, a mailbox transport rather than an interface — displaced entirely by CIECA in auto physical damage, and genuinely present inside a machine-readable contract at exactly one company anywhere: Whitespace in the London Market, which did not adopt ACORD so much as author the JSON Market Reform Contract and donate it. Compare FHIR, which is openly defined, government and industry backed, and callable by anyone. FHIR is callable; ACORD is licensable, and that difference is the whole difference.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of US Insurance APIs
Live in a production contract at exactly one US company — moving AL3 as batch files through a mailbox transport — and displaced outright by CIECA in auto physical damage.
The State of UK Insurance APIs
Genuinely present inside a machine-readable contract at one company in the world, and it is in London: the standard followed the API rather than the API following the standard.
The State of Australian Insurance APIs
The chairman of ACORD's board runs an Australian broker network whose entire 311-URL web estate mentions ACORD once, in his own biography.
The State of Canadian Insurance APIs
Carries production data in exactly one place across forty Australian and Canadian companies — through CLIEDIS, a standards-body channel, not any carrier's API product.
