Crypto accounting for funds

Crypto funds run on volume, multiple wallets and entities, and DeFi positions that off-the-shelf accounting can't track — while LPs and auditors expect institutional-grade numbers. CryptaCount is the fund-grade crypto sub-ledger that produces them.

What funds are up against

A crypto fund's activity spans many wallets and exchanges, high transaction counts, staking and DeFi positions, and multiple legal entities — all needing accurate cost basis, fair-value measurement, NAV, and a clean trail for the annual audit. Spreadsheets and generic crypto trackers don't hold up to that.

How CryptaCount delivers

• Built for volume. Ingest high transaction counts across every wallet and exchange, reconciled automatically.
• Fair value and cost basis. Apply your measurement policy and the right cost-basis method, with realized and (where applicable) fair-value movements posted to the GL.
• Fund, series & investor tracking. Track fund, series, and investor positions with NAV and high-water-mark, across multiple entities.
• DeFi and staking. Liquidity, lending, staking, and NFT positions captured and classified — not dropped.
• Audit-ready. A complete, traceable trail from each GL line to the source transaction, built for your LP audit.

Numbers your LPs and auditors can rely on

• Accurate pricing — valuations drawn from our pricing engine, not guesswork
• 12 cost-basis methods — applied consistently across the book; jurisdiction-mandated treatments (UK Section 104, Canada ACB) apply automatically
• Immutable trail — double-entry entries with integrity hashing for verifiable records
• Period close — summarized entries to your GL, with full detail retained

See the sub-ledger → · Compliance & reporting →

Why a fund's books break under volume and structure

A crypto fund fails on accounting for two reasons at once: the sheer volume of activity, and the structural complexity behind it. A strategy that touches many wallets, several exchanges and a shifting set of DeFi positions can generate transaction counts that no spreadsheet survives, and the moment more than one legal entity or series is involved, every figure has to be attributed correctly or the NAV is wrong. Generic crypto trackers were built for an individual watching a portfolio, not for a fund administrator producing institutional-grade numbers an LP and an auditor will scrutinise. CryptaCount is the crypto sub-ledger that holds that volume and structure together: high-throughput ingestion, automatic reconciliation, and entity-aware tracking that keeps the fund's economics coherent. The engine is described on the crypto sub-ledger → page.

The stakes are higher for a fund than for most businesses because the accounting output is also an investor-facing number. A misclassified transfer does not just distort an expense line — it moves the NAV, which moves what an LP is told their position is worth and what the manager's high-water-mark is measured against. That is why a fund cannot treat crypto bookkeeping as a year-end clean-up; it needs a reconciled record that holds up continuously.

The fund accounting workflow CryptaCount enables

For a fund, the workflow is built around producing reliable periodic numbers from messy, high-volume activity. The sub-ledger ingests every wallet and exchange, reconciles balances to the chain, and classifies the full range of positions — spot, staking, lending, liquidity and NFT activity — so nothing is silently dropped. Cost basis and, where the measurement policy requires it, fair-value movements are applied and posted, and fund, series and investor positions are tracked with NAV and high-water-mark across the entities in the structure. The result is a close that produces the same institutional-grade numbers each period rather than a reconstruction effort every quarter.

• Ingest at volume — high transaction counts across every wallet and exchange, reconciled automatically
• Classify all position types — staking, lending, liquidity and NFT activity captured, not left out
• Apply measurement — cost basis and fair-value movements posted per your policy
• Track the structure — fund, series and investor positions with NAV and high-water-mark across entities
• Attribute correctly — activity routed to the right entity so consolidation and NAV stay clean
• Close to the GL — summarized journal entries posted with full detail retained behind every line

Because the detail is retained behind each summarized posting, the administrator can produce a clean GL for the fund and still answer any LP or auditor question down to the individual transaction. The way those postings are assembled is set out on the journal entries → page.

Fair value, NAV and the measurement policy

Funds typically measure digital assets at fair value, which makes the valuation source and the timing of measurement central to every NAV. CryptaCount applies the fund's measurement policy consistently, drawing point-in-time valuations from its pricing basis so that period-end and intra-period marks rest on a defined source rather than a manual lookup. Realized results flow from disposals under the chosen cost-basis method, and fair-value movements are posted where the policy requires, so the NAV reflects both realised and unrealised changes coherently. Because the method and the valuation basis are recorded, the manager can explain to an LP exactly how a mark was struck, and an auditor can test it against a consistent rule rather than a judgment made in the moment.

Multi-entity structure and clean consolidation

A fund is rarely a single entity. Even where the platform does not model a full distribution waterfall, it keeps activity attributed correctly across the legal entities involved, so intercompany crypto movements are recognised as internal transfers rather than disposals, and basis follows the asset across the move. That attribution is what keeps consolidation honest: without it, a transfer between two of the fund's own entities can appear as a sale in one and an acquisition in the other, double-counting the asset and distorting the consolidated NAV. By scoping the sub-ledger per entity and netting internal moves, CryptaCount keeps the structure's economics coherent from the individual wallet up to the consolidated number an LP sees.

