When AML controls look good on paper but fail in practice: lessons from UBS Monaco’s €6m fine

Monaco’s financial regulator has fined UBS Monaco €6 million after identifying repeated failures in the bank’s anti-money laundering controls. 

The penalty was issued by the Autorité Monégasque de Sécurité Financière (AMSF), Monaco’s financial security authority. According to reports on the decision, the regulator found weaknesses across customer due diligence, beneficial ownership verification, politically exposed person (PEP) checks, transaction monitoring, suspicious activity reporting and internal control. Swissinfo reported that the AMSF described the number and repetition of the shortcomings as evidence of an “overall failure” in the institution’s compliance and internal control system.

The decision comes at a sensitive time for Monaco. The principality was added to the Financial Action Task Force’s grey list in 2024, placing it under increased monitoring for strategic deficiencies in its AML/CFT framework. The UBS penalty is the first fine against a global bank by Monaco’s watchdog since that designation.

The case is a useful reminder that AML compliance is increasingly being judged not by whether policies exist, but by whether they work when faced with high-risk clients, complex ownership structures and unusual transactions.

The facts behind the fine

The AMSF decision followed a 2024 inspection of UBS Monaco. Reports say the regulator identified several weaknesses in the bank’s approach to know your customer obligations and AML monitoring.

The AMSF found that UBS Monaco failed to properly identify and verify chains of ownership and control where customers had complex structures involving more than three levels between the account holder and the beneficial owner. The regulator also criticised the bank for failing to corroborate the background of high-risk customers, including PEPs, and for not properly checking the consistency of certain transactions.

The case also involved specific transaction monitoring concerns. Examples include two outgoing transfers of $400,000 each to a client’s personal accounts in Lebanon and Saudi Arabia, where the analysis was reportedly limited to the recurring nature of the transactions rather than supported by clear documentation of their purpose. Another example involved a €500,000 transfer to a jewellery company owned by a customer, reportedly justified by an invoice for only €73,000.

The inspection found the bank had failed to file a suspicious transaction report for 253 days after a flagged transaction, dismissed a €25 million transfer involving a Cayman Islands company without review, and onboarded a client using documents largely in Russian and untranslated.

UBS has not accepted the findings in the way regulators have framed them. The bank said it “takes note” of the administrative sanction, is examining the decision, and remains committed to complying with the highest regulatory standards. The decision may be appealed within two months.

Controls must work under pressure

Most regulated firms have AML policies. Many have customer due diligence procedures, risk rating processes, transaction monitoring systems, escalation routes and reporting obligations. The problem is that regulators are increasingly looking beyond the existence of those controls; they want to see whether the controls produce the right outcome.

That means asking whether beneficial ownership checks actually uncover who controls the customer. It means testing whether high-risk clients are treated as high-risk in practice. It means reviewing whether staff understand when a transaction should be escalated. It means checking whether suspicious activity reports are filed promptly, with enough information and without unnecessary delay.

An AML framework can look credible on paper while still failing in practice if alerts are closed too quickly, supporting documents are not translated or verified, risk ratings are not updated and commercial relationships are allowed to continue without proper challenge.

Complex ownership structures need more than a box-ticking review

One of the key issues reported in the UBS Monaco case was the handling of complex customer structures. The AMSF reportedly criticised failures to identify and verify chains of ownership and control where there were several layers between the account holder and the beneficial owner.

This is a common AML risk. Complex structures can be legitimate, especially in private banking, wealth management, real estate, family office and cross-border investment contexts. But they can also be used to obscure ownership, hide the source of funds or distance a beneficial owner from the movement of assets.

For compliance teams, the lesson is straightforward. Where ownership is complex, the evidence must be stronger, not weaker. Firms should be able to show:

  • who ultimately owns or controls the customer
  • why the structure exists
  • whether any intermediaries, trusts, companies or nominees increase the risk
  • whether the source of wealth and source of funds make sense
  • whether the structure is consistent with the customer’s stated profile and activity
  • what additional checks were performed before the relationship was approved or continued

A chart showing the ownership structure is useful, but even that is not enough on its own. The firm must be able to demonstrate that it understood the structure, challenged it where necessary and reached a documented risk-based decision.

PEPs and high-risk clients require real enhanced due diligence

The case also highlights the importance of enhanced due diligence for politically exposed persons and other high-risk customers. According to Monaco Daily News, the regulator found repeated failures to carry out sufficient checks on PEPs, cross-border transfers and the origins of client funds.

PEP status should not be treated as a label that sits passively in a customer file. It should trigger a more intensive review of risk, source of wealth, source of funds, expected activity, adverse media, linked parties and ongoing monitoring.

