What is Acceptance Test?

For complex or bespoke deliveries — particularly software, IT systems, machinery installations, or construction works — a visual inspection at handover is insufficient. A structured test is needed to demonstrate that the system actually does what it was contracted to do.

An acceptance test consists of a set of test scenarios based on the functional specification agreed at the outset of the project. Each scenario defines an action, the expected outcome, and the actual outcome. Scenarios that pass are accepted; scenarios that fail are recorded as findings.

The outcome of the acceptance test can be: full acceptance (all scenarios passed), conditional acceptance (defects identified but not blocking, remediation agreed), or rejection (critical defects that do not justify acceptance of the delivery).

Several contractual provisions are essential. First, acceptance criteria must be defined upfront: what constitutes a passed test and what counts as a critical defect? Second, the acceptance period must be specified: how many days does the buyer have to test and respond? Third, the contract should address what happens if the buyer does not respond within the acceptance period — in many contracts, silence is treated as acceptance.

In practice, a two-stage approach is common: an initial acceptance test at delivery, followed by re-evaluation after defects are remediated. Only after the second test passes does final acceptance take effect.

For SMBs acquiring IT systems or software solutions, a clear acceptance testing protocol is an essential part of the contract. Without one, delivery frequently leads to disputes about what was agreed and whether the system performs to specification.

Without an acceptance test, you accept a system on trust. Defects discovered after formal acceptance are harder to enforce: the warranty period has already started and the supplier has received the final payment instalment.

A well-structured acceptance process protects you as a buyer: you pay the final instalment only when the system genuinely works, the warranty period starts when you actually put the system into use, and defects are documented in writing before the supplier considers its obligations fulfilled.