MiFID II Retail Transaction Reporting: New Rules and Steps
The MiFIR review changes what EU firms must report about retail-client trades, from client categorisation to effective dates. Here is what is live, what is paused, and what it costs.
Key takeaways
- Retail-client trades have been reportable since 2018, and the filing duty belongs to the firm, not the client
- MiFIR's amended Article 26 does not apply on its own — ESMA says the current RTS 22 continues to govern until revised standards apply
- ESMA declined to propose a revised RTS 22 in June 2025 and moved to a broader review, so the Level 2 field set is unsettled
- Firms still file in T+1 through an ARM, and ESMA supervises data reporting services providers directly
MiFID II retail transaction reporting: what actually changed
Retail investors rarely notice transaction reporting until a broker asks for an extra identifier at onboarding. Behind that request sits one of the largest data pipelines in EU financial regulation: every executed transaction in a reportable instrument must be sent to a national competent authority (NCA), usually through an approved reporting mechanism (ARM).
The obligation sits with the investment firm, not the client, and has done since MiFID II applied in January 2018 through Article 26 of Regulation (EU) No 600/2014 (MiFIR). That distinction matters, because most of the current confusion comes from assuming that "new retail reporting rules" mean new duties for retail clients. They do not. What is changing is what the firm must report about the trade, and who polices the pipeline.
Two tracks: one in force, one paused
The MiFIR review, Regulation (EU) 2024/791, entered into force on 28 March 2024 and rewrites Article 26 directly. The parallel amendments to the MiFID II directive required national transposition by Member States.
The important catch: the revised Article 26 does not bite on its own. ESMA has stated in its Final Report on RTS 22 and RTS 24 of 23 June 2025 that, until revised technical standards apply, the Level 1 rules in force before the review — together with the existing RTS 22 and RTS 24 — continue to govern.
Then the timetable paused on purpose. ESMA was expected to deliver draft technical standards for Article 26. Instead, in that June 2025 Final Report, ESMA decided not to propose amendments at that stage, citing consultation feedback about the limitations of the existing regime, and launched a broader Call for Evidence on simplifying financial transaction reporting. For retail-facing brokers the practical result is a design-and-test holding pattern: the Level 1 text is law, the Level 2 field specification is not settled.
The data points in a report
The core blocks
A transaction report is not a single record about a trade but a bundle of blocks defined in Annex I, Table 2 of Commission Delegated Regulation (EU) 2017/590 — the technical standard known as RTS 22. It sets out 65 reportable fields, grouped by what each identifies:
- Instrument details — identifier (typically ISIN), asset class, price and quantity.
- Execution details — date and time, venue, and transaction identifiers.
- Buyer and seller details — client identification and, where relevant, the person who took the investment decision.
- Entity details — the legal entity identifiers (LEIs) of the executing, submitting and responsible entities.
- Indicators — flags describing how the trade was executed.
For natural persons, identification cannot rely on an LEI. Firms report the national client identifier method specified in Article 6 and Annex II of RTS 22, which is why brokers increasingly collect national identifiers or other personal reference data at onboarding. In the UK, the FCA has separately consulted on requiring national identifiers for natural persons — a jurisdiction-specific rule, not an EU one, and one worth tracking as a precedent on identifier quality.
What the review would add and remove
ESMA's October 2024 consultation paper on RTS 22 set out the field-level changes the amended Article 26 implies. The most retail-relevant:
- Effective date. A new field describing when the obligation under the transaction becomes effective. For debt instruments this aligns with settlement date; for derivatives it can sit in the future.
- Entity subject to the reporting obligation. A field identifying which entity is ultimately responsible when the executing, submitting and responsible entities differ.
- Chain and aggregated-order identifiers. New codes — a trading venue transaction identification code (TVTIC), a chain identifier, and an INTC code — to reconstruct who reported what in a chain and to identify aggregated orders allocated across clients.
- Client category. A proposed field capturing the client's MiFID II categorisation: retail client, professional client or eligible counterparty.
- Digital token identifiers. Fields to report ISO 24165 Digital Token Identifiers for distributed-ledger-technology instruments and their underlyings.
- Removals. The short-selling indicator (field 63) and the detailed waiver designation are proposed for removal, on the logic that the information is already captured elsewhere — a change recorded in ESMA's public hearing presentation on the RTS 22 and 24 review and its consultation paper.
None of these are binding yet: they are the shape of a possible future RTS, and ESMA has said the comprehensive review may change them.
| Dimension | Position today | Direction of travel |
|---|---|---|
| Reportable fields | 65 fields in Annex I, Table 2 of RTS 22 | New identifiers and client categorisation added; short-selling and waiver indicators proposed for removal |
| Scope of derivatives | OTC derivatives reportable only when executed on a trading venue | Certain centrally cleared OTC derivatives added regardless of venue (ESMA Final Report) |
| Reporting route | Investment firm reports via an ARM or a trading venue (Article 26(7) MiFIR) | Unchanged |
| UK regime (separate) | 65 fields; five-year default back-reporting (FCA PS26/15) | 52 fields; three-year back-reporting from 3 April 2028 |
The scope extension matters for derivatives desks rather than retail equity trading. Under the amended Article 26(2), OTC derivative transactions must be reported only when executed on a trading venue, except those specified in Article 8a(2) — which ESMA describes as certain centrally cleared OTC derivatives in euros, Japanese yen, US dollars or pounds sterling, with defined interest-rate-swap tenors, single-name credit default swaps referencing a globally systemically important bank, and CDS referencing an index of such banks (ESMA Final Report).
Reporting timelines and record keeping
Transaction reports must be submitted as soon as possible and no later than the end of the working day following execution — the familiar T+1 rhythm, set out in Article 26(1) MiFIR.
A separate obligation sits alongside it. Article 25 MiFIR, specified by RTS 24, requires firms to maintain order records — the trail from order receipt through to execution — for a retention period set in the Level 1 text. Order data is not transaction reporting: it is the audit trail regulators use to reconstruct how an order became a trade, and it covers retail orders that never execute.
Compliance tooling: ARMs, reconciliations and oversight
Most firms do not file directly. They route reports through an ARM, or through a trade repository acting as an ARM where the national authority permits (Article 26(7) MiFIR).
Two developments have changed the tooling market:
- ESMA supervises data reporting services providers directly. Authorisation and supervision of most approved publication arrangements and ARMs moved from national authorities to ESMA in January 2022, under the 2019 review of the European Supervisory Authorities, and the MiFIR review builds on that framework. ESMA's data reporting services providers page sets out the supervisory framework and reporting templates.
- New operational duties sit on ARMs. Delegated rules adopted in 2025 supplement MiFIR with requirements for data reporting services providers, requiring them to monitor systems continuously so a submitted report is confirmed as received, to run reconciliations against authority data on request, to notify a client when they detect an error or omission caused by that client, and to correct errors attributable to the ARM without delay.
For compliance teams, the practical toolkit is therefore: pre-submission validation; a population-versus-submission reconciliation; periodic extracts from the ARM to test against source systems; an LEI and national-identifier inventory; and a logged process for errors and omissions, with mapping between the old and new schemas.
Risks and costs
- Direct costs. ARM fees are typically priced per report or per volume band, so cost scales with trading activity. On top sit system changes, testing cycles and reconciliation tooling.
- Responsibility cannot be outsourced. Article 26 makes an ARM or trading venue responsible for failures attributable to it, but the investment firm must still take reasonable steps to verify completeness, accuracy and timeliness. Delegation is not absolution.
- Timing risk. Firms that build now to the 2024 proposals are building to a draft. Firms that wait risk a compressed implementation window when a revised RTS finally lands.
- Divergence risk. The UK is going its own way: the FCA's PS26/15, published in August 2026, cuts the field count from 65 to 52, shortens the default back-reporting period from five years to three, and sets a switch-over date of 3 April 2028, with a further consultation (CP26/34) covering the transition. Firms running both regimes can expect parallel schemas and duplicated testing.
- Data protection. Reports contain the personal data of retail clients. Retention, minimisation and access controls sit under GDPR obligations that are additional to the reporting rules.
- For retail clients. There is no direct fee and no filing duty. The indirect cost is onboarding friction — more identifier collection — and any pass-through of compliance spend in pricing.
Bottom line
MiFID II retail transaction reporting is not a new obligation on retail traders; it is a maturing obligation on the firms serving them, and the MiFIR review is rewiring the data set and the supervision around it. The Level 1 amendments are in force, the Level 2 field specification is under a comprehensive review, and the ARM layer faces direct ESMA supervision.
For brokers and compliance officers, the productive work now is unglamorous: clean identifiers, working reconciliations, documented error handling, and a change-management plan flexible enough to absorb a revised RTS 22 whenever it arrives.
Follow the shortlist
Focused on execution, costs and risk management? Our global ETF and stock research watchlist is tracked daily. Premium members get the full list, the reasoning behind every entry and updates when entries change.
See premium accessInformation and education only, not investment advice.
Related
0DTE Options Explained: Same-Day Expiry Volume and Risk
What zero-days-to-expiry contracts are, why they now dominate S&P 500 index options activity, and the gamma, execution and settlement risks retail traders take on.
TradingOptions Assignment and Exercise Risk for Retail Traders
How US-listed equity options are exercised and assigned at expiry — pin risk, dividend-related early assignment, broker margin policy, and where EU retail access differs.
TradingRetail Margin Trading: Leverage, Costs and Regulatory Safeguards
How retail margin trading works: Regulation T and FINRA requirements, the real price of borrowed money, liquidation triggers, and the safeguards US and EU rules provide.