Independent Singapore VCC guidance
Direct answer
A VCC record-restoration test should prove more than the existence of a backup. Select records that support decisions, ownership, cash, positions, investors and filings; restore them into a controlled location; reconcile completeness and cut-off; confirm that authorised users can interpret and process them; and test the first dependent output. Record every gap, temporary workaround and residual copy. Normal processing should resume only after an accountable owner accepts the restored state and unresolved differences have a safe treatment.
At a glance
- Select records by business consequence and dependency, not by storage size.
- Test content, permissions, timestamps, relationships and practical usability after restoration.
- Reconcile each affected VCC and sub-fund before reopening dependent processing.
- Close failed criteria through repair and retest, not through an unsupported management waiver.
Who this is for
- Fund managers, VCC directors, administrators and technology or continuity owners testing recovery of critical operating records.
Important exclusions
- A technical certification that storage media works without proving that the restored business record supports safe VCC operations.
Choose the records that matter to decisions
Start from critical VCC activities and work backward to the records needed to perform, supervise or reconstruct them. The population may include the investor register, capital activity, cash and position records, valuation inputs, approvals, contracts, standing instructions, compliance evidence and statutory information. For an umbrella VCC, identify the sub-fund owner and relationships between shared and separate records. Include current data, configuration, reference tables and the instructions needed to interpret the restored material. A backup of transactions without account mapping or approval history can be technically intact yet operationally unusable. Record the authoritative source, recovery method, owner, acceptable cut-off and the dependent output that will prove usability.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority| Record set | Failure consequence | Usability proof |
|---|---|---|
| Investor and capital records | Wrong ownership or dealing decision | Population and control totals reconcile to the approved cut-off |
| Cash and positions | Incorrect liquidity, exposure or settlement action | Independent provider record agrees and exceptions are understood |
| Valuation inputs and approvals | Unsupported NAV or investor report | Input version, override history and sign-off remain connected |
| Authority and instructions | Unauthorised payment, trade or disclosure | Current users and action limits match approved records |
| Compliance and corporate records | Lost evidence or incomplete filing support | Search, retrieval and document relationships work in practice |
Related guidance: critical VCC service outage map
Define a test that can fail clearly
Write acceptance criteria before the exercise begins. Specify the disruption point, unavailable systems, restoration location, record population, expected cut-off, permitted assistance and time sequence. Avoid a demonstration in which the provider chooses an ideal file and explains the result without challenge. Use a representative period containing changes, exceptions and approvals, while protecting real personal and confidential information. Include a record that crosses organisations so the exercise tests handoffs as well as storage. The test should distinguish restoration, reconciliation, usability and controlled return to service. Each criterion needs observable evidence and a named decision owner. If the expected result is ambiguous, the team cannot tell whether the recovery route is dependable.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporePre-test controls
- The scenario states which primary systems and normal access routes are unavailable.
- The record population includes ordinary activity, changes, exceptions and approval history.
- Expected control totals and cut-off points are fixed before restored results are inspected.
- Test users have defined roles, and privileged recovery access is time-bounded and logged.
- A safe test-data or protected production-data method is approved before extraction begins.
- Pass, conditional-pass and fail outcomes have distinct consequences and decision owners.
Related guidance: VCC administrator continuity test
Restore into a controlled operating state
Preserve the original recovery evidence before users edit the restored records. Capture source identifiers, backup date, restoration commands or requests, file counts, hashes where used, access grants and system messages. Place restored material in a separated location until reconciliation is complete. Confirm that encryption, credentials, reference data and application versions allow authorised people to open and understand the record without exposing it more widely. Check whether relationships survived, such as transaction-to-approval links or investor-to-class mappings. A recovered file is not a recovered process. The team should run a bounded business action, such as producing a position exception report or tracing one investor change from instruction to final register.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeControlled restoration sequence
- InitiateRecord the scenario, decision owner, affected VCC scope, recovery request and evidence-preservation instructions before any restoration action begins.
- RecoverRestore the agreed population into an isolated location using authorised credentials and capture the source, version, timing and access evidence.
- ReconcileCompare counts, balances, identifiers, cut-off activity and relationships against independent sources for every affected sub-fund.
- UsePerform the defined business task and verify that a capable user can interpret records, exceptions and approval history correctly.
- DecideAccept, restrict or reject the restored state, then document workarounds, open differences, monitoring and the route back to normal processing.
Reconcile before reopening dependent work
Reconciliation should establish both completeness and chronology. Compare the restored population with independent bank, custodian, administrator, order, communication or corporate records according to the process being tested. Identify activity between the restored cut-off and the decision time, then decide how it will be replayed once without duplication. Separate genuine business exceptions from restoration defects. For umbrella structures, do not let agreement at total-VCC level hide a sub-fund allocation error. Check that permissions reflect current authority rather than the date of the backup. Dependent work should reopen in a bounded order, with early outputs reviewed more closely until the team has evidence that the record and process are stable.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory AuthorityReturn-to-service path
- ContainKeep restored data separate and prevent automated downstream use while ownership, cut-off and authority checks remain incomplete.
- ReconcileResolve or safely classify differences by source, record type, VCC, sub-fund and affected business outcome.
- Catch upReplay missing activity through an approved sequence that prevents duplicated entries, messages, payments or investor actions.
- ObserveReview initial reports and transactions under heightened control until expected relationships and exceptions remain stable.
- NormaliseRemove temporary access and parallel copies only after the accountable owner accepts the operating evidence and residual risks.
Related guidance: VCC crisis-communication tabletop exercise
Close findings through repair and retest
Treat every failed criterion as a finding with consequence, cause, owner, action and retest evidence. A slow restoration, missing approval link or excessive access may call for different remedies even when the final file is usable. Keep the test record connected to service-provider actions so contractual promises can be compared with observed performance. If a workaround remains, describe its limits, staffing, data source and expiry rather than allowing it to become an invisible permanent process. Retest the failed path under conditions that could disprove the repair. Give directors and accountable managers a concise view of what was tested, what failed, which VCC processes remain exposed and who accepted the final state.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: VCC records retention schedule
Frequently asked questions
Is a successful backup job enough evidence?
No. A backup log may show that data was copied, but it does not prove that the right population can be restored, opened, reconciled and used by authorised people. The exercise should test the record relationships, current permissions, cut-off and at least one dependent business output.
Should a restoration test use live investor data?
Use the least sensitive data that can prove the control. Synthetic or protected test data may be suitable for technical steps, while some business reconciliation tests need carefully controlled real records. Approve the method, restrict access and remove test copies when the evidence has been retained safely.
What if the provider performs the restoration?
The provider may execute technical recovery, but the VCC and manager still need to define the business population and acceptance evidence. Challenge the result through independent totals, current authority records and a usable business task instead of accepting a supplier screenshot as complete assurance.
Can one test cover every sub-fund?
A shared platform test can cover common technology, but evidence should still demonstrate the relevant sub-fund mappings and separate records. Select scenarios that can expose cross-sub-fund contamination, missing identifiers or incorrect allocation rather than relying only on an umbrella-level total.
When can normal processing resume?
Resume after the restored cut-off, completeness, authority and dependent output have been accepted by the accountable owner. Any open difference should have a safe treatment, owner and monitoring. Temporary access, catch-up activity and parallel records should remain controlled until closure.
Official sources and further reading
- Risk Management Practices for Fund Management Companies (Monetary Authority of Singapore)
- Technology Risk Management Guidelines (Monetary Authority of Singapore)
- Response to Feedback on Business Continuity Management Guidelines (Monetary Authority of Singapore)
- Guidelines on Individual Accountability and Conduct (Monetary Authority of Singapore)
- Understanding VCC Features, Eligibility and Requirements (Accounting and Corporate Regulatory Authority)
- Overview of Managing a Variable Capital Company (Accounting and Corporate Regulatory Authority)
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.