Contractor vs employee misclassification in India

The single most common shortcut foreign founders try, when hiring their first engineer in India, is to pay them as an “independent contractor” on a monthly invoice. It looks legally tidy from the US/UK side. From the Indian side, the label on the invoice isn't what controls. Under Indian law, classification turns on the substance of the relationship, not the contract label — a full-time, exclusive, embedded engineer is an employee in substance regardless of what the agreement says. That mismatch is where the liability sits.

The misclassification risk rarely arrives as a surprise tax raid — it usually surfaces in diligence. When an investor or acquirer looks closely, a reassessment can pull back-payment of PF, ESI, TDS, and gratuity, plus interest — and can open questions about IP ownership that contractor agreements were meant to settle.

What “substance over form” means here

Indian courts and tax authorities apply a multi-factor test that mirrors international practice. The label on the contract is the weakest signal. The factors that move the needle:

Control. Do you direct how the work is done, not just what gets done? Standups, sprints, code reviews, the right to assign tasks — all employee-shaped.
Exclusivity. Is the person working solely for you, full-time? Genuine contractors have multiple clients.
Integration. Are they part of your team — Slack, code reviews, planning sessions? Employees yes, contractors usually no.
Tools and infrastructure. Whose laptop, whose IDE licences, whose GitHub, whose meeting tools? Employee-shaped if all yours.
Duration and continuity. A continuous, indefinite engagement is employee-shaped. Project-by-project with discrete deliverables is contractor-shaped.
Risk and reward. Does the person carry business risk? Genuine contractors invoice for delivery and absorb cost overruns. Employees don't.

A senior engineer working 40 hours a week, attending your standups, committing to your monorepo, using your AWS, for an unbounded period — that's employment substance, no matter what the contract says.

The cost when it goes wrong

If the engagement is later recharacterized as employment, the exposure typically includes:

PF. Employer share (12% of basic + DA) for the entire engagement period, plus interest and damages.
ESI. Where applicable.
TDS. Recharacterised from contractor TDS (10% under 194J) to salary TDS (slab-based), with the foreign company on the hook for the difference and penalty.
Gratuity. If the engagement crossed 5 years.
IP. Contractor IP-assignment clauses are weaker than employment IP. A successful misclassification challenge can leave you with weaker IP than you thought.

An illustrative worked example. Take a senior engineer at ₹22 LPA on a full-time, exclusive, multi-year engagement. If that engagement were later recharacterized as employment, the exposure — backdated employer PF and ESI, gratuity accrual, plus interest — can land in the ₹6–10 lakh per engineer range, before legal fees. The exact figure depends on tenure, salary structure, and which contributions apply; treat this as a sizing example, not a forecast. In practice this surfaces when a buyer or investor runs diligence, not as an unprompted knock from the authorities.

When a contractor relationship is actually fine

Genuinely project-shaped work, with a real deliverable, a real timeline, a real other-client portfolio, paid by milestone or output, can be a contractor. A fractional CTO with three clients, paid on a defined scope. A specialist hired for a 3-month migration. That's contractor substance.

A full-time engineer working on your product is not.

What to do instead

Two clean structures:

Hire through an EOR. The engineer is legally employed in India by the EOR. PF, ESI, TDS, gratuity, and IP assignment all flow correctly. You sidestep misclassification entirely.
Set up your own Indian entity. Worth it past roughly 15–25 India FTEs. Below that, the ongoing compliance cost outweighs the savings.

The wrong-shaped middle option — a foreign company invoicing an Indian individual as a contractor — is where the liability lives. Don't do it for long-term hires.

This guide is general information, not legal or tax advice. Engage qualified counsel before acting.

Sources

Primary (government):

Employees' Provident Fund Organisation (EPFO) — official portal — EPF & Misc. Provisions Act, 1952; employee definition, 12% employer + employee contribution on basic + DA.
Employees' State Insurance Corporation (ESIC) — official portal — ESI Act; 3.25% employer contribution for employees earning ≤ ₹21,000/month.
Income Tax Department, Government of India — Income-tax Act, 1961 (Section 192 / 194J).

Supporting (law / advisory firms):

Already have contractors in India? Here's how we convert them →