EU DAC8 Crypto Asset Reporting
DAC8 is the EU’s implementation of the OECD Crypto-Asset Reporting Framework (CARF), requiring crypto-asset service providers to annually report information on EU tax residents’ crypto activity via XML.
The goal is to give EU tax authorities structured visibility into cross-border crypto activity and strengthen tax compliance across member states.
What’s the scope?
Entities in scope
Any Reporting Crypto Asset Service Provider (RCASP)Â including MiCA authorised CASPs and non-MiCA / non-EU operators where they have EU tax resident users.
Customer nexus
EU tax-resident users (reporting is triggered by the users EU tax residency, not where the platform is headquartered).
Activity covered
Facilitating reportable crypto transactions (e.g. crypto-to-fiat, crypto-to-crypto, transfers and certain in-scope payment transactions under the framework)
Deadline
Collect data from 1 Jan 2026. Submit in 2027 (exact deadline set by each member state)
Reporting frequency
Annual reporting
File format
XML aligned with the DAC8 schema to submit to the tax authority in the EU member state where you’re registered.
Data fields needed
Accounts/wallets: Account ID/ref + wallet address/ID for reportable crypto activity- Individuals: Name, address, DOB, all EU tax residences, TIN per country (or valid reason code
where not available) - Corporates: Entity name, address, tax residence + TIN(s), plus controlling persons (same fields
as for individuals) - Transactions: Crypto-asset type, transaction category (buy/sell/exchange/transfer/payment)
and annual totals.
Reporting considerations to keep in mind
PIs/EMIs in scope*
*If they are the customer-facing entity providing the crypto service, either under their own crypto licence or via a group crypto entity they contract with.
Non-EU firms
Will need to register in an EU member state for DAC8 reporting.
Steps to submission
A step-by-step overview of how to prepare for DAC8, from onboarding and data capture to tagging, aggregation, and XML submission.
Fix onboarding
Capture EU tax residence, TINs (and any missing reason codes) from day one.
Tag EU customers
Add an ”EU” tag for DAC8 ensuring it’s based on tax residency (not nationality).
Tag transactions
Add transaction type tags (mentioned above) to every crypto event so totals can be extracted reliably.