Transaction Reporting Simplification: ESMA’s EUR 1bn Plan

ByOfficer

On 2 July 2026, ESMA put a price on something reporting teams have grumbled about for years. The regulator published its final report on the transaction reporting simplification agenda and estimated that cutting duplication across EMIR, MiFIR and SFTR could save the industry up to EUR 1 billion a year. The figure sits at the top of a cost-benefit range that starts at EUR 250 million, and it is the headline of a report that runs to a genuine reform proposal rather than a wish list.

Read the small print before rebuilding anything. The report is a set of findings and recommendations, built on a cost-benefit analysis. It is not a rule change. No reporting field is added or removed today. The EMIR REFIT reporting standards, the MiFIR Article 26 transaction reporting obligation and the SFTR Article 4 reporting obligation all stand exactly as they did on 1 July. What ESMA has done is set a direction and attach a number to it, and that number is large enough that firms should start mapping their exposure now.

ESMA Chair Verena Ross framed transaction reporting as central to market transparency, risk monitoring and detecting market abuse, and described the report as a decisive step to simplify the system. For reporting officers at banks, investment firms, fund managers and clearing members, the practical question is narrower: what does a “report once” future do to the pipelines they run today, and what should they be doing while the legislators and rule-writers catch up.

Related reading: our EMIR reporting guide

The EUR 1 billion figure, and what sits behind it

The report is ESMA12-1406959660-3235, published on 2 July 2026. Its central claim is that a simplified transaction reporting framework could deliver annual net savings of between EUR 250 million and EUR 1 billion once implemented. ESMA’s cost-benefit analysis also points to a reduction in recurring reporting costs of roughly 22 to 24 percent, ten-year discounted cumulative net benefits in the region of EUR 1.2 billion to EUR 4.9 billion, and recovery of the up-front build cost within three to four years.

Those are net figures. They already subtract the implementation cost of moving to a new framework, which is the part that lands on reporting teams first. The savings are also a projection, contingent on measures being adopted through the normal legislative and technical-standards process. A firm that reads “up to EUR 1 billion” as money arriving next year has misread the document. The realistic reading is that the recurring cost of running EMIR, MiFIR and SFTR reporting side by side is high enough that ESMA now has a quantified mandate to attack it, and that the payback horizon is measured in years, not quarters.

The report did not appear from nowhere. It closes out a process that ran through an interim report on 4 May 2026 (ESMA12-1406959660-3175), drew on more than 100 responses to ESMA’s Call for Evidence on a comprehensive approach for the simplification of financial transaction reporting, and included an open public hearing on 28 May 2026. The July report converts that evidence base into a costed recommendation.

Key dates on the transaction reporting simplification track

This is a multi-year reform, so the calendar matters more than any single deadline. The dates below are the ones a reporting team should hold in view.

  • 29 April 2024: the current EMIR REFIT reporting standards (the RTS in Commission Delegated Regulation (EU) 2022/1855 and the ITS in Commission Implementing Regulation (EU) 2022/1860) became applicable. This is the baseline the simplification would change.
  • 29 September 2025: the MiFIR Review’s statutory deadline for ESMA to submit updated draft RTS on Article 26 transaction-report details. ESMA’s 23 June 2025 final report on RTS 22 explicitly declined to submit a draft RTS by this date, folding the work into the comprehensive Call for Evidence that produced the simplification report instead; Commission Delegated Regulation (EU) 2017/590 remains the applicable RTS.
  • 4 May 2026: ESMA publishes its interim report (ESMA12-1406959660-3175), built on more than 100 Call for Evidence responses.
  • 28 May 2026: ESMA holds an open public hearing on the proposals.
  • 2 July 2026: ESMA publishes the final report (ESMA12-1406959660-3235) with the cost-benefit analysis and the up-to-EUR 1 billion estimate.
  • 2027: ESMA plans to present the RTS and ITS for the integrated collection of funds’ data, the parallel simplification track running alongside transaction reporting.
  • 29 March 2028: the statutory deadline under MiFIR Article 26(11), added by the MiFIR Review, for ESMA to report to the Commission on the feasibility of more integration in transaction reporting and less duplication across MiFIR, EMIR and SFTR.

The three regimes in scope: EMIR, MiFIR and SFTR

The simplification agenda covers three separate reporting regimes that grew up independently, each with its own legal base, its own technical standards and its own destination for the data.