That review also needs to be refreshed. A customer who was lower risk at onboarding can become higher risk over time. Their jurisdictional exposure may change. Their business activity may change. New adverse information may emerge. Transactions may begin to move outside the expected pattern.

The practical question is whether the firm’s monitoring process is alive to those changes. If the customer file says “high risk” but the actual monitoring looks the same as for everyone else, the control is unlikely to withstand regulatory scrutiny.

Suspicious activity reporting is a timing issue as well as a judgment issue

One of the most striking details reported in the case is the 253-day delay in filing a suspicious transaction report after a flagged transaction. According to reporting on the case, the delay related to a cheque cashed in September 2022 as part of an investment that raised immediate concerns, including an unusual round-trip transfer of €200,000. The filing was reportedly made only in June 2023.

Suspicious activity reporting is often treated as a legal threshold question: has suspicion arisen or not? But timing is equally important. Delayed escalation can create serious regulatory exposure, particularly where the firm had enough information to identify red flags much earlier.

Firms should be able to evidence:

  • when the alert first arose
  • who reviewed it
  • what information was requested
  • what explanation was provided
  • why that explanation was accepted or rejected
  • when the matter was escalated
  • when a suspicious activity report was filed, if required
  • why any delay was considered reasonable

Where those steps are missing or poorly documented, the firm will very likely struggle to show that it acted promptly and proportionately.

Transaction monitoring needs context, not just activity patterns

Another reported issue was the handling of transfers that were treated as recurring without sufficient documentation of their purpose. This is a practical risk for many firms. If a transaction is repeated often enough, it can start to appear normal. But recurring activity is not the same as legitimate activity.

Transaction monitoring needs context. A payment may be recurring, but it still needs to make sense in light of the customer’s profile, source of funds, stated business, known counterparties, jurisdictional exposure and risk rating.

For example, cross-border transfers to high-risk or sensitive jurisdictions, payments to personal accounts, transactions involving luxury goods businesses, and payments supported by inconsistent invoices should all prompt closer review. The issue is not whether any one factor automatically proves money laundering, but whether the firm recognised the risk and responded properly.

That response should be documented. A short note saying a payment is “usual” or “recurring” is unlikely to be enough if the underlying purpose has not been verified.

Local accountability cannot be outsourced to group compliance

For large financial institutions, group-level policies and systems are essential. But regulators still expect local entities to understand and manage their own risks. This is especially important where a local branch or subsidiary operates in a higher-risk market, serves high-net-worth clients, deals with complex structures or manages cross-border flows.

The UBS Monaco case underlines that local AML controls must be adequately staffed, documented and applied. The AMSF criticised failings including having too few staff to handle alerts and shortcomings in verifying the origin of certain clients’ wealth.

A group policy cannot compensate for a local team that lacks the resources, training or authority to investigate risk properly. Firms should consider whether local compliance teams have enough capacity to review alerts, challenge relationship managers, request further evidence, escalate concerns and pause activity when necessary.

Some practical takeaways

The case offers several practical takeaways for regulated firms, especially those dealing with high-risk customers, cross-border transactions, complex ownership structures or private wealth.

First, review whether enhanced due diligence is genuinely enhanced. High-risk customers should not simply be assigned a higher risk rating and left in the system. The customer file should show what additional checks were carried out, what evidence was obtained and how the firm reached its decision.

Second, test how alerts are closed. Firms should review a sample of closed alerts and ask whether the rationale is clear, whether supporting evidence is adequate, and whether the decision would still make sense to a regulator reviewing the file months or years later.

Third, examine suspicious activity reporting timelines. Delays are often easier for regulators to criticise than judgment calls. Firms should be able to reconstruct the full timeline from first concern to final decision.

Fourth, strengthen beneficial ownership verification. Where ownership chains are complex, firms should not rely on incomplete corporate documents or unexplained structures. They should obtain clear evidence of ultimate ownership and control, and document why the structure is considered legitimate.

Fifth, check whether documents are usable. Documents that are outdated, untranslated, unverifiable or from unreliable sources may create the appearance of due diligence without providing real assurance.

Finally, make sure training reflects real scenarios. Staff need to understand how AML red flags appear in practice: unusual invoice values, round-trip transfers, unexplained wealth, complex offshore entities, high-risk jurisdictions, PEP connections and vague commercial explanations.

The UBS Monaco fine is a reminder that AML failures rarely come from one missing document or one isolated mistake. They usually emerge from repeated weaknesses across the control environment: incomplete due diligence, weak challenge, poor documentation, delayed escalation and under-resourced monitoring.

Vinciworks practical, role-specific AML training helps staff recognise red flags, understand due diligence obligations and escalate suspicious activity appropriately.

Learn more →