Source of wealth and source of funds checks are among the most operationally demanding elements of an iGaming AML programme. When they are applied inconsistently or too late in the player journey, operators face regulatory censure, fines and reputational damage. This guide sets out a clear, step-by-step approach that compliance teams and MLRO functions can adapt to their own risk appetite and licensing jurisdiction.
Understanding the Distinction
These two checks are related but serve different purposes, and conflating them is a common operational mistake.
- Source of funds (SOF) refers to the specific origin of the money a player is depositing or wagering on a given occasion. A recent payslip, a bank statement showing a salary credit, or proceeds from a property sale are typical examples.
- Source of wealth (SOW) is broader: it addresses how a player accumulated their total net worth over time. This includes career history, business ownership, inheritance, investment returns and other lifetime accumulations.
An operator can verify that a deposit came from a player's personal bank account (SOF satisfied) while still having no understanding of how that bank account became so well funded (SOW outstanding). Regulators, including the UK Gambling Commission and Malta Gaming Authority, expect both layers to be addressed for higher-risk customers.
Setting Triggers and Thresholds
Rigid monetary thresholds are a starting point, not a complete strategy. A well-constructed trigger framework considers multiple signals in combination.
- Cumulative deposit or loss thresholds over a rolling 30 or 90-day period, not just per session.
- Velocity changes, such as a player whose average weekly deposit suddenly doubles or triples without any corresponding life event on file.
- Occupation-to-spend ratios where declared income appears inconsistent with wagering volume.
- Unusual win patterns, particularly consistent large withdrawals that could indicate layering behaviour.
- Players who request VIP treatment or account limits removed without explanation.
Thresholds should be reviewed at least annually and recalibrated against the operator's actual player population data. A threshold set for a mass-market sportsbook is not appropriate for a premium live casino attracting high-net-worth individuals.
Building an Evidence Pack
Once a trigger is hit, the compliance team needs a structured evidence collection process. Requesting documents in a disorganised or repeated manner frustrates legitimate players and signals poor internal controls to regulators.
Source of Funds Evidence
- Bank statements covering the period in which the relevant deposits were made, showing the crediting transaction.
- Payslips or employer confirmation letters for salaried players.
- Proof of a specific transaction such as a property sale completion statement or share sale contract note.
Source of Wealth Evidence
- Most recent tax return or equivalent national filing, which provides an independently verified income snapshot.
- Company accounts or director loan agreements for self-employed or business-owning players.
- Inheritance documentation such as a grant of probate or solicitor letter.
- Pension statements or investment portfolio summaries for retired players.
Operators should use a single, trackable request per player rather than issuing multiple requests across different channels. A secure document portal integrated with the CRM system is the most auditable approach.
Evaluating and Corroborating Evidence
Receiving a document is not the same as verifying it. Compliance analysts should cross-reference submitted evidence against open-source information: company registry filings, land registry data, LinkedIn career histories and adverse media. Where a player claims business ownership, the declared turnover of that business should plausibly support the wagering volume.
A player submitting a one-page letter from a private company they own is not the same as a player whose company accounts, filed at a public registry, confirm the declared profit level. The strength of third-party corroboration is what determines whether the check is genuinely satisfied.
Documenting Decisions and Escalation Paths
Every SOW and SOF review must produce a written decision record. This should note what was requested, what was received, what corroboration was performed, the analyst's assessment, and the MLRO's sign-off where required. Regulators routinely audit these records during inspections.
Where evidence is insufficient or a player refuses to cooperate, the operator must have a clear escalation path: restrict the account, file a Suspicious Activity Report if warranted, and document the rationale for any continued relationship or account closure. Continuing to accept deposits while a check remains unresolved is one of the most commonly cited failures in regulatory enforcement actions.
Balancing Compliance with Player Experience
High-value players are commercially important, but the manner of the check matters as much as the outcome. A well-managed SOW process involves a dedicated account manager explaining the regulatory requirement professionally, offering multiple evidence options, and setting a clear timeline. Players who understand the legal context are far more likely to cooperate than those who receive an abrupt automated request.
Operators that invest in trained compliance staff and clear player communication workflows consistently report higher document return rates and fewer account closures at the SOW stage.