Audit and investor reporting obligations

A fund answers to its LPs and to an annual audit, and both expect a record that ties out. The sub-ledger produces a complete, traceable trail from each GL line to the source transaction and its on-chain hash, with double-entry entries carrying integrity hashing for tamper-evident records — exactly the evidence an LP audit walks. Beyond the audit, funds are increasingly caught by structured reporting frameworks such as the OECD's CARF, the EU's DAC8 exchange-of-information rules, and the MiCA regime, all of which assume a classified, point-in-time record of activity. Because that record already exists in CryptaCount, the fund is positioned to support those obligations rather than rebuilding data under deadline. Measurement under IFRS or US GAAP is applied per the fund's policy — see crypto compliance reporting → and IFRS crypto accounting →.

Capturing DeFi and staking as the fund actually trades

Much of a crypto fund's economics lives in positions that generic accounting simply ignores. Staking rewards accrue and are received as income; lending positions generate interest and carry the lent asset off the spot balance; liquidity provision swaps a single asset for a pool position whose composition shifts with the market; and NFT activity has its own acquisition and disposal pattern. If these are dropped or lumped together, the fund's books understate both its income and its true asset position, and the NAV drifts away from reality. CryptaCount captures and classifies these position types rather than discarding them, so staking and reward income is recognised at value on receipt, lending and liquidity positions are reflected in the holdings, and the disposals that close them out realise gains and losses under the fund's chosen method. That completeness is what lets a manager show an LP the real drivers of return — not just spot price movement, but the yield and protocol activity the strategy was built around. It also means the auditor sees the same complete population the manager does, so there is no gap between what the fund reports and what the books can support. For a fund whose edge is in DeFi, accounting that can actually see DeFi is not a convenience; it is the difference between a defensible NAV and an estimate, and it is the foundation on which every investor statement and audited figure ultimately rests.

Common pitfalls in fund crypto accounting

• Spreadsheet NAV — manual books cannot carry a fund's volume or survive an LP audit; a reconciled sub-ledger can
• Dropped DeFi positions — staking, lending and liquidity activity omitted from the books understates the fund's economics
• Cross-entity contamination — activity attributed to the wrong entity distorts NAV and consolidation; it must be routed correctly
• Internal transfers booked as sales — moves between the fund's own wallets should net out, not create phantom gains in the NAV
• Inconsistent valuation — marks struck from ad-hoc lookups cannot be defended; a defined point-in-time basis can
• Switching cost-basis method mid-book — produces results no LP or auditor can reconcile; the method must be applied consistently

How CryptaCount helps crypto funds

For a crypto fund, CryptaCount is the fund-grade sub-ledger that turns high-volume, multi-entity, DeFi-heavy activity into numbers an LP and an auditor can rely on. It ingests and reconciles every venue, captures the full range of positions, applies the fund's measurement policy with a defensible valuation basis, tracks fund, series and investor positions with NAV and high-water-mark across entities, and posts summarized journal entries to the GL with the full record retained behind every line. The manager gets institutional-grade books continuously, not a year-end scramble. Explore the crypto sub-ledger → and journal entries → to see the engine in detail.

How is high-water-mark tracked across series?

Fund, series and investor positions are tracked with NAV and high-water-mark across the entities in the structure, so each series carries its own basis for measuring performance. Because the underlying activity is reconciled and attributed correctly, the high-water-mark rests on a NAV the manager can defend rather than an estimate.

Can it value our holdings at fair value for NAV?

Yes. The sub-ledger applies your measurement policy, drawing point-in-time valuations from its pricing basis, and posts fair-value movements where your policy requires them. Realized results come from disposals under your chosen cost-basis method, so the NAV reflects both realised and unrealised changes on a consistent basis.

Are transfers between our own entities handled correctly?

Yes. Moves between entities you control are recognised as internal transfers rather than disposals, with basis following the asset across the move. That keeps each entity's later results accurate and stops a single internal transfer from double-counting an asset in the consolidated NAV.

Will the books hold up to our annual LP audit?

Yes. Every figure traces from the GL line to the source transaction and its on-chain hash, and entries are recorded with integrity hashing for tamper-evident records. The auditor can re-perform the cost-basis calculation and tie out the population, which is exactly what an LP audit needs to see.

Why funds need a sub-ledger, not a tracker

A fund's books have to stand up to administrators, auditors and investors, which a portfolio tracker was never designed for. A sub-ledger gives a fund the reconciled, policy-driven record those parties expect: consistent cost basis across strategies and venues, traceable gains, and clean period journal entries that post to the general ledger. CryptaCount handles multi-entity and multi-venue activity and produces IFRS-aligned outputs, so the fund's NAV and financials rest on numbers that reconcile. See the sub-ledger and journal entries.