Compendium

Financial / Regulatory / Insurance Interchange DSLs Family Index

15 min read

Financial / Regulatory / Insurance Interchange DSLs Family Index

type: language-family-index family: financial-regulatory languages_catalogued: 30 tags: [language-reference, family-index, financial-regulatory, fix, swift, iso20022, fpml, xbrl, acord, mismo, edifact, x12, sbe, cdm]

Financial / Regulatory / Insurance — Family Index

Family overview

The financial-services world runs on a small zoo of interchange languages — almost all of them XML or tag=value text formats — that describe trading messages, financial products, regulatory reports, and insurance data. They are domain-specific languages in the strict sense: each has a published schema or session protocol, a versioning regime, a conformance test suite, and (usually) an industry body that controls extension. Unlike general-purpose data formats, they encode rich domain semantics — a <swap> element in FpML expects ISDA Definitions terms; a pacs.008 message in ISO 20022 expects a structured creditor-agent identifier with a BIC. Getting the schema wrong does not just produce a parse error: it produces a failed payment, a rejected regulatory filing, or a mispriced trade.

The single largest event in this ecosystem in living memory completed on 22 November 2025, when SWIFT’s MT/MX coexistence period ended and ISO 20022 became mandatory for cross-border payments on the FINplus service (BNY end-of-coexistence note, May 2025; Payment Expert, Nov 2025). Legacy MT messages — MT103, MT202, MT202COV — are formally retired in favour of their pacs.008 / pacs.009 ISO 20022 equivalents, ending a 50-year run for the SWIFT MT format and (in principle) ending the era of unstructured remittance fields. The Fed migrated Fedwire Funds to ISO 20022 in July 2025 and FedNow has used ISO 20022 since launch (July 2023); CHIPS converted in 2025; CIPS in China was ISO 20022-native from inception in 2015. The November 2026 release will further harmonise with SWIFT/CHIPS by removing unstructured postal addresses (Federal Reserve Financial Services).

Trading lives on a parallel stack. FIX (Financial Information eXchange) remains the universal protocol for order and execution flow between buy-side, sell-side, and venues. FIX 4.4 (2003) is still the workhorse tag=value version most counterparties certify against, even though FIX 5.0 SP2 (2009) is technically the newest application-layer version; the latest activity is on Simple Binary Encoding (SBE) for low-latency feeds (CME MDP 3.0 was the first major adopter in December 2014; Euronext, Moscow Exchange, Binance Spot, and ICE followed). Native exchange protocols — Nasdaq’s OUCH for order entry, ITCH for market data, OPRA for options — sit alongside FIX where microseconds matter. FpML (FpML 5.13 is the current Recommendation as of 2024–25) and the FINOS Common Domain Model (CDM) split the derivatives-modelling world; ISDA’s Translate 2.0 shipped in Q4 2025 to bridge them (FpML site, CDM on FINOS).

Regulatory reporting and insurance ride yet a third stack. XBRL 2.1 (2003 spec) plus Inline XBRL (iXBRL, 2010 Recommendation) is mandatory for SEC operating-company filings, ESEF in the EU since 2021, and HMRC in the UK; the SEC EDGAR XBRL Guide was refreshed April 2026. The EBA / EIOPA Data Point Model (DPM 2.0, governed by the EBA / EIOPA / ECB DPM Alliance since April 2024) is the substrate beneath EU banking and Solvency II reporting templates (current EIOPA taxonomy 2.8.2, June 2025). ACORD owns insurance with its GRLC (Global Reinsurance & Large Commercial) Generation 2.0 standards launched April 2025, adding JSON alongside XML; MISMO 3.6.2 is the current US mortgage data standard, with ULDD layered on top for Fannie/Freddie deliveries. And the legacy EDIFACT + ANSI X12 EDI world refuses to die — X12 published version 008060 in January 2025 and is hosting a 2026 implementer-education programme — even as it gradually loses ground to API-based integration (X12 release schedule).

In our deep library

