Entire Agreement Clauses in India: What They Switch Off

An entire agreement clause (also called a merger clause or integration clause) says the signed document is the whole deal. Everything said before signing, the sales call, the pitch deck, the term sheet, the reassuring email from the account manager, stops mattering once the contract is signed, unless it was also written into the contract itself. The one thing most people get wrong: they assume this clause also wipes out any claim for being lied to before signing. It does not, not automatically. Cutting off a misrepresentation claim needs a separate, express non-reliance clause, and even that cannot protect a party against its own fraud. This guide (published by Adira, which makes contract review and CLM software, so we have a commercial stake in you understanding contracts well, but this explainer stands on its own) walks through what the clause actually switches off, what Indian evidence law says about it, and what to check before you sign.

Plain meaning

Strip away the legal language and an entire agreement clause says: "Forget everything we discussed before this. Only what is written in this document, and documents it expressly says are part of it, counts." It does two things. First, it tells a court that the written contract is the primary, usually the only, source of what the parties agreed, so pre-contract emails, drafts, and verbal promises should not be used to add extra terms that are not in the final text. Second, it usually supersedes earlier written agreements on the same subject, a term sheet, a letter of intent, an earlier draft MoU, so those stop having independent legal force once the final contract is signed.

This is closely tied to how Indian evidence law treats written contracts. Once a transaction is reduced to a document, the document becomes the primary proof of what was agreed, and oral evidence generally cannot contradict, add to, or subtract from its written terms. An entire agreement clause is, in effect, the parties writing that evidentiary rule into their own contract in plain words, so there is no argument later about whether the document was meant to be complete.

Who it protects and what triggers it

An entire agreement clause protects whichever party benefits from the final written terms being the only terms that count, usually the party that drafted the contract, most often the vendor or service provider in a commercial deal. It is triggered the moment a dispute turns on something said or promised before signing that is not in the final document: a sales rep who promised a feature that never made it into the statement of work, a term sheet clause quietly dropped from the final agreement, an email confirming a discount that never appeared in the order form.

The clause does not care whether the earlier statement was made in good faith or was a deliberate exaggeration. It applies mechanically: if it is not in the document, or in something it expressly incorporates, it is treated as never agreed. This is why it needs careful reading before signing, not after a dispute starts. Once signed, "but they told me on the call that..." is a much harder argument to win, and the clause is written specifically to make it harder.

What to look for

Four mechanics decide how much an entire agreement clause actually locks in, and none are visible if you only skim the standard paragraph:

1. Does it name what "prevails"? Deals often run on a stack of documents, an MSA, a Statement of Work, an Order Form, technical annexures. If the clause does not say which document wins in a conflict, or worse, silently overrides an SOW that both sides understood would control commercial terms, you get a real fight later about which document is "the agreement."
2. Is there a non-reliance carve-out, and how wide is it? A clause that simply says "this is the entire agreement" is different from one that adds "and each party confirms it has not relied on any representation not set out in this Agreement." The second version is a non-reliance clause, and it is what actually narrows a future misrepresentation claim.
3. Is fraud carved out of the non-reliance language? Under Indian law you cannot contract out of liability for your own fraud. A non-reliance clause that tries to exclude all liability, including for dishonest statements, with no carve-out, is on shaky ground and a warning sign about the rest of the drafting.
4. What does it do to side documents you want to survive? A data processing addendum, a security annexure, a confidentiality undertaking signed separately, an entire agreement clause can accidentally supersede these unless it expressly says they remain in force.

The Indian position: Sections 91 and 92, Indian Evidence Act (now Sections 94-95, Bharatiya Sakshya Adhiniyam)

The Indian Evidence Act, 1872 governed this question for most of the life of Indian contract law, and the rule has now been carried forward, in near identical language, into Sections 94 and 95 of the Bharatiya Sakshya Adhiniyam, 2023, which replaced the Evidence Act for court proceedings from 1 July 2024 onward. The substance has not changed. Section 91 set out the "best evidence" rule for written contracts:

"When the terms of a contract, or of a grant, or of any other disposition of property, have been reduced to the form of a document... no evidence shall be given in proof of the terms of such contract, grant or other disposition of property... except the document itself, or secondary evidence of its contents in cases in which secondary evidence is admissible." Source: Section 91, Indian Evidence Act, 1872

