Acceptance and Deemed-Acceptance Clauses: When Work Is Treated as Approved

An acceptance clause tells you the exact moment a delivery, a batch of goods, or a piece of software stops being "work in progress" and becomes something the buyer has approved. That moment matters: it usually triggers the payment milestone and starts the warranty clock, and it can shut the door on your right to complain about defects. The one thing most people get wrong is treating "acceptance" as a formality that happens automatically on delivery. It does not. Under Indian law, acceptance is a specific legal event with its own triggers, and a "deemed acceptance" clause with a short, unrealistic window can waive a genuine defect claim before you have even noticed it. Adira, which publishes this guide, makes contract review and CLM software, so we have a commercial reason to want you to read contracts carefully; the explanation below stands on its own regardless of what tools you use to do that.

Plain meaning

An acceptance clause sets out how and when a buyer confirms that what was delivered, goods, a software build, a report, a construction milestone, meets the contract. It does three jobs: it defines the test (what the buyer checks, against what standard: a specification, agreed acceptance criteria, a set of test cases); it defines the process (how long the buyer gets to test, and whether the seller gets a chance to fix a defect before the buyer can reject outright); and it defines what happens if the buyer does nothing. Most acceptance clauses include a "deemed acceptance" trigger: if the buyer does not reject within a stated window, the delivery is treated as accepted whether or not anyone actually reviewed it.

That third piece is where the clause turns from housekeeping into a risk-allocation tool. A short deemed-acceptance window shifts the burden of vigilance onto the buyer and lets the seller walk away from liability for defects nobody had time to find.

Who it protects and what triggers it

An acceptance clause protects both sides. It gives the seller finality, so the buyer cannot later claim the whole delivery was defective from day one. It protects the buyer with a defined window and standard to test against, instead of taking delivery on faith.

The trigger is almost always one of three things: the buyer actively confirms acceptance, the buyer does something with the goods that only makes sense if accepted (installing equipment, deploying software to production), or the buyer lets a stated period pass without objecting. Only the first is a conscious choice; the other two can catch a buyer who was simply slow or understaffed.

What to look for

Four mechanics decide whether an acceptance clause is fair or quietly loaded against the buyer.

1. Who sets the acceptance criteria, and how specific they are. "Conforms to the Specification in Schedule 2" is testable; "is satisfactory to Buyer" is not, and usually favours whoever controls the test.
2. The review window, matched to what is realistically being reviewed. Ten days is fine for standard parts checked against a packing list; it is not enough for a proper user acceptance test on an ERP module.
3. What happens after a rejection. A defined cure period and re-test right, or does one failed test end things? A one-shot test with no cure right is harsh for anything beyond simple goods.
4. What counts as "use." Does any use, including a pilot, count as full acceptance of everything delivered? That one sentence can turn a cautious trial into a waiver of your right to reject the rest.

The Indian position: acceptance is a defined legal event, not a formality

For contracts involving the sale of goods, Indian law does not leave "acceptance" to convention. The Sale of Goods Act, 1930 sets out, in three connected sections, exactly when a buyer is deemed to have accepted goods, starting with the right to examine what was delivered.

Section 41 gives the buyer that right of examination before acceptance can be deemed to have happened at all:

"(1) Where goods are delivered to the buyer which he has not previously examined, he is not deemed to have accepted them unless and until he has had a reasonable opportunity of examining them for the purpose of ascertaining whether they are in conformity with the contract. (2) Unless otherwise agreed, when the seller tenders delivery of goods to the buyer, he is bound, on request, to afford the buyer a reasonable opportunity of examining the goods for the purpose of ascertaining whether they are in conformity with the contract." Source: Section 41, The Sale of Goods Act, 1930 (Indian Kanoon)

Section 42 is the operative deemed-acceptance provision, with three separate routes, only one of which is a conscious statement:

"The buyer is deemed to have accepted the goods when he intimates to the seller that he has accepted them, or when the goods have been delivered to him and he does any act in relation to them which is inconsistent with the ownership of the seller, or when, after the lapse of a reasonable time, he retains the goods without intimating to the seller that he has rejected them." Source: Section 42, The Sale of Goods Act, 1930 (Indian Kanoon)

Notice Section 42 does not name a fixed number of days; it uses "a reasonable time," which a court works out from the facts. A contractual acceptance clause is the parties agreeing in advance what "reasonable" means for this deal, which is why a very short window is risky: it may bind you even where a court left to decide on its own might have given you longer.

