Crypto sub-ledger vs portfolio tracker

They can look similar — both pull in your crypto activity and show numbers. But a portfolio tracker is built to show you balances and performance, while a crypto sub-ledger is built to produce accounting-grade records your books and auditors can rely on. For a business, that difference is everything.

What a portfolio tracker does

A tracker aggregates your holdings and shows balances, prices, and unrealized gains — useful for keeping an eye on a portfolio. It's designed for insight, typically for an individual investor, not for producing financial statements.

What a crypto sub-ledger does

A sub-ledger is designed for accounting. It doesn't just show numbers — it produces double-entry records, applies cost basis, posts journal entries to your general ledger, and keeps a defensible trail for audit. What is a crypto sub-ledger? →

The difference, side by side

A sub-ledger has what a tracker doesn't:

• Double-entry accounting — not just a balance, but proper debits and credits
• Journal entries to your ERP — posts to QuickBooks, Xero, NetSuite, or Sage → ERP integrations →
• Multiple cost-basis methods, jurisdiction-correct — the right treatment for where you file → Cost-basis methods →
• Standards support — measurement under IFRS or US GAAP, with impairment and fair value → Compliance & reporting →
• Audit trail — every figure traceable to the source transaction
• Period close and multi-entity — built for real accounting workflows

Why it matters for a business

A tracker can tell you roughly how your holdings are doing. It can't give your accountant a set of books, give your auditor evidence, or produce the numbers for a tax return or financial statements. The moment crypto has to appear in real accounting — for a company, a fund, or a firm's clients — a tracker isn't enough. That's the gap a sub-ledger fills.

CryptaCount is a sub-ledger, not a tracker

CryptaCount is built as a crypto sub-ledger: accounting-grade records, cost basis, journal entries to your ERP, and an audit trail — for finance teams, firms, funds, and the businesses that need their crypto on the books, not just on a dashboard.

See the sub-ledger → · Accounting for firms →

The accounting gap a portfolio tracker leaves

A portfolio tracker answers one question well: how is my crypto doing right now? It pulls in balances, marks them to current prices, and shows unrealized gains on a dashboard. That is genuinely useful for monitoring — but it is insight, not accounting, and the difference is structural, not cosmetic. A tracker never produces a debit and a credit. It does not apply a cost-basis method to a disposal, does not post a journal entry, does not distinguish a self-transfer from a sale, and does not retain a defensible trail behind its numbers. None of that is a flaw in a tracker — it was simply never built to feed a set of books. The problem appears the moment crypto has to show up in real accounting: on a company's balance sheet, in a fund's NAV, or in a firm's client engagement. At that point the tracker's headline number is unusable, because there is nothing underneath it an accountant or auditor can stand on. That missing layer — the bridge from raw activity to accounting-grade records — is precisely what the crypto sub-ledger provides. See the engine on the crypto sub-ledger → page.

What 'accounting-grade' actually requires

It is worth being precise about what a tracker is missing, because each item is something a business cannot do without once crypto is on the books:

• Double-entry records. Every event has to post balanced debits and credits, not just update a single balance. A tracker shows a number; the books need a movement on two accounts.
• Cost basis applied consistently. Disposals must be measured against a chosen method, the same way across every venue, so realized gains are comparable period to period.
• Journal entries mapped to a chart of accounts. The output has to land in the right GL accounts — digital assets, realized gain/loss, income, fees — not float on a dashboard.
• Classification. Trades, transfers, income, fees, DeFi and NFTs each have to be identified, because the classification decides whether a gain even exists.
• An audit trail. Every figure has to drill back to the source transaction. Evidence, not assertion, is what an auditor signs off on.
• Period close and multi-entity support. Real accounting runs on monthly or quarterly closes across several entities — workflows a performance view has no concept of.

A tracker delivers none of these because none of them serve its purpose. A sub-ledger delivers all of them because they are its purpose. That is the whole distinction in one line.

Controls and reconciliation: the part trackers skip

The deepest difference is in controls. Accounting is not just about producing a number; it is about being able to demonstrate that the number is complete, accurate and unchanged. That demands controls a tracker has no reason to implement. Completeness means every wallet and exchange is connected and every transaction is captured, with no silent gaps. Accuracy means each transaction is deduplicated — the same on-chain event arriving from both an exchange export and a wallet feed must be counted once, not twice — classified correctly, and measured on a consistent basis. Integrity means the record is tamper-evident, so a posted figure cannot be quietly altered after the fact. And reconciliation ties it all together: the sub-ledger's holdings must agree to the on-chain and exchange balances they represent, and the summarized entries must reconcile up to the general ledger they post into. A tracker simply displays whatever the feeds report; it has no mechanism to prove completeness, no dedup discipline you can rely on for books, and no reconciliation back to a GL — because it has no GL to reconcile to. Those controls are not a nice-to-have for a business; they are the difference between books that pass review and books that do not.

Where the two tools genuinely differ — a side-by-side

• Purpose — tracker: monitor performance; sub-ledger: produce accounting records.
• Primary user — tracker: an investor watching a portfolio; sub-ledger: a finance team, fund or accounting firm closing the books.
• Output — tracker: balances and unrealized gains on a screen; sub-ledger: double-entry journal entries posted to a GL.
• Cost basis — tracker: an approximate performance figure; sub-ledger: a method-driven, jurisdiction-correct realized result.
• Audit — tracker: nothing to hand an auditor; sub-ledger: a full trail from every figure back to its source transaction.
• Standards — tracker: none; sub-ledger: measurement aligned to IFRS → or US GAAP →.

