Independent Singapore VCC guidance
Direct answer
Create one log entry for every missing, stale, inconsistent, overridden or challenged valuation input that could affect a VCC or sub-fund NAV. Record the position, source, expected input, observed problem, potential effect, owner, decision authority, compensating control and release status. Keep facts separate from estimates. An item closes only when the accepted input or method is evidenced, the calculation is rerun, downstream reports reconcile and any broader affected population is reviewed.
At a glance
- Log the input problem before choosing a solution.
- Keep source facts, estimates and decisions distinct.
- Connect each item to positions and NAV outputs.
- Set explicit release and escalation status.
- Close through rerun and downstream reconciliation.
Who this is for
- Fund controllers, administrators, managers and valuation oversight teams preparing or reviewing VCC and sub-fund NAVs.
Important exclusions
- A valuation opinion, accounting conclusion or universal materiality threshold for a specific asset, fund document or investor arrangement.
Classify the unresolved input precisely
Open the record before selecting a workaround. Identify the VCC, sub-fund, share class if relevant, asset or liability, valuation point, expected source, required field and observed problem. Distinguish missing, late, stale, inconsistent, unauthorised, disputed and method-dependent inputs. These states lead to different responses. A delayed independent price is not the same as a price that conflicts with transaction evidence, and neither is the same as a model parameter whose governance owner has not approved a change.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore| Issue type | Evidence to retain | Initial control |
|---|---|---|
| Missing | Expected source, request history and dependency | Hold calculation or use only an approved contingency method |
| Stale | Prior value, age, market change and policy rule | Escalate fitness for the current valuation point |
| Inconsistent | Competing sources and reconciliation | Do not choose silently; route the difference |
| Challenged | Challenge, response and supporting analysis | Separate challenger, preparer and decision roles |
| Manual override | Original value, proposed value, reason and authority | Record approval and downstream impact explicitly |
Write the issue as an observable statement. For example, the expected file was not received by the calculation cut-off, or two approved sources contain different values for the same field. Avoid declaring that one source is wrong before analysis. Neutral language protects the evidence and helps oversight teams distinguish operational delay, data quality, methodology and judgment. It also lets trend reporting show whether recurring problems originate with a provider, asset type, model, timing design or unclear policy.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: VCC compliance checklist
Connect the input to affected outputs
Map every entry to the positions, calculations, classes, fees, dealing events, financial records and investor reports that consume the input. Record direction and plausible range where this can be assessed without inventing precision. The objective is to make the decision boundary visible, not to force a premature number. If the same source feeds several sub-funds, identify the complete population. An umbrella label should not conceal which pool, class or investor event is affected.
Sources: Accounting and Corporate Regulatory Authority · Monetary Authority of Singapore- Identify every position and legal fund layer that consumes the input.
- Record the calculation, report and operational event affected by the issue.
- Separate known amount, estimated range and unknown effect.
- Show whether other records use the same source or method.
- Assign a reviewer for completeness of the affected population.
- Keep investor-specific effects controlled but retrievable when needed.
Do not use materiality as a reason to omit the item. Record the issue first, then apply the fund-specific escalation and release framework. Several individually small uncertainties may aggregate, interact or indicate a wider control weakness. A clear log supports both item-level judgment and portfolio-level review. It also prevents teams from repeatedly solving the same source failure in private spreadsheets that never reach the people responsible for provider oversight or policy change.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: VCC sub-funds guide
Record authority, challenge and release status
For each entry, name the preparer, source owner, reviewer, decision-maker, executor and final checker. Record conflicts and any advice request. Use explicit states such as open, analysis in progress, approved contingency, NAV held, released with control, corrected and closed. A status called resolved is too vague if the calculation has not been rerun or downstream outputs remain unchanged. The decision record should state which input or method was accepted, why, for which valuation point and under what conditions.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority · Monetary Authority of Singapore- Detect and preserveCapture the expected input, observed issue, original values, timestamps, requests and affected position before intervention.
- Assess and containMap outputs, plausible effect, wider population and immediate restrictions without converting uncertainty into a fact.
- Challenge and decideRoute evidence and alternatives to documented authority, recording conflicts, conditions and rejected treatments.
- Recalculate and reconcileApply the approved input or method, rerun calculations and compare every affected output and communication.
- Close and improveAttach proof, review recurrence and assign provider, policy, system or timing remediation outside the item.
A release decision should be visible at item and NAV level. If release is held, identify who can remove the hold and which evidence is needed. If a controlled contingency is used, record its scope, expiry, sensitivity and follow-up. Do not let a calendar deadline become implied authority. Where the evidence does not support a responsible conclusion, maintain the hold or obtain the necessary specialist analysis rather than using a convenient prior value by default.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory AuthorityRelated guidance: VCC board effectiveness review
Close through recalculation and reconciliation
Closure requires more than receiving a late file. Confirm that the accepted input is complete, belongs to the right asset and valuation point, and was loaded correctly. Rerun the calculation, compare the result with the prior output, and reconcile fees, class values, dealing records, reports, accounting entries and communications that used the earlier state. If a NAV or report was already released, route correction and communication through the applicable governance rather than quietly replacing a file.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore- Accepted input or method has attributable evidence and decision authority.
- Calculation rerun uses the correct valuation point, position and fund layer.
- Difference analysis explains the change from the prior output.
- Fees, classes, dealing events, accounting and reports are reconciled.
- Any released output follows the approved correction and communication route.
- Related positions and recurring source failures have been reviewed.
Link root-cause work without keeping the valuation item artificially open forever. The item can close when the affected NAV chain is correct and evidenced, while a separate remediation action tracks provider performance, interface repair, policy clarity or timetable change. Trend reports should distinguish outstanding valuation risk from longer-term process improvement. This helps directors and managers focus on live release decisions without losing accountability for recurring weakness.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory AuthorityRelated guidance: umbrella VCC audit PBC tracker
Use the log as an oversight reference
Summarise open age, source, asset type, sub-fund, status, release impact, recurrence and remediation owner. Avoid ranking solely by count because one item can affect many positions or a critical investor event. Review whether one provider or manual interface creates repeated exceptions, whether contingency methods are becoming routine, and whether challenge is concentrated in one person. The log should support constructive challenge, not pressure teams to remove entries before the underlying evidence is complete.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeKeep the reference fields stable so the log can support period comparisons and provider reviews. At the same time, allow narrative evidence for unusual assets and methods. A rigid drop-down cannot capture every judgment, while free text alone prevents meaningful trend analysis. The best design combines controlled classifications with source-linked explanation, authority, calculation evidence and downstream reconciliation.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeFrequently asked questions
Should every late valuation input enter the log?
Use the approved significance and workflow design, but do not hide an issue merely because it was resolved quickly. The log should capture matters that need judgment, escalation, contingency, release control or evidence beyond routine automated retry.
Can the administrator choose between conflicting prices?
Only within the actual valuation policy, delegation and authority. Preserve both sources, record the difference and route any judgment or override appropriately. Operational convenience does not create decision authority.
Does an immaterial item need closure evidence?
Yes, proportionately. Materiality may affect escalation and release treatment, but the record should still show the accepted input or method, recalculation where applicable, and why the item no longer affects the relevant output.
When should NAV release be held?
Apply the fund-specific policy and authority. A hold is appropriate when evidence is insufficient for the authorised decision-maker to understand the affected population, potential effect, proposed treatment or conditions for a responsible release.
How is a recurring provider problem handled?
Close each affected valuation item through correction and reconciliation, then track the recurring cause in provider oversight or remediation. Use frequency, age, impact and manual intervention to decide whether controls, service terms or the provider should change.
Official sources and further reading
- Valuation Practices for Fund Management Companies (Monetary Authority of Singapore)
- Governance and Management of Variable Capital Companies (Monetary Authority of Singapore)
- Understanding VCC features, eligibility and requirements (Accounting and Corporate Regulatory Authority)
- Legal obligations of a VCC director (Accounting and Corporate Regulatory Authority)
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.