None of these formats has a standalone deep-library note — they sit beneath layered tooling rather than being programming languages in the Turing-complete sense. Cross-reference:

  • api-description — most modern incarnations of these formats are described via XML Schema, JSON Schema, OpenAPI, or AsyncAPI; ACORD GRLC Gen 2.0 explicitly added JSON-Schema implementations alongside XSD.
  • identity-auth-policy — financial APIs and SWIFTNet sit on heavy auth stacks (mTLS + BIC-based identity, FAPI 2.0 for Open Banking, OAuth/SAML for filer portals).
  • citation-formats — regulatory submissions cite legal authorities (CFR, MiFID II RTS, SFDR) that themselves use citation grammars catalogued there.
  • notation-spec — FIX Orchestra, FpML schema, and ISDA CDM Rosetta all rely on formal grammars / model-definition languages.
  • smart-contract — DeFi adjacent; ISDA CDM has an explicit “tokenised assets” working group and the boundary between CDM-modelled derivatives and on-chain instruments is increasingly thin.
  • stream-processing — ITCH, FIX, and SBE feeds are the canonical input topics for streaming engines; market data → Flink SQL → materialised view is the dominant 2026 microstructure-analytics pattern.
  • network-protocol-dsls — FIX (session layer), OUCH/ITCH (binary wire), and SBE all sit at the protocol-DSL boundary.

Tier 3 family table — Trading / market data

FormatFirst appearedOriginTypeStatus (2026)URL
FIX (Financial Information eXchange)1992 (FIX 2.7); 1993 first deployment between Fidelity and SalomonFIX Trading Community (industry consortium)Tag=value session protocol; ASCII; SOH-delimited fieldsActive — universal pre-trade / order / execution protocol; FIX 4.4 (2003) remains the workhorse despite FIX 5.0 SP2 (2009) being newerhttps://www.fixtrading.org/standards/
FIX 5.0 SP2 + Extension Packs2009 (5.0 SP2); EPs ongoingFIX Trading CommunityExtension Pack mechanism decouples application semantics from session layer (FIXT 1.1)Active as the spec frontier; 4.4 still dominates wirehttps://www.fixtrading.org/standards/fix-5-0-sp-2/
FIXML2001FIX Trading CommunityXML encoding of FIX application messagesActive but niche; used by some clearing houses and regulators (CFTC SDR submissions historically)https://www.fixtrading.org/standards/fixml-online/
FIX FAST (FIX Adapted for Streaming)2006FIX Trading CommunityBinary compressed encoding via templates + presence map; eliminates redundant tagsMaturing-out; largely displaced by SBE for new low-latency deploymentshttps://www.fixtrading.org/standards/fast-online/
Simple Binary Encoding (SBE)2013 RC; CME MDP 3.0 launched 7 Dec 2014FIX Trading Community (Real Logic / Martin Thompson reference impl)Binary, fixed-layout, zero-copy wire formatVery active — adopted by CME, Euronext, MOEX, ICE, Binance Spot; current spec 1.0 + SBE 2.0 RC work in progresshttps://www.fixtrading.org/standards/sbe-online/
FIX Orchestra2017 (1.0 RC); 1.1 RC2 published Nov 2024; 1.1 RC3 in progress 2025FIX Trading CommunityMachine-readable rules-of-engagement schema (Repository + DSL for session config, message flows, codesets)Active; the modern way to ship counterparty conformance specshttps://www.fixtrading.org/standards/fix-orchestra-standard/
OUCH (Nasdaq order entry)~2005 (Nasdaq INET integration); OUCH 5.0 currentNasdaqBinary, fixed-length-record order entry protocolActive — OUCH 5.0 / Nordic OUCH 5.02.6 (Nov 2025); minimum-latency Nasdaq order channelhttps://www.nasdaqtrader.com/content/technicalsupport/specifications/TradingProducts/Ouch5.0.pdf
ITCH (market data)2000Nasdaq (now widespread on non-Nasdaq venues too)Binary append-only message stream of full order-book events; UDP multicast typicalVery active — TotalView-ITCH 5.0; ITTO for options; ports adopted by BIST, MIAX, etc.https://www.nasdaqtrader.com/content/technicalsupport/specifications/dataproducts/NQTVITCHSpecification.pdf
OPRA (Options Price Reporting Authority feed)1976 (text); current binary OPRA-XL multicastOPRA LLC (US options exchanges’ SIP)Consolidated US options NBBO + trades feed; binaryActive; the consolidated US options data feedhttps://www.opraplan.com/specifications
Plaza II / FAST-on-Plaza (Moscow Exchange)2010sMoscow Exchange (MOEX)Binary FAST-template-based market data + transaction protocolsActive in MOEX ecosystemhttps://www.moex.com/s1320

