# Exclusions vs obligations in Estonian insurance law URL: https://insurancelawestonia.ee/estonian-insurance-contract-law/exclusions-vs-obligations/ Author: Dr Olavi-Jüri Luik, Partner, Head of Insurance Law, attorney at law (Advokaadibüroo WIDEN OÜ) Last updated: 2026-11-09 > How Estonian courts distinguish a risk exclusion from a disguised obligation, why it matters under VÕS § 452 and § 42, and how to draft clauses that hold. Many coverage disputes in Estonia turn on one question: is the clause the insurer relies on a **risk exclusion** (*välistus*), which simply defines what is not covered, or an **obligation** of the policyholder (*kohustus*, in German terms an *Obliegenheit*) dressed up as an exclusion? The answer determines whether the mandatory fault and causation tests of § 452 lg 2 of the Law of Obligations Act (*võlaõigusseadus*, VÕS) apply, whether the clause is subject to the fairness review for standard terms, and who bears which burden of proof.[^1] The author has written about this distinction in Estonian and comparative literature; this page summarises the current state of the law.[^2] **Figure 1. Exclusion or safety requirement: classification and consequence** The scheme covers conditions that apply before the insured event. Premium, post-loss obligations (Law of Obligations Act (võlaõigusseadus, VÕS) § 452(2) points 3–4) and the exceptions in VÕS § 427 must be checked separately. - **K1** Has the term become part of the contract, and is it valid? Incorporation (VÕS § 37), interpretation (§ 39(1)) and fairness review (§ 42). - No → The term cannot be relied on - Yes → K2 - **K2** Does the term delimit the cover or regulate the policyholder's conduct? Assess the substance, not the heading. Where the occurrence of the condition depends mainly on the policyholder's conduct, the term is as a rule a duty of care, i.e. a safety requirement (Supreme Court 2-23-10549/35, para 11). - Delimits the cover (exclusion, definition of the insured event) → Exclusion - Regulates conduct → K3 - **K3** What kind of obligation is it? - Obligation to reduce the risk or prevent its increase (§ 452(2) point 2): fault is not required; the effect decides → K5 - Other obligation to be performed before the insured event (§ 452(2) point 1) → K4 - **K4** Was the breach due to the policyholder's fault? - No → The insurer is not released - Yes → K5 - **K5** Is the breach established, and did it affect the insured event or the loss? The insurer must prove the breach, its effect and the extent of the effect (Supreme Court 2-22-2313/65, para 17). A mere possible connection is not enough (Supreme Court 2-23-10549/35, para 13). - No effect → The insurer is not released - Effect → Release to the extent of the effect - Outcome: **The term cannot be relied on** (Statutory rule) The statute and the remaining terms of the contract apply. - Outcome: **Exclusion** (Depends on the policy) No cover to the extent of the exclusion, if its conditions are met. - Outcome: **The insurer is not released** (Statutory rule) The release clause cannot be relied on (VÕS § 452(2)). - Outcome: **Release to the extent of the effect** (Case law) As a rule, to the extent that the breach increased the probability of the insured event; in full only if the risk materialised solely because of the breach (Supreme Court 2-22-2313/65, para 17). Intentionally causing the insured event releases the insurer by law (VÕS § 452(1)). The scheme simplifies; the outcome depends on the policy and the facts. Legal basis: [VÕS §§ 37, 39, 42, 427, 445, 452](https://www.riigiteataja.ee/akt/120062026018); [Supreme Court Civil Chamber 28.06.2024, 2-22-2313/65, paras 13, 15–17](https://rikos.rik.ee/?asjaNr=2-22-2313/65); [Supreme Court Civil Chamber 25.03.2026, 2-23-10549/35, paras 11–13, 15](https://rikos.rik.ee/?asjaNr=2-23-10549/35). Statutory text checked against the version in force on 9 November 2026. ## 1. Why the classification matters | Question | Risk exclusion | Obligation (safety requirement, condition) | |---|---|---| | Effect | Absence of cover (*katte puudumine*): no insured event in the first place | Release from the performance obligation (*täitmiskohustusest vabanemine*) or reduction of the indemnity, only on the conditions of § 452 lg 2 | | Fault | Irrelevant | Relevant (§ 452 lg 2 p 1, 3, 4) | | Causation | Irrelevant (unless the exclusion itself requires it) | Required (§ 452 lg 2 p 1, 2, 4) | | Cancellation window | None | § 470: insurer must cancel within one month to keep the release | | Standard-terms review | Core definition of the insured risk exempt from fairness review (VÕS § 42 lg 2), but subject to transparency and interpretation rules | Fully reviewable; must not undermine § 452 | | Compulsory liability insurance | Injured party not protected by § 521 lg 5 | Injured party protected by § 521 lg 5 | The last row was confirmed by the Supreme Court in 2025: where intentional conduct is lawfully excluded from cover, there is no insured event, and the protective rule in favour of the injured party in compulsory liability insurance does not apply.[^3] The finding concerned the trustee's own intentional breach and the term of the compulsory policy applied in that case, which the insolvency legislation expressly allowed. ## 2. The test applied by the Supreme Court The Supreme Court requires courts to classify a clause before assessing its validity.[^4] In 2024 the Court formulated the criterion: as a rule, the distinction turns on whether the occurrence of the condition depends on the policyholder's fault and conduct, and where it is mainly influenced by the policyholder's conduct, the clause is as a rule a duty of care (an obligation) rather than an exclusion.[^5] The Court did not classify the clause in that case itself but remitted the case to the circuit court. The counterpart of the test is that a clause describing objectively, independently of the policyholder's conduct, a risk that the insurer does not cover is a genuine exclusion (analytical conclusion). In 2026 the Court applied the test and agreed with the circuit court that two maintenance-related casco conditions regulated the policyholder's duty of care, because their occurrence was influenced by the policyholder's conduct.[^7] The wording, the heading of the clause and its location in the policy (for example under "Exclusions") are not decisive. Examples: | Clause | Likely classification | |---|---| | "Damage caused by war, nuclear energy or terrorism is excluded" | Exclusion: describes an objective peril | | "Theft from a vehicle that was not locked is excluded" | Obligation: depends on the policyholder locking the vehicle | | "Loss caused while the alarm system was not switched on is not covered" | Obligation | | "Loss resulting from a payment made without a call-back verification is excluded" | Obligation | | "Damage to property caused by gradual deterioration, wear and tear is excluded" | Exclusion | | "Losses caused by a driver under the influence of alcohol are excluded" | Mixed: often treated as an obligation not to drive (or allow driving) under influence, but intentional or grossly negligent conduct issues arise | | "Cyber losses where the insured failed to install critical security patches within 30 days are excluded" | Obligation | ## 3. Hidden limitations and the standard-terms rules Even a genuine exclusion must pass the standard-terms rules of VÕS §§ 35–44. The Supreme Court has held that the statute presumes that the insurer covers all expenses arising from the insured event, so restrictions must be clear and unambiguous; hidden restrictions may be ineffective or reclassified; and unclear terms are interpreted against the insurer.[^6] A surprising clause that the policyholder could not reasonably expect does not become part of the contract at all (VÕS § 37 lg 3), and a clause that unreasonably disadvantages the policyholder, especially by deviating from an essential principle of the law, is void (§ 42 lg 1).[^1] The exemption for core terms in § 42 lg 2 protects only the clauses that define the main subject matter, and only if they are clear. It does not protect an obligation disguised as an exclusion, because such a clause deviates from § 452, which is itself an essential principle of insurance law. ## 4. Intent, gross negligence and the scope of cover A frequent source of confusion is the treatment of fault-based exclusions: - **Intent.** The insurer has no obligation to perform where the policyholder, the insured or the beneficiary intentionally caused the insured event; the Supreme Court described this as a general principle of insurance (§ 452 lg 1; § 513 in liability insurance).[^3] An express exclusion of intentional acts is a genuine exclusion. The 2025 judgment concerned a bankruptcy trustee's own intentional breach and the wording of the compulsory policy applied in that case; under other policies, and in particular under crime and fidelity cover, it must be established separately from the wording whose intentional act is the insured risk and whose is excluded. - **Gross negligence.** An agreement releasing the insurer for grossly negligent causation of the insured event is possible, but it operates within the limits of § 452 lg 2. The Supreme Court has indicated that the general provisions apply also to accident insurance concluded for the benefit of a third party.[^2a] - **Criminal acts.** Exclusions for "criminal acts" should be read narrowly and in the light of their purpose. ## 5. Drafting recommendations for foreign wordings 1. Keep a clear separation between the **insuring clause and exclusions** (objective perils, types of loss, property, activities) and the **conditions** (conduct of the insured). 2. Do not move conduct requirements into the exclusions section to avoid § 452. Estonian courts will reclassify them. 3. For conduct requirements, provide expressly for proportional reduction in line with § 452 lg 2 and the 2024–2026 case law. 4. Use clear, specific language; define technical terms (for example "critical patch" or "independent verification"). 5. Review "other insurance", "sanctions", "war" and "cyber operation" exclusions separately; they are usually genuine exclusions but raise questions under § 486 and transparency rules (see [war exclusions and cyber](https://insurancelawestonia.ee/guides/war-exclusions-and-cyber)). ## 6. Burden of proof The policyholder must prove that an insured event occurred. The insurer must prove the facts of an exclusion and of a breach of an obligation. For obligations, the policyholder must then prove absence of fault. The effect of the breach is treated differently: the Supreme Court has held that the insurer must prove whether, and to what extent, the breach affected the occurrence of the insured event, that is, the breach and its causal link to an increase in the insured risk, whether the insurer claims full release or a reduction. The Court has balanced this by placing on the policyholder a duty to cooperate in clarifying the facts; in the 2026 case this meant allowing an expert to dismantle the failed engine, because otherwise the insurer could not discharge its burden of proof.[^7] ## Related pages - [Safety obligations and proportionality](https://insurancelawestonia.ee/estonian-insurance-contract-law/safety-obligations-and-proportionality) - [Policy wording review](https://insurancelawestonia.ee/services-for-insurers/wording-review) - [Reviewing policy wordings under Estonian law](https://insurancelawestonia.ee/guides/policy-wording-review-estonian-law) - [Supreme Court: intent, exclusions and scope of cover](https://insurancelawestonia.ee/supreme-court/intent-exclusions-and-scope-of-cover) - [Supreme Court: standard terms](https://insurancelawestonia.ee/supreme-court/standard-terms) ## References [^1]: Law of Obligations Act (võlaõigusseadus, VÕS) §§ 35–44, 427, 452, 470, 513, 521. RT I, 20.06.2026, 18 (in force 01.09.2026). ; English: . [^2]: J. Lahe, O.-J. Luik. Kindlustusõigus. Tallinn: Juura 2018; O.-J. Luik. The application of principles of European insurance contract law to policyholders of the Baltic States. Tartu 2016. . [^2a]: RKTKo 27.06.2025, 2-19-14759/139, p 14.2. . [^3]: RKTKo 15.10.2025, 2-21-16822/84, p 13–15. . [^4]: RKTKo 23.12.2014, 3-2-1-136-14, p 13–14. . [^5]: RKTKo 28.06.2024, 2-22-2313/65, p 13, 15–17. . [^6]: RKTKo 06.02.2013, 3-2-1-178-12, p 16–18. . [^7]: RKTKo 25.03.2026, 2-23-10549/35, p 11–13, 15. .