What shadow NAV is — and isn’t
A shadow NAV is the manager’s own calculation of the fund’s net asset value, built from its own book and its own valuation, and compared against the administrator’s figure before that figure is published.
It isn’t a replacement for the administrator. The administrator’s NAV remains the official one, used for subscriptions and redemptions. Nor is it a copy of the administrator’s work. Its value comes from independence: a separate data path, separate pricing and separate fee calculations, so that an error in one calculation shows up as a difference against the other.
Why funds run one
The administrator’s NAV is built largely from data the fund and its counterparties supply. A mis-booked trade, a missed corporate action or a fee accrued on the wrong base passes straight into the official number unless something independent catches it.
Three pressures push managers to run that check themselves:
- Allocators ask. Operational due diligence questionnaires routinely ask who independently verifies the NAV. “We rely on the administrator” tends to open the topic rather than close it.
- Timing. The official NAV may be monthly or weekly. A daily shadow NAV gives the manager a verified view in between.
- Cost of late discovery. An error found on the day it happens is a quick fix. The same error found after publication can mean restating NAVs and correcting investor dealings.
How it works
- Keep your own book. Positions and cash, reconciled daily against custodians, prime brokers and — for digital assets — exchanges and wallets.
- Value it on your policy. The same valuation point and pricing hierarchy the fund’s valuation policy sets out.
- Accrue fees and expenses per share class. Management and performance fees, with crystallisation handled per class.
- Compare. Match the shadow NAV to the administrator’s NAV at fund and share-class level.
- Apply a tolerance. Differences within tolerance are signed off. Differences outside it are investigated.
- Attribute and resolve. Each variance is traced to a cause, resolved with the administrator, and recorded as evidence.
Setting tolerances
Tolerances are usually expressed in basis points of NAV and set per fund and share class. A simple, liquid strategy can hold a tighter threshold than one with hard-to-price instruments. Whatever the level, write down three things: the threshold, who reviews a breach, and whether publication waits until it’s resolved.
A worked example
Illustrative figures for a fictional fund. A share class has a NAV of €50 million. The administrator’s figure and the shadow NAV differ by 6 basis points — €30,000 — against a tolerance of 2 basis points. The difference is attributed before publication:
| Cause | Impact | Resolution |
|---|---|---|
| Corporate bond priced from a stale close | 4.5 bps | Administrator reprices from the policy source |
| Management fee accrued on the prior day’s NAV | 1.2 bps | Methodology confirmed; shadow book aligned |
| Different FX fixing source | 0.3 bps | Within policy; documented |
After the reprice and the fee alignment, 0.3 basis points remain — within tolerance, explained, and recorded. The NAV is published on numbers both sides can account for. Without the shadow calculation, the stale bond price would have gone into the official NAV unnoticed.
Detection is only half the job. A variance isn’t closed until it has a cause.
What it catches most often
The variances that recur are ordinary: pricing differences between sources or cut-offs, trade-date versus settlement-date timing, corporate actions, and fee or accrual errors. For digital assets, add venue price divergence and inconsistent valuation points — covered in how crypto funds strike NAV.
Four ways to operate it
- Rely on the administrator alone. Cheapest, but offers no independent check and tends to raise due diligence questions.
- In-house, on spreadsheets. Independent, but fragile: dependent on one or two people and weak on evidence.
- In-house, on a platform. The book of record is reconciled daily, the shadow NAV runs on a schedule, and every check leaves an audit-ready trail.
- Outsourced. A middle-office provider runs it on the manager’s behalf. Make sure the provider is independent of the administrator whose NAV it checks.
Frequently asked questions
Is shadow NAV a regulatory requirement?
Rarely as such. Requirements depend on the fund’s regime — frameworks such as AIFMD set expectations for proper and independent valuation — but shadow NAV is mostly driven by allocators and operational due diligence teams, who expect an independent check on the administrator’s figures. Confirm what applies to your funds with your compliance adviser.
How is shadow NAV different from the administrator’s NAV?
The administrator’s NAV is the official figure used for subscriptions and redemptions. The shadow NAV is the manager’s own independent calculation of the same figure, used to check the official NAV before it is published.
What tolerance should a shadow NAV use?
Tolerances are usually expressed in basis points of NAV and set per fund and share class, depending on how complex and liquid the strategy is. The threshold, and what happens when it is breached, should be written into the fund’s NAV oversight procedure.
Can the fund administrator run the shadow NAV?
It defeats the purpose. A shadow NAV is valuable because it is independent of the official calculation, so it should be run by the manager or by a separate provider, not by the administrator whose NAV it checks.
Does shadow NAV work for crypto funds?
Yes, with two extra points of care: crypto trades continuously, so the valuation point must be fixed and documented, and venue prices diverge, so the pricing source for each asset must be defined. Digital assets are then valued and reconciled in the same cycle as the rest of the book.