FINOS with ISDA, ICMA and ISLA
Common Domain Model
FINOS-CDM-7
- Authority
- E, Industry domain standard or modelVoluntary market convention
- Maturity
- M2, Published and evolvingCurrent artifact with active change cadence or version-sensitive profiles
- Version
- 7.0.0, 17 July 2026
- Jurisdiction
- Global
One of twelve records open without an account, chosen to span every class of authority so the classification can be judged before anybody signs in.
What it does
Machine-readable product, legal agreement, event, process and reference-data model across derivatives, securities and securities finance
Implementation
Rune model, Java executable distribution, Python distribution, partial TypeScript model
What it does not do
Not a wire protocol, ledger token or legal agreement; map source artifacts and chain events with lineage and version
This is the field that matters. Most failures here are a standard asked to carry something it was never written for, and the resulting gap is discovered in production.
Where it applies
Layers, the questions it helps answer
- L2
Terms, contract and data semantics
Which terms, legal agreements, code lists and data definitions are canonical?
- L3
Lifecycle event and process model
What events, state transitions, calculations and exceptions exist?
- L4
Messaging and workflow
How are instructions, status, confirmations and reports exchanged?
- L13
Evidence, audit and verifiability
What proves design intent, implementation conformance and runtime operation?
Phases, when in the life of an instrument
- P0
Design time
legal classification, authority-of-record map, product archetype, standards shortlist
- P1
Build time
schemas, interfaces, mappings, adapters, rules, invariants and test plans
- P2
Issuance and deployment
identifiers, contracts, roles, registries, modules, documents and configuration manifest
- P3
Runtime preflight
signature, identity, eligibility, freeze, balance, NAV, oracle and route checks
- P4
Atomic execution
state transition, transfer, mint, burn, lock, settlement or message dispatch
- P5
Lifecycle servicing
calculations, corporate actions, payments, queues, elections and reconciliation
- P6
Operations and reporting
monitoring, statements, regulatory reports, evidence and incident response
- P7
Change, migration and exit
revocation, correction, upgrade, identifier continuity, migration, retirement and data export
lifecycleevent-modelopen-source
How it composes with others
Direction matters and is preserved. A conflict is not a warning about quality; it means the two cannot both hold without an adapter or a design change.
Mapped to from Bond Data TaxonomyICMA-BDT-2
Issuance terms can seed CDM product/lifecycle concepts through a governed semantic mapping.
Mapped to from Financial products Markup LanguageFPML-5.13
CDM 7 includes functional FpML ingestion; preserve original payload and mapping provenance.
Orthogonal to, a different layer ACTUS Data and Algorithmic StandardsACTUS
ACTUS specializes in contract-event/cashflow algorithms; CDM provides broader lifecycle and process semantics.
Source and terms of use
- Primary source
- https://github.com/finos/common-domain-model
- Licence and access
- Community Specification License 1.0 for model; code artifacts have separate licenses, commonly Apache 2.0
- Last verified
- 2026-08-15, primary source verified
The Institute links to and describes primary sources; it does not reproduce their normative text. Several of these documents are copyrighted and cannot be redistributed, and the licence note above is the record’s own statement of its terms, not a grant. Status is reported as observed at 2026-08-15 in catalogue release 1.0.0 and must be revalidated before use. Nothing here is legal, regulatory, accounting, tax, investment, security-audit or production-readiness advice, and neither a published status nor an open implementation is a regulatory approval or a certification.