What is a crypto sub-ledger?

A crypto sub-ledger is a subsidiary ledger that holds the transaction-level detail of your crypto activity, calculates cost basis and gains, and posts summarized journal entries to your general ledger. It's the same idea as an accounts-receivable or fixed-asset sub-ledger — a specialised system that does the detailed work, then feeds your books clean.

Why crypto needs its own sub-ledger

General ledgers and ERPs were never built to track wallets, tokens, and cost basis across thousands of on-chain and exchange transactions. Trying to do it directly clutters the GL with raw activity, breaks down on cost basis, and leaves no defensible trail. A sub-ledger solves that by sitting in front of the GL:

1. It ingests every transaction from your exchanges and wallets,
2. classifies each one and calculates cost basis and realized gains,
3. summarizes the activity into journal entries, and
4. posts those entries to your general ledger.

Your GL stays the system of record; the detail lives in the sub-ledger, where you can drill into any figure.

Sub-ledger vs general ledger

• The general ledger holds your summarized financial position — it's the system of record your statements come from.
• The sub-ledger holds the granular detail behind specific accounts (here, crypto), and reconciles up to the GL.

So a crypto sub-ledger doesn't replace your accounting system — it makes it possible to account for crypto properly, with every GL line traceable back to the underlying transaction. Crypto sub-ledger vs portfolio tracker →

What a crypto sub-ledger does

• Ingestion — every exchange and wallet, into one place
• Classification — trades, transfers, income, fees, DeFi, NFTs
• Cost basis — multiple methods, with jurisdiction-correct treatment → Cost-basis methods →
• Journal entries — summarized, double-entry, posted to your ERP → ERP integrations →
• Reconciliation & audit trail — every figure traceable to source

CryptaCount is a crypto sub-ledger

That's exactly what CryptaCount is built to be: the crypto sub-ledger that turns on-chain and exchange activity into accounting-grade records and posts them to QuickBooks, Xero, NetSuite, or Sage — with the transaction-level detail retained behind every line.

See the sub-ledger → · Accounting for firms →

Where the sub-ledger sits in your accounting stack

It helps to picture the sub-ledger as a layer that sits between your raw crypto activity and your general ledger. On one side are the exchanges and wallets generating thousands of trades, transfers, fees and rewards. On the other side is the GL or ERP that produces your financial statements and is the system of record your auditors rely on. Left to meet directly, those two worlds do not fit: the GL has no concept of an acquisition lot, a cost-basis method, or an on-chain transfer hash, and was never designed to carry the line-by-line detail crypto throws off. The sub-ledger is the translation layer in the middle. It absorbs the operational detail, turns it into accounting-grade records, and hands the GL only the summarized double-entry postings it actually needs. The pattern is the same one mature finance teams already use for payroll, inventory or a high-volume payments processor — the operational system holds the granular record, and only the net effect on each account reaches the GL. See the full engine on the crypto sub-ledger → page.

What the sub-ledger actually records

A general ledger records balances; a sub-ledger records events. For crypto, that means every economic action that has to be measured and eventually posted, captured at the level of the individual transaction so nothing is lost on the way to the books:

• Acquisitions — each buy or inbound receipt recorded as a distinct lot, with its date, quantity and cost, so cost basis can be calculated later.
• Disposals — sales and outbound spends measured against the cost basis of the lots consumed, producing a realized gain or loss.
• Transfers between your own wallets — recorded as movements, not sales, so they never create a phantom gain.
• Income events — staking, mining, rewards and airdrops recognized at value on receipt and kept separate from trading results.
• Fees — network (gas) and exchange fees captured in their own right rather than buried in proceeds.
• Revaluations and impairment — the period-end adjustments your reporting framework requires on the assets you still hold.

Each of these carries its full lineage — the wallet or exchange it came from, the on-chain or venue reference, the classification, and the basis on which it was measured. That lineage is what makes the sub-ledger an accounting record rather than a feed: every figure can be drilled back to the transaction that produced it.

Why a general ledger alone is not enough for crypto

Teams new to crypto accounting often try to handle it directly in the GL or ERP, and it almost always breaks down for the same reasons. First, volume: a single active trading week can generate thousands of on-chain events, and pushing each one into the GL bloats the trial balance, slows every report, and makes the books unreadable without adding any accounting value, because the GL only needs the net effect on each account. Second, cost basis: a GL has no native concept of acquisition lots or a disposal-ordering method, so it cannot compute a realized gain — the most important crypto number — on its own. Third, classification: the GL cannot tell a self-transfer from a sale, an airdrop from a purchase, or a fee from proceeds, yet those distinctions decide whether a gain even exists. Fourth, traceability: even if you forced the numbers in by hand, you would have no defensible trail linking each GL line back to the underlying wallet activity — the first thing an auditor asks for. The sub-ledger exists precisely to solve all four before anything reaches your books.

The journal-entry flow, step by step

