Building a Compliance Calendar: Recurring Reporting Deadlines Across UKGC, MGA, and AGCO

Compliance teams holding operating licences across the UK Gambling Commission, the Malta Gaming Authority, and the Alcohol and Gaming Commission of Ontario face a shared structural problem: three regulators, three distinct submission rhythms, and a calendar that does not care about your resourcing gaps. The consequences of missing a filing are not theoretical. The MGA enforcement register contains multiple decisions cancelling licences specifically because a licensee failed to submit player fund reports or compliance contribution calculations within the required timeframe. The UKGC routinely references late or inaccurate regulatory returns in its published regulatory settlements. AGCO enforcement actions against FanDuel and theScore have underlined that in Ontario, compliance documentation is scrutinised in detail.

This article maps the mandatory recurring submission obligations across all three regulators, anchored to the primary regulatory instruments in each jurisdiction, and organises them into an annotated annual calendar framework that compliance officers can adapt to their own financial year. It does not cover one-off application submissions or ad hoc regulatory requests, which fall outside a calendar planning model. Operators should treat this analysis as a structural framework and obtain jurisdiction-specific legal advice before finalising their internal deadlines, particularly where financial year-end dates or licence-specific conditions vary from the defaults described here.

Why a Multi-Regulator Calendar Matters

The instinct to manage UKGC, MGA, and AGCO compliance in separate silos is understandable. Each regulator has its own submission portal, its own terminology, and its own enforcement culture. But the calendar problem is cross-regulator by nature. A licensee with a December financial year-end will face MGA audited accounts due by late June, UKGC Q4 regulatory returns due in late January, and AGCO notification obligations running continuously. A licensee with a March financial year-end shifts those windows but does not simplify them.

The compounding effect is most acute in Q1 of the calendar year, when UKGC Q4 returns, MGA December player funds reports, and any financial year-end triggered MGA accounts submissions often land within weeks of each other. Compliance teams that do not pre-map these intersections routinely discover deadline conflicts only when a submission is already overdue. The practical answer is a master calendar built from each regulator’s primary instruments, reviewed at the start of every licence year, and owned by a named compliance function rather than distributed across finance, legal, and operations as separate workstreams.

UKGC: The Quarterly Return Cycle and Key Event Obligations

The foundational recurring obligation under the UKGC Licence Conditions and Codes of Practice is found at Licence Condition 15.3.1, which applies to all operating licences. It requires that, within 28 days of the end of each quarterly period, licensees submit an accurate Regulatory Return to the Commission in the form specified by eServices, the Commission’s online portal. The UKGC defines quarterly periods by reference to the licence year rather than the calendar year, so licensees must verify their specific quarter-end dates on initial issue and after any licence variation.

“Within 28 days of the end of each quarterly period licensees must submit an accurate Regulatory Return to the Commission containing such information as the Commission may from time to time specify.” : UKGC Licence Conditions and Codes of Practice, Licence Condition 15.3.1

The content of the Regulatory Return varies by licence type. Remote casino licensees, remote betting licensees, and combined licence holders submit different data fields. Historically the returns captured GGY figures, customer activity metrics, and responsible gambling interaction data. The Commission has consulted periodically on expanding the data scope of returns, and compliance teams should verify the current data specification against eServices at the start of each licence year. Inaccurate returns are treated as a separate breach from late returns: the LCCP requires the submission to be “accurate”, not merely timely.

Alongside the quarterly cycle, Licence Condition 15.2.1 governs the reporting of key events. The definition is broad: a key event is any event that could have a significant impact on the nature or structure of the licensee’s business. The LCCP requires licensees to report key events as soon as reasonably practicable and in any event within five working days of becoming aware of the event’s occurrence. Key events specified in LC 15.2.1 include, among others: a person becoming a shareholder holding five percent or more of the issued share capital (or voting rights, or dividend entitlement) of the licensee or its holding company; the appointment of or departure from a key position; the taking of a loan from any person not authorised by the Financial Conduct Authority; and a change in the location of key equipment.

Under Licence Condition 12.1.1 and the Money Laundering Regulations 2017, operators must maintain effective anti-money laundering and counter-terrorist financing controls, supported by ongoing risk assessments, governance oversight, and documented policies and procedures. Operators are expected to keep these controls under regular review and ensure that senior management and MLRO reporting structures provide effective oversight of AML effectiveness and emerging risk exposure. Larger operators may also be required to provide assurance statements or supervisory materials addressing AML effectiveness, safer gambling controls, and broader licensing objective risks as part of the UKGC’s risk-based supervisory framework. Separately, the Commission has indicated that certain AML failures or significant compliance breakdowns may trigger reporting obligations under LC 15.2.1 where the issue constitutes a reportable key event or materially impacts the licensee’s regulatory standing.

MGA: Monthly, Half-Yearly, and Annual Financial Filings

The Malta Gaming Authority operates the most granular recurring filing schedule of the three regulators covered here. The primary instrument is Directive 3 of 2018 : Gaming Authorisations and Compliance Directive (V2, October 2021), which sets out the reporting architecture for both B2C and B2B licensees.

The most frequent obligation is the monthly player funds report, governed by Article 39 of Directive 3 of 2018. All B2C licensees must provide the MGA with a monthly report on player funds in the format established by the Authority. The deadline is no later than twenty days following the end of the reporting month. This means a January player funds report is due by 20 February, a February report by 20 March, and so on throughout the year, generating twelve fixed deadlines annually. The MGA has reserved the right to extend this obligation to B2B licensees where those licensees hold player funds in connection with a pooled jackpot or otherwise.

“The player funds report must be submitted to the Authority no later than twenty (20) days following the end of the reporting month to which it refers.” : MGA Directive 3 of 2018, Article 39(2)

The importance of this deadline is not theoretical. The MGA enforcement register records multiple licence cancellations citing failure to submit player fund reports within the stipulated timeframe. In one published decision, the Authority cancelled a B2C licence in part because the licensee had failed to submit player fund reports for a consecutive run of months. Compliance teams that treat the monthly player funds report as a finance function task rather than a compliance function obligation are creating a structural gap: the report must be in the MGA’s Licensee Relationship Management System (LRMS) by day 20, not merely prepared by that date.

Article 40 of Directive 3 of 2018 requires licensees to file returns under the Gaming Licence Fees Regulations and the Gaming Tax Regulations in the manner required by those instruments. These returns track gaming revenue and compliance contribution calculations. Failures to submit the Compliance Contribution Calculator within the stipulated timeframe have featured in MGA enforcement decisions, in some cases alongside the player funds report failures that triggered cancellation.

For financial accounts, Article 41 of Directive 3 of 2018 establishes two distinct obligations. First, for the first six months of the financial year, licensees must submit management accounts signed by the key person responsible for the licensee’s finances by not later than the last day of the eighth month of the financial year. For a December financial year-end, this means the half-year accounts covering January to June must be submitted by 31 August. Second, licensees must submit audited financial statements within 180 days from the end of the financial year. For a December year-end, that is 28 June of the following year. For a March year-end, it falls in late September.

The MGA also operates a system of Agreed-Upon Procedures (AUPs) for B2C licensees. Under the AUP framework, licensees whose accounts fall within the defined scope must engage an approved auditor to prepare the AUP report on player funds and gaming revenue, and submit it through the LRMS. The MGA’s FAQs confirm that the compliance obligation rests with the licence holder, not the external practitioner, even where the auditor submits on the licensee’s behalf. Compliance teams should calendar the AUP engagement letter and no-conflict-of-interest declaration as separate milestones preceding the actual submission deadline.

AGCO: Outcomes-Based Notification and Ongoing Transparency Obligations

The AGCO’s Registrar’s Standards for Internet Gaming, which came into force on 4 April 2022 and were most recently updated in May 2025, reflect a deliberately outcomes-based regulatory model. Unlike the UKGC’s fixed-date quarterly returns or the MGA’s calendar-anchored monthly filings, the AGCO framework does not publish a single comprehensive schedule of recurring submission deadlines in the same format. Instead, the Standards create a continuous obligation of transparent engagement and timely notification that functions as a rolling compliance calendar obligation.

