Independent Singapore VCC guidance
Direct answer
Build the exit plan before serving notice. Freeze the contractual scope, list every deliverable, system, credential route, data set, open item and downstream dependency, then assign an accountable VCC owner and successor acceptance test to each. Run old and new operating paths in parallel where risk justifies it, reconcile data at a stated cutover point, change authorities and access deliberately, and close only when the successor can reproduce critical outputs without the departing provider’s memory or systems.
At a glance
- Start with continuity and evidence, not the notice letter.
- Map cross-provider dependencies and open work before choosing a cutover date.
- Accept data through reconciled outputs, not a file-count total.
- Remove access only through a controlled sequence with recovery owners.
- Retain a defensible closure record after the commercial relationship ends.
Who this is for
- VCC directors and operating teams preparing to change a critical external provider or test exit readiness.
Important exclusions
- Contract termination advice, emergency regulatory notifications, insolvency steps or a decision to terminate a provider without the relevant approvals.
Open the exit plan before notice
Provider oversight remains part of the VCC’s governance even when work is outsourced. Start by identifying the service, affected VCC and sub-funds, contractual notice and assistance terms, retained responsibilities, decision authority and immediate continuity risks. Do this before notice so the departing provider cannot become the only source of the information needed to plan its own exit.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Confirm who can decide, sign, notify and instruct for the VCC and every affected account or service.
- Collect the current agreement, schedules, amendments, service levels, data terms, business-continuity commitments and exit-assistance clauses.
- List live cycles, open incidents, unresolved reconciliations, complaints, filings, audit queries, tax work and investor events.
- Identify concentration risks where another provider depends on the departing provider’s data, approval or system access.
- Create a fallback route for critical work if cooperation, staff availability or system access deteriorates after notice.
Use separate commercial and operational tracks. Commercial discussions address notice, charges, disputed scope and liability. The operational plan protects investors, records, filings, cash, valuation and provider hand-offs. Linking the tracks is necessary, but making continuity conditional on resolving every commercial dispute is dangerous. Record disputed items without letting them obscure the minimum handover needed to operate.
Sources: Monetary Authority of Singapore · Inland Revenue Authority of SingaporeRelated guidance: VCC provider directory · VCC provider service-level escalations
Inventory data, access and dependencies
| Asset | Fields to record | Acceptance evidence |
|---|---|---|
| Data and documents | Authoritative owner, format, period, VCC or sub-fund scope, version and retention basis | Inventory-to-delivery reconciliation and sample retrieval |
| Systems and interfaces | Platform, administrator, users, feeds, keys, reports, backups and export method | Successful successor access and output comparison |
| Authority and access | Signatories, portal roles, approvers, contact records and emergency recovery owner | Approved change record and post-change access test |
| Open work | Task, deadline, amount, exception, evidence, preparer, reviewer and next decision | Successor acceptance with no orphaned item |
| Provider network | Inputs received, outputs sent, timing, format and escalation contacts | End-to-end hand-off test across affected providers |
Distinguish authoritative records from convenience copies. A shared drive export may contain reports but omit configuration, approval history, comments, transaction lineage or evidence stored inside the provider platform. For each record family, define what complete means, which version prevails and how the VCC will produce it after access ends. Do not store passwords in the inventory; record the approved access and recovery mechanism.
Sources: Accounting and Corporate Regulatory Authority · Inland Revenue Authority of SingaporeBuild a dependency map from inputs to outputs. For example, a bank or custodian feed may enter the administrator’s ledger, drive valuation, support investor statements, feed audit schedules and reconcile to financial statements. Moving only the final report leaves the successor unable to reproduce the result or investigate a later question. Each critical output needs its inputs, transformations, approvals and exception history.
Sources: Monetary Authority of Singapore · Inland Revenue Authority of SingaporeRelated guidance: VCC books and records location map
Run a controlled cutover
- BaselineFreeze the inventory, open-item list, authorities, balances, latest approved outputs and planned transaction calendar at an agreed reference point.
- TransferDeliver data and documents in agreed formats with manifests, checksums or control totals, scope labels and named sender and recipient.
- ReproduceHave the successor rebuild critical reports, balances, investor records, filings and provider interfaces without relying on informal explanations.
- Parallel controlCompare old and new outputs for a risk-based period and route differences to named owners before the cutover becomes final.
- Authority switchChange portal roles, bank mandates, distribution lists, system access and provider instructions in the approved sequence.
- CloseObtain acceptance, preserve unresolved commercial items separately, revoke residual access and archive the final evidence pack.
Choose the cutover point around the operating calendar. Avoid changing a critical provider immediately before a dealing day, valuation, investor distribution, audit close or filing unless the current provider creates the greater risk. Record which events will remain with the outgoing provider, which move to the successor and who reconciles the boundary. A date alone is not a cutover plan.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory AuthorityRelated guidance: fund administrator transition checklist
Prove successor readiness
Acceptance should be based on tasks the successor can perform. Select realistic production tests: retrieve an investor file, reproduce a NAV support pack, trace a cash movement, prepare a board report, answer an audit query, produce a sub-fund ledger, update an authorised contact and reconstruct an exception. Include older and closed items because recent work may still be accessible through temporary overlap.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority · Inland Revenue Authority of Singapore| Test | Pass condition | Escalation if failed |
|---|---|---|
| Record retrieval | The correct authoritative record is produced with scope, version and approval history. | Identify missing source, owner and recovery route. |
| Balance reproduction | Opening positions and material outputs reconcile to the agreed baseline. | Hold cutover for the affected process and investigate differences. |
| Authority execution | Approved users can instruct and unauthorised users cannot access or approve. | Activate recovery owner and correct mandates or roles. |
| Provider hand-off | Inputs and outputs move end to end on the required timetable. | Use the fallback interface and escalate the broken dependency. |
| Exception management | Open issues retain history, evidence, owner, decision and target date. | Reject closure until every material exception is accepted. |
The departing provider should confirm what it delivered and what it did not. The successor should confirm what it accepted and which qualifications remain. The VCC owner then decides whether an exception can remain open after cutover. This three-way record prevents “handover complete” from meaning only that a link was sent or an invoice was paid.
Sources: Monetary Authority of Singapore · Inland Revenue Authority of SingaporeClose access and retain evidence
- Confirm final deliverables, open exceptions, disputed items and the owner of every post-cutover action.
- Revoke or amend user access, portal roles, bank mandates, distribution lists, API connections and emergency credentials in the approved order.
- Obtain deletion or retention confirmations where contract and applicable obligations call for them, without destroying records the VCC still needs.
- Archive contracts, notices, inventories, data manifests, reconciliations, acceptance tests, approvals, correspondence and closure confirmations.
- Update the books-and-records map, provider register, responsibility matrix, incident log, board actions and next continuity test.
Keep the post-exit evidence independent of the departed provider’s platform. The VCC should be able to show what was transferred, how completeness was tested, which authorities changed, which access ended, what remained unresolved and how ongoing records are now produced. Retention decisions should follow the relevant corporate, tax, contractual and case-specific requirements.
Sources: Accounting and Corporate Regulatory Authority · Inland Revenue Authority of SingaporeFinish with a lessons review. Compare actual effort with the exit clauses, inventory and service history. Feed gaps into future provider contracts, onboarding, data portability, business continuity and service-level controls. A well-run exit should make the next provider relationship more resilient, not merely replace one name with another.
Sources: Monetary Authority of SingaporeRelated guidance: evidence-based VCC provider review
Frequently asked questions
When should a VCC provider exit plan be created?
Create the baseline during provider onboarding and refresh it during service reviews, not only when termination is likely. A current inventory of data, systems, authorities, dependencies and recovery methods gives the VCC options during poor performance, an incident, staff loss or an orderly commercial change.
Is a data export enough to complete the handover?
No. The VCC should reconcile the delivered population, confirm versions and scope, test retrieval, reproduce critical outputs and preserve approval and exception history. A folder of files may be incomplete or unusable even when the file count matches a manifest.
Should old and new providers operate in parallel?
Use a risk-based answer. Parallel processing can expose differences before final cutover, but it also creates duplicate instructions and version risk. Define which output prevails, who reconciles differences, how long overlap lasts and what conditions end or extend it.
Who should accept the provider handover?
A named VCC owner should accept it with input from the successor, affected providers, finance, compliance and directors as appropriate. The departing provider confirms delivery, the successor confirms usability, and the VCC decides whether any remaining exception is acceptable.
When should the departing provider lose access?
Remove access through an approved sequence tied to the cutover and recovery plan. Ending access too early can disrupt operations; leaving it open creates security and authority risk. Test new access first, preserve evidence, revoke old rights and verify that revocation worked.
Official sources and further reading
- Governance and Management of Variable Capital Companies (Monetary Authority of Singapore)
- Legal obligations of a VCC director (Accounting and Corporate Regulatory Authority)
- Post-registration guide for variable capital companies (Accounting and Corporate Regulatory Authority)
- Record Keeping Requirements (Inland Revenue Authority of Singapore)
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.