Section 43 protects a buyer who does validly reject:

"Unless otherwise agreed, where goods are delivered to the buyer and he refuses to accept them, having the right so to do, he is not bound to return them to the seller, but it is sufficient if he intimates to the seller that he refuses to accept them." Source: Section 43, The Sale of Goods Act, 1930 (Indian Kanoon)

One honest limit: the Sale of Goods Act, 1930 governs the sale of goods. A pure services contract, a software build with no goods component, is not directly covered. Courts often reason by analogy from Section 42 even in services deals, but acceptance mechanics in a pure services agreement are mainly a creature of what the contract says, under the freedom of contract recognised by the Indian Contract Act, 1872. That makes careful drafting more important in a services deal, not less, since no statutory floor does the work for you the way Section 41 does for goods.

A named case: Godrej and Boyce Mfg Co Ltd v Remi Sales and Engineering Ltd

Godrej and Boyce Mfg Co Ltd v Remi Sales and Engineering Ltd, Commercial Arbitration Petition No. 232 of 2024, decided by the Bombay High Court on 24 December 2025 (Sandeep V. Marne, J., citation 2025:BHC-OS:26730), is a direct, recent illustration of Section 42. Godrej bought 8,339 stainless steel tubes from Remi Sales for refinery heat exchangers, delivered in early 2017. Weeks later Godrej found rusting and pitting on some tubes; around 965 were sent back, cleaned, and reinserted into service. Only months after that did Godrej try to reject the entire consignment and withhold payment.

The tribunal, and then the Bombay High Court on a Section 34 challenge, held that Godrej's own conduct decided the case: installing and reinstalling the tubes was "inconsistent with the ownership of the seller" under Section 42, triggering deemed acceptance. Having used the goods, Godrej could not later reject the consignment; the remedy for any residual defect was a warranty claim, not rejection. The arbitral award of roughly Rs 4.25 crore against Godrej, with interest, was upheld.

The lesson generalises well beyond steel tubes: put a delivery to use, even partially, before you finish checking it, and you may have already accepted it in law, whatever your QA team still thinks is "under review."

Red flags

Normal	Red flag	Why it matters
Acceptance criteria reference a specific document (a spec, a test plan, agreed use cases)	Criteria are vague ("satisfactory to Buyer," "meets industry standards")	A vague standard lets whichever side controls the test decide the outcome, with little for a court to check the dispute against
Review window is matched to the complexity of what is being reviewed	Deemed-acceptance window is unrealistically short (three to five days for a complex system)	A short fixed window can be unreasonable on the facts, but if clearly agreed it is still a real risk, not just a technicality
Buyer gets a genuine right to inspect or test before the deemed-acceptance clock starts	Clock runs from delivery or invoice date, not from when testing could realistically begin	This can start the clock before the buyer even has Section 41's "reasonable opportunity" to examine
Seller gets a defined cure period after rejection, with a right to re-test	No cure right; one failed test is final, or cure is at seller's sole discretion	A one-shot test with no cure right is harsh for complex deliverables where a first-pass failure is common and fixable
"Use" that counts as acceptance is defined narrowly (full production use of the complete deliverable)	Any use, including a pilot or partial deployment, counts as acceptance of the whole delivery	You can lose your right to reject the rest just by running a cautious trial of part, as in Godrej v Remi Sales
Partial acceptance is addressed (accepting one batch does not waive rights on the rest)	Silent on partial delivery, so using one tranche arguably deems the whole order accepted	On a phased delivery, silence can bind you to the whole order over one tranche you used
Rejection requires only intimation to the seller, consistent with Section 43	Rejection requires the buyer to physically return goods before it is valid	Section 43 says intimation is enough; a clause demanding more is enforceable but adds cost a buyer may not expect

Bad clause versus better clause

Bad: "Deliverables shall be deemed accepted five (5) days after delivery unless Buyer notifies Seller in writing of any non-conformity. Any use of the Deliverables by Buyer, including for testing, shall constitute unconditional acceptance of the entire Deliverables. Seller shall have no obligation to cure any non-conformity notified after the deemed acceptance date."

What is wrong: five days is unrealistically short for anything beyond simple goods; any use, including a limited test, is defined as full acceptance, punishing exactly the caution a careful buyer should exercise; and there is no cure right once the window lapses.

