DAC 8 Directive (2026): How the EU Introduces Full Tax Transparency for Crypto-Assets — and What It Means for Businesses and Investors

This article is provided for informational purposes only and does not constitute legal or tax advice. For decisions in specific situations, we recommend consulting qualified professionals. The information is current as of the publication date (January 2026).

As of 1 January 2026, the European Union has launched the most extensive tax-control system for crypto-assets in history. DAC 8 (Council Directive (EU) 2023/2226) requires all crypto-exchanges, custodians, and brokers to automatically transmit detailed data on clients’ transactions to tax authorities — regardless of where the provider is incorporated.

This is not limited to EU residents. Ukrainian entrepreneurs with assets in the EU, owners of accounts on European exchanges, and investors with crypto portfolios all fall within the scope of the new requirements. Ukraine is already actively exchanging tax information with the EU under CRS, and Draft Law No. 10225-d is laying the groundwork for implementing similar rules domestically.

We are at a bifurcation point: the first week of January 2026 became the Rubicon after which the old strategies of hiding assets or passively ignoring reporting requirements turn from “grey-zone tactics” into a direct path to administrative and criminal exposure — including the risk of asset confiscation.

The Liglex Consulting team has prepared an in-depth analysis of this new reality: who is affected, what data will be collected, how the account-blocking mechanism works, and what you should do now to avoid unpleasant surprises.

---

What Is DAC 8 and How Does It Fit into the EU Administrative Cooperation System?

DAC 8 is the eighth amendment to the EU’s baseline Directive on Administrative Cooperation in taxation (Directive on Administrative Cooperation). For the first time, it introduces systematic reporting on crypto-asset transactions. To fully understand DAC 8’s scale and significance, it should be viewed not as an isolated act, but as the peak of a fifteen-year evolution of European tax law.

The DAC system is a living, increasingly complex organism that has adapted to each new challenge of globalization and the digital economy:

• DAC 1 (2011) — the foundation. It established automatic exchange for five income categories: employment income, directors’ fees, pensions, life insurance products, and income from immovable property.
• DAC 2 (2014) — the end of bank secrecy. Europe’s response to the U.S. FATCA. Implementing the Common Reporting Standard (CRS) obligated banks, custodians, and insurers to disclose account balances and income from financial assets. DAC 2 effectively dismantled traditional bank secrecy in Europe — but it was designed for fiat and left emerging digital assets outside its perimeter.
• DAC 3 (2015) — corporate transparency. A response to LuxLeaks. Mandatory exchange on advance tax rulings and advance pricing agreements (APAs).
• DAC 4 (2016) — the BEPS era. Country-by-Country Reporting (CbCR) for large multinational groups, enabling visibility into global profit allocation.
• DAC 5 (2016) — beneficial ownership transparency. Tax authorities’ direct access to ultimate beneficial owner (UBO) information collected under AML procedures.
• DAC 6 (2018) — targeting intermediaries. Mandatory disclosure by tax advisers, lawyers, and accountants of aggressive cross-border arrangements, creating an “internal oversight” environment.
• DAC 7 (2021) — the platform economy. Reporting obligations for digital platform operators (Uber, Airbnb, eBay). A first attempt to cover the gig economy — yet crypto-assets remained out of reach.
• DAC 8 (2023) became the necessary final piece of the mosaic. Due to pseudo-anonymity, cross-border nature, and self-custody, crypto-assets offered an ideal tool to bypass DAC 2. A taxpayer could hold millions of euros in Bitcoin, move them across borders without SWIFT, and no traditional bank would report it. DAC 8 removes this structural asymmetry.

According to estimates by the European Commission, DAC 8’s potential fiscal impact amounts to €1.7–2.4 billion in additional annual tax revenues. This underscores that, for Brussels and national governments, DAC 8 is not a theoretical exercise — it is a critical budgetary instrument.

“By adopting DAC 8, the EU has taken a leading position in implementing CARF and the OECD amendments to the Automatic Exchange of Information standard.” — KPMG EU Tax Centre

---

How Is DAC 8 Connected to MiCA and the Travel Rule?

DAC 8 does not exist in a vacuum. It is closely intertwined with other elements of the EU’s “digital finance package,” forming a comprehensive regulatory system:

