Independent Singapore VCC guidance
Direct answer
When a suspected VCC NAV error appears, freeze the affected output, preserve the original data and identify every downstream use before recalculating. Separate containment from correction: one workstream stops further reliance, while another rebuilds the NAV from controlled sources. Release a correction only after independent review has established the cause, affected investors, financial impact, required communications and accountable approval.
At a glance
- Contain dealing and reporting before the suspected error spreads into new outputs.
- Recalculate from an untouched source set and record the root cause separately from the correction.
- Assess affected investors consistently, including subscriptions, redemptions and fee calculations.
- Release corrected figures only after independent review and a documented decision.
Who this is for
- VCC operations teams, managers, administrators and directors responding to a suspected or confirmed NAV error.
Important exclusions
- A fixed compensation formula, legal advice on investor claims, or a replacement for the fund documents and provider agreements.
Contain the suspected error
Treat the first alert as an incident, not a spreadsheet correction. Stop the affected NAV from feeding dealing, investor statements, management fees, performance reports or board packs until the perimeter is known. Preserve the original files, timestamps, approvals and system outputs before anyone overwrites them. Name an incident lead and a decision owner, then record what is paused and what remains safe to continue. This prevents a small valuation issue from becoming a wider transaction and reporting problem.
Sources: Monetary Authority of Singapore · ACRAImmediate containment actions
- Identify the sub-fund, share class, valuation point and outputs that may be affected.
- Lock original source files, calculations, interfaces and approval evidence against alteration.
- Pause only the dependent dealing or reporting steps identified by the incident owner.
- Notify the manager, administrator and relevant governance owner through agreed escalation channels.
- Open an incident log with decisions, assumptions, owners, evidence locations and unresolved questions.
Related guidance: VCC compliance checklist
Map every affected use
A NAV difference matters through the decisions and transactions that relied on it. Build a dependency map covering investors who subscribed or redeemed, fees calculated from NAV, financial statements, regulatory or tax reporting, collateral, financing covenants, public or private performance reports and any downstream system. Record the released value, corrected value and consequence for each use. This step should precede compensation or communication decisions because the same numerical error can affect different parties in different ways.
Sources: Monetary Authority of Singapore · ACRAImpact triage
- Was the figure released?If not, correct it under normal review controls and preserve the near-miss evidence for process improvement.
- Did any transaction rely on it?If yes, identify each investor and cash movement before deciding any adjustment or communication.
- Did it feed another report?Trace every downstream document, system and calculation, including fee and performance outputs.
- Is the treatment disputed?Escalate the accounting, valuation or document interpretation with the evidence and competing views clearly separated.
Approve the correction and communication
The decision pack should state the facts, corrected calculation, impact assessment, proposed treatment, communications, residual uncertainty and control remediation. Route it according to the VCC governance documents and service-provider responsibilities. The administrator can prepare technical evidence, but accountability should not disappear into an outsourced process. Investor communications should use consistent facts, avoid premature blame and distinguish the corrected amount from any separate decision about reimbursement, fee adjustment or process change.
Sources: Monetary Authority of Singapore · ACRARelated guidance: VCC board agenda and evidence pack
Close only after controls are repaired
An incident is not closed when the number has been corrected. Confirm that all affected records were updated, cash adjustments completed, communications delivered, reports reissued where appropriate and open questions assigned. The root-cause review should identify which preventive or detective control failed, why review did not catch it and how the revised control will be tested. Add the incident to recurring governance reporting until every action has objective closure evidence.
Sources: Monetary Authority of Singapore · ACRAIncident closure sequence
- ContainStop further reliance, preserve evidence and define the affected valuation and output perimeter.
- RecalculateRebuild from controlled sources and obtain an independent technical review of every difference.
- AssessTrace investor, fee, reporting, accounting and operational consequences without assuming one treatment fits all.
- DecideApprove the corrected value, treatment, communications and control remediation through the documented governance route.
- Verify closureReconcile every correction and keep the action open until testing shows the repaired control operates effectively.
Related guidance: VCC fund administrator change checklist
Frequently asked questions
Does every suspected NAV error require a dealing suspension?
Not automatically. The incident owner should identify which dealing or reporting steps depend on the disputed figure and pause that perimeter. A broad suspension without analysis can create a different operational problem.
Should the original NAV workbook be corrected directly?
Preserve the released version and rebuild from a clean copy or controlled environment. That maintains the audit trail and lets reviewers compare the original output, corrected output and precise causes of the difference.
Who should decide investor treatment?
Use the decision route in the fund documents, governance framework and provider agreements. Technical teams should quantify consequences, while the accountable governance body considers consistency, investor terms and any advice needed.
Can the administrator close the incident alone?
The administrator may perform the recalculation and investigation, but the VCC and manager still need clear ownership of decisions, communications and remediation. Outsourcing the calculation should not obscure accountability.
What makes the incident file complete?
It should preserve the alert, original and corrected data, dependency map, root cause, impact analysis, decisions, communications, cash and ledger reconciliations, remediation actions and evidence that the revised control was tested.
Official sources and further reading
- Governance and Management of Variable Capital Companies (Monetary Authority of Singapore, checked 2026-07-19)
- Legal obligations of a VCC director (ACRA, checked 2026-07-19)
- Overview of managing a VCC (ACRA, checked 2026-07-19)
- Variable Capital Companies Act 2018 (Singapore Statutes Online, checked 2026-07-19)
This independent guide was checked against the linked sources on 2026-07-19. Rules and administrative practices can change; confirm the current official position before acting.
Discuss a Singapore VCC structure
For help coordinating a Singapore VCC setup or corporate administration, contact Raffles Corporate Services.
General information only. This article is not legal, tax, regulatory or investment advice and does not imply affiliation with or endorsement by ACRA, MAS or IRAS.