The Dutch DAC8 regime applies to the 2026 data year. Crypto providers within scope must collect customer and transaction data from 1 January 2026. Their first annual report is due by 31 January 2027. The filing relies on records from onboarding, wallets, transactions and finance.
Why this matters
DAC8 turns daily customer and transaction records into an annual tax report. Customer identity, address, tax residence and tax number must match the right transactions. Those details often sit in separate systems. A reversal may remain completed in finance, or a residence change may stay in the onboarding file. MiCA authorisation matters, but does not settle DAC8 scope alone. Staff time for customer follow-up, software changes and corrections can reduce a small provider’s margin.
Example
A customer passes identity checks in January and changes tax residence in June. After a platform migration, the customer has a new account number. The product system records execution time, while finance uses settlement time. The reporting file can then link transactions to the wrong customer or country. A BV paid €4,000 in crypto needs a file linking the invoice, wallet transaction, euro value, VAT entry and later sale or year-end valuation. A wallet screenshot does not explain the full business event.
XTROVERSO tips
- Map records from 1 January 2026. List customer and transaction data in onboarding, compliance, product, wallet and finance systems. Include records held by outside suppliers.
- Give each part a named owner. Assign owners for scope, customer data, transaction rules, technical delivery, customer notices and final sign-off. Record who resolves exceptions.
- Match customer records across systems. Compare customer IDs, addresses, tax residence and tax numbers. Check for duplicate accounts, changed details and missing fields.
- Reconcile the transaction population. Match wallet and platform activity to the reporting dataset and finance ledger. Keep reversals, failed transactions and migrations visible.
- Test the current technical version. Check which reporting specification the software uses. Keep release dates, test results and corrections in one controlled file.
- Keep crypto payments tied to the books. For a BV receiving crypto, reconcile the invoice, euro conversion, VAT, wallet evidence and ledger entry each month.
Need a review of your DAC8 records, ownership and reporting process? XTROVERSO can help identify gaps before filing begins
The data, sourcing, and analysis behind this article were conducted by Linda 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 Linda Pavan before publication.
References
- Taxence - Documents on the Dutch Tax Administration’s preparation for digital data exchange
- Wettenbank - National legal implementation and effective date
- Belastingdienst - Reporting scope, collected data and first filing deadline
- Belastingdienst ODB - DAC8 and CARF implementation schedule
- Belastingdienst ODB - CARF and DAC8 technical documentation
- AFM - Register of authorised and notified crypto providers
- Belastingdienst - Dutch tax treatment of crypto
- Belastingdienst ODB - CARF and DAC8 release notes