• MiCA (Markets in Crypto-Assets Regulation) — Regulation (EU) 2023/1114, introducing licensing requirements for service providers and a classification of crypto-assets. DAC 8 relies on MiCA definitions, creating a unified legal and terminological framework. If a company is licensed under MiCA, it automatically falls under DAC 8 tax monitoring.
• TFR (Transfer of Funds Regulation) — updated Regulation (EU) 2023/1113, implementing the FATF “Travel Rule” for crypto-assets. It requires transmission of sender/recipient information with transfers. DAC 8 complements TFR by adding an annual tax-reporting layer on top of AML-focused “transaction snapshots.”
• OECD CARF (Crypto-Asset Reporting Framework) — the OECD’s global standard that DAC 8 incorporates into EU law. This ensures Europe becomes part of a global data-exchange network. However, DAC 8 goes beyond CARF by introducing stricter enforcement — including an account-blocking mechanism absent from the OECD standard.

“DAC 8 follows the adoption of MiCA in 2023. The Directive aligns key definitions and terminology with MiCA to ensure coherence across the EU regulatory landscape.” — Aurélie Clementz, Tax Partner, Ogier

---

Who Must Report Under DAC 8?

The central actor in DAC 8 is the Reporting Crypto-Asset Service Provider (RCASP). The definition is intentionally broad to eliminate opportunities for regulatory arbitrage.

RCASPs include:

• Crypto-exchanges (Centralized Exchanges) — platforms enabling crypto-to-crypto and crypto-to-fiat exchange (Binance, Kraken, Coinbase, Bitstamp).
• Custodial providers — firms holding cryptographic keys on behalf of clients (BitGo, Fireblocks, exchange custodial wallets).
• Crypto brokers — intermediaries executing trades for clients even if they do not directly custody assets.
• Crypto-ATM operators — physical terminals converting cash into crypto.
• Decentralized operators (DeFi) — the most complex point. If a protocol has a development team, DAO, or other structure exercising “material influence” or “control,” it may be treated as an RCASP. Indicators include admin keys, ability to upgrade smart contracts, a controlled front-end interface, or fee extraction for identifiable beneficiaries.

A critical nuance is extraterritoriality. DAC 8 applies not only to entities incorporated in the EU. Any provider — regardless of incorporation (Seychelles, Bahamas, Dubai, USA) — that serves EU-resident clients must register in an EU Member State (Member State of Single Registration) and file reporting. Ignoring this can lead to website blocking within the EU (IP blocking) and enforcement via international mechanisms.

“From 1 January 2026, new tax reporting obligations in Luxembourg will affect more than 25,000 existing reporting financial institutions. Crypto-assets have so far remained an investment product with almost no tax transparency obligations — a loophole in the current system.” — PwC Luxembourg

---

What Data Is Transmitted to Tax Authorities?

The scope is unprecedented. RCASPs compile and submit a detailed annual “snapshot” of a client’s financial activity.

Client data (Reportable User)

• Full name (or legal entity name)
• Residential/registered address
• Date and place of birth (for individuals) — essential to distinguish identical names
• Tax Identification Number (TIN) for all tax-residency jurisdictions — the “gold key” linking reporting to domestic taxpayer databases
• Country (or countries) of tax residence

Transaction data (reported in aggregated form, but with high granularity)

• Exchange — buying/selling crypto for fiat (fiat-to-crypto, crypto-to-fiat)
• Crypto-to-crypto exchanges — swaps (e.g., BTC→ETH, USDT→USDC)
• Transfers — withdrawals to external wallets, including non-custodial/cold wallets; not only the transfer event but also the wallet address is captured, effectively de-anonymizing ownership
• Retail payments — payments for goods/services above USD 50,000

Financial metrics for each category

• Fair Market Value (FMV) in fiat at the time of each transaction
• Quantity of units
• Number of transactions

Important: DAC 8 does not set a general threshold — all transactions are reportable. The USD 50,000 threshold applies only to retail payments, aligned with OECD CARF harmonization.

---

Which Crypto-Assets Are Covered?

DAC 8 adopts an “all-inclusive” crypto-asset definition based on MiCA, with extensions to prevent migration into unregulated niches.

Clearly included

• Classic cryptocurrencies: Bitcoin (BTC), Litecoin (LTC)
• Privacy coins: Monero, Zcash — not excluded; often treated as a red flag
• Altcoins and platform tokens: Ethereum (ETH), Solana (SOL), BNB
• Stablecoins: USDT, USDC, EURC, DAI — treated as e-money tokens or asset-referenced tokens
• DeFi tokens: governance tokens (UNI, AAVE, MKR)
• Security tokens: tokenized shares, bonds

Conditionally included

• NFTs — collectible NFTs may theoretically be excluded, but if an NFT is used for payment or investment (liquidity, marketplace trading, collateral), it becomes reportable. In practice, providers tend to report most NFTs conservatively.