The value of the sub-ledger is clearest in how a period's raw activity becomes a clean set of journal entries. The flow is deliberately ordered, so each step builds on a verified one before it:

• 1. Ingest. Every transaction is pulled from each connected exchange and wallet into one place, deduplicated so the same on-chain event is never counted twice.
• 2. Classify. Each transaction is identified — trade, transfer, income, fee, DeFi interaction, NFT — because the classification decides how it is measured and posted.
• 3. Measure. Disposals are valued against cost basis under your chosen method; income is recognized at value on receipt; fees are isolated.
• 4. Summarize. The period's measured events are aggregated into double-entry journal entries — net movements in digital assets, realized gain or loss, income and fees — rather than a line for every transfer.
• 5. Post. Those summarized entries are mapped to your chart of accounts and posted to the GL, with each line retaining drill-down to the source transactions behind it.

The result is a GL that stays clean and a sub-ledger that keeps the complete record — not a trade-off between the two. See exactly how the postings are assembled on the journal entries → page, and how cost basis is calculated on the cost-basis methods → page.

Common pitfalls without a real sub-ledger

• Spreadsheets that drift. Hand-built workbooks lose deduplication, formula integrity and version control the moment volume rises, and there is no audit trail behind the totals.
• Self-transfers booked as sales. Without proper classification, moving assets between your own wallets invents realized gains that never occurred.
• Double-counted events. The same on-chain transaction can appear in both an exchange export and a wallet feed; without dedup it is counted twice.
• Cost basis recomputed each quarter. Re-deriving basis by hand every close is slow and error-prone, and rarely reconciles to the prior period.
• No drill-down. A GL figure with nothing behind it cannot be defended in audit; the evidence has to live somewhere, and the sub-ledger is where.
• Standards measured ad hoc. Impairment or fair-value adjustments applied inconsistently produce a balance sheet that does not tie out.

How CryptaCount works as your crypto sub-ledger

CryptaCount is built to be exactly this layer. It ingests activity from every exchange and wallet you connect, deduplicates and classifies each transaction, calculates cost basis under the method your accounting policy specifies, and summarizes the period into double-entry journal entries mapped to your chart of accounts. Those entries post to your general ledger or ERP, while the transaction-level detail stays retained behind every line, so any figure can be drilled straight back to its source. The carrying basis it produces feeds measurement under your reporting framework, whether you report under IFRS → or US GAAP →. Your GL stays the system of record and stays clean; the sub-ledger carries the detail and the audit trail. That division of labor is what makes it possible to account for crypto properly — at the scale a real business actually operates at.

More questions about crypto sub-ledgers

Is a crypto sub-ledger the same as a wallet or an exchange export?

No. A wallet or exchange export is raw activity — a list of transactions with no cost basis, no classification and no double-entry structure. A sub-ledger consumes those exports, deduplicates and classifies them, calculates basis and gains, and turns them into accounting-grade journal entries. The export is an input; the sub-ledger is the system that makes it into a record your books can rely on.

Does the sub-ledger replace my accountant?

No — it equips them. The accountant still owns the accounting policy: which cost-basis method to use, how to classify edge cases, how to measure holdings under the reporting framework. The sub-ledger does the heavy, repetitive work of ingesting, deduplicating, calculating and summarizing thousands of transactions consistently, then hands the accountant clean, traceable entries to review and post. It removes the manual grind, not the professional judgment.

How does the sub-ledger keep the general ledger clean?

By posting summaries rather than raw lines. Instead of pushing every transfer, swap, fee and reward into the GL, the sub-ledger aggregates a period's activity into a small number of double-entry journal entries that capture the net effect on each account. The GL gets a tidy, readable trial balance; the detailed line-by-line record stays in the sub-ledger, where each summarized line still drills back to the underlying transactions.

Can a sub-ledger handle multiple entities and currencies?

That is one of the reasons businesses adopt one. Real organizations hold crypto across several entities, wallets and exchanges, often in different presentation currencies, and they need those records to consolidate cleanly. A sub-ledger keeps each entity's detail separate and consistent while feeding summarized, properly mapped entries up to the GL — something a spreadsheet or a single-account tracker cannot do reliably at scale. Because the mapping and the cost-basis policy are set once and reused, a new entity, wallet or token flows into the same structure without a rebuild, and the consolidated picture stays coherent close after close.

When in the growth of a crypto business should a sub-ledger go in?

Earlier than most teams expect. The pain of retrofitting accounting onto crypto rises sharply with transaction volume and with the number of wallets, exchanges and tokens involved, and reconstructing cost basis and classification after the fact is far harder than capturing it as it happens. The practical trigger is the first period in which crypto has to appear in real financial statements, support an audit, or be reported across more than one entity. At that point a sub-ledger stops being optional, because the GL alone cannot produce the realized gains, the classification, or the audit trail that the books now depend on. Putting the layer in before volume climbs means every transaction is recorded cleanly from the start, rather than untangled under deadline at close.