Onboarding Crypto Clients: The Accounting Firm's Checklist (2026)

Accounting·

Onboarding Crypto Clients: The Accounting Firm's Checklist (2026)

Onboarding a crypto client is not the standard new-client form plus a wallet address. It is complete access capture, an engagement letter scoping on-chain work and its limits, and the firm's own AML/KYC of a higher-risk client — a firm obligation under professional rules.
Author avatar Wag3s TeamEditorial team specializing in Web3 finance, crypto tax, and DAO operations. Based in Zurich, Switzerland.

Reviewed by Wag3s Editorial Team — verified against the access-capture and engagement-scoping steps of crypto client onboarding and the firm's own client-due-diligence obligations · Last reviewed May 2026

Onboarding Crypto Clients: The Accounting Firm's Checklist

Once an engagement is scoped and accepted, onboarding is the step that turns a signed crypto client into a deliverable file, and this guide is the checklist for doing it without leaving gaps. A crypto client is not a normal new client with a wallet address attached. Onboarding has to deliver three things the standard process does not: complete access capture, an engagement letter that scopes the on-chain work and its limits, and the firm's own due diligence on what is often a higher-risk profile. This spoke picks up where scoping ends and sits beneath building a crypto practice. It is hedged, because these are the firm's obligations under its professional and AML rules.

The short version

  • Crypto onboarding adds three things: complete wallet and exchange access capture, a crypto-scoped engagement letter, and the firm's own client due diligence.
  • A standard new-client form plus one address is insufficient; it neither establishes complete data nor defines responsibility.
  • Treat "is this the complete set of addresses and accounts?" as a documented client representation, not an assumption.
  • The engagement letter scopes chains, wallets, and activity, reliance on completeness, clean-up versus ongoing work, DAC8 handling, and advisory limits.
  • The firm has its own AML and KYC obligation, and a crypto client can be higher-risk. This is jurisdiction- and professional-body-specific.
  • Declining or exiting is a legitimate professional decision. The obligations are the firm's, and this is not professional, legal, or AML advice.

Three things beyond the normal process

Onboarding elementWhy crypto needs it
Complete access captureAn undisclosed wallet means the books cannot reconcile to the chain
Crypto-scoped engagement letterDefines what the firm is and is not responsible for
The firm's own client due diligenceOften a higher-risk profile under AML rules

A form plus an address is insufficient on all three counts. These are the firm's obligations under professional and AML rules.

Access capture

Capture every wallet and exchange account in scope, read access sufficient to reconcile, and a confirmation that the list is complete. An undisclosed wallet means the books cannot be reconciled to the chain and the engagement cannot be delivered as represented. Make "is this the complete set?" a documented client representation rather than an assumption, which is the access half of scoping carried into the file.

The engagement letter

Beyond standard terms, the letter should scope which chains, wallets, and activity types are covered; reliance on client-provided completeness; historical clean-up versus ongoing work; how DAC8 reconciliation and readiness are handled; and which determinations, such as classification and tax positions, are advisory or require the client's own counsel. The aim is to define responsibility precisely. The wording is a firm and professional-rules matter, not a template to copy blindly.

The firm's own AML and KYC

An accounting firm generally has its own client due-diligence and AML obligations under its professional and jurisdictional rules, and a crypto client can present a higher-risk profile that affects due-diligence depth and ongoing monitoring. This is the firm's own obligation, separate from the client's business AML. The requirements are jurisdiction- and professional-body-specific and should be confirmed with compliance counsel rather than read from this article.

The right to decline

Onboarding should preserve the ability to decline or exit. If access cannot be made complete, the risk profile sits outside acceptance criteria, or the client will not provide the required information, then not proceeding is a legitimate professional decision. Build acceptance criteria and exit terms into onboarding as a firm judgement under professional rules.

