AFM · Netherlands

AFM MiFIR transaction reporting in the Netherlands

Fintech Passport

June 22, 2026 · 3-min read

AFM MiFIR transaction reporting in the Netherlands

Every Dutch-authorised investment firm files MiFIR transaction reports to AFM 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. AFM runs strict validation. This piece walks through what gets reported, the Dutch portal specifics, and where most projects lose time.

1. Legal basis

Regulation (EU) 600/2014 (MiFIR) — Article 26
Commission Delegated Regulation (EU) 2017/590 — implementing RTS
ESMA MiFIR Transaction Reporting Guidelines
AFM policy notices and submission instructions

2. Who files

Dutch-authorised investment firms (beleggingsondernemingen) executing transactions in financial instruments
Credit institutions providing investment services
Branches of EU investment firms in the Netherlands, 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; decision-maker and trader identification; instrument identification (ISIN, CFI, underlying); 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: AFM’s transaction-reporting portal, with XML upload or transmission through an Approved Reporting Mechanism (ARM)
Acknowledgement: AFM returns validation results within a defined window

5. Direct vs through an ARM

Same as in France, Italy and the Spanish equivalent — firms either submit XML directly or via an ARM. Most mid-tier Dutch investment firms use an ARM; large institutions submit directly.

6. Where data-quality work concentrates

Counterparty identifier completeness — LEI for legal entities, national identifier for individuals (BSN handling for Dutch retail clients with privacy considerations)
Decision-maker and trader identification for algo-driven flows
Instrument classification for OTC derivatives where the ISIN may not exist
Country-of-residence determination driving which national identifier applies

7. BSN and the Dutch privacy overlay

8. Interaction with other reporting

MiFIR transaction reporting sits alongside:

EMIR — derivatives reporting to a trade repository
SFTR — securities-financing transactions
DLR-routed prudential and statistical reporting
COREP-IFR — quarterly prudential

9. FAQ

How does this differ from peer EU jurisdictions?

Same EU framework, different supervisor channel — AFM in the Netherlands, CNMV in Spain, AMF in France, CONSOB in Italy. The XML schema and validation rules are uniform.

Can I use BSN as the national identifier?

BSN handling is privacy-sensitive in the Netherlands. AFM’s operational guidance specifies the acceptable identifier types per client category. Generally retail identifiers use the ESMA-defined CONCAT or alternative codes rather than direct BSN exposure.

What is the LEI?

Legal Entity Identifier — a 20-character ISO 17442 code mandatory for legal-entity counterparties.

Does AFM run inspections on reporting quality?

Yes. AFM’s data-quality team monitors reporting patterns and runs targeted inspections.

What changes under MiFIR Refit?

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

Are crypto-asset transactions in scope?

For instruments classified as MiFID II financial instruments (security tokens, tokenised securities) — yes. For pure crypto-assets within MiCA scope but outside MiFID II — different reporting regime under MiCA Articles 88+ and the Travel Rule.

10. What to do, today

If scoping a new beleggingsonderneming, build the transaction-reporting layer alongside the dossier.
Decide direct vs ARM submission.
Build the counterparty reference-data layer once and reuse across MiFIR, EMIR, SFTR.
Calibrate BSN handling against AFM’s operational guidance.
Track MiFIR Refit closely.