Fund reporting · Funds and administrators · Oct 10, 2026 · 2 min read
Crypto NAV and month-end close for fund administrators
A repeatable close process: fix the cutoff, check every balance, price consistently and hand investors numbers you can support.
By ChainLedger editorial team · Crypto audit, tax and fund reporting · Last reviewed
Key takeaways
- Pick one cutoff time and one pricing policy, and use them every period.
- Check balances before pricing. A missing transaction can't be fixed by a better price.
- Keep each period's holdings snapshot so prior NAVs can be rebuilt and explained.
Crypto markets never close, so a fund's month end is whatever time the fund says it is. A clean NAV process makes that choice once, applies it every period, and keeps the evidence for each number.
A month-end close in seven steps
- 1Sync every wallet and exchange account up to the cutoff.
- 2Rebuild each balance from history and check it against the live balance.
- 3Resolve anything flagged: missing purchases, unknown deposits, unpriced tokens.
- 4Snapshot holdings at the cutoff, for example 23:59:59 UTC on the last day of the month.
- 5Price each holding at the cutoff, using the fund's stated sources and pairs.
- 6Calculate realized and unrealized gains with the fund's book method.
- 7Lock the period and export the holdings and gains for the NAV pack.
Decisions to write down once
| Policy | Example |
|---|---|
| Cutoff time | 23:59:59 UTC on the last calendar day |
| Price source | Named exchange, USD pairs, nearest to cutoff |
| Book method | Average cost for NAV, FIFO for tax |
| Illiquid tokens and NFTs | Held outside NAV, or at a documented value |
| Staking rewards | Income when received, valued on arrival |
ChainLedger rebuilds holdings and value to 23:59:59 UTC on any date, keeps NFTs outside NAV, and runs the book and tax methods on the same checked records.
Related product page: Crypto fund administration software