Tier 3 family table — Derivatives / structured products

FormatFirst appearedOriginTypeStatus (2026)URL
FpML (Financial products Markup Language)1999 (FpML 1.0); FpML 5.13 Recommendation currentISDA (initially proposed by JPMorgan + PwC)XML schema for OTC derivatives + structured products (rates, credit, FX, equity, commodities, securities lending, repo)Active — FpML 5.13 covers CFTC Rewrite (2020) + ESMA EMIR REFIT; dominant XML representation for OTC trade reportinghttps://www.fpml.org/
ISDA Common Domain Model (CDM)2018 (originally ISDA); transferred to FINOS 2022ISDA + FINOS (now jointly governed with ISLA + ICMA)Domain model expressed in Rosetta DSL, generated as Java/Python/Scala/TypeScript/JSON; product + lifecycle eventsVery active — superset positioning vs FpML; Translate 2.0 (Q4 2025) provides standard FpML↔CDM mapping; CDM 7-dev introduced functional FpML mappers replacing legacy synonym mappershttps://cdm.finos.org/
Rosetta DSL2017+ (REGnosys)REGnosys (sponsored by ISDA)Domain-modelling language used to author CDM; emits multiple language targetsActive, the de facto authoring layer for CDMhttps://docs.rosetta-technology.io/
ISDA Digital Regulatory Reporting (DRR)2022+ISDA + FINOSCDM-derived rule sets for CFTC, EMIR REFIT, JFSA, MAS, ASIC, HKMA reporting regimesActive; CFTC DRR live, EMIR REFIT live since Apr 2024, ASIC + JFSA cutovers 2024https://www.isda.org/2023/10/16/digital-regulatory-reporting/
DTCC GTR submission formats2012+ (post-Dodd-Frank)DTCC Global Trade RepositoryXML message formats — historically FpML-based, ISO 20022-aligned for some regimesActive — the repository layer for OTC derivatives reportinghttps://www.dtcc.com/repository-and-derivatives-services/global-trade-repository

Tier 3 family table — Banking / payments

