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

A master services agreement (MSA) is a framework contract. It sets the terms that govern an ongoing supplier relationship once, so each new piece of work can be ordered through a short statement of work (SOW) instead of a fresh negotiation. The MSA holds the legal terms that rarely change, such as payment, liability, intellectual property, confidentiality and termination, while each SOW holds the commercial detail of a specific engagement: scope, deliverables, timeline and price. In Austria there is no single statute you fill in to create a valid MSA. It is built from the general civil law in the Allgemeines Buergerliches Gesetzbuch (ABGB), the commercial rules in the Unternehmensgesetzbuch (UGB) where both parties are businesses, and, where personal data or consumers are involved, data protection and consumer law. This guide sets out the local law that actually bites, the clauses an Austria MSA should contain, and a section-by-section skeleton you can adapt. It is general information, not legal advice; confirm the detail with qualified Austrian counsel before you sign. ## Austria: the local law that shapes your MSA Austrian contract law rests on freedom of contract under the ABGB, so the parties are largely free to agree their own terms. Two background distinctions still matter. First, the ABGB separates the service contract (Dienstvertrag, where the supplier owes its work over a period) from the works contract (Werkvertrag, under Paragraph 1165 and following, where a defined result is owed, with rules on acceptance and warranty for defects). An MSA is usually a services framework, but a SOW that commits you to a fixed deliverable can pull in Werkvertrag rules, so name the standard you are promising in each SOW. Courts look at what the parties actually agreed and did, not the label they used. Second, standard business terms (Allgemeine Geschaeftsbedingungen, AGB) are controlled. Where terms are pre-drafted and not individually negotiated, the ABGB allows a court to strike a clause that is grossly disadvantageous and surprising or that offends good faith (the Paragraph 879(3) content control and the Paragraph 864a rule on unusual clauses). A sweeping liability exclusion buried in standard terms is exactly what those rules target. ### When consumers or personal data are involved If the customer is a consumer, the Konsumentenschutzgesetz (KSchG) adds mandatory protections that cannot be contracted away. Where the MSA involves processing personal data on the other party's behalf, the EU General Data Protection Regulation (GDPR) and Austria's Datenschutzgesetz (DSG) require a separate written data processing agreement with the content in Article 28 GDPR, overseen by the national authority, the Datenschutzbehoerde (DSB). Reference that DPA from the MSA rather than burying data terms in the main body. ## The clauses an Austria MSA should contain A workable MSA keeps the stable legal terms in the master and pushes the deal-specific detail to the SOW. The core clauses are: - Structure and order of precedence. State that the MSA governs, that each SOW incorporates it, and which document wins if they conflict.

• Services and SOWs. How a SOW is raised, agreed and changed, what it must contain, and that no work is authorised without one.
• Charges and payment. Fees, rate cards, expenses, invoicing cycle, payment period, interest on late payment, and taxes (USt/VAT).
• Change control. A written process for changing scope, price or timeline.
• Intellectual property. Who owns pre-existing IP, who owns deliverables, and the licence each side grants.
• Confidentiality. Mutual confidentiality, permitted disclosures, and survival after termination.
• Data protection. A cross-reference to a GDPR Article 28 data processing agreement where the supplier processes personal data for the customer.
• Warranties and service levels. The standard of performance, any service levels or acceptance criteria, and the remedy if they are missed. Note the ABGB warranty rules (Gewaehrleistung) for defects.
• Liability. Caps and exclusions, with carve-outs for what mandatory law protects and bearing in mind AGB content control.
• Term and termination. Duration, renewal, termination for cause, for insolvency and for convenience, and what happens to live SOWs when the MSA ends.
• Exit and transition. Return or deletion of data and materials, handover assistance, and survival of key clauses.
• Governing law and disputes. Austrian law, the competent court or an arbitration seat, and the contract language. ## A master services agreement skeleton you can adapt Use this running order as a drafting checklist. It is a skeleton, not a finished contract, and it is not legal advice. 1. Parties and recitals

2. Definitions and interpretation
3. Structure, SOWs and order of precedence
4. Supplier obligations and standard of performance
5. Customer obligations and dependencies
6. Change control
7. Charges, invoicing, payment and taxes
8. Intellectual property and licences
9. Confidentiality
10. Data protection (cross-reference to the DPA)
11. Warranties, defect liability and service levels
12. Limitation of liability
13. Term, renewal and termination
14. Consequences of termination and transition assistance
15. Governing law, jurisdiction or arbitration, and language
16. Boilerplate (assignment, subcontracting, force majeure, notices, entire agreement) ## Common mistakes to avoid - Putting scope in the MSA. The master should carry legal terms; project detail belongs in the SOW. Mixing them makes both hard to change.

• A broad exclusion that will not survive AGB control. In standard terms, a grossly disadvantageous or surprising clause can be struck under the ABGB. Build a defensible cap, not an absolute one.
• No order of precedence. When a SOW silently contradicts the MSA, disputes follow. Say which wins.
• Treating data terms as boilerplate. Where personal data is processed, GDPR Article 28 content is mandatory.
• Ignoring the Dienstvertrag versus Werkvertrag line. A SOW that promises a fixed result can trigger Werkvertrag rules on acceptance and warranty. Be deliberate about what you are promising. ## Keeping the agreement alive after signing The work does not stop at signature. An MSA spins off SOWs, change orders, renewal dates and service levels, each with its own version and its own deadline. Most disputes come not from a badly drafted master but from a SOW that drifted out of scope, a renewal that auto-extended unnoticed, or a change agreed by email and never recorded. That is the case for keeping drafting, review, version history and obligation tracking in one place rather than spread across inboxes, a shared drive and a spreadsheet. Adira is one such AI workspace: you draft from your own templates, see each clause flagged as favourable, neutral or unfavourable to you, edit clauses in plain English, and keep a live timeline of every SOW, change order, renewal and obligation, built on Anthropic's Claude. Adira is India-first today; deeper support for Austrian law is on its roadmap rather than live, so treat it as a workflow layer here and keep local counsel for the legal substance.