Understand Article 140 of Brazilian Law 14,133 as applied to receipt of engineering works and services: detailed certificates, provisional and final receipt, rejection, testing, documentation, and responsibilities.
Check it out!
Article 140 of Brazilian Law 14,133 governs how the Administration must receive the contracted object and, for works and services, establishes a formal verification sequence: provisional receipt by the person responsible for monitoring and inspection, through a detailed certificate and verification of technical requirements; and final receipt by a public employee or appointed commission, also through a detailed certificate demonstrating compliance with contractual requirements.
This structure means that physical completion, delivery by the contractor, provisional receipt, technical acceptance, and final receipt are not synonyms. A work may be materially complete and still have incomplete documentation, pending tests, nonconformities, As-Built documentation inconsistent with execution, untraceable warranties, or contractual requirements that have not been demonstrated. In this condition, simply communicating that “the service is finished” does not replace the verification that supports receipt.
The article also provides that the object may be rejected, in whole or in part, when it does not comply with the contract; that receipt deadlines and methods must be defined in regulation or in the contract itself; and that inspections, tests, and other proofs required by official technical standards are, unless otherwise provided, borne by the contractor. For the client’s engineering team, therefore, Article 140 should be read as a delivery-governance rule: closeout needs to be planned with time, criteria, evidence, responsibilities, and a real correction window.
What Article 140 of Brazilian Law 14,133 requires for works and services
The Law separates two decisions. At provisional receipt, the person responsible for monitoring and inspection verifies compliance with technical requirements. At final receipt, a public employee or commission appointed by the competent authority formalizes, in a detailed certificate, that contractual requirements have been met.
This distinction is relevant because it prevents receipt from being treated as a single bureaucratic act. The first milestone is directly associated with technical verification of the object; the second broadens the analysis to the contractual conformity necessary to close the delivery. The article on the Final Receipt Certificate examines the distinction among physical completion, technical delivery, provisional receipt, acceptance, and final receipt.
| Stage | Responsible party under Article 140 | Central question | Expected evidence |
| Provisional receipt | Person responsible for monitoring and inspection | Were the technical requirements met? | Detailed certificate, inspections, tests, documents, and records |
| Treatment of outstanding items | Contractor and inspection, according to the contract | Were the identified deviations corrected and reverified? | Punch list, NCRs, correction evidence, and retests |
| Final receipt | Appointed public employee or commission | Were the applicable contractual requirements met? | Detailed certificate supported by the body of technical and contractual evidence |
Final receipt should not function as a substitute for inspection performed during execution. It consolidates a decision that needs to be supported by evidence produced throughout the contract.
Receipt requires evidence, not merely physical completion. When the object includes multiple disciplines, critical systems, or extensive documentation, final inspection needs to convert contractual requirements into objective and traceable verifications.
Provisional receipt: the detailed certificate begins with technical verification
For works and services, provisional receipt is associated with the role of the person who monitored and inspected the contract. This creates a direct relationship between execution control and the decision to recognize that the object has reached the technical conditions required for that milestone.
The expression detailed certificate is particularly relevant. A one-line document stating that “the services were received” does not, by itself, show which requirements were verified, which documents were analyzed, which tests were performed, or which outstanding items remain. The robustness of receipt depends on traceability among requirement, evidence, and technical conclusion.
In engineering contracts, verification normally needs to consider, according to the object:
- scope and quantities actually executed;
- adherence to design, specifications, and contractual documents;
- quality of execution and inspection records;
- inspections, tests, and commissioning results;
- nonconformities and their closure;
- final documentation and approved revisions;
- As-Built documentation consistent with the constructed condition;
- photographic reports and field evidence;
- warranties, certificates, manuals, and licenses;
- training, assisted operation, or transfer to operations when specified.
When the client’s structure does not have all the necessary specialization, technical support for inspection of engineering works and contracts can organize inspections, evidence, outstanding items, and verification without removing the public agent’s decision-making authority.
Final receipt: contractual compliance must be demonstrated
Final receipt is carried out by a public employee or commission appointed by the competent authority and requires a detailed certificate demonstrating compliance with contractual requirements. The word demonstrating changes the logic of the process: it is not enough to have a perception that the work “is ready”; there must be a documentary and technical basis capable of supporting the decision.
The Brazilian Federal Court of Accounts notes that final-receipt documentation, together with that produced for provisional receipt, forms the documentary basis for closeout and payment settlement. For works, final receipt occurs after project completion; partial measurements during execution are not the same as final receipt of the object.
Therefore, the documentary chain needs to be coherent. If execution presents a given field condition, the As-Built must represent that condition. If a requirement depends on performance, a corresponding test or inspection must exist. If a nonconformity occurred, there must be a treatment record and closure evidence. If the scope changed, contractual documentation must explain how that change was authorized and incorporated.
The Technical Acceptance Certificate in Engineering is a useful instrument for consolidating this validation, provided it is not treated as a receipt and is supported by applicable criteria and evidence.
What a detailed certificate means in an engineering context
The Law does not transform the detailed certificate into a single standard form. The required content depends on the object, contract, applicable regulation, and technical criticality. From the perspective of sound engineering governance, however, the document needs to allow the receipt decision to be reconstructed.
A technically defensible certificate tends to record:
- identification of the contract, object, stage, and parties involved;
- reference to the formal delivery or receipt request submitted by the contractor;
- list of the documents and revisions analyzed;
- technical and contractual criteria used in verification;
- inspections, tests, and verifications performed;
- status of outstanding items and nonconformities;
- any reservations admitted and their justification;
- remaining warranty, correction, or documentation obligations;
- objective conclusion regarding receipt, rejection, or need for correction;
- identification of those responsible for analysis and formalization.
The certificate does not need to reproduce every report in full. It should traceably reference the evidence supporting the conclusion. This architecture is compatible with Requirements, Evidence, and Acceptance Criteria Management, which organizes the relationship between what should have been met and what demonstrates compliance.
The object may be rejected in whole or in part
Article 140, §1, establishes that the object may be rejected, in whole or in part, when it does not comply with the contract. This provision prevents receipt from being treated as an automatic consequence of elapsed time or the contractor’s simple declaration.
Rejection needs to be supported by verifiable criteria. In engineering, this means demonstrating the divergence between a requirement and the condition found. The difference may involve quantity, quality, performance, documentation, safety, functionality, integration, schedule, or another contractual obligation.
Nonconformities need to be recorded objectively. The Nonconformity Report — RNC/NCR enables documentation of the deviation, disposition, responsibility, corrective action, retest, and closure. The Outstanding Items, RFIs, and Nonconformities Management solution extends this control across the project.
Not every outstanding item has the same criticality. An easily corrected naming error should not be treated as equivalent to the absence of a functional test for a critical system. The process needs to classify impact, risk, condition of use, and effect on receipt.
The contractual period is not exclusively an installation period
Article 140, §3, requires deadlines and methods for provisional and final receipt to be defined in regulation or in the contract. This point has an important management consequence: the contractor’s schedule must reserve time to deliver, be verified, correct outstanding items, and demonstrate the correction.
A 90-day contract does not mean the company has 90 days to execute physically and may submit the acceptance request on the last day. Proper delivery needs to fit within a planned sequence:
- completion of physical execution;
- consolidation of final documentation;
- formal receipt request;
- inspection and document analysis by the client;
- applicable commissioning, inspections, and testing;
- issuance of outstanding items;
- corrections by the contractor;
- reverification and retesting;
- technical opinion;
- receipt at the specified milestones.
When the tender documents and Terms of Reference do not define this logic, the problem is shifted to the end of the contract. The Technical Review of Terms of Reference for Engineering Works and Services and Technical Review of Tender Documents and Appendices help verify whether requirements, documents, responsibilities, and receipt criteria were defined before bidding.
Receipt begins during procurement planning. Acceptance criteria, final documents, tests, responsible parties, and correction windows need to be defined before execution; otherwise, the Administration tries to solve at closeout what should have been contracted from the beginning.
Technical Review of Terms of Reference for Engineering Works and Services
Inspections, tests, and proof of proper execution form part of receipt
Article 140, §4, establishes that, unless otherwise provided in the tender documents or in a regulatory act, the inspections, tests, and other evidence necessary to assess proper execution, when required by official technical standards, are borne by the contractor.
This provision reinforces that demonstrating conformity is not an ancillary activity. When a requirement can only be validated by testing, the test forms part of proof of delivery. The object does not become technically acceptable simply because it was installed.
In engineering systems, verification may involve electrical tests, functional testing, communication among subsystems, redundancy, performance, safety, failure operation, parameterization, integration, and other criteria defined in the design and contract. Commissioning of Works and Buildings organizes these tests into a documented sequence that can support receipt.
The Administration also needs to distinguish a performed test from a demonstrated test. A technician stating that “it was tested” does not replace a report identifying the procedure, instruments, test condition, result, acceptance criterion, and responsible person.
Final documentation is not an administrative accessory
Document quality forms part of delivery quality. The client needs to operate, maintain, audit, and eventually modify what it received. Without reliable documentation, the organization inherits an asset whose actual condition cannot be reconstructed safely.
For higher-complexity objects, final documentation may include As-Built drawings, equipment lists and serial numbers, certificates, warranties, test reports, design narratives, drawings, diagrams, backups, parameter settings, photographic records, manuals, training records, closed NCRs, and other documents defined in the contract.
The Engineering Data Book consolidates this set. When the package is extensive or presents inconsistencies, a Technical Audit of Data Book and Final Documentation can verify completeness, revision, traceability, and adherence to the contract before receipt.
A delivered document is not necessarily a validated document. At closeout, inconsistencies among field conditions, As-Built documentation, tests, warranties, and records can compromise receipt traceability even when the documentary package appears extensive.
Technical Audit of Data Book and Final Engineering Documentation
Provisional and final receipt do not eliminate responsibilities
Article 140, §2, establishes that provisional or final receipt does not exclude civil liability for the solidity and safety of the work or service, nor ethical-professional responsibility for proper execution, within the limits of the law or contract.
The Law also establishes specific rules for a works design and for works themselves. In the case of a design, final receipt does not remove the designer’s or consultant’s responsibility for damage caused by a design failure. In the case of works, the Law preserves the contractor’s responsibility for solidity, safety, functionality, and correction of defects under §6.
This means that receipt is not equivalent to waiving the client’s rights. However, poorly produced receipt documentation can make it difficult to reconstruct the history, identify the existing condition at the delivery milestone, and manage warranties afterward.
How to structure receipt from procurement planning onward
The best receipt process is one that does not need to improvise criteria at the end. Delivery requirements should originate during planning and run throughout the procurement life cycle.
At the Preliminary Technical Study stage, the Administration identifies the need, expected results, and constraints of the object. In the Terms of Reference or Basic Design, it converts those needs into scope, requirements, deliverables, performance criteria, and documentation. In the tender documents, it preserves consistency in selection and execution criteria. During the contract, inspection and management monitor evidence, measurements, changes, and outstanding items. At closeout, the records already exist and only need to be consolidated.
The sequence can be structured as follows:
| Phase | Definition needed for future receipt |
| Planning | need, risks, expected performance, and procurement strategy |
| Design/ToR | scope, documents, tests, acceptance criteria, and responsibilities |
| Tender documents | verifiable requirements consistent with competition |
| Qualification | proof of the required technical capacity |
| Execution | inspections, measurements, NCRs, changes, and evidence |
| Commissioning | performance and integration tests |
| Delivery | final documentation, formal request, and condition for inspection |
| Receipt | detailed certificates supported by evidence |
This view connects Article 140 to the rest of Brazilian Law 14,133 and to engineering of the procurement process. The article Can the Contract Inspector Have Technical Support? shows how specialized support can complement inspection when the complexity of the object exceeds internally available capacity.
Applied case: substantially installed electronic security system
Consider an electronic security implementation with IP CCTV and access control. The contractor completes most of the physical installation and reports that the system is ready. Cameras display images, controllers are energized, and the software is operating. Visually, implementation appears close to 100%.
When verification begins, however, the client’s engineering team identifies that the As-Built does not fully correspond to field conditions, some equipment lacks recorded serial numbers, test reports do not demonstrate acceptance criteria, some parameter settings are undocumented, identification items remain open, and the warranty package is not traceable. The formal receipt request was also submitted when only a few days remained in the planned operational term.
In this scenario, the relevant question is not “are the cameras working?” The question is whether the technical and contractual requirements have been demonstrably satisfied for the applicable receipt milestone.
The situation illustrates why an installed system is not a delivered system. A high physical percentage, substantial completion, or apparent operation do not replace documentation, testing, traceability, and closure of outstanding items.
What to verify before signing the receipt certificate
Before formalization, the technical responsible person, manager, or commission should work from a verification matrix compatible with the contract. A generic checklist does not replace the object’s actual requirements, but some control groups are recurrent.
Scope and execution
Verify whether quantities, systems, interfaces, materials, and services correspond to the contracted scope and formally approved changes.
Quality and nonconformities
Confirm the status of inspections, NCRs, punch lists, and outstanding items. Critical items cannot be hidden by a high physical completion percentage.
Testing and performance
Verify that specified inspections and tests were performed under the correct conditions and that results demonstrate the established criteria.
Final documentation
Verify that documents have the correct revision, signature or responsibility when required, internal consistency, and correspondence with the executed condition.
Warranties and operations
Confirm warranty start, term, and scope; manufacturer documentation; licenses; access; training; backups; and other elements needed for operations.
Formalization
Record the decision in a detailed certificate, identifying documents analyzed, outstanding items, reservations, and remaining responsibilities.
When the contractor simply reports that it finished the work, the content Construction Delivery Certificate: What to Verify Before Receipt and Acceptance provides a practical sequence for organizing the assessment.
Where Consulting Engineering and Owner’s Engineering fit
Article 140 defines administrative responsibilities for receipt; it does not replace the need for technical competence to assess complex objects. The decision remains with the designated agents, but forming that decision may require inspections, technical opinions, testing, document analysis, and multidisciplinary knowledge.
Owner’s Engineering works on the owner’s side to preserve requirements, interfaces, quality, evidence, and acceptance criteria throughout implementation. When engaged from planning onward, it reduces the likelihood that the organization will discover problems only at closeout.
A technically robust chain can involve:
Design and requirements → technical review of procurement → tender support → technical qualification → Detailed Design analysis → inspection/Owner’s Engineering → QA/QC → commissioning → final documentation → technical opinion → receipt.
This work does not replace administrative authority. It provides independent technical capacity so that the decision can be made based on evidence.
Technical independence is especially valuable at closeout. The contractor demonstrates what it performed; the owner’s engineering team verifies it, confronts requirements, organizes evidence, and supports the client’s decision on outstanding items, corrections, and acceptance.
How to contract technical support for the receipt process
The support scope should be defined according to the contract phase and existing problem. For a procurement still in planning, the priority is to structure criteria, documents, and receipt methods. During execution, the need shifts to inspection, evidence, and outstanding-item management. Near closeout, the focus becomes final inspection, commissioning, document auditing, and technical opinion.
A consistent scope may provide for:
- review of contractual receipt requirements;
- criteria-and-evidence matrix;
- field inspections;
- analysis of As-Built and final documentation;
- monitoring of inspections and tests;
- preparation or review of the punch list;
- verification of corrections;
- Data Book audit;
- support for the detailed certificate and technical opinion;
- support for transition to operations and warranties.
Technical Receipt of Engineering Works and Services materializes this need when the client requires an organized assessment of the object before closeout.
Final considerations
Article 140 of Brazilian Law 14,133 turns receipt into a verifiable process. For works and services, there are distinct responsibilities at provisional and final receipt, both supported by detailed certificates. The Law permits rejection of a noncompliant object, requires deadlines and methods to be defined, and preserves the need for inspections, tests, and responsibilities after receipt.
For the client’s engineering team, the practical consequence is direct: receiving is not recording that the contractor finished; it is forming and documenting sufficient evidence that the object meets the applicable technical and contractual milestone. The earlier criteria, documents, tests, and responsibilities are defined, the lower the probability that closeout becomes a dispute over what should have been demonstrated during execution.
Technical references
[1] BRAZIL. Law No. 14,133, April 1, 2021. Public Procurement and Administrative Contracts Law. Available at: https://www.planalto.gov.br/ccivil_03/_ato2019-2022/2021/lei/l14133.htm
[2] FEDERAL COURT OF ACCOUNTS (TCU). Procurement and Contracts: Contract Management and Final Receipt. Available at: https://licitacoesecontratos.tcu.gov.br/6-1-6-gestao-do-contrato-e-recebimento-definitivo-2/
[3] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO). ISO 21502:2020 — Project, programme and portfolio management — Guidance on project management. Available at: https://www.iso.org/standard/74947.html
Frequently asked questions
Article 140 provides for provisional receipt by the person responsible for monitoring and inspection, through a detailed certificate after verification of technical requirements, and final receipt by an appointed public employee or commission, also through a detailed certificate demonstrating compliance with contractual requirements.
No. Provisional receipt is a milestone distinct from final receipt. It is linked to verification of technical requirements and may be followed by treatment of outstanding items, corrections, additional verification, and final formalization according to the contract and regulation.
Yes. Article 140, §1, permits rejection of the object, in whole or in part, when it does not comply with the contract. The decision should be supported by criteria and evidence demonstrating the nonconformity.
Article 140, §3, establishes that the deadlines and methods for provisional and final receipt must be defined in regulation or in the contract. These milestones therefore need to be planned during procurement.
Unless otherwise provided in the tender documents or a regulatory act, Article 140, §4, establishes that inspections, tests, and other proofs required by official technical standards to assess proper execution are borne by the contractor.
No. The Law preserves civil, ethical-professional, solidity, safety, functionality, and defect-correction responsibilities under the applicable terms even after receipt.
When the object requires specialization the internal team does not fully possess, when documentation is extensive or inconsistent, when critical systems or multiple interfaces exist, when there are relevant outstanding items, when commissioning is needed, or when there is doubt about conformity among contract, design, execution, and evidence.
Complementary technical materials
Related solutions
- Requirements, Evidence, and Acceptance Criteria Management
- Contract, Scope, and Deliverables Management
- Outstanding Items, RFIs, and Nonconformities Management
Related services
- Technical Receipt of Engineering Works and Services
- Technical Support for Inspection of Engineering Works and Contracts
- Technical Audit of Data Book and Final Engineering Documentation
- Technical Review of Terms of Reference for Engineering Works and Services
- Technical Review of Tender Documents and Appendices for Engineering Procurement
Main content on this topic
- Final Receipt Certificate: Why Completed Installation Does Not Mean Accepted Delivery
- Construction Delivery Certificate: What to Verify Before Receipt and Acceptance
- Technical Acceptance Certificate in Engineering
- Installed System Is Not a Delivered System
- Can the Contract Inspector Have Technical Support?