FormatFirst appearedOriginTypeStatus (2026)URL
SWIFT MT messages1977SWIFT (Society for Worldwide Interbank Financial Telecommunication)Text-based, FIN-network legacy interbank messaging — MT103 (single customer credit), MT202 (FI-to-FI), MT940/MT942 (statements), MT760 (guarantees)Retired for cross-border payments as of 22 Nov 2025; MT remains for ancillary use cases (treasury, securities, trade finance) but FIN cross-border flow is MX-onlyhttps://www.swift.com/standards/iso-20022/iso-20022-financial-institutions-focus-payments-instructions
SWIFT MX / ISO 200222004 (first MX message); 2017 SWIFT MX standardSWIFT + ISO TC68 SC9 (universal financial industry message scheme)XML; rich structured data, structured remittance, structured creditor/debtor identifiersMandatory for SWIFT cross-border payments since Nov 2025 (FINplus); also Fedwire (Jul 2025), CHIPS (2025), FedNow (Jul 2023), CIPS (2015), T2/TARGET2 (Mar 2023)https://www.iso20022.org/iso-20022-message-definitions
ISO 20022 message families — pacs, pain, camt, acmt, remt, head2004+ISO TC68 SC9 (committee), with SWIFT as Registration AuthorityXML message dictionary by business area: pacs (FI-to-FI clearing+settlement), pain (initiation, customer-to-FI), camt (cash management/reporting), acmt (account management), remt (remittance), head (business application headers)Mandatory baseline for cross-border + many domestic high-value railshttps://www.iso20022.org/full_catalogue.page
FedNow message formatJul 2023 launchFederal ReserveISO 20022-native (subset of pacs.008, pacs.002, camt.056, etc.)Active; second Fed-operated rail alongside Fedwirehttps://www.frbservices.org/financial-services/fednow/what-is-iso-20022-why-does-it-matter
CHIPS message format2015+ ISO 20022 work; final cutover 2025The Clearing HouseISO 20022 since 2025 cutoverActive — primary US-dollar wholesale clearing alongside Fedwirehttps://www.theclearinghouse.org/payment-systems/chips
RTP (The Clearing House Real-Time Payments)2017The Clearing HouseISO 20022 from inceptionActive — US instant-payments rail, predates FedNowhttps://www.theclearinghouse.org/payment-systems/rtp
CIPS (Cross-Border Interbank Payment System)2015People’s Bank of China / CIPS Co.ISO 20022 from launch; RMB wholesale + cross-borderActive; revised rules effective 1 Feb 2026 (real-time gross settlement for single transactions, batch net settlement otherwise)https://www.cips.com.cn/en/
NACHA ACH file format1974 (NACHA founded); current 008060 eraNacha (formerly NACHA)Fixed-width text, batch-oriented; CCD, CTX, PPD, IAT, WEB, TEL Standard Entry Class codesVery active — moved $80T+ in 2024; ISO 20022→ACH translation guides published by Nacha (pain.001→credit, pain.008→debit)https://www.nacha.org/content/iso-20022
SEPA SCT / SCT Inst / SDD2008 (SCT); 2014 (SDD); 2017 (SCT Inst)European Payments CouncilISO 20022 XML — pain.001 for initiation, pacs.008 for clearingActive; SCT Inst is the EU instant-payments equivalent (10-second settlement), mandatory for euro-area PSPs from Jan 2025 (receive) and Oct 2025 (send) under the EU Instant Payments Regulationhttps://www.europeanpaymentscouncil.eu/document-library/rulebooks
Bacs (Direct Credit / Direct Debit)1968 (UK)Bacs Payment Schemes Ltd / Pay.UKFixed-width Standard 18 file formatActive legacy; UK New Payments Architecture programme is the long-running effort to migrate to ISO 20022https://www.bacs.co.uk/
CHAPS (UK high-value)1984Bank of EnglandMigrated to ISO 20022 in Jun 2023Active; first major UK ISO 20022 migrationhttps://www.bankofengland.co.uk/payment-and-settlement/chaps

Tier 3 family table — Regulatory reporting

FormatFirst appearedOriginTypeStatus (2026)URL
XBRL 2.12003XBRL InternationalXML business-reporting specification with taxonomies; instance documents reference concept definitionsActive baseline; current Recommendation 2003-12-31 with subsequent erratahttps://specifications.xbrl.org/work-product-index-group-base-spec-base-spec.html
Inline XBRL (iXBRL)2010 (1.1 Recommendation)XBRL InternationalHTML/XHTML with embedded XBRL tagging via ix: namespaceMandatory for SEC operating-company filings (since 2018–2021 phase-in), ESEF (since FY 2020), HMRChttps://www.sec.gov/data-research/structured-data/inline-xbrl
EBA / EIOPA Data Point Model (DPM)2010s; DPM 2.0 published Jun 2023EBA + EIOPA + ECB (DPM Alliance signed Apr 2024)Conceptual data dictionary feeding XBRL taxonomies for EU supervisory reportingActive — DPM Alliance governs evolution; EIOPA Insurance DPM/Taxonomy 2.8.2 (Jun 2025) latest for Solvency IIhttps://www.eba.europa.eu/risk-and-data-analysis/reporting-frameworks/dpm-data-dictionary
Solvency II reporting templatesJan 2016 (Solvency II go-live)EIOPADPM-driven XBRL templates (S.01–S.36 Quantitative Reporting Templates)Active; Taxonomy 2.8.2 with NACE 2.1 hotfix Jun 2025https://www.eiopa.europa.eu/tools-and-data/supervisory-reporting-dpm-and-xbrl_en
FIRE Data Standard2017Bank of England + Suade Labs (open)JSON Schema-based regulatory data dictionaryActive but niche — open-source attempt at common-language reg datahttps://suadelabs.github.io/fire/

