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
| Item | Why |
|---|---|
| List of all wallets, with public addresses | To pull the full on-chain history |
| List of all exchange accounts, open and closed | Closed accounts often hold missing purchases |
| View-only API keys for each exchange | To sync history without any trading rights |
| Exchange statements or CSV exports | For exchanges without an API, or closed ones |
| Prior-year returns and workpapers | To carry forward cost basis and methods |
| Custodian statements | For assets held with a custodian |
| Notes on gifts, payments, airdrops, mining | Income and basis that won't be obvious on-chain |
First-week checks
- 1Sync every account and check each balance against its live balance.
- 2List transfers to and from addresses that aren't on the client's list.
- 3Flag coins that arrived with no purchase on record.
- 4Confirm ownership of each wallet with a signed message.
- 5Screen addresses against OFAC lists before producing anything.
- 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