Picture a small Dutch crypto business in December. The finance lead is preparing the first DAC8 return, while the founder asks why several customer records lack a tax identification number. A software supplier has transaction data, but its categories do not match the ledger. Everyone has worked hard. The report is still not ready.
The Belastingdienst’s DAC8 guidance explains why this matters now. Relevant crypto service providers and operators have had to collect customer and transaction data since 1 January 2026. Their first return, covering 2026, is due by 31 January 2027. The reporting date may be next year, but the underlying work has already been running for months.
DAC8 is not a new tax on crypto. It is a reporting and information-exchange system. Yet reporting changes business behaviour because it connects customer identity, tax residence, transaction history and financial administration. I read this as a clear shift: tax compliance is moving closer to the moment when a customer enters the system or a transaction occurs.
The deadline is the end of the process
The reportable information includes identification details, tax residence, tax identification numbers and specified crypto transactions. Providers must also inform customers about the data reported to the Belastingdienst. That turns onboarding, transaction mapping and customer communication into parts of the same tax process.
A missing field is easy to overlook when a new customer wants access quickly. Six months later, collecting that information can become awkward. The customer may have moved, changed residence or stopped responding. A classification error can be worse because it may already have spread through the platform records, ledger and management accounts.
This is why the usual final-week response is poorly suited to DAC8. Extra hours cannot always repair records that were never collected. A sensible review begins further upstream: which entity has the reporting duty, which customers are reportable, where each required field sits, and who resolves differences between the platform and the accounts.
One report can travel far
Information about Dutch residents can reach the Belastingdienst through providers elsewhere in the European Union. The distance between a customer record, an exchange transaction and a Dutch tax position is narrowing. That does not make every difference suspicious. It does make unexplained differences more visible.
Dutch law also links intentional or grossly negligent failures under the relevant DAC8 duties to the sixth statutory fine category, which is €1.1 million in 2026. The number is serious, but it is not the most useful opening question for management. The better question is whether the business can explain how its submitted data was produced and checked.
That distinction matters. A company may have capable staff, reputable software and an external adviser, yet still lack one person who owns the full route from source record to submission. Responsibility can disappear between legal interpretation, technology, finance and customer service. Each party completes its task, but nobody confirms that the pieces agree.
Large-group rules can reach small desks
The minimum-tax rules sit at the other end of the company spectrum. The Wet minimumbelasting 2024 concerns multinational and domestic groups with annual consolidated turnover of at least €750 million. Its minimum rate is 15%. Most micro and small businesses are therefore outside its direct scope.
For qualifying groups with a first calendar-year reporting period covering 2024, the Dutch minimum-tax return and payment are due by 31 August 2026 where Dutch top-up tax is payable. That deadline brings tax calculations, cash, filing access and payment approval into one short period. A technically correct calculation is not enough if nobody has authority to file or release the payment.
DAC9 is intended to let relevant group information submitted in one EU member state move through international exchange, reducing duplicate submissions. That sounds like less administration, and in one sense it is. Yet one shared submission also places more weight on the dataset selected, reviewed and approved by the reporting entity. An error can travel as efficiently as a correct figure.
The practical question is ownership
A small Dutch subsidiary may never calculate Pillar Two tax. It can still receive a detailed request from its parent company for entity data, payroll figures, tax adjustments or supporting reconciliations. The request may arrive with a short deadline because the group assumes the information already exists in a usable form.
This is where smaller companies often feel the real burden of rules aimed at much larger organisations. The legal duty sits at group level, while the search for invoices, account mappings and local explanations lands on a modest finance desk. Time spent rebuilding old information competes directly with payroll, customer invoices and cash collection.
Return to that crypto founder in December. The useful response is not panic, nor another spreadsheet with unclear ownership. It is a short chain of named responsibility: who assesses scope, who maintains customer data, who reconciles transactions, who approves corrections and who signs off the final submission. External support can strengthen that chain, but it cannot replace internal accountability.
The lesson from DAC8, DAC9 and the minimum tax is not that every small business faces the same obligation. It is that modern tax reporting increasingly depends on records created outside the tax department and long before the deadline. Good compliance starts where the fact first enters the business. By filing day, the company should be reporting its history, not trying to reconstruct it.
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.
