DAC8 for Accounting Firms

DAC8 does not put a reporting obligation on accounting firms. It does something subtler and, for a practice with crypto clients, more demanding: it gives the tax authority an independent data feed that every crypto client's return will now be silently checked against. The firm's job changes from "compute and file" to "compute, reconcile against what the authority will independently see, and document the difference." This article lays out the new workflow.

TL;DR

• No direct DAC8 obligation for firms (unless the firm is itself a CASP). The change is a new reconciliation duty.
• The workflow gains a step: reconcile the client's books against what CASPs will have reported, before filing.
• First cross-check: FY 2026 returns, against data exchanged by 30 September 2027.
• Build a standard procedure: collect access → normalize → estimate CASP-reported figures → compare → investigate discrepancies against a firm-set materiality threshold → document in the client file.
• Re-scope and re-price crypto clients to reflect the added reconciliation work.

The workflow change, precisely

The pre-DAC8 crypto-client workflow:

1. Collect client wallet addresses and exchange access.
2. Reconstruct and compute gains/income under the relevant national rules.
3. File the return.

The post-DAC8 workflow adds a reconciliation step that is not optional in practice:

1. Collect client wallet addresses and exchange access.
2. Reconstruct and compute gains/income.
3. Estimate what each CASP will have reported for the client (aggregate acquired/disposed against fiat and crypto, transfers).
4. Reconcile the computed position against the estimated CASP figures.
5. Investigate material discrepancies — missing wallet, mis-classified counterparty, timing differences — before filing.
6. Document the reconciliation in the client file.
7. File the return.

Steps 3–6 are new. They exist because, from FY 2026, the authority receives the CASP data independently and a mismatch with the filed return is an automatic flag (see DAC8 impact on individuals).

What a standard DAC8 reconciliation procedure looks like

A practice handling multiple crypto clients should standardize this rather than improvising per client:

The materiality threshold is a firm policy, not a regulatory number — do not adopt an invented "X% / €Y" figure as if it were prescribed. Set it, document it, apply it consistently.

Professional exposure, framed correctly

The firm's exposure is not a DAC8 fine — that sits on CASPs. It is professional:

• A return that materially diverges from CASP-reported data without a documented basis is a quality-of-work and diligence problem.
• "We computed from the client's data" is no longer a complete answer when the authority has independent data the firm did not reconcile against.
• The documented reconciliation is what demonstrates the firm did its job.

This reframes DAC8 for a practice: it is a client-file diligence and professional-risk matter, managed with a standard procedure, not a new filing.

Re-scoping and re-pricing crypto clients

The added steps are real work. A crypto client in 2026 requires:

• History reconstruction (often multi-year, multi-chain)
• Ongoing transaction normalization
• An annual DAC8 cross-check and discrepancy investigation
• Reconciliation documentation

Firms typically move crypto clients off a flat return fee onto a scoped engagement that reflects transaction volume and chain/protocol complexity. The DAC8 reconciliation is a recurring annual line, not a one-off. Pricing that does not account for it underprices the engagement and absorbs the professional risk for free.

Where vendors fit

• Cryptio is the transaction-normalization layer many practices standardize on for multi-client crypto books.
• TaxBit produces the reporting-shaped figures useful for estimating the CASP-side numbers.
• Sumsub is relevant where the firm advises CASP clients on the due-diligence side.

The reconciliation judgement — materiality, discrepancy investigation — remains the firm's, supported by but not replaced by tooling.

How Wag3s helps

Wag3s Ledger is built for the practice workflow:

• Multi-client, multi-chain reconciliation from a single admin surface (see multi-chain reconciliation)
• Per-jurisdiction cost-basis computation (FIFO/LIFO/PMP)
• Per-user aggregation matching the DAC8 reportable categories, to estimate the CASP-side figures
• Retained lineage so the reconciliation memo is supported by traceable data

See the Wag3s for accountants page and the Ledger product page.

Further reading

• DAC8 Compliance Guide 2026
• DAC8 Data Collected
• DAC8 Impact on Individuals
• Crypto Accounting Pennylane Export
• Crypto Audit Readiness
• 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