EOR vs Contractor of Record in India: Tax, Benefits, IP

Choosing between an EOR and a contractor of record in India decides which Indian statute attaches to the person doing the work. That is a different question from which service costs less. In our own onboarding conversations it arrives as a cost question and turns out to be a statute question, because the two models sit on opposite sides of Indian employment law rather than on two rungs of the same ladder.

What is the difference between an EOR and a contractor of record in India?

The difference between a contractor of record and an employer of record in India is which legal relationship exists under Indian law, not which service level you buy. An EOR becomes the worker's legal employer, so employment statute attaches. A contractor of record becomes the contracting party to a services agreement with a self-employed person, so it does not.

A contractor of record, or COR, is the company that signs that services agreement in your place and carries the tax and paperwork obligations that follow from signing it. The glossary entry on what a contractor of record is carries the full definition.

India recognizes one legal employer per worker. So an EOR engagement produces exactly one employer, and a contractor of record engagement produces none. That is the axis everything else on this page runs along: not service level, not price, but whether there is an employment relationship for Indian statute to attach to.

This page is about what Indian statute does to each model. If you want the model-by-model comparison instead, including how each is priced and where each fits, how an agent of record compares with an employer of record covers it in full.

What actually changes in India when the same person moves from a contractor of record to an EOR?

Five things change, and none of them is the day rate. Indian tax withholding moves from a fee deduction to payroll. The GST registration question disappears. Provident fund, state insurance and gratuity begin to attach. Copyright stops depending on an assignment clause. And the exposure that accrued before the switch stays where it was.

Read the "does not attach" cells as a description of the model rather than as a way around anything. Nothing in the second column is a loophole. Whether a given engagement really is a contract for services is decided on substance rather than on the label, which is why contractor misclassification risk in India is the other half of this decision.

Which obligations attach on day one of employment

Three attach on the first payroll rather than on some later milestone: withholding on salary, provident fund and state insurance under the EOR's own registrations, and the employment terms the contract has to carry under Indian law. Gratuity attaches differently, as an accrual against length of service.

None of that is phased in. The day the employment contract starts is the day the obligations start, which is why the fully loaded cost of an EOR employee looks nothing like the invoice value of the same person as a contractor.

Which obligations fall away when the contract ends

Ending a services agreement ends the fee. It does not end two things that outlive it: where copyright in the work sits, and whether the engagement would survive a classification review of the period already worked.

Ending an employment contract is a different exercise. Notice, final settlement and any accrued gratuity are all obligations of the employer, and the EOR carries them because the EOR is the employer. What falls away on one side does not fall away on the other, and that asymmetry is easy to miss when the two models are priced next to each other.

Who withholds tax on each model, and under which provision?

We see this question asked backwards, with the rate settled before the payer is. On the contractor side, an India-resident payer withholds at source on the fee under the operative provision of the Income-tax Act 2025. On the EOR side, withholding runs through the employer's payroll, because the EOR is the legal employer.

Contractor payments: the operative provision and the two rates

The provision moved. Fees for professional and technical services were withheld under section 194J of the Income-tax Act 1961. That Act has been replaced, and the operative provision is now section 393(1), Table Sl. No. 6(iii) of the Income-tax Act 2025.

Two rates apply, a higher one on fees for professional services and a lower one on fees for technical services that are not professional services. Both are in the comparison table, and both bite once the annual threshold in the provision is crossed. Which of the two a given invoice falls under is decided by what the service is, not by what the contract calls it.

Where the India-resident payer is an individual or a Hindu Undivided Family, the challan-cum-statement for that payer's contractor and professional payments, which sits at its own entry in the same table, is Form 141, and Schedule C is the contractor and professional schedule.

Withholding is one strand of a wider set of obligations that also takes in GST on the invoice and the foreign-exchange channel the money travels through, and getting them out of order is where most first payments go wrong. If you want the payment chain end to end, how to pay contractors in India works through it.

EOR employees: withholding runs through payroll

There is no invoice and no fee deduction. The EOR runs salary withholding as part of the monthly pay run, deposits it under its own tax registrations, and files the returns that follow.

For you, that changes the artifact you receive. Instead of a contractor's invoice with a withholding line on it, you get a single monthly charge from the EOR, with the statutory detail sitting behind it on the employee's payslip.

Where a foreign payer sits