Excluded

• CBDCs — reported via CRS (DAC 2) as fiat
• Closed-loop in-game currencies — assets confined to a game ecosystem and not redeemable into fiat

---

Entry into Force: Key Dates

The Directive is already being applied: data collection began on 1 January 2026. Understanding the timeline is critical, because many effects are delayed.

Date	Event	What it means for businesses and investors
17 October 2023	Directive adopted	EU Council formally approved DAC 8
13 November 2023	Entry into force	DAC 8 became part of EU law (Acquis communautaire)
31 December 2025	Transposition deadline	All 27 Member States must adopt national implementing laws
1 January 2026	Start of application	Transaction data capture and client identification become mandatory
1 July 2026	End of transition period	Providers must complete IT implementation and verify legacy clients
1 January 2027	Completion of pre-existing user verification	RCASPs must obtain self-certification from existing clients
30 September 2027	First automatic exchange	Tax authorities exchange 2026 data
1 January 2028	Strict TIN validation	Algorithmic validation of TIN correctness becomes mandatory

Liglex analytical insight: It is a dangerous misconception that you can “relax” until the first exchange in 2027. That is a trap. Data is being collected now, in real time. If a provider fails to capture FMV at the moment of a transaction in January 2026, reconstructing it later may be technically impossible or prohibitively expensive.

---

The “60-Day Rule” and the Account-Blocking Mechanism

DAC 8 introduces a unique enforcement mechanism (“kill switch”) that does not exist under OECD CARF. This is arguably the Directive’s strictest and most debated innovation.

How it works (per Section V of Annex VI):

1. The provider requests client information (self-certification and TIN).
2. If the client does not respond, a first reminder is sent.
3. If there is no response, a second reminder is sent.
4. If the information is still not provided within 60 days of the first request, the RCASP must (mandatory obligation) refuse to execute new transactions for the client.

“The 60-day rule is strict: if a user fails to provide a valid self-certification after two reminders, you must block them from carrying out exchange transactions. This is an obligation, not an option — an imperative ‘freeze’ under the Directive.” — TaxDo

What the block means:

• Prohibition on new transactions (buy/sell/exchange)
• Under some interpretations, a freeze on withdrawals until the data is provided
• Unblocking only after complete self-certification is submitted

For businesses using crypto for settlements, this creates a liquidity risk. Compliance is no longer “paperwork” — it becomes a survival condition.

---

Reporting Technical Standards: Implementing Regulation (EU) 2025/2263

To ensure uniformity, the European Commission adopted Commission Implementing Regulation (EU) 2025/2263 of 12 November 2025, approving strict technical standards:

• Format: reporting is exclusively in XML. The schema closely mirrors OECD CARF 2.0.
• Data structure fields include:
  • ResCountryCode — country code of residence
  • TIN — tax number
  • CryptoAssetType — asset type
  • TxType — transaction type
  • WalletAddress — wallet address (for transfers)

Critically, mandatory WalletAddress reporting for transfers to non-custodial wallets creates a verified link in tax databases between a real identity and a blockchain address. This enables tax authorities to track subsequent movements using blockchain analytics tools (Chainalysis, Elliptic).

---

What Penalties Apply for Non-Compliance?

The Directive does not harmonize penalties; each Member State sets its own. This has resulted in significant divergence.

Country	Maximum penalty	Source
Netherlands	€1,030,000	PwC Netherlands
Luxembourg	€250,000 (min. €10,000)	Draft Law 8592
Italy	€1,500 – €15,000	Decreto 194/2025
Germany	Determined by national law	KStTG

Important clarification: the €20,000–€500,000 range mentioned in some sources appeared in the European Commission’s December 2022 proposal, but was removed from the final Directive after Member State objections.

“Fragmentation of penalty regimes creates regulatory arbitrage. Providers must account for the registration jurisdiction when selecting a Single Registration Member State.” — PwC Global

---

How Does DAC 8 Affect Ukrainian Residents?

Ukraine is not an EU Member State, so DAC 8 does not apply directly to Ukrainian residents. However, its impact is substantial through several interconnected mechanisms that make Ukrainians’ crypto transactions transparent to tax authorities.

Mechanism 1: Using EU exchanges

If a Ukrainian tax resident uses an EU-registered exchange (Binance with an EU licence, Kraken with EU registration, Coinbase Europe, Bitstamp), the exchange must apply DAC 8 requirements to that client:

• KYC/AML identity verification with proof of address
• TIN collection — for Ukrainians, this is the RNOKPP (taxpayer identification code)
• Tax residency determination based on self-certification and documentation
• Reporting all transactions to the tax authority of the exchange’s country of registration

