EOR vs PEO in India: The Legal Difference That Decides It

EOR vs PEO in India is not really a product comparison. It is a question about who Indian law will treat as the single legal employer of the person you are hiring, and India answers that question differently from the United States.

We have run India hiring for foreign companies for years, and the same call repeats. A US buyer asks for a PEO because that is the word their last three vendors used. What they can actually have depends on one fact, and it is a fact they usually have not been asked about: whether they hold an Indian entity today.

This guide works through what Indian law recognizes, what it requires instead, and which of the two models your own situation allows.

What is the difference between an EOR and a PEO in India?

An EOR in India is the single legal employer of your worker through its own Indian entity, so you hire without incorporating. A PEO in India works alongside an Indian entity you already hold, handling payroll and HR operations while you stay the legal employer. The dividing line is entity ownership, not service scope.

Who is the legal employer under each model

Under an EOR, the provider's Indian entity signs the employment contract, runs the payroll, holds the statutory registrations and appears on every filing the authorities see. The person works on your team every day, attends your standups and reports to your manager, and the provider is still the employer in law.

Under a PEO, nothing changes about who employs the worker. Your Indian entity signed the contract, your entity is named on the provident fund (PF, India's mandatory retirement savings scheme) and employee state insurance (ESI, the state medical and cash benefit scheme) registrations, and the provider sits behind you running the process. That single difference decides every other row in the table below.

What each model requires from you before you can hire

An EOR requires no Indian incorporation at all. The provider's entity already exists and its registrations are already live, so a first hire does not wait on a company formation you have not started. If the term itself is new to you, our glossary entry on the Employer of Record model covers the mechanics.

A PEO requires the entity first, and that is a longer list than most buyers expect: incorporation, a permanent account number and a tax deduction account number, PF and ESI registration once headcount thresholds are met, professional tax registration in every state where you have people, and a bank account that can actually run an Indian payroll. Until those exist there is nothing for a PEO to operate, which is why we point companies at employer of record services in India when the entity is still a plan.

Why does the US PEO co-employment model not work the same way in India?

In the United States, a PEO and its client share the employer role under an industry arrangement called co-employment, and the client stays the legal employer. India's framework contemplates a single legal employer for each worker and never defines co-employment in statute, so that shared split has nothing in Indian law to attach to.

What co-employment means in US practice

Co-employment in the US is a contractual arrangement, not a court finding. The client and the PEO each hold part of the employer role at the same time, the client keeps direction of the work, and the PEO takes on defined payroll and benefits responsibilities. It is designed, signed and documented in advance.

We treat that concept in full, including the federal tax position and the reason it does not transfer, in our guide to how the two models compare outside India. This section only needs the shape of it.

Why the same split does not travel to India

Indian statute has no clause under which two organizations each hold part of the employer role. Neither term appears in the definition clauses of the Labour Codes, so there is no status for a contract to claim and no registration that would record it. A tribunal asked to settle a dispute will name an employer, and it will name one. Our definition of co-employment sets out the term itself.

This is why we stop US buyers who ask us to set up a co-employment structure in India. Not because the request is objectionable, but because there is no Indian container to put it in, and paperwork that pretends otherwise is exactly the paperwork that gets tested later.

How do Indian courts decide who the legal employer is?

Indian courts do not look at the label on the contract. They apply control based tests: who pays the wages, who holds the power to dismiss or discipline, and who directs and controls how the work is done. Those three questions decide the employer, and they are why a PEO style split does not survive contact with an Indian tribunal.

The three control tests Indian courts apply

• Who pays the salary: the party whose funds reach the employee, and whose name sits on the payslip and the statutory filings.
• Who can dismiss or discipline: the party holding the power to end the employment, or to impose consequences short of ending it.
• Who directs and controls the work: the party deciding what gets done, how, and to what standard.

Foreign buyers assume the third test is decisive, because in most of their home jurisdictions direction of the work is close to the whole question. In India it is not, and that single point is the most useful thing on this page for anyone structuring an India team. Our overview of labor and employment law in India sets out the wider framework these tests sit inside.

What IAAI (2009) held about direction and control

In IAAI v. International Air Cargo Workers' Union, decided in 2009, the Supreme Court set out those tests and then drew the line that matters here. Direction and control by the principal employer does not by itself create employment, provided the contractor pays the salary and holds the right to regulate the employment.

For a US company that reads backwards. You can give day to day direction to someone whose legal employer is a third party without becoming their employer, as long as the other two tests point away from you. The four Labour Codes, in force since November 21, 2025, did not disturb the holding. The full case treatment sits in our deep dive on co-employment vs joint employment.

What SAIL (2001) left open about sham arrangements

SAIL v. National Union Water Front Workers, a Constitution Bench decision from 2001, is quoted loosely more often than it is read. It is about absorption, not about sharing liability, and it held there is no automatic absorption of contract labour by the principal employer.

What it left open is the part that should shape your paperwork. Where an arrangement is a sham, nominal or a camouflage, the workers are direct employees of the principal employer. That is the argument a mislabeled structure walks into, and it is why we spend time on contract wording a client assumes is boilerplate.

What does India require of a principal employer instead of a second employer?

Where a second organization is involved through a contract labour arrangement, India attaches specific secondary duties to the principal employer rather than making it an employer. Under the Occupational Safety, Health and Working Conditions Code, 2020, unpaid wages sit at section 55 and welfare facilities at section 53. India names duties, not a second employer.

The OSH Code is one of the four Codes, and it is where India's contract labour machinery now lives. Final central rules were notified on May 8, 2026, and state rules are still being issued unevenly as of August 2026, so the central position is settled while specifics vary with the states your people sit in. Our guide to the new labour codes in India tracks what changed.

Unpaid wages under section 55 of the OSH Code

Section 55 makes the contractor responsible for paying wages by bank or electronic transfer. If the contractor fails to pay within the prescribed period, or makes a short payment, the principal employer pays in full or pays the unpaid balance, and can then recover that amount by deduction or as a debt. Underpayment triggers it, not only non-payment, which is the part buyers miss when they assume a partial run is somebody else's problem.

Read the shape of that carefully. It is a payment obligation with a recovery right attached. It is not a declaration that the principal employer was the workers' employer all along, and the recovery right is the tell.

Welfare facilities under section 53

Section 53 places welfare facilities for contract workers on the principal employer, read with the facilities the Code specifies elsewhere. The duty is specific and enumerated, and it stops where the enumeration stops.

Neither section converts the principal employer into the employer of the contractor's workers. They allocate named responsibilities to a named party, which is a different legal move entirely.

Core-activity contract labour under section 57

Section 57(1) prohibits contract labour in an establishment's core activities, subject to a three limb proviso that carves out defined exceptions. Where it is disputed whether an activity is core, a designated authority advises and reports to the appropriate Government, and the appropriate Government makes the decision.

That allocation matters more than it looks. Whether an activity counts as core is settled by government, not by an expert body acting on its own, so it is a determination your arrangement is subject to rather than one you can negotiate with an assessor. Section 54 of the same Code addresses the effect of employing contract labour from a non-licensed contractor. Our explainer on the four Labour Codes covers how the Codes fit together.

Why these are duties, not a second employer

Put the three sections together and you have India's actual answer to the problem US law solves with joint employer doctrine. India names principal-employer duties and attaches them to a named party. It does not create a second employer, and it does not split the employer role between two organizations.

So when a provider tells you both companies will share liability in India, ask which provision they mean. There is a real and specific answer for wages and for welfare. There is no answer at all for a shared employer status, because no provision creates one.

Does that mean a PEO in India is illegal?

No. The accurate claim is that co-employment is not a statutory category in India, which is not the same as illegal and not the same as impossible. Most published guidance on this topic overstates it, and that overstatement is what leads buyers to the wrong conclusion about what they can and cannot do in India.

We hold this line even though the looser version would help us commercially. A buyer who believes the model is banned outright moves to an EOR faster. It is still the wrong reason to move, and a buyer who later reads the real position stops trusting everything else we told them.

What the absence of a statutory category actually means

It means there is no defined status to claim, no registration that would record it, and no provision a contract can point to. It does not mean an enforcement authority is looking for two-party service arrangements to act against. It means that if the arrangement is ever tested, the test will be the control questions above, and the answer will name one party.

That distinction changes what you should be worried about. The risk is not a penalty for choosing a model. The risk is a finding that the model was never what the paperwork said it was, which is a different problem with a different fix. Our article on whether EOR is legal in India works through the statutory basis in more depth.

What would actually make an arrangement unlawful

Specific failures do carry consequences: not depositing provident fund contributions or tax deducted at source, breaching state level registration requirements, using contract labour in a core activity outside the exceptions, or running a structure a tribunal finds to be a camouflage. Each of those is a defined failure with a defined consequence attached.

None of them is "you used a PEO". That is the boundary, and holding it is the difference between advice you can act on and marketing that frightens you into the right answer for the wrong reason.

When is a genuine PEO arrangement possible in India?

When you already hold your own Indian entity. A provider can then run payroll, statutory filings, benefits administration and day to day HR operations under your entity while you remain the legal employer. That is HR and payroll outsourcing, it is a real and workable PEO relationship, and it is simply not US-style co-employment.

What a PEO relationship looks like under your own Indian entity

The provider runs the monthly cycle on your entity's numbers, files PF, ESI, tax deducted at source and professional tax under your registrations, administers benefits and insurance, handles onboarding and offboarding paperwork, and gives your people somewhere to take an HR question.

None of it touches the employment relationship itself. It is payroll in India and HR operations delivered as a service, which is an ordinary arrangement and a good one once your entity is real and your headcount justifies the overhead.

What it costs, which headcounts it suits, and where it beats running the work in house are all set out on our PEO services in India page, so this article does not restate them.

If you want the operational walkthrough instead, our guide to hiring through a PEO in India covers onboarding, the monthly cycle and the handover points.

What stays with you as the legal employer

Everything that defines the role. The employment contracts are yours. The dismissal decision is yours. The statutory registrations sit with your entity, so a missed filing is your entity's default even where the provider caused it, and a service agreement can shift the cost of that but not the duty behind it.

That is the honest trade, and we say it on every PEO scoping call. The arrangement removes work. It does not remove employer liability, and a provider suggesting otherwise is describing a model India does not have.

How do you choose between an EOR and a PEO in India?

One question decides it. If you do not hold an Indian entity, you need an Employer of Record, whatever the provider calls the product, because someone has to be the single legal employer. If you do hold an Indian entity, a PEO arrangement is available and the choice becomes a scope question rather than a legal one.

EOR vs PEO in India is therefore a status question before it is a comparison. We ask two things on a first call: do you have an Indian entity today, and are you incorporating in the next six months. Almost everything else follows from those two answers.

If you do not hold an Indian entity

You need a provider that becomes the legal employer, and the product name on the invoice does not change that. If the provider's Indian entity signs the contract, pays the salary and holds the registrations, the arrangement is an EOR and it should be documented as one. Our guide to hiring employees in India without an entity covers how that runs in practice.

The comparison worth your time at this point is not EOR against PEO. It is EOR against incorporating, and it turns on headcount and how long you plan to stay. Our EOR vs entity calculator gives you the crossover point for your own numbers.

We work the same question through qualitatively in EOR vs setting up an entity in India, including the things a cost model tends to miss, such as who carries the wind-down if the market does not work out.

If you already hold an Indian entity

Your choice is genuinely open, and it is about scope rather than legality. If you want your entity to run its own employment and simply buy the operations behind it, a PEO arrangement fits. If you want some hiring kept off your own books, in a state where you are not registered or for a short-term team, an EOR can run alongside your entity for those people. We compare the direct route in EOR vs direct hiring in India.

Model the cost both ways before you commit, because the answer moves with headcount and with how many states you are in. Our employee cost calculator gives you the loaded cost of an Indian employee under your own entity, which is the number a per-employee service fee has to be compared against.

What to ask a provider before you sign

• Which entity signs the employment contract: the answer names the legal employer, and everything else in the arrangement follows from it.
• Whose registrations carry the filings: PF, ESI, tax deducted at source and professional tax sit with one entity, never split across two.
• Who holds the power to dismiss: if the provider cannot, the provider is not the employer, whatever the contract recites.
• What happens if a filing is missed: ask who the authority proceeds against, not who reimburses the penalty afterwards.
• Does this product need our own entity: the answer separates a PEO offering from an EOR offering in a single sentence.

If a provider answers "no entity needed" while calling the product a PEO, they are selling you an EOR under the wrong name. It is not necessarily a bad product. It is a product sold under a label that will not survive the first time somebody checks.

What goes wrong when the model is labeled incorrectly?

A mislabeled arrangement does not fail on the paperwork, it fails on the facts. If a tribunal applies the control tests and finds that the contract does not match reality, the exposure is a misclassification finding, the sham arrangement argument SAIL left open, and permanent establishment risk for the foreign parent that believed it was at arm's length.

Misclassification and reclassification exposure

A reclassification finding is retrospective. It reaches back across the whole period the arrangement ran, and the exposure is unpaid statutory contributions, interest and penalties, plus whatever employment entitlements attach to that period. Our breakdown of employee misclassification penalties in India sets out what that looks like in practice.

We run a structural check with clients before anyone signs anything, because the least expensive version of this conversation happens before the first hire rather than after the twentieth. Our misclassification check is the short version of it.

Permanent establishment risk for the foreign parent

Permanent establishment is the risk with no US analogue, and it lands on the parent company rather than on the arrangement. If the facts suggest your foreign company is carrying on business in India through people who are effectively yours, the question becomes whether India can tax a share of your profits. Our glossary entry on permanent establishment risk defines the term.

A properly structured EOR keeps that distance, because the provider's entity employs the people and carries the operations. A mislabeled structure does the reverse: it puts your name on the direction, on the dismissal, and sometimes on the payment, which is close to the fact pattern the analysis is looking for. We go through it in detail in permanent establishment risk in India.

If you are not sure where your current setup sits, our permanent establishment risk quiz will place it in a few minutes.

The sham and camouflage argument

This is the one that catches structures nobody thought were aggressive. The argument is not that you broke a rule. It is that the arrangement was never real, and it succeeds on evidence rather than on intent, which means good faith is not a defense to it.

The evidence is ordinary business material. Who interviewed and selected the person, whose systems they work in, who approves their leave, who ran their appraisal, who decided on the exit. When all of that points at the client and only the contract points at the provider, it is the contract that gives way.

How can Wisemonk help you hire in India under either model?

Wisemonk is an India-native Employer of Record (EOR) that helps global companies hire, pay, and manage talent in India without setting up a local entity.

If you do not hold an Indian entity, that means named hires working on your team within weeks, on compliant Indian employment contracts, without registering a company in India first.

We also run a separate Wisemonk PEO service for companies that already hold their own Indian entity. It covers payroll runs, statutory filings, benefits administration, onboarding and HR support, on a custom, scope-based quote.

We support 300+ global clients and more than 2,000 employees across India, process $20M+ in annual payroll, and hold a 4.8/5 rating on G2. Pricing starts from $99 per employee per month as of August 2026.

Here is how we help:

• Recruitment: sourcing, screening and closing candidates in India, whichever entity ends up employing them.
• Managed payroll: the monthly cycle with PF, ESI, tax deducted at source and professional tax filed on time, plus equipment procurement, delivery, tracking and returns.
• Background checks: pre-hire verification run before the contract is signed rather than after the first month.
• Contractor management: Contractor of Record cover for teams running contractors alongside employees.
• Entity setup: company registration in India, for companies that decide the PEO route is right and need the entity to exist first.

From our experience structuring India hiring for foreign companies, what decides these arrangements is never the contract wording, it is whether you can name the person who approved the leave and signed off the exit once the first dispute arrives.