• Insight
  • Wednesday 29th July 2026

DRR 7.0: Expanded regulatory coverage and key platform upgrades

DRR 7.0 is a major production release that brings together new regulatory coverage, regulatory enhancements, platform improvements and model upgrades introduced since September 2025.


As regulatory requirements continue to evolve across major jurisdictions, ISDA’s Digital Regulatory Reporting (DRR) provides a shared, machine-readable framework that helps firms improve data quality and adopt a more consistent and scalable approach to reporting.


The headline development is support for the SEC reporting regime, significantly expanding DRR’s global regulatory coverage. Alongside this, DRR 7.0 also delivers important updates for the CFTC, ASIC and MAS.


Beyond regulatory content, DRR 7.0 introduces a series of foundational upgrades designed to make the platform easier to use and maintain. These include migration to CDM 6, support for functional ingest mappings, the refactoring of Reportable Information, the removal of Rule Source and the introduction of a new base namespace.


These changes make DRR 7.0 one of the most significant releases to date, strengthening regulatory coverage while making it easier for firms to move from source data to compliant reporting outputs. REGnosys is proud to have contributed to this development as ISDA’s technical partner and alongside the many other firms taking part in ISDA’s reporting working groups.


What’s in DRR 7.0?


This release delivers progress in three key areas:


1. SEC support extends DRR's global reach

 

DRR 7.0 introduces support for the SEC reporting regime for security-based swaps. 


The implementation includes:


• a functional representation of the SEC reporting requirements covering Trade and Margin reports, Valuation and Public Price Dissemination.


• validation rules included in the TR technical specification.


• projection into the required DTCC Harmonised XML format.


• test coverage across asset classes and event types.

 

2. Upgrades to existing jurisdictions 


For CFTC, the DTCC implementation has been uplifted from 3.1 to 3.2, adding validation rules, business rules and functional logic. 


Both ASIC and MAS have been updated to 1.4 with enhancements across reporting rules, reporting conditions, counterparty validations, and closer cross-regime alignment with CDE and common reporting requirements. 


3. Model and platform upgrades


Migration to CDM 6


DRR 7.0 introduces support for CDM 6, enabling users to benefit from major modelling enhancements developed throughout 2025, including:


• The Asset Refactor, which addresses longstanding challenges around modelling non-derivatives products, product qualification, index representation, observable reuse, and price/quantity structures.


• The Option Payout Refactor, which simplifies option modelling through a new ExerciseTerms framework.


• The Standardised Initial Margin Schedule, which provides a structured calculation methodology. 


As some CDM 6 changes are not backwards compatible, organisations moving from CDM 5 should assess the impact on existing integrations and data models before adoption. REGnosys is here to help with expertise and tooling to tackle upgrades to models and mapping, and migration of persisted CDM data.


Reportable Information enhancement


Reportable Information has been refactored to create a clearer separation between jurisdiction-specific and jurisdiction-agnostic reporting data. 


• The partyInformation attribute has been renamed globalPartyInformation, while executionVenueType and sefOrDcmAnonymousIndicator have been moved into a new ReportableExecutionVenue type within TransactionInformation.


• A new jurisdictionInformation attribute consolidates jurisdiction-specific information relating to parties and transactions, making reporting data easier to identify, filter and interpret.


Functional ingest mappings and RecordKeeping


DRR 7.0 introduces the direct ingestion of FpML RecordKeeping messages into CDM objects through Rune functional mappings. Gaps between legacy synonym mappings and the newer ingestion framework have been closed, and new transformation functions allow ingestion outputs to be converted directly into reporting inputs. 


By replacing less transparent synonym mappings and Java-based implementations with clear functional logic, the release improves accessibility and maintainability while supporting a complete workflow.


Rule Source removal


Rule Source has been removed across all reporting regimes to eliminate its overlap with Rule Refs, which provide greater flexibility for overriding attribute behaviour within nested and complex structures.


The removal streamlines the reporting framework, while additional improvements to the organisation of regulatory provisions, regulation names, working-group notes and metadata make the underlying rules easier to navigate and maintain.


Base namespace introduction


DRR 7.0 introduces a new base namespace to create a clearer separation between DRR business logic and CDM-dependent functionality. 


The revised dependency hierarchy (base → cde → (regulation) common → jurisdiction-specific) allows each layer to reference only the functionality it requires, while the base namespace remains independent and contains core CDM dependency logic. This separation reduces coupling between model layers, improves architectural clarity and, most importantly, has been designed to make future upgrades significantly easier to manage.


Explore DRR 7.0


Further technical detail and implementation guidance are available in Rosetta and the release documentation:


• View DRR 7.0 in Rosetta: https://ui.rosetta-technology.io/workspace-manager

 

• Read the DRR 7.0 release notes: https://github.com/rosetta-models/digital-regulatory-reporting/releases/tag/7.0.0


• Read the CDM 6.0 release notes: https://github.com/finos/common-domain-model/releases/tag/6.0.0


Organisations planning to adopt DRR 7.0 should review the release documentation, assess the impact of the CDM 6 migration on existing integrations, and begin testing the updated reporting logic.


Reach out to us if you would like to discuss your adoption or migration plans and for help to comply, safer, cheaper and faster. Contact us at clients@regnosys.com.

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

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

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

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