EBA Issues User Guide for DPM Glossary Conversion File Under Quality Review Project
Key Takeaways
- The European Banking Authority has published a user guide explaining the conversion file that maps old DPM 1.0 glossary elements to the new DPM 2.0 glossary structure, resulting from its ongoing Quality Review project.
- Compliance and reporting teams must understand this mapping as it underpins the modeling of all EBA reporting frameworks and will inform the upcoming v4.0 release, directly affecting regulatory reporting taxonomies.
Deep Dive
This Industry Letter is a technical user guide rather than a binding rule change, but it carries significant downstream implications for institutions that rely on EBA's Data Point Model (DPM) for regulatory reporting. The DPM Quality Review project, launched in 2023, has so far reviewed 65% of the EBA glossary, covering liquidity templates and basic domains (Metrics, Main Category, Base, Counterparties, Portfolios, and Liquidity). The conversion file formally documents how old glossary elements (domains, dimensions, domain members, hierarchies) map to new DPM 2.0 constructs (categories, properties, items, subcategories), and this mapping has already been implemented in the modeling of all current EBA reporting frameworks.
For compliance and regulatory reporting teams, the key change is structural: domains are being reorganized into new or existing categories (sometimes split across multiple categories), dimensions are being relabeled, split, or newly created as properties, and domain members are being converted into items—including new compound items (to capture complex concepts like STS securitizations) and aggregating items (for hierarchy-based aggregations, such as trading and banking book portfolios). These changes affect how reporting templates are tagged and validated in institutions' regulatory reporting systems, and firms using XBRL/DPM-based reporting engines will need to update internal mappings, validation rules, and data dictionaries accordingly.
No explicit compliance deadline is stated in this letter, but the document explicitly serves as a reference for the development of DPM release v4.0, signaling that institutions should expect further glossary changes and should begin preparing their reporting infrastructure now. Given that 35% of the glossary (non-basic domains) remains under review, this is a living document that will be updated, and firms should treat the current conversion file as provisional guidance rather than a final specification.
Recommended actions include: (1) assigning data governance or regulatory reporting teams to review the conversion file in detail, particularly for the categories, properties, and items relevant to templates the institution submits; (2) engaging with EBA via the provided contact point to provide feedback during this consultation-like phase; (3) assessing IT and data architecture impacts, especially for reporting engines that rely on DPM 1.0 structures; and (4) tracking the release timeline for DPM v4.0 to align internal system upgrades. Risk implications center on operational and reporting risk—misalignment between old and new glossary structures could lead to reporting errors, validation failures, or supervisory data quality issues if institutions fail to update internal taxonomies in sync with EBA's framework evolution.
Source: European Banking Authority

