16.1 AMLA: KYC, Covered Transactions, and Structuring
Key Takeaways
- The Anti-Money Laundering Act (AMLA) and implementing rules require Philippine banks and Trust Entities to know their customers and apply customer due diligence (KYC/CDD) to trust and UITF clients before and during the relationship.
- A covered transaction commonly tested on the UCP is cash or equivalent activity of PHP 500,000 or more in a single banking day that triggers covered-transaction reporting duties under AMLA rules as taught for this exam.
- Structuring—breaking what would be a large reportable amount into smaller pieces under the threshold (for example PHP 1.5M split into three PHP 490,000 deposits)—is a red-flag pattern and may constitute illegal evasion of reporting.
- KYC/CDD is not a one-time account-opening formality; ongoing monitoring and refresh of client identity, beneficial ownership, and purpose of funds remain part of fiduciary and AML culture.
- Certified UITF marketing personnel must escalate AML red flags through bank AML channels rather than complete a sale that ignores suspicious patterns.
Why AMLA sits inside Module 5 (and your sales day)
Module 5 — Code of Conduct & Ethics is not only loyalty slogans and conflict vignettes. Philippine trust personnel who open UITF participations, accept subscription monies, or face walk-in “wealth” clients operate inside the same anti-money laundering perimeter that governs banks. The Anti-Money Laundering Act (AMLA) of the Philippines, as amended, together with rules of the Anti-Money Laundering Council (AMLC) and BSP supervisory expectations, requires covered institutions—including banks and Trust Entities—to know their customers, monitor transactions, and report covered and suspicious activity.
On the UCP Qualifying Exam, AMLA items typically test three durable ideas:
- KYC / CDD for trust and UITF clients
- Covered transactions at the PHP 500,000 single-banking-day threshold commonly taught for this exam
- Structuring (also called smurfing in informal industry talk) as a red-flag / potentially illegal evasion pattern
You do not need to recite every AMLC circular number to pass. You do need decision rules that keep a Certified UITF Sales Person from becoming the weakest link in a money-laundering scheme dressed up as a multi-asset subscription.
Money laundering in plain language (exam context)
Money laundering is the process of making proceeds of unlawful activity appear legitimate by moving, layering, or integrating them through the financial system. Classic stages taught worldwide still help you spot narratives:
| Stage | Idea | UITF-desk example |
|---|---|---|
| Placement | Introduce dirty funds into the system | Large cash brought for same-day UITF subscription with thin story |
| Layering | Obscure the trail through multiple transfers | Rapid subscribe–redeem cycles, third-party funders, complex routes |
| Integration | Make funds look clean | “Investment gains” later withdrawn as if ordinary portfolio proceeds |
UITFs are attractive for launderers because they look like legitimate wealth products, can move large amounts, and may sit next to deposit desks. Your job is not to be a prosecutor; it is to apply KYC, refuse incomplete identity stories, and escalate red flags so the bank’s AML unit and AMLC reporting machinery can work.
KYC and CDD for trust / UITF clients
Know Your Customer (KYC)
Know Your Customer (KYC) means the institution must identify and verify who the client is—and, where relevant, who the beneficial owner is—before establishing or continuing a business relationship. For UITF admission, KYC is not optional marketing paperwork; it is a legal and prudential control.
Typical KYC elements for individuals (institution forms vary; concepts are stable):
- Full name, date of birth, nationality, residential address
- Government-issued identification (and verification of authenticity/currency)
- Contact details and specimen signatures as required
- Nature of work / source of funds / source of wealth (risk-based depth)
- Beneficial ownership when the named client is not the true owner
For entities (corporations, partnerships, trusts, foundations):
- Legal existence documents and registration
- Authorized signatories and board/authority evidence
- Ownership and control structure; ultimate beneficial owners above bank thresholds
- Purpose of the UITF relationship and expected activity
Customer Due Diligence (CDD)
Customer Due Diligence (CDD) is the broader process that includes identification, verification, understanding the purpose of the relationship, and risk assessment. Enhanced Due Diligence (EDD) applies to higher-risk clients (for example certain PEPs—politically exposed persons—or complex ownership structures) under bank AML policy.
| CDD idea | Marketing-personnel meaning |
|---|---|
| Identify | Collect complete, consistent client data |
| Verify | Use acceptable IDs and bank verification steps—do not “skip because VIP” |
| Understand purpose | Why UITF? Horizon? Source of subscription money? |
| Risk-rate | Apply bank risk scoring; escalate high-risk cases |
| Monitor | Unusual size, frequency, or pattern vs profile → flag |
KYC is ongoing, not only day-one
Exam distractors often imply that once an account is opened, KYC is finished forever. Wrong. Material changes—new beneficial owner, unexplained surge in subscription size, third-party funders appearing, or mismatched occupation vs cash flows—trigger refresh and review. Suitability updates (CSA cycles) and AML monitoring are different systems that often surface the same client facts; do not ignore inconsistencies between them.
Covered transactions: the PHP 500,000 threshold
A covered transaction under AMLA teaching for this exam is activity that meets a defined reporting threshold. The figure you must lock in for UCP purposes is:
PHP 500,000 (or more) in a single banking day — the commonly tested covered-transaction threshold for reportable covered activity as presented in TOAP/UCP materials.
What “single banking day” means for study
- The threshold is evaluated on a per banking day basis as taught for covered-transaction reporting.
- Multiple movements that aggregate to PHP 500,000 or more in that day can matter—do not assume only one ticket at exactly PHP 500,000 counts.
- Covered-transaction reporting is a threshold-driven duty of the covered institution; it is distinct from (but can coexist with) suspicious transaction reporting, which is indicator-driven and amount-independent (Section 16.2).
Worked covered-transaction examples
| Scenario | Covered-transaction thinking (exam level) |
|---|---|
| Client remits PHP 500,000 cash/equivalent for UITF subscription in one day | Meets the commonly tested PHP 500,000 threshold → covered-transaction machinery applies |
| Client does PHP 300,000 in the morning and PHP 250,000 in the afternoon same day | Aggregate PHP 550,000 in a single banking day → treat as threshold-relevant; do not “hide” by splitting tickets in your mind |
| Client invests PHP 400,000 only | Below PHP 500,000 covered threshold on that fact alone—but suspicious indicators can still require STR thinking |
| Client wires PHP 2,000,000 from a verified payroll account with clean KYC | Large and potentially covered; large size alone is not automatically “guilty,” but reporting/process still follows AML rules |
Important precision for the exam: Covered-transaction reporting is not a substitute for KYC. A clean covered report with a fake identity is still an AML failure. Conversely, thorough KYC does not erase the institution’s duty to report covered activity when the threshold is met under applicable rules.
Structuring: breaking amounts to evade the threshold
Structuring is the deliberate breaking of a large amount into smaller pieces so that each piece (or each day, depending on the scheme) stays under the reporting threshold—with the purpose of avoiding detection or reporting.
Classic exam numbers (memorize the pattern)
A client wants to place PHP 1,500,000. Instead of one transparent path, the client proposes three deposits/subscriptions of PHP 490,000 each (or similar under-threshold slices), timed or routed to stay below PHP 500,000, and asks staff to “huwag na i-report” or to treat them as unrelated.
| Element | Why it is a red flag |
|---|---|
| Total economic intent ≈ PHP 1.5M | Above threshold in substance |
| Pieces ≈ PHP 490k each | Engineered under PHP 500,000 |
| Purpose of split | Avoid covered reporting / scrutiny |
| Staff role if complicit | Facilitating evasion—serious misconduct |
Structuring is not clever cash management. On the UCP and in real AML culture it is a red-flag pattern and can be illegal evasion of AML reporting duties when done to defeat the threshold. Marketing personnel must not:
- Suggest splitting tickets “so it won’t be reported”
- Coach clients on how to stay under PHP 500,000
- Open multiple nominee accounts to hide one controller without proper disclosure
- Accept “pakiusap, confidential, huwag nang malaman ng AML” as a valid instruction
Structuring vs legitimate staggered investing
Not every multi-day investment is structuring. A salary earner who invests PHP 50,000 monthly under a documented savings plan is ordinary. The difference is intent and pattern:
| More likely legitimate | More likely structuring / suspicious |
|---|---|
| Documented goal-based peso-cost averaging | Explicit request to avoid “AML report” |
| Amounts match known income and CSA | Amounts just under PHP 500,000 repeatedly without economic reason |
| One verified client, clear source of funds | Third-party cash, rotating names, refusal to explain |
| Client accepts full KYC and bank process | Client pressures for exceptions and speed only |
When in doubt, do not complete the convenience path—complete KYC, document, and escalate to the bank’s AML / compliance unit.
Red-flag catalog for UITF marketing personnel
Use this as an exam and branch checklist:
- Reluctance to provide ID or use of obviously inconsistent documents
- Third-party funders who will not identify themselves as beneficial owners
- Occupation vs amount mismatch (e.g., “student / unemployed” funding multi-million UITF subscriptions in cash)
- Just-under-threshold repeated activity near PHP 500,000
- Rapid subscription and full redemption with no investment rationale
- Pressure to skip process because the client is a VIP, politician, or “friend of management”
- Complex ownership with no commercial explanation
- Instructions to structure or to avoid reporting
Loyalty, prudence, and AML (ethics link)
AMLA duties reinforce Module 5 fiduciary themes:
- Loyalty to the legitimate participant and to the integrity of the financial system is not loyalty to a client who demands illegal concealment.
- Prudence includes careful KYC, refusal of incomplete files, and escalation—not reckless onboarding for AUM.
- Integrity / TOAP standards forbid coaching clients to evade controls.
Sales contests never authorize AML shortcuts. A subscription that clears cut-off but fails CDD is not a win.
Worked scenarios
Scenario A — threshold clear-cut
Client brings PHP 500,000 for a money-market UITF, clean government ID, employment certificate, and payroll trail.
Action: Complete full KYC/CDD and bank admission process; expect covered-transaction handling as applicable; no need to invent suspicion solely because the amount equals the threshold—but never waive identity because the amount is “only” five hundred thousand.
Scenario B — structuring request
Client: “I have PHP 1.5 million cash. Gawan mo ng three times PHP 490k para hindi ma-report.”
Action: Refuse facilitation; explain that deliberate threshold evasion is improper/illegal; escalate to AML/compliance; do not process the coached structure.
Scenario C — KYC incomplete, manager pressure
Manager: “Kilala ko ‘yan, i-process mo na, ID later.”
Action: No. CDD first. Escalate improper instruction. Manager familiarity is not a legal substitute for identification and verification.
Exam traps for this section
- Thinking AMLA applies only to deposit accounts, not UITFs — trust clients are still customers of a covered institution.
- Memorizing PHP 500,000 but forgetting single-banking-day / aggregation logic — threshold thinking is daily, not “per lifetime.”
- Confusing covered transactions with suspicious transactions — covered is threshold-based; suspicious is indicator-based (next section).
- Believing structuring is fine if each piece is below PHP 500,000 — purpose to evade reporting is the problem.
- Assuming VIP status waives KYC — it does not; it may increase scrutiny.
- Treating KYC as optional if CSA/RDS are signed — suitability forms do not replace AML identity controls.
Closing memory set
- AMLA binds banks/Trust Entities; UITF clients need KYC/CDD.
- Covered transaction (UCP teaching): PHP 500,000 in a single banking day.
- Structuring (e.g., PHP 1.5M → three × PHP 490k to avoid reporting) = red flag / illegal evasion pattern.
- Escalate—never coach clients under the threshold.
- KYC is ongoing; process beats AUM pressure.
Under AMLA concepts tested on the UCP, what is the commonly taught covered-transaction threshold for a single banking day?
A client asks a UITF marketer to split PHP 1.5 million into three subscriptions of PHP 490,000 each so the activity “will not be reported.” What is the best assessment?
What does KYC/CDD primarily require before establishing a UITF client relationship?
Which statement best distinguishes covered-transaction thinking from ordinary product suitability?