Standard 1.13 of the Registrar’s Standards requires operators to engage with the Registrar in a transparent way. At a minimum, operators must provide information requested by the AGCO promptly and ensure that all communications with the AGCO are accurate and complete. This transparency standard underpins the notification architecture: operators cannot wait for the AGCO to ask before disclosing material developments.

Standard 1.02 addresses the control environment directly. It requires that substantial changes to the Operator’s control environment be communicated to the Registrar in a timely manner. The AGCO does not define “timely” with a numerical deadline in the way the UKGC does with its five-working-day key event window, but the outcomes-based model means the Registrar will assess timeliness in light of the nature and impact of the change. In practice, compliance teams should treat any material platform change, significant supplier transition, corporate restructuring, or AML framework revision as triggering an immediate notification assessment.

The AGCO also publishes a Notification Obligations document, referenced explicitly in the Registrar’s Standards, which lists the specific circumstances in which operators and gaming-related suppliers must notify the AGCO. Operators should review this document at least annually and cross-reference it against their corporate change log. The document is a living instrument that the AGCO updates as the market matures. Compliance teams entering the Ontario market for the first time frequently underestimate the breadth of the notification obligations because the Registrar’s Standards present them at a high level of generality.

In enforcement, AGCO and iGaming Ontario have demonstrated a consistent pattern: failures in responsible gambling monitoring, advertising compliance, and betting integrity reporting have drawn the largest penalties. The $350,000 penalty imposed on FanDuel for failing to identify and report suspicious betting activity on Czech Table Tennis matches, and the $105,000 penalty against theScore for inadequate high-risk player identification, both reflect the AGCO’s expectation that operators self-identify and self-report material compliance gaps rather than waiting for regulatory inspection.

Structuring the Annual Calendar: A Worked Framework

The following framework assumes a December financial year-end for the licensee, which is a common scenario for operators holding all three licences. Compliance officers with a different year-end should shift the date-anchored items accordingly while retaining the structural logic.

Q1 (January to March): Year-End Convergence Window

January is the highest-risk month for multi-licence compliance teams. The UKGC Q4 regulatory return for a licence year ending 31 December falls due within 28 days of that quarter end, meaning no later than 28 January. Simultaneously, the MGA December player funds report is due by 20 January. If the licensee’s AML assurance submission to the UKGC is also due in Q1, compliance resources face genuine compression. Operators should assign Q1 a dedicated senior compliance resource review in December, not January, to ensure all data inputs are available when the submission windows open.

For MGA licensees, the January and February player funds reports (due 20 February and 20 March respectively) continue the monthly cycle through Q1. Any MGA AUP engagement that relates to the prior financial year should be initiated in Q1, well ahead of the 180-day audited accounts deadline.

Q2 (April to June): MGA Accounts and UKGC Mid-Year Return

For a December year-end, the MGA audited financial statements covering the prior year must be submitted by 28 June (180 days from 31 December). This is frequently the largest single-document compliance submission of the year. The auditor must be engaged early in Q1 to ensure the 180-day window is achievable in practice, particularly where the MGA requires engagement letters and no-conflict declarations before the audit scope can be formally scoped. The UKGC Q1 regulatory return (for the period ending 31 March) is due by 28 April.

Q3 (July to September): Management Accounts and Control Reviews

Under Article 41(1) of Directive 3 of 2018, the MGA management accounts covering H1 (January to June for a December year-end) must be submitted by 31 August. This submission must be signed by the key person responsible for the licensee’s finances. The UKGC Q2 regulatory return is due by 28 July. For AGCO, this quarter is an appropriate time to conduct the annual review of the Notification Obligations document against the operator’s corporate change register and to verify that the control activity matrix (required under Standard 1.02) is current and has been assessed by the independent oversight function.

Q4 (October to December): AML Reviews and Year-End Preparation