Common mistakes when a tracker is used as if it were accounting

• Reading unrealized gains as income. A tracker's headline gain is a mark-to-market view, not a realized result your income statement can recognize.
• Trusting balances that were never reconciled. A displayed balance is only as good as the feeds behind it; without reconciliation to a GL it can be wrong and never flagged.
• Double-counting cross-feed transactions. The same event from an exchange and a wallet inflates totals when there is no dedup you can depend on.
• Booking self-transfers as taxable disposals. A tracker that cannot classify a movement between your own wallets will misrepresent it as a sale.
• Exporting a dashboard into the GL. Pasting tracker numbers into the books with no journal structure and no drill-down leaves figures an auditor cannot test.
• Assuming a performance tool is audit-ready. It never was; the controls that make a record defensible are exactly what a tracker omits.

How CryptaCount closes the gap

CryptaCount is built as a sub-ledger, not a tracker. It ingests activity from every exchange and wallet you connect, deduplicates and classifies each transaction, applies the cost-basis method your accounting policy requires, and produces double-entry journal entries mapped to your chart of accounts and posted to your general ledger. Behind every figure it retains the source transactions, giving you a tamper-evident trail your auditors can follow, and it reconciles holdings to the underlying balances and the summarized entries up to the GL. Measurement aligns to your reporting framework, and the same engine drives both the balance sheet and the income statement. The result is what a business, a fund or a firm actually needs when crypto has to be on the books rather than on a dashboard: records, controls and evidence — not just a performance view. See how the postings are built on the journal entries → page, and how basis is calculated on the cost-basis methods → page.

More questions about trackers vs sub-ledgers

Can I just export my tracker's data into my accounting system?

Not in a way your books can rely on. A tracker's export is a list of balances and approximate gains with no double-entry structure, no consistent cost-basis method, no classification of transfers versus sales, and no drill-down behind the totals. Pasting that into a GL gives you figures an auditor cannot test and a close that will not reconcile. A sub-ledger produces the journal entries directly, mapped to your accounts and backed by the source transactions.

Why isn't unrealized gain enough for the books?

Because unrealized gain is a mark-to-market performance figure, not a transaction the books can recognize on its own. Your income statement records realized results when assets are actually disposed of, measured against cost basis, and your balance sheet carries the remaining holdings under your reporting framework's measurement rules. A tracker's unrealized number tells you how the portfolio is doing; it does not give you the realized gain, the carrying basis, or the journal entry the accounts require.

Do auditors accept portfolio-tracker reports as evidence?

Generally no, because a tracker provides assertions without an audit trail. An auditor needs to test completeness, accuracy and integrity — that every transaction was captured once, classified correctly, measured consistently, and left unaltered — and to trace each reported figure back to its source. A tracker has none of that machinery. A sub-ledger is designed around it, which is why its records, not a dashboard, are what stands up in review.

If I already run a tracker, do I still need a sub-ledger?

They serve different jobs, so many teams keep a tracker for day-to-day monitoring and add a sub-ledger for the accounting. The tracker tells you how holdings are performing; the sub-ledger produces the records, controls and audit trail your books and auditors depend on. The moment crypto has to appear in real financial statements — for a company, a fund or a firm's clients — the tracker alone is not enough, and the sub-ledger is the part that makes the accounting defensible. The two are complementary, not competing: monitoring and bookkeeping are different disciplines, and trying to force a performance tool to do an accountant's job is where crypto books most often go wrong.

Does the sub-ledger lose the at-a-glance view a tracker gives me?

No. Because the sub-ledger holds every transaction at the lot level, it has all the underlying data a tracker works from — and more, since it also carries cost basis, classification and the posting history. The difference is purpose: its job is to turn that detail into accounting records your books and auditors can rely on, rather than to present a performance dashboard. You keep full visibility into holdings and activity; what you gain on top is the double-entry structure, controls and audit trail that a performance view alone can never give you.

Moving from a tracker to a sub-ledger in practice

Knowing a sub-ledger is the right tool is one thing; making the move without disruption is another. The good news is that the two are complementary, so adopting a sub-ledger does not mean abandoning the dashboard you watch day to day — it means adding the accounting layer the tracker was never built to provide. The shift is mostly about where the source of truth lives. A tracker treats whatever the feeds report as final; a sub-ledger treats those feeds as raw input to be deduplicated, classified, measured, and reconciled before anything reaches the books. Practically, the transition is a matter of connecting the same wallets and venues, then letting the engine build the records the tracker never produced.

A clean transition usually runs through a short sequence:

• Connect every source the tracker already watched, so completeness carries over and no wallet is left out of the books.
• Let history be classified and deduplicated, so the same event from an exchange and a wallet is counted once, not twice.
• Apply the cost-basis method your accounting policy requires, consistently, so realised results are comparable period to period.
• Reconcile holdings and post journal entries, so the figures land in the general ledger with a trail behind each one.

From there the day-to-day monitoring can stay exactly as it was, while the close, the audit, and the statements run off accounting-grade records. CryptaCount is built as that layer: it turns connected activity into double-entry journal entries mapped to your chart of accounts, retains the source transactions behind every figure, and measures the position under your reporting framework — see the crypto compliance and reporting overview for how that measurement carries through. The change a team feels first is at close: instead of exporting a dashboard and hoping the numbers survive an auditor's questions, you post journals that already carry their own evidence, and the reconciliation that used to happen in a side spreadsheet now happens inside the books. The dashboard tells you how holdings are doing; the crypto sub-ledger is what your books and auditors actually rely on when crypto has to appear in real financial statements.