• Product
  • Tuesday 22nd September 2026

Bringing ICMA's Bond Data Taxonomy into the CDM ecosystem

The capital markets industry has made significant progress in developing common standards for representing financial products and transactions. As those standards mature, an increasingly important question emerges, how can they work together. 


Different standards have been developed to address specific market needs. As their adoption grows, so does the need to connect them without requiring firms to build and maintain their own bespoke mappings.


At REGnosys we have been exploring exactly that question through the creation of BDT-as-Rune.


BDT-as-Rune brings the ICMA Bond Data Taxonomy (BDT) into Rosetta, modelling the taxonomy as Rune data types and building functional mappings that transform that BDT data into the Common Domain Model (CDM).


What is BDT-as-Rune?


ICMA’s BDT Version 2.0 provides a standardised framework for representing key data associated with bond issuance, from instrument and issuer details through to economic terms.


BDT-as-Rune takes that standard one step further by representing the taxonomy as a Rune model.


The structure of the BDT is captured as Rune data types, creating a typed, machine-readable representation of the taxonomy that can be directly ingested and processed within Rosetta or integrated into your own applications using Rune’s code generators for Java, Python and other common programming languages.


This allows for transformation and mapping logic to be built around the BDT, using the same modelling language that underpins the CDM.


Connecting BDT to the CDM


Using the Rosetta Design platform, REGnosys has created Rune functions that map BDT concepts into their corresponding CDM representations, creating a bridge between standardised bond issuance data and the CDM ecosystem.


The mappings cover the core components of a bond issuance, including the instrument and its identifiers, issuer and party information, currency, maturity and economic terms.


Together, the BDT-as-Rune model and these functional mappings create an end-to-end transformation:


BDT XML → BDT as Rune → CDM


Why does this matter?


BDT and CDM both address different but complementary parts of the standardisation challenge.


The BDT provides a common way to represent and exchange pre-trade bond issuance data at source. The CDM provides a common representation of financial products, transactions and post-trade events that can be used across a wide range of downstream processes.


BDT-as-Rune connects the two.


For firms adopting these standards, this provides a practical path from standardised primary market data to a common CDM representation, reducing the need for each organisation to independently interpret the BDT and build its own transformation into downstream data models.


It also demonstrates a broader opportunity as the use of common standards grows across financial markets. Rather than every organisation building its own mappings between standards, those mappings can themselves be defined, tested and reused.


Explore BDT-as-Rune


To see BDT-as-Rune in action and learn how Rosetta can help connect existing industry standards to the CDM explore the BDT-as-Rune project in Rosetta at http://ui.rosetta-technology.io or contact the REGnosys Client Services team at clients@regnosys.com to find out more.

Data Modelling

Take an existing data pipeline of any form…

Just choose among your existing business processes to experiment a model-driven approach in +/- 2 days.​
We can start from any kind of artefact, from XML messages down to Excel or even PDF documents.

… To demonstrate the model-driven approach…

Our team of data engineering experts works in immersion with you and guide the process from start to finish.​
Our promise: some executable data pipeline running based on your model by the end of the workshop.

… Which you can deploy within your organisation

All it takes is a cross-functional team of developers and non-developers, who is open to a fresh (and fun!) approach.​
The buck doesn’t stop there. That team is now empowered to carry that project forward and build model-based pipelines for your organisation.
Contact us

Reporting Audit

First, map your data into CDM...

We have it covered it. All it takes is a +/- 2-day immersion workshop with your tech team to build your mappings.
As a by-product, you get a ready-to-use API to convert all your trade data

… And access your audit results on-line…

Once your trade data have been mapped, our reporting engine compares its output to your reports and analyses any discrepancy.
Analysis is developed within 6 weeks and results published into a web application.

… Through a powerful user interface

Forget static audit reports that end-up on a shelf.
Our reporting engine is available on-demand to reconcile your reporting process end-to-end and down to single trade flow, through a fully interactive interface.
Contact us

Model-Driven Regulation

Bring-on the regulatory text…

Can be anything in your existing corpus, as long as it’s digestible and relatively self-contained.
The target is to deconstruct that text and reconstruct a model of the regulation in +/- 2 days.

… We’ll handle the rest…

Our team of regulatory and engineering experts works in immersion with you and guide the process from start to finish.
Our promise: some executable code running by the end of the workshop, delivered to you and ready for demonstration.

… And you’re ready to develop rules on your own

All it takes is a cross-functional team, ideally all-encompassing from policy to technology, who is open to a fresh (and fun!) approach.
The buck doesn’t stop there. Your team is now empowered to carry that project forward inside your organisation.
Contact us

CDM Integration

We do the data mappings for you…

Just extract transaction data from your booking, reporting or any other systems, we handle the rest.
We build mappings in immersion with your tech team, as a packaged +/- 2-day workshop that includes valuable CDM training – and is fun (yes, really)!

… And deliver you a packaged output…

Forget data mapping spreadsheets and forget hard-coded translation buried deep into your code base.
What you get is a transparent, maintainable CDM translation dictionary, automatically packaged into an API to translate your internal trade messages.

… Which you can start using right away

Start using the API for testing right away. For production deployment, we offer a range of hosting options that adapt to your technology stack.
The application grows with you. Just edit your dictionary to connect more and more systems to CDM.
Contact us