Tier 3 family table — Insurance / mortgage / EDI

FormatFirst appearedOriginTypeStatus (2026)URL
ACORD XML / ACORD Data Standards1970 (paper forms); ACORD XML 2002+ACORD (Association for Cooperative Operations Research and Development)XML messages for life, P&C, annuities, reinsurance, surplus linesActive; broad insurance-industry baselinehttps://www.acord.org/standards-architecture/acord-data-standards
ACORD GRLC (Global Reinsurance & Large Commercial)2007 (GRLC 1.0); GRLC Generation 2.0 launched 10 Apr 2025ACORDXML + JSON; covers EBOT (accounting/settlement), ECOT (claims movement), CRP (contract/risk/pre-accounting); Unified Placing Standard part of Gen 2.0Active; Gen 2.0 is current modern target; GRLC 2016.10 (with Jul 2024 release) still in production at many shopshttps://www.acord.org/standards-architecture/acord-data-standards/Global_Reinsurance_Data_Standards
MISMO (Mortgage Industry Standards)1999MBA / MISMOXML reference-model architecture; current v3.6.2Active; v3.6 baseline 2023, v3.6.1, v3.6.2 successive updates supporting UAD, private-label RMBS rating-agency data exchange, YAML+JSON Schema artifactshttps://www.mismo.org/standards-resources/residential-specifications/reference-model
ULDD (Uniform Loan Delivery Dataset)2010Fannie Mae + Freddie Mac (FHFA)MISMO 3.0+ subset for GSE loan deliveryActive; layered atop MISMO 3.xhttps://singlefamily.fanniemae.com/delivering/uniform-mortgage-data-program/uniform-loan-delivery-dataset
UN/EDIFACT1987 (UN/ECE)UN/CEFACTHierarchical, segment-based ASCII EDI; D.NN releases (D.96A, D.01B, …, D.24A current)Active legacy — still trillions in B2B value, especially in EU supply chain; loses share to API integration but no clear sunsethttps://unece.org/trade/uncefact/introducing-unedifact
ANSI X121979Accredited Standards Committee X12 (ANSI)Segment-based ASCII EDI; transaction sets like 850 (PO), 810 (invoice), 837 (HIPAA claim), 270/271 (HIPAA eligibility)Active — version 008060 published Jan 2025; HIPAA-mandated implementation guides at 008060 completed Sep 2025; education programme 2026https://x12.org/

