Payment Against Acceptance: The Clause That Can Delay an Entire Project

In supply, technology and construction agreements, the parties often negotiate price extensively while leaving acceptance to a few lines. That omission can change when payment becomes due, whether delay damages continue to run and who bears the cost of repeated testing. Acceptance provisions require the same precision as pricing provisions.

Define the object of acceptance

Delivery and acceptance are not synonymous. Equipment may be physically delivered but fail commissioning tests; software may be installed without meeting its functional specifications; a construction milestone may have been substantially achieved despite minor defects. The contract should identify the deliverable, objective performance criteria, test environment and evidence required to confirm completion. If acceptance depends on the customer's subjective satisfaction, the supplier cannot forecast cash flow or establish breach reliably. If acceptance is automatic on delivery, the customer may lose meaningful assurance that the product performs as promised.

Avoid an indefinite payment gate

A clause requiring payment only upon a customer certificate is particularly dangerous when the customer controls certification and the contract imposes no decision period. The supplier should consider a requirement to inspect within a specified time, provide reasoned rejection notices and accept work not rejected on identified grounds. Deemed acceptance can be appropriate in some services but may be inappropriate for safety-critical equipment or statutory testing. The parties should decide whether minor defects justify withholding the whole milestone or only an objectively assessed portion. Withholding must have a contractual basis and should not be confused with an unrelated claim for damages.

Separate defects from variations

A customer cannot reasonably expect acceptance tests to become a route for demanding additional functionality outside the original scope. The specification, approved change orders and agreed tolerances should determine whether an item is defective or a variation has been requested. Conversely, a supplier should not describe an essential missing function as an enhancement merely to obtain payment. A transparent change-control process, with revised costs and timetable, can prevent both forms of opportunism. Retesting obligations should specify who pays where failure is attributable to defective delivery rather than changed customer requirements.

Link acceptance to title, risk and security

Commercial contracts often attach different consequences to delivery, installation, taking-over, provisional acceptance and final acceptance. Title to goods, insurance risk, warranty commencement, retention release and performance security should not move at contradictory times without deliberate agreement. In financed projects, lenders may use the acceptance certificate as a drawdown condition. The contract should therefore distinguish the customer's technical sign-off from the formal payment certificate and the bank's financing process. Where the customer delays certification, the supplier needs a workable record of completion and a defined dispute route.

Make acceptance capable of proof

Acceptance must be testable, timely and consistent with the rest of the contract. A sound mechanism states who inspects, by reference to which standards, within what period, and what happens if agreement is not reached. It should allow the customer to reject non-conforming work without giving either party indefinite control over the other's cash flow.