Independent Singapore VCC guidance
Direct answer
Challenge static data before VCC NAV by identifying every standing field that can change valuation, ownership, income, expenses or settlement, then comparing it with an authoritative source and its effective date. Freeze unsupported edits, open an exception with the affected sub-fund and period, and calculate the NAV impact of both the current and proposed values. A maker should prepare the correction while an independent reviewer checks source, scope and downstream effects. Release NAV only when material exceptions are resolved or handled through an approved policy, and retain the old value, new value, reason, approver and system evidence.
At a glance
- Standing data can create valuation errors even when market prices are correct.
- Every correction needs source, effective date and affected-record scope.
- Sub-fund, class and currency boundaries must be explicit.
- The close-out test should prove downstream records agree.
Who this is for
- VCC administrators and managers controlling security masters, account masters, rate tables and other NAV standing data.
Important exclusions
- A valuation opinion on a specific asset or permission to override governing accounting and valuation policies.
Detect staleness before calculation begins
Use both time-based and event-based checks. A review date alone will not catch an instrument amendment, provider migration, class launch, corporate action or change in account ownership. Compare effective dates, recent trade confirmations, custody files, legal documents and approved fee schedules with the master record. Flag values copied from a predecessor system, fields lacking a source reference, manual defaults, securities with recent events and fields shared across multiple sub-funds. Set risk-based review frequency rather than refreshing every item mechanically. The detection report should identify the affected VCC, sub-fund, class, asset, record, field, current value, source date and reason for challenge so the team can prioritise consequences, not merely count aged records.
Sources: Monetary Authority of Singapore · Singapore Statutes Online- Scan fields past their review date.
- Compare event notices with unchanged master records.
- Identify defaults and manually entered values.
- Trace shared fields across sub-funds and classes.
- Rank exceptions by potential NAV and ownership impact.
Related guidance: VCC compliance checklist
Contain the exception without rewriting history
When a field is challenged, preserve the existing value and stop uncontrolled edits. Open a ticket with the source evidence, proposed value, effective date, affected transactions and expected downstream systems. Decide whether the current NAV run can continue using a documented provisional treatment or must pause. Restrict the change to the correct legal entity, sub-fund, class and instrument. A global master update can repair one record while corrupting many unrelated portfolios. If the issue affects prior periods, do not backdate the system merely to make reports agree. Reconstruct the history, calculate each affected period and route any pricing error or investor impact through the approved correction policy and professional advice.
Sources: Singapore Statutes Online · Monetary Authority of Singapore- FreezeRetain the old field and stop manual changes outside the controlled exception process.
- SourceObtain authoritative instrument, contract, custody or approved schedule evidence with an effective date.
- ScopeList every sub-fund, class, period, transaction and report that consumes the challenged value.
- DecideApprove the corrected value, prospective date and any historical remediation through independent review.
Work a stale coupon-basis scenario
Assume a bond in one sub-fund was amended from a fixed coupon to a floating formula, but the administrator security master still carries the original rate. The market price file is current, so the position appears normal, yet accrued income is wrong. The analyst should authenticate the amendment, confirm the effective date and position ownership, recalculate accrual under both values, and identify every NAV since the change. The custodian income expectation and ledger should be compared, but neither is accepted without reconciling the terms. The maker prepares the change and impact schedule. The reviewer checks the evidence, formula, currency, period and sub-fund. The decision then separates current NAV release from historical correction and investor treatment.
Sources: Monetary Authority of Singapore · Singapore Statutes Online| Control point | Evidence | Decision output |
|---|---|---|
| Instrument term | Authenticated amendment and identifier | Correct coupon formula |
| Effective date | Executed event record | First affected accrual date |
| Ownership | Custody and sub-fund ledger | Affected legal portfolio |
| Impact | Old-versus-new calculation by NAV date | Release and remediation decision |
Approve changes with maker-checker discipline
The change request should show the exact old and new values, source, effective date, reason, systems, portfolios, transactions, reports and testing. Separate data ownership from system access. The person requesting or entering the change should not be the only reviewer of a material field. Where a provider maintains the master, the manager and administrator still need a way to challenge evidence and confirm scope. Record rejected changes as well as approved ones so repeated requests do not bypass prior analysis. Emergency updates need the same evidence with accelerated escalation, followed by post-event review. A screenshot alone is weak proof because it may not show source, effective date or whether the final value reached every consuming system.
Sources: Monetary Authority of Singapore · Singapore Statutes OnlineRelated guidance: VCC provider directory
Reconcile every downstream use before closure
After the approved update, rerun or inspect the security master, position record, accrual, valuation, fee calculation, general ledger, investor capital account, custody comparison and reporting output that use the field. Confirm the correction did not change another class or sub-fund. Tie the final NAV impact to the exception schedule and decision. If prior values were affected, retain original and corrected calculations and the investor-remediation conclusion. Close only when the authoritative source, master value, transaction processing, accounting and reporting agree. Feed the root cause into onboarding, provider interfaces or review frequency. A recurring stale field is a process weakness, even when each individual amount falls below a reporting threshold.
Sources: Singapore Statutes Online · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Verify the final master value and effective date.
- Recalculate all affected accruals and valuations.
- Check other sub-funds and classes for unintended changes.
- Tie correction entries to the approved impact schedule.
- Update preventive controls and retain complete evidence.
Related guidance: Singapore VCC guide
Frequently asked questions
Is static data the same as market data?
No. Market data usually changes by valuation point, while static data describes standing attributes such as identifiers, terms, ownership, currency and fee settings. Either type can produce a NAV error.
Can the latest custodian file prove the correct value?
It is useful evidence but may repeat the same stale source. Reconcile the custodian record with the controlling instrument, contract, account or approved schedule and its effective date.
Should every old field stop NAV release?
Not automatically. Assess materiality, uncertainty, scope and policy. The release decision should document why the field is resolved, immaterial under the approved method, or subject to a safe provisional treatment.
Can a master-data correction be backdated?
Only through controlled analysis of the effective date and historical consequences. Do not overwrite history simply to align reports. Preserve original values, recalculate affected periods and route remediation properly.
Who should approve a material static-data change?
Use the authority defined by the valuation and data-control framework, with maker-checker separation. Complex ownership, legal terms or investor impacts may require manager, director, administrator, custodian and professional-adviser input.
Official sources and further reading
- Variable Capital Companies Act 2018 (Singapore Statutes Online)
- Guidelines on Liquidity Risk Management Practices for Fund Management Companies SFA 04-G08 (Monetary Authority of Singapore)
- VCC features, eligibility and requirements (Accounting and Corporate Regulatory Authority)
Discuss your fund, family office or trust structure
Contact Raffles Corporate Services about Singapore VCC setup, fund structures, family offices and corporate administration.
- Email: hello@rafflescorporateservices.com
- WhatsApp: +65 8501 7133
- WhatsApp: +65 9018 0072
Where legal assistance is required, we can coordinate an introduction to an associate independent law firm, with your consent. The law firm advises you under a separate engagement. Raffles Corporate Services is not a law firm. Tax, investment management and trustee services, where needed, require appropriately qualified or authorised providers.
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.