HMRC Remote Gaming Duty: What Your Platform Must Log to Survive an RGD Review

Remote Gaming Duty at 40% of profits, effective for all accounting periods beginning on or after 1 April 2026 under the Finance Act 2026 amendment, is now the single largest recurring cost for most remote gaming operators serving UK customers. The rate change was confirmed in the Autumn Budget 2025 Policy Paper and codified through Finance Act 2026 Schedule 13. Yet the debate inside compliance and finance teams has centred almost entirely on the duty rate itself. The mechanics of what your platform must actually log, transaction by transaction, player by player, to support an accurate return and survive an HMRC records inspection receive far less attention. That is a material gap: at 40% of profits, an under-declared return is not a rounding problem. It is a liability HMRC can assess with interest across four years of records.

This article sets out the specific data architecture your platform must produce to satisfy HMRC’s RGD filing and records obligations. It draws on the Finance Act 2014 (Part 3, Chapter 3), Excise Notice 455A (the primary HMRC operational notice on RGD from 1 December 2014), Statutory Instrument 2014/2912 (Returns, Payments, Information and Records Regulations), and SI 2014/2257 (Registration, Records and Agents Regulations). Compliance teams should engage qualified tax counsel for jurisdiction-specific application of these obligations to their particular platform architecture.

The Legal Framework: What Gives HMRC the Right to Your Data

HMRC’s power to inspect operator records does not flow from the Finance Act 2014 alone. It rests on the older and broader authority of sections 118A and 118B of the Customs and Excise Management Act 1979. Under section 118A, HMRC officers have the right to see and take copies of any records, accounts, or other documents relating to the business. Section 118B extends this to require the reasonable production of information and documents, including taking copies or extracts. The Revenue Traders (Accounts and Records) Regulations 1992 (SI 1992/3150) provide the general framework for what revenue traders must maintain.

Excise Notice 455A has force of law for specific provisions under those instruments and the Finance Act 2014. Paragraphs within the notice that carry statutory authority are identified as such in the document. The notice covers the entire RGD regime from 1 December 2014 onward, superseding the earlier Notice 455. Operators who are liable to pay RGD are revenue traders under the Revenue Traders (Accounts and Records) Regulations, which means the general excise record-keeping obligation applies in full, supplemented by the RGD-specific requirements in Notice 455A.

What Counts as a Taxable Event: Defining the Log Perimeter

RGD is charged on a gaming provider’s profits from remote gaming with UK persons. The Finance Act 2014 section 155 defines a “chargeable person” as any UK person, meaning an individual who usually lives in the UK, and any body corporate not legally constituted in the United Kingdom where the gaming provider knows, or has reasonable cause to believe, that at least one potential beneficiary of prizes is a UK person.

Section 154 defines “remote gaming” as playing a game of chance for a prize by means of remote communication, where the playing of that game constitutes the provision of a gaming service in the United Kingdom. The two variants of remote gaming, ordinary gaming and pooled prize gaming, have different profit calculation methods set out in sections 156 and 157, and your logging architecture must support both. For ordinary gaming (section 157), profit is stakes received from UK persons less prizes provided to UK persons. For pooled prize gaming (section 156), the calculation runs through a multi-step process involving contributions to a gaming prize fund, top-up payments, and withheld amounts.

The UK-Person Determination Log: The Audit Pivot Point

The most frequently contested element in any HMRC RGD review is the operator’s methodology for determining whether a customer “usually lives in the UK.” Notice 455A directs operators to this determination and instructs them to check the notice for more information. The determination is not binary: HMRC expects documented evidence for each account classification, not merely a checkbox in your CRM.

Your platform must log, per player account, the evidence used to make the UK-person determination at the point of account opening and any subsequent re-determination. This includes the IP address geolocation data used at registration, the billing address on file, the payment instrument country code, any identity document jurisdiction, and the operator’s own written methodology for resolving conflicts between these signals. Where a player’s classification changes, for example a UK-resident who notifies a change of address to a non-UK jurisdiction, the platform must log the date of re-determination and the evidence supporting it. HMRC does not prescribe a specific methodology for making the determination, but if your records cannot show how you reached a classification for each account, an assessor can substitute their own view of what proportion of your players were UK persons.

Account-level data must be queryable by accounting period. If HMRC requests a schedule of UK-person determinations for a specific quarter, your platform must be able to produce it. A manual reconstruction from disparate CRM, KYC, and payment processor records is not a substitute for structured, contemporaneous logs.

