Wave crypto accounting

Wave crypto accounting brings crypto into the free books many freelancers and small businesses run on, without the chaos of raw exchange data. CryptaCount acts as the crypto sub-ledger in front of Wave: it ingests your exchange and on-chain activity, calculates cost basis and gains, and produces clean summarized journal entries you post to Wave — with the detail kept in the sub-ledger.

How crypto accounting for Wave works

Wave is your books; it was not built to reconcile wallets and token cost basis across thousands of transactions. CryptaCount sits in front of it as the crypto sub-ledger: it ingests your on-chain and exchange activity, calculates cost basis and gains under your measurement policy, and produces clean, summarized double-entry journal entries mapped to your chart of accounts — ready to post to Wave, with the transaction-level detail kept in the sub-ledger.

Getting CryptaCount's journals into Wave

CryptaCount produces summarized, double-entry crypto journals that you bring into Wave and post to your accounts. Mapped to your Wave chart, they keep the crypto side of the books tidy, so a small business's return rests on a reconciled record rather than a stack of exchange exports.

1. Map your crypto accounts — assign digital assets, realized gain/loss, income (staking, mining, rewards) and fees to the right accounts in your Wave chart.
2. Set your posting frequency — per period (monthly, quarterly) rather than per transaction.
3. Post the journals — bring the summarized entries into Wave, each backed by full sub-ledger detail.

What reaches your books

• Summarized period journals — double-entry, per period, not thousands of raw lines
• Mapped to your Wave chart of accounts — digital assets, realized gain/loss, income and fees
• Drill-down — every posted line traces to the underlying transactions in the sub-ledger

Why finance teams use it

• Cost basis at scale — 12 disposal methods (FIFO, LIFO, HIFO, WAVG, Specific ID, and more); jurisdiction-mandated treatments (UK Section 104 pooling, Canada ACB) apply automatically
• A clean close — summarized journals instead of thousands of raw lines
• Audit-ready — a traceable trail from each Wave journal line 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 →

Crypto for a free, small-business ledger

Wave is popular precisely because it gives freelancers and small businesses solid bookkeeping for free, but like any general ledger it was not built to reconcile wallets or calculate token cost basis. As soon as a Wave user touches crypto — accepting it in payment, holding it on the balance sheet, earning rewards — the crypto side needs a layer Wave does not provide. CryptaCount is that layer: it does the crypto-specific work and hands Wave clean summarized journals to post, so the books stay simple and correct.

The fit is natural for a lean operation: you do not need an enterprise ERP to account for crypto properly, you need a reconciled sub-ledger that produces period journals your Wave books can absorb. CryptaCount keeps the transaction detail and the audit trail, while Wave shows the clean summarized result — the same division of labour a large firm uses, sized for a small business.

From exchange data to postable journals

The hardest part of putting crypto into Wave by hand is turning raw exchange and on-chain data into something a simple ledger can use. CryptaCount does that translation: it ingests the activity, classifies each event, calculates gains under a consistent cost-basis method, matches self-transfers so they are not booked as sales, and outputs summarized journals mapped to your Wave accounts. What reaches Wave is a handful of clean lines per period, each traceable back to the underlying transactions.

Crypto on a small-business balance sheet

If your small business holds crypto rather than just transacting it, the holding sits on your balance sheet and its treatment follows your measurement policy — held at cost or revalued, with any impairment recognised as your policy and the applicable standards require. Wave records the resulting balances and movements, but the underlying cost basis and the events that change it live in the sub-ledger. CryptaCount keeps that detail and posts the periodic result to Wave, so a crypto holding is accounted for deliberately rather than left as an unexplained figure on the books.

Because what lands in Wave is summarised, your reports stay readable and your close stays fast even when the underlying month held thousands of crypto events — and nothing is lost, because the detail behind every line is preserved in the sub-ledger and one click away when you need to explain or reconcile a figure.

What the integration does and does not do

A clean division of labour between the sub-ledger and Wave is what makes both trustworthy, so it is worth being explicit about the boundary: CryptaCount is the crypto sub-ledger and a posting bridge, not a second set of books.

What it does: ingests activity from your exchanges and wallets, calculates cost basis and realised results under your policy, summarises each period into double-entry journals mapped to your Wave accounts, and gives you full drill-down to the source transactions. What it does not do: it does not push thousands of raw lines into your ledger, does not interfere with your existing Wave bookkeeping, and does not make accounting-policy decisions for you. Measurement, classification and method selection stay under your control in the sub-ledger; Wave remains the system of record for the financial statements.

