Master Services Agreement in Finland: Template, Key Clauses and Local Law (2026)

A Master Services Agreement (MSA) in Finland is the framework contract between a service provider and a customer. It sets the terms that apply to all work, then lets each project run under a short Statement of Work (SOW) instead of a fresh negotiation every time. This guide covers the Finnish law that governs an MSA, the clauses to include, a skeleton you can adapt, and the common mistakes. This is general information, not legal advice. Finnish contract rules are partly uncodified and shaped by case law, so confirm the detail with a qualified Finnish lawyer before you sign. ## When you need an MSA in Finland Use an MSA when the relationship is ongoing: managed services, consulting, development, marketing, or any work that repeats. The MSA holds the stable terms (liability, IP, confidentiality, payment), and each SOW adds the scope, price, and timeline for one piece of work. One well-drafted MSA can carry years of projects. ## Finnish law that governs an MSA Finland follows freedom of contract, so the parties largely set their own terms. A few statutes sit behind the agreement and fill gaps. ### The Contracts Act (228/1929) The Contracts Act (Laki varallisuusoikeudellisista oikeustoimista, 228/1929) is the cornerstone of Finnish contract law. It governs how a contract is formed, when it is void, and how parties are represented. Section 36 is important: a Finnish court can adjust or set aside a term it finds unreasonable, weighing the content of the contract, the circumstances when it was signed, and later events. This limit applies even between businesses, so one-sided liability or penalty terms can be reopened. ### The Sale of Goods Act (355/1987) The Sale of Goods Act (Kauppalaki, 355/1987) sets default rights and duties for the sale of goods between businesses. Pure services sit outside it, but a mixed services-and-supply MSA may touch it, so define clearly what counts as a deliverable. ### Payment and interest The Act on Payment Terms in Commercial Contracts (30/2013) implements the EU Late Payment Directive. In business-to-business deals the default payment period is 30 days, and a period longer than 60 days is allowed only if expressly agreed and not grossly unfair to the creditor. The Interest Act (633/1982) sets statutory interest on late payment. ### Limitation of claims The Act on the Limitation of Debt (728/2003) sets a general limitation period of three years. Note any longer or shorter period you intend, because silence defaults to the statute. ## Key clauses to include - Structure and order of precedence. State that the MSA governs, each SOW adds project detail, and which document wins if they conflict.

• Services and SOWs. Describe how work is commissioned: no work starts without a signed SOW.
• Fees and payment. Rates, invoicing, the payment period (keep it inside the 30 or 60 day rule), expenses, and interest on late payment.
• Intellectual property. Say who owns deliverables and who keeps background IP. Finnish copyright passes to the author by default, so assign or license it expressly.
• Confidentiality and data protection. Mutual confidentiality, plus a data processing agreement where personal data is involved (see below).
• Warranties and service levels. What the provider promises, and remedies if it falls short.
• Limitation of liability. A cap and exclusion of indirect loss. Remember Section 36: an extreme exclusion can be adjusted, so keep it proportionate.
• Indemnities. Typically for IP infringement and breach of confidentiality.
• Term and termination. Duration, renewal, termination for cause and for convenience, and what happens to live SOWs.
• Governing law and disputes. Finnish law, and either the Finnish courts (often the District Court of Helsinki) or arbitration under the Finland Chamber of Commerce rules. ## A usable MSA skeleton 1. Parties and definitions

2. Structure and precedence (MSA, SOWs, order of priority)
3. Scope of services and the SOW process
4. Provider obligations and service levels
5. Customer obligations and dependencies
6. Fees, invoicing, and payment terms
7. Intellectual property and licences
8. Confidentiality
9. Data protection (reference the DPA)
10. Warranties and disclaimers
11. Limitation of liability
12. Indemnities
13. Term, renewal, and termination
14. Consequences of termination (transition, data return)
15. Governing law and dispute resolution
16. Signatures ## Common mistakes to avoid - No order of precedence. When an SOW and the MSA disagree, an unclear hierarchy invites a dispute.

• Forgetting the IP assignment. Under Finnish copyright, rights stay with the author unless transferred. Silence leaves the customer with no ownership.
• Overlong payment terms. A period beyond 60 days that is grossly unfair to the creditor can be challenged under the payment terms Act.
• Extreme liability caps. A near-total exclusion risks adjustment under Section 36 of the Contracts Act.
• No data processing terms. If the provider handles personal data, a bare confidentiality clause does not meet GDPR. ## One workspace for your Finnish contracts An MSA rarely travels alone: it spawns SOWs, order forms, and renewals, each with its own dates and obligations. Keeping the master terms, every SOW, and the deadlines in one place, instead of scattered folders and inboxes, is what stops things slipping. Adira is an AI legal workspace built for that: draft, review, track, and store related contracts together, with each clause modelled so edits stay consistent across documents. Adira is deepest in Indian law today, and wider jurisdiction depth, including the Nordics, is on its roadmap, so treat non-India output as a starting draft for local counsel to check. Get the local law right first, use a clean skeleton, and keep the paperwork in one trail. The tooling is the last step, not the first.