Designing Acceptance Inspection Clauses: The Clause That Shapes Payment Timing and the Period of Liability for Non-Conformity
Hello, I'm Noriaki Asato, Representative Attorney at LegalAgent.
An acceptance inspection clause is not a procedural provision to be checked only when trouble arises. It is the clause that sets the timeline for the whole contract: under a contract for work, when the remuneration can be claimed, how long liability for non-conformity can be pursued, and which party bears the risk of loss of or damage to the subject matter. I believe that one reason disputes over acceptance keep recurring in system development and manufacturing outsourcing is that acceptance clauses are not worded in a way that identifies these starting points.
Three Starting Points That Shape Payment and the Liability Period
Under a contract for work, the remuneration is, as a rule, payable at the same time as the subject matter of the work is delivered. Article 633 of the Civil Code sets out this rule. Where delivery of a thing is not required, the proviso to the same Article applies mutatis mutandis Article 624(1), which concerns remuneration under an employment contract, and the contractor cannot claim remuneration until after finishing the work. In software development and system building, contracts are often designed so that this "delivery" is tied to passing the acceptance inspection. If the contract provides that delivery is not complete while the deliverable falls short of the acceptance criteria, the time at which remuneration can be claimed is pushed back accordingly. Civil Code, Article 633 (Japanese)
The period during which liability for non-conformity can be pursued is also tied to how acceptance is defined. Article 637(1) of the Civil Code provides that if the client fails to notify the contractor of a non-conformity in the kind or quality of the subject matter within one year after becoming aware of it, the client can no longer demand cure, a reduction of the remuneration or compensation for loss or damage, or cancel the contract. However, under paragraph (2) of the same Article, this time limit does not apply if, at the time of delivery (or, where delivery is not required, at the time the work was completed), the contractor knew of the non-conformity or did not know of it due to gross negligence. The one-year period under the Civil Code runs from the time the client becomes aware of the non-conformity, but contracts often set a separate liability period that starts on completion of acceptance. The Model Basic Agreement for Software Development Outsourcing (Second Edition) (Japanese) published by the Information-technology Promotion Agency, Japan (IPA) (the "IPA model contract") makes completion of acceptance the starting point of the liability period. Under Article 29(5), the vendor is liable only for non-conformities notified within a fixed period after acceptance is completed. If it remains unclear whether and when the deliverable passed, it also remains unclear when this contractual liability period begins. Civil Code, Article 637 (Japanese)
Which party bears the risk when the subject matter is lost or damaged for reasons attributable to neither party also depends on the time of delivery. For sales, Article 567(1) of the Civil Code provides that if, after delivery, the subject matter is lost or damaged for such reasons, the buyer cannot demand cure, a reduction of the price or other remedies on that ground and cannot refuse to pay the price. Article 559 applies the provisions of the section on sales mutatis mutandis to contracts for value other than sales, unless the nature of the contract does not permit this. In many contracts, the risk passes when delivery is complete. Whether delivery is treated as complete on passing the acceptance inspection or the risk passes earlier, at the time the deliverable is handed over, determines which party bears the loss from an accident that occurs during the acceptance inspection. Article 26(4) of the IPA model contract allocates the risk according to whether the deliverable has been handed over. It is important to draft the acceptance clause not as a formality but on the premise that its three effects, the claim for remuneration, the period for giving notice of non-conformity and the passing of risk, operate together. Civil Code, Articles 559 and 567 (Japanese)
Linking Acceptance to the Specifications and the Change Management Procedure
If the contract says only that "Party A shall inspect the deliverables and complete acceptance if they pass," it is impossible to tell what counts as passing. The acceptance criteria are often left not to the body of the contract but to attachments such as specifications, requirements definitions and test specifications. Start by checking whether those attachments are expressly made part of the contract.
Specifically, check the following three points as a checklist.
- Are the specifications and requirements definitions clearly incorporated as attachments to the contract and positioned as the basis for the acceptance criteria?
- Does the contract set an order of priority for cases where the specifications conflict with the proposal, the quotation or the minutes of meetings?
- Does the contract include a procedure for reflecting specification changes made during development in the acceptance criteria?
If specification changes are handled only orally or through chat tools, a gap opens up: the vendor considers the deliverable to have passed against the changed specifications, while the customer asserts that it failed against the original requirements definition. Unless the acceptance criteria are set together with rules for managing changes along the way, they cannot be used on the ground as the standard for deciding whether a deliverable passes.
Setting the Inspection Period and the Conditions for Deemed Acceptance
For the vendor, the inspection period is the waiting time before it can invoice; for the customer, it is the time to check that the system actually works. If the period is too short, the customer's inspection becomes a formality; if it is too long, it squeezes the vendor's cash flow. In practice, therefore, contracts often fix the period in calendar days and include a "deemed acceptance clause," under which the deliverable is treated as accepted if the customer does not give notice of the result within the period. Article 28(3) of the IPA model contract likewise provides that the software is deemed to have passed the inspection if the customer does not raise an objection in writing, stating specific reasons, within the inspection period.
Deemed acceptance protects the vendor against delayed collection, but from the customer's point of view there remains a concern that the deliverable will be unilaterally treated as accepted before its internal arrangements are in place. If you are adjusting the terms on the customer side, make clear whether the period starts on "the date the delivery note is received" or on "the date an environment in which the inspection can actually be performed is ready." In addition, if a notice of failure can be given in writing or by email and the method of notice is not made too strict, it becomes easier to communicate an objection within the period. If you are adjusting the terms on the vendor side, avoid any ambiguity about the start date and provide that the deliverable is treated as accepted on expiry of the period without any further demand. This makes it easier to avoid a situation in which invoicing is held up while the other party waits for internal sign-off.
Repairs After a Failed Inspection and Balancing the Parties' Interests
If the procedure after a failed inspection says only that the vendor "shall repair and redeliver," the people on the ground will be unsure how to proceed. The parties need to agree whether defects are handled differently depending on their severity, whether the re-inspection period is the same as the first one or shorter, and how termination and damages are dealt with if the deliverable still fails after repeated repairs.
To make the wording workable in practice, a realistic design is to classify defects as major or minor and, for minor defects that do not interfere with operation, to grant conditional acceptance with a separate deadline for repair. A provision that no acceptance will be given until every defect is fixed may look favorable to the customer, but if acceptance stalls over a minor display glitch or a small wording correction, the back-and-forth of work and payment may drag on. Making the re-inspection period shorter than the first and setting in advance a maximum number of repair rounds or a maximum repair period makes it easier to prevent the work from dragging on. A provision under which the customer may cancel the contract or demand a price reduction if the deliverable still fails after a certain number of repairs also gives the parties a standard for deciding whether to continue or end the transaction.
The vendor gives top priority to being able to predict when it can invoice and makes the acceptance criteria concrete, for example in the form of test items. Also consider a provision that extends the delivery date to the extent that the customer is late in providing materials or preparing the inspection environment. The customer, on the other hand, wants to confirm that the system can actually be used before payment and the liability period are triggered. It is therefore important for the customer to keep room to deal with defects that are hard to find in an ordinary inspection through liability for non-conformity even after acceptance. The IPA model contract also contains an optional clause covering non-conformities that, by their nature, the inspection cannot reasonably be expected to reveal. Under that clause, the vendor is liable if the customer gives notice within a fixed period after becoming aware of the non-conformity.
Refusal to Accept, Payment Due Dates and Reviewing the Clause Under the Torihiki Tekiseika Act
In system development and manufacturing outsourcing, also check whether the transaction is subject to the Act on Ensuring Proper Transactions with Small and Medium-sized Entrustees (Torihiki Tekiseika Act; formerly the Act against Delay in Payment of Subcontract Proceeds, etc. to Subcontractors). According to materials published by the Japan Fair Trade Commission and the Small and Medium Enterprise Agency, the amended Act took effect on January 1, 2026. It imposes 11 prohibited acts, including refusal to accept and late payment, and 4 obligations on entrusting business operators. Torihiki Tekiseika Act (Japanese)
Refusing to accept the deliverables of a small or medium-sized entrusted business operator when that operator is not at fault (refusal to accept) is one of the prohibited acts. It does not apply to service provision consignment or specified transportation consignment, but it applies to manufacturing consignment, repair consignment and information-based product creation consignment, such as the creation of programs. The Torihiki Tekiseika Act Text (November 2025) (Japanese) of the Japan Fair Trade Commission and the Small and Medium Enterprise Agency refers to cases where the details of the commission were not specified or the inspection criteria were unclear, so that it is not clear whether the deliverable differs from what was commissioned. In such cases, the Text states that refusing to accept the deliverable on the ground that it differs from what was commissioned is not permitted. The same applies where, after placing the order, the entrusting business operator arbitrarily tightens the inspection criteria and fails a deliverable that would have passed under the previous criteria. Practices such as using acceptance inspection as a pretext for postponing receipt itself, or refusing to accept because of minor defects, require careful consideration in transactions covered by the Act.
As for the payment due date, the entrusting business operator must set it within 60 days from the date on which it received the deliverable, and within as short a period as possible, regardless of whether it inspects the deliverable. If it fails to pay by the due date, it must pay late interest at an annual rate of 14.6% for the number of days from the day on which 60 days have elapsed from the date of receipt until the date of payment. The Text states that, even where inspection takes a considerable number of days, the payment system must allow for the time needed for inspection. A contract that allows a long period between receipt and completion of acceptance and makes payment due only after acceptance may breach this 60-day rule.
For information-based product creation consignment, the Text describes an exception concerning the date of receipt. An entrusting business operator may temporarily place a work in progress under its control in order to check it. If the parties have agreed in advance that receipt occurs when the entrusting business operator confirms that the work meets a certain standard, the day on which the work was placed under its control is not immediately treated as the date of receipt. However, if the work is under the entrusting business operator's control on the delivery date specified when the order was placed, the delivery date becomes the date of receipt, whether or not the check has been completed. This treatment is not permitted for manufacturing consignment or repair consignment.
Whether the Act applies depends on the combination of the content of the transaction and the capital and employee-number thresholds. At the clause design stage, check that the provisions on the inspection period and the payment due date stay within these rules. Reviewing the ordering company's internal practices is discussed in Complying with the Torihiki Tekiseika Act: Internal Practices Ordering Companies Should Review After It Took Effect.
When reviewing a contract, checking in order the link between the acceptance criteria and the attachments, the start of the inspection period and of deemed acceptance, the repair procedure and the maximum number of rounds, the connection with invoicing and the liability period, and the relationship with the rules of the Torihiki Tekiseika Act makes it easier to avoid omissions. Specific contract types are also discussed in Basics of Reviewing Software Development Agreements, How to Check Specifications and Acceptance Criteria in Manufacturing Supply Agreements and Checkpoints for Sales Agreements.