Even if the exchange is registered in Lithuania and the client is Ukrainian, the data is still collected. It is submitted to the Lithuanian tax authority, which may exchange it with Ukraine under bilateral arrangements or CRS.

Mechanism 2: CRS exchange — Ukraine is already in the system

Ukraine actively participates in automatic exchange under CRS (Common Reporting Standard), which can make EU-collected crypto data accessible to Ukrainian tax authorities:

Ukraine’s CRS timeline:

• 19 August 2022 — Ukraine signed the MCAA CRS
• 28 June 2024 — MCAA CRS entered into force for Ukraine after OECD Global Forum information security assessment
• 30 September 2024 — first international automatic exchange completed
• 1 January 2025 — CRS exchange with Switzerland became effective
• 1 May 2025 — Austria added Ukraine to its CRS partner list

Exchange scale:

• Ukraine sent information to 30+ jurisdictions
• Ukraine received data from 50+ jurisdictions

This means DAC 8 crypto data collected by an EU exchange can be transmitted to Ukraine through CRS. The tax authority can reconcile balances, income, and transactions against declarations.

Mechanism 3: Ukrainian legislation — moving toward DAC 8

Ukraine is progressively aligning its rules with European standards, including approaches to crypto taxation.

Law “On Virtual Assets” No. 2074-IX

• Adopted by the Verkhovna Rada and signed by the President in February 2022
• Not yet effective — pending amendments to the Tax Code
• Defines the NSSMC as the market regulator
• Grants the NBU licensing powers for financial institutions dealing with currency-backed assets

Draft Law No. 10225-d (taxation of crypto-assets)

• Adopted at first reading on 3 September 2025
• According to EY Ukraine, represents “an initial step toward implementing CARF and the EU DAC 8 Directive”

Key tax provisions in the draft:

Parameter	Rate / condition
Base rate	18% PIT + 5% military levy = 23%
Preferential 2026 rate	5% PIT + 5% military levy = 10% (for assets acquired before the law takes effect)
Non-taxable operations	Transactions below 1 minimum wage
Crypto-to-crypto	Not taxed until conversion into fiat
Expected effective date	1 January 2026

“The new draft law integrates European rules MiCA and DAC 8 (CARF) and introduces new tax obligations for service providers and private investors.” — Multilaw Network

Ukraine’s crypto market: why it matters

Ukraine is among global leaders in crypto adoption, making taxation highly material for millions of citizens.

Indicator	Value	Source
Chainalysis Global Crypto Adoption Index 2024	6th globally	Chainalysis
Crypto inflows (Jul 2023 – Jun 2024)	$106.1 billion	Chainalysis
Number of crypto holders	~6.5 million (~15% of population)	Ipsos/WhiteBIT
Share of financially active population investing in crypto	25%	Ipsos Survey
Position in Eastern Europe	2nd (after Russia)	Chainalysis
DEX volumes	$34.9 billion (+160%)	Chainalysis

These figures explain why Ukrainian authorities are pushing regulation: billions of dollars in potential tax revenue are at stake.

NBU position

The National Bank of Ukraine maintains a balanced position:

• Regulates digital assets with currency-like functions
• NBU Governor Andriy Pyshnyy supports regulated crypto activity
• Official position: virtual assets should not become legal tender
• Draft law 13356 — potential empowerment for inclusion in reserves

Practical 2025 actions: In September 2025, the NBU blocked Lithuania-based Trustee Global UAB for “unlicensed financial payment services,” affecting more than 7,000 cards of Ukrainian users. This demonstrates the regulator’s readiness for active enforcement.

---

Practical Scenarios: How It Works in Real Life

To translate legal concepts into real business decisions, Liglex Consulting modeled three typical scenarios.

Scenario 1: A private holder (the “cold wallet” problem)

Situation: Ivan, a French tax resident (a Ukrainian national with a residence permit), has a verified account on a major exchange (e.g., Binance or Kraken). In 2020, he bought 10 BTC and held them on the exchange. In February 2026, amid market growth, he decides to lock in profits: he swaps 1 BTC into USDT and then withdraws USDT to his personal hardware wallet (Ledger).

DAC 8 mechanics:

• Identification: From 1 January 2026, the exchange must update Ivan’s data. It requires confirmation of tax residency and a French tax number (Numéro Fiscal). If Ivan ignores requests for 60 days, partial account blocking (“kill switch”) applies — no new trades until documents are provided.
• Data capture: The exchange records two separate transactions:
• • Exchange (crypto-to-crypto): BTC→USDT. FMV of 1 BTC in EUR is recorded at the exact timestamp. In France, this is a taxable disposal event, so Ivan must report the gain.
  • Transfer: USDT withdrawal to Ledger. The exchange records the amount and, critically, the external wallet address — permanently linking the address to Ivan in tax databases.
