Co-Employment vs Joint Employment in India Explained

Co-employment and joint employment are US legal concepts, and neither one is a statutory category in India. That single fact changes how a foreign employer should structure an India hire, and it is the part almost every article on this topic gets wrong.

We place and pay people in India for a living, so we field this question constantly from founders, HR leads and CFOs who have read a US-law explainer and want to know what carries over. Some of it does. The commercial logic of dividing employer functions carries over fine. The legal machinery does not.

This guide answers the definitional questions properly, then does the thing the US-law pages cannot: it explains what happens to both concepts when the work is actually performed in India, which is where the liability sits when you are hiring into India from abroad.

What are co-employment and joint employment?

Co-employment is a deliberate arrangement in which two organizations share employer responsibilities for the same worker under a contract, typically a client and a PEO or staffing firm. Joint employment is a legal finding, usually by a court or agency, that two entities both act as employer of the same worker. One is designed; the other is found.

Both describe the same underlying situation, which is a worker with two organizations exercising employer-like power over them. What separates the terms is how you arrive there and who decides.

What is co-employment?

Co-employment describes a contractual arrangement where two organizations each hold part of the employer role for the same person at the same time. In the US market it is the standard way of describing a professional employer organization (PEO) relationship: the PEO handles payroll, employment taxes and benefits as the administrative employer, while the client keeps day-to-day direction of the work.

The defining feature is intent. Both parties sign a service agreement that sets out who does what, and the split is documented before the first payroll cycle runs. Our glossary entry on co-employment goes deeper on how those responsibilities divide across models, so we will not rebuild that comparison here.

A concrete example: a 40-person US software company signs with a PEO. The PEO files the payroll taxes and sponsors the health plan. The engineering manager still sets sprint goals, approves time off and runs performance reviews. Two entities, one worker, one written contract. A PEO arrangement in India does not work the way that US sentence implies, and the difference is the subject of this article.

What is joint employment?

Joint employment is a status that a court or an agency assigns after the fact. Nobody signs a joint-employment agreement. An investigator or a judge looks at who controlled the work, who paid, and who could hire and fire, then concludes that two entities were both employers of the same worker, whatever the paperwork said.

The classic fact pattern is a staffing agency and its client. The agency recruits, pays and formally employs the worker. The client controls the schedule, the tools and the daily instructions. When a wage claim or a discrimination claim lands, the client can be pulled in as a joint employer even though it never signed an employment contract with that person.

Subcontracting chains produce the same result, and so do contingent workforce arrangements where a vendor's people sit inside your team for years. The risk is not the label. The risk is inheriting an employer's liabilities without having priced or planned for them.

How do co-employment and joint employment differ?

The difference is how the relationship comes about. Co-employment is chosen: two organizations agree in writing to divide employer functions. Joint employment is found: a regulator or a court decides on the facts that both entities acted as employer, often when neither intended it. One is a design decision, the other is an outcome.

Read the table the practical way. Every row on the co-employment side describes something you can control before you hire. Every row on the joint employment side describes something that gets decided about you afterwards, by someone else, using evidence you may not have curated.

How is control and responsibility split?

In a co-employment arrangement the split is written down and both sides can point to it. Payroll, tax withholding, benefits administration and statutory filings usually sit with the administrative employer. Task assignment, performance management and business direction sit with the client. Where a dispute arises, the contract is the first document anyone reads.

In a joint employment finding there is no split, and that is the whole problem. Both entities are treated as exposed to the same obligations for the same worker, so unpaid wages, benefits or a wrongful termination claim can be pursued against either. Nothing was allocated in advance because nobody planned for the finding.

This is why an unintended joint employment finding sits so close to worker misclassification in practice. Both are cases where the paperwork says one thing, the facts say another, and the facts win.

Does Indian law recognize co-employment or joint employment?

No. Indian labour law does not define co-employment or joint employment as statutory categories, and neither term appears in the definition clauses of the Labour Codes. Indian courts decide who the employer is using control-based tests, and the framework contemplates one legal employer per worker. A second entity can carry duties without being that employer.

That is the whole answer, and it is worth being precise about what it does and does not mean. It does not mean co-employment is illegal in India, and it does not mean a two-party arrangement is impossible. It means there is no statutory status called co-employment or joint employment for a court to award, so the analysis runs entirely through who the employer is.

