If you're one of the 9,000+ HR professionals on this list, there's a good chance you've either lived this or watched a colleague live it: a global company — usually US, UK, or EU-headquartered — wants to hire someone in India. Setting up a legal entity here is slow and expensive, so instead they offer a "contractor" agreement. Fixed monthly retainer. Fixed hours. A company laptop. A seat in daily standups. A manager who assigns and reviews the work like any other employee.
On paper, it's a contractor relationship. In practice, under Indian law, it very often isn't — and the gap between the two is where real financial and legal exposure sits, for the employer and sometimes for the "contractor" too.
Why foreign employers default to this
Setting up an Indian entity means registering under the Companies Act, handling GST, and running statutory payroll compliance — Provident Fund (EPFO), Employee State Insurance (ESI), gratuity, and state-level Shops & Establishments Act registrations. For a company hiring one or two people in India, that overhead can look disproportionate. Hiring "on contract" looks like the fast, low-friction option.
The problem is that Indian labour law doesn't care what the agreement is titled. It looks at how the relationship actually functions.
What actually determines classification
Indian courts and labour authorities apply a substance-over-form test, built around a few consistent questions:
Control — Does the company dictate hours, tools, and how the work gets done, not just what gets delivered?
Exclusivity — Is this person's time effectively committed to one company, with no real capacity to serve other clients?
Integration — Are they embedded in the company's team structure — reporting lines, internal tools, company email, standups — rather than engaged for a defined, bounded piece of work?
Duration and continuity — Is this an ongoing, indefinite arrangement rather than a project with a natural end?
Answer "yes" to most of these, and the relationship looks like employment, regardless of what the contract calls it.
What breaks when it's wrong
Misclassification in India isn't a paperwork technicality — it creates concrete liability:
EPFO and ESI exposure. If the relationship is reclassified as employment, the employer can be liable for retroactive Provident Fund and ESI contributions — plus interest and penalties — going back to when the relationship actually started functioning as employment, not from when anyone noticed.
Shops & Establishments Act and Payment of Wages Act exposure. These state-level laws govern working hours, leave, and termination protections for employees. A reclassified "contractor" can claim entitlements under these laws retroactively, including notice pay and statutory leave encashment.
India's new Labour Codes. As the four consolidated Labour Codes roll out across states, definitions of "employee" and "worker" are tightening, and the compliance and wage-definition requirements around them are becoming more codified — narrowing the room foreign employers have historically used to justify a contractor label.
The FEMA/RBI angle most foreign employers miss. Payments to a genuine contractor are treated as a service export and typically flow in as a standard foreign remittance against an invoice. Payments that function like salary but get routed the same way can raise questions under FEMA's foreign exchange reporting rules — a wrinkle that's specific to cross-border engagements and rarely shows up in generic classification guidance written for domestic markets.
For the person on the other side of this — the Indian professional signing the contractor agreement — misclassification isn't abstract either. It usually means no PF contribution building toward retirement, no ESI health coverage, no statutory leave, and no severance protection if the engagement ends abruptly. It's worth knowing what you're not getting before you accept "contractor" as the default.
A practical checklist before you sign — on either side
Before structuring or accepting a "contractor" role with a foreign employer, it's worth asking:
Am I (or is this person) free to take on other clients, or is this effectively full-time and exclusive?
Is work assigned and reviewed the way a manager would direct an employee, or delivered against a defined scope?
Is this engagement open-ended, or tied to a specific project with a natural end date?
Is the person using company-issued equipment and integrated into internal systems, or operating independently?
If most of the answers point toward "employee," the safer and more compliant path — for the company and the individual — is usually an Employer of Record (EOR) arrangement rather than a contractor agreement. An EOR employs the person locally on the company's behalf, handling PF, ESI, statutory leave, and termination compliance correctly from day one, without the company needing to set up its own Indian entity.
Deel's Employer of Record product handles India-specific statutory compliance — PF, ESI, and local labour law — on the employer's behalf.
This is exactly the gap Deel's EOR product is built for: it lets a foreign company hire someone in India as a properly compliant employee — PF, ESI, gratuity, and statutory leave all handled — without the company standing up its own Indian legal entity.
This post contains affiliate links. We may earn a commission at no extra cost to you.