EMIR, Regulation (EU) No 648/2012, requires counterparties and CCPs to ensure that derivative contracts, and any modification or termination, are reported to a trade repository under Article 9, subject to the responsibility-allocation rules in Article 9(1a) to 9(1f). The reporting standards were rebuilt for EMIR REFIT and have applied in their current form since 29 April 2024. MiFIR, Regulation (EU) No 600/2014, requires investment firms to report executed transactions in in-scope financial instruments to their national competent authority under Article 26, with the current RTS 22 remaining Commission Delegated Regulation (EU) 2017/590 until the revised RTS starts applying. SFTR, Regulation (EU) 2015/2365, requires SFT counterparties to report securities financing transactions, such as repos, securities lending and margin lending, to a trade repository under Article 4 on a T+1 basis, subject to the responsibility-allocation rules in Article 4(3). Our guide to MiFIR transaction reporting and our SFTR reporting explainer set out each regime in detail.

The overlap is where the cost lives. A single interest rate swap between two EU financial counterparties is reportable under EMIR to a trade repository, from both sides. If that instrument is admitted to trading on a venue, the transaction is also reportable under MiFIR Article 26 to the competent authority. A repo used to fund a bond position is an SFTR report. The same legal entity identifiers, the same unique trade identifiers and much of the same reference data are re-keyed into three different schemas, validated against three different rule sets and reconciled through separate channels. The current regimes already rely on structured reporting standards: EMIR REFIT uses ISO 20022 XML schemas, SFTR reporting uses ISO 20022 XML templates, and MiFIR transaction reporting is built around detailed field-by-field XML reporting guidance. That existing standardisation is one reason ESMA considers a common modular structure achievable.

Why duplication costs so much today

When ESMA asked the market what drives the cost and complexity of transaction reporting, the answers clustered around a few themes. Respondents pointed to overlapping and inconsistent requirements across regimes, regulatory changes that arrive frequently and out of step with each other, fragmented reporting channels, and dual-sided reporting that forces two counterparties to describe the same trade and then reconcile the two versions.

Each of those has a direct operational cost. Unsynchronised change cycles are a good example. EMIR REFIT moved to its current standards on 29 April 2024, while MiFIR and SFTR run on their own change timelines. A reporting team ends up rebuilding overlapping data logic more than once, because the regimes that share fields do not upgrade together. Dual-sided reporting adds a reconciliation burden that exists only because two firms report the same economic event separately, and reconciliation breaks then consume analyst time that produces no supervisory value.

The point that teams sometimes miss is what “report once” is aiming at. The target is an architecture that collects a data point once and lets authorities with different mandates reuse it, so a firm supplies the same identifier and reference field a single time rather than three times over. No portal is about to appear and swallow all three regimes overnight; the near-term measures are far more modest than that end state, and understanding the gap between the two is the difference between sensible preparation and premature spend. The EBA’s own supervisory reporting simplification work on the prudential side shows the same instinct at play across the EU reporting stack.

The two-track plan: near-term fixes and a long-term architecture

ESMA recommends a staged approach, and reading the two stages separately keeps expectations honest.

The intermediate measures are the ones that could move without waiting for a rebuilt framework. ESMA points to expanding delegated reporting arrangements so that more firms can pass the mechanics of reporting to a counterparty or service provider, simplifying the procedures around intragroup exemptions, and making targeted adjustments that remove low-value or duplicative requirements. These are trims and process changes to the regimes as they stand, and they are where any early relief is most likely to come from.

The long-term measure is the structural one: a single integrated transaction reporting framework across MiFIR, EMIR and SFTR, built on a common modular structure that reflects the specificities of different products, with data reusable across authorities and supervisory mandates. This is the “report once” principle in its full form. It is also the part that requires Level 1 and Level 2 change, which is why the timeline stretches toward the 29 March 2028 milestone and beyond rather than resolving inside 2026.

What “report once” does not mean for your obligations

Because the phrase is easy to over-read, it helps to state the boundaries plainly.

