The Finalized EBA 4.3 Technical Package: What Changed?

Introduction

On 9^th July 2026, the European Banking Authority (EBA) released the final technical package for the version 4.3 of its reporting framework. It locks in the reporting requirements for the Third-Country Branches (TCB’s) under the Capital Requirements Directive (CRD) and gives the Anti-Money Laundering Authority (AMLA) the data infrastructure it needs, to run its risk assessment exercise.

For the Banks who are following these compliances; this release version matters even if they don’t have the TCB or AML obligation today, this is the first EBA package built entirely on DPM 2.0 architecture, the Authority finished rolling out in version 4.2.

A common misconception among compliance teams is that Framework 4.3 alters core Common Reporting (COREP) or Financial Reporting (FINREP) templates. Instead, Framework 4.3 expands the supervisory perimeter to bring TCBs under standardized prudential review and establishes data-collection mechanics for the AMLA.

What’s New in the EBA 4.3 Technical Package?

The final package covers two distinct reporting streams. Nothing in framework 4.3 amends existing COREP, FINREP, resolution, benchmarking, liquidity, ESG or Digital Operational Resilience Act (DORA) templates, those changes are scoped separately into framework 4.4.

Third-Country Branch (TCB) supervisory reporting

The final draft Implementing Technical Standards (ITS) sets out supervisory reporting obligations for TBS operating in the EU, under Article 481(1) of the CRD VI. The first reference date is 31^st March 2027.

AMLA Risk Assessment Data Collection

The package introduces the Data Point Model (DPM) and XBRL taxonomy components supporting AMLA’s methodology for identifying which obliged entities will fall under its direct supervision from 2028. The first date is 31^st December 2026.

Deep Dive into Technical Deliverable

The EBA 4.3 release goes beyond policy text to deliver technical parts across the four key areas:

1. DPM 2.0 Database Architecture: This enhances metadata definitions without breaking the existing core banking schemas. It provides exact database concepts for the TCB structures and AML risk scoring variables.
2. Validation Rules and Syntax Shifts: The final release updates validation rule syntax and logic checks. Legacy custom pre-validation scripts that rely on v4.1 or v4.2 syntax will fail when parsing v4.3 packages. Updating internal expression parsers prior to testing is critical.
3. XBRL Taxonomy and Sample files: XBRL taxonomies and reference instance files are now available for software engineers. These allow vendor platforms to build intake models and test rendering pipelines well before live filing periods.
4. The Glossary Usage Exploration File: To support ongoing simplification efforts, the EBA introduced a new Glossary Usage Exploration file. This standalone tool maps data definitions, cross-module concepts and semantic relationships across DPM, helping reporting teams trace data lineage.

Critical Timelines to Follow

Staying compliant requires aligning development cycles with EBA and AMLA milestones:

Conclusion

The finalized EBA 4.3 Technical Package establishes clear requirements for TCB transparency and AMLA selection data. While core reporting frameworks remain untouched for now, the underlying updates to DPM 2.0 schemas and validation rules demand immediate attention from IT and compliance teams.

Teams that treat 4.3 as a “not our templates” release tend to discover taxonomy and tooling gaps only when the bigger changes land. Use this window to test your systems, map your data, and get ahead, before framework 4.4 raises the stakes.

By updating data pipelines today, financial institutions can meet upcoming 2026-2027 deadlines smoothly while building a reliable foundation for Framework 4.4.