Crypto accounting for accounting firms

Your clients are holding and transacting in crypto — and your standard tools weren't built for wallets, tokens, or cost basis. CryptaCount gives your firm one platform to manage every client's crypto books, automate the hard parts, and post clean entries straight to their ledgers.

The problem with crypto clients today

Crypto work usually lands on the firm as a spreadsheet nightmare: exports from a dozen exchanges and wallets, no reliable cost basis, transfers that look like disposals, and no audit trail. It doesn't scale, it's error-prone, and it's hard to bill for the hours it actually takes.

How CryptaCount changes that

CryptaCount acts as the crypto sub-ledger for each of your clients:

• One platform, every client. Manage all your crypto clients from a single practice view, each with their own workspace and permissions.
• Cost basis, automated. Ingest every exchange and wallet, apply the right method per jurisdiction, and produce realized gains without manual reconciliation.
• Post to their books. Summarized period journal entries flow to your clients' ledgers — Xero is live today, with QuickBooks export available now and a direct connector on the roadmap — mapped to each client's chart of accounts.
• Audit-ready by default. Every figure traces from the GL line back to the source transaction.

Built for the way firms work

• Multi-client management — workspaces, roles, and permissions for your team and your clients
• 70+ jurisdictions — the cost-basis and reporting rules your clients actually file under
• 12 cost-basis methods — FIFO, LIFO, HIFO, WAVG, Specific ID, and more, applied consistently; jurisdiction-mandated treatments (UK Section 104, Canada ACB) apply automatically
• DeFi, NFTs, staking — the transaction types standard tools choke on
• Drill-down detail — answer any client or reviewer question from the transaction level

Win crypto work without building a crypto team

You don't need in-house blockchain expertise to take on crypto clients. CryptaCount does the ingestion, the cost basis, and the journal entries; your firm does the accounting and advisory it already does best — now for a client base most firms can't serve.

See the sub-ledger → · Compliance & reporting →

Why crypto engagements eat firm margin

The reason a crypto client erodes realisation is rarely the accounting judgment — it is the hours spent assembling data before any judgment can be applied. A single client may hand the firm CSV exports from four exchanges, a hardware wallet, two browser wallets and a DeFi position spread across several chains, none of which agree on column order, timestamp format or even what a 'transaction' is. Staff then burn billable time normalising files, guessing at transfers, and rebuilding cost basis from incomplete history. The work is unbillable because the client cannot see why reconciling a wallet should cost more than reconciling a bank account, and it is unrepeatable because next quarter the same manual grind starts from scratch. That is the structural problem CryptaCount removes by giving the firm a single crypto sub-ledger that ingests every venue once and keeps the history reconciled between periods.

When the data layer is solved, the engagement changes shape. Instead of seniors cleaning spreadsheets, they review classified activity and exceptions; instead of partners signing off on figures no one can reproduce, they sign off on entries that trace to source. The firm can then price the work on the value of the accounting and advisory it delivers, not on the volume of data-wrangling it had to absorb. See how the engine is structured on the crypto sub-ledger → page.

The practice workflow CryptaCount enables

For a firm, the unit of work is the client, and the platform is built around that. Each client sits in its own workspace with its own connected exchanges, wallets, chart of accounts and cost-basis policy, while the firm sees every workspace from one practice view. Onboarding a new crypto client becomes a defined sequence rather than an open-ended project: connect the venues, let the sub-ledger ingest and reconcile, resolve the first batch of exceptions, agree the measurement policy and method with the client, then run the first period close. From that point the workflow repeats predictably every month or quarter.

• Intake — connect each client's exchanges and wallets; the sub-ledger pulls full history, not just the current balance
• Reconcile — on-chain balances are tied out before anything is classified, so the starting point is trustworthy
• Classify exceptions — staff resolve only the transactions the engine flags, not every line
• Set policy once — cost-basis method and measurement basis are agreed per client and reused each period
• Close and post — summarized journal entries flow to the client's ledger, mapped to their chart of accounts
• Answer questions from source — any reviewer or client query drills from the GL line to the underlying transaction

Because the same structure applies to every client, a firm can standardise its crypto offering the way it has standardised bookkeeping or payroll: a documented process any trained team member can run, rather than tribal knowledge locked in one staffer's spreadsheet. The mechanics of how postings are assembled are described on the journal entries → page.

Controls a firm can stand behind

A firm puts its name on the numbers, so the control environment matters as much as the output. Within each workspace, role-based permissions separate who can connect a data source, who can classify and post, and who can review — the segregation of duties a reviewer expects to see. Closed periods lock, so a late edit cannot silently change a month the firm has already signed off. Every posted figure carries an unbroken trail back to the source transaction and, for on-chain activity, to the transaction hash, which means a partner can answer a challenge by opening the evidence rather than rebuilding it. Cost-basis method and measurement policy are applied consistently and recorded per client, so the same client's results are reproducible from one period to the next and from one staff member to another.

Reporting obligations the firm has to field