It does not mean a single existing system you can migrate to now. The integrated framework is a design ESMA is recommending, not a live utility with a connection specification. It does not mean your current obligations are suspended or relaxed. Until Level 1 and the supporting technical standards change, EMIR Article 9, MiFIR Article 26 and SFTR Article 4 apply in full, on their current formats and timelines. It also does not remove the need to identify the entity legally responsible for each report. Voluntary delegation under EMIR or SFTR does not normally transfer responsibility away from the counterparty or entity responsible for reporting, but both regimes also contain mandatory responsibility-allocation rules for specific relationships, including financial counterparties reporting for certain non-financial counterparties and fund managers reporting for UCITS or AIFs. Wider delegated reporting will make that allocation more important, because more firms may rely on third parties while still needing clear accountability for the submitted data.

Treating the report as a signal rather than an instruction is the correct posture. Nothing in it changes what applies today, and its value is showing where the requirements are heading.

The legislative backdrop already points this way

The July report is not an isolated idea. The MiFIR Review, Regulation (EU) 2024/791 of 28 February 2024, already amended Article 26 and inserted Article 26(11), which requires ESMA to report to the Commission by 29 March 2028 on the feasibility of more integration in transaction reporting and the streamlining of data flows, explicitly to reduce duplicative or inconsistent requirements across MiFIR, EMIR and SFTR. The same review set the 29 September 2025 date for updated Article 26 RTS. On the derivatives side, EMIR 3, Regulation (EU) 2024/2987 published in the Official Journal on 4 December 2024, continues to reshape the EMIR framework, including the Active Account Requirement that brought its own reporting templates. Firms tracking that strand can see how a new EMIR obligation turns into filing detail in the ESMA active account reporting templates.

The 2026 simplification report and the 2028 Article 26(11) report are distinct documents with distinct legal footing, and it is worth keeping them apart. The July report is ESMA’s response to the burden-reduction agenda and its own Call for Evidence. The 2028 report is a hard statutory deliverable written into MiFIR. They pull in the same direction, which is why the “report once” language now has both a costed business case and a legislative anchor behind it.

What reporting teams can do now

Nothing in the report obliges a firm to act. That said, the teams that come through the transition cheaply will be the ones that used the lead time, and the preparatory work is low-regret because it improves data quality under the current regimes regardless of what the reform finally looks like.

The first step is a mapping exercise. When I sit with a reporting inventory, the overlaps are rarely where people expect: a venue-traded derivative that generates an EMIR pair report and a MiFIR Article 26 report from the same booking, with the LEI and the instrument reference data sourced differently for each, is the kind of duplication that a “report once” model would collapse. Knowing which of your flows are genuinely duplicative, and which only look similar, tells you where a future saving is real.

From there, the practical list is short. Inventory your delegated reporting arrangements and your intragroup exemptions, because those are the two levers the intermediate measures touch first. Keep reference-data hygiene tight, particularly LEI renewal and unique trade identifier generation, since a common framework will be built on shared identifiers and will expose weak data faster than three separate schemas do. Track the RTS and ITS pipeline rather than the press coverage, because the operative detail will land in technical standards. And engage through the consultation process while the design is still open, since the intermediate measures are the parts most likely to be shaped by practitioner feedback. Our SFTR reporting explainer is a useful reference point when you scope which securities financing flows sit inside the overlap.

Frequently Asked Questions

Does the 2 July 2026 report change my EMIR, MiFIR or SFTR reporting obligations?

No. The report is a costed recommendation, not a legal instrument. EMIR Article 9, MiFIR Article 26 and SFTR Article 4 continue to apply on their current formats and timelines. Any change will come through amendments to the Level 1 regulations and the supporting technical standards, which follow their own legislative timetable.

Is the EUR 1 billion saving guaranteed?

No. EUR 1 billion is the upper bound of a projected annual net savings range that starts at EUR 250 million, drawn from ESMA’s cost-benefit analysis. It assumes the simplification measures are adopted, it is net of implementation cost, and ESMA estimates the up-front build is recovered within three to four years rather than immediately.

What does “report once” actually mean in practice?

It describes a target design in which a data point is collected once and then reused by authorities with different mandates, instead of a firm supplying overlapping data separately under three regimes. In the near term it does not exist as a single system. The immediate measures are narrower: wider delegated reporting, simpler intragroup exemptions, and removal of low-value or duplicative fields.

If delegated reporting is expanded, who is responsible for errors?

