Glossary term
Accept Contract Deliverables
TERM SUMMARY
Accept Contract Deliverables is the contract-administration activity in which the responsible official receives deliverables, compares them with the contract's requirements, and formally accepts or...
- Why it matters
- Accept Contract Deliverables is the contract-administration activity in which the responsible official receives the deliverables a supplier has produced, compares them with the requirements in the contract, and formally...
- Category
- Canadian government procurement terminology
- Reference role
- This term page is designed to be linkable, crawlable, and easy to quote or summarize.
Accept Contract Deliverables is the contract-administration activity in which the responsible official receives the deliverables a supplier has produced, compares them with the requirements in the contract, and formally accepts or rejects them. It is the point at which the Crown confirms that what was delivered matches what was bought.
In Government of Canada guidance, acceptance follows the resolution of any discrepancies with the vendor and supports certification under section 34 of the Financial Administration Act. The Supply Manual lists it as activity 5.4.5 and assigns it to the Project Manager/Technical Authority.
Where acceptance sits in federal contract administration
The Treasury Board Secretariat describes a "Manage Procure to Payment" process. Its contract-administration subprocess, numbered 3.1.6, covers monitoring the contract, certifying receipt and acceptance of deliverables, reviewing financial performance, and managing vendor issues. Acceptance is therefore one step in a chain that runs from monitoring the work through to payment. The full text is in the Treasury Board Secretariat policy document.
The same guidance links acceptance to certification under section 34 of the Financial Administration Act. Once discrepancies are resolved, the deliverables are officially accepted as part of that certification. Acceptance is a formal record that supports the later steps, not an informal sign-off.
Who makes the acceptance decision
The Supply Manual assigns "Accept Contract Deliverables" to the Project Manager/Technical Authority, often shortened to PM/TA. This separates the technical judgement about whether a deliverable meets the contract from payment processing and other contracting functions, which sit with other officials.
For a supplier, this means the person who reviews and accepts the work is usually the technical lead named in the contract, not the contracting officer who negotiated it. Related activities include receiving deliverables, contract monitoring, acceptance criteria, acceptance testing, rejection, certification of receipt, and payment.
How deliverables are checked and documented
Federal guidance describes receiving deliverables as physically receiving them and then accepting or rejecting them based on damage, quantity, or other criteria defined by the contract. Deliverables are compared with the contract's terms and conditions. Any discrepancies are noted and resolved with the vendor before the deliverables are officially accepted.
Documentation supports the decision. The guidance gives these examples of records that may back up receipt or acceptance:
- a bill of lading
- the deliverable itself
- a timesheet
- a notice of acceptance
Acceptance procedures written into solicitations
Individual solicitations can spell out the acceptance steps. One Public Services and Procurement Canada solicitation, published on CanadaBuys, requires the contractor to submit each deliverable to the Technical Authority and notify the Contract Authority. The contractor must also provide an acceptance form and the deliverable in the format specified by Canada.
Where a solicitation sets out its own procedure like this, it governs how that contract's deliverables move from submission to acceptance.
What this means for a supplier bidding on Canadian public contracts
A supplier must provide the contracted goods, services, or other deliverables in the required format and satisfy the contract's applicable acceptance requirements. If a deliverable does not meet them, the buyer may reject it or require correction. Federal guidance expressly provides for rejection based on criteria such as damage, quantity, or other conditions the contract defines.
Bid teams should read the acceptance language in a solicitation closely. Identify who the Technical Authority and Contract Authority are, what acceptance form is required, and what format each deliverable must take. Keep records such as delivery documents, timesheets, and notices of acceptance, since they support the buyer's certification and move the contract toward payment.