EBA-ECB-EIOPA DPM Alliance — DPM 2.1 metamodel consultation and metadata naming conventions

Tag: S-2026-07-31-eba-dpm-2-1-metamodel-consultation Type: report (public consultation launch + guidance) Author(s): Data Point Model (DPM) Alliance — a joint initiative of the EBA, ECB and EIOPA (SRB observer) Date of source: 2026-07-31 (consultation launched; closes 30 September 2026) Date ingested: 2026-08-19 Authority weight: high — the EBA’s own press release and publications listing, retrieved directly via WebFetch. Raw file: S-2026-07-31-eba-dpm-2-1-metamodel-consultation.md. Source URL: eba.europa.eu/publications-and-media/press-releases/eba-ecb-eiopa-data-point-model-alliance-consults-improvements-their-data-dictionary-metamodel-better.

What it claims

On 31 July 2026 the Data Point Model (DPM) Alliance — the joint EBA-ECB-EIOPA initiative that governs the DPM data dictionary — launched a two-month public consultation on enhancements to its DPM metamodel (DPM 2.1) and simultaneously published naming conventions for a consistent approach to reporting metadata. The consultation closes 30 September 2026.

The Alliance frames the work as making “financial sector statistical and supervisory reporting across the EU simpler, smarter and more proportionate” and as a step “towards integrated European reporting across all regulatory frameworks”. DPM 2.1 “builds on the DPM, a structured, consistent and machine-readable approach to regulatory metadata”, intended to reduce complexity, improve data quality and lower reporting costs. Concretely it is described as facilitating “the integration and alignment of the EBA’s integrated prudential and resolution reporting frameworks and the ESCB Integrated Reporting Framework (IReF)”, and it introduces enhanced metadata versioning and extends the metamodel to host logical data models. The accompanying naming conventions provide “a common approach for naming metadata” to support effective use of the common data dictionary.

Background: DPM is “a well-established and proven data dictionary developed and used by the EBA and EIOPA” to integrate their reporting frameworks; DPM Standard 2.0 was published in June 2023; in March 2024 the EBA, EIOPA and ECB established the DPM Alliance to extend DPM to ECB statistical reporting and jointly govern the standard, with the SRB participating as an observer. The press release links the work to the EBA’s October 2025 report on the efficiency of the regulatory and supervisory framework and its simplification actions. Supporting documents published alongside: a Factsheet on DPM standard 2.1 and the naming conventions guidelines (dated 30 July 2026).

Notable quotes

“To facilitate the integration of reporting, they launched today a public consultation on enhancements to their DPM metamodel for two months. They also published naming conventions for a consistent approach to metadata.” — EBA press release, 31 July 2026

“It builds on the DPM, a structured, consistent and machine-readable approach to regulatory metadata. This will help reduce complexity, improve data quality and lower reporting costs.” — EBA press release, 31 July 2026

What’s speculative vs. asserted

• Asserted (facts): the 31 July 2026 launch of the two-month DPM 2.1 metamodel consultation (closes 30 September 2026); publication of metadata naming conventions (dated 30 July 2026); the DPM Alliance composition (EBA/ECB/EIOPA, SRB observer) and its March 2024 establishment; DPM Standard 2.0 in June 2023; DPM 2.1’s stated aims (integrate prudential/resolution and ESCB IReF reporting; enhanced metadata versioning; host logical data models; reduce complexity/cost, improve data quality).
• Aspirational / forward-looking: the “simpler, smarter, more proportionate” and “reduce complexity / improve data quality / lower reporting costs” benefits are stated objectives of a consultation-stage metamodel, not yet realised outcomes.
• Not AI/model-risk: this is data-dictionary/metadata standardisation for supervisory and statistical reporting. Service-line mapping (RRE, GFD) is the ingesting agent’s assessment, stated explicitly.

Topics this feeds

• EBA Simplification and Efficiency Programme — DPM 2.1 is the natural next step in the programme’s reporting/data-architecture strand, extending the DPM 2.0 / Reporting Framework 4.3 / JBRC integrated-reporting workstream that the programme already tracks.
• EBA — European Banking Authority — a further EBA data-governance instrument (co-owned with ECB/EIOPA).
• BCBS 239 and Data Lineage — a shared metadata dictionary and naming conventions are the standards substrate that firms map risk-data lineage and reconciliation controls to [inference].
• EBA Pillar 3 Data Hub — the P3DH centralisation and SNCI pre-fill rely on the same DPM/XBRL metadata backbone [inference].

Open questions raised

• How much re-baselining of firms’ internal data lineage, reconciliation and DQ controls will DPM 2.1’s “enhanced metadata versioning” and “logical data models” require during migration from DPM 2.0?
• Will the IReF alignment materially change the datapoints or semantics banks must produce, or is it primarily a back-end metamodel/governance change transparent to reporting firms?
• Does the metamodel work create any explicit hooks for AI/model-governance metadata, or is it confined to prudential/statistical reporting?