The crypto sub-ledger built for accurate books

Underneath every CryptaCount report is a purpose-built crypto sub-ledger: it records each transaction at source, applies the right cost basis, and posts balanced double-entry journals you can reconcile, report, and audit — then feeds the summary into your general ledger.

What a crypto sub-ledger actually does

Your general ledger is the system of record. It was never designed to hold thousands of token transfers, swaps, gas fees, and staking events — let alone track cost basis across them. A crypto sub-ledger fills that gap. It captures the full detail of on-chain and exchange activity, does the crypto-specific accounting, and hands your GL clean, summarised journals.

That's the line between CryptaCount and a portfolio tracker. A tracker tells you what a wallet is worth. A sub-ledger gives you the debits and credits — cost-basis-accurate gain/loss, an audit trail, and reconciliations that prove the numbers are complete.

Cost basis, done to the standard

Cost basis is where most crypto accounting goes wrong. CryptaCount tracks it at the lot level and lets you apply the method your jurisdiction or policy requires: 12 disposal methods including FIFO, LIFO, HIFO, WAVG, and Specific Identification — selectable per entity, across 70+ jurisdictions.

Your chosen method applies consistently; jurisdiction-mandated treatments such as UK Section 104 pooling and Canada ACB apply automatically, so a mixed-jurisdiction group is handled correctly without manual workarounds.

Change of method, mixed jurisdictions across a group, or a specific-ID disposal for tax-lot optimisation — all handled in the ledger, not in a spreadsheet on the side. How each cost-basis method works →

Double-entry with an audit trail you can defend

Every event CryptaCount records becomes a balanced journal entry with a tamper-evident, hashed audit trail. Nothing is a free-floating number. When an auditor asks how a balance was derived, the answer is a traceable chain of postings back to the on-chain transaction — not a manual reconstruction.

Built for groups, not just single wallets

Multi-wallet, multi-entity. Consolidate hundreds of wallets across multiple legal entities into one set of books, with per-entity method and jurisdiction settings and a consolidated view on top.

Realised & unrealised gain/loss. Gain/loss computed from actual cost basis — realised on disposal, unrealised at fair value where the standard requires it — not an estimated P&L.

DeFi and NFTs as real records

DeFi and NFT activity is where manual crypto accounting collapses. CryptaCount captures it as proper accounting events:

• DeFi: liquidity provision, lending, borrowing, staking, rewards, and wrapping — classified and posted, not left as raw transfers.
• NFTs: mints, purchases, sales, and royalties recorded with cost basis and gain/loss.

Reconciliation that proves completeness

A sub-ledger is only as good as its reconciliation. CryptaCount ties three sources together — on-chain activity ↔ exchange records ↔ your general ledger — so you can demonstrate completeness and accuracy rather than assert it. Gaps and mismatches surface before close, not during audit.

Feeds the GL you already run

Reconciled journals sync to your accounting system — Xero and Zoho are live today, with QuickBooks, NetSuite, and Sage on the roadmap. The sub-ledger does the crypto work; your existing accounting system stays the system of record. Exchange, wallet & ERP integrations →

Why CryptaCount

• Native chain data — transaction detail read from our own on-chain data infrastructure, not rented from third-party APIs, so DeFi and internal transfers are captured more completely and traced to source.
• Accounting-first — built by an FCCA-qualified team around double-entry and controls, not a tracker with an export button bolted on.
• 12 methods, 70+ jurisdictions — the ledger bends to your policy and local rules, not the other way round.

Explore further: Crypto compliance & reporting → · Accounting for firms →

The full picture: where a sub-ledger sits in your finance stack

To see why a crypto sub-ledger matters, it helps to look at the whole stack rather than one screen. At the bottom sit the raw sources — exchange accounts, custodial venues and on-chain wallets, each emitting a different shape of data. In the middle sits the sub-ledger, the layer that turns those raw movements into accounting: it identifies each event, assigns a cost basis, and produces balanced double-entry postings. At the top sits your general ledger, where the summarised journals land and the financial statements are produced. CryptaCount occupies that middle layer deliberately, because it is the layer that off-the-shelf accounting systems and portfolio trackers both leave empty. If you want the long-form definition, the what is a crypto sub-ledger → page walks through it from first principles.

