Independent Singapore VCC guidance
Direct answer
Treat a spreadsheet as critical when its failure could change a trade, payment, valuation, investor record, limit, filing or management decision. Put those files in a controlled inventory with one accountable owner, approved purpose, trusted inputs, protected formulas, access limits, version history and independent review. Test changes against known results before release, retain evidence for each production run, and reconcile outputs to authoritative records. Replace or retire files when complexity, volume or dependency makes proportionate spreadsheet control unreliable.
At a glance
- Classify files by decision impact and recoverability, not by whether they look technically complex.
- Separate input, calculation, review and release evidence so a correct output can be reproduced.
- Test formula and logic changes before the revised version enters a live process.
- Set migration or retirement triggers before a temporary spreadsheet becomes permanent infrastructure.
Who this is for
- Files used by VCC managers, administrators or oversight teams for calculations, reconciliations, approvals, reports, allocations or control evidence.
Important exclusions
- A claim that every spreadsheet needs the same controls, or a substitute for secure systems where the file cannot be governed reliably.
Inventory files by business outcome
Start with processes and decisions, not a search for every workbook. Ask where a file can influence an order, bank release, NAV input, allocation, investor statement, risk measure, regulatory response or board report. Record the business purpose, owner, users, storage location, data sources, downstream consumers, frequency and recovery need. Include files operated by service providers when the VCC or manager relies on their result. Remove duplicates only after confirming which version is authoritative.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore| Field | Control question | Evidence |
|---|---|---|
| Purpose | Which decision or record depends on the file? | Named process and downstream consumer. |
| Ownership | Who understands and approves its operation? | Accountable owner and trained backup. |
| Inputs | Where does each material value originate? | Source, cut-off and reconciliation method. |
| Logic | Which formulas, scripts or manual steps transform data? | Protected logic map and change history. |
| Output | Where is the result used or released? | Approval, interface and retained production evidence. |
Related guidance: VCC pricing and market data provider review
Tier the file by impact and control need
A visually simple file can be high impact if it creates a payment amount or investor allocation. Score the consequence of an incorrect result, the difficulty of detection, the number of users, manual touchpoints, formula complexity, data sensitivity, frequency and ability to reproduce the output. Use the tier to set review, testing, access, backup and evidence expectations. Reassess the tier when volume, purpose, logic, user base or downstream reliance changes.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeSpreadsheet risk tier
- Convenience onlyUse ordinary document controls when the file does not feed a controlled record or decision and can be recreated easily.
- Operational supportAssign ownership, protect key fields and retain enough evidence to review the supporting calculation.
- Critical decision inputApply independent testing, restricted release, production evidence, recovery planning and periodic control review.
- Control is no longer credibleFreeze non-essential change and begin migration to a more reliable governed process or system.
Control inputs, formulas and access
Separate raw inputs, transformation logic, review fields and final outputs where practical. Lock formulas and reference tables against accidental edits, restrict write access and avoid shared credentials. Validate source completeness, cut-off and entity or sub-fund identifiers before calculation. Make manual overrides visible with a reason, preparer and approver. Store the production file in a controlled location rather than relying on email attachments or personal folders that obscure the authoritative version.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeMinimum design controls
- Label the VCC, sub-fund, period, data cut-off, file version and accountable owner inside the controlled file.
- Protect formulas, reference tables and output ranges from unapproved or accidental editing.
- Validate row counts, totals, dates, identifiers, duplicates and missing values before calculation.
- Record every manual adjustment with rationale, supporting evidence, preparer and independent approver.
- Restrict production release to authorised users and retain the exact version used for the decision.
Related guidance: VCC report data lineage sign-off
Test every material change before release
Define the requested change, business reason, affected logic, test data, expected results and rollback route. Compare the revised file with the current production version using normal, boundary and error cases. Investigate every difference rather than accepting a new total because it looks plausible. The developer should not be the sole approver for a critical release. Give the approved version a unique identifier and preserve the old version so the prior output can be reconstructed.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeControlled release sequence
- SpecifyDescribe the requested change, affected calculation, owner, expected result and any connected output or process.
- DevelopMake the change in a non-production copy while preserving the current approved version and input evidence.
- TestRun normal, boundary, error and regression cases against known outcomes, recording every material difference.
- ApproveUse an independent reviewer to confirm purpose, tests, access, version identity and rollback readiness.
- ReleaseMove only the approved version into production, communicate the cutover and monitor the first completed run.
Related guidance: test VCC investment rules after a system release
Create evidence for each production run
A protected template does not prove that a particular run was complete or correct. Retain the source extract or reference, version identifier, run date, preparer, automated or manual checks, exceptions, reviewer and released output. Reconcile the result to the appropriate books, bank, custody, administrator or reporting record. When the file is rerun, explain what changed and link replacement output to the original. This evidence allows later review without relying on the operator’s memory.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: VCC control finding evidence closure
Prepare recovery and continuity
Maintain a recoverable approved version, required reference data, operating instructions and a trained backup. Test whether the file can be run from clean inputs without hidden links, unavailable drives, personal macros or one specialist’s knowledge. Define the point beyond which manual catch-up is unsafe because volume, time or missing data becomes excessive. Recovery should include reconciliation of delayed and duplicate processing, not just reopening the workbook.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeRecovery test evidence
- Approved file and reference data can be restored without a personal device or inaccessible account.
- A trained backup can follow the instructions and explain the main checks and failure points.
- Hidden links, external queries, macros and dependent files are identified and available.
- The test includes realistic volume, exceptions, review, output release and downstream reconciliation.
- Failures produce owned remediation and a retest rather than an unsupported statement of readiness.
Retire the file through a controlled cutover
Set retirement triggers for scale, performance, access, security, unsupported logic, repeated errors and excessive dependence on manual review. Before cutover, compare old and new results across representative periods and resolve differences. Archive the final approved file, logic, evidence and ownership history according to the records process. Remove production write access and update procedures, training and downstream links. Keep rollback authority bounded so the retired tool does not quietly return as an uncontrolled parallel process.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeFrequently asked questions
Does every spreadsheet need independent approval?
No. Apply controls proportionate to business impact. A file that affects a trade, payment, valuation, investor record, limit or external response deserves stronger independent review than a disposable convenience calculation.
Is password protection enough?
No. It may limit editing, but it does not establish trusted inputs, tested logic, authorised change, version identity, review evidence, backup or reconciliation to authoritative records.
Who should own a critical spreadsheet?
Assign one accountable business owner who understands the process and consequences, plus technical or operational support and a trained backup. Ownership should not rest solely with the person who built the file.
How should manual overrides be controlled?
Make them visible, state the reason, link supporting evidence, identify the preparer and obtain independent approval before release. Review recurring overrides as possible design or data problems.
When should a spreadsheet be replaced?
Replace or redesign it when scale, complexity, sensitivity, error history, recovery weakness or dependence on one person makes proportionate control unreliable. Use a tested cutover and preserve the prior evidence.
Official sources and further reading
- Risk Management Practices for Fund Management Companies (Monetary Authority of Singapore)
- Technology Risk Management Guidelines (Monetary Authority of Singapore)
- Guidelines on Individual Accountability and Conduct (Monetary 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.