For Dutch listed companies already familiar with ESEF reporting, KVK digital filing may appear to be more or less the same.
Both use XBRL-based technology. Both make financial information machine-readable. Both involve tagging, validation and filing-ready digital reports.
But they are not interchangeable.
KVK vs ESEF: What’s the difference?
ESEF applies to issuers whose securities are listed on an EU-regulated market. It requires annual financial reports to be prepared in xHTML, with Inline XBRL tagging applied where required.
KVK reporting is the statutory filing of annual financial statements with the Netherlands Chamber of Commerce. From the 2025 financial year, large legal entities must also file their annual accounts digitally.
| Area | ESEF | KVK |
| Primary authority | AFM in the Netherlands | Netherlands Chamber of Commerce |
| Main purpose | Digital annual reporting for investors and capital markets | Statutory filing in the Business Register |
| Format | xHTML with Inline XBRL where applicable | XBRL or xHTML/iXBRL for large companies |
| Taxonomy | ESEF taxonomy (IAS 1/IFRS 18) | IFRS/Dutch GAAP/Other GAAP |
| Filing destination | AFM and applicable publication channels | KVK Business Register |
| Same file? | No, separate requirements must be assessed | No, requires the appropriate KVK output |
Similar foundation, different requirements
Companies with ESEF experience already understand many parts of digital reporting:
- XBRL tagging
- Taxonomy selection
- Technical validation
- Source-document management
- Review and approval
- Filing-deadline coordination
However, ESEF experience does not automatically make a company ready for KVK filing. The taxonomy, reporting scope, format and filing destination can differ in some cases.
In short, the experience is transferable. The final filing is not.
Can the two workflows be coordinated?
Yes. ESEF and KVK should be treated as separate obligations, but companies do not necessarily need two disconnected reporting processes.
A coordinated approach can help teams:
- Work from controlled source information
- Align both reporting timelines
- Reduce repeated internal reviews
- Manage annual-report changes more efficiently
- Avoid unnecessary handoffs between providers
- Prepare the correct output for each filing destination
This is especially important when late changes must be reflected accurately across multiple reporting deliverables.
Common mistakes to avoid
Companies managing both requirements should avoid:
- Assuming the ESEF report can automatically be filed with KVK
- Using the same taxonomy for both outputs
- Starting KVK preparation only after ESEF is completed
- Assigning the requirements to separate teams without coordination
- Underestimating validation and correction time
The safest approach is to confirm both requirements early and build them into the same annual-reporting calendar.
One partner for ESEF and KVK
DataTracks provides managed reporting support for both ESEF and KVK from tagging and validation to preparation of the appropriate filing-ready deliverables.
With over 20 years of regulatory reporting experience, DataTracks has supported more than 30,000 clients and prepared over 400,000 reports across 26 countries.
ESEF and KVK may share the same digital-reporting foundation, but each requires its own technical approach.
Same same, but different and easier to manage with one experienced reporting partner.
Managing ESEF and KVK reporting?
Speak to DataTracks about coordinating both requirements through one managed reporting workflow.
Write to contact@datatracks.com for more
