First-Year Corporate Compliance Calendar for a Lottery Operator
Create an entity-specific obligations register before trading. Work backwards from confirmed due dates and keep recurring duties, event-driven changes, approvals and filing evidence connected.
Build a lottery operator’s corporate compliance calendar immediately after incorporation and before transactions begin. Combine corporate filings, board actions, accounting close, tax coordination, licence reporting, insurance and contract renewals in one controlled obligations register. Give every item a source, due-date rule, preparer, approver, deputy and evidence location.
Inventory obligations separately for every entity and licence
Start with company-register records, constitutional documents, engagement letters, licence conditions, tax registrations and material contracts. Record the legal or contractual source and last-confirmed date. Incorporation dates, financial year-end, first reporting periods and licence dates may create different cycles; fixed dates copied from another business can be wrong.
Inventory annual returns, accounts, tax filings, licence reports and renewals, beneficial-ownership updates, board actions, registered-office charges, payroll, insurance, policy reviews and contract renewals where they apply. Include every company, licence and employing location. Ask a suitably qualified local adviser to resolve uncertain requirements before the date becomes operational.
Use the governance and UBO checklist to connect the register with the right directors, records and approval authority. The specialist-selection guide helps distinguish preparation, advice and filing responsibilities.
Build an obligations register, not just reminder dates
| Field | What to record | Why it matters |
|---|---|---|
| Entity and obligation | Exact company, licence, jurisdiction and period covered | Prevents a correct submission being attached to the wrong entity or cycle |
| Source and due-date rule | Confirmed legal or contractual basis, calculation method and confirmation date | Avoids copying unsupported universal dates |
| Preparation dependencies | Reconciliations, information requests, reviews and internal cut-offs | Makes work visible before the external deadline |
| People and approvals | Preparer, accountable reviewer, authorised approver, provider and deputy | Separates coordination from professional and director responsibilities |
| Status and escalation | Current stage, blockers, next action and escalation owner | Distinguishes a document request from a completed obligation |
| Completion evidence | Final submission, receipt, approval, acceptance where relevant and follow-up | Shows what was actually done and what remains open |
This is a planning template, not a list of filings every company must make. Attach provider cut-offs and required approvals to the relevant entries. Keep the source and evidence in a controlled repository rather than in one person’s private inbox.
Work backwards from submission and approval
A due date is the end of a process. If annual accounts depend on reconciled ledgers, director review and external filing, place each predecessor task in the calendar with an internal cut-off based on the actual process. “Annual” work may need preparation well before the anniversary.
Use distinct statuses: not started, in preparation, awaiting third party, approved, submitted and accepted where the process includes acceptance. Documents sent to a provider are not proof that the correct entity and period were filed. Confirm the submission, save the receipt and record any condition or follow-up request before closing the item.
Payment and financial reporting dependencies should agree with the payment-stack workstream. Unreconciled bank or PSP records can delay several obligations at once.
Add event-driven duties alongside recurring cycles
Maintain a second layer for changes that do not wait for an anniversary: new directors or beneficial owners, address changes, new domains, material outsourcing, incidents, policy breaches, capital transactions and market entry. Not every event creates the same duty in every jurisdiction. Define who reports it internally, who assesses the applicable consequences and who authorises any notification.
As an internal operating recommendation, review the forward calendar at least monthly in the first year and more frequently around launch or renewal. This is not a universal statutory meeting frequency. Escalate missing evidence before the external deadline and preserve the reasons for delays. The calendar owner coordinates; directors and regulated professionals retain their respective responsibilities.
Use the launch partner map to keep external providers accountable for deliverables and align launch-related predecessor tasks with the pre-go-live checklist.
Scenario: first accounts and licence renewal overlap
Suppose accounting records are incomplete when a renewal pack needs current financial information and corporate confirmations. Open one dependency plan covering bookkeeping corrections, bank and PSP reconciliations, director approval, adviser questions and the renewal submission. Treat the requests as linked work, not separate administrative emails.
Identify which information is final, which is provisional and whether the relevant authority or provider needs to be contacted. Save decisions and receipts in both obligation files. Afterwards, adjust monthly closing dates and evidence ownership so the collision becomes visible earlier next time.
Make the calendar survive a handover
Each item needs a deputy, source link and short operating note describing the next action. Before a high-risk deadline, confirm that another authorised person can locate the evidence, explain the status and perform that action. A departure or provider change should not erase the method.
Review the calendar after jurisdiction, ownership, activity or business-model changes. Keep earlier sources and completion evidence under the appropriate retention and access rules so the company can explain which requirement was used at the time.
Practical checklist
- Confirm financial year-end and the first reporting periods.
- List recurring and event-driven duties for each entity, licence and employing location.
- Record confirmed sources, due-date rules and last-confirmed dates.
- Add accounting, tax, licence, insurance and contract dependencies where applicable.
- Assign a preparer, approver, reviewer and deputy to every item.
- Use status labels that separate preparation, submission and completion evidence.
- Review upcoming work, escalate missing evidence and retain receipts.
- Make handover instructions accessible to authorised replacements.
Frequently asked questions
Can one generic calendar be used for all group companies?
Use one coordinated register if helpful, but validate duties and dates for each entity and activity. Financial years, licence periods and event triggers may differ.
When is a calendar item complete?
When the required action and appropriate completion evidence have been confirmed. Sending papers to an adviser is only a process stage, not necessarily a completed filing.
Who owns the calendar if an external accountant handles filings?
Name an internal coordinator and accountable approvers. The accountant owns its agreed professional scope, while company directors and other responsible parties retain their duties.
Primary-source context and limits
The G20/OECD Principles of Corporate Governance 2023 provide broad governance context. The IFRS Foundation’s Standards Navigator is a source of accounting standards and related materials, not a filing calendar. Neither determines which reporting framework or deadline applies to a particular lottery company.
Duties and dates depend on the actual entity, jurisdiction, activity and current rules or contracts. The register does not establish compliance or supply country-specific tax or filing instructions.
Connect corporate dates with platform dependencies
Bring the launch calendar, technical evidence requests and assigned owners to WhiteLotto’s team for a discussion of platform scope and dependencies. Statutory filings, accounting, tax advice and regulatory decisions remain separate workstreams.