The UKGC Q3 regulatory return is due by 28 October. This quarter is also the natural time to complete internal AML framework reviews across all three jurisdictions in preparation for annual assurance submissions. AGCO’s outcomes-based model requires that responsible gambling policy reviews, supplier list reviews, and control environment assessments be completed and documented before year-end rather than in response to a regulatory request. For MGA licensees, October through December is the window in which to finalise the compliance contribution calculations and verify that all monthly player funds reports for the year have been submitted and reconciled against back-office records.

Enforcement Consequences of Missed Submissions

The MGA enforcement register makes the consequences explicit. In published cancellation decisions, the Authority has treated repeated failures to submit player fund reports and compliance contribution calculators as grounds for licence cancellation, not merely financial penalties. In one case, failure to submit player fund reports for a consecutive run of months from August 2019 through February 2020 was cited as a distinct breach alongside non-payment of licence fees. The enforcement outcome was cancellation of the B2C authorisation. In a separate case, the failure to submit the completed Compliance Contribution Calculator within the stipulated timeframe was itself characterised as a breach warranting cancellation-level consequences when combined with other defaults.

The UKGC has referenced inaccurate and late regulatory returns in formal regulatory settlements, including cases where the return failures were symptomatic of broader compliance dysfunction. The Commission’s position in its published policy materials is that regulatory returns are a primary supervisory tool: they enable the UKGC to detect emerging harm trends and to identify licensees whose operations have changed materially since their last licence variation. An inaccurate return is therefore treated not merely as an administrative error but as a potential indicator of a wider failure to cooperate with the Commission’s regulatory functions.

Practical Implementation: Calendar Ownership and Version Control

A compliance calendar is only as useful as its update process. Each of the three regulators reviewed here has updated its submission requirements, thresholds, or reporting formats within the last two years. The UKGC amended LCCP 15.2.1 to raise the shareholding notification threshold from three percent to five percent. The MGA moved to V2 of Directive 3 of 2018 in October 2021 and continues to develop its LRMS portal infrastructure for electronic submissions. The AGCO updated the Registrar’s Standards in May 2025 and revised its responsible gambling training standards in July 2025. A compliance calendar built on the 2022 version of any of these instruments and not reviewed since will contain errors.

In practice, operators should assign a named owner for each regulator-specific calendar section, require that owner to verify the primary source instrument at the start of each licence year, and run the calendar through a formal review whenever the regulator publishes updated guidance or consultation responses. The UKGC’s “We Asked, You Said, We Did” consultation response publications are a reliable indicator of imminent LCCP changes: they typically precede formal LCCP updates by two to six months and provide advance notice of amended deadlines or new requirements.

Version control for the calendar itself matters. Compliance teams that maintain the calendar as a shared spreadsheet without version numbering and named reviewers routinely discover, during regulatory inspections, that the document auditors are shown does not reflect the actual submission history. The calendar should be treated as a compliance record, not a planning tool, and retained accordingly.

Key Resources

UKGC Licence Conditions and Codes of Practice : gamblingcommission.gov.uk/licensees-and-businesses/lccp. The primary instrument for all UKGC recurring obligations. LC 15.3.1 (regulatory returns), LC 15.2.1 (key events), and LC 12.1.1 (AML) are the core provisions for calendar planning.

MGA Directive 3 of 2018 : Gaming Authorisations and Compliance Directive (V2, October 2021) : available via mga.org.mt regulatory framework page. Articles 39–41 govern the monthly player funds report, management accounts, and audited financial statements respectively.

MGA Compliance Audit Manual (MGA/G/001) : mga.org.mt. Provides auditor-facing verification checklists that are also useful for compliance teams preparing submissions: the manual’s management accounts and player funds sections reflect what the MGA expects to see when verifying timely compliance.

AGCO Registrar’s Standards for Internet Gaming (last updated May 2025) : agco.ca. Standards 1.02 and 1.13 are the primary notification and transparency obligations. The AGCO Notification Obligations document, referenced in the Standards, should be reviewed separately and calendared as a standalone annual update.

MGA Enforcement Register : mga.org.mt/licensee-register/enforcement-register. A primary-source record of enforcement decisions, including those citing specific reporting deadline failures. Reviewing recent decisions annually provides practical calibration of the MGA’s enforcement priorities.