ESMA published its Final Report on the simplification of financial transaction reporting on 2 July 2026, and the headline writes itself: a single "report once" framework across MiFIR, EMIR and SFTR, with net savings the regulator frames at up to €1 billion a year once it lands. In plain terms, "report once" means one set of transaction data submitted once, rather than separately under MiFIR, EMIR and SFTR, with full rollout targeted for H2 2031. But the more useful way to read the report is against its own binding constraint. Every recommendation in it is bounded by a single principle - preserve information value - and once you take that principle seriously, it becomes the ceiling on how much cost can actually be removed. The savings are real, but they’re only what’s left over after ESMA has protected the supervisory dataset. That framing explains almost every choice in the document, including the ones ESMA declined to make.

Key Takeaways

• ESMA published its Final Report on 2 July 2026, closing the review it opened with a June 2025 Call for Evidence and continued through the May 2026 Interim Report.

• Core recommendation: a long-term Level 1 change integrating MiFIR, EMIR and SFTR into a single "report once" framework (Scenario 2a), with reporting infrastructure consolidated into one type of reporting venue.

• The structured intermediate step is gone. All three variants of Option 1a have been dropped as standalone measures - ESMA is going straight for full integration.

• Eight independent relief measures are recommended for earlier relief - two requiring Level 1 change, six achievable through ESMA's own Level 2/3 rulemaking.

• Delegated reporting for FC-to-NFC trades is the priority near-term fix for dual-sided reporting, one of the top three cost drivers identified across the review.

• The cost-benefit case: a three-to-four-year payback, 22–24% in annual savings, and a 10-year net benefit of €1.2bn to €4.9bn across the industry.

• Full rollout is targeted for H2 2031, contingent on Level 1 negotiations concluding by mid-2028.

• The real signal is the ceiling. Every recommendation is bound by the requirement to preserve information value - and the measures ESMA declined to take mark exactly where that ceiling sits.

The Problem ESMA Is Solving

The report reconfirms the cost drivers established through the Call for Evidence and the Interim Report. None of them is new, but the report is useful in ranking them and, more importantly, in tracing each back to a structural feature of the framework rather than to data volume. Five drivers matter:

• Regulatory change frequency. MiFIR, EMIR and SFTR are reviewed on separate sectoral timetables, so firms absorb a continuous wave of implementation projects rather than a one-off build. ESMA notes that change-management costs for major reporting entities are of a similar order of magnitude to their recurring run costs - which tells you the churn itself, not the reporting, is the expense.

• Inconsistency in terms and definitions. The same concept is defined differently across regimes, forcing translation layers and reconciliation logic that exist purely to bridge the frameworks.

• Dual-sided reporting. Under EMIR and SFTR both counterparties report the same trade, which generates pairing, matching, break investigation and correction work. Stakeholders are consistent that the reconciliation tail, not the submission itself, is the real cost - and for non-financial counterparties this is the single largest driver.

• Duplication in reference data and direct reporting. Economically equivalent trades - derivatives above all - are reported multiple times under different schemas and validation rules, with the enrichment and reference-data work duplicated each time.

• Fragmented submission channels and architectures. Parallel TR and ARM pipelines mean multiple technical connections, multiple sets of validations and feedback loops, and multiple fee relationships. This is the driver ESMA leans on hardest, because it is the one the target model is designed to collapse.

The Core Recommendation: Report Once (Scenario 2a)

The report inherited a two-step logic from the Interim Report - an intermediate structural step, then the long-term target - but the decisive move is that ESMA endorses the destination and declines to build the staircase. The structured intermediate step (Option 1a and its variants) is not recommended as a standalone stage; what survives of it is treated lower down, both as a targeted short-term measure and among the options ESMA rejected. That leaves one recommendation standing.

It is to fold MiFIR, EMIR and SFTR into a single modular template, submitted through one type of reporting infrastructure, with TRs and ARMs merged. Several things follow from that design, and they cut in different directions.

• It removes message-level duplication between MiFIR and EMIR - the same trade stops being reported twice under two schemas.

• It forces a single change environment. One template, reviewed once, ends the unsynchronized sectoral churn that is the top-ranked cost driver.

• It forces harmonized cost consideration. A single framework means changes have to be weighed against a single, visible cost base rather than smeared across three regimes.

• It is highly divergent from global OTC derivatives harmonization. The rest of the world has spent a decade converging on common derivative data standards; a bespoke EU mega-template pulls against that, and the report is candid that global alignment is a principle it is trading off here.

• The payback is genuinely long-term. On ESMA's own numbers the model reaches net benefit around three years after implementation - but implementation lands in 2031, so the break-even sits near the back end of the decade.

