The Acceptance Testing Clause: What It Means and How to Negotiate It (2026)

What is an acceptance testing clause? An acceptance testing clause sets out how a buyer checks that what a supplier delivered, usually software, a system or custom work, actually meets the agreed requirements before the buyer has to accept it and, often, before the final payment is due. It defines the test, the pass or fail standard, how long the buyer has to test, what happens if the delivery fails, and when the delivery counts as accepted. It matters because acceptance is the trigger for money and risk. Acceptance usually releases a payment milestone, starts the warranty period, and shifts responsibility for the delivered item onto the buyer. A weak clause lets a supplier treat a flawed delivery as accepted; a strong one gives the buyer a clear, time-boxed right to say "this does not meet what we agreed" and to require a fix. This article is general guidance, not legal advice. Acceptance mechanics vary by deal and jurisdiction, so have a qualified professional adapt any clause. ## Sample acceptance testing clause ```

ACCEPTANCE TESTING 1. ACCEPTANCE CRITERIA The Deliverables must meet the acceptance criteria set out in [Schedule [X] / the agreed specification] (the "Acceptance Criteria"). 2. TEST PERIOD On delivery, the Customer has [N] business days (the "Test Period") to test the Deliverables against the Acceptance Criteria. 3. NOTICE OF RESULT Before the end of the Test Period the Customer will give written notice that the Deliverables are: (a) accepted; or (b) rejected, with reasonable detail of each failure to meet the Acceptance Criteria. 4. REMEDY ON FAILURE If rejected, the Supplier will at its cost correct the failures and re-deliver within [N] days, and a new Test Period of [N] days will apply to the re-delivered Deliverables. 5. REPEATED FAILURE If the Deliverables fail acceptance [N] times, the Customer may, at its option, [accept with a price reduction] / [terminate the relevant order and recover sums paid for the rejected Deliverables]. 6. DEEMED ACCEPTANCE The Deliverables are deemed accepted if the Customer uses them in live production [other than for testing] or does not give a notice under clause 3 within the Test Period.

- **Test period (clause 2).** Negotiate a period long enough to run a realistic test. Suppliers want it short so the milestone is reached; buyers want enough days to exercise the system properly.
- **Notice and detail of failure (clause 3).** Requiring "reasonable detail" of each failure is fair to the supplier, who needs to know what to fix, and protects the buyer from a vague rejection being ignored.
- **Remedy and re-test (clauses 4 and 5).** The fix-and-re-test loop is standard. The real negotiation is the exit: after how many failed cycles can the buyer get out or take a price cut? Suppliers prefer endless re-tests; buyers want a clear off-ramp.
- **Deemed acceptance (clause 6).** This is where buyers lose rights. Suppliers push for broad deemed-acceptance triggers, such as "any use" or short silence. As a buyer, carve out use for testing or evaluation, and make sure silence only triggers acceptance after a clear, reasonable period. Deemed acceptance on "going live" is reasonable, but "any use whatsoever" is a trap. ## Common mistakes to avoid - Leaving the acceptance criteria to be agreed after signing, so there is nothing objective to test against.
- A "satisfaction" standard instead of defined, measurable criteria.
- A deemed-acceptance trigger so broad that normal testing or a short delay loses the buyer's rights.
- No cap on re-test cycles, so a chronically failing delivery never lets the buyer exit.
- Not linking acceptance to the payment milestone and the start of the warranty period, so the two drift apart. ## A note on jurisdiction and contract type Acceptance testing is mostly a matter of what the parties agree rather than a statutory right, so the drafting does the work. That said, in a sale of goods, background law on rejection of non-conforming goods can also apply, and it varies by jurisdiction (for example the US Uniform Commercial Code, the UK Sale of Goods Act 1979, and India's Sale of Goods Act, 1930). For construction and engineering, acceptance often appears as "taking over" or "practical completion" with its own regime. Match the clause to the contract type and confirm the background law in your jurisdiction. Last verified October 2026. ## Where a contract workspace helps A good acceptance clause is only useful if it is actually used: the criteria attached, the test period diarised, the rejection notice sent in time, and the right linked to the payment milestone. Across many supplier contracts, those dates and obligations are easy to lose. Drafting acceptance testing terms, reviewing how they connect to the payment and warranty clauses, and tracking the test periods and rejection deadlines can all live in one AI workspace tuned to how your company buys. [Adira](https://adiralaw.com) brings that kind of single workspace to acceptance testing and the terms around it. The clause above stands on its own for negotiating a fair provision.