DAC8 Client Readiness: Getting Crypto Clients Ready Before the First Exchange

DAC8 is no longer a future event. It has been in force since 1 January 2026, and the first automatic exchange of crypto data to tax authorities lands in 2027. The firm's job now is client readiness — identity data, complete history, omissions surfaced before the window where corrections move from voluntary to audited closes. This guide is that readiness work, hedged, because the obligations and any disclosure are the client's under tax rules.

TL;DR

• Readiness ≠ reconciliation: readiness is pre-first-exchange prep; the reconciliation workflow is the ongoing post-exchange procedure.
• Timeline: DAC8 in force 1 Jan 2026; first automatic exchange 2027; CASPs already collecting identity/NIF + transaction data.
• The window is now and finite — once data is exchanged, a previously unreported position is visible.
• After exchange, corrections are generally treated under tax-audit procedures, not voluntary disclosure (state directionally; penalties not quantified here).
• Readiness = correct identity/NIF with platforms + complete disclosed history + reconciled position + flagged discrepancies.
• The disclosure decision is the client's, on counsel advice — the firm surfaces and reconciles. Jurisdiction-specific; not legal/tax advice.

Readiness vs reconciliation

Both are jurisdiction-specific and counsel-confirmed; this article is the pre-exchange half.

The timeline is finite

DAC8 has been in force from 1 January 2026; the first automatic exchange of crypto-asset data to tax authorities occurs in 2027. CASPs are already collecting users' tax identification and identity data and transaction information to be transmitted. The readiness window is now and finite, not open-ended. Exact timing/obligations are jurisdiction-specific, tax-adviser-confirmed.

Why the closing window matters

Once data is exchanged, a previously unreported position is visible to the tax authority, and generally a correction made after that point is treated under tax-audit procedures rather than as a voluntary disclosure, with the more favourable voluntary-disclosure treatment no longer available. The firm's role is to identify potential omissions early so the client can take advice while options are wider. Penalty consequences are not stated here — jurisdiction-specific, an avocat fiscaliste / tax adviser question.

What readiness requires

• Confirm identity/tax-identification details are correct with each platform.
• Ensure every wallet/exchange is disclosed and the history is complete.
• Reconcile that history so the client's own position is known before the authority's version.
• Flag discrepancies for advice.

The objective: no surprises at first exchange. Exact data set and remediation are jurisdiction-specific and the client's/firm's responsibility under professional and tax rules (the readiness extension of onboarding).

Whose decision the disclosure is

The decision to correct or disclose a past omission, and how, is the client's, taken on legal/tax advice (typically an avocat fiscaliste / tax adviser) — not a step the accounting firm decides unilaterally. The firm surfaces the issue early and reconciles the facts so advice can be taken in time. Keeping that boundary clear is part of the firm's professional scope; the disclosure is a counsel-led, jurisdiction-specific decision.

Practical guidance

1. Separate readiness from reconciliation — do readiness now, before 2027.
2. Treat the window as finite — DAC8 in force 2026, first exchange 2027.
3. Verify identity/NIF with platforms + complete disclosed history.
4. Reconcile so the client's position is known first, flag discrepancies.
5. Route disclosure decisions to the client's tax counsel — not the firm unilaterally.
6. Confirm obligations/treatment with an avocat fiscaliste / tax adviser — jurisdiction-specific; not legal/tax advice.

How vendor tools support readiness

Cryptio and Bitwave help assemble complete wallet/exchange history and reconcile it so the client's position is known before the first exchange. The tool supports readiness; identifying omissions for advice and the disclosure decision remain a client/counsel matter the firm facilitates within its scope.

How Wag3s helps

Wag3s for accountants assembles complete multi-wallet/exchange history and reconciles it so a firm can surface discrepancies and get clients ready before the 2027 first exchange — while the omission/disclosure decision stays the client's on counsel advice, and DAC8 obligations stay jurisdiction-specific and counsel-confirmed. See the accountants page.

Further reading

• DAC8 for Accounting Firms
• DAC8 Compliance Guide
• Onboarding Crypto Clients (Accounting Firm)
• Expert-Comptable & Crypto Clients (France)
• Scoping a Crypto Accounting Engagement
• Crypto Company Tax Audit France

Sources

• DAC8 client readiness = pre-first-exchange prep (identity/NIF correctness with platforms, complete disclosed history, reconciled position, flagged discrepancies); distinct from the ongoing post-exchange reconciliation workflow
• DAC8 in force from 1 January 2026; first automatic exchange of crypto-asset data to tax authorities in 2027; CASPs already collecting user tax identification/identity and transaction data — readiness window is now and finite
• After the exchange a previously unreported position is visible and a correction is generally treated under tax-audit procedures rather than voluntary disclosure (penalty consequences not quantified here — jurisdiction-specific, avocat fiscaliste/tax adviser question)
• The decision to correct/disclose a past omission is the client's on legal/tax advice (not the firm unilaterally); the firm surfaces and reconciles within its professional scope — jurisdiction-specific; not legal/tax advice