Hiring Freelance Developers in Germany: False Self-Employment

Short answer: In Germany a freelancer counts as an employee for social security if, in practice, they work under your instructions and are integrated into your organisation; that's the test in § 7 SGB IV, and what the contract calls them matters far less than how the work is done. If the authorities later decide a "freelance" developer was really employed (Scheinselbstständigkeit), the client can owe back social security contributions for up to four years, or thirty if the shortfall was intentional. The safest route for a long or close engagement is a status determination by the Deutsche Rentenversicherung's clearing office, which is free and can be requested before the work starts.

The legal test in plain English

§ 7(1) SGB IV defines employment as non-independent work, especially within an employment relationship, and names two indicators: working under instructions and integration into the client's work organisation. Everything else follows from those two ideas. The Deutsche Rentenversicherung (DRV) decides on "an overall assessment of all the circumstances of the individual case" (§ 7a(2) SGB IV), so there's no single box that makes someone safe.

For developers, the question usually comes down to: does this person behave like an outside business delivering a result, or like a team member who happens to send invoices?

Risk-signal checklist

Score your current or planned engagement. Several ticks in the left column means real risk.

Signals of employment	Signals of genuine freelancing
Fixed working hours set by you, joins daily stand-ups as a team member	Chooses own hours; attends meetings that relate to their deliverable
Takes tasks from your backlog like an employee, assigned by your lead	Contracted for a defined scope, milestone or feature
Paid by the hour or month regardless of outcome	Paid per deliverable or fixed price, with real risk if it overruns
Works on your laptop, with your company email and title	Uses own equipment and own business identity
Listed in your org chart, has a manager, takes holiday "approved" by you	No line manager; plans own availability
Works only for you, long-term	Several clients over the year, markets their services
No own staff, no own business presence	Has a website, company, sometimes subcontractors
Can't send someone else to do the work	Could deliver through another qualified person

None of these is decisive alone. A senior developer billing a day rate can still be genuinely self-employed. A fixed-price contract doesn't help if the person in reality sits in your sprint, reports to your CTO and works only for you for two years.

Why the client carries most of the risk

Back contributions. Under § 25 SGB IV, contribution claims become time-barred four years after the end of the calendar year in which they fell due, and thirty years if contributions were intentionally withheld.
The employee share mostly lands on you. § 28g SGB IV lets an employer recover the employee's share only by deducting it from pay, and a missed deduction can generally be made up only in the next three pay runs. For a past freelance relationship, that usually means the client pays both shares.
Criminal exposure. § 266a of the Criminal Code makes it an offence for an employer to withhold employees' social security contributions, punishable by a fine or up to five years' imprisonment. Prosecutions are aimed at deliberate cases, but the provision explains why advisers take this seriously.

A separate trap: the one-client freelancer

Even when someone is genuinely self-employed, § 2 sentence 1 no. 9 SGB VI makes self-employed people compulsorily insured in the state pension scheme if they don't regularly employ an insured employee and work, long-term and essentially, for only one client. That obligation sits with the freelancer, not you, but it's worth knowing when a developer tells you you're their only client.

The status determination procedure (Statusfeststellung)

§ 7a SGB IV lets the parties ask the DRV Bund to decide whether an engagement is employment or self-employment. The DRV's page on the procedure says:

It's run by the DRV Bund's clearing office (Clearingstelle)
It's free, and takes three months on average
It can be done before the work starts, which gives clarity early
You apply online with form V0027 and supply all agreements relating to the engagement: the contract, any description of the work, and an explanation of oral arrangements

Points in § 7a worth knowing:

Advance decision. On request the DRV decides before the work begins, based on the written agreements and the intended way the contract will be performed (§ 7a(4a)). If the arrangements change materially within the first month, you must tell the DRV.
Apply within one month. If the application is made within a month of the work starting and employment is found, the start of employment can be the date of the decision rather than the first day, provided the worker agrees and had their own health and pension cover in the meantime (§ 7a(5)).
Group opinions. Once the DRV has decided one case, the client can ask for an opinion on other engagements of the same kind (§ 7a(4b)).
Some of these rules are temporary. § 7a(7) says the advance-decision and group-opinion provisions, among others, expire at the end of 30 June 2027 unless extended. Check the current position if you're reading this after that date.

The DRV also offers an anonymous, non-binding online "Selbstcheck Erwerbsstatus" for a first impression.

A safer setup for freelance developers

Contract for outcomes. Describe deliverables, acceptance criteria and milestones, not hours and duties.
Let the freelancer run the how. You set requirements and review results; they decide method, tools and timing within the deadline.
Keep them visibly external. Their own equipment and email where possible, no internal job title, no place in the org chart.
Avoid permanent capacity contracts. "40 hours a week, open-ended" with one developer looks like a job.
Separate onboarding. Access to repositories and tools on a project basis, removed at the end.
Document reality, not just the paper. The DRV looks at how the contract is actually carried out.
Use the status check for long or close engagements. It costs time, not money.
Hire when it's really a job. If you need someone in your team every day for the foreseeable future, an employment contract (or an employer-of-record arrangement for someone abroad) is the honest structure.

This overview is general information, not legal or tax advice; a German employment lawyer or Steuerberater should look at any long-running engagement.

FAQ

Is a developer working from another EU country affected by German rules?

Which country's social security law applies depends on the EU coordination rules, not just on where the client sits. Get advice for cross-border set-ups.

Does using an agency instead of an individual remove the risk?

It changes the parties, but if the agency's developer in practice works under your instructions inside your team, similar questions can arise. Structure the agency contract around deliverables as well.

Can we ask for a status decision after the project has started?

Yes. It's usually better to apply within the first month, because of the start-date rule in § 7a(5).

Is a day rate automatically a red flag?

No. Payment method is one signal among many; instructions and integration carry more weight.

If you'd rather hand a project to an outside team that delivers against a defined scope, describe what you need built.