NAV
Net Asset Value (NAV) is the per-share or per-unit value of a fund's net assets, calculated as (total assets − total liabilities) / units outstanding. For mutual funds and ETFs, NAV is computed daily after market close. For hedge funds and private funds, NAV is computed monthly or quarterly with a reporting lag of 30–90 days. The lag is the operational reality of illiquid-asset valuation.
NAV is the central accounting datum for any pooled investment vehicle. Mutual funds NAV at 4:00 PM ET each business day; trades placed before the cutoff settle at that day's NAV. ETFs trade continuously at market prices that should track NAV but can deviate (creating arbitrage opportunities for authorized participants). Hedge funds and private funds NAV less frequently — typically monthly for hedge funds with semi-liquid strategies, quarterly for private equity and real estate.
The reporting lag for private funds is the source of the 'private fund smoothing' phenomenon. A Q4 2024 hedge fund NAV typically arrives in late January 2025; a Q4 2024 private-equity NAV typically arrives in early March 2025. During the lag, the fund's reported NAV is stale — it doesn't reflect post-quarter market movements. This produces apparent low-volatility for private funds (because the volatility is hidden in the reporting lag) and creates timing-mismatch problems for portfolio analytics that mix public and private holdings.
NAV calculation methods vary across fund types. Hedge funds typically use mark-to-market for liquid assets and last-trade or appraisal-based valuation for illiquid positions. Private equity funds use 'fair value' methodology under ASC 820 (for US GAAP) or IFRS 13 — typically a combination of comparable-company analysis, transaction multiples, and discounted-cash-flow valuation, recalibrated quarterly. Real-estate funds use appraisal-based methods, often blending external appraisals with market-data adjustments.
The time-stamp on NAV is data, not metadata. A 'current' NAV from a private equity fund is the most recent reported NAV — possibly 60–90 days old. Synthetic test data and aggregation engines must treat NAV as 'NAV as of [date]' rather than 'current value' to avoid producing wrong household-level analytics.
Synthetic alternative-fund positions should track NAV with explicit asOf timestamps. Stale NAV during the reporting lag should be the default state. Mark-to-market NAVs (hedge funds) and appraisal NAVs (private equity, real estate) should have different lag profiles. Aggregation engines computing household-level metrics should respect the asOf gaps rather than treating all NAVs as contemporary.
Common pitfalls
- Treating the 'most recent' NAV as today's value — for private funds, it might be 60–90 days stale.
- Aggregating public and private NAVs without timestamp alignment — produces apparent diversification benefits that are actually just lag.
- Computing volatility on private-fund NAVs without lag-adjustment — drastically understates true volatility.
- Using stale NAV for capital-allocation decisions during volatile market periods — the fund's assets may have moved 10–20% since the last NAV without reflecting in the reported number.
Examples
Q4 2024 quarter ends Dec 31. Fund GP requires 60 days for quarterly close: NAV statement issued ~March 1 2025. Held by an investor who reviews their portfolio Feb 15: most recent reported NAV is Q3 (Sept 30 2024) — almost 5 months stale. Markets moved 8% over Q4; the Sept 30 NAV reflects none of it. Investor's apparent total return for 2024 is the Q3-2024 figure, not 2024-year-end. The portfolio-level dashboard must surface the staleness explicitly.