Enforcement Files · 2021–25 · Code of Conduct

UBS Fined Twice in Three Years

Same bank, same root-cause lineage, two penalties — how a systemic professional-investor classification error became a chronic compliance condition.

Updated: 2026-10-21 Reading time: ~9 min Series: Enforcement Files
Home / Compliance Guides / Enforcement Files / UBS Repeat

In November 2025 the SFC fined UBS AG HK$8 million — for professional-investor (PI) classification errors persisting over 12 years. It was not UBS's first fall on the same theme: in November 2021 it had already been fined HK$9.8 million for monitoring failures around a PI-only securities-lending service. Same bank, same root-cause lineage, two fines in three years — a perfect specimen of a chronic compliance condition.

HK$8M2025 fine (25PR167)
HK$9.8M2021 fine — same PI theme
560Misclassified joint accounts found in a 2018–2022 look-back
>12 yrsDuration of the classification-system flaw
UBS two-fine timeline From latent system flaw to two SFC fines and a four-year look-back. ~2009 onwards Joint-account logic flaw Latent for >12 years 2021.11 First fine HK$9.8M SPL service PI control 2018–2022 look-back 560 misclassified accounts Internal review 2025.11 Second fine HK$8M 25PR167 Reading: the 2021 fine targeted the execution layer (monitoring of a PI-only service); the 2025 fine targeted the design layer (the classification logic itself). Same theme, different depth — the SFC digs down layer by layer. Fixing the surface is not fixing the root. Sources: SFC press release 25PR167 (Nov 2025), SFC 2021 disciplinary action
UBS timeline — a system flaw latent for 12 years; the SFC fined from execution layer to design layer.

1. The two fines punished different things

2021 (HK$9.8m): UBS's securities-lending service (SPL) was designed for PI clients only, but internal systems allowed non-PI clients to subscribe — a monitoring failure at the execution layer.

2025 (HK$8m): a four-year look-back (Jul 2018–Jul 2022) found 560 Hong Kong-booked/managed joint accounts wrongly classified as PI — because the system logic treated a joint account as PI if any single holder met the portfolio threshold. A design-layer defect: the rule itself was coded wrong.

The PI rules are clear: a joint account counts as PI only if all holders qualify — not one. That boolean bug sat in production for twelve years.

2. Why it matters

3. Legal and regulatory analysis

InstrumentHow it appliesCompliance meaning
Professional Investor Rules (SFO sub-leg.)PI portfolio thresholds — joint accounts require all holders to qualifyClassification is a hard rule; "one qualifies" is not enough
Code of Conduct 5.1/5.2 (know your client + suitability)Wrong classification corrupts the foundation of suitabilityProduct eligibility and disclosure exemptions all fail
Code of Conduct 4.3 (internal controls)Systems need periodic review and back-testingTwelve years undetected = no effective review

Deeper still is the "codification risk" of classification rules: the PI definition exists as legal text; in systems it becomes a boolean — and every translation step is a defect opportunity for every institution encoding regulation into code.

RegSir's take

The biggest lesson for compliance officers: someone must read the source legislation, not just the system documentation. These defects persist not because nobody checks, but because everyone checks the system against its own spec — nobody re-verifies the code against the Rules word by word. The discounted second fine is also a clear signal: the SFC rewards not "no mistakes" but "found it yourself + fixed it completely". A chronic compliance condition is survivable; the absence of any mechanism to detect it is not.

4. Compliance takeaways

5. Official sources

DocumentLink
SFC press release 25PR167 — UBS disciplinary action (Nov 2025)sfc.hk ↗
Securities and Futures Ordinance (Cap.571) — Professional Investor Rules (sub-leg. 571D)elegislation.gov.hk ↗
SFC — 2021 UBS disciplinary action (SPL service PI controls)sfc.hk ↗
SHARE THIS ANALYSIS WhatsApp Telegram LinkedIn X

How would your case be characterised? Ask RegSir.

Describe the facts — RegSir analyses them against the Securities and Futures Ordinance, SFC guidance and enforcement precedent, provision by provision.

Try 3 questions free →