Independent Singapore VCC guidance
Direct answer
Run a non-cash rehearsal that follows one test subscription from receipt through eligibility checks, cut-off, bank and administrator records, valuation, approval, share issuance, register update and investor output. Add at least one late or inconsistent input so the team proves its exception path, not only the happy path. Launch only after every handoff reconciles, access works for primary and backup roles, and each unresolved issue has an owner and an explicit launch consequence.
At a glance
- Use controlled test data and stop before any live transfer or share issue.
- Trace one transaction through every system and approval, not separate departmental demos.
- Rehearse exceptions involving cut-off, cash, identity, price or file mismatch.
- Reconcile investor, bank, administrator and member records before declaring readiness.
- Treat unresolved ownership or access gaps as launch decisions, not minor notes.
Who this is for
- New standalone VCCs and umbrella sub-funds preparing for their first subscription and valuation cycle.
Important exclusions
- A live investor transaction, legal approval of offering documents or a substitute for provider acceptance testing.
Define a safe rehearsal boundary
Use fictional investor and transaction data, read-only bank evidence or sandbox outputs, and a clearly marked rehearsal date. No participant should send money, issue shares, alter the live register or release a live investor notice. Freeze the assumed fund, class, currency, dealing point, cut-off, valuation inputs, approval roles and expected output before the exercise starts. A changing scenario makes it impossible to tell whether the process or the test design caused a mismatch.
Sources: ACRA · ACRARehearsal boundary checks
- Test investor, account and transaction identifiers cannot be mistaken for a live instruction.
- The assumed fund, sub-fund, class, currency and dealing point are frozen.
- Every participant knows which systems are sandbox, read-only or represented by controlled evidence.
- A stop rule prevents any payment, trade, share issue, registry action or investor communication.
- The observer records outcomes without correcting the process silently during the run.
Freeze the source data and authority map
Create a single rehearsal pack containing the approved test subscription, investor status, fund and class terms, bank evidence, valuation file, fee assumptions, sign-off matrix and output templates. Mark the source owner for each item. The manager, administrator, directors or delegated approvers may own different decisions; the rehearsal should use the actual agreed authority model. If participants cannot identify who may accept, reject, price, release or amend an item, record an authority failure instead of inventing a convenient approver.
Sources: MAS · ACRA| Decision | Expected role | Evidence |
|---|---|---|
| Accept dealing instruction | Role named in the operating model | Timestamped instruction and eligibility status |
| Confirm cash status | Bank or operations control owner | Account-level evidence matched to the test reference |
| Approve valuation exceptions | Approved valuation decision-maker | Exception record, rationale and sign-off |
| Release NAV or dealing output | Named release role | Final file, version and approval timestamp |
| Update member record | Transfer-agency or register owner | Reconciled test entry and control total |
Related guidance: VCC first-close document room
Walk one subscription end to end
Start when the designated channel receives the test instruction. Record the received time, completeness check, investor-status result, fund and class mapping and expected dealing point. Pass the same transaction reference into cash checking, administrator input, valuation and register output. Avoid re-keying different identifiers for each team. The observer should be able to reconstruct the transaction from the original instruction to the final test statement without asking participants which spreadsheet or email was authoritative.
Sources: ACRA · ACRAFirst dealing-day rehearsal flow
- ReceiveCapture the controlled instruction through the designated channel and preserve its timestamp, version and transaction reference.
- ValidateCheck investor readiness, document completeness, fund and class mapping, dealing eligibility and required approvals.
- MatchReconcile the test cash evidence and transaction reference to the instruction without using an unexplained suspense item.
- PriceProcess the valuation file, exceptions and approval route using the same method planned for the live cycle.
- IssueProduce the test share entry, register update and investor output, then reconcile units, value and identifiers.
Related guidance: VCC subscription cash release checklist
Inject exceptions before launch
A rehearsal that contains only perfect inputs proves that the teams can follow a script. Add controlled exceptions one at a time: an instruction received near cut-off, cash with a mismatched reference, a stale valuation input, an unavailable approver, an incorrect class code or a failed output transfer. Observe who detects the issue, what is paused, who decides, how the decision is documented and how all affected records are reconciled after resolution.
Sources: MAS| Injected issue | Control being tested | Acceptable evidence |
|---|---|---|
| Late instruction | Cut-off and dealing-point decision | Timestamp, decision authority and consistent downstream status |
| Cash mismatch | Account and transaction reconciliation | Held status, investigation and matched resolution |
| Price exception | Valuation challenge and approval | Source evidence, rationale and approved outcome |
| Unavailable approver | Backup authority and access | Verified backup path or documented stop decision |
| Class-code error | Static-data validation | Rejected input, corrected source and downstream reconciliation |
Reconcile every output
Compare the administrator’s transaction and unit output with the test bank evidence, valuation result, register entry, investor statement and control totals. For an umbrella VCC, confirm that the sub-fund and class remain consistent in every artifact. A correct total can still conceal a wrong allocation, so reconcile identifiers and ownership as well as value. Keep the original failed file and the corrected version to show the exception path and prevent the repaired artifact from erasing evidence of the problem.
Sources: ACRA · ACRAEnd-of-cycle reconciliation
- Transaction reference is identical or traceably mapped across every participating system.
- Fund, sub-fund, class, currency, investor and account identifiers agree.
- Cash, price, units and value reconcile to the approved test outcome.
- Register and investor output use the final approved information and version.
- Rejected or superseded files remain identifiable and cannot be released accidentally.
- Every exception has a recorded decision, owner, downstream check and closure evidence.
Related guidance: VCC register of members checklist
Make a go or no-go decision
Close the rehearsal with a short readiness decision. Separate defects that block launch from improvements that can be completed under a controlled post-launch plan. A blocker includes an unowned approval, inaccessible system, unreconciled output, unclear fund or class mapping, failed backup role or unresolved legal or investor-status question. Assign each issue an owner, evidence requirement and retest. The decision record should identify who accepted any residual operational risk and why the first live cycle remains controlled.
Sources: MAS · ACRARelated guidance: VCC launch readiness assessment
Frequently asked questions
Is a first dealing-day rehearsal the same as launch readiness?
It is one focused part of launch readiness. Incorporation, documents, provider appointments, accounts, distribution permissions and governance may all need separate confirmation. The rehearsal tests whether an approved investor transaction can move through the operating chain and produce reconciled records without a live financial or registry consequence.
Should the team use real investor data?
Prefer fictional or properly masked data designed for the test. The record should be realistic enough to exercise validations but unmistakably non-live. If any production system requires personal data for testing, use the organisation’s approved privacy, security and access process and keep the scope to the minimum necessary.
What exceptions should be tested first?
Choose exceptions that can stop or misstate a dealing cycle: a late instruction, unmatched cash, wrong fund or class, stale price, unavailable approver and failed file transfer. Add strategy-specific scenarios later. The aim is to prove detection, authority, pause, correction, communication and reconciliation rather than to create the largest possible test library.
Who should observe the rehearsal?
Use an observer who understands the intended workflow but is not responsible for fixing each step during the exercise. The observer records timestamps, handoffs, missing evidence, informal workarounds and inconsistent decisions. Control owners can then validate the findings and agree remediation and retesting after the run.
When is the VCC ready for its first live dealing day?
Readiness exists when the end-to-end test reconciles, planned access works for primary and backup roles, exceptions follow an approved path, and no unresolved issue undermines authority, investor eligibility, fund or class mapping, valuation, cash control, register accuracy or release. The accountable launch body should record the decision and any bounded residual actions.
Official sources and further reading
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.