← Insights

IReF in 2031: what the ECB’s timeline means for supervisors everywhere

The Eurosystem has set a 2031 go-live for its Integrated Reporting Framework. Why it matters beyond the euro area, and five things to do now.

Jess Luper · 9 November 2026 · 5 min read

In June 2026 the Eurosystem set out the milestones for its Integrated Reporting Framework, IReF: a one-year pilot from the second quarter of 2030 and go-live in the second quarter of 2031, followed by a period of parallel reporting. It brings banks' separate statistical reporting requirements into one framework. Five years can sound like a long way off. For anyone who has run a reporting change, it is not.

Q2 2031IReF go-live, after a one-year pilotECB, 8 Jun 2026 →
Q2 2030start of the IReF pilot phaseECB, 8 Jun 2026 →
Sep 2018AnaCredit loan-by-loan reporting began, the euro area’s first big granular datasetECB →

What the ECB actually decided

The decision is about timing and commitment. IReF moves from design to delivery, with dates that banks, national central banks and software providers can plan against. The ECB says the goal is a lighter reporting load for banks over time, by integrating requirements that are reported separately today (ECB). Underneath that is a bigger shift: from templates designed around questions to granular data from which many questions can be answered.

Why it matters outside the euro area

IReF is a euro area project, but the direction is global. The Bank of England's February 2026 discussion paper on Future Banking Data reviews what the PRA collects and how often (Bank of England), and authorities in Asia and the Americas have their own granular programmes. When the largest supervisors move from templates to data, vendors, standards and expectations follow. Smaller authorities will feel the pull whether or not they plan for it.

IReF is a five-year programme. The decisions that make it easy or hard are the ones supervisors take this year.

What changes for supervisors

Three things. The data model becomes the asset that matters, so it needs owners, versioning and governance like any other supervisory instrument. Validation has to work at a much larger scale and as data arrives, not in a batch after the deadline. And analysts move from reading templates to querying data, which needs different tools and skills. None of these waits for 2031. Each can start with one dataset.

A practical path for smaller authorities

You do not need IReF's scale to get its benefits. Pick one question your templates answer badly, collect the smallest granular dataset that answers it, run it alongside the existing return and prove the numbers reconcile. Our guide to granular data reporting sets out the steps.

Put it to workFive things to do before 2031, wherever you supervise
  1. 1Name an owner for your supervisory data model, separate from any single return.
  2. 2List the figures you collect more than once across returns, and pick one to define once.
  3. 3Choose one granular dataset to pilot alongside an existing template.
  4. 4Make sure your validation runs as data arrives, not after the deadline.
  5. 5Ask your platform provider how a move to granular collection would work, and how long it would take.

Source: ECB, press release, 8 June 2026. For the standards behind it, see data standards, explained.

Share this articleShare on LinkedIn
Was this useful?
Free PDF · 21 pagesThe supervisory data standards field guide.XBRL, validation, DPM, SDMX and more, each with sourced facts and a checklist.Get the guide →

For supervisors

New guides and Insights, by email

One short email when we publish something worth your time, from Jess Luper. No spam, unsubscribe any time.

Our view

RegTech and SupTech are converging on real-time supervision by 2030. Line4 is built for that: checks at the gate in seconds, AI you can audit, and a switch that takes a week.

Where next