Covered Dutch crypto providers have collected customer and transaction data since January 1, 2026. Their first DAC8 report, for 2026, is due January 31, 2027. Groups whose first calendar-year period covered 2024 face a June 30 information deadline and an August 31 Dutch top-up tax filing and payment deadline in 2026.
Why this matters
DAC8 links customer identity, tax residence, tax numbers, and specified crypto transactions. Providers must tell customers what they report. Missing onboarding fields or wrong transaction categories can reach the ledger and final return. The minimum tax targets groups with €750 million in consolidated revenue. Smaller Dutch entities may still need to send payroll, invoice, and entity data to a parent company. DAC9 allows one EU filing, so the reporting entity needs reviewed source records.
Example
A Dutch crypto provider receives complete transaction files from its software supplier. Its ledger uses different transaction categories, and several customer files lack tax identification numbers. Finance corrects the ledger mapping. Customer service requests the missing details. Compliance decides which customers and transactions are reportable. One named employee then checks that the platform, ledger, and final report match. That chain gives each task an owner before the submission is approved.
XTROVERSO tips
- Confirm which entity is responsible. Record whether your business is directly covered by DAC8 or the minimum tax. Also note whether it only supplies data to another group entity.
- Map every required field. List each customer, transaction, payroll, tax, and entity field. Record its source system, file owner, and review date.
- Test records against the ledger. Compare platform transactions with the ledger and management accounts. Resolve category differences before they enter later reports.
- Name one process owner. Assign one person to oversee the route from source record to submission. Advisers and software suppliers can assist, but the business must approve the final report.
- Prepare filing and payment access. Check registration, portal access, authorised signatories, cash, and payment approval before the deadline. Keep these tasks in one planning file.
- Keep evidence of each review. Save reconciliations, corrections, decisions, customer notices, and approvals. The file should show how each reported figure was produced.
Need a clear map of your reporting duties, records, owners, and deadlines?
The data, sourcing, and analysis behind this article were conducted by Paolo Maria Pavan. AI was not used to identify sources, build the factual basis, or produce the analytical judgment contained here. AI was used only as a drafting aid. The final English text was personally reviewed, edited, and approved by Paolo Maria Pavan before publication.
References
- Wijziging Besluit Bestuurlijke Boeten Belastingdienst: nieuwe boeteregels voor DAC8, DAC9 en minimumbelasting - Taxence
- Belastingdienst - DAC8 reporting starts with 2026 customer and transaction records
- Belastingdienst - DAC8 registration and reporting access
- Rijksoverheid - DAC8 makes crypto activity more visible to tax administration
- Belastingdienst - Scope and first filing cycle of the Dutch minimum tax
- Belastingdienst - Pillar Two applies only to very large multinational and domestic groups
- Rijksoverheid - DAC9 reduces duplicate group reporting but increases reliance on one reliable data submission
- Rijksoverheid - Administrative and systems pressure behind DAC9
