ESMA MiFIR Transaction Reporting

Understand, validate and oversee EU MiFIR transaction reporting with confidence

EU MiFIR transaction reporting is designed to support market abuse surveillance and regulatory oversight by requiring investment firms to submit complete and accurate transaction reports to their National Competent Authority (NCA). The obligation is set out in Article 26 of MiFIR and supported by RTS 22 and ESMA reporting guidance.

For firms in scope, the challenge is not simply sending files to an ARM or competent authority. It is demonstrating that reportable transactions have been identified correctly, that client, trader, algorithm and instrument data is complete and accurate, and that there are policies and controls in place to ensure accurate reporting.

What is EU MiFIR Reporting?

EU MiFIR transaction reporting refers to the obligation under Article 26 of MiFIR for investment firms that execute transactions in financial instruments to report the complete and accurate details of those transactions to the competent authority no later than the following working day after execution. The list of reportable fields, corresponding formats, and timelines by when reports need to be submit are specified in Commission Delegated Regulation 2017/590 (RTS 22)

The MiFIR transaction reporting regime is not a trade repository framework. It is a transaction surveillance regime designed to support competent authorities in monitoring markets and identifying market abuse and supervisory issues.

Who is required to report under EU MiFIR reporting?

EU MiFIR transaction reporting applies to EU investment firms and EU branches of third-country firms that execute transactions in financial instruments in scope under Article 26. Reports are often submitted via an Approved Reporting Mechanism (ARM), but the legal obligation remains centred on the investment firm.

Scope and EU nexus

EU MiFIR transaction reporting encompasses transactions executed by EU investment firms and their global branches, as well as non-EU entities executing transactions through their EU branches.

The reporting obligation captures transactions in financial instruments admitted to trading or traded on a trading venue, or where the underlying is such an instrument, subject to the detailed perimeter in Article 26(2) and RTS 22. Scope analysis often turns on product coverage, execution model, venue status and the investment-firm role in the transaction.

For cross-border firms, that makes instrument reference data, entity scoping, client and trader mapping, and execution flow analysis especially important. In practice, firms need to be confident not just that they understand the legal perimeter, but that they can apply it consistently across order flow, allocation models and reporting workflows.

What must be reported?

EU MiFIR transaction reports include prescribed details relating to:

• the entity executing the transaction

• persons or algorithms responsible for the investment decision and execution

• details of the buyer and seller of the transaction

• details of the people or algorithms making the decision to buy or sell the financial instrument

• instrument identification code or product characteristics of the financial instrument being transacted

• economic details of the transaction

• execution date and time

• venue of execution

• short sale and waiver indicators where relevant

In practice, that means firms need to control not only the core trade economics, but also the surrounding reference data, client / trader attribution and execution metadata that make the report usable for market surveillance.

Reporting deadlines

EU MiFIR transaction reporting is generally subject to a T+1 reporting timeline. Investment firms must report no later than the following business day after execution.

For firms in scope, that means reporting timeliness depends on prompt capture of transaction data, stable instrument reference data, robust enrichment processes and a process capable of identifying and correcting errors before recurring reporting defects develop.

Is EU MiFIR reporting single-sided, dual-sided or delegated?

EU MiFIR transaction reporting is not a single-sided or dual-sided trade repository regime. It is an investment-firm reporting obligation to the competent authority, often operationalised through an ARM. The correct lens is therefore not “which side reports to a TR”, but whether the firm executing the transaction has discharged its Article 26 obligation correctly.

Operationally, firms may rely on ARMs, trading venues and third-party support, but that does not remove the need for strong internal control over scope, enrichment, data quality and exception management.

Are there EU MiFIR reporting exemptions or reliefs?

Under Article 2(5) of RTS 22, the definition of a “transaction” excludes activities that do not reflect a new investment decision by an investor. These exemptions broadly include financing and clearing activities, such as securities financing transactions and contracts arising solely from clearing or settlement, as well as operational or custodial movements including collateral transfers and custody-driven changes. They also cover post-trade lifecycle events, such as novations, portfolio compression, and derivative adjustments, and transactions that arise automatically from pre-determined contractual terms or corporate actions, for example exercises, redemptions, dividend reinvestment plans, or the creation and redemption of fund units.

In addition, investment firms may rely on the transmission conditions set out in Article 4 of MiFIR Article 26 transaction reporting, under which a firm that transmits an order to another investment firm for execution is deemed to have satisfied its reporting obligation, provided it transmits all required transaction details and the receiving firm agrees to report the transaction.Consequences of non-compliance

EU MiFIR transaction reporting failures create regulatory, operational and reputational risk, particularly where firms cannot evidence control over scope, client identifiers, trader / algorithm attribution, instrument reference data and timeliness. Transaction reports play a critical role in market surveillance, so poor data quality directly undermines supervisory objectives.

For firms in scope, the expectation is clear: transaction reports must be accurate, timely and supported by a defensible control framework.

How En:ACT helps with EU MiFIR reporting oversight

En:ACT helps firms strengthen control over their EU MiFIR reporting obligations by ingesting raw transaction data from any source system, performing books and records reconciliation, and assessing 100% of transactions and fields against the applicable EU MiFIR rules.

Using transparent, regulator-linked logic, the platform identifies:

• product and entity eligibility issues

• field-level errors

• cross-field inconsistencies

• missing or stale instrument data

• LEI and client identifier problems

• trader / algorithm attribution gaps

• timing and venue anomalies

Each identified issue is linked directly to the specific EU MiFIR rule breached, giving firms a clear view of what is wrong, why it matters and where remediation is required.

En:ACT also ensures rules are kept up to date to reflect developments across:

• regulatory text

• regulator guidance

• consultation papers

• relevant industry papers

For EU MiFIR specifically, that means firms benefit from rule coverage maintained in line with Article 26, RTS 22 and ESMA reporting guidance.

Specialist EU MiFIR expertise from the Novatus Intelligence team

Our EU MiFIR capability is supported by specialists within the Novatus Intelligence team, including SMEs with backgrounds across banking, asset management, product and regulation.

For EU MiFIR specifically, that means access to specialists who understand Article 26, RTS 22 and the practical control issues firms face in maintaining transaction reporting quality.

‍

Common EU MiFIR reporting challenges

Some of the most common EU MiFIR reporting issues include:

• incorrect scope assessment

• missing or stale instrument reference data

• incomplete client identifiers

• trader / algorithm mapping failures

• weak timing controls

• poor reconciliation between front-office records and submitted reports

In many cases, the issue is not one bad field. It is a mismatch between the transaction as executed, the enrichment applied to it and the final report delivered to the competent authority.

‍

Why firms choose En:ACT for EU MiFIR oversight

Firms use En:ACT because it gives them more than a validation tool. It provides a control framework around EU MiFIR transaction reporting.

With En:ACT, firms can:

• test reporting quality against transparent rule logic

• reconcile source data to reported data

• identify issues before they become regulatory problems

• benchmark reporting quality over time

• evidence oversight of ARM reporting models

• prepare for change with greater confidence

The result is stronger reporting assurance, better governance and a clearer line of sight from raw transaction data to competent-authority submission quality.

‍