ESMA Regulatory Reporting: MiFIR, EMIR, SFTR & How to Stay Compliant in 2026

ESMA (European Securities and Markets Authority) doesn't regulate investment firms directly — but it sets the rules that national competent authorities enforce, and it directly supervises trade repositories, credit rating agencies, and benchmark administrators. If your firm reports under MiFIR, EMIR, or SFTR, you are operating within ESMA's framework, and the technical standards underpinning each regime update regularly.

This guide covers the three core ESMA reporting regimes, what changed recently, the most common compliance failures, and how to build a reporting programme that can absorb ongoing regulatory updates.

MiFIR Transaction Reporting

MiFIR (Markets in Financial Instruments Regulation) requires investment firms to report all transactions in financial instruments admitted to trading or traded on EU venues to their national competent authority (NCA) by the end of the next business day (T+1).

The obligation is broad: it covers equities, bonds, derivatives, structured products, and emission allowances. Reportable events include executions on behalf of clients, own-account trading, and certain reception and transmission of orders. The key question is whether the instrument is within scope — MiFIR reporting scope is defined by whether the instrument is traded on an EU trading venue, not by where the trade itself occurs. A firm trading a London-listed instrument on a US venue may still have MiFIR reporting obligations.

MiFIR 2: What Changed

MiFIR 2 (Regulation (EU) 2024/791) entered into force in June 2024, with phased application through 2025 and 2026. The key changes for transaction reporting:

• Consolidated tape: MiFIR 2 mandates the creation of a consolidated tape for equities, ETFs, and bonds — a long-awaited reform to European market data fragmentation. New tape providers will be authorised by ESMA.
• New reporting fields: MiFIR 2 introduced additional fields for transaction reports, including new counterparty identification requirements and changes to how algorithmic trading is flagged.
• T+1 settlement: The EU is moving toward T+1 settlement in 2027. MiFIR reporting timelines will need to align with the accelerated settlement cycle.
• Systematic internaliser (SI) regime: MiFIR 2 revised the SI calculation methodology, changing which firms qualify as SIs and therefore their pre- and post-trade transparency obligations.

The ESMA technical standards implementing MiFIR 2 changes are being published in phases. Compliance teams need to track ESMA's consultation papers and final technical standards, not just the regulation text itself.

EMIR: OTC Derivative Reporting

EMIR (European Market Infrastructure Regulation) requires both counterparties to an OTC derivative contract to report trade details to an authorised trade repository (TR) by T+1 after execution, modification, or termination. Unlike MiFIR — where the investment firm reports — EMIR imposes reporting obligations on both sides of the trade. This creates the possibility of mismatches between counterparty reports, which trade repositories must flag and firms must reconcile.

EMIR 3: What Changed

EMIR 3 (Regulation (EU) 2024/2) entered into force in February 2024, with most provisions applying from October 2025 or later. Key EMIR 3 changes:

• ISO 20022 XML format: EMIR 3 mandates a new ISO 20022 XML reporting format, replacing the previous CSV-based structure. This requires significant technical changes to reporting systems.
• Expanded reporting fields: The number of reportable fields increased substantially, adding more granular data on collateral, margins, and counterparty details.
• Active account requirement: EMIR 3 introduced an "active account requirement" requiring certain firms to hold an active clearing account at an EU CCP for specific categories of systemically important OTC derivatives — a response to concerns about EU market infrastructure dependence on LCH (UK).
• Revised thresholds: EMIR 3 modified how clearing thresholds are calculated for NFC counterparties.

The EMIR 3 reporting changes represent some of the most operationally demanding in recent years. Firms that delegated EMIR reporting to their FCM or prime broker need to confirm that their delegation arrangements cover the new EMIR 3 requirements.

"EMIR 3's ISO 20022 format change is not a like-for-like field mapping exercise. The new schema introduces new concepts and validation rules. Firms that have been running EMIR reporting on autopilot since 2017 will face a meaningful rebuild, not just a patch."

SFTR: Securities Financing Transaction Reporting

SFTR (Securities Financing Transactions Regulation) requires daily T+1 reporting of all securities financing transactions (SFTs) to an authorised trade repository. SFTs include:

• Repurchase agreements (repos and reverse repos)
• Securities lending and borrowing
• Buy-sell backs and sell-buy backs
• Margin lending transactions

Like EMIR, SFTR is a dual-sided reporting regime — both counterparties must report. SFTR applies to EU financial counterparties and branches of third-country entities. Non-financial counterparties are currently exempt from SFTR reporting obligations, though this may change under a future review.

SFTR reports are highly complex — the maximum number of reportable fields per transaction is 155, covering collateral details, haircuts, reuse of collateral, and detailed counterparty information. The reconciliation rate between counterparty reports is significantly lower for SFTR than for EMIR, in part because of the complexity of collateral data requirements.

AIFMD II and Fund Reporting

AIFMD II (the revised Alternative Investment Fund Managers Directive) entered into force in April 2024. While not strictly a "reporting regime" in the same sense as MiFIR/EMIR/SFTR, it introduced significant changes to AIFM reporting obligations:

• Revised Annex IV reporting: AIFMD II updated the Annex IV reporting template — the periodic report AIFMs submit to their NCA covering fund leverage, assets, and investor exposure.
• Loan origination funds: AIFMD II introduced a new framework for loan-originating AIFs, with specific reporting requirements for fund-level leverage and concentration.
• Delegation and outsourcing: New requirements for AIFMs to report on delegation arrangements to NCAs.

ESMA is in the process of updating its AIFMD technical standards to reflect AIFMD II. Fund managers need to track ESMA's Level 2 technical standards pipeline alongside their Annex IV reporting workflows.

Common ESMA Reporting Failures

Enforcement by national competent authorities has increased significantly since 2022. The most common failure patterns across ESMA's reporting regimes:

LEI lapses: Legal Entity Identifiers expire if not renewed annually. An expired LEI invalidates transaction reports — MiFIR reports with an expired counterparty LEI are rejected. Firms that don't actively manage their LEI portfolio (and their counterparties' LEIs) accumulate reporting breaks.

Incorrect field population: The technical standards for MiFIR, EMIR, and SFTR define field population logic in significant detail. Q&As from ESMA and NCAs frequently clarify edge cases. Firms that haven't reviewed Q&As since their initial implementation may be populating fields incorrectly without knowing it.

Late submissions: T+1 deadlines are strict. Operational incidents that delay reporting generate immediate compliance risk. Many firms don't have adequate escalation procedures for reporting failures — they discover the break after the deadline has passed.

Reconciliation breaks: For dual-sided regimes (EMIR, SFTR), trade repositories flag unmatched or mismatched reports. Firms that aren't actively monitoring their reconciliation rates at the TR allow break populations to accumulate, which creates regulatory exposure and operational complexity to unwind.

Missing guidance updates: ESMA and NCAs publish Q&As, updated validation rules, and guidance notes continuously. Firms that validated their reporting against the 2020 technical standards may not have picked up 2023 or 2024 updates that changed specific field requirements.

How to Build a Scalable ESMA Reporting Programme

ESMA's reporting regimes are not set-and-forget: the technical standards, validation rules, and interpretive guidance update continuously. A reporting programme designed for 2020 requirements is not compliant with 2026 requirements without active maintenance.

Governance: Assign clear ownership for each reporting regime. MiFIR, EMIR, and SFTR have different counterparty scopes, different technical standards owners, and different NCA contacts. Siloed ownership leads to gaps where cross-regime interactions (a derivatives trade that also generates SFT collateral flows, for example) fall between teams.

Validation infrastructure: Implement pre-submission validation against current technical standards. Many reporting failures can be caught before submission — but only if validation rules are updated when ESMA publishes new versions. A static validation ruleset from 2021 will not catch 2024 field requirement changes.

Break management: For EMIR and SFTR, establish a daily process for reviewing trade repository reconciliation reports. Set thresholds for acceptable break rates and escalation procedures when thresholds are breached.

Regulatory monitoring: ESMA publishes updates relevant to these reporting regimes from multiple units: the Markets Infrastructure and Reporting team, the Investment Management team, and the Capital Markets Union teams all generate relevant publications. NCAs add a second layer — AFM, BaFin, AMF, FCA, CSSF, and others publish jurisdiction-specific guidance that can go beyond the ESMA baseline.