• Reporting: By 30 September 2027, the exchange forms an XML report under Implementing Regulation (EU) 2025/2263 and submits it to the tax authority in its registration Member State.
• Automatic exchange: That authority automatically transmits the report to France (DGFiP) by 30 September 2027 — fully automated, no special request required.

Implications for Ivan: French tax authorities receive:

• Income data from the BTC→USDT exchange (capital gains base — up to ~30% in France)
• The cold wallet address and confirmation that assets are held there
• Full annual trading history

Ledger’s anonymity is effectively compromised at the entry/exit point. Authorities can apply blockchain analytics (Chainalysis, Elliptic) to trace subsequent movements.

Practical takeaway: If significant funds on a cold wallet were not previously declared, any transfer from an exchange to that address creates a documentary trail. A legalization strategy (voluntary disclosure, amnesty programs where applicable) should be developed before executing transactions in 2026.

---

Scenario 2: A business using crypto (operational transparency)

Situation: A German IT company receives payments from international clients in USDC to a corporate account with an institutional custodial service (e.g., Fireblocks). Part of the funds are converted into EUR for operating expenses; part is used to pay freelance developers abroad in crypto.

DAC 8 mechanics:

• Corporate identification: Fireblocks (as RCASP) identifies the company as a German tax resident. Critically, the provider must “pierce the corporate veil” and collect UBO data. For Passive NFEs, this is mandatory.
• All operations are captured: Inflows (USDC from clients) and outflows (to contractors, for conversion) are recorded with EUR FMV at the timestamp of each transaction. This requires high-precision historical pricing infrastructure.
• Reporting: Data is submitted to Germany’s Federal Central Tax Office (BZSt), including breakdown by transaction type, counterparties (where known), and amounts.

Risks and consequences:

• Automated reconciliation: DAC 8 data will be algorithmically matched to corporate tax returns. Any mismatch in conversion rates or undeclared income triggers an audit flag.
• Accounting synchronization: If corporate books record conversion at end-of-day rates while DAC 8 records FMV at 10:34:56, the discrepancy becomes an audit trigger.
• Contractor implications: If contractors are EU residents (e.g., Poland, Spain), transfers to them may also enter exchange systems, de-anonymizing their income and affecting contractor relationships.

Practical takeaway: Businesses handling crypto should:

• Implement automated FMV calculation at the time of each operation
• Align accounting policies with DAC 8 requirements
• Inform contractors about potential data transmission
• Conduct a compliance audit before the end of 2026

---

Scenario 3: A non-EU exchange (the end of offshore arbitrage)

Situation: A Ukrainian citizen with a Spanish residence permit becomes a Spanish tax resident and uses a Dubai- or Seychelles-registered exchange, assuming it shields assets from Spain’s Agencia Tributaria. This worked before 2026 — now it creates critical risks.

DAC 8 mechanics:

• Registration obligation: If a non-EU exchange wants to legally serve EU clients, it must select one EU Member State for Single Registration (e.g., Ireland, Lithuania). This is a requirement, not an option.
• Data collection: After registration, the exchange must identify the user as a Spanish tax resident, collect Spanish TIN (NIE/NIF), verify data, and report.
• Data transmission: The exchange files in Ireland (or another registration state), and the Irish tax authority automatically forwards the report to Spain.

If the exchange refuses to register:

• It may be placed on the EU “non-compliant provider” list maintained by the Commission
• Access to the website/app can be blocked at the ISP level within the EU (IP blocking)
• The client may lose access without VPN (itself a compliance red flag)
• The exchange risks secondary consequences, including loss of access to the EU banking rails (SEPA)
• Fiat off-ramps through EU banks will raise Source of Funds questions

Additionally, changing residency later does not remove data already collected for the Spanish residency period. Retroactive escape from DAC 8 is not possible.

Practical takeaway: “Hiding offshore while living in the EU” becomes unworkable and high-risk. The real options are:

• Full legalization and transparency in the country of residence
• Genuine change of tax residency (with physical relocation and severing EU ties)
• Using licensed providers with a clear tax strategy

---

Liglex Consulting Recommendations: What Should You Do Now?

For private investors and HNWIs

