Independent Singapore VCC guidance
Direct answer
Use one event record, then classify from verified facts. An incident is an event that affected a process, record, asset, decision or output. A caught error reached the wrong state but was detected before the next harmful step. A near miss is a credible failure path interrupted before the event occurred. A control weakness is a deficient design or operation found without a specific event. Record actual and potential impact separately, map every affected VCC and sub-fund, and update the classification as evidence develops.
At a glance
- Classify from the event chronology, not the reporter label or financial outcome alone.
- Record actual impact and credible potential impact as separate fields.
- Keep caught errors and near misses visible for pattern analysis.
- Map attribution and governance separately for each affected VCC or sub-fund.
Who this is for
- VCC managers, directors and providers using a common operational event process across investment, dealing, valuation, investor and technology activity.
Important exclusions
- A universal legal-reporting threshold, a conclusion about misconduct, or a substitute for urgent containment, specialist advice or required notification analysis.
Create one event record before choosing a label
Open the record with observable facts: what happened, when it was detected, the last known correct state, the systems and providers involved, the affected VCC or sub-fund, immediate containment and evidence location. Preserve original messages, files, logs, approvals and later corrections. Do not wait for root cause or financial impact before recording the event. An early neutral record allows operations, risk, compliance and providers to work from the same chronology while classifications remain provisional.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeInitial event record
- Describe the observed state without assuming cause, blame or materiality.
- Identify affected and potentially affected VCCs, sub-funds, investors and providers.
- Preserve original data, timestamps, communications and correction history.
- Record containment already applied and the person authorised to change it.
- Assign a coordinator while specialist owners assess separate consequences.
Related guidance: critical VCC service outage map
Apply a consistent classification test
Ask whether the process or record entered an incorrect state. If it did and an activity, book, asset, decision or output was affected, classify an incident. If the wrong state occurred but a control stopped the next harmful step, record a caught error and retain the actual control consequence. If the state never occurred but evidence shows a credible path that nearly passed through the controls, record a near miss. If testing reveals a deficient control without a specific event path, record a control weakness and link later events to it.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeEvent classification tree
- Incorrect state affected activityRecord an operational incident and assess actual as well as potential consequences.
- Incorrect state was caughtRecord a caught error, the detecting control and the next step that was prevented.
- Failure path was interrupted earlyRecord a near miss with evidence showing why the path was credible.
- Weakness found without an eventRecord a control deficiency and define the population that could be exposed.
Related guidance: VCC trading-error classification and correction
Work through a multi-sub-fund scenario
Assume an administrator receives one allocation file for two sub-funds. A reference-data change causes one security code to reject. Operations notices the rejection before settlement, resubmits the allocation and both trades settle correctly. The rejected instruction is a caught error because an incorrect operational state existed and required repair. It may also expose a broader control weakness if the same identifier feeds other portfolios. The second sub-fund is not automatically incident-free merely because its row processed; it belongs in the affected population if it shared the faulty dependency.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore| Fact | Classification effect | Required follow-up |
|---|---|---|
| One allocation row rejected | Actual caught error in the affected sub-fund process | Preserve reject, repair, approvals and downstream reconciliation. |
| Settlement completed correctly | Limits actual consequence but does not erase the event | Confirm cash, position, valuation and reporting stayed accurate. |
| A shared code table caused the reject | Potential cross-sub-fund control weakness | Test the complete dependency population and similar identifiers. |
| Another row passed through the same table | Potentially affected, not automatically clean | Verify the value and resulting books independently. |
| Alert reached an unmonitored mailbox first | Separate detection weakness | Repair ownership and escalation before relying on the alert. |
Assess consequence on separate dimensions
Record actual and credible potential impact for investment authority, cash, assets, valuation, investor dealing, disclosure, financial records, regulatory obligations, confidentiality, service continuity and reputation. Keep gross impact separate from recoveries or provider reimbursement. For umbrella VCCs, identify attribution by sub-fund and any shared umbrella consequence. A low financial loss can still expose a serious control gap, while a large market movement does not by itself prove an operational failure caused the loss.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore| Dimension | Actual-impact question | Potential-impact question |
|---|---|---|
| Assets and cash | What moved, failed or was unavailable? | What could have moved before detection? |
| Books and valuation | Which record or calculation was wrong? | Which reports or decisions could have used it? |
| Investors | Was dealing, allocation or communication affected? | Which investor outcome depended on the control? |
| Sub-fund segregation | Which pool bore the position, expense or liability? | Could the shared failure cross another pool? |
| Governance and obligations | Which decision or response was delayed? | What escalation could have been missed? |
Related guidance: VCC operational-loss attribution by sub-fund
Route parallel responses without duplicating facts
One operational event may require separate workstreams for trade correction, valuation, investor impact, technology recovery, provider escalation, conduct review, breach analysis or external notification assessment. Keep one factual chronology and link the specialist decisions rather than opening disconnected narratives. Each owner should record scope, authority, action and outcome. The event coordinator should resolve contradictions and ensure that a correction in one system reaches every affected record. Urgent containment should continue while classification is refined.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeParallel response model
- Contain the processStop further propagation, preserve evidence and protect accurate books, assets and decisions.
- Assign specialist assessmentsRoute operational, investment, technology, compliance and investor questions to clearly authorised decision owners.
- Maintain one chronologyLink findings and decisions to shared facts while preserving different professional conclusions.
- Reconcile correctionsVerify the final corrected state across manager, administrator, custodian, accounting and reporting outputs.
- Confirm governance closureRecord residual risk, remediation, communication and the authority that accepts the result.
Related guidance: VCC service-provider incident response
Reclassify openly as evidence changes
Classification is not a one-time label. A near miss may become an incident when later review finds a wrong report. An apparently isolated incident may reveal a control weakness across several mandates. Preserve the earlier label, the evidence available at that time and the reason for change. Trend both event type and causal control so recurring weaknesses are visible even when outcomes differ. Close only after impact, correction, required decisions, remediation and retesting are addressed or formally linked to active owners.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeFrequently asked questions
Is every near miss an operational incident?
A near miss is worth recording, but it is useful to distinguish it from an event that actually changed a process, record or output. The shared record can still route investigation and remediation without pretending that actual impact occurred.
How is a caught error different from a near miss?
In a caught error, the process reached an incorrect state and a later control prevented further harm. In a near miss, the incorrect state did not occur, but evidence shows a credible failure path that was interrupted earlier.
Can an event have no financial loss and still be significant?
Yes. It may reveal exposure involving investor treatment, mandate compliance, data, governance, service continuity or sub-fund segregation. Assess actual and potential consequence across dimensions rather than using booked loss as the only severity measure.
Who decides whether external notification is required?
The authorised compliance, legal or incident-governance owner should assess the facts against the applicable requirements and preserve the decision basis. The operational classification helps organise evidence but is not itself a universal reporting threshold.
When should an event be reclassified?
Change the classification when verified evidence changes whether an incorrect state occurred, what it affected or how widely the weakness extends. Preserve the earlier decision and reason for change so the chronology remains auditable.
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)
- Guideline SFA 04-G05 on Licensing and Conduct of Business for Fund Managers (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.