ECB's IReF: What the Revised Reporting Timeline Means for Banks
The European Central Bank has confirmed the first genuinely workable implementation schedule for its Integrated Reporting Framework, known as IReF. A one-year pilot phase will open in Q2 2030, with mandatory IReF reporting commencing in Q2 2031. For accounting firms advising European credit institutions, CFOs overseeing regulatory reporting, and auditors reviewing data-quality controls, this is not a distant horizon. The preparatory work the ECB expects is substantial, and the sequencing starts now, well before the draft regulation is even published.
What IReF Is and Why It Matters for Financial Reporting
IReF stands for the Integrated Reporting Framework, an ECB initiative designed to harmonise and simplify the statistical reporting obligations of euro-area banks. Today, credit institutions submit statistical data to multiple authorities on overlapping schedules, a process that is both time-consuming and resource-intensive. IReF consolidates those obligations into a single, more granular framework with the goal of reducing duplication, improving data quality, and giving monetary policy authorities cleaner, more comparable data.
The role of BIRD
Sitting alongside IReF is the Banks' Integrated Reporting Dictionary, or BIRD. Where IReF is the regulatory obligation, BIRD is the central data dictionary that establishes a common vocabulary across institutions. It is not mandatory, but it is a key enabler: banks that adopt BIRD can prepare and manage their data more consistently across IReF and other reporting requirements. In practical terms, BIRD helps bridge the gap between a bank's internal data architecture and the granular outputs IReF will require.
Connection to crypto financial statements and IFRS considerations
IReF is a statistical reporting framework rather than an accounting standard, so it sits outside the direct scope of IFRS crypto assets guidance or the FASB's ASC 350-60 fair-value model for crypto holdings. That said, the data-quality and granularity demands IReF imposes will inevitably touch asset classification, valuation inputs, and the ledger-level records that underpin crypto financial statements. Institutions carrying digital assets on their balance sheets will need those positions represented with the same precision IReF demands of any other asset class. The framework's emphasis on source-data accuracy, rather than template-level aggregation, raises the bar for everyone involved in producing or auditing financial statements that include crypto or digital asset positions.
The Revised Implementation Timeline
Based on an ECB press release dated 8 June 2026, KPMG's Digital Assets team has outlined three confirmed milestones:
| Milestone | Expected timing | Key detail |
|---|---|---|
| Public consultation on draft IReF Regulation | Second half of 2027 | Final legislative proposal shaped by consultation feedback; supervisors expected to publish further requirements ahead of publication |
| Start of one-year pilot phase | Q2 2030 | Reporting agents test ability to meet IReF data and process requirements with supervisors |
| First official IReF reporting (go-live) | Q2 2031 | One-year parallel reporting phase: existing statistical reporting continues alongside IReF submissions |
The significance of this schedule is not simply its dates. Previous IReF timelines were widely regarded as aspirational. The current one represents, for the first time, an implementation window of approximately 2.5 years between the pilot start and the consultation that precedes it, which KPMG describes as a realistic window rather than a postponement. That framing matters: it signals that supervisors view the framework as operationally ready to design against, even before the draft regulation appears.
Five Action Areas Banks Must Address
The KPMG analysis identifies five distinct domains where institutions need to act now. Each carries direct implications for the accounting and finance functions that sit alongside regulatory reporting teams.
1. Data governance
IReF demands highly granular data and strong controls to protect data quality end to end. The key shift is that corrections at the template or aggregate reporting level will no longer be acceptable on their own. Deviations and quality issues must be identified and resolved as early as possible within the data supply chain, and those corrections must be available consistently across all relevant functions and entities. For accounting teams, this means that the clean-data discipline now expected of regulatory reporting will need to extend into general ledger management, including ledger entries for digital asset positions where valuation can change intraday.
2. IT architecture
The technical infrastructure supporting IReF reporting must be scalable, resilient, and capable of handling correction submissions and the associated reporting processes. Initial target architecture blueprints are already beginning to emerge across the market, according to the KPMG analysis. Institutions that have not yet mapped their current architecture against future IReF requirements are already behind the curve of peers who have started that exercise.
3. Organisational integration and skills
IReF requires stronger integration between regulatory reporting functions and bank-wide management activities. Staff will need to be equipped with the knowledge to meet IReF-specific obligations. This is not simply a technology project. It is a structural change to how reporting teams relate to finance, risk, and senior management, a dynamic that CFOs and chief accounting officers should be shaping now rather than reacting to in 2030.
4. Embedding regulatory metrics in management steering
The ECB framework envisions an environment where regulatory metrics derived from reporting processes are embedded in management and steering activities, including performance monitoring, planning, and the definition of management actions. For accounting firms advising clients, this represents a meaningful shift in the status of regulatory reporting data. It moves from a compliance output to an input for business decisions, which changes both the governance model and the audit trail requirements around that data.
5. Target-state design and roadmap
KPMG recommends that institutions define a target state across five dimensions: IT architecture, data management, processes, organisation, and management. That target state then becomes the baseline against which current-state gaps are identified. The practical sequencing suggested is to begin with architecture and data management dimensions first, and to use the publication of the draft IReF Regulation in 2027 as the trigger to elaborate and finalise the remaining dimensions. A detailed roadmap aligned with the confirmed milestones allows work packages to be executed in a controlled and efficient manner rather than in a compressed sprint ahead of go-live.
Accounting and Audit Implications
The IReF framework does not directly amend accounting standards, but its downstream effects on financial statement quality and audit readiness are real.
For accounting firms and auditors
The move away from aggregate-level corrections toward supply-chain-level data quality means that audit trails must be traceable from the source transaction to the reported figure. Auditors reviewing regulatory reporting processes will increasingly need to assess data lineage controls, not just the final submission. For clients holding digital assets, this connects directly to the granularity already required under IFRS crypto assets guidance and, for US GAAP reporters with European operations, the fair-value measurement disciplines embedded in ASC 350-60. A client whose crypto bookkeeping relies on manual reconciliations and batch exports will struggle to meet IReF's source-data quality expectations.
For CFOs and finance directors at euro-area banks
The parallel reporting phase planned for the first year of go-live in 2031 means that teams will need to run two reporting regimes simultaneously. Budget cycles from 2027 onward should account for the additional headcount, systems investment, and external advisory costs that this will involve. The CFO's office should be part of the target-state design process from the outset, not brought in as an approver at the end. The integration of regulatory metrics into management steering specifically requires finance leadership to define which metrics matter and how they feed into planning processes.
Digital asset positions and IReF granularity
Banks with crypto or digital asset exposures face a specific challenge. The granularity IReF requires at the instrument and counterparty level is considerably higher than what many legacy statistical reporting templates demanded. Institutions that have been treating crypto positions as a residual or miscellaneous category within existing templates will need to reclassify and restructure that data well before the pilot phase opens. For advisers helping clients think through how stablecoins are accounted for under IFRS, the IReF data requirements add another layer of precision to an already complex classification exercise. The question of what the Tether KPMG attestation means for financial statement preparers is a useful reference point for how granular data expectations are already rising in the stablecoin space, a trend IReF will accelerate for banks more broadly.
What Accounting Firms Should Be Doing Right Now
The 2027 consultation is the next hard deadline in this timeline. That gives firms roughly a year to prepare clients before the regulatory text begins to take shape. The immediate priorities are:
Near-term steps for advisers and internal teams
- Map clients' current statistical reporting data flows against the IReF granularity requirements already published by the ECB and assess where source-data gaps exist.
- Review IT architecture readiness and flag scalability constraints before target-state design begins.
- Engage finance and management steering teams early, given IReF's explicit goal of embedding regulatory metrics in business decisions.
- Build IReF readiness into 2027 and 2028 budget proposals. The parallel reporting year in 2031 will require resourcing that takes years to plan and recruit for.
- For clients with digital asset positions, align crypto bookkeeping and ledger practices now with the source-data quality standard IReF will impose, rather than waiting for the draft regulation to clarify specifics.
The consultation in H2 2027 will be the first formal opportunity to influence the final legislative text. Firms that have already done the gap analysis will be far better placed to respond substantively and to advise clients on where to seek adjustments.
Frequently Asked Questions
What is the IReF and which institutions does it apply to?
IReF is the Integrated Reporting Framework developed by the European Central Bank to harmonise statistical reporting across euro-area banks. It applies to credit institutions in the euro area that are currently required to submit statistical data to national central banks and the ECB. The framework introduces more granular reporting requirements and replaces or consolidates a significant share of existing statistical reporting obligations.
When does IReF go live and what are the key dates between now and then?
The confirmed milestones are: a public consultation on the draft IReF Regulation in the second half of 2027, the start of a one-year pilot phase in Q2 2030, and the first official mandatory reporting in Q2 2031. A parallel reporting period running alongside existing statistical submissions is planned for the first year of go-live.
How does IReF interact with IFRS accounting standards for digital assets?
IReF is a statistical reporting framework, not an accounting standard, so it does not amend IFRS or FASB requirements directly. However, the granularity it demands at the instrument and counterparty level means that ledger-level data quality, including for digital asset positions, must meet a higher standard than most legacy statistical templates required. Institutions applying IFRS crypto assets guidance or the fair-value model under ASC 350-60 will need to ensure their source data is precise enough to feed both their accounting outputs and IReF submissions without manual adjustment at the aggregate level.
Is BIRD mandatory alongside IReF?
No. BIRD, the Banks' Integrated Reporting Dictionary, is a voluntary central data dictionary that the ECB makes available to help institutions standardise their data preparation. While IReF will be mandatory through regulation once the legislative process is complete, BIRD participation remains optional. That said, adopting BIRD is widely considered a practical enabler for IReF compliance, particularly for institutions that need to align data across multiple reporting domains.
What should accounting firms be doing to prepare clients before the 2027 consultation?
The priority is a current-state gap analysis covering data governance, IT architecture, and organisational readiness across relevant client entities. Firms should also help clients map their digital asset positions against IReF granularity expectations now, since reclassifying and restructuring that data is a multi-year exercise. The 2027 consultation is the first formal opportunity to shape the final regulation, and clients who have completed their gap analysis will be able to respond substantively and seek targeted adjustments to the draft text.
Source: KPMG Digital Assets