Gambling Licensing

UKGC Financial Risk Assessments: Operator Preparation

UKGC financial risk assessments are moving towards implementation, but the first-stage start date has not yet been confirmed. Remote gambling operators serving Great Britain should distinguish the announced approach from requirements already in force before changing customer journeys or instructing suppliers.

For businesses reviewing their British operating model, gambling licence advisory should connect regulatory interpretation with practical delivery. The immediate task is to prepare a controlled implementation plan, with assumptions clearly marked and existing customer-protection controls maintained.

Status checked: 18 November 2026. The preparation steps below are advisory recommendations. They are not a substitute for the Gambling Commission’s forthcoming formal response or final technical requirements.

What changed in the November UKGC update?

In its 17 November implementation update, the Gambling Commission confirmed that two implementation groups are operating. One addresses delivery with operators and credit reference agencies; the other focuses on credit information arrangements. Systems integration, technical definitions and implementation dependencies remain under discussion.

The formal consultation response is expected in the coming weeks. The Commission says it will confirm the Stage 1 implementation timeline at the end of the year. The largest operators will be first, with smaller operators and business-to-business representatives also contributing to preparation.

For a compliance team, this is a reason to organise delivery work now while keeping final configuration subject to the published requirements. Treat a supplier’s provisional specification as a dependency to review, rather than evidence that the regulatory position is settled.

Which financial risk assessment thresholds have been announced?

The Commission’s July staged-implementation announcement sets out the following framework. These are announced stages, not confirmation that every threshold is currently operative.

Stage Customers aged 25 and over Younger customers / higher-risk group
Stage 1 Net deposits exceeding £5,000 over a rolling 24 hours Net deposits exceeding £2,500 over a rolling 24 hours
Interim stages To be set following further engagement To be set following further engagement
Final implementation Net deposits exceeding £1,000 over 24 hours or £3,000 over 90 days For under-25s: exceeding £750 over 24 hours or £2,000 over 90 days

Build threshold scenarios into a test plan, with clear version control. Ask product and engineering teams to document how rolling windows, withdrawals, age changes and incomplete transaction data would be handled. These are implementation questions for confirmation, not additional technical rules supplied by this article.

A useful release record should identify the source supporting each setting, the person approving it and the date on which it becomes applicable. Avoid embedding provisional values in several systems where a later change could leave inconsistent customer treatment.

How do assessments differ from financial vulnerability checks?

Financial vulnerability checks are an existing, separate control. Social Responsibility Code 3.4.4 requires covered licensees to check public records for significant vulnerability indicators. Since 28 February 2025, the threshold is deposits minus withdrawals exceeding £150 in a rolling 30-day period.

The code also requires consideration of other permitted customer information, proportionate action and a recorded rationale. It includes an exception where a financial vulnerability check or financial risk assessment has been conducted within the preceding 12 months. Operators should check the condition’s licence scope and full wording when reviewing their procedures.

Keep the two processes separately named in operating procedures, training and dashboards. A customer-service colleague should be able to identify which process generated a case, what information was used and which escalation route applies. A generic label such as “financial check” makes those distinctions harder to maintain.

Do financial risk assessments replace AML source-of-funds checks?

No. The Commission’s explanation of financial enquiries distinguishes checks on the legitimacy of funds from concerns about financial harm. A financial-risk result should not be treated as proof that the customer’s money has a legitimate origin.

Maintain separate decision records for safer gambling and anti-money laundering (AML), even where the same customer is being reviewed. Each team should understand the purpose of the information it receives and the limits of the conclusion it can draw. Our article on gambling AML controls addresses that wider compliance context.

As a preparation exercise, trace a sample customer case through both workflows. Check whether a closed safer-gambling case could accidentally close an unresolved AML task, or whether a document request gives the customer an inaccurate explanation of its purpose. Correct those workflow weaknesses without assuming a future assessment will resolve them.

What should operators prepare before implementation?

Assign ownership across the delivery chain

Appoint an accountable lead and identify the decisions requiring compliance, product, engineering, data-protection and customer-operations input. Record supplier dependencies alongside internal work. A project plan that lists only an integration delivery date will miss the operational decisions needed after a result arrives.

Ask each supplier what remains provisional, what evidence supports its proposed configuration and how changes will be communicated. Define who accepts updated specifications and who checks their effect on customer handling. This is particularly useful where a platform provider and a separate case-management supplier share the workflow.

Design the response to incomplete or unmatched results

In its July explanation of financial risk assessments, the Commission described limited credit-reference information intended to identify current financial difficulties. It also explained that some customers may not receive a document-free result, including because identity details are inaccurate or credit-reference records have not caught up with a move or name change.

Prepare an exception queue that distinguishes a failed technical request from an unresolved identity match and an assessment indicating financial difficulty. Record the responsible team and next action for each scenario. Test what happens if a supplier is unavailable or returns a response the receiving system does not recognise.

Control access and customer communications

The July explanation says assessment information must be used for regulatory purposes and not commercial purposes. It also describes proportionate support informed by the wider customer picture, including reducing marketing or supporting deposit limits.

Review proposed data flows before giving broad access to results. Document which roles need information to make a decision and which systems need only the resulting operational instruction. Keep sensitive assessment detail out of general sales notes and promotional segmentation.

Prepare customer explanations for different outcomes and have compliance review them. Staff should distinguish an unresolved information issue from a decision based on identified risk. Avoid promising a document-free experience in every case, and make the route for questions or review understandable.

Build an evidence pack for testing and approval

Use a release checklist covering configuration, supplier testing, exception handling, permissions, staff training and decision records. Include expected outcomes for ordinary cases and failure scenarios. Retain evidence showing what was tested, which issues remained and who accepted the release.

Separate regulatory assumptions from completed work. For each open point, record the official publication or supplier clarification needed to close it. This makes it easier to update the plan when the formal response arrives without reopening decisions that were already supported.

Where an operator uses outsourced AML and compliance support, agree the boundary between advisory oversight and operational ownership. Outsourcing a review should not leave customer cases without an internal decision-maker.

What remains uncertain?

The November update does not supply a confirmed Stage 1 commencement date. Detailed implementation work continues. Operators should track the formal response and subsequent timetable announcement rather than infer a deadline from the date of a blog post.

The July announcement describes limited early-stage enforcement reassurance for failure to act following an assessment, while expressly preserving existing licence requirements. It should not be read as general permission to pause customer protection. Keep current controls operating while the new process is prepared.

This article concerns financial-risk preparation. Separate controls, including player fund segregation, still need their own procedures and assurance. Do not combine unrelated compliance sign-offs into a single “FRA ready” status.

FAQ

Are UKGC financial risk assessments already live for every operator?

The announced approach is staged, beginning with the largest operators. As at 18 November 2026, the latest implementation update has not confirmed the Stage 1 start date.

Is the £150 vulnerability check the same assessment?

No. It is a separate public-record financial vulnerability check under Social Responsibility Code 3.4.4. Keep its workflow distinct from preparation for credit-reference-based assessments.

Should smaller operators prepare now?

They can map systems, responsibilities and supplier dependencies now. Final configuration and release decisions should follow the requirements and timetable applicable to their business.

What should management request from the project team?

Request a gap assessment, a supplier-dependency list and a test plan with named owners. Ask which settings remain assumptions and what evidence will be needed before release approval.

How VMGlobals can help

VMGlobals can help operators review the regulatory scope, map compliance responsibilities and prepare implementation questions for suppliers. A focused gap assessment can turn the published requirements into a practical action plan while keeping unresolved regulatory points visible.

More insights