12.2 Prohibited Transactions for Trust Entities
Key Takeaways
- Trust entities managing UITFs are barred from self-dealing and conflicted trades that harm participants—especially dumping bank proprietary positions into the fund at non-market prices.
- Using the UITF to deliver improper related-party benefit, preferential pricing, or undisclosed affiliate advantage violates fiduciary duty and BSP trust conduct rules.
- Guaranteeing principal or returns on a UITF, or treating/marketing the UITF as a bank deposit or PDIC-insured product, is prohibited and is classic misselling.
- Arm’s-length standards require independent market pricing, disclosure, and governance approval where related-party dealing is even considered—not branch improvisation.
- CUSP personnel escalate conflicts; they do not “fix” breaches by adjusting NAVPU or promising bank capital backstops.
Fiduciary product, not a bank parking lot
A UITF is administered by a Trust Entity under a Declaration of Trust / Plan Rules. The trustee holds legal title for the benefit of participants. That structure triggers fiduciary duties of loyalty and prudence: fund assets exist for unit holders, not as a convenient dump site for the commercial bank’s unwanted inventory, not as a side pocket for related-party favors, and not as a fake deposit with a guarantee sticker.
Section 12.1 limited how concentrated the portfolio may be. This section limits how the trustee and the bank may deal with the fund and what may never be promised to clients. On the UCP exam, prohibited-transaction stems often sit next to ethics items—same instinct, different module label.
Self-dealing: the flagship prohibition pattern
Self-dealing in UITF context means the trust account and the bank’s proprietary / corporate book (or other conflicted parties) trade with each other in ways that put the bank’s interest ahead of participants—or that fail strict arm’s-length, disclosure, and governance approval requirements.
Classic exam fact pattern
Prohibited / highly restricted: purchasing debt (or other) securities from the bank’s own proprietary trading desk into the UITF without prior board (or required governance) approval and without true arm’s-length terms—especially at prices that favor the bank.
Concrete abuse:
- Bank Treasury is long an illiquid corporate bond that mark-to-market has hurt on the bank’s own P&L.
- Someone “helps” by selling that bond into the UITF at a premium above market bids.
- Bank book looks better; UITF participants overpay; future NAVPU and remaining unit holders suffer.
That is not “good relationship management.” It is a fiduciary and regulatory breach.
What arm’s-length means (exam definition)
An arm’s-length transaction is one in which parties deal as independent market participants: current market prices, verified by independent sources, no preferential terms for insiders, and full process integrity.
| Arm’s-length (acceptable pattern) | Not arm’s-length (exam fail) |
|---|---|
| Executed at current market prices verified independently | Bought from bank book at a premium above highest market bid |
| No special discount or sweetheart fee for board relatives | Fee discounts only for directors’ family accounts |
| Documented, disclosed, governance-cleared where required | RM and spouse’s company deal bypasses committee review |
| Participant interest first | Bank proprietary P&L first |
Even when related-party dealing is not absolutely impossible under every historical circular nuance, the UCP teaching posture is clear: self-dealing is prohibited unless strict arm’s-length terms, full disclosure, and required board/governance approval are satisfied. Branch staff do not “approve” self-dealing at the teller window.
Worked PHP self-dealing example
- Independent market quotes for Corporate Bond Z: best available offer consistent with market ≈ PHP 98.50 (clean, conceptual).
- Bank proprietary desk sells Bond Z to the UITF at PHP 102.00 “to support the franchise.”
- Notional transferred: PHP 100,000,000 face; economic overpay vs market is material.
Result: the fund’s cash buys an overpriced asset; NAV is impaired relative to true market; every participant—including retirees who subscribed last week—subsidizes the bank book. Correct staff response if discovered: stop, report to Trust Committee / compliance / risk, do not “smooth” by manually editing NAVPU.
Improper related-party benefit
Related-party abuse is broader than one bond ticket:
- Preferential allocations of hot deals to insider accounts at the expense of the pooled fund.
- Using UITF cash to prop up an affiliate’s securities issuance without investment merit under Plan Rules.
- Fee or expense arrangements that siphon value to affiliates beyond disclosed, allowed charges.
- Information abuse—front-running fund trades for proprietary or personal accounts (also an ethics Module 5 theme).
The unifying test: Does this use of trust assets or trust process primarily benefit the bank, an affiliate, an insider, or a favored client rather than participants as a class under the Plan Rules? If yes, treat it as prohibited territory.
Philippine branch reality
Universal banks sell deposits, loans, bancassurance, and UITFs under one roof. The commercial RM may feel pressure to “help Treasury,” “help the IPO of a client group,” or “move inventory before quarter-end.” UCP certification exists partly so marketing personnel can say:
“Trust assets are segregated and managed for UITF participants. We cannot place bank proprietary paper into the fund at non-market prices or promise outcomes that BSP rules forbid.”
Guarantees of principal or return — always prohibited framing
UITFs are investments. Under BSP trust rules and TOAP conduct standards:
- The trustee must not guarantee principal.
- The trustee must not guarantee a rate of return.
- The bank must not market a UITF as if bank capital or PDIC will backstop NAVPU declines.
Prohibited client lines (memorize the pattern)
- “Garantizado ang principal nito, parang time deposit.”
- “If NAVPU falls, the bank will top up from capital.”
- “Minimum 5% a year guaranteed by the trust department.”
- “Safe deposit alternative with guaranteed payout.”
Accurate alternative
“This is a UITF. Your units are valued at NAVPU, which moves with markets. Principal and earnings are not guaranteed. The product is not a deposit and is not PDIC-insured. You can lose money.”
Guarantees are not “aggressive sales.” They are false product characterization and a regulatory prohibition area. They also corrupt suitability: a conservative client who needs capital preservation may be sold equity risk under a guarantee fantasy.
Treating a UITF as a deposit — prohibited product identity
Closely related to guarantees is deposit mischaracterization:
| Deposit truth | UITF truth |
|---|---|
| Client is generally a creditor of the bank | Client is a participant with beneficial interest via units |
| Eligible deposits may have PDIC coverage | UITF units are not PDIC-insured |
| Contractual principal framework (subject to bank solvency/terms) | Market value via NAVPU; can fall |
| Interest language common | Performance via NAVPU, not passbook interest |
Prohibited operational/marketing patterns:
- Booking or describing the UITF subscription as a “special savings” or “high-yield deposit.”
- Telling clients “withdraw anytime like ATM savings” when Plan Rules impose dealing cut-offs, settlement timelines, or early redemption charges.
- Implying PDIC stickers apply to unit balances.
- Using deposit account screens without trust disclosures to hide the investment nature.
Exam stems often pair this with Risk Disclosure Statement (RDS) and Product Highlights / KIIDS duties: required disclaimers exist because the product is not a deposit.
Other prohibited or high-risk patterns you should recognize
- Commingling trust assets with bank proprietary funds (segregation breach—linked Module 3 asset segregation).
- Manual NAVPU manipulation to hide bad marks or overpriced related-party buys.
- Waiving Plan Rules verbally (fees, holding periods, eligible assets) without lawful amendment and notice processes.
- Misuse of fund for the bank’s liquidity stress or window-dressing.
- Selling without UCP certification / unauthorized marketing personnel.
Not every bad act is labeled “self-dealing,” but all share a theme: participant interest subordinated to bank or personal interest, or false product identity.
What is not prohibited (trap reverse)
Candidates sometimes over-flag ordinary trust operations:
| Activity | Usually legitimate if disclosed/authorized |
|---|---|
| Investing in National Government T-bills/bonds under Plan Rules | Yes — standard |
| Charging the trust fee stated in the Declaration of Trust / Plan Rules | Yes — compensation for trusteeship |
| Outsourcing record-keeping to an accredited administrator under BSP-permitted arrangements | Often yes — process must still protect participants |
| Ordinary market purchases of listed securities from unaffiliated counterparties at market | Yes |
| Required client disclosures, CSA, RDS | Mandatory, not “optional ethics” |
The exam contrasts these with the self-dealing bond dump and guarantee language.
Governance and escalation path
When a conflict appears:
- Do not execute the off-market related-party idea.
- Escalate to trust compliance, risk, and/or the Trust Committee pathways under bank policy.
- Document facts (prices, counterparties, who requested the trade).
- Protect participants first—fiduciary priority.
- Never “fix” a bad trade by rewriting history in the NAVPU file.
CUSP staff are not the Trust Committee, but silence after seeing self-dealing is not loyalty to the bank—it is exposure for everyone, including the salesperson who looked away.
Worked client / mystery-shop scenarios
Scenario A — proprietary dump
Treasury asks the UITF desk to buy PHP 50,000,000 of Bank-held paper at above-market price before quarter-end. Correct: refuse non-arm’s-length self-dealing; escalate. Incorrect: process “as a favor” and tell participants nothing.
Scenario B — guarantee to close a sale
High-net-worth client: “I will invest PHP 5,000,000 only if you guarantee no loss.” Correct: decline guarantee; re-map suitability; offer only accurate risk language or a true deposit product if that matches need. Incorrect: side letter “bank will cover NAVPU dips.”
Scenario C — deposit label
Client: “Is this PDIC?” Staff: “Same bank, same protection.” Incorrect—prohibited misrepresentation. Correct: UITF is not a deposit and not PDIC-insured.
Exam traps for this section
- Calling T-bill investment self-dealing — false; government paper is normal.
- Calling contractual trust fees prohibited — false.
- Thinking self-dealing is fine if the RM “discloses verbally” only — insufficient; arm’s-length + governance standards apply.
- Believing bank capital guarantees cure fiduciary breaches — false and prohibited.
- Treating UITF as PDIC deposit to win the sale — prohibited misselling.
- Fixing bad related-party prices by editing NAVPU — fraudulent and forbidden.
Memory line
No self-dealing dumps of bank paper into the UITF at non-market prices; no improper related-party benefits; no principal/return guarantees; no deposit or PDIC costume on a trust product—participants first, arm’s-length always.
Which of the following best illustrates a prohibited self-dealing pattern for a Trust Entity managing a UITF?
A relationship manager promises that if a bond UITF’s NAVPU falls, the commercial bank will restore the client’s original principal from bank capital. Why is this improper?
Which transaction best meets the arm’s-length standard in trust operations?
Marketing materials describe a peso multi-asset UITF as “a high-yield deposit alternative fully protected like PDIC savings.” What is the correct compliance assessment?