High-roller accounts generate disproportionate revenue, but they also carry disproportionate compliance risk. Operators who have faced regulatory censure or licence reviews over the past several years share a common thread: their source of wealth (SOW) and source of funds (SOF) processes looked adequate on paper but collapsed under scrutiny when applied to real, high-velocity players. The lessons below come from aggregated operational experience, regulatory findings published by the UK Gambling Commission, Malta Gaming Authority, and equivalent bodies, and the day-to-day case work that OnlineShine's AML and MLRO teams conduct on behalf of operator clients.
Why SOW and SOF Are Not the Same Thing
Confusing these two concepts is one of the most persistent errors compliance teams make. Source of funds refers to where the money used in a specific transaction or deposit originated, a salary account, a savings account, the proceeds of a property sale. Source of wealth is broader: it describes how the player accumulated their total net worth over time. A player can have entirely legitimate SOF, a bank transfer from a personal current account, while their underlying SOW remains unexplained or implausible.
Regulators expect operators to satisfy both tests for high-value accounts, not one or the other. Treating an uploaded payslip as a complete answer to a SOW enquiry is a failure that has resulted in formal warnings and, in more serious cases, licence conditions being imposed.
Common Operational Failures Observed in Practice
Accepting Documents Without Verification
A frequently cited incident pattern involves operators accepting self-certified wealth declarations or easily reproduced documents without independent corroboration. A player claiming director-level income should prompt checks against company filings, publicly available accounts, or directorships registered with the relevant national authority. Accepting a letter on company letterhead, without cross-referencing any public record, is not sufficient due diligence.
Triggering Reviews Too Late
Internal thresholds set purely in monetary terms, for example reviewing accounts only after cumulative deposits exceed a specific figure, mean that a high-frequency depositor can accumulate significant exposure before enhanced due diligence begins. Velocity indicators, rapid escalation of bet sizes, frequent same-day deposits, or sudden large withdrawals, should trigger a SOW review independently of absolute deposit totals.
Inconsistent Application Across Account Managers
Where VIP management is handled by relationship teams, compliance standards often vary between account managers. One manager may request and record full documentation; another may rely on a verbal assurance logged as a case note. Regulatory investigators reviewing player files will identify this inconsistency immediately. Standardised checklists, mandatory sign-off from a nominated MLRO, and regular inter-rater reliability reviews across the VIP team are operational controls that close this gap.
Closing Cases Without Resolution
A pattern observed repeatedly is a SOW case being opened, the player going quiet or reducing activity, and the case being closed without a satisfactory conclusion recorded. If the player returns and resumes high-level play, the unresolved case may not be surfaced automatically. Case management systems must flag unresolved SOW enquiries as persistent, not historical, so that any future account activity reopens the review rather than bypassing it.
What Robust SOW and SOF Processes Look Like in Practice
- Tiered triggers that combine monetary thresholds with behavioural velocity indicators, reviewed quarterly against actual player population data.
- A document matrix specifying which evidence type is acceptable for each wealth profile: employment, self-employment, investment income, inheritance, business sale, property.
- Independent corroboration steps for each document type, including company registry checks, land registry searches, and financial statement cross-referencing where applicable.
- A mandatory MLRO or deputy sign-off before a SOW case is closed as satisfied, regardless of the account manager's assessment.
- Automated flags in the player management system that permanently link unresolved SOW cases to the player record, surviving account dormancy.
- Periodic retrospective audits of closed SOW cases, conducted by a party independent of the original reviewer.
The Regulatory Trajectory Operators Need to Anticipate
Regulators across multiple jurisdictions are moving toward requiring operators to demonstrate proactive SOW assessment rather than reactive compliance. This means that waiting for a player to reach a trigger threshold before beginning enquiries is increasingly being viewed as inadequate. Risk-based profiling at onboarding, informed by disclosed occupation, country of residence, and initial deposit patterns, allows operators to segment players likely to reach high-roller status and begin proportionate SOW enquiries earlier in the lifecycle.
A SOW file that could withstand independent regulatory scrutiny is not just a compliance requirement; it is operational insurance against the reputational and financial cost of enforcement action.
OnlineShine supports operators by building and stress-testing SOW and SOF frameworks as part of managed MLRO and compliance services. If your current process has not been reviewed against recent regulatory findings, the gap between policy and practice is likely larger than your internal audits suggest.