Responsibility depends on the legal allocation of the reporting obligation. Voluntary delegation does not normally move responsibility away from the counterparty or entity responsible for reporting. However, EMIR and SFTR also contain mandatory responsibility-allocation rules, including financial counterparties reporting for certain non-financial counterparties and fund managers reporting for UCITS or AIFs. Firms should map the entity legally responsible for each flow before relying on a delegate.

Does this affect UK EMIR and UK MiFIR reporting?

No. ESMA’s report concerns the EU regimes. UK EMIR and UK MiFIR are separate onshored frameworks supervised by the Bank of England and the FCA and are not covered by this EU simplification work. Firms reporting under both should not assume the EU changes flow across to their UK obligations.

When should we expect concrete changes?

The intermediate measures could move earlier where they can be delivered through supervisory, Level 2 or Level 3 action. The integrated framework requires Level 1 change and new Level 2 work. ESMA’s final report says that, in an optimistic scenario, Level 1 changes would be in place by mid-2028, the integrated Level 2 template could be completed by mid-2029, and the fully integrated solution could be in place toward H2 2031. Planning around a multi-year horizon is realistic; planning around a 2026 go-live is not.

How does this connect to the funds reporting simplification?

It is a parallel track. Alongside transaction reporting, ESMA is working on the integrated collection of funds’ data, with RTS and ITS expected in 2027. The two share the same simplification logic of collecting data once and reusing it, but they are separate deliverables with separate timelines.

Related Articles

Key Takeaways

  • ESMA’s 2 July 2026 final report (ESMA12-1406959660-3235) estimates that simplifying EU transaction reporting could save the industry between EUR 250 million and EUR 1 billion a year in net terms.
  • The report is a recommendation, not a rule change. EMIR, MiFIR and SFTR reporting obligations are unchanged until Level 1 and the technical standards are amended.
  • ESMA proposes a two-track path: near-term intermediate measures (wider delegated reporting, simpler intragroup exemptions, removal of low-value or duplicative fields) and a long-term integrated “report once” framework.
  • “Report once” is a target design for collecting data once and reusing it across authorities, not a single portal that exists today.
  • EMIR and SFTR both contain mandatory responsibility-allocation rules alongside voluntary delegation, a point that matters more as delegated reporting expands.
  • The direction has a legislative anchor: MiFIR Article 26(11), added by Regulation (EU) 2024/791, requires ESMA to report to the Commission on greater integration by 29 March 2028.
  • Low-regret preparation now includes mapping overlapping data flows, inventorying delegated arrangements and intragroup exemptions, and tightening LEI and unique trade identifier hygiene.
  • The EU simplification does not touch UK EMIR or UK MiFIR reporting, which remain separate onshored regimes.

Sources and References

Reading the direction of travel

The EUR 1 billion headline will do its job of getting the report read. The more useful signal for a reporting team is quieter: a regulator with a legislative mandate to reduce duplication has now attached a costed business case to it, and has named the specific levers it will pull first. Nothing here obliges a firm to change a single field today, but the overlaps a firm tolerates across EMIR, MiFIR and SFTR are now on a supervisory list of things worth removing. The firms with clean identifiers and a clear map of their duplicative flows will be the ones that capture the saving rather than pay for the rebuild.

Last updated: July 2026

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts

  • EMIR Active Account Requirement: ESMA’s First Effectiveness Report

    On 6 July 2026, the European Securities and Markets Authority (ESMA) published the first stage of its effectiveness assessment of the EMIR Active Account Requirement, together with the first annual report of the Joint Monitoring Mechanism. The rule applies to financial and non-financial EU counterparties that are subject to the EMIR clearing obligation and meet…

  • MiCAR Reporting Obligations for CASPs: Complete Implementation Guide

    Last updated: March 2026 Introduction MiCAR (Markets in Crypto-Assets Regulation) creates the first comprehensive regulatory framework requiring crypto-asset service providers to implement authorization, prudential reporting, transaction monitoring, and incident notification systems. The Markets in Crypto-Assets Regulation (Regulation (EU) 2023/1114) represents the first unified rulebook for crypto-asset activities across the entire European Union. For reporting teams…

  • CRR Article 430a Immovable Property Loss Data: The 2025 Hard Test

    On 6 July 2026 the European Banking Authority published its 2025 immovable property loss data: the annual dataset of losses and exposures for residential and commercial property across the EU and EEA. For a standardised-approach credit-risk reporting team, that dataset does real work. It is one of the inputs that decides whether the preferential risk…