Where a second entity is involved through a contract-labour arrangement, the Occupational Safety, Health and Working Conditions Code 2020 attaches specific secondary duties to the principal employer, including liability for unpaid wages under section 55 and responsibility for welfare facilities under section 53, without making that principal employer the workers' employer. India solves the same commercial problem the US solves with a joint-employer doctrine, but it does it by naming duties rather than by naming a second employer.

This is a meaningful gap in how labor and employment law in India is usually explained to foreign buyers, and it is the reason we treat the imported US vocabulary with care.

What did India's Labour Codes replace?

India's four Labour Codes have been in force since November 21, 2025, replacing 29 central labour laws, though certain provisions are not yet commenced and Central and State rules are still being finalized as of July 2026. The four are the Code on Wages 2019, the Industrial Relations Code 2020, the Code on Social Security 2020, and the Occupational Safety, Health and Working Conditions Code 2020 (the OSH Code).

This matters for reading older material. Most of the Indian statutes cited in co-employment articles have been subsumed into and replaced by a Code, so a citation to the old Act is a signal the page has not been updated. Our guide to the new Labour Codes in India covers the transition in detail, and the four Labour Codes glossary entry is the short version.

How do Indian courts decide who the employer is?

The controlling formulation comes from International Airport Authority of India v. International Air Cargo Workers' Union, decided April 13, 2009. The Supreme Court asked "who pays the salary; who has the power to remove/dismiss from service or initiate disciplinary action; and who can tell the employee the way in which the work should be done, in short who has direction and control over the employee."

The holding that matters most for a foreign employer is the qualification the Court added. Where a contract is for the supply of labour, the workers do work under the direction, supervision and control of the principal employer, "but that would not make the worker a direct employee if the salary is paid by the contractor and the right to regulate employment is with the contractor."

Read that twice. Direction and control by the principal employer does not, by itself, create employment. Under a US joint-employer analysis, the same facts would often push hard toward a finding. In India they do not, provided the contractor genuinely pays and genuinely holds the right to regulate the employment. That judgment is unaffected by the Labour Codes and is current law as of July 2026.

The second case to know is Steel Authority of India Ltd. v. National Union Water Front Workers, decided August 30, 2001 by a Constitution Bench. It held that there is no automatic absorption of contract labour by the principal employer. The surviving principle from it, and the one that should shape how you set up an arrangement, is the carve-out: where the arrangement is sham, nominal or a mere camouflage, the workers are treated as direct employees of the principal employer. Substance beats form. That, and not any statutory doctrine, is India's real answer to the joint employment question.

What does this mean if you use a PEO or an EOR in India?

It means the mental model has to change. A US buyer reads "PEO" and expects a co-employer. In India, our PEO in India page states the position plainly: US-style co-employment is not legally recognized here, so what is being sold under that label is an arrangement where one entity is the legal employer and the other directs the work.

Under an Employer of Record arrangement, the EOR is the single legal employer of the person you hire. The employment contract is between the worker and the EOR, the worker sits on the EOR's payroll, and the EOR is the entity registered for statutory contributions. You set the work, the goals and the outcomes. If you want the mechanics of why that structure holds up, whether an EOR is legal in India walks through the statutory basis, and the EOR glossary definition covers the model itself.

The employee does not have two employers under this structure. They have one, and it is the EOR. We are deliberate about that phrasing because the alternative framing, which describes an India EOR as co-employment, invites exactly the sham-and-camouflage argument that SAIL left open.

Who is liable for what under India's principal-employer rules?

India's answer is not joint employment but principal-employer duties. Where you engage workers through a contractor, the Occupational Safety, Health and Working Conditions Code 2020 attaches specific secondary obligations to the principal employer, mainly wages on the contractor's default and welfare facilities, without making that principal employer the workers' employer.

Take the wages row first, because it is the one that surprises people. Under section 55, the contractor pays wages by bank or electronic transfer. If the contractor fails to pay within the prescribed period, the principal employer is liable to pay the wages in full, or the unpaid balance, and may then recover that amount from the contractor by deduction from sums payable under the contract or as a debt. You can end up writing the cheque. You do not become the employer by writing it.

Social security follows the worker rather than the contract. In the Code on Social Security 2020, section 2(26) defines "employee" to include a person employed "either directly or through a contractor", section 2(27) defines "employer" as one who employs "whether directly or through any person", and section 16(1) frames the provident-fund obligation for employees "whether employed directly or by or through a contractor". In practice that means provident fund, India's mandatory retirement savings scheme and the closest analogue to a US 401(k), and Employees' State Insurance, the state medical and cash-benefit scheme, cannot be dropped by routing people through a vendor. Our guide to payroll compliance in India covers how those contributions are actually administered each cycle.

