# What Is NAV Reporting for Crypto Funds?

> How digital asset funds calculate Net Asset Value across wallets, chains and DeFi protocols — and why manual spreadsheet NAV breaks at scale.

- **URL:** https://octav.fi/blog/what-is-crypto-nav-reporting
- **Published:** 2026-05-23
- **Author:** Octav Team — Portfolio Intelligence for Digital Assets
- **Topic:** NAV Reporting
- **Tags:** nav-reporting, fund-accounting, compliance
- **Source:** Octav, Practical guides on crypto NAV reporting, multi-chain portfolio management and digital asset APIs, from the team behind Octav.

---
Net Asset Value is the single number a fund's investors, auditors and
administrators all agree to look at. For a traditional fund it is close to
arithmetic. For a digital asset fund holding positions across fifteen chains and
forty protocols, arriving at that number is the hard part.

## What NAV means for a digital asset fund

NAV is total assets minus total liabilities, divided by units outstanding. The
definition does not change because the assets are on-chain. What changes is the
difficulty of enumerating the assets in the first place.

A crypto fund's balance sheet is spread across:

| Position type | Where it lives | Why it is easy to miss |
| --- | --- | --- |
| Spot holdings | Wallets, exchanges, custodians | Multiple addresses per strategy |
| Lending positions | Aave, Morpho, Compound | Principal and accrued interest are separate |
| LP positions | Uniswap, Curve, Balancer | Value is a function of pool composition |
| Staked assets | Native staking, liquid staking | Rewards accrue continuously |
| Vesting or locked | Escrow, veTokens | Illiquid, but still an asset |

## Why spreadsheet NAV breaks

Manual NAV works at ten positions. It fails at two hundred, for reasons that
compound:

- **Pricing is inconsistent.** Two analysts pull a token price from two venues
  at two timestamps and produce two different NAVs.
- **Protocol positions are opaque.** A balance query returns an LP token, not
  the underlying assets it represents.
- **Reconciliation is unbounded.** Every new chain the fund touches multiplies
  the number of sources someone has to check by hand.

## What an automated NAV process needs

Any system that produces an auditable NAV has to do four things:

1. Discover every position the fund holds, without being told where to look.
2. Value each position from a consistent, timestamped price source.
3. Snapshot the result daily, immutably, so prior NAVs can be re-derived.
4. Produce an export an auditor accepts without re-keying it.

Points three and four are where most in-house tooling stops. A number you cannot
reproduce six months later is not a number an auditor can sign off on.

## Further reading

Enumerating positions is the hard half of NAV, and it is its own subject:
[Tracking DeFi Positions Across Multiple Chains](/track-defi-positions-multichain)
covers why lending, LP and staking positions resist a simple balance query.

If you would rather pull the underlying data yourself, see
[How to Pull Portfolio Data From a Crypto API](/crypto-portfolio-api-guide).

Once the NAV exists, the movements behind it still have to be booked and
evidenced:
[Crypto Transaction Reconciliation for Audits](/crypto-transaction-reconciliation).

For how NAV fits the wider operating stack, see
[Crypto Portfolio Management for Funds](/crypto-portfolio-management-funds).