• Audit your digital footprint (do it now): Map all exchange accounts, including old/forgotten ones from 2017–2020. While retroactive taxation is legally constrained, 2026 data is being recorded in real time.
• Validate your TIN on every platform: Ensure correct TIN and accurate tax residency. A single digit error or outdated residency can send data to the wrong jurisdiction and trigger cross-border inquiries.
• Legalization strategy for cold wallets: Any transfer from an exchange to a hardware wallet (Ledger, Trezor) “lights up” that address permanently. If funds were not declared, plan legalization (voluntary disclosure, amnesties where available, declaration as property at FMV) before transacting.
• No structuring (“smurfing”): Avoid splitting large transfers into many small ones to evade thresholds. Tax authorities and financial intelligence units detect such patterns algorithmically. This can elevate exposure to intentional tax evasion allegations.
• Document Source of Funds: For large positions, prepare bank statements, purchase agreements, prior tax returns. EU banks will require these upon fiat off-ramps.

For businesses (corporate crypto treasuries)

• Upgrade KYC/onboarding procedures: If you accept crypto from partners/clients, build internal processes to collect their TINs. Add contractual obligations for counterparties to provide tax data and notify of residency changes.
• Accounting integration and automation: Implement automated FMV calculation in fiat at the moment of each transaction. Manual “average rates” or end-of-day conversions will not match DAC 8 reports and will trigger questions.
• Audit DeFi activity: Staking, yield farming, liquidity pools, lending require correct tax characterization. Misclassification can lead to penalties and recalculation of tax bases.
• Policy for self-custody addresses: Define internal controls for external transfers — who can initiate, how purpose is documented, how addresses are recorded.
• Prepare for audit: Maintain an “audit folder” with crypto accounting policy, transaction exports, cost basis calculations, and Source of Funds documentation — ready to provide within days, not weeks.

Strategic view

Do not attempt to “outsmart” the system by moving to unregulated Asian exchanges or deep DeFi without an exit strategy. With non-EU provider registration and blocking mechanisms, the window for grey-zone crypto banking in Europe has closed. The future is full transparency and lawful tax efficiency through proper planning, available reliefs, and robust ownership structuring.

---

What Comes Next?

DAC 8 marks the end of the “digital Wild West.” It transforms crypto from a tool of cyberpunks and the shadow economy into a fully regulated, transparent financial asset integrated into the global tax system. For EU tax authorities, it is a “Holy Grail” of information — the ability to see the full picture of residents’ crypto activity.

We are witnessing the emergence of an all-encompassing “fiscal panopticon” covering stablecoins, NFTs, complex DeFi protocols, and transfers to cold wallets. EU tax authorities now have both a legal mandate and a unified technological toolkit to link a cryptographic hash to a real taxpayer identity.

Key trends in the coming years:

• Global expansion: 63–75 jurisdictions have joined CARF; first exchanges start in 2027. By 2028–2029, most developed economies will be within automatic exchange networks.
• DeFi scrutiny: Expect broader provider definitions to capture DAOs and developer teams where admin keys or control exist.
• DAC 9? The Commission is already considering the next iteration to close remaining loopholes, particularly for P2P and non-custodial wallets.
• MiCA integration: Tax compliance becomes a de facto condition for maintaining licensing.
• Blockchain analytics as standard: Tax authorities increasingly use Chainalysis, Elliptic, CipherTrace. DAC 8’s identity–wallet linkage becomes the entry point.

“DAC 8 ensures that wealthy private individuals and institutional investors can no longer exploit jurisdictional arbitrage.” — aInvest Market Analysis

For capital owners, this is a signal for immediate action. The time when crypto tax issues could be ignored ended on 1 January 2026. Security now depends not only on wallet passwords, but on the quality of your tax strategy and reporting integrity.

Liglex Consulting can serve as your navigator in this new transparent reality. We help not only with compliance (to avoid blocks and penalties) but also with structuring asset ownership to minimize risks and tax burden within a strict yet predictable legal framework.

---

DAC 8 Readiness Checklist (10 Items)

The best approach is not “performative compliance,” but a measurable data system: residency → transactions → tax base → provable sources.

1. Provider map: where assets are stored, where trades occur, which entities/accounts are involved
2. Asset classification: what may qualify as “reportable crypto-assets,” including stablecoins and certain NFTs (case-by-case)
3. Tax residency of key persons (owner, beneficiaries, managers) and documentary support
4. Full export of 2026 transactions plus “tail” data to reconcile historical cost basis
5. Cost basis methodology and a unified P&L register for crypto operations
6. External-address (self-custody) transfer policy: approvals, purposes, retained documentation
7. Crypto accounting policy (P&L / Balance Sheet / Cash Flow effects) approved before the reporting period
8. Source of Funds / Source of Wealth for large fiat inflows/outflows
9. GDPR/confidentiality: what data may be transmitted by law and how provider notices are structured
10. Scenario modelling: what happens when tax authorities/banks/investors request explanations — prepare responses in advance

