Independent Singapore VCC guidance
Direct answer
A provider exit plan is credible only when the VCC has tested the handover, not merely negotiated a termination clause. Run a controlled exercise using a defined cut-off date, representative data, a receiving environment and named decision owners. The test should prove that records can be exported, understood, reconciled and reloaded; that open items and authorities remain visible; and that access can be removed without interrupting valuation, dealing, payments or investor servicing.
At a glance
- Test the data in the successor's environment, not just in the outgoing provider's portal.
- Reconcile opening balances, open transactions and exception histories at one cut-off.
- Separate data ownership, service continuity, access revocation and commercial settlement.
- Retain a defect log and repeat the test after material system or service changes.
Who this is for
- VCCs and managers relying on administrators, custodians, transfer agents, cloud services or other critical providers.
Important exclusions
- A live termination notice or a substitute for contract, data-protection, employment or insolvency advice.
Define what a successful exit means
An exit test should demonstrate continuity of the business service, not simply delivery of files. Define the critical outcomes first: a reliable NAV process, complete investor and transaction records, controlled payments, retained corporate records, open exception visibility and a clean authority handover. MAS materials on third-party risk and operational resilience emphasise governance, sound risk management, external dependencies, response and recovery. Translate those expectations into observable outcomes for the VCC and each affected sub-fund.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority| Service | Proof of usable handover | Failure signal |
|---|---|---|
| Fund accounting | Positions, prices, accruals, journals and exceptions reload and reconcile | Only static statements are available |
| Investor records | Holdings, dealing history, documents and restrictions remain linked | Investor files lose transaction context |
| Payments | Authorities, templates, pending items and callback records are transferred | Open payments or approvers cannot be identified |
| Corporate records | Registers, filings, minutes and action logs are complete and readable | Records exist only inside a closed portal |
| Technology | Interfaces, credentials, keys and dependencies have named replacement owners | Service stops when one account is disabled |
Related guidance: building a board-ready outsourcing inventory
Build the test pack before asking for an export
- A service inventory showing systems, interfaces, data owners and downstream consumers.
- A data dictionary that defines fields, identifiers, time zones, status codes and file relationships.
- A cut-off instruction covering completed, pending, failed and cancelled activity.
- Representative samples for every sub-fund, share class, investor type and material transaction route.
- A receiving environment with a named loader, reviewer and reconciliation owner.
- A communications tree for directors, the manager, providers and affected operational teams.
- A defect severity scale and an agreed point for stopping or repeating the exercise.
Include both machine-readable and human-readable outputs where the service depends on structured records. The machine-readable file proves portability; the human-readable report lets an independent reviewer understand balances, status and approvals. Ask for configuration data as well as transactions. A successor cannot reproduce fee calculations, dealing rules, tolerance checks or reporting logic from final balances alone. Keep personal and confidential data within approved test controls, and use masked samples if live information is not necessary to prove the process.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: mapping critical VCC services before an outage
Run the handover as a controlled timeline
- PrepareFreeze the test scope, cut-off, sample population, responsibilities, security controls and success criteria before the outgoing provider creates files.
- DeliverRecord when each file, report, credential inventory and open-item schedule arrives, including its version, checksum or other integrity evidence.
- LoadImport the data into a separate receiving environment and document every transformation, default value, rejected record and manual correction.
- ReconcileCompare positions, cash, investor holdings, transactions, accruals, exceptions and authorities to the agreed cut-off using independent source records.
- OperateSimulate one complete critical cycle such as NAV review, dealing, payment approval or investor reporting without relying on the outgoing portal.
- CloseApprove defects, retest material gaps, archive evidence and update the contract schedule, runbook and board action register.
Time each stage, but do not optimise only for speed. A fast export that omits exception history or cannot be loaded is not a successful handover. Record dependencies on people, proprietary tools and undocumented judgment. If the outgoing provider must explain a field or repair a script during the test, capture that dependency and decide whether it belongs in the standing procedure. Where several providers share the process, test the interfaces between them rather than declaring each component ready in isolation.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeReconcile the evidence and classify defects
| Severity | Example | Required response |
|---|---|---|
| Critical | A balance, authority or investor record cannot be reconstructed | Stop approval, contain the risk and repeat after remediation |
| High | A material interface or open-item history needs manual rebuilding | Assign an owner, deadline and independent retest |
| Moderate | Documentation is incomplete but the service can be reproduced | Correct the runbook and verify the next export |
| Low | Presentation or naming differs without affecting completeness or control | Record and correct in routine maintenance |
Reconciliation should trace both totals and lineage. Matching a cash total does not prove that transactions, sub-fund attribution, approval history and outstanding items are correct. Use control totals for completeness, then sample individual records from source through export, transformation and reload. Retain the reason for any accepted difference. A defect is not closed because a provider says it is fixed; the receiving team should reproduce the corrected outcome from a new delivery or a controlled patch.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: exercising audit rights over a service provider
Approve access removal and the residual-risk pack
- All critical reconciliations are signed by owners independent of file preparation.
- Pending transactions, complaints, breaks and corporate actions have receiving owners.
- Bank, custody, portal, file-transfer and privileged access lists are current.
- Data retention, deletion and return obligations are mapped to evidence.
- Successor and outgoing providers agree the final cut-off and responsibility split.
- Residual defects have explicit acceptance, compensating controls and review dates.
- The board receives the decision, not just the project status report.
Access revocation should follow the approved cut-over sequence. Removing access too early can strand open activity; leaving it open creates an unnecessary pathway into VCC data or assets. Use a named authority to approve each class of access, verify removal independently and retain evidence from the relevant system. The final pack should state what was tested, what was not tested, the unresolved defects, the fallback option and the point at which the exercise will be repeated.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: VCC compliance checklist
Frequently asked questions
How often should a VCC test a provider exit plan?
Set the frequency by criticality and change. Repeat after a material system migration, service-scope change, merger, persistent control failure or new dependency. A lighter periodic test can confirm that contacts, exports and access records remain current.
Can the outgoing provider run the entire test?
The provider can create exports and explain its system, but the VCC or manager should own success criteria and independent reconciliation. A handover is not proven until a receiving team can understand and use the information.
Does a contract clause prove data portability?
No. A clause establishes rights and responsibilities, but it does not show that the files are complete, documented, timely or reloadable. The practical test exposes proprietary formats, hidden dependencies and missing configuration.
Should live personal data be used in the exercise?
Use only what is necessary and approved. Masked or synthetic data may prove many technical steps, but selected live records may be needed for reconciliation. Apply the relevant confidentiality, security and data-protection controls.
What should directors approve after the test?
Directors should receive the scope, critical outcomes, material defects, remediation owners, residual risks, fallback arrangement and retest point. They should challenge whether the VCC can keep operating through an actual provider failure or replacement.
Official sources and further reading
- Third-Party Risk Management (Monetary Authority of Singapore)
- Achieving Operational Resilience for Financial Institutions in Singapore (Monetary Authority of Singapore)
- Risk Management Practices for Fund Management Companies (Monetary Authority of Singapore)
- 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.