The reason the middle layer exists is that crypto breaks the assumptions a general ledger was built on. A GL expects a manageable number of transactions, each already classified and already denominated in your reporting currency. On-chain activity arrives as the opposite: thousands of transfers, swaps, gas charges, staking receipts and contract interactions, none of them labelled and none of them carrying a basis. A sub-ledger absorbs that volume and complexity so the GL never has to. The pieces fit together as a pipeline — ingestion, classification, cost-basis engine, reconciliation, then posting — and the value comes from every stage feeding the next without a spreadsheet in between.

Who actually needs one

A crypto sub-ledger is not for everyone who holds a token. It earns its place the moment crypto stops being a rounding error and starts being something an auditor, a tax authority or a board will ask about. In practice that means a fairly specific set of finance teams:

• Accounting and audit firms carrying crypto-active clients who need defensible books rather than a tracker screenshot — see crypto accounting for firms →
• Funds, trading desks and treasuries with high transaction counts where realised and unrealised gain/loss has to be measured, not estimated
• Web3 and token-issuing companies holding treasury assets, paying contributors in crypto, and earning protocol or staking income that must be classified
• Multi-entity groups consolidating wallets across several legal entities and jurisdictions into one set of books
• Corporates with a crypto balance-sheet position that has grown large enough to require formal measurement under a reporting standard

What unites them is that the answer to "how was this balance derived?" has to be evidence, not assertion. The moment that question is foreseeable, a sub-ledger stops being optional.

The workflow, end to end

The day-to-day rhythm of running CryptaCount as your sub-ledger follows the same sequence every period, which is precisely what makes a crypto close repeatable instead of a research project. First, ingest: activity is pulled from every connected exchange and wallet at transaction level. Second, classify: each event is identified as an acquisition, a disposal, an internal transfer, an income receipt, a fee or a revaluation, with anything ambiguous flagged for a human decision rather than silently guessed. Third, apply cost basis: your chosen method runs across every lot to measure the result of each disposal. Fourth, reconcile: on-chain balances are tied to exchange records and to the GL so nothing is missing or double-counted. Fifth, post: summarised, balanced journals are generated and synced up to your accounting system, each line drilling back to its source.

Two stages deserve emphasis because they are where manual processes fail. The cost-basis stage is unforgiving — a single mis-tracked transfer poisons every later gain — which is why CryptaCount carries basis with the asset and applies your method consistently rather than re-deriving it each period. The reconciliation stage is what proves completeness: it is the difference between believing the books are right and being able to demonstrate it. Together they turn the close from a defensive exercise into a controlled one. The journal entries → page shows exactly how the postings are assembled.

Built for groups, not single wallets

A single wallet is easy; a group is where crypto accounting becomes hard, and where a sub-ledger stops being a convenience and becomes a control. CryptaCount is multi-wallet and multi-entity by design: hundreds of wallets across several legal entities consolidate into one set of books, each entity keeping its own cost-basis method and jurisdiction settings while a consolidated view sits on top. That matters because gain/loss has to be computed from actual lot-level cost basis — realised on disposal, and unrealised at fair value where the standard requires it — rather than estimated as a portfolio P&L. Intercompany movements between wallets you control are recognised as internal transfers, not disposals, so they never create phantom gains that pollute consolidation. The same engine that handles one wallet handles the whole group, which is why adding an entity, an exchange or a token flows into the existing structure instead of triggering a rebuild.

A buyer's guide: what to evaluate before you commit

Crypto accounting tools look similar in a demo and behave very differently at close. If you are comparing options, the questions that actually separate them are about depth and defensibility, not feature counts:

• Is it double-entry, or a tracker with an export? A real sub-ledger posts balanced debits and credits; a tracker reports a number you still have to journal yourself
• How many cost-basis methods, and can they vary per entity? Mixed-jurisdiction groups need method selection at the entity level — review the cost-basis methods → in detail
• Does jurisdiction-mandated treatment apply automatically? Pooling rules and averaged-basis regimes should not be manual workarounds
• Where does the chain data come from? Native infrastructure captures internal transfers, gas and DeFi more completely than a rented third-party API
• Can it reconcile three sources? On-chain, exchange and GL reconciliation is what evidences completeness — a tool that only ingests one source cannot
• Does every figure trace to source? A hashed, tamper-evident audit trail back to the transaction is the dividing line at audit
• Will it scale to many wallets and entities? Consolidation should be native, not a second spreadsheet on top

Scoring candidates against that list, rather than against a feature grid, tends to collapse a long shortlist quickly. Most tools answer the first two questions well and the rest poorly.

Common pitfalls a proper sub-ledger removes

• Cost basis lost on transfers in — assets moved from another platform with no basis attached distort every later gain; basis must travel with the asset
• Self-transfers booked as disposals — moving funds between your own wallets should never create a taxable sale or a phantom gain
• Method drift — switching cost-basis method part-way through a period produces results no one can reconcile
• Gas and fees buried in trade lines — netting network and exchange fees into proceeds hides real costs and distorts the gain
• Unclassified DeFi left as raw transfers — liquidity, lending and wrapping events that are never classified become reconciliation gaps at year-end
• Spreadsheet closes — error-prone, unversioned and unauditable; a reconciled sub-ledger replaces the spreadsheet entirely

How CryptaCount delivers this

CryptaCount was built as a sub-ledger first, not a tracker with accounting bolted on afterwards. It reads chain activity through our own on-chain data infrastructure rather than renting it, so internal transfers and DeFi are captured more completely and traced to source. It applies any of 12 disposal methods across 70+ jurisdictions at the entity level, with mandated treatments such as UK Section 104 pooling and Canada ACB applied automatically. It reconciles on-chain, exchange and GL data before anything posts, and it hands your existing accounting system clean, summarised journals with a hashed audit trail behind every line. The result is books you can defend rather than reconstruct. Explore further: crypto compliance & reporting → · exchange, wallet & ERP integrations → · crypto accounting by asset →.

Do we replace our general ledger with CryptaCount?

No. Your GL stays the system of record. CryptaCount sits in front of it as the crypto sub-ledger, absorbing the volume and complexity of on-chain and exchange activity and feeding the GL clean, summarised journals. The two systems do different jobs, and keeping that division is what makes both trustworthy.

How granular is the audit trail?

Every balance traces through balanced journal entries to the lots that produced it, and each lot ties back to an on-chain transaction hash or an exchange record. The trail is hashed and tamper-evident, so a reviewer can walk from the financial statement all the way to the blockchain without a manual reconstruction in the middle.

Can different entities in our group use different cost-basis methods?

Yes. Method is selected per entity, so a group spanning several jurisdictions can run the method each entity's policy or local rules require, while jurisdiction-mandated treatments apply automatically. A consolidated view sits on top, so the group reports as one without forcing a single method everywhere. The cost-basis methods → page covers each option.

How does the sub-ledger prove nothing is missing?

Through three-way reconciliation. CryptaCount ties on-chain activity to exchange records and to your general ledger, so gaps and mismatches surface before close rather than during audit. That is the practical difference between asserting completeness and demonstrating it.

What happens to DeFi and NFT activity that other tools ignore?

It is captured as real accounting events. Liquidity provision, lending, borrowing, staking, rewards and wrapping are classified and posted rather than left as raw transfers, and NFT mints, purchases, sales and royalties are recorded with cost basis and gain/loss. This is usually where manual crypto accounting collapses, and where a purpose-built sub-ledger earns its keep.