A creditor of one sub-fund cannot touch another sub-fund's assets, even though both sit inside the same corporate entity. Section 29 of the Variable Capital Companies Act 2018 is the provision that makes it true - and it's worth understanding exactly where the wall stands, because "ring-fencing" gets thrown around loosely and the statute is more specific than the marketing.
The phrase "ring-fencing" appears in almost every VCC pitch deck. It rarely comes with a citation. Section 29 is the actual mechanism - a statutory provision that does one specific job, with defined limits on both sides of what it covers and what it doesn't.
What the old way looked like
Before the VCC framework existed, a Singapore manager wanting real legal separation between strategies had two options. Incorporate a separate company for every strategy - separate audit, separate registered office, separate banking relationship, separate board meetings, multiplied by however many strategies you're running. Or use a unit trust structure, which offers less of the corporate governance apparatus institutional investors expect.
- Four separate companies
- Four annual audits
- Four registered office relationships
- Four sets of banking infrastructure
- Four board meeting calendars
- Four separate compliance filings
- One corporate umbrella
- One governance layer
- One administrator relationship
- Four legally separate sub-funds
- Same statutory firewall between them
- One MAS-licensed manager
Section 29 exists specifically to let one VCC umbrella house four sub-funds instead - one corporate shell, often one administrator relationship - while keeping the same firewall between them that separate companies would provide.
The mechanism, concretely
Section 29 of the VCC Act does three things in sequence. Understanding the sequence matters more than memorising the label.
"The assets of a sub-fund of a VCC are available only to meet the liabilities of, and claims against, the VCC that are attributable to that sub-fund, and are not available to meet liabilities of, or claims against, the VCC that are attributable to any other sub-fund of the VCC."
What the wall doesn't cover
Section 29 is a liability segregation provision. It is not a guarantee of returns, a protection against poor underwriting, or a shield against losses within a sub-fund itself. The wall runs between sub-funds - it does not run between a sub-fund and its own investment risk.
| Scenario | Does Section 29 apply? | What actually governs |
|---|---|---|
| Sub-Fund B creditor claims Sub-Fund A's assets | Blocked | Section 29 - statutory bar on cross-sub-fund recourse |
| Sub-Fund A loses 40% of its value | Not covered | Investment risk - governed by the fund's strategy and the manager's underwriting |
| VCC-level liabilities (e.g. umbrella audit fees) | Partial | VCC Act s.29(4) - umbrella-level costs can be allocated across sub-funds per the fund's constitutional documents |
| Manager misconduct affecting one sub-fund | Not covered | MAS conduct requirements, fund documents, and civil liability - not Section 29 |
| Investor in Sub-Fund A redeems during stress | Not covered | Redemption terms in the sub-fund's offering documents |
Why this matters for a multi-strategy investor
If you're allocating to a private credit strategy and a structured income strategy through the same VCC umbrella, Section 29 means a default event in the private credit sub-fund - however bad - cannot be satisfied out of the structured income sub-fund's assets. Your structured income allocation is not collateral for someone else's credit exposure.
That protection is unconditional. It doesn't depend on the manager maintaining clean books (though they must). It doesn't depend on a court ruling in your favour in a specific jurisdiction. It is written into the statute that governs the VCC's existence.
The practical test: When a manager says their VCC is "ring-fenced," ask which section of the VCC Act they're referring to. If the answer is Section 29, the mechanism is statutory and unconditional between sub-funds. If the answer is "our fund documents provide for it," that's contractual - a different and weaker form of protection.
The one administrative condition that matters
Section 29 requires that assets and liabilities be properly attributed to sub-funds in the VCC's books. This is not a heavy operational burden - it's standard fund administration practice. But it is a condition. A VCC that commingles sub-fund assets in its accounts - even inadvertently - creates a factual dispute about which assets belong to which sub-fund, which is exactly the kind of dispute Section 29 is designed to prevent.
This is why the quality of a VCC's fund administrator matters. The statutory protection is robust; the administrative hygiene that preserves it is the manager's responsibility.