A German software company can hire offshore developers without Scheinselbstständigkeit (false self-employment) exposure by contracting a company rather than individuals, and by leaving the right to direct each engineer with that company. The contract title matters less than daily practice. If your managers set an offshore freelancer's hours, hand them tasks personally and add them to your org chart, the label "freelancer" will not protect you.
724SOFTWARE, a Vietnam IT company with 200+ professionals and delivery experience across 10+ countries, runs offshore dedicated teams from Vietnam, and this guide sets out how to keep the vendor in the employer role in practice as well as on paper. That match between paper and practice is what a German status review examines.
TL;DR
Scheinselbstständigkeit is judged on how the work actually runs, not on what the contract says.
Individual freelancers you contract directly carry the most risk. A team employed and managed by a vendor carries much less.
In the Dienstvertrag vs Werkvertrag choice, a Dienstvertrag usually fits ongoing team work. A Werkvertrag fits a defined deliverable.
Send requirements through the vendor's lead. Keep hours, time-off approval and performance reviews with the vendor.
Have German employment counsel review the setup before the first engineer starts.
About the Author
This guide comes from the delivery team at 724SOFTWARE, which runs dedicated teams and offshore development centres from Vietnam for clients in 10+ countries and holds a 95% client retention rate. It describes how we structure engagements for European buyers. It is not legal advice.
What is Scheinselbstständigkeit, and why does it matter for offshore hiring?
Scheinselbstständigkeit describes a person who is contracted as self-employed but works, in practice, as an employee. Section 7 of the German Social Code Book IV defines employment as non-independent work. Two features mark it: integration into a company's operations, and following the employer's instructions on time, place and manner of work.
If a review reclassifies the relationship, the company can owe social security contributions retroactively for several years. Where evasion was intentional, that can stretch to decades, and criminal charges are possible.
This matters offshore because many German teams start by contracting one or two remote freelancers directly. That setup looks most like employment. The freelancer joins your stand-ups, takes tickets from your managers and works your hours.
How a status review works: think of a customs inspection. The officer reads the shipping label, then opens the container. If the contents differ from the label, the contents decide. Your contract is the label. Your Jira history, Slack threads and calendar invites are the contents.
Why does an offshore dedicated team carry less risk than individual freelancers?
The safer structure, then, is one where the contents genuinely match the label. In an offshore dedicated team, the vendor employs, pays and line-manages the engineers. You contract with a company for a service. Comparisons of outsourcing companies and freelancers set out the differences in control, continuity and accountability between the two routes. Dedicated developers can still work exclusively on your product.
Factor | Direct freelancer | Employer of Record (EOR) | Offshore dedicated team
|
|---|---|---|---|
Who employs the engineer | Nobody (self-employed) | The EOR, on your behalf | The vendor |
Who directs daily work | Usually you | You | Vendor's lead, against your requirements |
Misclassification exposure | Highest | Low | Low when practice matches the contract |
Replacement if someone leaves | Your problem | Your problem | Vendor's responsibility |
An EOR suits companies that want remote employees without setting up a local entity. You still manage each person directly, though, so you take on the full line-management work of an employer.
Author's view: for a German software company that needs several engineers over an extended period, a dedicated team usually fits better than direct hiring because the vendor bears the employment liability and continuity risk.
Dienstvertrag vs Werkvertrag: which contract fits an offshore development team?
Once the structure is a team, the next decision is what the vendor owes you. That choice also shapes how the work should run. A Dienstvertrag is a service contract: the vendor owes qualified effort. A Werkvertrag is a contract for work: the vendor owes a defined, accepted result.
Dienstvertrag | Werkvertrag
| |
|---|---|---|
Vendor owes | Professional services | A specified deliverable |
Billing | Actual working hours | Milestones or acceptance |
Fits | Ongoing product development | A bounded component with acceptance criteria |
Main risk | Your managers drift into directing individuals | Scope disputes when requirements change |
Long-running product work changes weekly, so a Dienstvertrag that clearly states the team's responsibilities usually fits better. Either contract fails if your managers end up giving personal instructions to individual engineers. Define the role and the engagement model before you screen candidates. That step prevents the most common mismatch.
How do you avoid Scheinselbstständigkeit in daily collaboration?
With the contract signed, Scheinselbstständigkeit vermeiden becomes an operating habit. These checkpoints keep practice aligned with paper:
Name a vendor-side lead. Your product owner sets priorities and acceptance criteria. The vendor's tech lead or PM assigns tasks to individuals.
Keep HR decisions with the vendor. Working hours, time off, performance reviews and replacements are the vendor's decisions.
Mark accounts as external. Vendor engineers should not appear in your employee directory or org chart.
Pay the vendor, never individuals. Invoices cover the team's hours.
Write requirements for the team. A ticket addressed to the team and reviewed in sprint ceremonies reads differently from a direct message assigning personal work.
Plan onsite visits. If engineers travel to Germany to work, the German Posted Workers Act requires their foreign employer to guarantee core German labour standards. These include minimum wage, maximum working hours and paid annual leave.
Review once a year. Teams drift, so check that daily reality still matches the contract.
What should a German company check before choosing an IT outsourcing Vietnam partner?
None of these checkpoints work unless the vendor can actually carry the employer role. Before you sign with an IT outsourcing Vietnam provider, check the following:
Real employment. Ask who employs the engineers and who runs their reviews. A broker or freelancer marketplace pushes the risk back onto you.
Management depth. The seniority ratio and a named delivery lead matter more than headcount.
Data transfers. Confirm GDPR compliance and Standard Contractual Clauses for personal data. Vietnam has no EU adequacy decision.
Security and quality. ISO 27001 sets out how an organisation manages sensitive data, identifies risks and applies controls. ISO 9001 covers quality management. Ask how the vendor's alignment shows up in your project.
Billing you can audit. You should be able to match hours-based invoices against delivery.
Overlap and response. Confirm working hours that overlap with the German business day and a written incident response time.
Frequently Asked Questions
Can offshore freelancers create Scheinselbstständigkeit liability?
Yes, where German social security law applies. Cross-border cases also raise the question of which country's rules apply, so take legal advice.
Does a dedicated team remove the risk entirely?
No. It lowers exposure only while the vendor genuinely directs the engineers.
Is a Werkvertrag safer than a Dienstvertrag?
Not automatically. Both are judged on how the work actually runs.
Can our product owner speak with engineers directly?
Yes, about requirements and acceptance. Task allocation and HR matters stay with the vendor's lead.
Do we need a German entity?
No. In a dedicated team model, the vendor employs the engineers in its own country.
Must engineers speak German?
Usually not. Agree on the working language at the start.
About 724SOFTWARE
724SOFTWARE is a Vietnam-based company that builds web and mobile applications through dedicated teams, embedded staff augmentation and offshore development centres. Its 200+ professionals, 58% of them senior-level, deliver from Vietnam in English, Mandarin, Korean and Japanese. The company is GDPR compliant, aligned with ISO 9001 and ISO 27001:2022 standards, and bills on actual working hours. Teams scale from 1 to 50+ pre-vetted engineers in 2-4 weeks. A follow-the-sun model backs incident response in under 10 minutes. As a selected Anthropic partner, 724SOFTWARE trains its engineers to use Claude Code in daily delivery. It has no German entity and works with German clients from Vietnam as a long-term technology partner.
If you are planning your first offshore hires, bring your draft contract and working model to a conversation with the 724SOFTWARE team at https://724software.com.vn/.