Section 92 goes further, this is the actual parol evidence rule that an entire agreement clause leans on:

"When the terms of any such contract, grant or other disposition of property, or any matter required by law to be reduced to the form of a document, have been proved according to the last section, no evidence of any oral agreement or statement shall be admitted, as between the parties to any such instrument or their representatives in interest, for the purpose of contradicting, varying, adding to or subtracting from, its terms." Source: Section 92, Indian Evidence Act, 1872

Two things matter here. First, once you have proved the document, Section 92 stops you using oral evidence to change what it says. Second, Section 92 carries a set of provisos, the most important for contract disputes being proviso 1, which allows oral evidence to prove facts that would invalidate the document altogether, fraud, want of consideration, illegality, mistake. This is the statutory root of why an entire agreement clause cannot shield fraud: the law that gives the clause its teeth carries its own fraud exception built in.

A named Indian case: Mangala Waman Karandikar v Prakash Damodar Ranade

In Mangala Waman Karandikar (D) Tr. Lrs. v Prakash Damodar Ranade (Supreme Court of India, 2021 INSC 288, decided 7 May 2021, Civil Appeal No. 10827 of 2010), a three-judge bench dealt with a party trying to lead oral evidence to explain the terms of a written document, arguing the provisos to Section 92 should let in evidence about what was really agreed. The Court held that the provisos to Sections 92 and 95 of the Evidence Act apply only where the language of the document itself leaves the question genuinely doubtful, not simply because one party now wishes the terms had been different. Where the terms are clear and unambiguous on their face, oral evidence cannot be brought in to contradict or vary them. See the full judgment on Indian Kanoon.

Why this matters for an entire agreement clause: it confirms Indian courts read a clear, unambiguous written contract as controlling, and will not casually let a party reopen it with "but we discussed something different." That is good news if you are relying on the deal as signed, and bad news if you are hoping to point to a verbal promise that never made it into the document, unless you can bring the dispute within a Section 92 proviso, most realistically fraud.

Red flags

Normal	Red flag	Why it matters
States clearly which document prevails in a conflict (usually the Order Form or SOW on commercial terms)	Silent on precedence, or overrides an SOW that was supposed to control	The document everyone thought would govern, discounts, deliverables, timelines, can be silently displaced
Paired with an express, specifically worded non-reliance clause	Only a bare "this is the entire agreement" statement	Without non-reliance wording, a misrepresentation claim is not automatically excluded
Non-reliance language expressly carves out fraud and fraudulent misrepresentation	Tries to exclude liability for fraud too, with no carve-out	Unenforceable against fraud under Indian law, and a sign the rest of the drafting was careless
Side documents meant to survive (DPA, security addendum, confidentiality undertaking) are expressly listed as surviving	Silently supersedes a separately signed DPA or security annexure	A compliance-critical document can vanish without anyone noticing until an audit or a breach
Features, SLAs, and commitments discussed in sales calls are reflected in the written contract	Promised features are missing from the contract, and the clause locks that gap in	Becomes the tool that erases a verbal promise the vendor does not want to keep
One clause in the main body, cross-referenced consistently across annexures	Multiple, inconsistent entire agreement clauses across the MSA, order form, and annexures	Creates a dispute over which clause controls and whether earlier documents still apply
Applies equally to statements made by both sides	Protects only the drafting party's pre-contract statements, silent on the other side's	One-sided protection despite being framed as a neutral, standard clause

Bad clause → better clause

Bad: "This Agreement constitutes the entire agreement between the parties and supersedes all prior agreements, representations, and understandings, whether written or oral, relating to its subject matter."

What is wrong: no statement of which document prevails if the Order Form or SOW conflicts, no non-reliance language, and it risks accidentally superseding side documents like a DPA that both parties want to survive.

Better: "This Agreement, together with any Order Form, Statement of Work, and annexure expressly referenced in it, constitutes the entire agreement between the parties relating to its subject matter, and supersedes all prior agreements, negotiations, and discussions, whether written or oral, other than the Data Processing Addendum and Confidentiality Undertaking executed separately, which remain in full force. If this Agreement conflicts with an Order Form on commercial terms, the Order Form prevails. Each party confirms it has not relied on any representation, warranty, or undertaking other than as expressly set out in this Agreement, except that nothing in this clause limits or excludes either party's liability for fraud or fraudulent misrepresentation."