Transaction-Level Data: The Minimum Required Log Entries

The Gambling Tax Service return for RGD requires the filing of aggregate profit figures: gross stakes from UK persons, prizes paid to UK persons, and the resulting net profit on which duty is charged. Those aggregate figures must be supportable by transaction-level records. The following table sets out the minimum data points that your platform must be capable of producing per gaming session or transaction to reconstruct an RGD return under HMRC scrutiny.

Data Element	Why It Is Required	Failure Mode
Player account identifier (unique)	Ties each gaming transaction to a UK-person determination record	Cannot link taxable transactions to player classification evidence
UK-person classification flag (per account, per period)	Determines whether the transaction falls within RGD scope	HMRC substitutes its own assessment of UK-player proportion
Transaction timestamp (date and time, UTC)	Places the transaction within the correct accounting period	Period-boundary transactions mis-allocated, period profit overstated or understated
Game type (ordinary gaming / pooled prize gaming)	Selects correct profit calculation method under ss.156, 157 FA 2014	Pooled and ordinary profits calculated on wrong basis, material mis-declaration
Stake amount (actual payment received)	Input to the profit calculation under s.157(1)(a)	Understated or overstated stake aggregates, inaccurate return
Freeplay flag and nominal stake value	Finance (No. 2) Act 2017 s.46 brought freeplay offers into scope, the nominal full-amount stake is treated as having been made	Freeplay sessions excluded from scope, under-declaration of dutiable profits
Prize paid (monetary value)	Deducted from stakes under s.157(1)(b) to arrive at ordinary gaming profit	Incorrect prize deductions inflate or deflate net profit
Gaming prize fund assignment (for pooled gaming)	Step 1 of the pooled prize gaming calculation under s.156	Pool contributions mis-stated, retained-prize calculations under s.158 distorted
Retained prize amounts and cessation dates	Section 158 requires recognition of retained prizes when qualifying amounts cease	Retained-prize profits omitted from return, under-declaration across multiple periods
Accounting period identifier	Aggregates must map to a specific quarter (standard: 3-month periods)	Transactions attributed to wrong return period, potential overclaim or underclaim

Freeplay Logging: The Change Most Platforms Have Not Fully Implemented

The Finance (No. 2) Act 2017, section 46, inserted section 160A into the Finance Act 2014 with effect from a date specified in HMRC commencement orders. This provision brought freeplay offers, defined as offers that waive all or part of a gaming payment, into the RGD charge. Where a chargeable person participates in remote gaming in reliance on an offer that waives the entire gaming payment, that person is treated as having made a gaming payment equal to the amount that would have been required without the offer. Where the offer waives only part, the person is treated as having made an additional gaming payment equal to the difference.

“Where the chargeable person participates in the remote gaming in reliance on an offer which waives all of a gaming payment, the person is to be treated as having made a gaming payment of the amount which would have been required to be paid without the offer.”

Your platform must record, per freeplay session: the game type, the player’s UK-person status, the nominal stake value that would have been required without the freeplay offer, the timestamp of the session, and whether the freeplay was redeemed in that session or carried forward. Many platforms log whether a freeplay was used but do not record the full nominal stake value in a field that feeds into the RGD computation. That is a structural gap. If a proportion of your promotional budget runs through freeplay offers to UK-resident players, the omission creates a systematic under-declaration of dutiable profits.

Pooled Prize Gaming: Additional Log Requirements

Pooled prize gaming, encompassing jackpot products and similar pooled mechanics, requires a more detailed ledger than ordinary gaming. Section 156 of the Finance Act 2014 requires a multi-step calculation. Your platform must log, per accounting period: the aggregate of relevant gaming payments made to the gaming prize fund, any payments assigned to the fund and deducted at Step 1, any top-up payments made by the gaming provider to the fund, any prizes paid from the fund to UK persons, and any residual amounts remaining in the fund at period end that may constitute retained prizes under section 158.

Retained prizes are recognised as profits under section 158 when “qualifying amounts cease to be qualifying amounts,” in practice when the gaming provider is no longer obligated to pay them out. The date on which an unclaimed prize lapses must be captured as a discrete log event, because that date determines the accounting period in which the retained-prize profit is recognised. If your system closes unclaimed jackpot amounts without a timestamped event record, you cannot reconstruct retained-prize recognition across multiple periods, and HMRC will challenge any period in which retained prizes appear to have been omitted.

Return Filing Architecture: The 30-Day Rule and the GTS Interface

SI 2014/2912 Regulation 3 requires an RGD return for each accounting period not more than 30 days after the end of the period. The standard accounting period for RGD is quarterly (three months), though HMRC will agree non-standard periods in limited circumstances. If the 30th day falls on a weekend or bank holiday, the return and payment are due by the end of the previous working day. Returns must be filed even for periods in which no duty is payable: a nil return is not optional.

Returns are submitted through the Gambling Tax Service (GTS), HMRC’s electronic filing system. The GTS return for RGD requires two headline figures: profits in the period on which tax is due, and negative profits from a previous return, which can be carried forward under section 155(5) to reduce profits in later periods. The simplicity of those two fields masks the data complexity required to produce them accurately. Your platform’s RGD computation pipeline must be able to generate, at period end, the following aggregates from transaction-level records: total gaming payments received from UK persons, total prizes paid to UK persons, the net ordinary gaming profit, separately computed pooled prize gaming profit, retained prize additions, and any carry-forward of negative profits from preceding periods.

How Long Must RGD Records Be Kept, and What Does “Readily Accessible” Mean?

HMRC guidance confirms that records must be kept for four years, as HMRC might ask to see them at any point within that window. For RGD, the relevant section of Notice 455A sets out the records applicable to the remote gaming duty specifically. Records must be kept in a readily accessible format and produced when asked: this is not a procedural formality but an operational requirement that your data architecture must satisfy.

In practice, “readily accessible” means that an HMRC officer arriving for a records inspection should be able to receive structured exports of transaction-level data within a timeframe consistent with a scheduled review, not weeks of engineering effort. Platform logs stored in raw event streams without a queryable layer, or archived to cold storage without an indexed retrieval mechanism, fail this standard. Compliance teams should confirm with their engineering counterparts that transaction logs are stored with immutability controls that prevent retroactive amendment, indexed by accounting period and player account identifier, exportable in a structured format (CSV or equivalent) covering all the fields set out in the section above, and retained for the full four-year window including periods following any platform migration or supplier change.

The Records Regulations at SI 2014/2257 also address the question of agents. Where an operator acts through a UK fiscal representative or tax agent, the records obligations follow the operator, not the agent. Joint and several liability for groups of corporate bodies under common control is established at SI 2014/2257 Regulation 4, which means intra-group platform arrangements do not distribute or dilute the record-keeping obligation.

The Intersection with UKGC Record-Keeping: Dual Compliance Advantage

The Gaming Duty Excise Notice 453, the premises-based gaming equivalent of Notice 455A, observes that “any records that the Gambling Commission ask you to keep under their social legislation will normally be sufficient for our purposes.” This principle carries across to RGD, though with important caveats. The UKGC’s Licence Conditions and Codes of Practice require licensees to maintain extensive records of customer interaction, account history, and transaction data to support responsible gambling and anti-money laundering obligations. Those records overlap substantially with the transaction-level data HMRC requires, but they are not identical.

The key gap is the UK-person determination log. The UKGC does not require a specific field recording the evidence used to classify a player as UK-resident for tax purposes. KYC records establish identity and age, but the RGD determination is specifically about usual place of residence, not legal identity, and the evidence base may differ. A player verified as over 18 via a UK-issued document may no longer “usually live” in the UK if they have permanently relocated. Your platform’s data architecture should treat the UK-person determination as a distinct, tax-specific record that sits alongside but is separate from your UKGC KYC and responsible gambling records. A full account of the UKGC’s remote operating licence obligations, including the record-keeping and technical requirements that underpin those obligations, is available in the UKGC licence requirements profile.

For operators holding a UKGC remote operating licence alongside their RGD registration, there is a meaningful compliance dividend in a unified data schema. A single transaction record that captures account ID, timestamp, game type, stake, prize, UK-person flag, and freeplay indicator serves both regulatory frameworks. The alternative, maintaining separate logging streams for regulatory and tax purposes, creates reconciliation risk at every period end. UKGC vs MGA licence cost modelling demonstrates how the 40% RGD rate now dominates the total cost of UK market participation, making accurate computation more financially consequential than at any prior rate.

The Proposed Remote Betting and Gaming Duty: What Changes and What Does Not