That boundary is what keeps the crypto numbers defensible: because policy choices live in the sub-ledger and are applied consistently, any figure posted to Wave can be reproduced and explained on request, and a revised period is transparent rather than a silent overwrite.

Keeping crypto in step with the rest of Wave

Crypto should not be the one part of the business that reports differently from everything else. Because the journals are mapped to your Wave chart of accounts — and, where Wave supports classes, departments or projects, can carry those tags too — your digital-asset holdings, realised gains, income and fees roll up through the same structure as the rest of your numbers. Add an exchange, a wallet or a new token and it flows into that same structure with no rebuild, so the crypto side scales with the business rather than becoming a parallel system someone maintains by hand.

The payoff is operational as much as it is about correctness: your team spends its time on decisions — resolving exceptions, choosing policy — rather than wrangling exchange exports into Wave. The mechanical work of ingestion, cost basis, reconciliation and posting is automated, leaving you a clean Wave ledger and a crypto record that stands up to audit.

Why the sub-ledger posts summaries, not every transaction

Wave is superb at your day-to-day books, but it was never meant to hold tens of thousands of token movements with individual cost-basis lots behind them. Rather than firehosing raw transactions into Wave, CryptaCount posts summarized journals per period — the net effect of the period's activity on each account. A busy month can produce thousands of events; posting each one would make Wave unreadable and bury the figures that actually matter to the financial statements.

The principle is the same one finance teams already apply to payroll or a payments processor: the operational system keeps the line-by-line detail, and only the summarized debits and credits reach the general ledger. Each posted line in Wave still drills back to the exact underlying transactions, so you keep a clean ledger and a complete, reconcilable record at the same time. See journal entries →.

Mapping crypto to your Wave chart of accounts

You assign each kind of crypto activity to a Wave account — holdings to asset accounts, disposals to realized gain/loss, staking and reward income to a revenue or other-income account, and network and exchange fees to expense accounts. Set the mapping once and it is reused every period, so the journals stay consistent close after close. Add an exchange, wallet or token and it flows into the same structure with no rebuild.

• Digital asset accounts — combined, 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 separate from trading results

The close and reconciliation workflow

With CryptaCount feeding Wave, the close follows a steady rhythm. CryptaCount ingests the period's transactions from every connected exchange and wallet and flags whatever needs a decision — an unknown counterparty, an unrecognized token, or a transfer that might be an internal move rather than a disposal. You resolve those exceptions, confirm that on-chain balances reconcile to the sub-ledger, review the cost-basis results, then generate the period journals and post them to Wave.

Reviewing at the Wave end is quick because the journals are summarized: a handful of lines per account, each backed by a full transaction list you can open on demand. Self-transfers between your own wallets net to zero instead of creating phantom gains, balances reconcile to the chain before anything posts, and a closed period stays closed. It is a process you can run the same way every month and hand to a reviewer.

Controls and the audit trail

Every summarized journal line in Wave traces to the precise disposals, receipts and fees that produced it, and each of those ties to a transaction hash or an exchange record. That unbroken chain — financial statement to journal to lot to transaction to blockchain — is exactly what an auditor walks, and it is recorded as you go rather than rebuilt at year-end. Cost-basis method, measurement policy and classification are applied consistently and retained, so any figure can be reproduced on request. See crypto compliance reporting →.

Multi-entity and multi-currency

If you run several Wave entities, 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 distorted by mismatched bases or double-counted transfers. CryptaCount values transactions when they occur and can present results in your functional or presentation currency, so the journals posted to Wave reflect the position you report rather than raw token quantities. Measurement under IFRS or US GAAP is applied in the sub-ledger per your policy.

Common pitfalls when posting crypto to Wave

• Raw transactions in the GL — bloats Wave and makes reports unusable; post summarized journals instead.
• Lost cost basis on transfers in — coins arriving from another platform with no basis distort every later gain.
• Self-transfers booked as sales — moving funds between your own wallets should never create a disposal.
• Inconsistent cost-basis methods — switching method mid-period produces results no one can reconcile.
• Spreadsheet closes — error-prone and unauditable; a reconciled sub-ledger replaces the spreadsheet.

How CryptaCount works with Wave

CryptaCount does the crypto-specific work — ingestion, cost basis, classification and reconciliation — then hands Wave what a general ledger should receive: clean summarized journal entries mapped to your accounts, with full drill-down behind every line. Wave stays the system of record; the transaction detail stays where it can be reconciled and audited. To see how it would fit your Wave setup, our team can walk through it with you.