Section 57 is the one that catches product and engineering teams. Contract labour may not be engaged in an establishment's core activities, subject to enumerated exceptions, with a designated authority deciding what counts as core. If the work you are contracting out is the work your India operation exists to do, that provision is a live issue, not a footnote.

When do the contract-labour rules apply?

Thresholds moved under the Codes, and the direction of travel was upward. The contract-labour provisions apply where 50 or more contract workers are engaged, raised from 20 under the superseded Contract Labour (Regulation and Abolition) Act 1970, and a contractor engaging 50 or more must hold a licence under Chapter XI of the OSH Code 2020, with licensing at section 47.

Standing orders, the formal service rules an establishment must certify and follow, now apply at 300 or more workers under section 28 of the Industrial Relations Code 2020, raised from 100 under the 1946 Act.

For most foreign employers hiring a team of five to fifty in India, neither threshold is reached. That is genuinely useful to know, and it is also the trap: falling below a threshold removes a filing obligation, it does not remove the question of who the employer is. That question has no threshold. Our explainer on what a statutory employee means in India covers where the definitional lines fall.

What are the risks of co-employment and joint employment in India?

The real risks are three. A documented co-employment arrangement can allocate duties that Indian law does not allow you to allocate. An undocumented one invites a finding that your arrangement was camouflage, which converts contract workers into your direct employees. And a foreign company whose people in India look like its own workforce can create permanent establishment exposure for tax.

What are the risks of a co-employment arrangement?

The first risk is a contract that divides obligations Indian law does not treat as divisible. A US-style service agreement may say the client is not responsible for wages. Section 55 of the OSH Code 2020 says otherwise on a contractor's default, and the statute does not defer to your commercial terms.

The second is definitional drift. If the arrangement is described to the worker as co-employment, the worker's own understanding of who employs them becomes part of the evidentiary record, and it may not match your paperwork. We keep our India employment contracts unambiguous about a single employer for exactly this reason.

The third is that a poorly structured arrangement is often just contractor misclassification wearing better clothes. If someone works full time, on your schedule, on your systems, under your manager, calling the relationship a shared one does not change what a tribunal will see.

What happens if joint employment is found on the facts?

There is no joint employment status to be found in India, so what actually happens is the camouflage outcome from Steel Authority of India. If a tribunal or a court concludes the contract-labour arrangement was sham, nominal or a mere camouflage, the workers are treated as direct employees of the principal employer, with the full employment relationship that implies.

The consequences follow the reclassification rather than a special penalty for the arrangement itself: back contributions, statutory benefits computed from the actual start date, termination protections, and the standing of a direct employee in any dispute. Our breakdown of employee misclassification penalties in India goes into what that exposure looks like in practice.

If you want a fast read on where your current setup sits, our misclassification quiz runs through the factors a reviewer would apply.

Can this create permanent establishment risk?

It can, and it is the risk foreign employers most often overlook because it sits with the tax authority rather than the labour authority. A foreign company's arrangement with workers in India can create permanent establishment exposure, which brings attributable profits into the Indian tax net.

The triggers usually discussed are a fixed place of business in India, a dependent agent who habitually concludes contracts on the company's behalf, and employees performing core revenue-generating functions rather than support work. The governing concepts are "business connection" under the Income-tax Act, 2025 (Act 30 of 2025), which replaced the Income-tax Act 1961 and applies to tax years beginning on or after April 1, 2026, read with the permanent establishment article of the applicable double taxation avoidance agreement.

Notice how this interacts with everything above. The more directly you control the work of people in India, the more comfortable you may be on the labour analysis after the International Airport Authority judgment, and the more attention the tax analysis deserves. Our guide to permanent establishment risk in India covers the depth, and the PE risk quiz gives you a first read on your own facts.

How do US joint-employer tests compare with India's approach?

The honest comparison is that they are not the same kind of question. In the US, joint-employer status is a live and shifting regulatory question that different agencies answer differently, and the answer has changed more than once in five years. In India, the question is not framed that way at all: there is one employer, and courts identify which entity it is.

Three practical consequences for a US company hiring in India. First, a compliance memo written against the NLRB standard does not transfer, because the Indian test does not weigh control the same way. Second, the US instinct to minimize direct control in order to defeat a joint-employer finding is not needed in India on the labour analysis, though it still matters for tax. Third, the Indian question you should actually be answering is the one nobody asks: which single entity is the legal employer, and can it prove it.

The primary sources for the US side are the NLRB's own statement of the joint-employer standard, the Labor Department's notice of proposed rulemaking on joint employer status, and the EEOC enforcement guidance on contingent workers.

How should you structure hiring in India to avoid these risks?

Pick a structure where one entity is unambiguously the legal employer, then make your records match it. In practice that means either an Employer of Record, where the EOR employs and you direct, or your own India entity, where you employ directly. What creates exposure is the middle ground, where nobody can point to a single employer with the paperwork to prove it.

The table is a starting point, not a verdict. We usually run the numbers before the structure, because the answer often turns on cost per head at your target team size rather than on principle. Our comparison of EOR versus setting up an India entity covers the trade-offs, the EOR vs entity calculator does the arithmetic, and the employee cost calculator gives you a loaded cost per hire. If you are weighing an EOR against employing people yourself once an entity exists, EOR versus direct hiring in India is the closer comparison.

What should your contracts and records show?

Documentation is where the camouflage argument is won or lost, and the standard is not "we have a contract". It is that an outside reviewer reading your records reaches the same conclusion your contract asserts. Five things should be consistent across every document:

• Who the employer is: one entity named as employer in the employment contract, on the payslips, in the statutory registrations, and in the offer letter the person actually received.
• Who pays the wages: payment runs from the legal employer's account to the worker, on a stated cycle, with the statutory deductions made and remitted by that same entity.
• Who can discipline and dismiss: the power to terminate, and to run a disciplinary process, sits with the legal employer, exercised on the legal employer's letterhead even where you raised the issue.
• Who directs the work: stated plainly in the services agreement as the client's role, and consistent with the way instructions actually flow day to day.
• What the worker was told: onboarding material, the handbook and the email signature should not describe the person as your employee if a different entity employs them.

The failure mode we see most often is a clean contract with contradicting operational reality. A dismissal letter sent on the client's letterhead, or a payment made directly by the foreign parent, undoes a great deal of careful drafting. If the underlying question is whether the person should be an employee at all, start with contractor versus employee in India and, if the answer is employee but you have no entity, hiring employees in India without an entity sets out the route.

How can Wisemonk help you hire compliantly in India?

Wisemonk is an India-native Employer of Record. We help companies hire, pay, and manage employees in India without setting up a local entity, and we take responsibility for the compliance work behind every payroll cycle so that provident fund, state insurance, professional tax and income tax withholding are handled correctly and on time. We are the single legal employer of the people we place for you, which is precisely why we do not describe what we do as co-employment.

We work with 300+ global clients, manage more than 2,000 employees in India, and process $20M+ in annual payroll. Our clients rate us 4.8 out of 5 on G2, and our EOR pricing starts from $99 per employee per month with no percentage of payroll and no surprise line items.

• Employer of Record: we act as the legal employer through our India EOR service, holding the employment contract, running the payroll and carrying the statutory registrations while you direct the work.
• Managed payroll and statutory compliance: our managed payroll service covers monthly processing, provident fund and Employees' State Insurance remittances, professional tax across states, and income tax withholding, for companies that already have an India entity.
• Contractor engagement through a Contractor of Record: where a genuine contractor relationship is the right answer, our Contractor of Record service handles the agreements, invoicing and compliance checks that keep the classification defensible.
• Recruitment: our India recruitment team sources and screens candidates in the local market, which matters when you have no hiring presence on the ground.
• Equipment and onboarding support: we procure, configure and ship laptops and devices to employees across Indian cities, and run day-one onboarding so a new hire is productive from the first week.

We provide EOR services in India, and we are expanding rapidly into the US and UK markets.

What our clients say

Companies from the US, UK, and Europe trust us to build their teams compliantly and fast. Here's what our clients say:

"I'm very happy that I discovered Wisemonk. They have been a pure pleasure to work with, and their attention to detail is impressive. They helped us understand their pricing model, find top-qualified individuals, interview them, and then onboard them. I gave them criteria for the type of people we sought, and they delivered. The individuals they were able to find have been some of the best engineers I have ever worked with. I recommend Wisemonk to anyone who is in need of staffing assistance."
- Dan Sampson, Head of Engineering at Cobu