Clients increasingly ask their accountants what the new wave of crypto reporting means for them, and the firm needs a data foundation that can answer. Frameworks such as the OECD's CARF (Crypto-Asset Reporting Framework), the EU's DAC8 information-exchange rules, and the MiCA regime in Europe are pushing structured, jurisdiction-aware reporting onto crypto-active businesses. None of these can be satisfied from a pile of CSVs; they require a complete, classified, point-in-time record of activity tied to identifiable counterparties and venues. Because CryptaCount already holds that record per client, the firm is positioned to produce the underlying figures and reconciliations rather than scrambling when a client forwards a notice. See crypto compliance reporting → for how the reporting layer is organised.

Measurement is the other half of what the firm signs. Whether a client reports under IFRS or US GAAP, the sub-ledger applies the agreed measurement basis and produces the resulting entries, so the firm's financial statements rest on a consistent policy rather than ad-hoc valuations. The IFRS treatment is described on the IFRS crypto accounting → page.

Onboarding a crypto client without a crypto team

The biggest barrier to a firm taking on crypto work is the belief that it first needs to hire blockchain specialists. It does not. The specialist knowledge — how to read on-chain data, how to identify token movements, how to attach cost basis across transfers — is built into the platform. What the firm brings is exactly what it already has: the accounting judgment to agree a measurement policy, the diligence to review exceptions, and the client relationship to gather wallet addresses and exchange access. A typical first engagement is a guided setup: the firm connects the client's venues, the sub-ledger reconciles history, and the firm reviews the first classified period together with the client to confirm the policy choices. After that, the engagement runs on the same cadence as the rest of the client's bookkeeping.

Standardising crypto across the whole client book

What turns crypto from a novelty into a service line is repeatability across many clients at once. From the practice view, a firm can see the state of every client's crypto close — which have been ingested, which have outstanding exceptions, which are reconciled and ready to post — without logging into each one separately. That visibility lets a manager assign work, spot a client whose data has not synced, and keep every engagement moving on the same monthly or quarterly rhythm. The same role structure, the same exception-review step and the same posting discipline apply to each workspace, so a staff member trained on one client is trained on them all. As the firm wins more crypto clients, the marginal effort of adding another is the onboarding sequence, not a fresh research project, because the platform already knows how to read the chains and venues the new client uses. That is how a firm scales a crypto practice without scaling headcount in lockstep, and it is why a documented, tool-backed process beats a talented individual's spreadsheet: the spreadsheet leaves when the staffer does, but the workflow stays with the firm. Over time the firm also accumulates institutional knowledge of how to classify the unusual transactions its clients encounter, and because that knowledge is captured in the reconciled record rather than in someone's memory, the quality of the close improves period after period instead of resetting with each engagement.

Common pitfalls in firm crypto engagements

• Quoting crypto like ordinary bookkeeping — without a sub-ledger the data work is open-ended; with one it is predictable and can be priced as a defined service
• Accepting client spreadsheets as source — a re-keyed spreadsheet has no audit trail; ingesting the venues directly preserves one
• Treating self-transfers as disposals — wallet-to-wallet moves between a client's own addresses must net out, not create phantom gains
• Switching cost-basis method mid-engagement — produces results no reviewer can reconcile; fix the method per client and apply it consistently
• No segregation of duties — one person ingesting, classifying and posting is a control gap; use workspace roles to separate the steps
• Rebuilding history every period — re-importing from scratch each quarter wastes hours; a reconciled sub-ledger carries the prior periods forward

How CryptaCount helps accounting firms

For an accounting firm, CryptaCount turns crypto from a loss-leading favour into a repeatable line of business. It absorbs the data engineering — ingestion, reconciliation, cost basis and classification — and hands each client's ledger clean, mapped, summarized journal entries that the firm can review and post in minutes, with the full transaction record one click away when a question lands. The firm keeps the accounting and advisory it does best, standardises the process across every crypto client from a single practice view, and can finally serve a client base most firms still turn away. Explore the crypto sub-ledger → and journal entries → to see the engine in detail.

How do we price a crypto engagement profitably?

Once the sub-ledger removes the open-ended data work, the engagement has a predictable shape: setup, periodic close, and exception review. Most firms price it like a recurring bookkeeping service scoped to the client's transaction volume and number of venues, rather than billing unrecoverable hours against a spreadsheet rebuild. The reproducible process is what makes the margin defensible.

Can different clients use different cost-basis methods?

Yes. Method and measurement policy are set per client workspace, so one client can file under a pooling regime while another uses a lot-based method, each applied consistently within its own books. Jurisdiction-mandated treatments are applied automatically where they apply, so the firm is not configuring rules by hand for every country.

What happens when a client adds a new exchange mid-year?

You connect the new venue to that client's workspace and the sub-ledger ingests its history into the same reconciled record, mapped to the same chart of accounts. There is no rebuild of prior periods — the new source simply joins the existing structure and flows into the next close.

Can our staff and the client both have access?

Yes. Each workspace supports role-based permissions for your team and, where you want it, the client. You decide who can connect sources, who can classify and post, and who can only view, so the firm keeps control of the books while the client retains the visibility they expect.