Map Every Dependency in a VCC NAV Calendar

Define the NAV event and its uses

Start with the fund documents, valuation policy, dealing terms and reporting commitments. Record the valuation point, time zone, currency, frequency, publication target and every use of the result, including subscriptions, redemptions, fees, performance, financial reporting and investor communications. An umbrella VCC may have different cycles by sub-fund or share class. Build separate paths where cut-offs or methods differ instead of forcing every strategy into one generic calendar.

Related guidance: VCC compliance checklist

Map every source input and owner

List positions, trades, cash, prices, foreign exchange rates, corporate actions, income, expenses, investor activity, financing, collateral and tax items. Record the provider, system, file name, expected arrival, cut-off, fallback source and accountable owner for each dependency. Separate automated delivery from verified completeness. A file arriving on time does not prove that its population, date, currency or account scope is correct.

Build the critical path and challenge window

Connect tasks in the order they must complete. Market-data validation may depend on security masters; price challenges may affect accruals; cash and position reconciliations can change exposure; investor activity can alter shares and fee calculations. Identify tasks with no time buffer and reserve a genuine challenge window before release. Do not make the official deadline so tight that reviewers can only approve the administrator output without investigation.

Related guidance: VCC roles and responsibilities

Define blocking and exception rules

For each dependency, state whether a delay blocks calculation, blocks release, permits an approved estimate or requires restricted use. Define escalation by age, value, affected investors and mandate significance. Manual prices, estimated expenses and unresolved cash or position breaks should remain visible with the source, rationale, approver and next action. A green workflow status should not hide a material judgment or an item carried forward repeatedly.

Test the calendar before relying on it

Run scenarios for a late custodian file, stale private-asset input, missing corporate action, unsettled trade, foreign-exchange gap, fee dispute, large subscription and administrator outage. Ask the team to identify the affected NAVs, blocking rule, fallback, approver, communication and evidence. Repeat the test for a sub-fund with a different time zone or dealing frequency. Record where the sequence depends on one person or an unverified spreadsheet.

Reperform selected calculations from source records and trace a released NAV into subscription, redemption, fee and investor-reporting outputs. Confirm that corrections propagate to every dependent use. Test access and version controls around manual journals and price overrides. The objective is not to simulate every failure, but to prove that the calendar exposes dependencies and routes exceptions without inventing authority.

Related guidance: VCC sub-funds guide

Operate and improve the dependency map

Record actual arrival times, recurring exceptions, overrides, rework and missed challenge windows. Review patterns by provider, market, asset class, sub-fund and owner. Adjust cut-offs only through the approved governance route and preserve the reason. A later target that allows reliable challenge may be safer than an earlier publication time that depends on optimistic inputs or routine manual overrides.

Version the calendar when funds, share classes, markets, providers, systems or valuation methods change. Keep the prior version for earlier NAV evidence and confirm affected staff and providers received the new sequence. Report material weaknesses to the manager and VCC governance body, with remediation owners and dates. Closure requires observed improvement in live cycles, not only an updated diagram.

Related guidance: Singapore VCC guide