Within the global reinsurance and specialty market, data exchange underpins every transaction — from placement through to settlement.
Across this scope, three distinct ACORD GRLC (Global Reinsurance & Large Commercial) message flows define how the market operates: standardized Placing, Accounting and Claims. Each is at a different point in its evolution, and understanding where each sits today is essential context for what comes next.
For Accounting and Claims, the operative data standard is XML/SOAP only, with JSON complements actively in development. For Placing, JSON is the primary standard, already live and generating significant interest across the market. XML placing implementations exist, but are limited to specific niche use cases.
The global reinsurance and specialty market is navigating a period of deliberate, managed evolution. XML/SOAP has served the market well; it is robust, well understood, and the foundation of substantial existing investment. But technology has moved on, developer ecosystems have shifted, and the market's tolerance for integration friction has declined.
The question is no longer whether the market needs to evolve its messaging infrastructure. The question is how to do it without breaking what already works.
ACORD's answer is clear: XML and JSON will coexist, allowing the market to modernise at its own pace while protecting existing integrations.
ACORD's dual-standard approach lets carriers and brokers evolve on their own terms — protecting existing XML investments while opening the door to a faster, simpler, and more connected market. The market shouldn't have to choose between protecting past investment and enabling future capability. The dual-standard approach ensures it doesn't have to.
The Case for JSON - In Plain Terms
JSON (JavaScript Object Notation) is not a new technology. It is the dominant format of the modern web, natively aligned with RESTful APIs, microservices, and event-driven architectures. It is what today's developers build with, and what modern platforms expect.
For the reinsurance and large commercial market, this matters for three specific reasons:
1. Payload efficiency. The ACORD JSON Standards have been modified to allow partial payloads, meaning only the data relevant to a specific business intent (e.g. Quote Request, Claim Advice, Endorsement) is transmitted. The XML Standard, by contrast, was designed to require full schema transmission even for minor changes, increasing message size, processing overhead, and latency. In high-volume environments, this is not just a minor inefficiency, but a substantial structural cost.
2. Developer availability. The pool of professionals with deep XML/SOAP expertise is shrinking, while expertise in JSON and REST is broad and continuing to expand. Organisations that build new integrations on XML face a compounding talent problem, higher implementation costs, and longer timelines, while depending upon a shrinking specialist base.
3. ePlacing is JSON-only. ACORD's ePlacing Standard, is built exclusively on JSON. Earlier Placing XML implementations were niche, limited to specific counterparties or use cases, and have not evolved into a broader market standard. With v1.5, ePlacing formally progresses as a JSON-only capability. Organisations that defer engagement with JSON are not postponing a future transition — they are opting out of an active and expanding segment of the market today.
XML vs. JSON: Different Strengths
XML/SOAP
ESTABLISHED STANDARD
|
JSON/REST
NEXT-GENERATION STANDARD
|
• Protects existing technology investments
• Remains fully supported for Accounting & Claims
• Full schema required per transmission
• Deep but shrinking developer talentpool
• Suited to longstanding counterparty relationships |
• Aligned with RESTful APIs and microservices
• Only option for ePlacing - adoption accelerating
• Partial payloads reduce bandwidth and latency
• Large, growing global developer base
• Enables async, event-driven architectures |
Interoperability Is the Strategic Prize
The most commercially significant impact of a dual-standard market is not technical, but rather about trading partner reach.
In a market where some organisations operate on XML and some move to JSON, the firms that implement both standards expand their addressable counterparty base. Those who implement only one create a constraint on whom they can transact with efficiently.
Organisations that move early to support both formats position themselves to trade with the widest possible range of partners — and to do so without the translation friction and manual workarounds that erode margins and introduce operational risk.
A Dual Path That Respects Reality
One of the most common objections to standards modernisation in insurance is the weight of existing investment. Carriers and brokers have spent years, and significant capital, building and refining XML-based integrations. The idea of wholesale replacement can be, understandably, unappealing.
ACORD's dual-standard approach addresses this directly. XML implementations are not
being deprecated. Firms can continue running XML for in-force books of business, while
onboarding new business onto JSON if they choose to. This means no forced disruption to existing operations.
This dual-standard approach of parallel operation, and incremental migration as and when it makes commercial sense, means the pace of change is yours to determine.
What This Means for You — Right Now
| •For (Re)Insurers |
• Assess your ePlacing exposure. If brokers in your target segments are moving to JSON-based ePlacing, your XML-only infrastructure may already be creating invisible friction in your trading relationships.
• Evaluate your integration roadmap. New system builds and platform upgrades are natural inflection points to introduce JSON capability without disrupting existing XML operations.
• Engage with the ACORD GRLC Technical Design Authority. The TDA group can advise on implementation sequencing, schema alignment, and counterparty coordination. |
| •For Brokers |
• Dual-standard capability is a competitive differentiator. Brokers who can
trade with both XML- and JSON-based carriers maximise their carrier panel and minimise the risk of being locked out of future market infrastructure.
• ePlacing is live and growing. Early movers on JSON/ePlacing are establishing workflow and counterparty relationships that will compound in value as adoption broadens.
• Existing XML workflows are protected. There is no cliff edge. A phased approach allows parallel operation throughout the transition period.
|
The Bottom Line
| 2 |
0 |
∞ |
Fully supported standards
— XML and JSON —
operating in parallel |
Forced cutover —
transition entirely on your terms and timeline |
Counterparty reach for firms implementing both formats |
The global reinsurance and large commercial market is not facing a binary choice between legacy and modernity. ACORD's dual-standard approach is precisely designed to eliminate that dilemma.
JSON offers a simplified, scalable, and future-ready messaging architecture aligned with where the technology industry and the talent market are already heading. XML remains fully supported, protecting investments that have taken years to build. Together, they give the market something rare in large-scale technology transitions: genuine flexibility.
Whether you are a new entrant building from a clean slate, an established carrier managing a complex legacy estate, or a broker seeking to maximise your trading partner footprint, the path forward exists. The question is simply how quickly you choose to walk it.
Ready to explore what JSON adoption looks like for your organisation?
ACORD's GRLC Technical Design Authority supports carriers and brokers at every stage of the journey. Reach out to GRLC@acord.org learn more about the ACORD Data Standards programme, ePlacing, accounting and claims, and the resources available to support your transition.
by Adnan Nasar-Ullah Lead BA Consultant, ACORD GRLC