DAC8 Has Reached the Books, and January Leaves Little Room

The first Dutch DAC8 filing begins with customer and transaction records being built throughout 2026.

A crypto founder opens three screens during a Monday meeting. One shows verified customers, another wallet movements, and the third the finance ledger. All three look orderly. Yet customer identifiers differ, transaction times do not align, and tax residence sits in a separate onboarding system.

That is where the Dutch DAC8 obligation becomes real.

The Dutch implementing act was published on 10 April 2026 and applies from 1 January 2026. The Belastingdienst requires providers within scope to collect customer and transaction information for the 2026 calendar year. Their first annual report is due by 31 January 2027.

The reporting year is already running. At the same time, the technical environment has received specifications, testing support and release updates through July and August.

The deadline is only the final movement

DAC8 requires more than exporting transactions from a platform. Reportable information can include a customer’s identity, address, tax residence and tax identification number. It can also include specified exchanges, transfers and payment transactions.

A provider must connect those facts to the right customer and reporting country. By the following 31 January, it must tell customers what information it has reported.

This is a governance problem before it becomes a submission problem. The annual message to the Belastingdienst is the final movement. The real work lies in hundreds of earlier decisions about customers, wallets, jurisdictions and transaction types.

Consider the founder’s three screens. A customer may pass identity checks in January, change residence in June and use several accounts after a platform migration. One system retains the original address. Another uses a new account number. Finance groups transactions by settlement date, while the product system records execution time.

Each difference may look minor. Together, they can produce an incomplete or inconsistent report.

Small providers should watch the cost as well. Reporting quality requires customer follow-up, software work, testing and time spent resolving unusual transactions. Manual repairs may feel manageable with a few hundred customers. As volumes, products and jurisdictions grow, they become a margin question.

MiCA status is not the whole answer

The AFM register identifies crypto providers authorised or notified in the Netherlands and elsewhere in the European Union. That status matters. A firm’s DAC8 position also turns on its activities, establishment and reporting links.

This deserves founder attention. MiCA, customer due diligence, sanctions controls and tax reporting can draw on overlapping information, but each uses it for a different purpose. When separate teams or suppliers collect the same customer facts, duplication can conceal disagreement.

A tax residence entered during onboarding may never reach finance. A wallet classification made by compliance may not appear in the reporting engine. A reversal accepted by operations may remain recorded as a completed transaction elsewhere.

The useful management question is not simply, “Who handles DAC8?” It is, “Who can explain the route from customer acceptance to the submitted figure?” Shared ownership can sound collaborative while leaving difficult exceptions without an owner.

Timing adds another layer. The law applies from 1 January, although publication followed in April. A provider that waited for the final Dutch act may now need to revisit records and decisions made earlier in the year. Reconstruction takes longer and produces weaker records than resolving gaps while staff still remember the event.

Ordinary businesses have a different exposure

Most Dutch small businesses are not crypto service providers. Owning crypto or accepting it from a customer does not place them in charge of the provider’s annual report. DAC8 changes reporting and information exchange, while the Dutch tax treatment of crypto remains governed by the existing tax rules.

Suppose a design BV issues a €4,000 invoice and accepts payment in crypto. The company must translate the receipt into euros for turnover and VAT. Later movements in value affect profit or loss. Crypto still held at the balance-sheet date follows the tax treatment described by the Belastingdienst.

The finance record should connect the invoice, wallet transaction, euro conversion, VAT entry and later disposal or valuation. A wallet-balance screenshot rarely explains the full business event. An exchange download is equally thin when nobody can link its account identifiers to customers, invoices and ledger entries.

Wider reporting will change the practical environment. Tax authorities can use received information for risk analysis. Aggregated DAC8 data will not automatically complete a tax return, but differences between external transaction information and a company’s own records will become easier to identify.

Back at the Monday meeting, the founder does not need another broad policy presentation. The useful conversation is narrower. Which customer records lack tax numbers? Which residence changes remain unresolved? Can finance reconcile the transaction population with the reporting dataset? Which technical specification does the software use? Who signs off the exceptions?

January starts in August

The first filing deadline may look distant. In a small company, five months disappear quickly between product work, customer issues, year-end accounts and staff leave. Testing in January leaves little room to correct data collected over the previous twelve months.

Strong preparation is quiet and repetitive. Teams compare customer identifiers across systems. They follow up missing tax-residence information. They assign clear ownership to wallet and transaction classifications. Reversals and migrations remain visible. Technical changes are dated, tested and understood before entering production.

For a BV that uses crypto only as an asset or payment method, the same principle applies on a smaller scale. Monthly reconciliation costs less than rebuilding a year of wallet movements during the tax return.

DAC8 brings more crypto information into formal tax exchange. Its deeper effect is simpler. It reduces the distance between the wallet, the customer record and the books. Businesses that close that distance now will reach January with fewer explanations to assemble and more facts already in place.

The data, sourcing, and analysis behind this article were conducted by Linda Pavan Geraedts. 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 Geraedts before publication.

References

• Documenten openbaar over voorbereiding Belastingdienst op nieuwe regels voor digitale gegevensuitwisseling - Taxence
• Wettenbank - National legal implementation and effective date
• Belastingdienst - Who reports, what data is collected and first filing deadline
• Belastingdienst, Ondersteuning Digitaal Berichtenverkeer - Technical delivery remains an active implementation project
• Belastingdienst, Ondersteuning Digitaal Berichtenverkeer - Recent technical releases and reporting documentation
• Autoriteit Financiële Markten - MiCA authorisation, supervision and overlap with financial-crime controls
• Belastingdienst - Tax position of crypto users and businesses that hold or receive crypto
• Belastingdienst, Ondersteuning Digitaal Berichtenverkeer - CARF/DAC8 release notes