In a Werkvertrag, Abnahme (§640 BGB) is the moment that changes the legal position of both parties. Remuneration falls due, the risk passes to the client, the limitation period for defect claims starts and the burden of proof for defects shifts. Agile software delivery does not fit naturally into a single acceptance at the end. The solution is not to abandon Abnahme, but to design it for increments: clear acceptance objects per sprint, measurable criteria, a defined review window and a classification of defects. This guide explains the statutory mechanics and translates them into a clause pattern.
Why acceptance design matters more now
More software is being built by external teams, and the contracts behind that work are under more strain. Bitkom counted 109,000 unfilled IT positions in Germany in 2025 and reported that an open IT role took an average of 7.7 months to fill. The 2026 figure fell to 79,000, but 78 percent of companies surveyed by Bitkom still report a shortage of IT specialists. Demand keeps rising at the same time: Bitkom expects German software revenue to grow 9.9 percent to EUR 58.1 billion in 2026, and 57 percent of German companies with 20 or more employees now use AI, up from 36 percent a year earlier.
When capacity has to come from outside, the contract takes over the role a line manager would otherwise play: it defines what "done" means. In a Werkvertrag that instrument is Abnahme. A clause that does not fit sprint delivery is either ignored in practice, which weakens your legal position, or it blocks payment and strains the relationship with the team you depend on.
What Abnahme does in German law
| Effect | Provision | Relevance for software |
|---|---|---|
| Duty to accept a work that conforms to the contract, no refusal for insignificant defects | §640 Abs. 1 BGB | Requires a shared definition of significant and insignificant defects |
| Deemed acceptance after a reasonable deadline unless refused with at least one defect | §640 Abs. 2 BGB | Prevents increments from remaining in limbo |
| Loss of certain defect rights for known defects unless reserved | §640 Abs. 3 BGB | Acceptance protocols should list known defects with a reservation |
| Remuneration falls due on acceptance, partial remuneration for partial acceptance | §641 Abs. 1 BGB | Enables payment per accepted sprint or milestone |
| Passing of risk | §644 BGB | Relevant for later regressions and data loss |
| Start of limitation period for defect claims | §634a Abs. 2 BGB | Each partial acceptance can start its own period |
Before acceptance, the contractor generally has to show that the work is free of defects. After acceptance, the client has to prove a defect. This shift alone explains why acceptance should be deliberate and documented.
The core design decision: real partial acceptance or progress check
Many agile contracts mention sprint reviews and acceptance without saying whether a sprint acceptance is a legal Teilabnahme with the effects above, or merely a technical review on the way to a final acceptance. Both models are legitimate. They need to be chosen explicitly.
- Real partial acceptance per increment. Each sprint increment is a separate acceptance object with its own criteria. Payment and limitation run per increment. Suitable where increments are usable and testable in isolation, for example a service, an interface or a feature behind a flag.
- Technical review plus final or milestone acceptance. Sprint reviews confirm progress and record feedback, without legal acceptance effects. Legal Abnahme takes place at defined milestones. Suitable where value only materialises once several increments are integrated.
A hybrid is common: technical reviews per sprint, legal partial acceptance per release or milestone.
Where acceptance only happens at milestones, the contractor's cash flow between acceptances becomes a question. §632a BGB allows instalment payments (Abschlagszahlungen) in the amount of the value of the services performed and owed under the contract. A fixed monthly instalment, offset at milestone acceptance, is a common way to combine Abnahme with predictable payment flows.
Defining the acceptance object
Acceptance can only be as precise as the Leistungsbeschreibung. For each acceptance object, the contract or the sprint document should name the deliverable, the acceptance criteria per user story, the non-functional requirements that apply (performance thresholds, security checks, test coverage targets if agreed), the environment in which acceptance tests run, and the documentation that belongs to the delivery. A Definition of Done is a useful team instrument, but it should be referenced in the contract as a criterion, not replace the acceptance criteria.
Defect classes
§640 Abs. 1 Satz 2 BGB prevents refusal for insignificant defects. Without a shared classification, every refusal becomes a dispute about significance. A three-level model is widely used:
- Class 1, critical: the deliverable or a core function cannot be used, or there is a security or data integrity issue. Acceptance may be refused.
- Class 2, significant: a function is materially impaired, a workaround is not reasonable. Acceptance may be refused.
- Class 3, minor: cosmetic or isolated issues with reasonable workaround. Acceptance is declared with a reservation, the defect is fixed within an agreed period.
Contractual classifications support the statutory standard. In standard terms (AGB), they are subject to review under §307 BGB, so they should be balanced.
Clause pattern (illustrative)
1. The contractor notifies the client in text form of the completion of each acceptance object defined in the sprint document. 2. The client tests the acceptance object against the agreed acceptance criteria within [x] working days in the agreed test environment. 3. The client declares acceptance in text form or refuses acceptance stating at least one defect of class 1 or 2. Defects of class 3 do not entitle the client to refuse acceptance and are recorded in the acceptance protocol with a reservation. 4. If the client neither accepts nor refuses within the period stating a class 1 or 2 defect, §640 Abs. 2 BGB applies. 5. Productive use of the acceptance object beyond testing purposes is deemed acceptance unless the client has refused acceptance in accordance with paragraph 3.
The number of days, the definition of the test environment and the handling of productive use need to match your release process. Clause 5 in particular should be reviewed carefully where the contract is based on standard terms.
Operational checklist
- Each sprint document lists acceptance objects and their criteria before the sprint starts.
- A named person on the client side is authorised to declare or refuse acceptance.
- The acceptance protocol records date, object, result, defects with class and reservations.
- Regression defects in previously accepted increments are handled as defect claims, not as new scope.
- Payment schedules reference accepted objects, not calendar months, in a Werkvertrag.
When a Dienstvertrag is the better fit
If acceptance criteria cannot be defined in advance, for example in research or exploration phases, forcing Abnahme into the contract creates disputes. A Dienstvertrag with reporting duties and review points is the more honest structure for those phases, and many engagements combine both over time.
This article is general information and does not constitute legal advice for your specific situation.
Acceptance works best when it is designed into the delivery rhythm from the first sprint rather than negotiated after the first dispute. That is why niogod™ structures its pods around a sprint-based Leistungsbeschreibung with acceptance criteria and Abnahme under §640 BGB where the scope allows it, and a Dienstvertrag where it does not, as outlined in the deployment protocol. If a sprint-based engagement is on your roadmap, it is worth agreeing the acceptance mechanics before the first line of code is written.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation