Many DACH companies start offshore engineering by contracting individual developers in India directly, often through platforms or referrals. The question that follows is usually framed as Scheinselbständigkeit: could these freelancers be reclassified as employees? The honest answer has two parts. German social security law is largely territorial, so the classic German consequences are much less likely while the person lives and works entirely in India. But the risk does not disappear. It shifts to foreign labour law, tax, intellectual property, data protection and the moment the freelancer starts working in Germany.

The numbers behind the question

Classification is not a theoretical risk in Germany. According to the federal government's answer to a parliamentary question in August 2025, the Deutsche Rentenversicherung carried out 23,052 status determination procedures in 2024. In the first half of 2025, a further 13,212 procedures followed; 5,146 ended with a finding of dependent employment and 7,706 with a finding of self-employment. Roughly two in five of those decisions therefore went against the self-employed label.

Enforcement is broad as well. German customs reported that the Finanzkontrolle Schwarzarbeit opened around 98,200 criminal proceedings across all sectors in 2025 and put the damage caused by undeclared work at about EUR 675 million. The demand side explains why direct freelancer contracts remain tempting regardless: Bitkom counted 109,000 unfilled IT positions in Germany in 2025, with an average vacancy of 7.7 months.

What Scheinselbständigkeit means in German law

§7 Abs. 1 SGB IV defines Beschäftigung as non-self-employed work, in particular in an employment relationship. Indicators are work under instructions and integration into the work organisation of the party giving instructions. If a nominal freelancer is in fact employed, the German client is treated as the employer, owes the total social security contribution (Gesamtsozialversicherungsbeitrag) retrospectively, and may face criminal exposure under §266a StGB for withheld contributions. These are the consequences most German managers associate with the term.

The territorial limit

§3 Nr. 1 SGB IV provides that the rules on compulsory insurance apply to persons employed or self-employed within the territory of the Code. A developer who lives in Bangalore, works from there and never performs work in Germany is generally outside the German compulsory insurance system, even if the relationship would qualify as employment by German criteria. The social security agreement between Germany and India covers pension insurance and regulates postings. It does not change this basic principle for locally resident freelancers.

This is the point at which many analyses stop. It is also the point at which the more relevant risks begin.

Where the risk actually sits

Risk areaTriggerWhat to check
Work in GermanyExtended on-site periods, relocation, regular visitsGerman social security and labour law may apply to work performed in Germany, residence and work permit requirements apply in addition
Applicable labour lawRelationship is in substance employmentUnder Art. 8 Rome I Regulation, a choice of law cannot deprive an employee of mandatory protection of the country where the work is habitually performed, which here points to Indian law
Indian labour and social security lawReclassification under Indian lawIndia's four Labour Codes took effect in November 2025. Obtain Indian legal advice on how direct engagements are assessed
Tax presence in IndiaIndividual acts for the German company in a way that could create a permanent establishmentReview with tax advisers under the Germany India double taxation agreement
Intellectual propertyNo effective written assignmentIndian copyright law requires written assignments and contains default rules on duration and territory
Data protectionFreelancer processes personal dataIndividual becomes a processor in a third country, requiring a DPA under Art. 28 DSGVO, a transfer tool under Art. 44 ff. DSGVO and credible technical and organisational measures

Why integration still matters

Even where German social security law does not apply, the factual pattern of the relationship matters for the other regimes. A freelancer who works full time for one client, uses the client's equipment and accounts, receives daily tasks from client managers and has no other customers will look like an employee under most legal systems. The same criteria that German authorities apply, instructions and integration, are reflected in the tests of many other jurisdictions. Designing the relationship as genuine independent service delivery reduces risk across all of them.

Signals of genuine independence

  • The freelancer has several clients or a realistic opportunity to have them.
  • Work is defined by deliverables, with acceptance and invoicing per deliverable or milestone.
  • The freelancer decides on working time, place and methods within the agreed scope.
  • The freelancer uses own equipment and carries own business costs.
  • The freelancer may use substitutes or subcontractors, subject to confidentiality and quality obligations.
  • No inclusion in the client's org chart, HR tools or internal team rituals as a member.

Operational risks that are not legal, but decisive

Individual engagements concentrate knowledge in single persons. Illness, a better offer or a visa move ends continuity without notice periods that protect the client. There is usually no second reviewer, no internal quality assurance and no structured knowledge transfer. Security commitments are hard to verify for a single person working from a personal laptop. For short, well-defined specialist tasks, these risks are acceptable. For core product development over 12 months or more, they often are not.

Decision framework

  1. Duration and centrality. Under three to six months and peripheral to the core product: individual freelancers can work. Long-running and core: consider a company structure with its own management layer.
  2. Personal data. If production personal data is involved, assess whether a single individual can meet Art. 28 and Art. 32 DSGVO requirements in a verifiable way.
  3. Germany exposure. If on-site work in Germany is planned, obtain German advice on social security, labour law and residence law before the first trip.
  4. Rights chain. Ensure a written assignment of rights that covers duration, territory and types of use explicitly.
  5. Indian law. For full-time, exclusive engagements, obtain Indian legal and tax advice before signing.

Whichever route you take, keep brief documentation: where the work is performed, how it is commissioned and accepted, and which trips to Germany are planned. Review it once a year, because in practice a short specialist task turns into a permanent full-time engagement surprisingly often.

The alternative structure

Contracting a company that employs its engineers locally, carries the employer obligations in India and delivers under a Werkvertrag or Dienstvertrag moves employer duties to the party that can actually fulfil them. It also introduces a management layer that can direct the team, which is what keeps the German side out of the employer role.

This article is general information and does not constitute legal or tax advice for your specific situation.

Moving the employer role to a company that can actually carry it is the structural answer to the freelancer question. niogod™ is built on that logic: engineers are employed in India, directed by the vendor's own German-speaking Projektleiter and deliver under a Werkvertrag or Dienstvertrag, as described in the pod structure. If you currently work with individual freelancers in India, reviewing the setup before you scale it is a conversation worth having early.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights