Werkvertrag vs. Dienstvertrag vs. Employee Leasing: German Contract Types Explained

External work in Germany runs through three legal paradigms: the work-result contract (Werkvertrag), the service contract (Dienstvertrag) and labor leasing (Arbeitnehmerüberlassung). Choosing deliberately, and living the choice, decides your compliance profile. An educational overview, not legal advice.

Elena Voss·Head of AI Delivery, Aiporate··8 min read·Share on XLinkedIn

Key takeaways

  • A Werkvertrag owes a result: the contractor promises a defined, acceptable work product and bears the risk of achieving it, including remedying defects. Payment is tied to acceptance of the result.
  • A Dienstvertrag owes effort: the provider promises careful work, not a guaranteed outcome, think advisory, ongoing development support, operations. The client pays for the activity, not for a warranted result.
  • Arbeitnehmerüberlassung owes labor capacity: a licensed lender's employee works under the client's direction, with the AÜG's licensing, duration and equal-treatment regime attached.
  • The single most important distinguishing question is who directs the work day to day. Direction by the client is the defining feature of leasing and the classic red flag inside a Werk- or Dienstvertrag.
  • German authorities and courts classify by lived reality, not the paper label. A Werkvertrag executed like leasing is treated as leasing, with all consequences. Choose the paradigm deliberately, then make daily practice match it.

Every external engagement in Germany, a freelancer building your data pipeline, an agency team extending your platform, a leased engineer filling a capacity gap, legally runs through one of three paradigms: the Werkvertrag (contract for a work result), the Dienstvertrag (contract for services) and Arbeitnehmerüberlassung (labor leasing, ANÜ). They look interchangeable on a purchase order and are anything but: they allocate risk, direction rights and compliance obligations completely differently, and picking the wrong one, or picking the right one and living the wrong one, is where most German staffing compliance problems begin. This article compares the three for business readers. It is an educational overview, not legal advice; classification of any real engagement should always involve your own legal counsel.

The three paradigms in one view

Werkvertrag (work result)Dienstvertrag (services)Arbeitnehmerüberlassung (leasing)
What is owedA defined, acceptable result (the 'Werk')Careful performance of an activityA worker's labor capacity under client direction
Who directs the workContractor organizes and directs itselfProvider directs its own peopleThe client, that is the point of leasing
Who bears delivery riskContractor: no acceptable result, no (full) payment; defects must be remediedClient: pays for effort even if the outcome disappointsClient: the lender owes a suitable worker, not a project outcome
Regulatory overlayGeneral civil law (BGB); misclassification risk if lived like leasingGeneral civil law (BGB); same misclassification riskAÜG: license, explicit labeling, maximum duration, equal pay/treatment
Typical IT use casesBounded builds: a migration, an integration, an MVP with acceptance criteriaOngoing advisory, staff-augmentation-style support, maintenance, SRE supportCapacity gaps where the client must direct the person like internal staff
Payment logicMilestones/fixed price tied to acceptanceTime-based or retainer, owed for the activityHourly/daily rate to the lender, who employs and pays the worker
Werkvertrag vs. Dienstvertrag vs. Arbeitnehmerüberlassung

Werkvertrag: buying a result

The Werkvertrag is the strongest risk transfer available: the contractor promises a concrete, verifiable result and does not earn full payment until the client accepts it. Defects are the contractor's problem to remedy. This paradigm fits engagements you can specify: migrate this system with these acceptance tests passing, deliver this integration against this interface contract, ship this MVP against this feature list. Its power is also its constraint: a Werkvertrag needs a genuinely definable work product and a real acceptance process. If the truth is that you want a good engineer working alongside your team on whatever the sprint brings, dressing that up as a Werkvertrag creates paper that contradicts practice, and in Germany the practice wins. A real Werkvertrag also means the contractor directs its own work: how the result is achieved, in what order, with which people, is the contractor's call within the agreed constraints.

Dienstvertrag: buying diligent effort

The Dienstvertrag is the paradigm for work whose outcome cannot honestly be guaranteed: consulting, ongoing development support, architecture advisory, operations. The provider owes careful, professional performance of the agreed activity, not a warranted result, and is paid for that activity. Most freelancer engagements in German IT are legally Dienstverträge (as so-called free service contracts with a self-employed party). The compliance edge here is different from the Werkvertrag: because no acceptance milestone anchors the engagement, the day-to-day working mode carries even more classification weight. A freelancer on a Dienstvertrag who remains self-directed, works toward an agreed scope and stays organizationally external is a clean configuration; one who is task-steered by the client's leads inside the client's sprint mechanics drifts toward disguised leasing or, if contracted directly as a solo freelancer, toward false self-employment. The Dienstvertrag label protects nothing by itself.

