Concept card

Indemnification Clause

As of 2026-07-24T14:00:00Z

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Indemnification Clause?

Indemnification obligations are usually carved OUT of the liability cap entirely — the single most dangerous interaction in B2B service contracts.

An indemnification clause obligates one party to defend and financially make whole the other against specified claims brought by a third party — someone outside the contract altogether. It is distinct from a straightforward damages clause because it covers the cost of defending a lawsuit brought by an outsider, not just compensating the other contracting party's own loss. In SAP analytics engagements the consultant typically indemnifies the client for intellectual-property infringement in the deliverables, data-protection breaches caused by the consultant's own negligence, and misconduct by the consultant's subcontractors; the client typically indemnifies the consultant for claims arising from client-supplied data, systems, or explicit direction the consultant warned against. Without careful drafting this symmetry breaks down fast, and it usually breaks in the client's favour, because the client's legal team drafts first.

The critical interaction with the liability cap

The single most dangerous pattern in SAP consulting contracts is a well-negotiated liability cap sitting next to an indemnification clause that is carved out of it. A consultant who fights hard for a two-hundred-thousand-euro aggregate cap and then signs a broad indemnification obligation covering any third-party intellectual-property claim has not actually limited exposure at all — the indemnification clause reopens the door the cap just closed. The working discipline is to treat every indemnification clause as if it were uncapped, because in the overwhelming majority of contracts it is, and to negotiate its scope with the same rigour normally reserved for the cap itself.

The five SAP-analytics-specific scenarios worth naming explicitly

Why it matters

A consultant can negotiate a €200k liability cap, then accept a broad IP-infringement indemnification clause that bypasses it completely, exposing millions in defence costs alone.
The asymmetry runs both ways by default — consultants often indemnify broadly (IP, data breach, subcontractor conduct) while clients indemnify only narrowly.
Five SAP-analytics-specific scenarios recur: OSS licence violation, unlicensed SAP partner code, DAC misconfiguration leaking PII, subcontractor breach, worker-misclassification claims.

Key points

Indemnification = obligation to defend + reimburse third-party claims.
Usually CARVED OUT of liability cap — if uncapped, consultant's cap is fiction.
Five SAP scenarios: OSS license · third-party SAP IP · data-breach · sub-contractor · worker-classification (refuse).
Four elements: trigger · defence-control · notice · cap.
Standard ask: sub-cap = 1-2× annual fees, indirect damages excluded.
Defence control to indemnifier (cost-aligned).
Mutuality: client indemnifies for client-side risks (data, direction, IP failures).
Worker-classification indemnification: always refuse (out-of-scope, tax-authority risk).
Indemnification Clause is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.

Terms used on this page

Indemnification: Obligation of one party (indemnifier) to defend and reimburse the other (indemnitee) against specified third-party claims.
Carve-out from liability cap: Indemnification obligations excluded from the C062 cap, exposing indemnifier to unlimited liability without separate sub-cap.
Sub-cap: Lower-tier cap applied to indemnification (e.g., 1-2× annual fees). Without it, indemnification bypasses liability cap entirely.
Defence control: Right to select counsel and direct litigation strategy. Should sit with the party paying the costs (indemnifier).
Notice window: 5-15 day period from awareness within which indemnitee must notify indemnifier. Missing typically voids indemnification.
Trigger scope: What events activate indemnification obligation. 'Negligent acts or wilful breach' is narrow; 'any claim arising from' is anti-pattern.
Worker-classification indemnification: Tax-recharacterisation indemnification (e.g., URSSAF / IR35 recovery). Should always be refused as out-of-scope risk for consultant.
Mutuality: Symmetric indemnification: client indemnifies consultant for client-side risks (data provided, direction given, IP failures).

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →