Finland's 2027 gambling licence: separate the application from launch

Resolve the software-date conflict against the enacted law

The Police overview gives July 2027 for software-licence applications and July 2028 for the requirement. At our 30 October check, the English application FAQ also contained a software-specific answer giving January 2027 and January 2028. Those dates conflict. Retain the guidance as a dated observation, then check the controlling text.

We checked the consolidated Finnish text of the Gambling Act 10/2026, section 106 on 31 October 2026. It applies the listed software-licensing provisions from 1 July 2027. It separately applies section 2(2) and section 33 to software licences from 1 July 2028. Those are the statutory dates used in this guide; the January wording in the FAQ is not used to set a deadline.

The record distinguishes what the enacted provision says from how it applies to a particular supplier, product or workflow. Recheck amendments and current authority instructions before acting. The Finlex page also links an English translation completed on 22 October 2026; the authoritative Finnish and Swedish texts remain the reference.

A useful evidence register records the conflict, the controlling section, the date checked and any question about your actual activity that still needs an answer. This guide has not obtained a written authority determination for an individual supplier.

Four checkpoints before an operator launch

An application receipt establishes filing, not approval. An approval needs to be read with its conditions and effective date. The Police's licence-holder obligations separately describe audits and connection to supervisory systems. A commercial launch plan needs evidence for each checkpoint.

• Product scope: record which entity, games and operating model the application covers, and which permission each requires.
• Decision: retain the actual licence decision and conditions, rather than a filing receipt or press statement.
• Validity: verify the licence's effective date and any later restriction or change.
• Readiness: map required audits, technical connections, player-protection procedures and other applicable obligations to evidence and an accountable owner. Have qualified advisers verify the requirements for the actual operation.

Keep application costs separate from an all-in budget

A government application fee is only one cost category. A useful planning budget also separates legal and compliance work, technical integration, testing, audits, staffing, taxes and recurring supervision costs where applicable. This guide does not quote an all-in licence price or guarantee a processing time.

Ask what each quoted figure covers, which year it applies to, whether it is payable if the application is refused, and whether it changes with product scope. Save the current official fee schedule with the estimate. A schedule should include dependencies and uncertainty rather than treating a target processing period as a promised decision date.

Use a question-led evidence register

Start with the decision you need to make: whether to file, how to sequence a supplier integration, or which claim can be made publicly. For each material statement, retain the source title, link, publication or revision date, time checked, jurisdiction, entity, product scope and any conflicting evidence.

The blank country-evidence CSV below includes a place for unresolved questions. A completed research brief should state its cutoff and distinguish official records from interpretation. It does not replace legal advice, a licence application service or a regulator's determination. The Estonia licence-check guide shows a different jurisdiction's public-record workflow; its categories do not transfer automatically to Finland.