Where you pay a contractor directly from outside India, whether an Indian withholding duty attaches turns on whether you have a business connection or a presence in India. Put that question to your tax adviser before the first invoice, because if a duty does attach it attaches to you and not to the contractor.

When does GST registration become the contractor's problem, and does it become yours?

It becomes the contractor's problem once their aggregate turnover passes the services threshold under section 22 of the CGST Act 2017, which is Rs 20 lakh, about $21,000 as of September 2026. It becomes yours indirectly: the invoice you receive changes, the amount you pay changes, and your evidence of payment changes with it.

A lower Rs 10 lakh threshold reaches only four states: Manipur, Mizoram, Nagaland and Tripura. Naming them is worth the extra clause, because "special category states" is a much longer list and the GST services threshold does not follow it.

Three things change on your side when a contractor crosses the threshold:

• Your invoice trail: a registered contractor issues a tax invoice carrying a GSTIN, and an unregistered one does not, so the document sitting in your accounts payable file is a different document.
• Your evidence of payment: whether the contractor can treat the work as an export of services under GST depends on conditions being met, and those conditions reach back into how you pay and what you can evidence.
• Your rate negotiation: a contractor who becomes liable to register usually reprices, and it is better to see that coming than to meet it in month seven.

For the contractor side in more detail, GST and TDS compliance for India contractors sets out how the two obligations sit alongside each other.

None of this arises under an EOR. There is no contractor invoice, the person is paid through payroll, and GST registration is not a question anyone in the chain has to answer.

When do PF, ESI and gratuity attach, and what does that do to your cost?

We see this land in the fully loaded cost rather than the platform fee. Under a contractor of record, provident fund, state insurance and gratuity do not attach, because there is no employment. Under an EOR they attach from the first payroll, under the EOR's own registrations, and they are part of your cost from month one.

The obligations sit under the Code on Social Security 2020, one of India's four Labour Codes, in force as of September 2026. Provident Fund is the Indian retirement savings scheme, closest in shape to a 401(k). ESI is state-run health cover for lower-paid employees. Gratuity is a service-length payment made on exit.

What each one costs depends on the salary it is calculated against and on the ceilings and eligibility conditions written into the Code, so the honest answer to "what will this add" is a calculation rather than a number. The PF, ESI and gratuity obligations page carries the rates and thresholds those calculations use.

Gratuity is the one that surprises people

Gratuity is a length-of-service obligation, so it only exists where there is service to measure. It accrues once an employee meets the qualifying period, and the Code defines both the period and how continuous service is counted.

Both definitions matter, and a bare statement of the rule with the conditions stripped off usually understates or overstates a foreign employer's exposure. Treat it as an accrual to model, not as a rule to memorize.

On the contractor of record side there is nothing to measure, because there is no employment. Which means converting a long-standing contractor to an EOR employee starts a clock rather than inheriting one, and that is often the single largest line item people had not modelled. If you want the arithmetic on a specific salary, what an India hire really costs runs it.

Who owns the work product and the code by default under Indian law?

Under section 17 of the Copyright Act 1957, the author is the first owner of copyright, and an independent contractor is the author of what they write. There is no work-for-hire default in Indian law. Without an express assignment, the contractor keeps the copyright. An EOR employee's work sits inside an employment relationship, where the default runs the other way.

Every IP review we run on an inherited India codebase starts in the same place: the signature page of the original services agreement. Not the repository, not the invoices, not the offer email. The document either assigns the copyright or it does not.

This is the sharpest practical difference between the two models, and it is the one US and UK buyers most often carry the wrong intuition into, because the domestic default they are used to points the other way. Protecting intellectual property when hiring in India sets out the wider position.

What an express assignment actually has to do

Two things, and paying for the work is neither of them.

• It has to be express: an assignment is a term of the agreement, not something inferred from the fact that an invoice was raised and settled.
• It has to be signed by the person who created the work: where you contract with a one-person company rather than with the individual, check that the chain runs from whoever typed the code, through that company, to you. A gap anywhere in that chain is a gap in your title.

Where you are drafting from scratch, the India independent contractor agreement essentials are the place to start, because an assignment bolted on afterwards is a negotiation rather than a term.

What this means for a codebase already built by contractors

An assignment signed today speaks from today unless it says otherwise. So a new employment contract does not reach backward and move copyright in work created before it existed.

Where an India codebase was built by contractors on agreements with no assignment clause, section 17 put first ownership with them and left it there. The fix is a separate assignment covering the earlier work, executed by the people who wrote it, not a clause in a forward-looking contract. The IP chain for India developers walks through where those gaps usually sit.