• It requires channel consolidation, and the details are unresolved. ESMA sets out three implementation models - existing (national), hybrid (national collection, EU storage/analytics), and full EU centralization - and explicitly declines to recommend one. The direction of travel is set; the architecture isn't.

None of this contradicts the thesis. "Report once" is the most that can be done precisely because it reorganizes the plumbing without dropping the data - it is simplification held to the information-value line. The savings come from collapsing channels and templates, not from collecting less.

The Eight Short-Term Measures

Because 2031 is a long way off, ESMA pairs the target with eight independent measures, each held to three conditions: quick to implement, cheap, and fully compatible with the eventual integrated model. Two need Level 1 change; six are within ESMA's gift at Level 2/3.

1. Extend mandatory delegated reporting (Level 1)

• Extend delegation so the financial counterparty reports on behalf of all non-financial counterparties, not just the sub-threshold NFC- population already covered under EMIR 9(1a).

• FC-FC and NFC-NFC allocation is left for later. ESMA proposes a Level 1 principle of delegation to the "most sophisticated counterparty" and a mandate to define that at Level 2/3 - which means those categories need further discovery before responsibility is settled.

• The benefit is conditional. If many or all current reporting counterparties still have to retain the capability to report - because they still have responsibility to report some transactions - then the operational saving is thinner than the headline suggests. Delegation reduces submissions; it only pays off fully if it also lets firms decommission reconciliation and, ideally, reporting build.

2. Streamline the EMIR Article 9 intragroup exemption (Level 1)

• Centralize the notification at EU level instead of filing with each NCA, and cut aggregated net-position reporting from weekly to monthly.

• Hard to criticize - reducing the process friction is straightforwardly good. But note what it doesn't do: it changes the mechanism of the exemption, not its scope. The exemption itself is neither extended nor loosened; the plumbing around it is simplified.

3. Reduce the MiFIR back-reporting horizon from five to three years (Level 2/3)

• Positive burden reduction, with an NCA override to request older data (up to five years) for targeted supervisory, market-integrity or enforcement cases. Record-keeping stays at five years.

• Worth flagging the comparison it stops short of: this is a horizon reduction, not the CFTC's no-action approach to correcting dead or expired trades. It trims how far back you routinely correct; it doesn't relieve the obligation to correct trades that no longer exist economically.

4. Targeted exemptions from MiFIR transaction reporting (Level 2/3)

• Broaden the RTS 22(5) exclusions: fund unit creation/redemption by fund managers, routine corporate actions with no market-abuse signal (keeping IPOs, takeover bids, placings and debt issuance), and employee share plans below a proportionate monthly threshold (c. €2,000 cumulative). High-volume, low-signal flow removed without touching the events that matter for surveillance.

5. Deprioritize a list of optional RTS 22/23 fields (Level 2/3)

NCAs would not prioritize supervisory action on a defined set of optional fields, without any schema change. The list:

F63 is deprioritized only for the LRGS, ILQD and SIZE values, which no longer align with the revised RTS 2 deferral flags; firms may keep existing arrangements where changing would be disproportionate.

6. Targeted adjustment of EMIR reconciliation - "name of the underlying index" (Level 2/3)

• This matches the FCA's direction on the same field. One nuance worth catching: ESMA's stated intent is not to remove the field from reconciliation outright, but to adjust supervisory expectations on break management for it - a softer, less-noticed move than a clean removal. As a free-text field it will never match cleanly across counterparties; the fix is to stop treating those breaks as a problem rather than to stop matching.

7. Simplify the EMIR Errors & Omissions notification framework (Level 2/3)

• The insight here is that the cost isn't the notification - it's the standing infrastructure firms run to decide whether one is needed, including in every case where nothing is ultimately filed. ESMA intends to revisit the thresholds and the process. Sensible, if under-specified.

8. SFTR reporting of trades where settlement fails (Level 3)

• Exclude SFTs from SFTR where the opening leg fails to settle before the T+1 deadline - a trade that never settles never creates the exposure SFTR exists to capture. This dovetails with the EU's move to T+1 in 2027, and ESMA is careful to keep settlement-fail monitoring under CSDR rather than let it leak back into SFTR.

What ESMA Left on the Table - and Why It Matters

The excluded options are the clearest test of the thesis, because this is where a burden-reduction argument runs straight into the information-value wall.

• FX derivatives out of MiFIR. Stakeholders argued FX derivatives are already fully covered under EMIR, so MiFIR reporting is pure duplication - and the FCA has been willing to act on exactly this. ESMA declined. Removing them now would shrink the MiFIR dataset ahead of a coordinated redesign, risking temporary gaps, and would then need re-engineering when 2a lands. The report's tell is that it argues the target model will be functionally equivalent to removing FX from MiFIR anyway - i.e. the same relief, but only once it can be delivered without ever thinning the data.

