EBA Releases User Guide for DPM 2.0 Glossary Conversion File

Key Takeaways

• The European Banking Authority has published a user guide explaining the conversion file that maps its legacy DPM 1.0 glossary to the new DPM 2.0 data model, as part of the ongoing DPM Quality Review project.
• This document is critical for institutions that rely on EBA taxonomies for supervisory reporting, as it details how domains, dimensions, and domain members will be restructured into categories, properties, items, and subcategories ahead of the v4.0 reporting framework release.

Deep Dive

This update is a technical but consequential communication from the EBA regarding the structural overhaul of its data point model (DPM) glossary, which underpins all EU supervisory reporting taxonomies. The conversion file and accompanying user guide document how existing glossary elements—domains, dimensions, domain members, and hierarchies—will be reclassified into the new DPM 2.0 structure of categories, properties, items, and subcategories. For compliance and regulatory reporting teams, this is foundational infrastructure change: approximately 65% of the EBA glossary has already been reviewed, covering liquidity templates and basic domains (Metrics, Main Category, Base, Counterparties, Portfolios, and Liquidity).

Key changes include the introduction of new conversion typologies such as "1:X" splits (where one old element is replaced by multiple new ones), "compound items" (which decompose complex concepts into constituent parts), and "aggregating items" (which consolidate related items under a hierarchy). These are not merely cosmetic relabeling exercises; in many cases, a single old domain member will be replaced by two or more new items across different categories, which has direct implications for how reporting templates are modeled and how historical data maps to future submissions. Institutions using EBA taxonomies for COREP, FINREP, or other supervisory returns will need to trace these mappings carefully to avoid misclassification once DPM 2.0 is operationalized.

While no explicit compliance deadline is stated in this letter, the document signals that the new glossary is already being used to model all EBA reporting frameworks and will serve as the reference for developing the v4.0 release. This suggests that reporting entities and their technology/data teams should begin reviewing the conversion file now, rather than waiting for formal implementation, to ensure internal data dictionaries, XBRL taxonomies, and reporting logic are aligned with the new structure in advance of v4.0.

Recommended actions include: (1) assigning data governance or regulatory reporting teams to review the conversion file in detail, particularly for domains relevant to the institution's reporting scope; (2) engaging with the EBA via the provided contact point to provide feedback during this still-ongoing review (non-basic domains remain work in progress); (3) updating internal data lineage and mapping documentation to reflect anticipated DPM 2.0 structures; and (4) monitoring for further EBA communications on the v4.0 framework timeline. The primary risk is operational—misalignment between legacy and new glossary structures could lead to reporting errors, template breaks, or delayed remediation once the new taxonomy is enforced. Given the central role of DPM in EU prudential reporting, early preparation will mitigate downstream compliance and data quality risk.

Source: European Banking Authority