14.1 Risk Disclosure Statement (RDS)

Why Module 4 makes the RDS a hard gate

Module 4 — Sales Process (about 15% of the TOAP UCP Qualifying Exam) tests whether you can move a client from interest to admission without shortcutting disclosures. Chapter 13 covered Client Suitability Assessment (CSA)—who should buy what. This section covers the Risk Disclosure Statement (RDS)—what every admitted participant must acknowledge in writing about risk before units are issued.

UITFs sit beside savings and time deposits in the same branch. Clients hear “bank” and instinctively expect PDIC protection and principal safety. The RDS exists to break that habit before cash becomes units. On the exam and in mystery shops, a salesperson who “explains everything orally” but never completes a proper RDS fails the standard.

What the RDS is (and is not)

The RDS is not a guarantee letter, interest rate quote, credit score, or substitute for suitability. Signing it means the client has been informed that markets move, NAVPU fluctuates, and losses of principal are possible—not that the bank will make the client whole.

BSP form discipline: substantially Appendix 57 / Q-34

Under the BSP UITF / consumer-protection framework associated with Circular 1152 and related MORB/MORNBFI appendices, the RDS must be provided substantially in the form prescribed by BSP—commonly referenced as Appendix 57 (banks / MORB lane) and the parallel Appendix Q-34 (non-bank trust / MORNBFI lane). Exam language expects:

1. Use of the prescribed (or substantially conforming) BSP template, not a freestyle branch letter.
2. Delivery and client signature/acknowledgment before admission (before subscription is processed into units).
3. Content that makes risks understandable, not buried in tiny print after the sale.

“Substantially in the form” means your bank’s approved RDS may carry institutional branding and product naming, but it must preserve the substance of the BSP risk-disclosure template—especially the investment nature of UITFs, non-deposit character, and risk of loss. Marketing cannot invent a one-paragraph “I understand risks” sticky note and call it an RDS.

Timing rule (memorize)

RDS first → then admission.
If the client has not signed/acknowledged the RDS, do not process the subscription. There is no exam-correct path of “book the units now, collect signatures at month-end.”

What risks the RDS typically surfaces

Exact wording follows the bank’s approved BSP-aligned template, but exam-level risk themes include:

The RDS does not need to forecast tomorrow’s NAVPU. It must make clear that past performance is not a guarantee of future results and that the trustee does not insure outcomes.

Minimum document package for participants

BSP-aligned UITF sales practice requires that participants receive, at minimum, a coherent package of disclosures and transaction documents. Teach this list as a checklist, not optional extras:

1. CSA results — the client’s profile outcome and the mapping logic that supports (or constrains) the product offered.
2. RDS — signed risk acknowledgment in substantially the BSP form, before admission.
3. Participating Trust Agreement — the client’s agreement to participate under the fund’s Plan Rules / trust arrangement.
4. Confirmation of Participation (subscription) or Confirmation of Redemption — post-deal advice showing at least:
   • applicable NAVPU,
   • number of units issued or cancelled, and
   • peso value (or foreign-currency value where the dealing currency is not peso).

Worked branch flow

1. Client Ana completes KYC and CSA → profile Moderate.
2. RM maps her to a peso bond UITF (suitable under bank matrix).
3. RM provides PHS/KIIDS summary facts and walks through the RDS.
4. Ana signs the RDS and Participating Trust Agreement before cash is applied.
5. Subscription hits the dealing cut-off; ops issues units.
6. Ana receives Confirmation of Participation: e.g., NAVPU 1.250000, units 80,000, peso amount PHP 100,000.

If step 4 is skipped, the sale is compliance-defective even if NAVPU math is perfect.

How CUSP personnel should present the RDS

Good practice (exam + mystery shop):

1. Hand over or display the full approved RDS—do not summarize only the happy parts.
2. Explain that UITFs are trust investments, not deposits.
3. State clearly that units are not PDIC-insured and principal is not guaranteed.
4. Invite questions; do not rush the signature while the client is still reading.
5. Keep the signed copy in the bank/trust record per retention rules; give the client a copy or access channel as policy requires.
6. If the client refuses to sign, stop—no admission.

Bad practice (misselling-adjacent):

• “Just sign here; it’s standard bank paperwork like the ATM form.”
• “We only need RDS for equity funds; money market is basically a deposit.”
• Backdating the RDS to match yesterday’s dealing date.
• Letting a spouse or assistant sign without proper authority documentation.
• Using an expired or non-approved template that omits BSP substance.

RDS vs Confirmation of Participation

Candidates mix these on exams:

A confirmation is a dealing receipt, not a risk waiver. An RDS is a risk gate, not a unit certificate.

Interaction with CSA and risk waivers

• Suitable product: CSA maps client to fund → still need RDS before admission.
• Client insists on higher-risk fund: CSA mismatch requires a written risk waiver process (Chapter 13) and still requires a proper RDS—a waiver does not erase disclosure.
• CSA update every three years (or on material change): when product risk or profile changes, reconfirm that disclosures and acknowledgments remain current under bank policy; never assume a five-year-old signature covers a newly aggressive mandate without process.

Exam traps for the RDS

1. Treating PHS as a signed RDS substitute — PHS informs; RDS is the formal risk acknowledgment.
2. Signing after units are issued — too late; admission requires prior RDS.
3. Claiming money market UITFs need no RDS — all UITF admissions need proper risk disclosure discipline.
4. Confusing RDS with Declaration of Trust — DOT/Plan is fund governance; RDS is client risk acknowledgment.
5. Believing RDS creates PDIC coverage — opposite: it reinforces that coverage does not apply.
6. Forgetting the minimum package — CSA results, RDS, Participating Trust Agreement, and confirmations with NAVPU/units/value.

One-liner to memorize

RDS = BSP-form risk acknowledgment signed before UITF admission; it sits with CSA results, Participating Trust Agreement, and post-deal confirmations of NAVPU, units, and cash value—never a deposit guarantee.