Better: "Buyer shall have thirty (30) days from delivery, or ten (10) business days from completion of the acceptance tests in Schedule 3, whichever is later, to test the Deliverables against the criteria in Schedule 3 (the "Acceptance Period"). Buyer may reject the Deliverables in whole or in part by written notice specifying the non-conformity. On a valid rejection, Seller shall cure it within fifteen (15) business days and Buyer shall have a further ten (10) business days to re-test. Deployment of a Deliverable solely to conduct the acceptance tests in Schedule 3 shall not, by itself, constitute acceptance. If Buyer does not reject within the Acceptance Period, the Deliverables shall be deemed accepted."

What changed: the window ties to a defined test process with a realistic minimum; a cure-and-re-test cycle means a first failure is not fatal; and testing is carved out from "use," so the buyer can run acceptance tests without accidentally accepting a defective build.

How it interacts with related clauses

An acceptance clause is a hinge between several other clauses, and reading it alone misses most of the risk.

• Warranty. Acceptance usually starts the warranty clock. A short window paired with a warranty that only begins at acceptance shortens your real coverage.
• Payment terms. Acceptance is commonly the trigger for a payment milestone. A seller who controls the test and sets a short window effectively controls when it gets paid.
• Limitation of liability. Once accepted, your remedy usually shrinks from "reject and get your money back" to "claim damages within the cap." A generous acceptance process preserves the stronger remedy for longer.

You do not need a lawyer to spot most of this. You can mark up an acceptance clause, flag a deemed-acceptance window that looks too short, or check whether a cure-and-re-test right exists, for free, using Weave.

US and global contrast

US commercial contracts, under the Uniform Commercial Code for goods, use a broadly similar structure: acceptance on a buyer's signification, on failure to reject after a reasonable opportunity to inspect, or on an act inconsistent with the seller's ownership, close cousins of Section 42. The UCC also gives buyers "revocation of acceptance," letting a buyer undo an acceptance later if a defect was hard to discover at the time and substantially impairs the goods' value, a safety valve Indian statutory law does not provide in the same form; once Section 42's deeming fiction is triggered, the Indian fallback is generally a warranty or damages claim, not an unwinding of acceptance, as Godrej v Remi Sales shows. Do not assume a "deemed acceptance" clause copied from a US master services agreement carries the same UCC-style safety net inside an Indian law contract.

FAQ

What is a deemed-acceptance clause? A clause that treats a delivery as accepted if the buyer does not raise a rejection within a stated window, whether or not the buyer actually reviewed it. For goods, Section 42 of the Sale of Goods Act, 1930 provides a similar default, deeming acceptance after "the lapse of a reasonable time" without a rejection notice; a contract clause typically fixes that reasonable time as a specific number of days.

Can a very short deemed-acceptance window, like three days, actually be enforced in India? It can be, if the contract clearly states it, because Section 42's "reasonable time" default only fills gaps where the contract is silent. Negotiate the window before signing.

Does using part of a delivery count as accepting all of it? It depends on the clause. In Godrej and Boyce Mfg Co Ltd v Remi Sales and Engineering Ltd, using and reinstalling some of the delivered tubes was treated as deemed acceptance under Section 42. A well drafted clause should say explicitly whether using part of a delivery affects your rights over the rest.

Does Section 42 of the Sale of Goods Act apply to software or services contracts? Not directly. The Act governs the sale of goods. A pure software or services deliverable falls under general contract law, mainly the Indian Contract Act, 1872, so your acceptance mechanics depend on what the contract says.

If I reject goods, do I have to send them back to the seller? No, not unless the contract says otherwise. Section 43 says a buyer who validly refuses to accept goods "is not bound to return them to the seller, but it is sufficient if he intimates to the seller that he refuses to accept them." Some contracts add a return obligation, which is enforceable by agreement.

This guide explains what an acceptance clause generally does under Indian law, how Sections 41 to 43 of the Sale of Goods Act, 1930 define deemed acceptance for goods, and what to check before you sign one. It does not tell you whether a specific window in your contract is reasonable, whether an act you took has already triggered acceptance, or how a court would decide your particular facts, that depends on your industry, your contract's wording, and what actually happened, and is not legal advice. Talk to a lawyer before you rely on, or sign away, an acceptance right on a deal that matters.