The EBA wants to cut your reporting burden in half — read the fine print

Here's a small exercise. Pull up the list of supervisory reporting templates your team submits to your regulator — COREP, FINREP, large exposures, liquidity, whatever applies. Now ask yourself: how many of those data points are generated by a clean, automated pipeline, and how many involve somebody copy-pasting from a spreadsheet, manually reconciling two systems, or emailing a colleague in another department to ask "is this number right?"

If you're honest, the ratio is probably worse than you'd admit in a board pack.

I bring this up because the EBA just proposed something that sounds like very good news on the surface. They want to cut the number of data points in EU harmonised supervisory reporting by approximately 50%. The consultation launched in April, a public hearing was held on 5 May, and responses are due by 10 July 2026. Target implementation is September 2027.

Fifty percent fewer data points. Unprecedented simplification. That's the headline.

The reality is more complicated, and if you run a reporting or data team at a mid-market bank with EU exposure, you need to understand what's actually happening before you celebrate.

The 50% reduction is real — Bloomberg Law confirmed the figure — but it's the net number after a much messier set of changes. The EBA isn't just deleting half the fields and going home. They're doing three things simultaneously.

First, they're folding stress-test and benchmarking data collections into the regular reporting framework. If you've been treating your annual stress-test submission as a separate exercise — different data extracts, different validation rules, different sign-off process — that's over. Those fields now need to be production-quality, submitted on a regular cycle, not assembled in a war room once a year.

Second, they're adding new data points for IFRS 18, ESG disclosures, and FRTB. These aren't small additions. ESG data alone touches parts of the loan book that most mid-market banks have never had to report on at field level.

Third, they're removing the data points that are genuinely redundant or unused. That's where the net 50% comes from — you lose a lot of old fields, but you gain a set of new ones that are harder to source.

The XBRL.org summary puts it plainly: the EBA is integrating multiple ad-hoc collections into one framework. That's not simplification in the sense your CFO is imagining. It's consolidation. And consolidation means your reporting pipeline needs to handle data it currently doesn't touch.

I'll admit something. Years ago, a regulator announced a "streamlining" of a reporting framework I was responsible for. I told my manager the project would take two months. It took six. The reduction in templates masked a complete reshaping of the underlying data requirements, and I'd read the press release instead of the consultation paper. I don't enjoy telling that story, but it's exactly what I see happening here.

The team looks at the headline — "50% fewer data points" — and assumes the project is a pruning exercise. Remove some fields, update some templates, done by Q3.

Then somebody actually reads the consultation document and realises the stress-test data that used to be assembled manually once a year now needs to flow through the same automated pipeline as your monthly COREP submission. And the ESG fields require data from the loan origination system that has never been connected to the reporting warehouse. And the FRTB fields need market-risk data at a granularity the current extract doesn't support.

What looked like a simplification project becomes a re-architecture project. The timeline stays the same. The budget doesn't.

If the answer is no, that's the size of the gap you're looking at. And September 2027 is closer than it feels.

Large banks with dedicated regulatory reporting teams will absorb this. They have the infrastructure, the headcount, and the vendor relationships to re-plumb their pipelines in time.

Mid-market banks — especially those with EU subsidiaries that report under the EBA framework while the parent reports under PRA rules — are in a harder spot. The reporting team is smaller. The data infrastructure is often a patchwork of vendor systems, internal databases, and spreadsheets held together by institutional knowledge. Adding stress-test data and ESG fields to a pipeline that was already fragile is not a small ask.

And if you're a UK bank that doesn't report to the EBA directly but has EU-regulated entities that do, there's a coordination problem on top of everything else. The subsidiary's reporting requirements just changed shape, and the group data warehouse may not be set up to feed it.

This week, download the EBA consultation paper and ask your head of regulatory reporting one question: which of the new data points — stress-test integration, ESG fields, FRTB — can our current pipeline produce automatically, and which ones would require a new data source or a manual workaround? Don't wait for the final rules. The consultation closes 10 July. If you haven't mapped the gaps by then, you're already behind the banks that have.

— Aksel

The Analytical Banker is a weekly note on data, analytics, and AI inside corporate banking — written for finance leaders who actually have to make this stuff work. Reply to this email if something here resonates, or forward it to a colleague who'd benefit.