Glossary

NAV Reconciliation — Definition, Process, and Why It Matters for Verification

NAV reconciliation is the process of cross-checking a portfolio's stated net asset value against an independent source. Definition, fund-administration practice, and how NakedPnL applies the same principle for public verification.

By NakedPnL Research·May 9, 2026·5 min read

TL;DR

NAV reconciliation is the process of cross-checking a portfolio's stated net asset value against an independent source — typically a prime broker, custodian, or on-chain ledger.
Fund administrators reconcile daily as a matter of routine; differences trigger investigation before NAV is finalised.
NakedPnL applies the same principle in public verification by re-fetching from the venue API and (where applicable) reconciling against the on-chain subgraph.

Definition

NAV reconciliation is the process of comparing a portfolio's stated net asset value (NAV) against an independent record of the underlying positions and cash, identifying any discrepancies, and resolving them before the NAV is treated as final. In institutional fund operations the reconciliation typically runs nightly between the manager's internal book of record and the prime broker's or custodian's statement of positions and cash. In on-chain crypto contexts the reconciliation is between a venue's REST API response and the canonical on-chain ledger (or a subgraph derived from it).

Why it exists

A NAV figure is the foundation of every performance metric, fee calculation, and investor statement that follows. If the NAV is wrong, every downstream number is wrong. Reconciliation exists to catch errors at the earliest possible point — failed trades, missed corporate actions, mispriced thinly-traded positions, fee calculations that did not run, accrued interest that was forgotten, or, in crypto, withdrawals that were processed but not yet reflected in the venue's wallet view. None of these are unusual; they are the normal operational friction of running a portfolio. Reconciliation makes the friction visible.

Standard reconciliation flow

Pull the position file from the manager's internal book of record at the cut-off time.
Pull the position file from the independent source (prime broker, custodian, or on-chain ledger) at the same cut-off time.
Compare position-by-position by instrument identifier.
Flag every break: missing positions, quantity mismatches, price differences above a tolerance, cash mismatches.
Investigate each break against the trade blotter, settlement schedules, and corporate-action calendar.
Either resolve the break with documented evidence or defer NAV publication until the difference is explained.
Compute the reconciled NAV, sign off, publish.

How NakedPnL applies the same principle

NakedPnL is not a fund administrator and does not run an internal book of record competing with the venue's record. The reconciliation it performs is between sources: the venue's REST API response and, where available, an independent on-chain or subgraph view of the same account. For Polymarket positions, lib/venues/polymarket/reconcile.ts compares REST snapshot positions against the Graph Protocol subgraph and records any divergence in the audit chain rather than silently picking one source. For exchanges without an independent reconciliation surface, the daily snapshot uses the venue's response as the primary record but writes the canonicalised raw response into the SHA-256 hash chain so any later divergence (if the venue restates) is detectable.

The principle in both cases is the same: a stated NAV is only useful if there is a path to challenge it. Reconciliation provides that path. The verification methodology guide on independent third-party verification goes deeper into how the chain bundle and venue responses can be re-checked.

Common reconciliation breaks and what they mean

Position quantity mismatch — usually a settlement timing difference. The trade has executed but the cash leg has not yet cleared.
Price mismatch — different fair-value sources used for the same illiquid instrument; the manager and the administrator disagree on the mark.
Missing position — a corporate action was processed by one side and not the other (e.g. a stock split, a token swap, a chain merge).
Cash mismatch — a fee accrual was applied on one side and not the other; or, in crypto, a withdrawal was deducted from one record before the other.
Multiple small mismatches across many positions — typically a price file that did not refresh; rerun the pricing pipeline.

Net asset value (NAV) — the value being reconciled.
Fund administrator — the party performing reconciliation in regulated fund operations.
Prime broker — one of the two records typically reconciled.
Time-weighted return — the calculation that consumes the reconciled NAV series.

Frequently asked questions

Does NakedPnL replace a fund administrator's reconciliation?

No. A regulated fund still needs an independent administrator to perform full position-and-cash reconciliation against prime-broker records. NakedPnL records the venue's stated NAV and, where possible, reconciles against an independent source (e.g. on-chain subgraph for Polymarket). It is complementary to administrator-level reconciliation, not a substitute.

What happens if an exchange restates an old NAV figure?

The original snapshot row remains in the append-only chain. A new row is added recording the restatement. Any reviewer can see both values and judge whether the restatement materially changes the published TWR. Silently overwriting the old number would break the chain.

Why is reconciliation harder in crypto than in equities?

Equities have a clear settlement infrastructure (DTCC, central securities depositories) that produces an authoritative position record. Crypto venues each operate their own internal ledgers and the on-chain ledger only sees deposits and withdrawals, not internal venue trades. So the reconciliation surface is sometimes only between two venue endpoints rather than between the venue and an independent custodian.

How often does reconciliation actually find errors?

Operationally, every day. Most are tiny — fee accruals, FX timing, dust amounts. The point of reconciliation is not to catch big errors (those are rare) but to keep the small ones from accumulating into a drifted NAV. A book that is reconciled daily diverges far less than one reconciled monthly.

References