Notable threads

  • The 22 November 2025 SWIFT cutover ended a 50-year run. The MT/MX coexistence period closed and ISO 20022 became the sole format for SWIFT cross-border payments on the FINplus service. From January 2026, banks still relying on the SWIFT translation tool incur penalty fees. This isn’t just a format swap — MX (pacs.008, pacs.009, camt.054) carries structured creditor/debtor identifiers, structured remittance information, ultimate-debtor/ultimate-creditor distinct from instructing parties, and LEI fields, which together unlock straight-through processing, AML screening accuracy, and ISO 20022-consistent reconciliation that the legacy MT free-form :70: remittance field never could. The follow-on November 2026 SWIFT/CHIPS/Fedwire release further tightens this by removing unstructured postal-address options entirely (Federal Reserve Financial Services). The migration began March 2023 and ran a 2.5-year coexistence; the lesson for future format migrations is that two and a half years of dual-rail at the world-banking scale is roughly the floor.

  • FIX 4.4 still dominates the wire despite FIX 5.0 SP2 being newer. This is a common pattern in industry interchange: counterparties certify against a specific version, and once thousands of bilateral certifications exist, no one wants to recertify. FIX 5.0 SP2 (2009) decoupled application semantics (FIX 5.0) from session layer (FIXT 1.1) and introduced the Extension Pack mechanism — the modern way to evolve the standard without bumping the version number. In practice, much of the post-2009 evolution lives in EPs against an underlying 5.0/4.4 base. Most counterparty docs still say “FIX 4.4 with these extensions” rather than “FIX 5.0 SP2”.

  • SBE is displacing FIX/FAST in the low-latency tier. CME MDP 3.0 (Dec 2014) was the first major adoption; Euronext, Moscow Exchange, ICE, and Binance Spot followed. SBE wins on raw decode latency: fixed-layout binary, zero-copy access, no presence-map decode (FAST’s bottleneck), no tag-lookup (FIX tag=value’s bottleneck). FIX FAST is increasingly maintained-only — SBE took its niche. The remaining FIX-family work is on FIX Orchestra (1.1 RC2 published Nov 2024; RC3 in progress with multi-encoding generic framework), the machine-readable rules-of-engagement spec that lets counterparties ship a single Orchestra file and auto-generate session config, message validators, and conformance tests.

  • FpML vs ISDA CDM is the cleanest example of an old XML standard being supplemented (not replaced) by a model-driven successor. FpML (1999, currently 5.13 Recommendation) is XML-Schema-first: instances are XML, validation is XSD-based, evolution is XSD additions. CDM (2018→FINOS 2022) is model-first: the Rosetta DSL describes products, lifecycle events, and processes once, and code generators emit Java/Python/Scala/TypeScript/JSON. ISDA published Translate 2.0 in Q4 2025, providing standard FpML↔CDM mapping in CDM 7-dev, and explicitly positions the two as coexisting — FpML for legacy interchange, CDM for new model-driven systems and the ISDA Digital Regulatory Reporting initiative. CDM also underpins the tokenised-assets working group, putting it on the on-chain bridge that FpML cannot easily reach.

  • XBRL/iXBRL has won the regulator-readable-financials format war. SEC operating-company filings have been Inline-XBRL-mandatory since the 2018 phase-in; ESEF (European Single Electronic Format) made iXBRL mandatory for EU listed-company annual reports under IFRS from FY 2020; HMRC has required iXBRL for UK corporation-tax returns since 2011. The SEC EDGAR XBRL Guide is refreshed periodically (April 2026 latest). The technical innovation of iXBRL is the dual-purpose document — humans see HTML, machines see embedded ix:nonNumeric/ix:nonFraction tags pointing at taxonomy concepts — which finally let regulators retire the era of “one PDF for humans, one XBRL instance for machines, and they don’t always match”.

  • EU regulatory reporting fragmentation lives inside DPM. Each EU regulator (EBA for banking, EIOPA for insurance, ESMA for markets, ECB for monetary statistics) historically maintained its own XBRL taxonomy, often with overlapping but inconsistent data definitions. The April 2024 DPM Alliance between EBA + EIOPA + ECB is the cross-regulator response, layered on DPM Standard 2.0 (published Jun 2023). Solvency II templates (Quantitative Reporting Templates S.01–S.36) ride on the EIOPA DPM/Taxonomy (2.8.2 currently). Whether the DPM Alliance can actually unify the taxonomies — or just the underlying meta-model — is the open question of 2026–28.

  • EDIFACT and ANSI X12 won’t die. X12 published version 008060 in January 2025 and is running an Education, Information, and Messaging programme through 2026. EDIFACT D.24A is the current directory. The EDI standards still move trillions of dollars in supply-chain B2B transactions and most HIPAA healthcare claim flows in the US (X12 837P/837I/837D). The “EDI is dying” narrative has been wrong for fifteen years — what’s actually happening is hybrid EDI/API integration (modern API endpoints in front of legacy EDI translators) rather than replacement. New trading partners go API; the installed base stays EDI; nobody wants to rebuild a working pipeline.

Citations

Graph View