The last two ongoing conditions behind a Section 13O/13U exemption sit squarely on a fund accountant's desk rather than a portfolio manager's or a company secretary's: keeping VCC sub-funds legally segregated in the books, and assembling the annual renewal pack that proves everything held up over the period. They are separate problems, but they compound each other — a segregation failure discovered at renewal is far more expensive to unwind than one caught the week it happened.
What VCC sub-fund segregation actually requires
Most Singapore family offices run their structure through a VCC umbrella with multiple sub-funds, often with different 13O or 13U elections per sub-fund. The entire regulatory value of that structure rests on one guarantee: sub-funds carry no cross-liability. One sub-fund's creditors cannot reach another sub-fund's assets — but only if the accounting actually enforces that separation, not just the constitutive documents.
That means each sub-fund needs its own general ledger, its own trial balance, and its own financial statements — not a shared chart of accounts with a sub-fund "tag" attached to each line. A tag is a UI convention that a mis-keyed entry can silently violate. Real segregation means the system refuses to let a transaction, journal entry or allocation reference more than one sub-fund in the first place — validation at the schema level, not a rule someone is supposed to remember.
What this looks like without hard enforcement: a shared ledger with sub-fund tags, where a mis-tagged expense or a rushed month-end entry commingles two sub-funds' books without anyone noticing until an auditor pulls the trial balance apart and asks why an entry touches two entities that are supposed to have no relationship to each other.
What this looks like on aama.io: each sub-fund gets an independent ledger, trial balance and set of financial statements, with cross-sub-fund postings blocked before they can be saved — not caught in review after the fact. An umbrella-level roll-up is still available for the family's overall position, but it is clearly labelled as a consolidated view, not a legal consolidation, so nobody mistakes a reporting convenience for something the structure was deliberately built to avoid.
The annual renewal pack
13O runs on a five-year renewal cycle and 13U on ten (confirm the current cadence with MAS, as scheme terms are revised from time to time). At renewal, you are not just reporting your current state — you have to evidence that the AUM test, investment-professional headcount, LBS and CDR were met throughout the period, at each required measurement point, for every fund and every sub-fund with its own election.
What this looks like assembled by hand: pulling twelve (or sixty) months of AUM snapshots, LBS ledgers and CDR calculations out of spreadsheets and email threads, per sub-fund, and hoping nothing was missed or inconsistently recorded along the way — the kind of reconstruction project that turns a routine renewal into weeks of billable adviser time.
What this looks like on aama.io: because CDR and LBS are tracked continuously rather than assembled at year-end, the renewal pack is a byproduct of normal operations rather than a special project — one click pulls together AUM test results, CDR ratio history and LBS accumulation, per sub-fund where structures require it, into an exportable PDF and Excel package ready to hand to your tax or fund administration adviser, with an archive of prior years' packs for the full exemption period.
Why these two are worth solving together
A renewal pack assembled from a shared ledger with soft sub-fund tags carries the risk that the underlying numbers are wrong before you even start compiling them — you can't evidence a sub-fund's CDR or LBS position cleanly if its transactions were never cleanly separated from its umbrella siblings in the first place. Fixing segregation after years of shared-ledger history is a real remediation project. Building it in from the first sub-fund is not.
This guide is general information, not accounting, tax or regulatory advice. Renewal cadences and evidentiary requirements reflect MAS guidance as understood in 2026 and are revised periodically — confirm the current position with MAS and a licensed adviser. For the other three ongoing conditions, see the full compliance overview.
Running a VCC umbrella with several sub-funds? See how aama.io enforces sub-fund segregation and assembles the renewal pack automatically, or talk to our team about your structure.