HM Treasury published a consultation in April 2025 proposing to merge RGD, General Betting Duty, and Pool Betting Duty into a single Remote Betting and Gaming Duty (RBGD). The Autumn Budget 2025 Policy Paper subsequently confirmed that the government would not proceed with a single unified rate, retaining differentials between remote betting and gaming duties. The 40% RGD rate is confirmed for accounting periods beginning on or after 1 April 2026. The proposed RBGD, if introduced, is currently expected no earlier than October 2027 and remains subject to further consultation and Budget-process rate-setting.

The consultation confirmed that existing digital filing infrastructure, the Gambling Tax Service, would require modification to support RBGD, and that HMRC would engage with businesses on changes to registration and accounting systems. Critically, the April 2025 consultation document confirmed that the point-of-consumption model would be retained: RBGD would be charged on profits from UK customers, determined by the same UK-person methodology that applies under current RGD. The record-keeping architecture described in this article is therefore not a transitional solution. It is the permanent framework, subject to system changes that HMRC has committed to consulting operators on before implementation.

“Remote gambling providers with a liability to RGD, GBD and PBD already transact digitally with HMRC, including submitting returns through the Gambling Tax Service. Streamlining the current three online taxes into a single tax will require some changes to how these systems currently operate.”

Penalties and Enforcement: The Consequence of Logging Gaps

Non-compliance with RGD obligations attracts civil penalties under Finance Act 1994 section 9. HMRC guidance sets out four primary failure modes that generate penalties: failure to notify business changes on time, failure to file returns and pay by the due date, inaccurate returns that result in under-payment, and failure to notify HMRC that a duty assessment is too low. The last category is particularly relevant for logging failures: if HMRC issues an assessment based on estimated figures and the assessment is too low, the operator has an affirmative obligation to notify HMRC. Silence in the face of an under-assessment is itself a penalty trigger.

Beyond penalties, the April 2025 consultation confirmed that the sanctions regime introduced alongside the 2014 point-of-consumption reforms remains in force. These include HMRC working with other tax jurisdictions to recover outstanding debts, HMRC requiring operators with poor compliance history to provide financial security, and HMRC having powers to prosecute serious non-compliance. The financial security requirement, effectively a bond or deposit against future duty liability, is a material operational consequence for any operator who accumulates a non-compliance record. At a 40% duty rate, even a moderate revenue base generates a significant annual RGD liability, making the financial security quantum potentially large.

Operators with multi-product platforms that combine remote gaming with sports betting should also track the General Betting Duty implications in parallel. GBD at 25% on remote betting profits applies from 1 April 2027 under the Autumn Budget 2025 proposals. A single platform that commingles gaming and betting transaction flows without product-level tagging will face the same logging problems for GBD that this article addresses for RGD. The time to implement product-level transaction classification is now, before the GBD rate change takes effect.

Compliance teams managing the interface between HMRC tax obligations and their UKGC licence conditions should also review MGA system audit requirements, which sets out a comparable analysis of platform logging obligations under a different regulatory regime, useful context for operators holding dual licences.

Key Resources

Finance Act 2014, Part 3 Chapter 3 (sections 154, 162): Primary legislation establishing the RGD charge, defining “remote gaming,” “gaming provider,” “chargeable person,” and the profit calculation methods for ordinary and pooled prize gaming. Available at legislation.gov.uk.

Excise Notice 455A: Remote Gaming Duty (HMRC, updated to reflect 1 April 2026 rate): The operational notice governing RGD from 1 December 2014. Certain paragraphs have force of law under the Finance Act 2014, SI 2014/2257, SI 2014/2912, and the Revenue Traders (Accounts and Records) Regulations 1992. Available at gov.uk.

SI 2014/2912, The General Betting, Pool Betting and Remote Gaming Duties (Returns, Payments, Information and Records) Regulations 2014: Sets the 30-day return deadline (Regulation 3) and the 30-day extended payment window (Regulation 4). Available at legislation.gov.uk.

SI 2014/2257, The General Betting, Pool Betting and Remote Gaming Duties (Registration, Records and Agents) Regulations 2014: Governs registration requirements, group registration, and the appointment of agents and UK fiscal representatives. Available at legislation.gov.uk.

HM Treasury Consultation: The Tax Treatment of Remote Gambling (April 2025): Sets out the proposed RBGD framework, confirms retention of the point-of-consumption model, and addresses transitional system changes to the Gambling Tax Service. Available at gov.uk.

Autumn Budget 2025 Policy Paper, Changes to Gambling Duties (November 2025): Confirms the 40% RGD rate from 1 April 2026, the 25% GBD rate from 1 April 2027, and the decision not to proceed with a unified RBGD rate. Available at gov.uk.