CONSOB · Italy

CONSOB MiFIR transaction reporting in Italy

Fintech Passport

June 22, 2026 · 3-min read

CONSOB MiFIR transaction reporting in Italy

Every Italian-authorised investment firm files MiFIR transaction reports to CONSOB the day after the trade. The obligation flows from Article 26 of MiFIR — Regulation (EU) 600/2014 — and applies to every transaction in financial instruments admitted to trading on an EU venue. The reports feed ESMA’s transaction-reporting database for market-surveillance. CONSOB runs strict data-quality validation. This piece walks through what gets reported, the Italian portal specifics, and where most reporting projects lose time.

1. Legal basis

Regulation (EU) 600/2014 (MiFIR) — Article 26 sets the obligation
Commission Delegated Regulation (EU) 2017/590 — the implementing RTS specifying fields and validation rules
ESMA’s MiFIR Transaction Reporting Guidelines — the operational reference
CONSOB Regolamento Mercati and dedicated reporting instructions — Italian operational rules

2. Who files

Italian-authorised investment firms (SIMs) executing transactions in financial instruments
Credit institutions when providing investment services
Branches of EU investment firms in Italy, for transactions executed through the branch
Branches of third-country firms in scope

3. What is reported

The MiFIR transaction report carries 65 fields per transaction (uniform EU schema). Headline groups:

Reporting party LEI
Buyer / seller identification — LEI for legal entities, national identifier for individuals
Decision-maker and executing-trader identification
Instrument identification — ISIN, CFI, underlying for derivatives
Transaction details — date, time, price, quantity, venue, currency
Buy / sell indicator, capacity
Waivers and special-purpose flags

4. Cadence and channel

Frequency: daily — transactions on day T reported by T+1 close of business
Format: XML against the ESMA RTS schema
Channel: CONSOB’s transaction-reporting portal, with XML upload or transmission through an Approved Reporting Mechanism (ARM)
Acknowledgement: CONSOB returns validation results within a defined window — accepted, rejected, or pending

5. Direct reporting vs through an ARM

Same as in the French AMF MiFIR piece: firms either submit XML directly to CONSOB or via a regulated ARM. Most mid-tier Italian SIMs use an ARM; large institutions submit directly.

6. Where data-quality work concentrates

Italian-specific:

Codice Fiscale handling for Italian-resident individuals — the ESMA RTS accepts Codice Fiscale as the national identifier for Italian retail clients
Country-of-residence determination — affects which national identifier applies
CONSOB’s validation layer adds checks beyond the baseline ESMA validation

7. Interaction with other reporting

MiFIR transaction reporting sits alongside:

EMIR — derivatives reporting to a trade repository
SFTR — securities-financing transactions to a trade repository
Banca d’Italia Segnalazioni — prudential and statistical
COREP-IFR — quarterly prudential

8. FAQ

Does MiFIR transaction reporting apply if I don’t trade myself?

The obligation is on the executing firm. If you transmit orders to another firm for execution, the executing firm reports. Article 26(4) MiFIR sets specific residual notification cases.

How does this differ from the Spanish or French equivalents?

Same EU framework. The Italian flow goes to CONSOB; the Spanish flow to CNMV; the French flow to AMF. The XML schema, fields and validation rules are uniform EU-wide.

What is the LEI?

Legal Entity Identifier — a 20-character ISO 17442 code mandatory for every legal-entity counterparty in a MiFIR report. Without an LEI, the report is rejected.

How is Codice Fiscale used?

For Italian-resident individuals, the Codice Fiscale is the accepted national identifier under the ESMA RTS. The format must match the ESMA-defined country-specific identifier structure.

Does CONSOB run inspections on reporting quality?

Yes. CONSOB’s data-quality team monitors reporting patterns and runs targeted inspections where quality is low.

What changes under MiFIR Refit?

The MiFIR Refit (Regulation (EU) 2024/791) revises the transaction-reporting framework. ESMA is updating the technical standards; the timeline for application is set in the Regulation.

9. What to do, today

If you are scoping a new SIM, build the transaction-reporting layer alongside the dossier; it goes live at grant.
Decide direct vs ARM submission early.
Build the counterparty reference-data layer once and reuse across MiFIR, EMIR, SFTR.
Run ESMA-published validation rules before submission.
Track MiFIR Refit closely.