Skip to main content
Version: 5.20.0

Continuous Integration:

FINOS - Incubating

Codefresh build status

What is the FINOS CDM?

The FINOS Common Domain Model (CDM) is a standardised, machine-readable and machine-executable blueprint for how financial products are traded and managed across the transaction lifecycle. It is represented as a domain model and distributed in open source.

For an overview of the Common Domain Model, a comparative analysis with FpML, an exploration of the CDM's historical development and events, as well as insights into its further applications, including its role in the ecosystem and support for smart contract technology, we recommend reviewing the CDM Overview deck.

ISDA’s Digital Regulatory Reporting (DRR) solution leverages the open-source Common Domain Model (CDM) to convert industry-agreed interpretations of new or amended regulatory reporting rules into clear, machine-executable code. This approach enhances implementation efficiency and reduces costs. Institutions contributing to the development of the ISDA DRR include (but are not limited to) those listed on ISDA’s Digital Regulatory Reporting Page.

ISDA has also launched the Get Started with the CDM for Collateral Guide! You can now access a wealth of resources and tutorials on CDM for collateral management on the CDM-Collateral Initiatives page.

If you’re interested in the Common Domain Model (CDM), please complete the CDM Interest Form to join our mailing list. By signing up, you’ll receive updates on CDM initiatives, meeting agendas, and other working group activities.

Purpose​

A single, digital processing standard for trade events and actions enhances financial markets' operational efficiency in several ways:

  • Enables inter-operability and straight-through processing across firms, solutions and platforms, reducing the need for reconciliation caused by variations in how each firm records trade lifecycle events.
  • Accelerates financial technology innovation by providing a common, readily operational foundation for how technologies like distributed ledger, smart contracts, cloud computing, and artificial intelligence can be applied to financial markets.
  • Delivers better regulatory oversight, promotes transparency and alignment between regulators and market participants and enables consistency in regulatory reporting, by providing a standard representation of trade data and supporting machine executable reporting requirements.

For further information about the CDM and its applications, please consult the CDM section of the FINOS website or contact FINOS directly at cdm@lists.finos.org.

Model Overview​

The key models defined in the CDM are listed below. Click each one to learn more.

  • Product model - describes a thing (e.g. contract or instrument) that is used to transfer financial risk between two parties.
  • Event model - provides data structures to represent the lifecycle events of financial transactions.
  • Process model - lays the foundation for the standardisation, automation and inter-operability of industry processes.
  • Reference data model – describes underlying business entities such as parties, legal entities, floating rate indexes, and so on that needed to model the in-scope products, events, legal agreements and function components.
  • Use cases – business process areas in the financial ecosystem that the CDM supports.

Design Principles​

To support the objectives described above, the CDM is built according to a set of design principles that include the following concepts:

  • Normalisation through abstraction of common components
  • Composability where objects are composed and qualified from the bottom up
  • Mapping to existing industry messaging formats
  • Embedded logic to represent industry processes
  • Modularisation into logical layers

These design principles are further detailed in the design principles section of the CDM documentation.

Governance​

The CDM governance framework regulates the development of the CDM in open source.

Scope​

The CDM covers OTC derivatives, cash securities, securities financing, commodities, and can expand to include other Capital Markets products and Asset Classes.

CDM 2025 Roadmap​

Below is the full roadmap as ratified by the Steering WG in Feb 2025, subject to change as priorities evolve.

  • The latest CDM roadmap of expected contributions sponsored by the presently participating trade associations: ICMA, ISDA and ISLA can be found under Roadmap .
  • Releases can be tracked on the CDM Releases page.

CDM Components

The CDM is made of three sets of components, as laid-out in the FINOS CDM components diagram below:

  • The FINOS CDM Distribution (in the centre, in purple)
  • The Rune DSL (on the left, in grey)
  • CDM Applications (on the right, in blue)

FINOS CDM Distribution​

The FINOS CDM distribution is openly accessible to all industry participants, subject to the FINOS CDM open source licence. This distribution is fully downloadable.

The FINOS CDM distribution comprises three main sets of components:

  • Model definition, which corresponds to the model as expressed in the Rune DSL and contained into a set of .rosetta files organised as namespaces. The primary dimensions of the model are listed below and further described in the above.
    • Product
    • Event
    • Legal Agreement
    • Process
    • Reference Data
    • Mapping (Synonym)
  • Executable code distribution, automatically generated from the model definitions expressed in the Rune DSL using available code generators. Once a code generator is implemented for a particular language, the corresponding code generation is included as part of the CDM build and release process, allowing the CDM to be automatically distributed in that language going forward.
  • Default implementation, comprising manually-written code (in Java) which, combined with the auto-generated code, provides a complete implementation of the model. This hand-written code is distributed together with the CDM to facilitate adoption by firms, which can directly use the CDM distribution to set-up and test an implementation. The default implementation can be used in its original state or be disabled or extended by industry participants in their implementations. For example, the default implementation uses the de-facto Java hash function to support cross-referencing in the CDM, but firms may elect to use an alternative implementation.

Note: Only the Java executable code distribution is complete: i.e. it represents the entire CDM as defined in Rosetta (plus any associated default implementation). Other distributions may only capture parts of the model: for instance, the Scala and TypeScript distributions include the complete data model and function specifications, but not the functions' executable code.

Rune DSL​

The CDM is written in a Domain-Specific Language (DSL) called the Rune DSL, that comprises a language (i.e. syntax, semantics and rules) and code generators.

The language includes one default code generator into java. To facilitate adoption and implementation of the CDM by the community of industry participants, the Rune DSL is available in open source under an Apache 2.0 license. This allows industry participants to write and share code generators into any other languages.

Note: All the language components, their syntax and purpose are detailed in the Rune DSL Documentation. The documentation also describes the mechanism to write and use code generators.

CDM Applications​

An ecosystem of CDM-based application components from software providers exists in order to support the adoption of CDM and the implementation of CDM-based production systems by industry participants. These applications may be open source software or licensed under commercial terms. In particular:

  • Rosetta is a Software Development Kit (SDK or dev-kit) for the Rune DSL, that provides the community with a free and easy way to contribute code to the CDM. Please refer to the Rosetta Documentation for more details.

Note: Rosetta has been developed by technology firm REGnosys. FINOS encourages the adoption of CDM by software providers but does not endorse any CDM application component.

Using the CDM (Java)

The Java distribution of the CDM is designed to be built and used with Maven.

It depends on some open source java artifacts which are freely available from an artifact repository. Maven can be configured to use this repository using the repository settings contained in the settings.xml file in the CDM jar.

For more details, please follow the CDM Java Distribution Guidelines.