Source of wealth and source of funds checks are among the most scrutinised areas in iGaming compliance audits, yet they remain a persistent source of regulatory findings. For high-roller accounts, the stakes are higher on both sides: the revenue contribution is significant, but so is the reputational and financial exposure if the process is handled poorly. Understanding where teams consistently go wrong is the first step toward building a defensible, proportionate framework.
Why High-Roller SOW and SOF Checks Fail in Practice
The core problem is rarely a lack of policy. Most operators have documented enhanced due diligence procedures. The failures tend to occur in execution, consistency and evidential quality. Regulators in the UK, Malta and the Netherlands have all cited cases where operators held documents on file but could not demonstrate that those documents had been critically assessed, verified against third-party data or linked to the player's actual deposit and wagering patterns.
The Most Common Mistakes
1. Accepting Self-Declaration Without Corroboration
A player stating their occupation or income level in a registration form is not source of funds evidence. It is a starting point for verification. Compliance teams sometimes treat a submitted letter or payslip as a closed matter without checking whether the declared salary plausibly accounts for the volume and frequency of deposits. A consistent failure mode is accepting a single payslip covering a modest monthly income while the account shows deposits many multiples of that figure across the same period.
2. Treating SOW and SOF as Interchangeable
These are distinct concepts and regulators treat them as such. Source of funds refers to the specific money being deposited, for example proceeds from a recent property sale or a business dividend payment. Source of wealth refers to the broader accumulation of the player's overall assets and financial standing. An effective check addresses both, and the documentation requirements differ. Using a payslip as evidence of SOW when the player has claimed their wealth derives from an inheritance or investment portfolio is a category error that will not survive regulatory scrutiny.
3. Trigger Thresholds Set Too High or Applied Inconsistently
Operators sometimes set enhanced due diligence triggers at a flat deposit threshold without accounting for velocity, session frequency or net loss patterns. A player who deposits just below the trigger level repeatedly is exhibiting behaviour that warrants review regardless of the nominal figure. Equally, applying thresholds inconsistently across different VIP tiers or account managers creates audit risk and potential discrimination claims.
4. Delayed Requests That Arrive After Significant Losses
Requesting SOW documentation after a player has already lost substantial sums is one of the most damaging operational patterns in terms of regulatory and reputational risk. The timing signals that the check was motivated by the relationship rather than the risk profile. Proactive triggers based on cumulative deposits, not cumulative losses, are the standard regulators expect to see.
5. Poor Documentation of the Assessment Decision
Holding a document is not the same as having conducted due diligence. The compliance file should record what evidence was received, what verification steps were taken, what open-source or third-party data was consulted, and the reasoning behind the decision to continue or restrict the account. A one-line note saying "documents reviewed, satisfied" will not satisfy a supervisory authority conducting a themed review.
What a Defensible High-Roller Check Looks Like
Operators who perform this well share several characteristics. They use risk-scored customer profiles that combine deposit behaviour, declared occupation, geography and payment method to generate proportionate requests. They document the evidential chain clearly, including what was verified externally. They conduct periodic review of existing high-value accounts rather than treating initial EDD as a one-time exercise. They also train account managers to understand that a compliance request is a customer service interaction requiring a clear explanation to the player, not an internal administrative task.
- Cross-reference declared income against deposit velocity over a rolling 90-day period.
- Use open-source checks such as Companies House, Land Registry or professional body registers where the player has declared business ownership or a regulated profession.
- Document the specific source of each large deposit individually, not just the general wealth picture.
- Set calendar-based review dates for ongoing high-roller monitoring, not just event-triggered reviews.
- Ensure the MLRO or a designated deputy signs off on high-risk continuations, creating a clear accountability trail.
The Operational Balance
There is a reasonable concern among operators that overly intrusive or clumsy due diligence requests drive high-value players to less regulated competitors. That concern is legitimate but it is not a compliance defence. The answer lies in process quality, not reduced rigour. A well-designed SOW workflow, delivered through an experienced account management team with clear scripting and a smooth document portal, is far less disruptive to the player relationship than many operators assume. The players who present genuine risk tend to disengage when checks are applied consistently and professionally. That outcome is precisely what the framework is designed to produce.
Compliance quality in high-roller due diligence is measured not by the documents collected but by the quality of the assessment made and the clarity of the reasoning recorded.