Practical guidance

  1. Capture complete access with a documented completeness representation.
  2. Use a crypto-scoped engagement letter covering chains, reliance, clean-up, DAC8, and advisory limits.
  3. Run the firm's own client due diligence; crypto can be higher-risk.
  4. Separate the firm's AML obligation from the client's business AML.
  5. Keep clear acceptance and exit criteria, since declining is legitimate.
  6. Confirm acceptance, due diligence, and engagement terms with the professional body and compliance counsel. These are jurisdiction-specific, and this is not professional, legal, or AML advice.

How vendor tools support onboarding

Cryptio and Bitwave help capture and validate wallet and exchange connections so completeness of access can be assessed at onboarding. The tool supports access capture; the engagement terms, the client due diligence, and the acceptance decision remain the firm's obligation under its professional and AML rules.

Where Wag3s fits

Wag3s for accountants supports complete wallet and exchange access capture and flags gaps, so a firm can document completeness at onboarding rather than assume it. The judgement layer stays with the firm: the engagement letter, the firm's own client due diligence, and the acceptance decision are the firm's obligation. See the accountants page.


Further reading

Scoping the first engagement correctly: historical versus ongoing

The most common scope mis-match at the start of a crypto engagement is treating historical clean-up work and ongoing accounting as if they are the same type of service. They are not, and conflating them in the engagement letter creates billing disputes and unmet expectations.

Historical clean-up is retrospective: the firm reconstructs transaction history, determines cost basis, reconciles wallet activity to reported positions, and produces accounting records for prior periods. This work has a defined scope (specific periods, specific wallets), a defined deliverable (reconciled books and reports), and variable effort depending on how clean the client's existing records are. The firm cannot know exactly how long it will take until the data has been imported and assessed. Pricing it as a fixed-fee engagement at proposal stage requires enough discovery to understand the volume and quality of the transaction history.

Ongoing accounting is prospective: the firm maintains the books month by month as new transactions occur. Volume is more predictable, categorization decisions carry forward from prior periods, and the work becomes more efficient as the firm builds knowledge of the client's protocol interactions and treasury behaviour. Monthly retainer pricing is common for this work.

The engagement letter should be explicit about which type of work is covered and how the billing basis differs:

  • Historical scope: define the periods covered, the wallets in scope, the deliverable (reconciled ledger to X date), the billing basis (time and materials or fixed fee after discovery), and any exclusions (specific DeFi protocols the firm's tools cannot parse).
  • Ongoing scope: define the monthly workflow, the deliverable cadence, the assumptions (client provides complete access; all transactions by the 5th of the following month), and the protocols covered.

Mixing the two without distinguishing them in the fee structure is the source of most post-engagement disputes in crypto accounting practices. The client believes the historical work was included in the ongoing rate; the firm charged for it separately. Both believed the engagement letter was clear.

The other practical scoping point: DeFi protocol coverage. Not all crypto accounting tools can correctly parse all DeFi interactions. The engagement letter should state which protocol interactions are within the firm's scope (and the tool's capability) and which are out-of-scope or require manual treatment. This is not a weakness — it is an honest scope definition that protects both parties.

Sources

This is an operational onboarding guide, so it draws on the firm-side acceptance and engagement-letter model rather than a single external authority.

  • Crypto onboarding adds complete wallet and exchange access capture, a crypto-scoped engagement letter, and the firm's own client due diligence on top of standard client acceptance; a form plus one address is insufficient.
  • Access capture requires every in-scope wallet and exchange, read access to reconcile, and a documented client completeness representation, because an undisclosed wallet means the books cannot reconcile to the chain.
  • The engagement letter scopes chains, wallets, and activity, completeness reliance, clean-up versus ongoing work, DAC8 handling, and advisory, classification, and tax limits; the wording is a firm and professional-rules matter.
  • An accounting firm has its own client due-diligence and AML obligations (crypto is often higher-risk), separate from the client's business AML. Declining or exiting is a legitimate professional decision. These points are jurisdiction- and professional-body-specific, and this is not professional, legal, or AML advice.
Editorial disclaimer
This article is informational and does not constitute professional, legal, or AML advice. Client acceptance, due diligence, and engagement terms are governed by the firm's professional and AML rules and jurisdiction. Confirm with the relevant professional body and compliance counsel.