Whether you are a freelancer or an employee in Germany is not decided by your contract, your invoices or your Gewerbeanmeldung — it is decided by how the work is actually performed. If you work under instructions, embedded in the client’s organization, with no real entrepreneurial risk, you are legally an employee — with dismissal protection, paid vacation and sick pay — no matter what the „freelance agreement” says. This doctrine, Scheinselbstständigkeit (sham self-employment), is a serious liability problem for the company and, used well, a powerful lever for the worker — especially at the moment the client tries to end the contract. IT contractors and consultants are the highest-risk group we see.
The legal test: § 7 SGB IV
Employment for social-insurance purposes is „non-independent work, in particular in an employment relationship” — with the statute itself naming the two core indicators: working under instructions and integration into the work organization of the instructing party (§ 7 (1) SGB IV). The courts and the Deutsche Rentenversicherung weigh the overall picture (Gesamtbild) of the relationship, not any single factor and never the label. The recurring criteria:
Instructions (Weisungsgebundenheit)
- The client determines when you work (core hours, sprint schedules, mandatory meetings),
- where you work (office presence, on-site requirements), and
- how you work (methods, tooling, review and approval chains).
Integration (Eingliederung)
- Company email address, badge, hardware and system accounts,
- membership of a team with employees doing the same work,
- participation in standups, jour fixes, performance and staffing planning,
- vacation coordinated with — or approved by — the client.
No entrepreneurial risk
- Fixed monthly remuneration or a day rate paid for time, not for a work result,
- no own staff, no meaningful own capital or equipment, no own market presence,
- no realistic chance of profit or loss beyond „more hours, more money.”
One client
- Working essentially full-time for a single client over a long period is not itself decisive, but it colors every other factor — and it removes the strongest counter-argument a genuine entrepreneur has.
The Statusfeststellungsverfahren at DRV Bund
Either party — worker or client — can ask the Clearingstelle of the Deutsche Rentenversicherung Bund to determine the status bindingly (§ 7a SGB IV). Since the 2022 reform the procedure determines the employment status as such (Elementenfeststellung), can be initiated before the engagement even starts (Prognoseentscheidung), and can cover groups of identical contracts. Decisions typically take a few months; they bind the social-insurance carriers and are a strong (though not formally binding) signal for the labor courts.
Timing is strategic. An application during the running relationship changes the dynamics with the client immediately; one filed after the end is a common companion to employment-law claims. The application itself has no deadline — but the money claims it supports face limitation periods and sometimes short forfeiture clauses.
Consequences of misclassification
For the company: the expensive side
- Retroactive social contributions for up to four years (§ 25 SGB IV) — thirty years where intent is established. Crucially, the company owes both the employer and the employee share; it may recoup the employee share only by deduction from the next three salary payments (§ 28g SGB IV). Where the relationship is over, that means the company keeps essentially the entire bill — routinely 30–40% on top of everything it paid you, plus late-payment surcharges of 1% per month.
- Criminal exposure for withholding social contributions (§ 266a StGB) for the responsible managers in intent cases.
- Payroll tax liability and unwinding of VAT that should never have been invoiced.
For you: mostly upside
The worker’s financial downside is limited by design — the three-payroll recoupment cap protects you from the contribution back-bill. What you gain is the full employee toolkit, largely retroactively:
- Dismissal protection: the „termination of the freelance contract” is legally a dismissal — it needs written form (§ 623 BGB) and, in businesses over ten full-time equivalents after six months, a KSchG-recognized reason.
- Paid vacation — including payout of untaken days, often for several years back where you were never in a position to take „employee vacation” (see vacation entitlement),
- sick pay, parental-leave rights, working-time protection, overtime rules and statutory notice periods.
One honest caveat: in some constellations companies counter-claim the difference between the freelance fee and a comparable employee salary. These claw-back claims face high hurdles and limitation defenses, but they belong in the risk assessment before you escalate.
The strategic moment: when the client ends the contract
Sham self-employment claims have maximum force at contract end. The client believes it can terminate with an email and a notice clause from the framework agreement. If you are actually an employee, that termination is typically void twice over — no written-form dismissal, no KSchG ground. The play:
-
Build the status file
Collect evidence of instructions and integration: calendar invites to standups, the client email account, access badges, Jira/ticket assignments, vacation-approval threads, on-site requirements, the one-client revenue picture.
-
Treat the termination like a dismissal — deadline included
File a Kündigungsschutzklage at the labor court within three weeks of the termination, arguing employee status. Courts accept these „status” dismissal claims; missing the window forfeits the strongest lever.
-
Optionally trigger the DRV procedure
A parallel Statusfeststellungsverfahren raises the client’s contribution and criminal exposure — and therefore its settlement motivation.
-
Negotiate the package
Continued engagement, a proper employment contract, or a settlement pricing in dismissal-protection risk, vacation payout and notice-period pay.
Because the three-week rule of § 4 KSchG applies once you assert employee status, the safe course is always the precautionary Kündigungsschutzklage within the three-week deadline — the labor court can determine the status question within that case.
High-risk group: IT contractors and consultants
The pattern we see most: a developer, data engineer or consultant on a day rate, twelve months and counting at one client, embedded in a scrum team next to employees, client laptop and email, daily standups, sprint planning by the client’s product owner, vacation slotted around release dates. Every element of that sentence is a § 7 SGB IV criterion. Agencies and „contracting” intermediaries in the chain do not neutralize the analysis — they mostly add a second candidate respondent. If this describes your setup, you have a status case whether you ever intend to use it or not; the only question is when it is worth deploying.
Worked example
Priya, a UK national in Cologne, has worked 2.5 years as a „freelance” data engineer for one client: day rate €520, four days per week (≈ €9,000 per month invoiced), client laptop, standups at 9:15, vacation approved by the team lead, 100% of her revenue from this client. The client terminates the framework agreement by email with four weeks’ notice.
We file a Kündigungsschutzklage within three weeks, asserting employee status: the email termination is void for lack of written form, and no KSchG ground exists. The client’s exposure, roughly modeled: back contributions of 30–40% on ~€108,000 per year for up to four years (well over €100,000, essentially non-recoupable from Priya), payroll-tax risk, and salary accruing month by month while the „termination” is void. Settlement at the Gütetermin: €42,000 plus payout of 2.5 years of never-granted vacation (≈ €10,400) and an agreed clean end date — against an initial client position of „the contract simply expired.”
Frequently asked questions
My contract says I am an independent contractor. Doesn’t that settle it?
No. The label is close to irrelevant; the lived reality of instructions, integration and risk controls. German authorities and courts decide status against the contract wording wherever practice diverges from it.
Can I be forced to repay social contributions if I am reclassified?
Your exposure is narrow: the company can deduct your employee share only from the next three payments after reclassification (§ 28g SGB IV). Where the engagement has ended, there is usually nothing to deduct from. The bulk of the back-bill stays with the company — that asymmetry is deliberate.
Does having a GmbH or invoicing through an agency protect the client?
Not reliably. Courts look through structures to the actual work relationship. Intermediary chains can add complexity about who the „real” employer is — sometimes the agency, sometimes the end client under hidden-labor-leasing rules — but they rarely make a genuinely embedded worker independent.
I want to stay freelance — I earn more this way. Should I do anything?
A legitimate position — many contractors price the missing protections into their rates. Keep your own file (multiple clients, own equipment, result-based deliverables) so genuine independence is documentable if the DRV ever asks, and expect client pressure toward compliant setups.
Is there a deadline for invoking employee status?
For the status as such, no fixed deadline — but the claims built on it have clocks: three weeks for attacking a termination (§ 4 KSchG), limitation periods for wage-type claims, and four years back for contributions. The practical rule: the moment a termination or dispute appears, get the status assessed within days, not months.
Which court decides — civil or labor court?
If you assert employee status, the labor court (Arbeitsgericht) decides — including whether that status actually exists. For the worker this venue is favorable: no cost-shifting for lawyer fees at first instance and judges who apply the § 7 SGB IV criteria daily.