In Germany, if a freelance developer is in practice an employee, the client owes the social security contributions, and under §25 SGB IV the claim runs back four years after the end of the year the contributions fell due. The contract label doesn't decide it. Either side can ask the pension insurer (Deutsche Rentenversicherung, DRV) for a binding status decision, which took 82 days on average in 2024 in the optional procedure, according to a government answer to the Bundestag.
This is general information, not legal advice. Take your own case to a German adviser. It's one of the questions in our EU engineering hiring compliance: contracts, IP and GDPR guides, and the wider European legal checklist has a shorter Germany section that this article deepens.
What Scheinselbständigkeit means for a client of freelance developers
Scheinselbständigkeit is the German word for false self-employment: someone invoicing as a freelancer who works like an employee. There's no statute by that name. The law is §7 SGB IV, which defines employment as non-self-employed work and names two indicators: work under instructions, and integration into the instruction-giver's work organisation.
So the question for a client is simple to state and hard to answer: does this developer, in practice, work under your direction and inside your organisation?
Does it reach a company with no German entity? How contributions are enforced against a foreign client with no German presence is something we don't have a primary source for, so we won't guess. It's the first question to put to a German adviser.
How a status is decided in practice
The DRV looks at the concrete case. Contract wording is evidence, not the answer.
The best-known court example is the Herrenberg case. In its judgment of 28 June 2022 (B 12 R 3/20 R), the Federal Social Court (BSG) looked at a piano teacher at a municipal music school paid on fee contracts (Honorarverträge). It found employment: the teacher was integrated into the school's organisation and had no entrepreneurial scope. That the parties meant the arrangement as freelance didn't exclude employment.
What carries over to software work is the test: instructions, integration, entrepreneurial risk. What doesn't is anything teaching-specific. We found no BSG judgment setting a rule for software developers. The case above concerns a teacher, so anyone telling you the courts have settled how agile development is classified is ahead of the sources.
Here's our judgment, not a checklist from the DRV. Picture a developer who joins your daily stand-ups, takes tickets assigned by your engineering manager, works on your laptop with a company email address, keeps set hours, and has no other client. That points toward employment on the §7 indicators, whatever the invoice says. A developer who delivers a scoped module, picks their own hours and tools, carries the risk of rework and serves several clients looks different.
You'll also hear thresholds, such as one client providing five-sixths or 80% of income. Those are advisers' rules of thumb. They aren't in §7.
Who pays if the DRV reclassifies the engagement
The client, mostly. The statute is specific.
| Question | What the source says |
|---|---|
| Who pays the contributions? | The employer pays the total contribution (§28e SGB IV) |
| How far back can claims go? | Four years after the end of the calendar year they fell due; 30 years if intentionally withheld (§25(1) SGB IV) |
The statute says four years, counted from the end of the calendar year, so the practical reach can approach five years for the earliest months.
We don't state surcharge rates or penalty amounts because we found no primary source for them.
The Statusfeststellungsverfahren: asking the DRV before you start
The Statusfeststellungsverfahren is the status determination procedure. Under §7a SGB IV, the parties apply in writing or electronically to DRV Bund (the Clearingstelle). Either party can apply alone. It isn't available once a health fund or a pension-insurer audit has already started a status procedure.
The rules that matter to a client:
- If you apply within one month of starting work and the DRV finds employment, employment starts on the day the decision is announced, provided the worker agrees and has their own health and old-age cover meanwhile (§7a(5)).
- The total contribution falls due only once a finding of employment is unappealable (§7a(5)).
- Objection and lawsuit against DRV Bund decisions have suspensive effect (§7a(6)).
- Since 1 April 2022 the procedure decides status only, not insurance duty (government answer, Drucksache 21/1059).
The numbers come from the Bundestag government answer cited in the lead (Drucksache 21/1059, 24 July 2025). In 2024 the DRV made 23,052 status decisions in the optional procedure: 9,397 found employment and 13,057 found self-employment. The two outcomes don't sum to the total because some procedures end without a finding either way. Processing took 82 days on average in 2024 (33 days in the obligatory procedure). Of 3,002 objections, 669 succeeded fully or partly. The DRV doesn't break outcomes down by occupation or sector, so there's no developer-specific hit rate to quote.
One caution: a decision settles status for that engagement, if the real working practice matches what was assessed. It isn't a general certificate for the developer.
Your options, compared
| Option | What it settles | What stays open |
|---|---|---|
| Freelancer, contract written to match real working practice, no application | Nothing formally; practice is the evidence | Full exposure if the DRV later finds employment on the §7 indicators |
| Freelancer plus a voluntary §7a application before start | A binding status finding for that engagement; the optional procedure averaged 82 days in 2024 (the government answer gives no timing data for the separate prognosis decision, a forward-looking status assessment before work starts) | Wait time before the work starts, and the result may be employment |
| Employ directly | You are the employer by definition; the freelance question disappears | Full German employer obligations; ask an adviser |
| Intermediary or employer of record (EOR) | Changes who the contracting employer is | How German authorities treat the arrangement and how contributions are enforced; ask an adviser |
We have no German EOR facts or pricing from a source we trust, so the last row says only what the arrangement does in principle. For the contract itself, the contract clauses that sit alongside status cover what an agreement should and shouldn't say about how the work is organised. A clause can't make practice match.
Hiring from other countries raises the same question under different law. The Dutch equivalent has its own enforcement dates, and the UK tax-status question turns on residence and place of work. Neither answer transfers to Germany.
Why not to wait for a reform
The status procedure may change, but we don't describe any proposed changes because none has been published as law. A draft is not law, and a German adviser can tell you what stands now.
The takeaway doesn't depend on any reform. The §7 test applies today, and contributions that fall due now can be claimed for four years.
What this means for your engineering plan
One way to start is an inventory. List every freelancer you engage who lives or works in Germany and compare their real working practice with the §7 indicators: who assigns the work, whose tools and hours, how many other clients. That's a judgment call for your team and your adviser, not a DRV checklist.
For long engagements, one option is to apply under §7a before the work starts, with the timing caveats above. If client-controlled tooling, schedules and stand-ups are deliberate, compare the employment route.
The foreign-client enforcement question is worth putting to a German adviser before signing. If finance owns the contractor budget line, they'll want the four-year look-back. For the headcount side, see whether contractors count against headcount.
FAQ
Is false self-employment illegal in Germany?
The label itself isn't an offence. The consequence is contribution claims against the client. Whether anything beyond that applies to you is for counsel to say.
Who is liable, the client or the freelancer?
Under §28e SGB IV the employer pays the total contribution, so the client carries the main exposure. Whether and how the freelancer is separately affected isn't covered by the sources we used, so ask an adviser.
How long can the DRV go back?
Four years after the end of the calendar year in which the contributions fell due, under §25(1) SGB IV. If contributions were intentionally withheld, the period is 30 years.
How long does a status decision take?
In 2024 the optional procedure took 82 days on average, according to a Bundestag government answer. The obligatory procedure took 33 days. The DRV doesn't publish a figure for software developers specifically.
Is this the same as US worker misclassification?
No. Different legal systems. German status turns on §7 SGB IV: instructions and integration into the client's organisation. A US classification doesn't settle German status, and the reverse holds too.
Sources
- Gesetze im Internet: §7 SGB IV, Beschäftigung
- Gesetze im Internet: §7a SGB IV, Anfrageverfahren
- Gesetze im Internet: §25 SGB IV, Verjährung der Ansprüche
- Gesetze im Internet: §28e SGB IV, Zahlungspflicht, Vorschusspflicht
- Deutscher Bundestag: Drucksache 21/1059, government answer of 24 July 2025
- Bundessozialgericht: judgment of 28 June 2022, B 12 R 3/20 R