DAC8 Client Readiness: Getting Crypto Clients Ready Before the First Exchange (2026)
DAC8 Client Readiness: Getting Crypto Clients Ready Before the First Exchange (2026)
Reviewed by Wag3s Editorial Team — verified against DAC8 in force from 1 January 2026, the first automatic exchange in 2027, CASP collection of user identity/NIF and transaction data, and the closing window for resolving past omissions · Last reviewed May 2026
DAC8 Client Readiness: Getting Crypto Clients Ready Before the First Exchange
DAC8 is no longer a future event, and this guide is about the specific, time-limited work it creates for a firm right now: getting crypto clients ready before the first data exchange. The directive 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 today is client readiness: correct identity data, a complete history, and omissions surfaced before the window in which corrections move from voluntary to audited closes. This spoke is distinct from the ongoing reconciliation workflow and sits under building a crypto practice. It is hedged, because the obligations and any disclosure are the client's under tax rules.
The short version
- Readiness is not reconciliation: readiness is the pre-first-exchange preparation; the reconciliation workflow is the ongoing post-exchange procedure.
- Timeline: DAC8 in force 1 January 2026, first automatic exchange in 2027, with CASPs already collecting identity and tax-identification (NIF) and transaction data.
- The window is now and finite, because once data is exchanged a previously unreported position becomes visible.
- After the exchange, corrections are generally treated under tax-audit procedures rather than voluntary disclosure (stated directionally; penalties are not quantified here).
- Readiness means correct identity and NIF with the platforms, a complete disclosed history, a reconciled position, and flagged discrepancies.
- The disclosure decision is the client's, taken on counsel advice; the firm surfaces and reconciles. This is jurisdiction-specific and not legal or tax advice.
Readiness vs reconciliation
| Readiness (this article) | Reconciliation (the workflow) | |
|---|---|---|
| When | Before the first exchange | From the first exchange onward |
| What | Identity, history, and omissions prep | Reconcile books against reported data |
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, and 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. The exact timing and obligations are jurisdiction-specific and tax-adviser-confirmed.
Why the closing window matters
Once data is exchanged, a previously unreported position becomes 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 the options are wider. Penalty consequences are not stated here; they are jurisdiction-specific and an avocat fiscaliste or tax adviser question.
What readiness requires
- Confirm identity and tax-identification details are correct with each platform.
- Ensure every wallet and 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 is no surprises at the first exchange. The exact data set and any remediation are jurisdiction-specific and the client's and firm's responsibility under professional and tax rules. This is 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 and tax advice (typically an avocat fiscaliste or 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
- Separate readiness from reconciliation, and do readiness now, before 2027.
- Treat the window as finite: DAC8 in force 2026, first exchange 2027.
- Verify identity and NIF with the platforms and complete the disclosed history.
- Reconcile so the client's position is known first, and flag discrepancies.
- Route disclosure decisions to the client's tax counsel, not the firm unilaterally.
- Confirm obligations and treatment with an avocat fiscaliste or tax adviser. This is jurisdiction-specific and not legal or tax advice.
How vendor tools support readiness
Cryptio and Bitwave help assemble a complete wallet and 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 and counsel matter that the firm facilitates within its scope.
Where Wag3s fits
Wag3s for accountants assembles a complete multi-wallet and exchange history and reconciles it, so a firm can surface discrepancies and get clients ready before the 2027 first exchange. It does the reconciliation, not the disclosure call: the omission and disclosure decision stays the client's on counsel advice, and the 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
- EUR-Lex — Council Directive (EU) 2023/2226 (DAC8): the directive that extends automatic exchange of information to crypto-assets, the basis for the reporting cycle that makes client readiness time-limited.
- DAC8 client readiness is pre-first-exchange preparation (identity and NIF correctness with the platforms, a complete disclosed history, a reconciled position, and flagged discrepancies), distinct from the ongoing post-exchange reconciliation workflow.
- DAC8 is in force from 1 January 2026, with the first automatic exchange of crypto-asset data to tax authorities in 2027; CASPs are already collecting user tax-identification and identity and transaction data, so the 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 are not quantified here; they are jurisdiction-specific and an avocat fiscaliste or tax adviser question). The decision to correct or disclose is the client's on legal and tax advice, not the firm unilaterally; the firm surfaces and reconciles within its professional scope. This is not legal or tax advice.
Expert-Comptable & Crypto Clients in France: Scope, Limits, DAC8 Prep (2026)
A French expert-comptable can serve crypto clients, but the role has a scope and limits set by professional rules, and DAC8 — transposed via the loi de finances 2025, in force from 2026 — changed what readiness means. The role, the limits, and the prep, as a professional and tax-rules question.
The Crypto Accounting Firm Tech Stack: Build, Buy, or White-Label (2026)
A firm's crypto stack is three layers — ingestion/reconciliation, a sub-ledger and chart of accounts, and a tax/reporting layer including DAC8. Almost no firm should build the ingestion layer. The stack, the build-vs-buy line, and what stays the firm's, hedged.
Every chain, integration, and competitor mentioned in this article gets its own page — coverage detail, comparison signals, and the audit trail your finance team needs.
- Chain
Solana
SPL tokens, native stake, Jupiter, Metaplex NFTs.
View page - Chain
Polygon
PoS, zkEVM, MATIC → POL migration, validators.
View page - Chain
Ethereum
ERC-20, DeFi, gas, restaking — the largest ecosystem.
View page - Integration
NetSuite integration
Mid-market and enterprise crypto subledger.
View page - Integration
QuickBooks integration
SMB GL with daily JE sync.
View page - Integration
Safe integration
DAO and corporate multi-sig accounting.
View page