Operator's Guide5 min read

UKGC compliance: connect each control to evidence

A policy describes what the business intends to do. Compliance also needs a working process, a responsible person and evidence that the control operates. For a GB-facing online casino or sportsbook, that work covers the customer account, gaming products, financial crime controls, suppliers and regulatory reporting.

Ivan KiselevIvan Kiselev
UKGC compliance: connect each control to evidence

This guide suggests an implementation method for remote operators. Apply it to your particular permissions and the current requirements. Software suppliers carry a different set of responsibilities and should start with the UK software licensing guide.

Establish the applicable requirements

Start with the permissions and conditions on the license. Identify the relevant LCCP provisions, Remote gambling and software technical standards (RTS), testing requirements and other applicable laws. Record the source version and effective date, including future changes not yet in force.

The UKGC RTS introduction separates requirements from implementation guidance. You can design your own implementation, as long as it meets the requirement. The guidance examples show one possible design.

For the law and the regulator's role, see the UK gambling legislation overview. Keep the operating control file on what your team must do and show.

Build a control-to-evidence matrix

The owners below are suggested functions. Assign a named person in your own organization to each control, even where a vendor runs the process or a policy describes it.

Control area

Working check

Evidence to retain

Suggested owner

Customer onboarding

Test applicable age and identity checks, including unsuccessful checks

Test account, outcome and exception/escalation record

Operations and compliance

Financial crime

Connect assessed risks to due diligence, monitoring and escalation

Risk assessment, case records and decision rationale

Relevant AML lead

Safer gambling

Verify how the team identifies risk, acts and reviews outcomes

Interaction records, restrictions and follow-up

Safer gambling lead

Self-exclusion

Test exclusion handling across the relevant systems and channels

Blocking and reconciliation results, incident records

Operations and engineering

Financial limits

Test default prompts, limit types, time periods and reductions

Recorded test cases and configuration/version

Product and compliance

Game release

Match applicable testing to the deployed product and build

Test report, release approval and change history

Technical management

Complaints

Trace receipt, response and the applicable escalation route

Case chronology and outcome

Complaints owner

Regulatory reporting

Reconcile return data and review reportable events

Submitted return, reconciliation and event assessment

Finance and compliance

For each control, add the governing provision, the applicability decision, a review date and the action to take if the control fails. Record the version and date with every successful test, so you can rely on it in a later investigation.

Bind testing to releases and changes

Follow the UKGC testing strategy for the product and change. Where independent testing is required, select a test house from the UKGC list that is approved for the relevant scope.

Use a release record that identifies the product, build, configuration, affected markets, report reference, approval and deployment date. Before you deploy a change, classify its effect on fairness and other applicable requirements. Tie each test report to the configuration it tested before you reuse it for a later release.

If you find a defect, record the affected versions and customers, your immediate containment decision, the correction and whether a notification duty applies. Build the release process so you can stop or withdraw the affected product while you assess the issue.

Check financial limits against the current RTS version

As checked on October 27, 2026, RTS 12 includes gross deposit limits, account-level limits, required time periods and customer prompts. The UKGC last updated the live section on September 30, 2026. The UKGC's implementation update first gave June 30; its update note of May 26, 2026 moved the second phase to September 30, 2026.

Test the journey in the live configuration: a new account, an existing account, a customer declining a limit, a reduction and overlapping limits. Check that the description on screen matches the calculation behind it. If the applicable definition requires gross deposits, a setting called “deposit limit” should calculate on gross deposits, not net.

For online slots, also check the age-dependent stake limits: £5 for players aged 25 and over and £2 for ages 18 to 24. Record the product and age scope with these values.

Separate customer risk and financial crime decisions

Financial vulnerability checks, safer gambling interactions and AML checks can draw on some of the same information. Each answers its own question. Build a route for the decision each process must make, and record the reasons for any action.

SR Code 3.4.4 sets the financial vulnerability threshold for operators within its scope. The threshold is deposits minus withdrawals exceeding £150 in a rolling 30-day period, subject to the provision's exceptions. The code does not apply to every software or host license, so check your scope first. Act on other information that indicates harm too, whatever the threshold shows.

Financial risk assessments (FRAs) are a separate check, and they are not live. A UKGC blog of July 7, 2026 describes a “careful, staged approach”. The UKGC will set the Stage 1 start date in its consultation response, which it has not yet published. Until then, keep FRAs, and any rules from the earlier pilot announcement, out of your live controls. Confirm the current provision for the activity you are implementing.

AML obligations also depend on the activity and its legal scope. At MGL Solutions we support AML programs, and the MGL AML service overview describes that work. Your UK control file should name the specific risk, action, accountable person and evidence for the proposed operation.

Keep reporting on a calendar

The current UKGC regulatory returns guidance requires quarterly returns, due within 28 days of the quarter-end. It also requires a nil return if, at the due date, you hold the relevant license but have not started or have ceased the activity.

Give the data extraction, reconciliation, review and submission of each return their own calendar dates. Handle key event reporting outside that quarterly workflow: a reportable change can require action before the next return.

For a change of corporate control, track the notification clock and the application-to-continue or surrender requirement as two separate deadlines. Name the people who assess each corporate change.

Handover from application to operation

Give the operating team the granted permissions, applicable requirements, named responsibilities, unresolved actions and current evidence locations. Use the application preparation guide to hand over a working dossier that someone keeps up to date.

If you need documentation support, the MGL compliance policies service describes what we offer. For any engagement, agree with us the jurisdiction, the deliverables and who implements what. You remain responsible for the licensed activity.

More From This Author

Rate This Article

Your feedback helps us improve our industry research and publish more useful insights for operators and founders. By sharing your opinion, you help our team better understand what topics matter most to professionals in the iGaming industry.

How Valuable Was It For You?
What Would Make It Better?