Crypto accounting for QuickBooks

CryptaCount is the crypto sub-ledger that sits in front of your general ledger. A direct QuickBooks Online integration is on the roadmap: it will ingest your on-chain and exchange activity, calculate cost basis and gains, and post clean period journal entries to QuickBooks — so your books stay the system of record and the transaction-level detail stays in the sub-ledger.

The QuickBooks Online connector is coming soon. Today you can run the full crypto sub-ledger in CryptaCount and export journal entries for import into QuickBooks.

How it will work

QuickBooks wasn't built to track wallets, tokens, or cost basis across thousands of transactions — that's what the sub-ledger is for. Once the connector is live, CryptaCount will:

1. Ingest every transaction from your exchanges and wallets,
2. Calculate cost basis and realized gains/losses (your choice of method) and apply your measurement policy,
3. Summarize the activity into journal entries per period, and
4. Post those entries to QuickBooks, mapped to your chart of accounts.

Your GL stays clean; every posted line will drill back to the underlying transactions in CryptaCount.

Available today: export for QuickBooks

Until the direct connection ships, you can run the full sub-ledger in CryptaCount and export summarized journal entries to import into QuickBooks Online or Desktop — the same double-entry, period-level postings, mapped to digital assets, realized gain/loss, income (staking, mining, rewards), and fees.

What will sync

• Period journal entries — summarized, double-entry, ready to post
• Chart of accounts mapping — your GL accounts, kept aligned
• Drill-down — every posted line traces to transaction-level detail in the sub-ledger

Why finance teams use CryptaCount

• Cost basis at scale — 12 disposal methods (FIFO, LIFO, HIFO, WAVG, Specific ID, and more) across exchanges and wallets; jurisdiction-mandated treatments (UK Section 104 pooling, Canada ACB) apply automatically
• Clean close — summarized entries instead of thousands of raw lines cluttering the GL
• Audit-ready — a complete, traceable trail from each GL line back to the source transaction
• IFRS / US GAAP — measurement handled in the sub-ledger per your policy

Explore the engine: Crypto sub-ledger & cost basis → · Accounting for firms →

Why the sub-ledger posts summaries, not every transaction

QuickBooks Online is a general ledger built for invoices, bills and bank feeds — not for carrying tens of thousands of token movements, each with its own acquisition lot and cost basis. The whole point of running CryptaCount as the crypto sub-ledger in front of your GL is to keep that detail where it belongs: in a system designed to reconcile wallets and exchanges, then hand QuickBooks a clean, period-level summary. When the connector is live it will post summarized journal entries rather than a line for every transfer, swap, fee and reward. A single trading week can generate thousands of on-chain events; pushing each one into QuickBooks would bloat the GL, slow every report and make the trial balance unreadable — without adding a shred of accounting value, because the GL only needs the net effect on each account.

The sub-ledger model mirrors how mature finance teams already handle payroll, inventory or a high-volume payments processor: the operational system holds the line-by-line record, and only the summarized debits and credits reach the GL. Crypto is no different. CryptaCount aggregates an accounting period's activity into entries that move digital assets, realized gain/loss, income (staking, mining, rewards) and fees by their net amounts, and every posted line drills straight back to the underlying transactions. You get a tidy ledger and a complete record — not a trade-off between the two. Read more about how the engine is structured on the crypto sub-ledger → page.

Mapping to your chart of accounts

Before any entry posts, you decide where each kind of crypto activity lands in your QuickBooks chart of accounts. CryptaCount separates the economic events — acquisitions, disposals, transfers between your own wallets, income receipts, network and exchange fees, and revaluations — and lets you map each to a specific GL account. A typical setup points digital asset holdings at one or more asset accounts, realized gains and losses at income-statement accounts, staking and reward income at a revenue or other-income account, and fees at an expense account. Because you control the mapping, the postings match the account structure your auditors and stakeholders already expect, instead of forcing your books to fit the tool.

• Digital asset accounts — one combined holdings account, or split by asset, venue or strategy
• Realized gain / loss — disposals measured under your chosen cost-basis method
• Income — staking, mining, rewards and airdrops recognized at value on receipt
• Fees — network (gas) and exchange fees, kept distinct from trading results
• Revaluation / remeasurement — where your policy requires period-end adjustments

Mapping is set once and reused every period, so the entries stay consistent close after close. If you add a new exchange, wallet or token, it flows into the same account structure without a rebuild. See how postings are assembled on the journal entries → page.

What the integration will and will not do

It helps to be precise about the boundary between the sub-ledger and QuickBooks, because a clean division of labor is what keeps both systems trustworthy. The connector is a posting and mapping bridge — not a replacement for either product.

