MiFIR transaction reporting requirements
MiFIR requires investment firms to report the details of executed transactions to their competent authority, no later than the following working day. It is single-sided, field-level and unforgiving — a missing identifier is a rejected report.
REGREP is an independent software provider. This page explains the framework in plain language and is not legal or regulatory advice — confirm your reporting obligations with your competent authority.
- Instrument
- Regulation (EU) No 600/2014
- Scope
- Investment firms executing transactions in reportable instruments
- Reporting artefact
- Transaction reports
- Format
- ISO 20022 XML, generally via an approved reporting mechanism
- Supervisor
- National competent authority
- Penalties
- Administrative measures and sanctions set by each member state
What MiFIR asks of you
The short version: what the framework requires, who it applies to and when it bites.
What it requires
Firms report the prescribed details of each executed transaction — instrument, price, quantity, venue, timestamps, and the parties and decision-makers behind it — to their competent authority.
Who it applies to
Investment firms executing transactions in financial instruments admitted to trading or traded on a trading venue, including certain instruments whose underlying is traded on a venue.
When it applies
No later than the close of the following working day, with corrections and cancellations filed as errors come to light.
What has to be done
Penalty powers derive from Regulation (EU) No 600/2014 as applied through national law.
| Obligation | What it means in practice |
|---|---|
| Determine reportable transactions | Establish which transactions and instruments fall in scope, including instruments reportable by reference to their underlying. |
| Report by the following working day | Submit complete transaction reports within the deadline, generally through an approved reporting mechanism. |
| Identify every party | Report valid legal entity identifiers for firms and clients, and the prescribed identifiers for the natural persons making investment and execution decisions. |
| Report complete field content | Every prescribed field must be populated correctly — incomplete or malformed reports are rejected and count as unreported until fixed. |
| Correct and cancel | Respond to competent authority feedback by correcting or cancelling reports through the prescribed mechanism, and notify significant misreporting. |
From your data to a validated filing
Activate only the module the obligation needs. Every price covers one regulated entity unless stated otherwise, and excludes VAT.
MiFIR transaction reporting
Delivered as a scoped project on the REGREP ISO 20022 engine. Field-level mapping, identifier sourcing and rejection handling are specific to your execution flow.
Talk to usScoped to your transaction flow Talk to usISO 20022 messaging
The same engine generates and validates ISO 20022 messages, including SEPA payment messaging, as a scoped engagement.
Talk to usScoped to your message set Talk to usRelated to MiFIR
EMIR
The derivative reporting counterpart: contracts reported to a trade repository by both counterparties.
Read the requirements →Structured data guide
Plain-language explainers on ISO 20022, structured messaging and high-volume reporting.
Read the guide →ISO 20022 module
See the messaging engine behind our MiFIR project work, including SEPA content.
See the module →Questions, answered
How is MiFIR reporting different from EMIR?
What makes transaction reports fail?
Do I report directly or through an ARM?
Why is MiFIR not a self-serve module?
Scope your transaction reporting flow.
Tell us where your execution data comes from and where rejections are coming from today.