What changed and why: it now names which document controls a conflict, expressly preserves the side documents meant to survive, adds real non-reliance language, and carves out fraud so it is not trying to do something Indian law will not permit.

How it interacts with related clauses

An entire agreement clause rarely stands alone. Three clauses decide how much it actually bites:

• Representations and warranties. If a specific promise matters to you, get it written as a warranty in the contract. Anything left out of the written warranties is presumed not to be part of the deal.
• Order of precedence. When a deal runs on an MSA plus an SOW plus annexures, the entire agreement clause and the precedence clause need to say the same thing. A common, costly error is an entire agreement clause that contradicts a "this SOW prevails" line buried in the SOW itself.
• Indemnity and limitation of liability. If a non-reliance clause successfully narrows a misrepresentation claim, that claim often has to be pursued, if at all, through the ordinary breach and indemnity mechanics instead. Read all three together, not in isolation.

You can mark up how these clauses sit against each other directly in a document, for free, using Weave, which lets you flag and comment on clauses before you send a contract back for negotiation.

US and global contrast

US contracts use merger clauses similarly, and US courts also generally hold parties to a signed, unambiguous agreement. The bigger difference is around fraud carve-outs. US case law, especially in Delaware, has developed a demanding standard: a general non-reliance clause is often not enough to bar a fraud claim, courts want language specifically disclaiming reliance on the particular categories of statements at issue, not just boilerplate. Indian law reaches a similar result through a different route, the fraud proviso is built directly into Section 92 (now Section 95 of the Bharatiya Sakshya Adhiniyam) itself, rather than a separate body of case law about how specific a disclaimer must be. Either way, the lesson is the same: do not assume a generic entire agreement clause quietly excludes a fraud claim, in neither system does it.

FAQ

Does an entire agreement clause protect a vendor from a promise made on a sales call? Generally, yes, in the sense that a promise not in the written contract becomes very hard to enforce once the clause and Section 92 (Section 95 of the Bharatiya Sakshya Adhiniyam) are read together. This is why any feature, SLA, or commitment you were promised verbally needs to be written into the contract before you sign, not left to trust.

Can oral promises ever override a written contract in India? Rarely, and only within the Section 92 provisos, most importantly where the oral evidence would show the contract is void or voidable, for reasons like fraud, mistake, or illegality. A clear, unambiguous written contract otherwise controls, as the Supreme Court confirmed in Mangala Waman Karandikar v Prakash Damodar Ranade.

What is a non-reliance clause and how is it different from an entire agreement clause? An entire agreement clause says the document is the complete agreement. A non-reliance clause is a separate statement where each party confirms it has not relied on any representation outside the written contract. Only the non-reliance language does real work in narrowing a future misrepresentation claim.

My Statement of Work says it "prevails," but the main agreement has an entire agreement clause. Which wins? It depends entirely on how both clauses are drafted, and inconsistent drafting here is common. The safest fix is to make the entire agreement clause and the precedence clause say the same thing explicitly, rather than leaving a court to work it out.

Can an entire agreement clause exclude liability for fraud? No. Under Indian law, and reflected directly in proviso 1 to Section 92 (carried into Section 95 of the Bharatiya Sakshya Adhiniyam), a party cannot use a contract clause to exclude liability for its own fraud. A non-reliance clause that tries to do this anyway is a red flag about the drafting generally.

Does Section 92 apply if my contract was never fully reduced to writing, say if key terms were only exchanged by email? Sections 91 and 92 apply once a transaction has, in fact, been reduced to a document. If your "contract" is a scattered set of emails and no single signed document covers the terms in dispute, the analysis is messier, which is itself a reason to get a proper written agreement in place.

This guide gets you to understanding what an entire agreement clause does under Indian law and what to check before you sign. It does not tell you whether a specific clause in your contract excludes a claim you may have, that depends on the exact wording and the facts of what was said before signing, and is not legal advice. Talk to a lawyer before you rely on, or sign away, a claim based on a pre-contract promise.