DAC8 Transposition by Country

DAC8 set one hard EU deadline — transpose into national law by 31 December 2025, apply from 1 January 2026 — and the Member States hit it unevenly. This spoke is not about the Directive's substance; it is about the rollout. For a CASP operating across several Member States, "uneven transposition" decides which national rules you actually have to satisfy and, just as importantly, when those rules became knowable. The substance of the obligation sits in the DAC8 vs CARF hub and the data-collected reference; here the question is purely the patchwork of national implementation and how to plan around it.

The rollout in short

• The deadline was to transpose by 31 December 2025 and apply from 1 January 2026. First reporting period: calendar year 2026. First exchange: by 30 September 2027.
• The rollout was uneven: a significant number of Member States transposed at or just past the deadline, and several adopted after 1 January 2026 with retroactive application to the start of the reporting period.
• Late transposition buys no grace period: the EU effective date did not move, so data collection had to begin 1 January 2026 regardless.
• National details vary: reportable fields, electronic-search providers, penalty levels, and filing deadlines are set per Member State and are not identical.
• Plan for variation, not uniformity: one core data model plus per-jurisdiction overlays.

The EU-level timeline is fixed

The Directive sets the dates that do not change regardless of national transposition speed:

These are the anchors. A CASP plans against them, not against any individual Member State's statute date. The single most common planning error is treating a late national transposition as permission to start data collection late — it is not (see DAC8 compliance guide).

What "uneven" actually looked like

By early 2026, roughly half of the 27 Member States had transposed DAC8 into national law — several of them very close to the 31 December 2025 deadline. The remainder followed through the first months of 2026, with some adopting their transposing legislation after the 1 January 2026 effective date and applying it retroactively to the start of the first reporting period.

The practical consequences of a late-transposing Member State:

1. The obligation still applies from 1 January 2026. Retroactive application means a CASP that delayed data collection waiting for the national statute has a back-fill exercise covering January 2026 onward.
2. National details landed late. Penalty levels, the list of accepted electronic-search providers for due diligence, and the exact technical schema for some Member States were not knowable until the transposition was published — but the data they govern was already being generated.
3. The exchange deadline did not move. Whatever the national transposition date, FY 2026 data must be exchanged by 30 September 2027.

Why this matters for a multi-jurisdiction CASP

A CASP serving users across several Member States does not file 27 different reports. It reports to its home Member State authority, which exchanges the data onward. But the data has to carry the per-jurisdiction detail the exchange requires, and those details differ:

The design principle that survives uneven transposition: one core data model, per-jurisdiction overlays. Build the model against the home-state transposition and the EU schema, then layer the national variations for the Member States whose residents you serve. A model hard-coded to one Member State's rules breaks the moment you onboard users elsewhere.

How to plan around it in 2026

For a CASP in mid-2026, the prioritized actions:

1. Confirm your home-state transposition is final and read the national specifics (fields, deadline, electronic-search providers, penalties).
2. Map your user base by Member State of tax residence — this defines which national overlays you actually need.
3. For any late-transposing Member State you serve, treat the obligation as live from 1 January 2026 and check whether you have a back-fill gap.
4. Do not wait for full EU uniformity — it will not arrive in time to be a planning input. Build for variation now.
5. Reconcile your transaction data continuously so the back-fill, where it exists, is feasible (see multi-chain reconciliation).

Where vendors fit

• Sumsub handles the due-diligence layer, including the per-jurisdiction electronic-search variation that uneven transposition produces.
• TaxBit generates the reporting output and can emit per-jurisdiction variants from a single data model.
• Cryptio normalizes the underlying transaction data so the back-fill required by late transposition is actually possible.

No single tool resolves uneven transposition — it is a data-model and program-management problem first.

Where Wag3s sits: one model, many overlays

The design principle that survives uneven transposition is one core data model with per-jurisdiction overlays, and that is a data-layer job. Wag3s Ledger supports it:

• Multi-chain reconciliation with retained lineage so a back-fill from 1 January 2026 is feasible (see multi-chain reconciliation)
• Per-user aggregation by Member State of tax residence
• Counterparty categorization at the transaction level
• Audit reconstruction of any reported aggregate

Reading each national transposition — the accepted electronic-search providers, the local filing deadline, the penalty regime — is work for qualified counsel in each Member State; Wag3s holds the data model they parameterize. See the Wag3s Ledger product page for module details.

Further reading

• DAC8 Compliance Guide 2026 — the umbrella article
• DAC8 vs CARF Difference
• DAC8 vs MiCA
• DAC8 Data Collected
• DAC8 CASP Penalties
• DAC8 and Non-EU Exchanges
• Multi-Chain Reconciliation

Sources

• Council Directive (EU) 2023/2226 (DAC8) — EUR-Lex
• European Commission — DAC8 overview
• OECD Crypto-Asset Reporting Framework — model rules and commentary
• Example national transpositions: BMF (Germany) — Gesetz zur Umsetzung der Richtlinie (EU) 2023/2226; France (DGFiP) — Décret n° 2025-1276 du 19 décembre 2025 on CASP reporting obligations