---

DAC 8 Transposition Across EU Member States: Current Status

Not all EU countries are at the same stage of implementation. Understanding a specific jurisdiction’s status is essential when choosing a strategy.

Germany — transposition completed

Parameter	Data
Law	Kryptowerte-Steuertransparenzgesetz (KStTG)
Bundestag	Approved on 6 November 2025
Bundesrat	Approved on 19 December 2025
Publication	Bundesgesetzblatt, 23 December 2025
Entry into force	24 December 2025
Reporting deadline	31 July 2027 for the 2026 period
Competent authority	Bundeszentralamt für Steuern (BZSt)

Netherlands — in progress

Parameter	Data
Bill	Act to Implement the EU Directive on the Exchange of Information on Crypto-Assets
Submission to Parliament	8 July 2025
Maximum penalty	€1,030,000
Reporting deadline	31 January 2027

Luxembourg — in progress

Parameter	Data
Bill	Draft Law No. 8592
Submission to Parliament	24 July 2025
Maximum penalty	€250,000 (min. €10,000)
Reporting deadline	30 June 2027

Italy — transposition completed

Parameter	Data
Council of Ministers	Approved on 8 October 2025
Parliament	Final approval in December 2025
Penalties	€1,500 – €15,000

---

Global Context: CARF and Expansion Beyond the EU

DAC 8 is part of a global move toward crypto tax transparency. OECD CARF is forming the international standard, with growing participation.

CARF status:

Metric	Number
Initial statement (Nov 2023)	58 jurisdictions
Current status (end of 2025)	63–75 jurisdictions
First exchanges in 2027	52 jurisdictions
First exchanges in 2028	15+ jurisdictions

Key non-EU jurisdictions that have joined CARF:

• United Kingdom
• Switzerland
• Singapore
• Canada
• Australia
• Japan
• South Korea
• UAE (in progress)

This means the strategy “leave the EU for another jurisdiction” has a limited shelf life. By 2028, most developed countries will exchange crypto transaction information automatically.

---

FAQ: Frequently Asked Questions

1) When does DAC 8 data collection start?

Data collection began on 1 January 2026. From that date, RCASPs must record client transactions with FMV in fiat at the moment of each transaction. The first automatic exchange among EU tax authorities will occur by 30 September 2027for the 2026 reporting period. In practical terms, this is roughly a 20-month window before your tax authority receives your full 2026 crypto activity data.

2) Does DAC 8 apply to Ukrainian residents?

Not directly, since Ukraine is not an EU Member State. However, if a Ukrainian resident uses an EU exchange (Binance with EU licensing, Kraken, Coinbase Europe), transaction data will be collected and submitted to the exchange’s Member State tax authority, and may then be transmitted to Ukraine via CRS (effective since September 2024). In addition, Draft Law No. 10225-d is preparing a domestic framework for crypto taxation in Ukraine.

3) What happens if I do not provide my TIN to an exchange?

This is one of DAC 8’s strictest mechanisms. After two reminders, if 60 days pass without valid self-certification, the exchange must block your ability to transact (buy/sell/exchange). Under some interpretations, withdrawals may also be frozen. Unblocking occurs only after complete self-certification with a correct TIN is submitted.

4) Are NFTs reportable?

Yes, if used for payment or investment purposes. Purely collectible NFTs may theoretically be excluded, but in practice the boundary is difficult to apply. If an NFT is traded on marketplaces (OpenSea, Blur), has market pricing, or is used as DeFi collateral, it is reportable. Providers often report most NFTs conservatively to avoid under-reporting risk.

5) Does DAC 8 cover transfers to cold wallets?

Yes — and this is critical. Transfers from an exchange to a non-custodial (cold) wallet are reported with the recipient wallet address, creating a verified link between your identity and a blockchain address. Tax authorities can then trace movements with blockchain analytics. P2P transfers between two non-custodial wallets (without a centralized provider) are formally outside automatic exchange, but may be traceable once one address has been “lit up.”

6) What if I already transacted in January 2026 without providing a TIN?

Update your data immediately on all exchanges. Providers must request self-certification and send two reminders; the 60-day countdown runs from the first request. Transactions executed before the TIN is provided will still be included in reporting, but marked as having late data submission.

