Practical planning questions for work connected to Finland

Questions to resolve

• Which Finnish, Swedish, and English versions are required and who reviews each one.
• EUR display, VAT and invoicing inputs, payment providers, refunds, and reconciliation.
• GDPR, processors, data location, permissions, retention, deletion, security, and incident response.
• Accessibility, public-sector expectations, cookies, analytics, mobile use, and international users.

Language and localization

Define the language used for contracts, meetings, technical documentation, support, and user-facing content. Machine translation can assist drafting but should not be treated as certified or automatically publication-ready.

Privacy and data

Document what information is collected, why it is needed, who can access it, which vendors process it, where it may travel, how long it is retained, and how correction, export, deletion, and incidents are handled.

Payments and commerce

Define currency display, price ownership, approved tax and invoicing inputs, providers, settlement, refunds, subscriptions, disputes, reconciliation, failed states, and support.

Accessibility and usability

Set a target before design and testing. Include keyboard use, screen-reader structure, focus states, contrast, errors, labels, mobile interaction, and representative testing where appropriate.

• Open Statistics Finland
• Open NCSC-FI guidance
• Open the Ombudsman’s site
• Open the service-developer portal
• Open the Bank of Finland
• Open Finlex

Official sources

Use current official sources as research starting points. Recheck them for the actual service, audience, location, vendor, and launch date. Record who decides what applies.