The Dutch reporting calendar for a payment firm
The Netherlands is the most consolidated reporting environment in this cluster — one central submission channel for most statistical and prudential returns — and it has one obligation that is a connection rather than a filing. Getting the Dutch calendar right is therefore less about tracking many channels and more about understanding the twin-peaks split and the handful of obligations that sit outside the central channel.
1. Twin peaks, in reporting terms
| Counterparty | What it collects |
|---|---|
| DNB | Prudential and statistical returns, and the integrity-risk framework |
| AFM | Conduct, and transaction reporting where investment services are provided |
| FIU-Nederland | Unusual transaction reports |
| Belastingdienst | Cross-border payment data |
| Kamer van Koophandel | Beneficial-ownership register |
2. The inventory
- BSI and MIR statistical reporting to DNB — the monthly balance-sheet and interest-rate returns.
- The DNB reporting channel — the centralised XBRL submission route covering the prudential and statistical families.
- Unusual transaction reports to FIU-Nederland through goAML, event-driven.
- SIRA — the systematic integrity risk analysis, a maintained document rather than a periodic file.
- The Banking Information Reference Portal — a mandatory connection before issuing Dutch IBANs, with an availability requirement attached.
- CESOP via Digipoort — quarterly, with its own certificate problem for foreign PSPs.
- MiFIR transaction reporting to the AFM where investment services are provided.
- Fraud reporting and the payment statistics that carry it.
3. The obligation that is a connection
The most distinctive item on the Dutch list is not a return at all. The reference portal is a mandatory connection that must be in place before Dutch IBANs are issued, and it carries an availability requirement rather than a deadline — the connection has to work, continuously, not merely exist.
That reframes the control. A filing obligation is monitored by checking that something went out; an availability obligation is monitored by checking that something is up. Those are different tests, owned by different teams, and a reporting register that lists only the first will not surface a degraded connection.
4. One channel is an advantage, with a catch
Consolidating the prudential and statistical families into a single XBRL channel removes a lot of the per-return plumbing that other markets impose. The catch is concentration: onboarding to that channel, and the XBRL discipline it requires, is a single point of dependency for most of the calendar.
Facts: an EMI authorised elsewhere in the EU sets up a Dutch entity and plans to issue Dutch IBANs, with reporting scheduled to be built after launch.
What the analysis produces: the reference-portal connection is a precondition to issuing IBANs at all, so it sits before launch rather than after. Channel onboarding and the test environment sit on the critical path for the statistical and prudential returns. And the unusual-transaction standard needs to be built into monitoring from day one, because retro-fitting a lower threshold means re-reviewing the period since launch.
What the practitioner does: treats the portal connection and the channel enrolment as launch dependencies rather than reporting tasks, and calibrates AML detection to the Dutch standard from the outset rather than porting a suspicion-based model from another market.
FAQ
What is different about Dutch AML reporting?
The standard is “unusual” rather than “suspicious”, and it is supported by objective indicators as well as subjective ones — a lower and differently framed trigger than most member states.
What must be in place before issuing Dutch IBANs?
The connection to the Banking Information Reference Portal, which is mandatory before issuance and carries an availability requirement.
Is there one submission channel?
Most prudential and statistical reporting runs through a single centralised XBRL channel, which simplifies the plumbing but concentrates the dependency on one onboarding.
Which Dutch obligation has no filing at all?
The reference-portal connection. It is a state to be maintained with an availability requirement, not a return to be sent — so it needs an uptime control rather than a due-date monitor.
5. The obligations that are documents
Two Dutch items are neither filings nor connections but maintained documents, and they are assessed on inspection rather than on submission. The systematic integrity risk analysis is the clearest: it is a living assessment of the integrity risks the firm faces, and its quality is tested by the supervisor reading it, not by a validation rule.
That changes what “up to date” means. A return is current if the latest period was filed; a document is current only if it reflects the business as it is now. The control is therefore a trigger-based refresh — a new product, a new market, a new distribution channel or a material incident should each re-open the assessment — layered on top of a periodic review. Firms that refresh only on the annual cycle end up defending a document that describes last year’s business.
Related: The DNB reporting channel · The German reporting calendar · The Dutch AML framework
