Independent Singapore VCC guidance
Direct answer
A market-data outage should trigger the VCC valuation contingency plan, not an improvised price substitution. Freeze the affected universe, record the last good timestamp, identify every NAV field that depends on the failed feed, and use only pre-approved alternative sources or valuation methods. Separate data recovery from the decision to release NAV. The manager and valuation reviewers must challenge stale or conflicting results, disclose unresolved effects where required, and retain a complete post-incident reconciliation before the cycle is closed.
At a glance
- Map the outage to affected funds, assets and calculations.
- Use only authorised fallback sources and methods.
- Keep restoration evidence separate from NAV approval.
- Back-test provisional decisions after primary data returns.
Who this is for
- Price, FX, index, corporate-action or reference-data disruption affecting VCC valuation
Important exclusions
- Using an outage as permission to override governing documents or conceal a valuation uncertainty
Classify the outage before calculating
Record the provider, dataset, failure time, last good observation, affected instruments and dependent calculations. Determine whether the issue is missing data, delayed data, corrupted values, mapping failure or a wider provider incident. Operational-resilience planning requires the important service and dependencies to be understood, so the incident owner should map the feed through valuation, risk, dealing, fee and investor-reporting outputs rather than treat it as a single vendor ticket.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority| Failure | Immediate control | Release question |
|---|---|---|
| Missing prices | Freeze affected universe and last-good timestamp | Is an approved alternative source available? |
| Corrupted values | Quarantine the batch and compare independent observations | Can the extent of contamination be proven? |
| Late corporate action | Hold entitlement and instrument mapping | Would NAV or units be misstated? |
| Reference-data break | Block unmapped securities and classifications | Can the correct identity and terms be independently established? |
Related guidance: VCC cyber incident response
Invoke the authorised fallback hierarchy
Use the valuation policy and offering terms to identify the allowed hierarchy, such as another independent source, broker evidence, model input or committee-approved estimate. Record why the normal source is unavailable and why the substitute is suitable for the asset and time. Do not choose the value that produces the least NAV movement. If the documents do not authorise a defensible route, escalate the release decision rather than creating a new method during the incident.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Confirm the fallback appears in the approved valuation framework.
- Use an independent source where the conflict profile permits.
- Record timestamp, contributor, market context and adjustments.
- Apply the method consistently to similarly affected positions.
- Identify any investor, director or auditor communication trigger.
Related guidance: valuation model version-control guide
Challenge provisional values
Compare the fallback with the last good price, observable markets, related instruments, cash flows and position size. Set thresholds for absolute movement, percentage movement and NAV impact, but do not let a threshold replace judgement about a concentrated or illiquid holding. Separate the preparer from the reviewer. A restored feed is not automatically correct, so compare the first recovered batch with independent evidence before using it.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Prepare the affected-position listInclude quantity, source, timestamp, fallback method and calculated NAV impact. Retain the documented result for independent review before the next decision.
- Run independent challengeTest outliers, stale observations, liquidity, events and instrument mapping. Retain the documented result for independent review before the next decision.
- Decide release statusRelease, delay or escalate according to the documents and materiality assessment. Retain the documented result for independent review before the next decision.
- Record rationaleRetain evidence for each exception and the person who approved the outcome.
Run the post-incident reconciliation
When primary data returns, compare it with every provisional or fallback value and recalculate the affected outputs. Investigate differences, determine whether corrections or investor communications are required under the actual documents, and record the decision. Update the dependency map, fallback contacts, access and test schedule. The useful lesson is not merely how long the outage lasted, but whether the control path produced timely, reproducible and fair valuation decisions.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Primary data returnsValidate the provider timestamp, completeness and instrument mapping. Retain the documented result for independent review before the next decision.
- Back-test valuesCompare each fallback with recovered data and quantify NAV and transaction effects.
- Resolve consequencesEscalate corrections, notifications or control changes under the governing framework. Retain the documented result for independent review before the next decision.
- Retest the planConfirm alternative access and decision authority before the next valuation cycle. Retain the documented result for independent review before the next decision.
Related guidance: VCC shadow NAV reconciliation
Practical review and evidence pack
The incident pack should also record who detected the outage, which automated alerts worked, whether manual access remained available, and how the team prevented the same unavailable source from appearing through a second interface. Keep screenshots or exports of the provider status, but do not treat a status page as proof that the fund data is complete. Compare instrument counts, timestamps, currencies and corporate-action fields against the expected universe. Where a fallback source has different conventions, document the normalisation before a value reaches the NAV engine. These checks make the release decision reproducible for directors, auditors and later incident review.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory AuthorityFrequently asked questions
Can the last available price always be reused?
No. Its suitability depends on the asset, elapsed time, market events, liquidity and the approved valuation framework. A last price can be stale even when it is the only displayed value.
Does feed restoration mean NAV can be released?
No. The recovered data must still be checked for completeness, mapping and plausibility, and all affected calculations and exceptions must be reconciled. Record the conclusion against the actual documents, affected entity and current official requirements, with qualified advice where the facts remain uncertain.
Who should approve a fallback price?
Use the authority in the valuation policy and governing documents. Preparation, independent challenge and release should be separated where the operating model allows. Record the conclusion against the actual documents, affected entity and current official requirements, with qualified advice where the facts remain uncertain.
What should be retained after the incident?
The affected universe, timestamps, fallback evidence, approvals, NAV impact, communications, recovered-data comparison and remediation owners. Record the conclusion against the actual documents, affected entity and current official requirements, with qualified advice where the facts remain uncertain.
Official sources and further reading
- Operational resilience (Monetary Authority of Singapore)
- Overview of managing a VCC (Accounting and Corporate Regulatory Authority)
- VCC key features, eligibility and requirements (Accounting and Corporate Regulatory Authority)
Discuss your fund, family office or trust structure
Contact Raffles Corporate Services about Singapore VCC setup, fund structures, family offices and corporate administration.
- Email: hello@rafflescorporateservices.com
- WhatsApp: +65 8501 7133
- WhatsApp: +65 9018 0072
Where legal assistance is required, we can coordinate an introduction to an associate independent law firm, with your consent. The law firm advises you under a separate engagement. Raffles Corporate Services is not a law firm. Tax, investment management and trustee services, where needed, require appropriately qualified or authorised providers.
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.