• Central-bank SFTs out of SFTR/MiFIR. Same logic. The scope reduction is only acceptable once the information is guaranteed to survive elsewhere in the integrated template, so it is deferred into 2a rather than taken now.

• The structured intermediate scenario (1a). Rejected not on principle but on arithmetic: non-negligible cost or data gaps, benefits that don't clearly clear the bar, and a real risk of sunk cost when the target model arrives. The useful fragment (delegated reporting for FC-NFC) is kept as a targeted measure; the scenario as a whole is not.

In every case the burden-reduction argument is sound on its own terms, and in every case it loses to the requirement not to reduce the data available to supervisors before an integrated replacement is ready. That is the ceiling. "Report once" is ESMA reaching as high as that ceiling allows - reorganizing how data flows rather than reducing what is collected - and the excluded options mark exactly where the ceiling sits.

Costs and Benefits

A word on the numbers, which are worth taking at face value rather than dwelling on. ESMA ran two cost-benefit analyses: a Deloitte study of 30 market participants, extrapolated to the full population by three separate methods, and its own survey of 18 NCAs plus the ECB-ESRB. The market-side result is consistent across all three extrapolations - a positive net present value, payback in three to four years, and 22–24% in recurring annual savings, close to the Commission's 25% burden-reduction target - with a 10-year cumulative benefit of €1.2bn to €4.9bn. The supervisory side expects significant one-off implementation costs offset by a 9–11% cut in running costs. The methodology is sound, but its real function is confirmatory: it puts quantified weight behind a direction the qualitative feedback had already set, rather than changing the conclusion.

Timeline

• Final Report published — 2 July 2026

• Level 1 changes finalized — mid-2028 (optimistic)

• Integrated Level 2 template complete — mid-2029

• IT development complete — mid-2030

• Full "report once" framework operational — H2 2031

The two Level 1 measures move at the pace of co-legislator negotiation, which is the dominant source of uncertainty. The six Level 2/3 measures run on a faster, ESMA-controlled track - Level 3-only changes could arrive in the short term, the coordinated Level 2/3 work over the medium term.

Frequently Asked Questions

What is the ESMA Final Report on transaction reporting simplification? It is ESMA's formal set of recommendations under its MiFIR Article 26(11) mandate, published 2 July 2026, calling for a long-term integration of MiFIR, EMIR and SFTR into a single "report once" framework, alongside eight nearer-term relief measures.

What is Scenario 2a, the "report once" framework? It integrates MiFIR, EMIR and SFTR into one reporting model, so market participants submit transaction data once through modular templates rather than separately under three regimes. It is ESMA's recommended long-term target, with full rollout estimated for H2 2031.

Is Option 1a still being considered? No. ESMA assessed all three sub-variants and recommended against implementing any of them as a standalone step, in favor of moving directly to Scenario 2a supported by the eight independent measures.

What is changing for dual-sided reporting under EMIR and SFTR? ESMA recommends expanding delegated reporting so that, for trades between a financial and non-financial counterparty, the financial counterparty reports on behalf of both sides by default - removing the reconciliation burden that stakeholders identified as a top cost driver, and the single largest driver for non-financial counterparties.

How much could the reforms save the industry? ESMA's cost-benefit analysis estimates 22–24% in annual savings under Scenario 2a, with implementation costs recovered in three to four years and a 10-year cumulative net benefit of €1.2bn to €4.9bn, depending on methodology. But those savings are what remains after the supervisory dataset has been protected - the information-value principle sets the ceiling.

Does the non-financial counterparty still have any reporting obligation once delegation applies? Yes. The NFC no longer submits the report, but stays responsible for providing accurate trade details to the financial counterparty and for the correctness of that data. Liability for data accuracy does not transfer with the reporting task; it moves upstream.

Does this change anything for firms right now? Not immediately. The Level 1 measures require EU legislative agreement; the Level 2/3 measures move faster but still require ESMA rulemaking. Treat this as a signal for infrastructure planning rather than an immediate compliance deadline.

When does the ESMA "report once" framework take effect? Level 1 changes are targeted for mid-2028, the integrated Level 2 template for mid-2029, and full rollout for H2 2031. The two Level 1 measures depend on EU co-legislator negotiation, which is the main source of timeline uncertainty.

The Bottom Line

The direction is now settled: no more phased structural experiments, a direct move to an integrated framework, backed by a cost-benefit case ESMA is prepared to defend. For reporting teams the planning question shifts from "which interim option do we build for" to "how do we stay adaptable until the real thing arrives." But the strategic read is simpler than the savings headline. ESMA has told the market how much cost it is willing to remove - and it is precisely the amount that can be removed without collecting less. The €1 billion is what simplification looks like when it is capped by the data.