FAQs

General

What is DRR?

Digital Regulatory Reporting (DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data.) is an industry initiative that converts regulatory reporting rules into machine‑executable code, ensuring consistent and cost‑effective implementation across firms. It providesIDE Integrated Development Environment. A software application that brings together all the essential tools a developer needs to write, test and debug code in one unified workspace. a shared, open‑access expression of reporting logic that firms can adopt directly.

Who created DRR?

DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. is led by ISDAISDA International Swaps and Derivatives Association. The global trade association for participants in the derivatives markets. and developed collaboratively across the financial industry. It’s built using the Common Domain Model (CDMCDM Common Domain Model. 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.), developed by FINOSFINOS Fintech Open Source Foundation. A nonprofit organization that brings together the global financial services industry to collaboratively build open‑source software, standards, and best practices., which providesIDE Integrated Development Environment. A software application that brings together all the essential tools a developer needs to write, test and debug code in one unified workspace. the shared data and process model underpinning the reporting logic.

What problem does DRR solve?

Regulatory reporting is traditionally expensive, inconsistent and prone to interpretation differences. DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. standardises the rules so all firms implement the same logic, reducing cost and improving data quality.

How does DRR ensure consistent reporting across firms?

DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. expresses regulatory rules as machine executable logic, removing ambiguity in how firms interpret requirements. As more firms adopt the same CDMCDM Common Domain Model. 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.-based transformations, reporting outputs become far more consistent across the industry.

Does DRR support multiple jurisdictions?

Yes, very much so. DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. is designed to be multi jurisdictional. It includes rule models for major regimes such as CFTCCFTC Commodity Futures Trading Commission – United States regulator overseeing derivatives markets, including swaps and futures., EMIREMIR European Market Infrastructure Regulation – the European Union’s main rulebook for regulating derivatives markets., ASICASIC Australian Securities and Investments Commission – the financial regulator for Australia, MASMAS Monetary Authority of Singapore – Singapore’s central bank and integrated financial regulator. and others. Each jurisdiction has its own transformation logic, but all share the same CDMCDM Common Domain Model. 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. foundation.

How often is DRR updated?

DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. is updated whenever regulatory rules change or clarifications are issued. Because it is an open, collaborative model, updates are published centrally so all firms can adopt the latest logic at the same time, reducing divergence.

Can I extend or customise DRR for my own use case?

Yes. DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. is open-access and can be extended to support firm-specific workflows or additional reporting requirements. However, core DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. logic should remain unchanged if you want to stay aligned with the industry standard interpretation.

Technical

How does DRR relate to the CDM?

DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. is built as an extension of the CDMCDM Common Domain Model. 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., using CDMCDM Common Domain Model. 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. data structures to represent transaction inputs and CDMCDM Common Domain Model. 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. functions to express reporting logic. This alignment reduces duplication, improves interoperability, and ensures that reporting outputs are consistent across jurisdictions and firms.

What data do I need to run DRR?

You need transaction data structured according to the Common Domain Model (CDMCDM Common Domain Model. 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.). DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. then applies enrichment, transformation, and projection steps to produce the required regulatory fields. The DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. documentation includes examples of the expected input payloads.

Can I test DRR logic before integrating it into my systems?

Yes. The DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. documentation includes examples for running transformations directly in the RosettaRosetta REGnosys’s proprietary platform used as an execution engine for DRR. UI or via Postman. This allows you to validate your data, inspect intermediate steps and confirm outputs before embedding DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. into production workflows.

Regulatory

How does DRR ensure that regulatory rules are interpreted consistently across firms?

DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. expresses regulatory requirements as machine executable logic built on the Common Domain Model (CDMCDM Common Domain Model. 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.). Because the logic is deterministic, the same input always produces the same output, no matter who runs it. This removes firm specific interpretation and ensures that all participants apply the rules in a consistent, regulator aligned way.

Does DRR replace a firm’s responsibility to understand the regulation?

No. DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. helps firms implement the rules accurately, but it does not replace the need to understand the underlying regulation. Firms remain responsible for compliance, governance and oversight. DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. simply providesIDE Integrated Development Environment. A software application that brings together all the essential tools a developer needs to write, test and debug code in one unified workspace. a transparent, industry agreed interpretation that reduces ambiguity and implementation risk.

How does DRR handle differences between regulatory jurisdictions?

DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. uses a shared CDMCDM Common Domain Model. 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. foundation but applies jurisdiction specific logic in the Report and Project stages. This means common concepts (like events, products and parties) are reused across regimes, while each jurisdiction’s unique reporting rules are implemented separately. The result is consistency where possible and specificity where required.

Can regulators rely on DRR outputs for supervisory analysis?

Yes. One of DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data.’s core goals is to improve the quality and comparability of regulatory data. Because DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. logic is transparent, version controlled and applied consistently across firms, regulators receive cleaner, more standardised data. This supports better supervision, reduces reconciliation issues and strengthens trust between industry and regulators.

How does DRR support auditability and regulatory assurance?

Every value produced by DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. can be traced back through the full reporting pipeline – Ingest, Enrich, Report and Project. An execution engine such as RosettaRosetta REGnosys’s proprietary platform used as an execution engine for DRR. exposes each intermediate step, making it easy to see exactly how a rule was applied and where a value came from. This end to end lineage providesIDE Integrated Development Environment. A software application that brings together all the essential tools a developer needs to write, test and debug code in one unified workspace. strong evidence for audits, internal controls and regulatory reviews.

Troubleshooting

Why is my DRR run failing before it reaches the Report stage?

This usually happens when the CDMCDM Common Domain Model. 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. input is incomplete or doesn’t match the expected structure. DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. validates the data during the Ingest and Enrich stages and any missing fields, incorrect types or invalid event structures will stop the run early. Check the validation messages in your execution engine (e.g. RosettaRosetta REGnosys’s proprietary platform used as an execution engine for DRR.) – they’ll point to the exact field or object that needs fixing.

My output doesn’t match the example in the documentation. What should I check first?

Start by confirming that you’re using the same DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. version as the example. DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. is versioned, and even small updates can change outputs. Next, compare your CDMCDM Common Domain Model. 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. input with the example input to ensure the same fields, values and event types are present. Differences in enrichment logic often come from differences in the underlying data.

Why am I seeing ‘no mapping found’ or ‘unmapped attribute’ errors?

These errors appear when DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. logic expects a value that isn’t present in the CDMCDM Common Domain Model. 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. input or hasn’t been enriched earlier in the pipeline. Check the relevant enrichment rules to confirm that the attribute is being populated. If the attribute is optional in the regulation but required by the logic, review the jurisdiction’s mapping rules to see whether a default or fallback value should be applied.

The DRR output schema doesn’t match what my reporting system expects. What should I do?

First, verify that you’re using the correct jurisdiction and version of the DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. Project logic. Each jurisdiction has its own output schema, and older versions may differ from current regulatory requirements. If the schema is correct but your system still rejects it, compare the field names and types against the regulator’s published schema to identify mismatches.

How do I troubleshoot unexpected values in the final reporting output?

Use your execution engine’s step by step view to trace the value back through Project, Transform, Enrich and Translate. Each stage shows exactly how the value was derived. Look for:

• Incorrect or missing enrichments
• Conditional logic that didn’t behave as expected
• Upstream CDMCDM Common Domain Model. 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. fields that were populated incorrectly

Once you identify the stage where the value changed unexpectedly, you can adjust the input or logic accordingly.