Compliance · Investor protection & transparency

MiFID II / MiFIR

MiFIR reporting applies to investment firms and banks entering into transactions in financial instruments admitted to trading on trading venues (e.g. exchanges, MTFs, brokers). In addition, MiFID II introduces client-protection requirements.

Key obligations

MiFIR imposes the obligation to report to the supervisory authority (via an ARM or directly) transactions in instruments admitted to trading on trading venues, while MiFID II adds the client-protection layer: best-execution monitoring, suitability and cost registers, and archiving of client communication. The Cesarz_MiFIR product and a dedicated solution area carry this regime.

  • Transaction reporting (Art. 26 MiFIR and RTS 22): complete, accurate reports of reportable transactions to the supervisory authority, at T+1.
  • Suitability & cost registers: investor-protection records kept complete and audit-ready.
  • Communication archiving: phone and SMS records of employee-client communication, retained and retrievable.
Risco Regulatory Radar

Recently in MiFID II / MiFIR

15.10.2026

Transparency manual updated: which OTC derivatives are in scope and how to report their reference data

ESMA has updated its manual on transparency: new guidance on identifying OTC derivatives subject to transparency requirements, on how their identifying reference data should be provided (including for the consolidated tape), and on the tick-size regime, with the published Q&As folded in. What it means for you: a follow-up to the 1 September reference-data change: check your OTC instrument classification and the reference data you publish against the new guidance.

Zespół MiFIR · Risco Software · See MiFIR reporting →

03.09.2026

Commodity derivatives: new weekly position reports live from 3 September

ESMA has confirmed the go-live of the new weekly commodity derivatives position reporting framework on 3 September 2026: updated requirements, technical specifications and validation rules based on XML schema version 2.0. What it means for you: position reports built the old way are no longer compliant — move to schema v2.0 and the new validations before rejections start.

Zespół MiFIR · Risco Software · See MiFIR reporting →

All alerts →

Make the obligation
routine.