Independent Singapore VCC guidance
Direct answer
Map concentration by service and dependency, not only by provider name. List each VCC and sub-fund service, its provider, critical system, data source, bank or custodian connection, key location, specialist staff and material fourth parties. Then identify which single failure could interrupt several services or sub-funds together. Assess peak exposure, recovery objectives, substitutes, data portability and exit lead time. Accept, reduce or transfer the concentration through an explicit decision, and monitor changes rather than assuming separate contracts create real diversification.
At a glance
- A single group can appear as several vendors while relying on one platform, team or data centre.
- Review sub-fund impact separately, then aggregate shared dependencies at umbrella and manager level.
- A backup is credible only when access, data, capacity, authority and operating steps have been tested.
- Record why concentration is accepted and which signals trigger reduction or escalation.
Who this is for
- Umbrella and standalone VCCs whose administration, custody, banking, technology, compliance or data services create shared operational dependencies.
Important exclusions
- Investment portfolio counterparty limits, legal conclusions about outsourcing, or a claim that using one provider is automatically inappropriate.
Map services before provider names
Begin with the outcomes needed by each sub-fund: trade capture, cash movement, custody, investor dealing, NAV, financial records, compliance monitoring and reporting. For each service, record the contracted provider and the operating dependencies behind it. Two providers may use the same cloud platform, pricing source, bank, file gateway, offshore processing centre or specialist. Conversely, one provider may run genuinely separated systems and teams. The map should show the failure path instead of assuming concentration from branding alone.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore| Layer | Record | Concentration question |
|---|---|---|
| Service | Outcome and affected VCC or sub-fund | Which fund activity stops if it fails? |
| Provider | Contracting entity and operating team | Are multiple services owned by the same decision chain? |
| Technology and data | Platform, interface and key data source | Do separate providers share the same dependency? |
| Fourth party | Material subcontractor or infrastructure | Can the manager see and challenge changes? |
| Recovery | Alternative, data export and tested capacity | Can service continue within the required window? |
Related guidance: board-ready VCC outsourcing inventory
Measure common failure exposure
Assess how many critical services and sub-funds depend on the same failure point at the same time. Consider peak dealing days, valuation cut-offs, capital calls, financial closes and staff holidays. Separate volume concentration from knowledge, access, location and data concentration. A small contract can still be critical if only one specialist understands the interface or only one route can release payments. Record actual controls and tested capacity rather than contractual promises alone.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeCommon-failure questions
- Which sub-funds share the same processing queue, platform, credentials or specialist team?
- Which services depend on one pricing source, bank connection, file route or data field?
- Can an incident at one provider prevent another provider from operating?
- Does the recovery route have current data, authority, licences and enough capacity?
- Which reporting or investor decisions could proceed with stale or partial information?
Related guidance: critical VCC service outage map
Work a three-sub-fund scenario
Assume three sub-funds use one administrator. Sub-fund A and B use the administrator pricing engine, while C receives an external price file that still enters the same NAV platform. A and B use different custodians, but all three send instructions through one managed file gateway. The administrator contract lists a backup site, yet the backup uses the same identity service. The concentration is therefore wider than NAV production: one identity or gateway failure can block data intake for all three sub-funds even though vendors and custodians differ.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore| Fact | Hidden dependency | Decision response |
|---|---|---|
| Different custodians for A and B | Shared instruction gateway | Test an alternate verified instruction route for both custodians. |
| External pricing for C | Same NAV intake and identity service | Include C in platform and access outage scenarios. |
| Backup administrator site | Same identity provider | Verify independent access and recovery authentication. |
| One specialist owns interfaces | Knowledge and authority concentration | Cross-train, document and test a replacement operator. |
| All NAVs close together | Peak-time capacity concentration | Test recovery using combined volume, not one sample fund. |
Test alternatives instead of counting them
A second provider, backup site or manual route is useful only if it can receive current data, authenticate authorised users, process the service, communicate with connected parties and return complete records. Test the handoff at realistic combined volume. Include cut-off times, privacy and confidentiality, reconciliations and the return to normal service. Where a full substitute is impractical, design narrower resilience such as independent data copies, alternate communication, delayed non-critical work or the ability to calculate and approve a controlled estimate.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeAlternative-capability test
- ActivateConfirm authorised people can invoke the alternative route without relying on the failed dependency or credentials.
- Load dataUse current, complete and reconciled records for every affected sub-fund in the test population.
- Process volumeRun realistic combined demand across sub-funds, including exceptions, approvals and peak-time capacity constraints.
- ReconcileProve outputs reach books, cash, positions, investors and reports correctly, with all differences investigated.
- ReturnTest backlog transfer and controlled restoration to the primary service without omitted or duplicated records.
Make an explicit concentration decision
Concentration can be reasonable where scale, integrated data or control quality outweighs the residual risk and the VCC can recover within its needs. The decision should identify the exposure, affected sub-funds, tested mitigants, unresolved gaps, accountable owner and triggers for change. Alternatives may include splitting services, adding an independent data copy, renegotiating access and reporting, reducing peak overlap or preparing an orderly exit. Avoid a nominal diversification that adds interfaces but leaves the common failure point unchanged.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeConcentration decision
- Impact is low and recovery is provenAccept the concentration with routine monitoring, periodic retesting and notification of material dependency changes.
- Impact is material but mitigants are credibleAccept explicitly with documented tests, warning thresholds and suitable board or committee visibility.
- Recovery depends on the same failure pointRedesign the alternative route or reduce the shared dependency before relying on the proposed recovery.
- Exposure exceeds tolerance with no credible recoveryRestrict further concentration and begin a controlled transition with owners, milestones and continuity safeguards.
Related guidance: VCC provider exit and handover plan
Monitor changes across the provider chain
Update the map when a sub-fund launches, service moves, provider changes platform, a fourth party is added, an interface changes or a specialist leaves. Track incidents, queue age, capacity, control findings, test results and exit readiness. Require enough provider information to understand material dependency changes. Review the map after an outage or near miss, because the real operating path often differs from the contract diagram. Report the affected fund layer and shared dependency so governance owners can see concentration before it becomes a multi-fund failure.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: counterparty concentration across VCC sub-funds
Frequently asked questions
Is using one administrator for several sub-funds automatically too concentrated?
No. Assess critical services, common dependencies, impact and tested recovery. A single strong provider can be appropriate if the residual exposure is understood and governed.
What is a fourth-party dependency?
It is a material provider used by the contracted provider, such as infrastructure, data, processing or specialist support. The operational map should show where it can affect VCC services.
Do different contracts provide diversification?
Not necessarily. Separate contracts may still depend on the same platform, team, bank, identity service, data source or location. Trace the actual operating path and test whether one failure can interrupt both arrangements.
How should umbrella VCCs assess concentration?
Review impact and operating needs by sub-fund, then aggregate shared systems, providers, staff and data at umbrella and manager level. Keep component values visible so one high-risk sub-fund is not hidden by the combined result.
When should the concentration map be refreshed?
Refresh it after launches, provider or platform changes, material fourth-party changes, incidents, failed tests and other events that alter the dependency path. A regular review should also confirm that recorded alternatives remain accessible and capable.
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.