Independent Singapore VCC guidance
Direct answer
Treat investor-data handover as a controlled migration, not a file delivery. Define the authoritative record for every investor, VCC, sub-fund, class, holding, dealing event, payment instruction and evidence item. Map fields and identifiers, reconcile control totals, sample source documents, rehearse cutover and record every exception. After migration, compare both environments, prove critical workflows and communications, then remove legacy access only when ownership, retention and recovery responsibilities are accepted.
At a glance
- Define authoritative records before extracting data.
- Map meaning and lineage, not just column names.
- Use totals plus evidence-based samples.
- Rehearse cutover and exception handling.
- Close legacy access through recorded acceptance.
Who this is for
- VCCs moving transfer-agency or investor-record responsibilities between administrators, systems or internal teams.
Important exclusions
- A data-protection impact assessment, legal transfer mechanism or permission to move personal data without checking contracts, notices and applicable law.
Set the handover perimeter and authority
List the legal entities, umbrella, sub-funds, classes, investor accounts, nominees, contacts, holdings, transactions, bank instructions, due-diligence evidence, tax classifications, restrictions, complaints, open exceptions and communications included in the move. For each data family, name the current system of record, record owner, approved recipient and reason for transfer. A folder called investor data is not a perimeter. The same investor can have different rights, restrictions and positions across sub-funds or classes, so the migration unit must preserve those relationships.
Sources: Accounting and Corporate Regulatory Authority · Accounting and Corporate Regulatory Authority · Monetary Authority of Singapore| Data family | Authoritative source | Acceptance test |
|---|---|---|
| Identity and contacts | Approved investor master and evidence index | Field values trace to current source documents |
| Fund relationships | VCC, sub-fund, class and account hierarchy | Every account resolves to the correct legal fund layer |
| Holdings and dealing history | Register and transaction ledger | Opening position plus movements equals closing position |
| Payment instructions | Controlled bank-instruction record | Status, approval and change history remain visible |
| Open issues and restrictions | Workflow and exception registers | Owner, status, evidence and next action survive cutover |
Confirm who is authorised to extract, inspect, transform, accept and retain each record set. Limit working copies and record where they are stored. If the incumbent controls a key identifier, lookup table or evidence archive, surface that dependency early. The receiving operator should be able to explain the data using its own field dictionary before the live cutover. Unresolved scope items belong in a visible decision log, not in a later promise to send anything missing.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory AuthorityRelated guidance: VCC investor onboarding evidence map
Map fields, meaning and evidence lineage
Create a mapping that covers source field, business meaning, format, allowed values, transformation, destination field, evidence link, owner and validation rule. Similar labels can hide different meaning. Status may describe an investor, an account, a due-diligence review or a dealing instruction. A blank may mean not applicable, unknown, not collected or lost. Preserve these distinctions rather than converting every empty value to one default. Record code lists and calculation logic so the receiving team can interpret history after the incumbent is no longer available.
Sources: Monetary Authority of Singapore · Inland Revenue Authority of Singapore- Map stable identifiers before names, because names and contact details can change.
- Preserve VCC, sub-fund, class, account and transaction relationships explicitly.
- Document code values, date conventions, currencies, time zones and status meanings.
- Link critical decisions and restrictions to the evidence that supports them.
- Record transformations, defaults, rejected values and manual corrections.
- Assign an owner and acceptance rule to every material field group.
Do not migrate only the latest state when history explains authority or a restriction. A current payment instruction may need prior change evidence. A current holding may need transaction lineage. An accepted investor may have open refresh work or a condition that remains active. Decide what history moves into the live platform, what remains in a controlled archive and how users retrieve it. IRAS record-keeping material is useful for designing retrievable business records, while the operational transfer should also follow the VCC governance and data ownership agreed for the appointment.
Sources: Inland Revenue Authority of Singapore · Monetary Authority of SingaporeRelated guidance: VCC fund administrator continuity test
Reconcile populations, totals and samples
Use population counts and control totals to prove completeness, then use targeted samples to prove meaning and evidence. Counts should cover investors, accounts, holdings, transactions, open cases and attachments by VCC, sub-fund, class and status. Financial totals should reconcile by currency and relevant date. A perfect total can still hide swapped accounts or lost restrictions, so sample high-risk and changed records, not only random clean cases. Trace each sample from source evidence through transformation to the destination and expected workflow behaviour.
Sources: Accounting and Corporate Regulatory Authority · Monetary Authority of Singapore| Layer | Question | Evidence |
|---|---|---|
| Population | Did every expected record arrive once? | Counts by entity, fund layer, class, status and file type |
| Financial | Do positions and movements reconcile? | Holdings, cash references and transaction control totals |
| Semantic | Does each field retain its intended meaning? | Mapping tests, code translation and exception results |
| Document | Can users retrieve support for critical decisions? | Evidence-index samples and access tests |
| Workflow | Will the destination act correctly? | Subscription, redemption, change and reporting scenarios |
Maintain one exception register with source value, destination value, issue type, impact, proposed treatment, owner, approval and retest evidence. Do not correct source data silently during migration. If a factual error is verified, preserve the old value and correction basis. If meaning is disputed, hold the record or mark it visibly until the accountable owner decides. This prevents the project team from making investor or compliance decisions merely to achieve a clean migration dashboard.
Sources: Monetary Authority of Singapore · Inland Revenue Authority of SingaporeRehearse cutover and critical workflows
Run a rehearsal using the planned extraction point, transformation, loading sequence, controls and people. Time each dependency and include failure scenarios: a late file, corrupt attachment, unmatched account, changed bank instruction, open redemption or unavailable incumbent contact. Confirm the freeze window, new instruction route, investor communication, rollback boundary and authority to proceed. A rehearsal should produce evidence and changes to the plan, not merely a meeting conclusion that the team feels ready.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Freeze scopeConfirm included populations, open events, cutover point, channels, roles and conditions for proceeding or stopping.
- Extract and secureProduce controlled files, hashes or equivalent integrity evidence, inventories and approved access for named recipients.
- Transform and loadApply the approved mappings while capturing rejected records, defaults, changes and manual intervention.
- Reconcile and testComplete totals, samples, document retrieval and critical investor workflow scenarios before acceptance.
- Accept and containRecord residual issues, ownership, temporary controls, communication and any restricted operating state.
Critical workflow testing should use realistic records across more than one sub-fund and class where applicable. Test contact updates, evidence retrieval, payment-instruction change, subscription, redemption, restriction display, statement generation and issue escalation. Confirm that users can see the right information and cannot see unauthorised records. If a workaround is accepted, document its duration, owner, capacity limit and removal test. Temporary manual controls should not become permanent by silence.
Sources: Accounting and Corporate Regulatory Authority · Monetary Authority of SingaporeRelated guidance: VCC provider exit and handover plan
Accept ownership and close legacy access
Acceptance should state which populations passed, which exceptions remain, who owns them, what temporary controls apply and whether any activity is restricted. The receiving operator must accept not only files but also ongoing accountability for retrieval, correction, workflow and reporting. Keep the incumbent available for an agreed stabilisation route without allowing two uncontrolled systems to become simultaneous authorities. New activity should have one defined entry point and be reconciled if any parallel processing remains.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Signed acceptance identifies passed controls, residual issues and operating restrictions.
- New instructions enter through one approved channel and system of record.
- Legacy access is reduced, revoked or retained under named archive controls.
- Copies, credentials, shared folders and temporary migration tools follow an approved closure plan.
- Record retention and retrieval ownership is explicit for live and archived information.
- A post-cutover review confirms that exceptions and temporary controls are closing.
Close with an access and asset inventory. Include user accounts, service identities, shared mailboxes, portals, secure-transfer locations, keys, reports, archives and working copies. Obtain return, deletion or retention evidence appropriate to the arrangement and record unresolved items. The VCC should be able to retrieve its records and operate without depending on an orphaned account or a former provider employee. A later review should compare actual issues with rehearsal assumptions and improve the next transition plan.
Sources: Monetary Authority of Singapore · Inland Revenue Authority of SingaporeRelated guidance: VCC manager replacement data pack
Frequently asked questions
Is delivering a data file enough to complete the handover?
No. Completion requires a defined perimeter, field meaning, relationships, evidence links, control totals, exception treatment, workflow testing, acceptance and access closure. A file can arrive successfully while critical records remain unusable or incorrectly related.
Which records should be sampled?
Use both broad coverage and targeted risk. Include recent changes, open exceptions, restricted accounts, multiple sub-funds or classes, bank-instruction changes, complex ownership, incomplete evidence and records transformed manually during the migration.
Can the old and new systems run in parallel?
A bounded parallel period can support reconciliation, but one authority and one route for new activity should be clear. Record how duplicate changes are prevented, how differences are resolved and when legacy write access ends.
Who should approve migration corrections?
The accountable data or process owner should approve corrections under the agreed governance. Migration staff should not make investor, eligibility or authority conclusions simply to remove an exception. Preserve old values and the evidence supporting verified changes.
When may the incumbent provider lose access?
After acceptance confirms the receiving operator can retrieve records and run critical workflows, and after residual support, retention and archive arrangements are defined. Revoke or restrict access through an inventoried, evidenced closure process.
Official sources and further reading
- Understanding VCC features, eligibility and requirements (Accounting and Corporate Regulatory Authority)
- Post-registration guide for variable capital companies (Accounting and Corporate Regulatory Authority)
- Governance and Management of Variable Capital Companies (Monetary Authority of Singapore)
- 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.