Does a contractor of record remove your misclassification risk in India?

No. It changes who holds the contract, not how an Indian court decides who the employer is. That decision looks at substance rather than the label, and it turns on three tests: control, integration and economic dependence. A contractor of record that gets the paperwork right reduces the evidence against you. It does not change the tests.

The three tests ask who directs how the work is done, how far the person is integrated into your operation, and how far their income depends on you. India also names principal-employer duties rather than creating a second employer, so employer status is never split between a provider and your company.

For the tests themselves, who counts as an independent contractor in India works through each one with the Indian case law behind it.

What follows if an engagement fails those tests is a separate question with its own numbers, and misclassification penalties in India is where they live.

What an indemnity covers, and what it cannot move

An indemnity is a commercial promise between you and the provider about who pays. Read what it says, because that wording is the whole of the protection you are buying. Four things to find in it:

• Scope: which categories it covers, whether that is assessed tax, statutory dues, defence costs, or all three.
• Exclusions: what it carves out. Look specifically for your own direction of the work, and for anything predating the date the provider became the contracting party.
• The cap: what the ceiling is, and whether it is per claim or in aggregate.
• Conditions: what you have to do to keep it alive, usually notification within a period and cooperation on the defence.

Whatever is left after those four is the residual you are carrying yourself, and it is worth writing that down before you sign rather than after.

What happens to exposure that has already accrued if you convert a contractor to an EOR employee?

We ask to see the conversion paperwork before a switch date is agreed, for one reason. Conversion changes the relationship going forward. It does not retire what accrued while the person was engaged as a contractor. And the conversion documents themselves describe the working pattern that came before, which makes them evidence.

That cuts both ways. A conversion done cleanly is a good record of a genuine change in the relationship. A conversion done carelessly reads as an admission about the period before it, which is the shape what happens on reclassification describes.

What to settle before the switch date

• The classification position on the period already worked: what the engagement actually looked like, decided on the three tests rather than on the contract heading.
• Copyright in everything produced before the switch: section 17 put it with the contractor, and only an assignment moves it.
• Whether the services agreement is terminated or novated: these are different documents with different consequences, and the choice should be deliberate.
• What the final contractor payment settles: and, just as importantly, what it does not.
• The start date on the employment contract: whether it is the switch date or an earlier date is itself a statement about when employment began, so pick it knowing that.

Converting contractors to employees sets out the sequence these steps run in.

What the new employment contract should not silently re-assert

An IP assignment that covers only work done on or after the start date leaves the pre-switch codebase exactly where section 17 put it. That is the most common quiet gap in a conversion pack, and it is invisible until someone runs diligence on the repository.

Two more to read closely. A recital describing the person as previously engaged as an independent contractor is a characterization you will have to stand behind. And a continuous-service clause that dates service from the switch date is one thing, while one that back-dates it is a concession with a cost attached.

What does each model cost you in India?

The two models are priced on different units, so comparing them per head compares two different things. A contractor of record is priced on the contractor's payout. An EOR is priced per employee per month, and that fee sits on top of gross salary and employer statutory contributions. The platform fee is not the cost of the employee.

Two different units, and it is worth being precise about which is which:

• Contractor of record: priced on what you pay the person. Wisemonk charges 6% per contractor payment, so the cost moves with the payout and there is no separate per-seat charge.
• EOR: priced per employee per month, with gross salary and employer statutory contributions sitting on top. Wisemonk EOR is priced on that per-employee-per-month unit, and in most models the salary and contributions dwarf the fee.

Which is why the useful comparison is not fee against fee. It is total cost of the engagement against total cost of the engagement, with the statutory layer in the EOR column and the contractor's own tax position in the other. What an India EOR costs breaks the employment side down into its components, including the ranges.

The model decision comes before the provider decision, and the contractor side is the harder of the two to shortlist, so the contractor of record providers that cover India is worth reading before you brief anyone.

How do you decide between an EOR and a contractor of record for your India team?

We start this with one question rather than a price: who decides how the work gets done. If you direct it, you are describing employment, and an EOR is the model that matches. If the specialist controls the method and delivers against a defined scope, a contractor of record matches. Cost follows that answer rather than setting it.

Five questions to answer about your own engagement before you pick a model:

1. Who sets the hours and the working pattern?
2. Is the deliverable defined, or is the person filling a role?
3. Does this person work for anyone else, or is their income substantially from you?
4. Is the work part of your core operation or adjacent to it?
5. Who owns what they produce, and does anything say so in writing?

Answer those five honestly and the model usually picks itself, which is a better outcome than picking a model and then writing a contract that argues for it. For a faster read on a single engagement, a two-minute misclassification check runs the same signals.

Signals that point to an EOR

• You set the working pattern: hours, availability, the standups they attend.
• The person is filling a role, not delivering a scope: the job would still exist if they left.
• The work is core: it sits inside what your business does rather than beside it.
• You are their main source of income: economic dependence is one of the three tests, and it is the one that shifts quietly over time.
• You want the IP default on your side: rather than resting on an assignment clause holding up.

The signal set is close enough to the general classification question that contractor vs employee in India is the fuller version of this list.

Signals that point to a contractor of record

• The scope is defined and finite: a deliverable with an end, not a seat with a start date.
• The specialist controls the method: you specify the outcome, they decide how to reach it.
• They have other clients: and their income does not substantially depend on you.
• The work is adjacent: specialist input into something you do, rather than the thing you do.
• You want speed with a clean contracting party: and you are willing to hold the classification discipline that comes with it.

When the answer is neither

Two situations come up often enough to name. If you already hold an Indian entity and an HR function, you are already the legal employer, and what you need is PEO or managed payroll running on your own registrations rather than a third party becoming the employer.

And if you are paying an Indian agency or consultancy against an invoice, the counterparty is a business rather than an individual, so this is a vendor payments question and the classification tests are not the ones that apply. Choosing an employment model in India lays the routes out side by side.

What do you need in place before your first India hire on either model?

The two models need different documents. On the contractor side: a services agreement with an express IP assignment, and a classification review of the engagement as it is actually run. On the EOR side: an India-law employment contract, payroll registration under the EOR's entity, benefits enrollment, background verification and equipment. Neither list is long, but neither is optional.

On the contractor of record side

• A services agreement in the right shape: fixed-rate or pay-as-you-go, with the rate and the payment unit set per contractor rather than forced into one template.
• An express IP assignment inside it: signed by the individual who will do the work, for the reasons section 17 makes unavoidable.
• A classification review of the engagement: run on how the work will actually be directed, not on how the agreement describes it.
• An authorized signatory and secure e-signature: so the contract is executed by someone with authority to bind the contracting party, and the execution is evidenced.
• Invoicing and a billing cycle you can live with: automatic invoice generation and a monthly or bi-weekly cycle keeps the paper trail intact without anyone chasing it.

Contractor onboarding checklist covers the operational side of getting this started.

On the EOR side

• An India-law employment contract: carrying the terms Indian law requires, in the EOR's name.
• Payroll registration under the EOR's entity: with provident fund and state insurance enrolment following from it.
• Benefits enrollment: health cover in particular, arranged with the employee directly rather than left to them.
• Background verification: run before the start date, with consent, to Indian regulatory requirements.
• Equipment: sourced and shipped to an Indian address, which is a longer lead time than most first-time hirers plan for.

EOR onboarding in India sets out how these run in sequence and what a realistic start date looks like.

How can Wisemonk help you hire in India on 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.

For a team you engage on either model, that means named people working on compliant Indian contracts within weeks, on the model Indian law actually supports for the way you direct the work, without registering a company in India first. We are an India specialist, expanding to more countries, so India is the market our own entity, payroll registrations and counsel sit in.

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 September 2026.

Here is how we help:

• Contractor of Record: we become the legal contracting party for your Indian contractors, with compliant agreements, IP assignment, classification memos and payouts.
• India PEO: if you already hold an Indian entity, we run payroll, statutory filings, benefits and onboarding under your own registrations.
• Managed India payroll: the monthly pay run and its filings executed for you where you keep your entity and your HR team.
• Background verification providers in India: identity, employment, education, court and police checks run before a start date.
• Vendor and freelancer payments in India: for paying Indian agencies and consultants against invoices through RBI-approved channels, with the remittance documentation retained.

Equipment sourcing and shipping to Indian addresses runs alongside our EOR engagements, which is usually the practical detail people discover last.

From our experience running both models in India, the engagements that go wrong are almost never the ones where someone picked the wrong model. They are the ones where nobody revisited the choice after the work changed shape, which is why we review each contractor engagement rather than only at the start.