Training Staff for Crypto Accounting: The Review Gap

Of the four legs of a crypto practice, people is the one a firm cannot buy overnight, and this guide is about closing that gap. A firm can buy a crypto sub-ledger this afternoon. It cannot buy, this afternoon, a reviewer who can look at a Uniswap mint or a restaking position and tell whether the tool got it right. That gap, competent review, is the real constraint on a crypto practice, because the review responsibility stays the firm's. This spoke is the people leg of building a crypto practice: what the team actually has to learn, and how to phase it. It is hedged, because required competence and supervision are governed by professional rules.

The short version

• Tooling is buyable overnight; reviewer competence is not, and the review and sign-off responsibility does not move to the tool.
• Staff need on-chain literacy (wallets, transfer versus disposal, swaps, LPs, lending, staking, restaking, receipt and LP tokens, gas and fees) and standards knowledge (the applicable classification and recognition framework).
• Knowing one without the other still cannot fully evaluate tool output.
• Structure the team as a deep core that sets the approach and reviews complex cases, with broader staff holding working literacy under supervision and an escalation path.
• Key-person risk (all knowledge in one person) and thin-literacy risk (no deep core) are both real.
• DAC8 (in force 2026, first exchange 2027) adds reconciliation and readiness competence. Required competence and supervision are governed by professional rules. This is not professional or training advice.

Why training is the bottleneck

Tooling produces output that still has to be reviewed and owned by competent staff. A reviewer who does not understand what a liquidity-pool mint, a staking receipt token, or a restaking position represents cannot tell whether the tool got it right. Infrastructure is acquirable overnight; reviewer competence is not. The professional responsibility to review and sign off does not move to the tool, so the knowledge gap is the real scaling constraint.

What a traditional accountant must learn

The goal is critical review of tool output, not becoming a developer. The required depth is firm- and role-specific, and a supervision judgement.

Product knowledge is not enough

On-chain literacy explains what happened; standards knowledge (the applicable IFRS, US GAAP, or local framework) explains whether the accounting is right. A reviewer strong on one and weak on the other still cannot fully evaluate the output. Training therefore pairs on-chain mechanics with the classification and recognition frameworks, calibrated to the firm's clients and jurisdiction.

Structuring the upskilling

The common structure is a small deep core that sets the firm's approach and reviews complex cases, with broader staff holding working literacy for routine cases under that supervision and an escalation path for unusual activity. The structure is a firm decision, but concentrating all the knowledge in one person is a key-person risk, and spreading thin literacy with no deep core is a review-quality risk.

DAC8 adds a competence area

With DAC8 in force from 1 January 2026 and the first automatic exchange in 2027, staff also need the reconciliation-against-reported-data and client-readiness competence (see DAC8 for accounting firms), not only the accounting. The obligations are jurisdiction-specific and sit with the firm and the client under professional and tax rules.

A practical training sequence for a traditional accounting team

The following sequence illustrates how a firm might phase the upskilling — it is a framework, not a standard, and the firm must calibrate it to its client base and professional rules:

Phase 1 — On-chain basics (all staff who will touch crypto files): Start with blockchain fundamentals — what a wallet address is, how to read a block explorer, the difference between an on-chain transfer and a disposal, what gas fees are and why they appear on every transaction. The objective is that staff can read a transaction history and distinguish routine transfers (wallet-to-wallet, gas) from economic events (swaps, disposals). This phase requires no DeFi knowledge; it is the prerequisite for everything else.

Phase 2 — DeFi interaction types (mid-level and above): Introduce the most common protocol interactions in the client base: Uniswap-style swaps, liquidity provision and LP tokens, lending and borrowing (Aave, Compound), and staking/restaking (including receipt tokens such as stETH). For each, the training should answer: what did the protocol do, what tokens appeared or disappeared, what is the accounting consequence? The goal is pattern recognition — can the reviewer look at an on-chain event and name what it is and what account it affects?

Phase 3 — Standards application (reviewers and seniors): Map each on-chain pattern to the firm's chosen accounting framework. How does a swap affect cost basis? Where do staking rewards land on the P&L (income at control, at what value)? How are LP positions decomposed? This is where on-chain literacy meets the firm's technical accounting positions, and where the IFRS/US GAAP framework shapes the actual journal entries. This phase is the most jurisdiction- and framework-specific, and is where the firm's technical leads must be involved.

Phase 4 — DAC8 reconciliation (all staff handling French/EU clients from 2026): Staff need to understand what a CASP reports under DAC8, how to obtain that data for a client, how to compare it against the books, and what to do when there is a discrepancy. This is a new competence area that did not exist before 2026 and cannot be inferred from general accounting training.

Practical guidance

1. Treat reviewer competence as the constraint, because tooling does not supply it.
2. Train on-chain literacy and standards together; both are needed to review.
3. Build a deep core plus supervised working literacy, with escalation.
4. Mitigate key-person and thin-literacy risks deliberately.
5. Add DAC8 reconciliation and readiness to the competence set.
6. Set required competence and supervision per professional rules. This is jurisdiction-specific and not professional or training advice.

How vendor tools support training

Cryptio and Bitwave expose the parsed legs of on-chain activity, which is a useful teaching surface for reviewers learning what an interaction is. The tool supports learning; the competence to review and the supervision responsibility remain the firm's.

Where Wag3s fits

Wag3s for accountants shows each on-chain interaction broken into its component legs with the classification applied, which gives a firm's reviewers a concrete surface to build the literacy that lets them evaluate the output. It is a teaching aid for the review, not a substitute for it: the required competence, the review, and the supervision stay the firm's under its professional rules. See the accountants page.

Further reading

• Building a Crypto Accounting Practice
• Crypto Asset Account Classification
• DeFi Position Chart of Accounts
• DAC8 for Accounting Firms
• White-Label Crypto Accounting
• Crypto Accounting Firm Tech Stack

Sources

This is an operational guide to building team competence, so it rests on the reviewer-competence requirement rather than a single external standard.

• Tooling is acquirable overnight but reviewer competence is not, and the professional responsibility to review and sign off does not move to the tool, so the knowledge gap is the real constraint on scaling a crypto practice.
• Staff need on-chain literacy (wallets, transfer versus disposal, swaps, LPs, lending, staking, restaking, receipt and LP tokens, gas and fees) and standards knowledge (the applicable classification and recognition framework); one without the other cannot fully evaluate output.
• The common structure is a deep core that sets the approach and reviews complex cases, with broader staff holding supervised working literacy and an escalation path; key-person and thin-literacy are both risks.
• DAC8 (in force 1 January 2026, first exchange 2027) adds reconciliation and readiness competence; the directive text is linked in the DAC8 client-readiness guide. Required competence and supervision are governed by professional rules and are jurisdiction-specific. This is not professional or training advice.