8.3 Multi-Class Funds
Key Takeaways
- A multi-class UITF issues more than one class of units under one plan/fund structure, with distinctive features per class.
- Class differences commonly include fee schedules, currency features, distribution/income features, or channel rules—as written in Plan Rules.
- Within each class, units remain uniform; across classes, economics may differ.
- Multi-class design is a product governance feature, not a salesperson’s tool to invent private side deals.
- Suitability and disclosure must identify the specific class being sold, including its fees and features.
From one unit type to several classes
Earlier structure chapters taught that in a single-class UITF, units are fungible: one unit has the same pro-rata rights as another. Multi-class funds keep the idea of unitized participation but allow more than one class of units under one UITF plan structure. Each class can carry distinctive features—most often differences in fees, currency, or distribution characteristics—while the fund still pursues a common investment mandate at the portfolio level (subject to how the trustee administers class accounting).
Think of multi-class as one strategy kitchen, several ticket types—not as several unrelated trust entities glued together by a marketing brochure.
Definition for UCP
A multi-class UITF is a fund structure that may issue different classes of units of participation, each with distinctive features defined in the Plan Rules, while remaining part of one overall plan/fund framework.
| Concept | Multi-class meaning |
|---|---|
| One fund / plan structure | Shared product governance and core investment framework |
| Multiple unit classes | Class A, Class B, Institutional, USD class, distributing class, etc. (labels are fund-specific) |
| Distinctive features | Fees, currency denomination features, income distribution features, minimums, or distribution-channel rules as allowed |
| Uniformity rule | Units are equal within a class |
| What staff cannot do | Invent a private “Class RM Special” with guaranteed NAVPU |
Why multi-class exists in Philippine distribution
1. Different client segments, same strategy
A retail class might carry a standard trust fee and lower minimums. An institutional or high-net-worth class might feature a lower fee schedule with higher minimum investment—economics that reflect servicing models without creating an entirely separate portfolio mandate from scratch.
2. Currency packaging
Some structures offer classes denominated or dealt with different currency features so peso and dollar clients can align subscription currency preferences under one product family (always subject to Plan Rules and FX operational reality).
3. Distribution vs accumulation features
A fund family may pair an accumulating class (income retained in NAVPU) with a distributing class (income features described in Section 8.4). Multi-class architecture is the legal/product shell that makes those feature differences possible inside one plan design.
4. Channel or service distinctions
Plan Rules may attach class features to how the class is distributed (e.g., wealth desk vs digital), provided governance and disclosure stay clean. This is still not a license for unfair preferential dealing that harms other participants outside the rules.
What multi-class is not
| Misconception | Reality |
|---|---|
| Two separate UITFs pretending to be one | Multi-class is one structure with class features; separate funds have separate Plan Rules identities |
| A deposit class plus an equity class in one “hybrid PDIC product” | All classes remain UITF units—not PDIC deposits |
| A way to guarantee one preferred client’s principal | No class legitimately turns market risk into a bank guarantee by renaming units |
| Permission for the RM to rewrite fees verbally | Fee schedules are Plan Rules / approved schedule items |
| Automatic proof of higher suitability | Class labels do not replace CSA |
Rights within vs across classes
Within a class
If you and another client both hold Class A units, your per-unit rights in that class are the same. Buying earlier or later does not create preferred Class A units with a NAVPU floor.
Across classes
Class A might accrue a higher ongoing fee than Class I. Over time, NAVPU paths can diverge between classes even though they relate to the same broad strategy, because fee drains and distribution policies differ. That divergence is expected economics—not an error—when disclosed.
Beneficial interest reminder
Participants still hold beneficial interest via units; the trustee still holds legal title to fund assets in trust capacity. Multi-class does not collapse that split.
NAVPU and class accounting (exam-level)
Trustees maintain valuation discipline so each class’s unit value fairly reflects assets attributable to that class net of class-specific fees and distribution mechanics. You are not expected to reconstruct full transfer-agency ledgers on the exam, but you are expected to know:
- NAVPU is still the dealing price language for subscriptions/redemptions per class.
- Comparing “the fund’s return” without specifying which class can mislead.
- A cheaper-fee class can show a higher net NAVPU path than a higher-fee class over the same market move.
- Marketing charts must use the class actually offered to that client segment.
Simple fee divergence illustration
Assume two classes share similar gross portfolio results for a month:
- Class R trust fee accrual (illustrative): higher annual rate → larger daily drag
- Class I trust fee accrual: lower annual rate → smaller daily drag
If markets are flat, Class I NAVPU may decline less (or rise more net of fees) than Class R purely from fee difference. Clients comparing friends’ statements across classes without knowing fee schedules often misunderstand “underperformance.”
Plan Rules control the feature set
Multi-class features must be written and approved, typically covering for each class:
- Class designation and eligibility (who may buy)
- Fee and charge schedule
- Currency and dealing particulars
- Distribution / unit income policy if any
- Minimum initial and additional investments
- Any switching rules between classes (if allowed)
- Risk disclosures that remain true for all classes (non-deposit, market risk) plus class-specific notes
Sales process implication: when completing product explanation and RDS, name the class. “Our equity UITF” is incomplete if Class A and Class B differ on fees or distribution.
Switching and suitability
If Plan Rules allow switches between classes (for example, retail to institutional after meeting a higher minimum), treat the switch as a product-feature change that may affect costs and income characteristics. It is not a loophole to reset risk profiles. CSA still governs whether the underlying strategy fits; class choice fine-tunes economics and features inside that fit.
If Plan Rules do not allow free switching, do not promise a backdoor conversion at the branch.
Relationship to feeder / FoF / distributing
These designs can combine in real product shelves (subject to each fund’s rules):
| Combination idea | Teaching note |
|---|---|
| Multi-class feeder | Classes differ by fee/currency while ≥90% still sits in one target |
| Multi-class FoF | Classes differ by fee while ≥90% sits in multiple targets under FoF rules |
| Multi-class distributing | One class may distribute unit income; another may accumulate |
The exam may test one concept at a time. In the branch, read the specific Plan Rules so you do not mix features from three different products into one pitch.
Client suitability implications
Multi-class can improve fit when used honestly:
| Client need | Class feature that might matter |
|---|---|
| Large ticket, fee-sensitive | Lower-fee institutional class if eligible |
| Prefers cash-flow style features | Distributing class (with full unit-income education) |
| Prefers growth via NAVPU only | Accumulating class |
| Currency preference | Currency-featured class if available and understood |
| Small ticket retail | Retail class minimums |
Misuse patterns to avoid:
- Pushing a higher-fee class solely to maximize bank revenue when a cheaper eligible class exists and is appropriate.
- Telling a client a fee-class difference “removes market risk.”
- Opening the wrong class “by accident” repeatedly without correction.
- Implying multi-class means VIP clients get principal guarantees.
Ethics modules will reinforce fairness; product modules require you to know the mechanics that unfairness would abuse.
Philippine branch conversation examples
Accurate:
“This UITF has two classes. Class A is the retail class with the standard trust fee. Class I has a lower fee but a higher minimum. Both invest under the same broad strategy framework, remain market-risk products, and are not PDIC-insured. Let’s see which class you qualify for and which fits your CSA profile.”
Inaccurate:
“Class I is the safe class; Class A is the risky class.” (Fee class ≠ risk class unless Plan Rules truly define different mandates—which would raise separate product questions.)
“I’ll create Class X just for you with no fees and guaranteed NAVPU.” (Not a thing.)
Exam traps for multi-class funds
- Thinking multi-class means unequal rights inside one class — within class, units are uniform.
- Treating multi-class as multiple unrelated funds — it is one plan structure with class features.
- Believing a class can be PDIC-insured — no.
- Allowing verbal side classes — features come from Plan Rules.
- Comparing performance across classes without adjusting for fees/distribution — misleading.
- Assuming multi-class replaces CSA — it does not.
- Confusing multi-class with FoF — multi-class is about unit features; FoF is about multiple target CIS holdings.
Memory hook
Multi-class = one UITF structure, several unit classes with Plan-Rules-defined differences (fees, currency, distribution, etc.). Equal within class; disclose the class you sell.
What is the best UCP-level definition of a multi-class UITF?
Which feature difference is commonly associated with multi-class UITF design?
A relationship manager promises a preferred client a specially invented unit class with half fees and a NAVPU floor ‘not written in the brochure yet.’ What is wrong with this?
Why might two classes of the same multi-class UITF show different NAVPU performance over the same quarter?