Arbeitnehmerüberlassung: buying directed capacity, openly

Labor leasing is the one paradigm where client-side direction is not a bug but the defining feature: the lender employs the worker, the client directs the work. In exchange, the AÜG attaches a regulatory regime, the lender needs a license, the contract must openly declare itself as leasing, assignments are subject to a statutory maximum duration (18 months by default, modifiable within limits by collective agreements), and the worker is entitled to equal treatment with comparable staff, with equal pay generally required after nine months at the latest. Leasing is the honest choice when you genuinely need to steer an external person like internal staff for a bounded period. It is more administratively demanding and, over time, economically converges toward the cost of an employee, which is precisely the legislative intent. What leasing is not: a fallback you can silently activate when your Werk- or Dienstvertrag turns out to be lived like leasing. Since the 2017 AÜG reform, disguised leasing is sanctioned even if the provider holds a license, because the arrangement was not declared openly.

Why lived reality beats the paper label

German classification doctrine has one consistent theme across false self-employment, disguised leasing and sham Werkverträge: substance over form. Authorities and courts examine how the engagement actually operates, who assigns tasks, who controls hours and absence, how integrated the external person is, who carries delivery risk in fact, and they will reclassify against the contract when practice contradicts it. This has a practical consequence that surprises many buyers: compliance is not a legal-department event at signing, it is an operating discipline for the entire engagement. The most common failure is not a badly drafted contract but a well-drafted one that nobody follows: the Werkvertrag whose acceptance process quietly stops being used, the Dienstvertrag freelancer who gets absorbed into the team's task board, the six-month capacity bridge that enters its third year. Periodic review of the lived engagement against the chosen paradigm, quarterly, or at every extension, is the cheapest compliance instrument available.

How to choose deliberately

  • Start from the honest answer to one question: who needs to direct this work day to day? If it is your managers, the clean options are leasing or employment, not a services label.
  • If you can specify an acceptable result, prefer the Werkvertrag: it transfers the most delivery risk and gives the clearest compliance profile, provided the acceptance discipline is real.
  • If you are buying expertise and ongoing effort without a guaranteeable outcome, use a Dienstvertrag and protect the provider's or freelancer's self-direction operationally, not just contractually.
  • If the engagement is long-term and integration is the point, consider whether the honest instrument is a permanent hire rather than any external construction.
  • Whatever you choose, write the operating model down (direction, communication paths, acceptance or review mechanics) and re-check the lived practice against it at fixed intervals, with your legal counsel involved in the setup and the borderline calls.

Frequently asked questions

Can one engagement mix elements of Werkvertrag and Dienstvertrag?

In practice engagements often contain both result-shaped and effort-shaped components, and frameworks with statements of work per component are common. The classification risk arises when the label and the lived mode diverge, so each component should be scoped honestly for what it is, ideally with counsel reviewing the structure.

Which of the three models is 'safest'?

None is categorically safest; each is safe when lived as designed and risky when not. A genuine Werkvertrag has the clearest risk transfer, a genuine Dienstvertrag the most flexibility, and open leasing the most regulatory overhead but also the most honesty when client direction is truly needed. The dangerous option is any label whose daily practice contradicts it.

Does agile collaboration automatically indicate leasing?

No, but it raises the design bar. Joint plannings, demos and reviews can be structured as coordination between client and contractor rather than direction of individuals, for example by steering through the backlog and acceptance rather than assigning tasks to the provider's people. How this is set up in daily tooling matters, and borderline setups deserve legal review.

Who decides the classification in the end?

In a dispute or audit: the authorities and courts, based on the overall picture of the lived engagement, contract text included but not decisive. That is why the practical advice across all three paradigms is the same: choose deliberately, document the operating model, live it, and review it periodically with counsel.

Head of AI Delivery, Aiporate

Elena has spent 12 years building and embedding AI and data teams inside B2B SaaS companies, from first pilot to enterprise-wide platform. At Aiporate she leads how forward-deployed talent is matched, onboarded and shipped to production.

Need the team to make this real?

Describe your need in plain English, get the exact hire, forward-deployed talent or a fractional leader, vetted and matched in 72 hours.

Scope your need →

Keep reading

The Weekly Brief

Intelligence for building AI-native organizations.

One email a week: the sharpest thinking on AI hiring, infrastructure, teams and strategy, for the people building the future of work.

Join operators, founders and CTOs. No spam, unsubscribe anytime.