Skip to content
All guides

Client onboarding · All teams · Oct 3, 2026 · 2 min read

Onboarding a new crypto client: the document request checklist

What to ask for on day one, how to spot what's missing, and how to set the engagement up for a clean first year.

By ChainLedger editorial team · Crypto audit, tax and fund reporting · Last reviewed

Key takeaways

  • Ask for every account, including closed ones. Missing accounts cause most problems later.
  • Public addresses and view-only keys are enough. Never accept private keys.
  • Check balances early so gaps surface weeks before the deadline, not days.

The first weeks of a crypto engagement decide how painful the rest of it will be. A complete request list, sent on day one, saves rounds of follow-up and late surprises.

What to request

ItemWhy
List of all wallets, with public addressesTo pull the full on-chain history
List of all exchange accounts, open and closedClosed accounts often hold missing purchases
View-only API keys for each exchangeTo sync history without any trading rights
Exchange statements or CSV exportsFor exchanges without an API, or closed ones
Prior-year returns and workpapersTo carry forward cost basis and methods
Custodian statementsFor assets held with a custodian
Notes on gifts, payments, airdrops, miningIncome and basis that won't be obvious on-chain

First-week checks

  1. 1Sync every account and check each balance against its live balance.
  2. 2List transfers to and from addresses that aren't on the client's list.
  3. 3Flag coins that arrived with no purchase on record.
  4. 4Confirm ownership of each wallet with a signed message.
  5. 5Screen addresses against OFAC lists before producing anything.
  6. 6Agree the lot method, cutoff and pricing policy with the client in writing.

In ChainLedger, each client gets their own workspace. Wallets connect by address, exchanges with view-only keys, and balance checks and flags appear as soon as the first sync finishes.

Related product page: Wallet and exchange integrations