What it will do: ingest activity from your exchanges and wallets, calculate cost basis and realized results under your policy, summarize each period into double-entry journal entries, map those entries to your chart of accounts, and post them to QuickBooks Online with drill-down back to the source transactions. What it will not do: it will not turn QuickBooks into a crypto data warehouse, will not post thousands of raw lines, will not overwrite your existing bank or invoice workflows, and will not make accounting-policy decisions for you. Measurement, classification and method selection stay under your control inside the sub-ledger; QuickBooks remains the system of record for the financial statements.

The close and reconciliation workflow

A monthly or quarterly close with crypto follows a predictable rhythm once the sub-ledger is in place. First, CryptaCount ingests the period's transactions from every connected exchange and wallet and flags anything that needs a human decision — an unknown counterparty, a token it has not seen, or a transfer that may be an internal move rather than a disposal. You classify those exceptions, confirm that on-chain balances reconcile to what the sub-ledger expects, and review the cost-basis results. Only then do you generate the period entries and post them.

Because the postings are summarized, the review at the QuickBooks end is fast: you are checking a handful of journal lines per account, each backed by a full transaction list you can open on demand. Self-transfers between your own wallets net to zero rather than creating phantom gains, wallet balances are reconciled to the chain before anything posts, and the period locks so late edits do not silently change a closed month. The result is a close you can repeat the same way every period and explain to anyone who asks.

Controls and the audit trail

Auditability is the reason to use a sub-ledger at all. Every summarized line that reaches QuickBooks traces to the exact disposals, receipts and fees that produced it, and each of those ties to an on-chain transaction hash or an exchange record. That unbroken chain — financial statement to journal entry to lot to transaction to blockchain — is what an auditor expects to walk, and it is built into the way CryptaCount records activity rather than reconstructed after the fact. Cost-basis method, measurement policy and classification decisions are applied consistently and recorded, so the figures can be reproduced. For how this supports your reporting obligations, see crypto compliance reporting →.

Multi-entity and multi-currency considerations

Many crypto-active businesses run more than one entity, and report in a currency that is not the U.S. dollar. CryptaCount values transactions at the time they occur and can present results in your functional or presentation currency, so the entries posted to QuickBooks already reflect the period-end position you need rather than raw token quantities. Where you operate several QuickBooks companies, you keep a sub-ledger scope per entity and map each to its own chart of accounts, so intercompany crypto movements stay clean and consolidation is not muddied by mismatched bases or double-counted transfers. Measurement under IFRS or US GAAP is applied in the sub-ledger according to your policy — see IFRS crypto accounting →.

Common pitfalls this design avoids

• Importing raw transactions into the GL — bloats QuickBooks and makes reports unusable; the sub-ledger posts summaries instead
• Lost cost basis on transfers in — coins moved from another platform with no basis attached distort every later gain; CryptaCount carries basis with the asset
• Self-transfers booked as sales — moving funds between your own wallets should never create a taxable disposal or a phantom gain
• Inconsistent cost-basis methods — switching method mid-period produces results no one can reconcile; the engine applies your chosen method consistently
• Manual spreadsheets at close — error-prone and unauditable; a reconciled sub-ledger replaces the spreadsheet entirely
• Fees buried in trade lines — network and exchange fees mixed into proceeds hide real trading costs; CryptaCount separates them

How CryptaCount will work with QuickBooks

In short: CryptaCount does the crypto-specific heavy lifting — ingestion, cost basis, classification and reconciliation — and hands QuickBooks Online exactly what a general ledger should receive, which is a clean set of period journal entries mapped to your accounts. Today you can run the full sub-ledger and export those summarized entries to import into QuickBooks; when the direct connector ships it will post them for you, with the same drill-down behind every line. Either way, QuickBooks stays the system of record and the transaction detail stays where it can be reconciled and audited. Explore the crypto sub-ledger → and journal entries → to see the engine in detail.

Can we keep our existing QuickBooks bank feeds and invoicing?

Yes. The sub-ledger only adds crypto journal entries to your GL; it does not touch your bank feeds, invoices, bills or any other QuickBooks workflow. Those continue exactly as they do now, and the crypto postings sit alongside them mapped to the accounts you choose.

How often will entries post to QuickBooks?

At whatever frequency your close runs — typically monthly or quarterly. You set the posting cadence to match your accounting periods so each period's crypto activity is summarized and posted as one tidy set of entries rather than a constant trickle.

What happens if we restate or reclassify a prior period?

Because every posted line traces back to its source transactions, a reclassification is transparent: you can see precisely which transactions changed and what the revised summary looks like. The sub-ledger keeps the history, so prior-period adjustments are auditable rather than a mystery overwrite in the GL.

Do we need accounting expertise to set up the mapping?

You need to know your own chart of accounts, which any team using QuickBooks already does. The mapping aligns crypto event types — holdings, gains and losses, income, fees — to the GL accounts you nominate. It is configured once and reused, and most teams have it set up in a single sitting.