Source of wealth and source of funds checks remain the sharpest compliance edge for iGaming operators managing high-value player relationships. Done poorly, they create friction that drives VIPs to competitors. Done well, they build defensible audit trails, satisfy regulators across multiple jurisdictions, and reduce exposure to financial crime. This 90-day roadmap gives compliance teams and operational leads a structured path from policy gap to live process.
Why High Rollers Require a Distinct AML Framework
Standard know-your-customer onboarding is not sufficient for players who deposit or wager above defined thresholds. Regulators including the UK Gambling Commission, Malta Gaming Authority, and Dutch Kansspelautoriteit expect operators to understand not just who a high-value player is, but where their money originates and whether their accumulated wealth is consistent with observed play patterns. Failing to draw this distinction is one of the most common findings in regulatory audits conducted throughout 2024 and 2025.
The practical difference matters operationally. Source of funds (SOF) establishes the immediate origin of specific deposits, such as a salary payment or the sale of an asset. Source of wealth (SOW) maps the broader accumulation of a player's overall financial position. Both are required for a complete enhanced due diligence profile, and regulators treat them as complementary rather than interchangeable.
Days 1 to 30: Policy, Thresholds, and Ownership
The first phase is foundational and should produce four concrete outputs.
- Threshold definition: Set deposit, loss, and net gaming revenue triggers that automatically flag a player for enhanced due diligence. Many operators align with the FATF guidance and local regulatory thresholds, but internal risk appetite should shape the final numbers. Document the rationale.
- Policy gap analysis: Compare your current AML policy against the specific SOW and SOF requirements in each jurisdiction where you hold a licence. Identify clauses that are vague, missing, or untested.
- MLRO sign-off: The Money Laundering Reporting Officer must formally own the updated policy and the escalation path from operational staff to senior management. Assign named individuals, not job titles alone.
- Document template library: Build a standardised set of acceptable evidence categories, payslips, tax returns, company accounts, inheritance documentation, property sale records, and create a weighting matrix so case handlers apply consistent judgement.
Days 31 to 60: Systems, Training, and Player Communication
Policy without operational infrastructure produces inconsistent outcomes. The middle phase focuses on embedding the framework into daily operations.
- CRM and back-office integration: Configure automated alerts so that when a player crosses a threshold, the compliance queue is populated immediately. Manual spreadsheet tracking is not scalable and creates audit risk.
- Case management workflow: Define the decision tree from alert to resolution. Include time limits for each stage, typically 72 hours for initial outreach and 14 days for document review, so that stalled cases do not sit unresolved.
- Staff training: VIP account managers are often the first point of contact. Train them to request documentation in a tone that is professional, non-accusatory, and consistent. Role-play sessions using realistic scenarios reduce hesitation and improve compliance rates.
- Player communication scripts: Draft templated messages that explain why documentation is needed, what is acceptable, and what happens if a player does not respond. Transparency reduces drop-off rates at this stage.
Days 61 to 90: Live Testing, Audit Trails, and Continuous Review
The final phase validates the system under real conditions and prepares the operator for regulatory scrutiny.
- Parallel running: Run the new process alongside existing procedures for the first two weeks of this phase. Compare outcomes and identify gaps before full cutover.
- Audit trail quality: Every SOW and SOF decision must be documented with the evidence reviewed, the handler's assessment, and the senior approval where required. Regulators expect to reconstruct the decision-making process from the file alone.
- Suspicious activity reporting integration: Ensure that players who cannot satisfactorily evidence their wealth are routed to the MLRO for SAR consideration, not simply declined and closed without further action.
- Quarterly review schedule: SOW profiles are not static. A player's financial position changes. Build a calendar-based refresh cycle, typically every 12 months for active high-value players, into the ongoing compliance programme.
Operators who treat source of wealth checks as a one-time event rather than a continuous risk signal consistently underestimate their exposure during regulatory inspections.
Operational Considerations for Multi-Licence Operators
If you hold licences in multiple jurisdictions, the 90-day roadmap must be applied once per regulatory regime, not once across the business. Thresholds, acceptable documents, and SAR obligations differ between, for example, a UK licence and a Malta licence. A centralised compliance function with jurisdiction-specific overlays is the most efficient structure for managing this complexity without duplicating operational effort unnecessarily.
