- The EBA confirmed on 13 March 2026 that credit assessments issued by ECAIs operating outside the scope of Regulation (EC) No 1060/2009 remain subject to specific supervisory treatment under Q&A 2024_7220.
- Q&A 2026_7731 identifies and corrects a technical error in COREP DPM v4.2, where SubCategory “new_CO4” was incorrectly applied instead of “new_CO1” in liquidity templates C_67.00.a and C_67.00.w.
- Institutions using automated COREP reporting pipelines must validate their DPM v4.2 implementations immediately to ensure accurate Additional Liquidity Monitoring Metrics submissions.
EBA Finalises Q&A on Out-of-Scope ECAI Credit Assessments
The European Banking Authority (EBA) published its latest batch of final Question and Answer clarifications on 13 March 2026, addressing a supervisory grey area that has created compliance uncertainty for institutions relying on external credit ratings. Q&A reference 2024_7220 directly addresses the treatment of credit assessments produced by External Credit Assessment Institutions (ECAIs) that fall outside the registration and certification requirements of Regulation (EC) No 1060/2009 — the EU’s foundational Credit Rating Agencies (CRA) Regulation. The clarification draws a clear boundary around when and how such assessments may still be applied under the Capital Requirements framework, providing institutions with a firmer regulatory footing when mapping counterparty and asset exposures to risk weights.
For compliance and credit risk teams, the practical implication is significant. Where an ECAI’s assessments are not governed by the CRA Regulation — for instance, certain export credit agencies or assessments issued in third-country contexts — institutions must now apply the precise eligibility criteria confirmed in this Q&A before incorporating those ratings into their Standardised Approach capital calculations. Failure to do so risks misclassification of risk weights and potential capital adequacy shortfalls under CRR III.
Technical Correction Issued for COREP Liquidity Templates in DPM v4.2
The second finalised Q&A, reference 2026_7731, carries immediate operational urgency for reporting teams. The EBA has confirmed a technical implementation error within Data Point Model (DPM) version 4.2 affecting the Additional Liquidity Monitoring Metrics (ALMM) templates — specifically C_67.00.a and C_67.00.w. The SubCategory value “new_CO4” was incorrectly specified in the technical artefacts where “new_CO1” should have been applied. This is not a policy change but a structural data classification error with direct consequences for XBRL-based regulatory submissions.
“SubCategory ‘new_CO4’ was used instead of ‘new_CO1’ — a technical implementation error in DPM v4.2 affecting COREP liquidity templates C_67.00.a and C_67.00.w.”
Operational Impact on Regulatory Reporting Teams
Institutions and their technology vendors that have already built or updated COREP reporting workflows against DPM v4.2 must audit their taxonomy mappings without delay. Incorrect SubCategory tagging in ALMM submissions can trigger validation failures at national competent authority level — including BaFin, De Nederlandsche Bank, and the ECB’s supervisory arm for significant institutions under the Single Supervisory Mechanism (SSM). Firms should coordinate with their RegTech vendors and XBRL solution providers to patch the affected templates prior to their next reporting reference date.
Broader Regulatory Reporting Context
Both Q&As form part of the EBA’s ongoing Single Rulebook Q&A process, which provides legally grounded interpretive guidance to firms navigating the EU banking regulatory framework. While Q&As do not carry the force of binding technical standards, national supervisors consistently reference them during inspections and model validations. The March 2026 batch reinforces the EBA’s sustained focus on reporting accuracy and the integrity of supervisory data as the Basel IV/CRR III transition continues across member states.
The DPM v4.2 SubCategory correction in Q&A 2026_7731 is a quiet but operationally sharp alert — firms that automated ALMM reporting against the original flawed taxonomy may have already submitted non-compliant data for prior reference periods, creating potential restatement exposure. Combined with the ECAI scoping clarification, this release signals that the EBA is tightening the granularity of both capital and liquidity data quality expectations heading into the full CRR III implementation cycle. Reporting officers should treat both Q&As as action items, not advisory reading.