7) How does DAC 8 affect DeFi operations?

It depends on the protocol. If a DeFi platform has an identifiable operator (developer team, DAO governance structure, front-end provider), it may qualify as an RCASP and be required to comply. Fully decentralized protocols without an identifiable operator may remain outside the Directive formally — but moving funds between DeFi and a centralized exchange will still be captured at the exchange level.

---

Author: Sergey Lipatnikov

No advice: This material is not legal, tax, investment, or any other professional advice. It should not be treated as a call to act or refrain from acting. The author and editorial team do not provide tax planning or compliance services via this publication.

Regulatory volatility: EU and Member State legal frameworks (including “gold plating”) are subject to change. Technical standards and tax authority interpretations may change without notice. We do not guarantee full accuracy at the time of reading.

Limitation of liability: The authors and owners of the resource are not liable for any direct or indirect losses arising from the use of this material, including penalties imposed by tax authorities, account blocks (“kill switch”), or lost profits.

Professional assistance: For decisions related to DAC 8 compliance, tax exposure assessment, or due diligence procedures, we strongly recommend consulting qualified tax advisers and lawyers specializing in the relevant jurisdiction (Member State of Reference).

---

List of Sources Used

1) EU Legal Acts (Primary EU Law)

• Council Directive (EU) 2023/2226 of 17 October 2023 amending Directive 2011/16/EU on administrative cooperation in the field of taxation (DAC 8). Official Journal of the European Union, L 2023/2122.
• Commission Implementing Regulation (EU) 2025/2263 of 12 November 2025 amending Implementing Regulation (EU) 2015/2378 as regards the standard forms and computerized formats (XML technical standard).
• Regulation (EU) 2023/1114 of 31 May 2023 on markets in crypto-assets (MiCA Regulation).
• Regulation (EU) 2023/1113 of 31 May 2023 on information accompanying transfers of funds and certain crypto-assets (TFR / Travel Rule).

2) International Standards (OECD)

• OECD (2023), Crypto-Asset Reporting Framework (CARF) and Amendments to the Common Reporting Standard, OECD Publishing, Paris.
• OECD (2024), CARF XML Schema and User Guide for Tax Administrations.

3) Member State Transposition (National Implementation)

• Netherlands: Wetsvoorstel Implementatie EU-richtlijn gegevensuitwisseling cryptoactiva (Bill No. 36782, 2025).
• Germany: Gesetz zur Umsetzung der Richtlinie (EU) 2023/2226 (Kryptowerte-Steuertransparenzgesetz – KStTG), adopted by Bundesrat on 19 December 2025.
• Italy: Schema di decreto legislativo recante recepimento della direttiva (UE) 2023/2226 (Legislative Decree No. 194/2025).
• France: Projet de loi de finances pour 2025 (Finance Bill 2025), articles relating to DAC 8 transposition and DGFiP registration.
• Luxembourg: Projet de loi No. 8592 (Draft Law on DAC 8 implementation), July 2025.

4) Expert Analysis and Reports

• GMN Analysis (2025). DAC 8: Global Paradigm of Tax Transparency & Operational Imperatives. Strategic Research Report.
• CLD Briefing (Jan 2026). DAC 8 Status Update: Compliance Requirements & Timeline. Analytical Note.
• Market Analysis (2026). DAC 8 Technical Implementation & Country Specifics (Netherlands, Italy, Germany). Consolidated Briefing.
• PwC Tax Insights. EU Direct Tax Newsalert: DAC 8 Implementation and Penalties (Netherlands/Germany), 2025–2026.
• EY Global Tax Alerts. Member States adoption of DAC 8 and national transposition updates, 2025.
• EY Global Tax Alert “EU adopts Directive introducing tax transparency rules for crypto assets”, October 2023.
• PwC Luxembourg “DAC 8 — an extension of existing tax transparency obligations”, 2025.
• KPMG EU Tax Centre “ETF 512: DAC 8 reporting and exchange of information”, May 2023.
• RSM US “DAC 8 and CARF present extensive reporting challenges”, 2025.

5) Reference Resources

• European Commission. Taxation and Customs Union: Administrative Cooperation in (direct) taxation.
• BZSt (Bundeszentralamt für Steuern). DAC 8 Registration Portal Documentation, 2026.

6) Ukraine

• EY Ukraine “The Draft Law on the taxation of income from virtual assets”, 2025.
• Chainalysis “2024 Global Crypto Adoption Index”.
• State Tax Service of Ukraine — CRS Implementation Report, 2024.
• KPMG “UA – Exchange of Information Takes Place under CRS”, 2024.