Employer of Record in India: When to Use an EOR

Employer of Record in India: When to Use an EOR

Hiring an employer of record in India is one of the fastest ways to put a person on the ground in Bengaluru, Pune or Gurugram without first incorporating a company, opening a bank account and registering for provident fund. It is also one of the easiest decisions to get wrong — either by staying on an EOR long after it stopped making financial sense, or by using one when a simple contractor agreement or a proper subsidiary would have served better.

This guide is written for two very different readers.

The first is a founder, CFO or people leader at a company headquartered outside India — the US, UK, Singapore, UAE, Australia, the EU — who has found a candidate in India and needs to make them an offer next month, not next year. The second is an Indian company: a Mumbai-headquartered business opening a small sales pod in a state where it has no registrations, a startup piloting a two-person team in a new city, or an enterprise running a global capability centre (GCC) experiment before it commits to a full entity.

Both readers face the same core question. Do you rent an employer, or do you become one?

We will not sell you an answer. This is a vendor-neutral decision guide: what an EOR actually is in legal terms, what it does and does not do, how it compares to contractors, staffing agencies, PEOs and payroll-only vendors, how the cost mechanics really work, and — the part most articles skip — when an EOR is the wrong answer and how to exit one cleanly without destroying your employees' continuity of service.

One caveat up front, and we will repeat it: employment law, tax residency and permanent establishment analysis in India are fact-specific. Nothing here is legal or tax advice. Every structural decision described below should be validated with qualified Indian tax counsel and employment counsel before you sign anything.

---

What an Employer of Record in India Actually Is

An employer of record is a company that legally employs a worker on your behalf. On paper, the EOR is the employer. It issues the employment contract, runs payroll, deducts and deposits statutory contributions, files returns, maintains statutory registers, and appears as the employer in every government record that matters.

In practice, you — the client — direct the work. You decide what the person builds, who they report to, what their goals are, when they get promoted and when the relationship should end. You do everything a manager does except sign the payslip.

That split is the entire product. The EOR sells you the legal shell of employment; you retain the substance of management.

The three-party structure

Every EOR arrangement in India involves three relationships:

1. Client ↔ EOR. A commercial services agreement. This is where fees, indemnities, notice periods, liability caps, IP assignment flow-through, data processing terms and termination rights live. It is a B2B contract, and it is the document that determines whether you are protected when something goes wrong.

1. EOR ↔ Employee. A genuine India-law employment contract. The employee is on the EOR's rolls, gets a UAN for provident fund, an ESI number if applicable, Form 16 from the EOR's TAN, and — critically — accrues gratuity eligibility and leave against the EOR.

1. Client ↔ Employee. Practically, everything. Day-to-day direction, tooling, team membership, performance conversations. Legally, nothing formal — and that gap is precisely what needs careful handling around intellectual property and confidentiality, which we cover at length below.

Why the structure exists at all

India does not have a "hire a foreigner's employee" registration you can obtain. If a foreign company wants a payrolled employee in India, it either sets up a legal presence — a private limited company, a branch office, a liaison office with its restrictions — or it uses a third party that already has one.

Setting up a private limited company in India is not exotic. It is a well-trodden path: name reservation, incorporation, PAN and TAN, a bank account, GST registration if relevant, professional tax registration in the applicable states, shops and establishments registration, EPFO and ESIC registration once thresholds are crossed. But it takes real elapsed time, it creates permanent obligations (board meetings, statutory audit, annual filings, transfer pricing documentation if you transact with the parent), and it is very hard to unwind quickly if the India experiment doesn't work.

The EOR exists to compress that timeline from months to days, and to make the exit as simple as a contract termination.

What an EOR is not

An EOR is not a way to avoid Indian employment law. The employee is a full Indian employee with full statutory entitlements. An EOR does not reduce your PF liability, does not exempt anyone from gratuity, and does not make termination easier than Indian law allows. It moves the administration and the record-keeping, not the obligations.

An EOR is also not automatically a shield against permanent establishment risk. It reduces some exposures and creates others depending on what the employee actually does — a topic we will return to, and one where you genuinely need tax counsel rather than a vendor's marketing page.

---

EOR vs Staffing Agency vs PEO vs Contractor vs Payroll-Only

The terminology in this market is loose, and vendors use words inconsistently. Here is how the models actually differ in substance.

Employer of record

The EOR is the sole legal employer. It recruits nobody — you find the person — but it employs them, pays them and carries the compliance. The worker is dedicated to you full-time and behaves like a member of your team. Duration is open-ended.

Staffing agency / manpower supplier

A staffing agency sources and supplies workers, often for defined projects, seasonal peaks or high-volume roles. The agency is the employer, but the commercial logic is different: you are buying labour capacity, often with the agency handling recruitment, and often with a markup structure tied to bill rates rather than a flat administrative fee. In India, arrangements of this type frequently sit within the contract labour regulatory framework, which brings its own registrations and principal-employer obligations. If your arrangement looks like supplying workers to your premises for your operations, get counsel to confirm whether contract labour rules apply to you as principal employer.

PEO / co-employment

The classic PEO model, as understood in the US, is co-employment: two entities share employer responsibilities, and the client must already have its own legal entity and employer registrations. The PEO takes over payroll, benefits administration and compliance support; the client remains an employer of record in its own right.

Co-employment as a formal legal doctrine does not map neatly onto Indian law. In India, "PEO" is often used loosely — sometimes to mean an EOR, sometimes to mean an outsourced HR and payroll service for a company that already has an entity. When a vendor says PEO, ask a single clarifying question: whose entity employs the person and whose PF registration is used? The answer tells you which model you are actually buying.

Independent contractor

You engage the person as a service provider on a professional services agreement. They invoice you, handle their own taxes, and are not on anyone's payroll. No PF, no gratuity, no leave entitlement.

This is legitimate for genuinely independent professionals with multiple clients, their own tools and control over how and when they work. It becomes risky the moment the relationship looks like employment in substance — fixed hours, exclusive engagement, a manager, a laptop you provided, a seat in your org chart. More on that risk shortly.

Payroll-only / payroll bureau

You have an Indian entity. A vendor processes payroll on your registrations, prepares challans and returns for your signature, and generates payslips. The vendor is not the employer and takes no employment liability. This is a processing service, not an employment service. Many companies conflate this with EOR because both involve "someone else running payroll" — the difference is whose name is on the employment contract and whose PF code the contributions land in.

Comparison table

Read that table with one question in mind: what am I actually buying? If you need someone to find the person, an EOR will not help. If you need someone to carry the employment, a payroll bureau will not help.

---

Why Misclassifying an India-Based Worker as a Contractor Is Risky

This is the single most common shortcut, and it deserves a section of its own.

The pattern is familiar. A foreign company finds a great engineer in Hyderabad. Setting up an entity feels heavy. An EOR feels expensive. So the engineer signs a consulting agreement, invoices monthly in USD, and works 40 hours a week exclusively for the company, attends daily standups, uses a company laptop, has a manager and a performance review, and has done so for three years.

That is not a contractor relationship in substance. It is employment with an invoice stapled to it.

What "substance over form" means here

Indian authorities and courts, like those in most jurisdictions, look past the label on a contract to the reality of the relationship. The factors that typically matter include:

• Control. Who decides what work is done, how, and when? Fixed working hours and a reporting manager point toward employment.
• Integration. Is the person embedded in your team, on your org chart, in your internal systems, with a company email address?
• Exclusivity and economic dependence. Does the person have other clients, or is essentially all their income from you?
• Tools and infrastructure. Who provides the equipment and workspace?
• Substitution. Can the person send someone else to do the work? A genuine contractor usually can; an employee cannot.
• Duration and continuity. A three-year exclusive engagement reads very differently from a three-month project.
• Payment structure. A fixed monthly amount that never varies with deliverables looks like salary.

No single factor decides it. The overall picture does.

The exposures, in general terms

If a long-running contractor arrangement is re-characterised as employment, the consequences can stack:

Statutory contribution arrears. Provident fund contributions that should have been made — employer and employee share — can become payable retrospectively, potentially with interest and damages. ESI may apply for employees below the wage threshold. The employer share is a real cash cost; the employee share may be practically irrecoverable from someone who has already left.

Gratuity. Employees who complete the qualifying period of continuous service become entitled to gratuity. A re-characterised engagement can bring long-tenured "contractors" into scope, and the accrual is calculated on years of service you thought you did not have.

Leave and statutory benefits. Earned leave accrual under the applicable state shops and establishments legislation, maternity benefit entitlements, statutory bonus where applicable, and the associated record-keeping obligations.

Withholding tax mismatch. Payments to contractors and salary to employees are withheld under different provisions at different rates. A re-characterisation can create shortfall, interest and penalty exposure for the payer.

Termination disputes. A contractor whose agreement is not renewed has limited recourse. An employee has notice, dues, full-and-final settlement rights, and — depending on the nature of the role and applicable law — potentially more. Misclassification claims very often surface at the moment of exit, brought by the person who was let go.

Permanent establishment exposure. This is the one that keeps foreign CFOs awake. If a person in India is habitually concluding contracts on behalf of a foreign company, or performing core business functions from a fixed place in India, the foreign company may be treated as having a taxable presence in India. That can mean corporate tax on profits attributable to the India activity, filing obligations, transfer pricing documentation, and years of retrospective exposure if it is discovered late.

PE analysis depends on the specific facts, the nature of the person's role, and the applicable double taxation avoidance agreement. It is genuinely complex. Do not resolve this from a blog post — including this one. Get an Indian tax adviser to look at your specific facts.

Where an EOR helps, and where it does not

Using an EOR moves the employment relationship onto an Indian entity that is properly registered, which removes the misclassification problem for that worker and generally reduces some categories of exposure.

It does not automatically eliminate PE risk. If your India-based salesperson is negotiating and effectively closing deals for the foreign parent, the fact that an EOR signs their payslip does not, by itself, answer the PE question. Structure the role, the authority and the contracting flow deliberately, and have tax counsel confirm it.

---

What an Employer of Record in India Handles — and What It Does Not

Vendors describe their scope differently. Here is the realistic division of labour.

What a competent EOR handles

• Employment contracts drafted under Indian law, including notice periods, probation, confidentiality, and IP assignment clauses (subject to the flow-through issue discussed later).
• Onboarding documentation — PAN and Aadhaar collection, bank details, previous employment details, Form 11 for PF, nomination forms, and the background check if you have contracted for it.
• Payroll processing — monthly gross-to-net computation, salary structuring across basic, HRA, allowances and reimbursements, and disbursement to employee bank accounts.
• Statutory deductions and deposits — provident fund (employee and employer share), ESI where applicable, professional tax in the relevant state, labour welfare fund where applicable, and TDS on salary.
• Statutory filings and returns — monthly PF and ESI returns, professional tax returns, quarterly TDS returns, and annual Form 16 issuance.
• Payslips and tax documentation — monthly payslips, investment declaration and proof collection cycles, Form 16 at year end.
• Statutory registers and records — attendance, wages, leave registers and other records required under applicable state and central legislation.
• Insurance and benefits administration — group medical cover, personal accident and term life where offered, and enrolment or de-enrolment as people join and leave.
• Leave administration — tracking accrual and consumption in line with the applicable state legislation and your policy, within the bounds of what the law permits.
• Offboarding and full-and-final settlement — notice period administration, leave encashment, gratuity where applicable, relieving and experience letters, and PF exit marking.
• Local employment law updates — flagging changes in minimum wages, state-specific rules, or contribution thresholds that affect your people.

What an EOR does not handle

• Performance management. The EOR will not tell you whether your engineer is any good, will not run your review cycle, and will not build your competency framework.
• Culture, engagement and retention. People join your team, not the EOR's. If they are disengaged, that is your problem to solve.
• Recruitment. Most EORs do not source candidates. Some offer it as a separate paid service. Assume you are doing the hiring.
• Day-to-day direction. By design. The EOR must not be seen to be directing work, and you would not want it to.
• IP strategy. The EOR provides a contract template. Whether your inventions actually end up owned by your parent company is an architecture question you have to think about.
• Equity administration. Granting stock to EOR-employed staff is a genuinely awkward problem. See the dedicated section below.
• Commercial risk on your business. If your India experiment fails, the EOR is not carrying that.
• Making termination easy. Indian employment law applies in full. An EOR will administer a termination correctly; it will not make an unlawful one lawful.

The mental model: an EOR is infrastructure, not a people function. You still need someone who owns HR.

---

EOR vs Own Entity: A Decision Framework

The honest answer to "should I use an EOR in India?" is: it depends on seven variables. Here they are, with a scoring approach you can actually run in a meeting.

The seven variables

1. Headcount. One to five people in India strongly favours an EOR. Twenty-plus almost always favours an entity, because the per-head fee compounds while entity fixed costs do not. The middle band is where judgement lives.

2. Time horizon. Under twelve months favours an EOR — you may never reach the crossover point. Three-plus years favours an entity, because you will pay for the EOR many times over and end up building the entity anyway.

3. Control requirements. Do you need to set your own policies, run your own performance and comp cycles, sign your own contracts and build a distinct employer brand? Entity. Are you happy operating within the EOR's employment templates? EOR.

4. IP sensitivity. If the India team is producing core intellectual property — your product, your algorithms, your patentable work — the ownership chain matters enormously, and an entity gives you a cleaner one. If the team is doing sales support, customer success or operations, the IP question is lighter.

5. Cost. Straightforward arithmetic once you model it. We do a worked example below.

6. Compliance burden appetite. An entity means statutory audit, board meetings, annual filings, transfer pricing documentation if you transact with the parent, and a finance person who understands Indian compliance. Some companies simply do not want that overhead for a three-person team.

7. Exit friction. Shutting down an Indian private limited company is materially harder and slower than terminating an EOR agreement. If there is real uncertainty about whether India works out, that optionality has value.

Scoring matrix

Score each row 1 to 5, where 1 = strongly favours EOR and 5 = strongly favours own entity. Weight the rows by how much each factor matters to you, then compute a weighted average.

Interpreting the weighted score:

• Below 2.0 — EOR is clearly right. Use one, and revisit in twelve months.
• 2.0 to 3.0 — EOR now, with an explicit entity trigger written into your plan (for example, "we incorporate when we cross 10 heads or 18 months, whichever first").
• 3.0 to 4.0 — Start the entity process now, and use an EOR as a bridge for the people you need to hire in the meantime. This hybrid is extremely common and often the smartest play.
• Above 4.0 — Go straight to an entity. An EOR will cost you money and time you will not get back.

The trigger point in the 2.0–3.0 band matters more than the score itself. Companies rarely make a bad initial EOR decision; they make a bad continuation decision by never revisiting it.

---

EOR Cost Structure in India: How the Money Actually Works

We are not going to publish price figures. Rates vary by vendor, headcount, salary band, contract length and negotiation, and any number printed in a blog post is stale within a quarter. What is stable is the structure — and understanding the structure is what lets you compare quotes properly and spot the costs that do not appear on the first page of a proposal.

The two headline pricing models

Per-employee-per-month (PEPM) flat fee. A fixed monthly amount per employee, regardless of salary. Predictable, easy to budget, and generally better for you if you are hiring senior, well-paid people. Watch for tiering — the fee often steps down as headcount rises, so ask for the full tier table, not just the rate at your current size.

Percentage of payroll. The fee is a percentage of gross salary or of total payroll cost. Cheaper for junior hires, punishing for senior ones, and it means your admin cost rises every time you give someone a raise. If you are quoted a percentage, always convert it to an effective PEPM at your actual salary levels before comparing.

Some vendors offer both and will let you choose. Run both models against your projected salary bands for the next 24 months and pick the one that is cheaper across the whole period, not just at month one.

What sits underneath the fee

The service fee is only part of what leaves your bank account. Your total monthly outflow per employee typically comprises:

• Gross salary as agreed with the employee.
• Employer statutory contributions — the employer share of provident fund, ESI where applicable, and any other applicable employer-side contributions. These are legally mandated costs, not vendor charges, and would exist under your own entity too.
• The EOR service fee — PEPM or percentage.
• Benefits premiums — group medical, personal accident, term life. Sometimes bundled, often billed at cost plus an administration margin.
• Payment processing and FX costs — the spread on converting your currency to INR, plus wire fees.

The costs that surprise people

These are the line items that turn a clean-looking quote into a difficult conversation six months in.

Security deposits and advance funding. Most EORs require you to pre-fund payroll before the disbursement date, and many require a deposit — often expressed as one or more months of total employment cost per employee — held for the duration. This is a working capital cost, not a fee, but it is cash you do not have.

Severance and termination funding. If you terminate an employee, someone has to fund notice pay, leave encashment, gratuity if applicable, and any settlement. That someone is you. Read the agreement carefully: some EORs require you to pre-fund a termination reserve, some require immediate payment on notice, and some will not process a termination at all until funds are received. Understand whether the vendor also charges a separate offboarding fee.

Notice buyouts. If you want someone to leave immediately rather than serve notice, you pay for the notice period. Budget for it in any planned reduction.

Statutory bonus. Where applicable under the relevant legislation and wage thresholds, statutory bonus is an annual obligation. Some quotes fold it into the cost estimate; others do not mention it until the payout month. Ask explicitly.

Gratuity accrual. Gratuity becomes payable on completion of the qualifying continuous service period. Vendors handle this differently — some invoice a monthly accrual so the cost is smoothed, some invoice the lump sum when it crystallises. The second approach produces a nasty quarter. Ask which model applies and get it in writing.

Annual leave encashment. Accrued and unused leave typically gets encashed at exit under the applicable policy and law. It accrues quietly all year.

Insurance renewal escalation. Group medical premiums in India generally trend upward at renewal, particularly for small groups with claims history. Do not assume year-one pricing holds.

FX volatility. You are paying INR costs from a foreign-currency budget. A 5% currency move is a 5% budget move. Some vendors offer rate locks; most do not.

Onboarding and offboarding fees. Per-event charges for setup, background verification, document collection, exit processing and issuance of relieving letters.

Change fees. Mid-cycle salary revisions, address changes across states, promotions and structure changes may attract charges depending on the contract.

Cost structure comparison

That last row is the whole ballgame. An EOR's cost is almost entirely variable; an entity's cost is substantially fixed. Variable costs win when volume is low. Fixed costs win when volume is high. The only question is where the lines cross for you.

---

Worked Example 1: Finding the EOR vs Entity Crossover Point

All figures below are hypothetical and used purely to illustrate the arithmetic. They are not price quotes, benchmarks or estimates of market rates. Build your own model with your own quotes.

The setup

GlobalStack Inc. is a US software company with no Indian presence. It wants to hire engineers in India. Assume, purely for illustration:

• Illustrative EOR service fee: $600 per employee per month (a made-up round number chosen to make the maths readable).
• Illustrative one-time entity setup cost: $8,000 (incorporation, professional fees, registrations, bank account, initial legal).
• Illustrative recurring entity overhead: $2,500 per month (accounting retainer, statutory audit amortised, company secretarial, compliance software, registered office, a fraction of a finance person's time).

Salaries and statutory employer contributions are identical under both models, so they cancel out of the comparison entirely. That is an important simplification and it holds in reality: an EOR does not change what you pay the employee or the government.

Year-one comparison at different headcounts

Year-one crossover in this illustration lands between five and six people.

The steady-state view

Year one is distorted by the one-time setup cost. From year two onward, the entity costs only the $30,000 annual overhead:

At 20 people in this model, the entity is roughly $114,000 a year cheaper — enough to fund a senior engineer.

What the numbers do not capture

Do not stop at the table. Three adjustments matter:

Time value. The entity takes weeks to months to stand up. If your candidate has a competing offer, the EOR's speed has real economic value that no spreadsheet row captures.

Risk cost. Under your own entity, compliance mistakes are yours. That has an expected cost — penalties, interest, remediation, management time — which is low if you run good systems and non-trivial if you do not.

Exit cost. If GlobalStack decides in month 14 that India is not working, closing an entity is slow, expensive and administratively draining. Terminating an EOR agreement is a notice letter. If your probability of exit is meaningfully above zero, the EOR's optionality is worth something real.

A reasonable synthesis of this illustrative model: use an EOR up to roughly four or five people, plan the entity as you approach that band, and be operating your own entity before you cross ten. Your actual numbers will differ. Run them.

---

Worked Example 2: An Indian Company Using an EOR Domestically

EOR is often framed as a cross-border product. It is not. Indian companies use it too, and the logic is different.

The scenario

Meridian Analytics is a Chennai-headquartered company with roughly 180 employees, a single office, and registrations in Tamil Nadu. It wants to:

• Place three enterprise sales people in Maharashtra, Karnataka and Delhi NCR, working from home and travelling to client sites.
• Pilot a four-person data engineering pod in Kolkata for a specific client contract that runs 14 months.

Meridian's HR head is weighing three options.

Option A — Put everyone on the Chennai payroll. Simplest administratively, but the moment you have employees working regularly in another state, questions arise about state-specific registrations, professional tax in the state of work, shops and establishments applicability, and state-specific leave rules. Whether and when a registration obligation is triggered depends on facts like whether you have an establishment in that state. This is exactly the sort of question to put to counsel rather than assume away.

Option B — Register in each state. Clean and correct, but it means new professional tax registrations, potentially new shops and establishments registrations, state-specific compliance calendars, and ongoing filings in four states instead of one — for seven people.

Option C — Use an EOR that already holds registrations in those states. The seven people are employed by the EOR, which already files in Maharashtra, Karnataka, Delhi and West Bengal. Meridian directs the work, pays a per-head fee, and adds no new state registrations to its own compliance calendar.

How Meridian should think about it

For the 14-month Kolkata pod, Option C is compelling. The engagement has a defined end date. Building registrations and a compliance footprint in West Bengal for a fixed-term project — then unwinding it — is disproportionate effort. The EOR's fee is essentially the price of not adding a permanent compliance obligation for temporary work.

For the three sales people, it depends on trajectory. If Maharashtra and Karnataka are going to become real offices with 15 people each within two years, Meridian should register properly and build the muscle now. If they will remain one- or two-person remote pods indefinitely, the EOR may be permanently cheaper than four parallel state compliance calendars.

The general principle for domestic EOR use in India: an EOR is a way to buy geographic reach without buying geographic compliance. It makes most sense where the headcount per state is low and likely to stay low, or where the engagement is genuinely time-bound.

The trap: using an EOR domestically to keep people "off the books" or to avoid statutory obligations you would otherwise have. That is not what the model does. The obligations exist regardless; the EOR just administers them on its own registrations. If a vendor pitches domestic EOR as a way to reduce PF liability or avoid gratuity, walk away.

---

IP Assignment and Confidentiality: The Biggest EOR Mistake in India

If you take one operational point from this article, take this one.

The problem in one sentence

The EOR employs the person, so the standard employment contract assigns work product to the EOR — not to you.

Think about what that means. Your engineer in Pune writes the core of your new pricing engine. Their employment contract, signed with an Indian EOR company they have never met, says inventions created in the course of employment vest in the employer. The employer is the EOR. Your parent company is not a party to that contract.

If the chain of assignment from employee → EOR → your entity is not explicit, complete and continuous, you may have a genuine gap in your ownership of your own product.

When this actually surfaces

Almost never during normal operations. It surfaces at the worst possible moments:

• Due diligence in a funding round or acquisition. Buyers' counsel ask for the IP chain for every contributor. "Our EOR employed them" is the start of a long conversation and, in the worst case, a diligence finding that affects price or timing.
• A patent filing. Inventorship and ownership need to be established cleanly.
• A dispute with a departing employee who claims rights in something they built.
• An EOR change or termination. If you switch providers, does the IP assigned to the old EOR come with you?

How to fix it

Four layers, all of which you should have:

1. Employee-level assignment with an explicit onward assignment. The employment contract between the EOR and the employee should assign IP to the EOR and explicitly contemplate onward assignment to the client, naming your entity or defining it clearly. Ask to review the actual clause, not a summary.

2. Client-level assignment in the services agreement. Your agreement with the EOR should contain a present, unconditional assignment of all IP created by EOR employees in performing services for you, to your named entity. Present-tense assignment ("hereby assigns") is generally stronger than a promise to assign in future. Have your IP counsel review the wording.

3. A direct agreement between the employee and your entity. Many companies have EOR-employed staff sign a direct confidentiality and IP assignment agreement with the client entity, alongside their EOR employment contract. Get advice on doing this carefully — you want the IP and confidentiality protection without creating facts that muddy who the employer is. Counsel can help you draft it so it supplements rather than contradicts the employment relationship.

4. Practical hygiene. Code in your repositories under your organisation's account. Documents in your systems. Design files in your workspace. Do not let work product accumulate in vendor-controlled or personal environments. Practical control of the artefacts is not a substitute for legal assignment, but it prevents a bad situation from becoming worse.

Confidentiality and trade secrets

The same logic applies. If the confidentiality obligation runs only to the EOR, your ability to enforce it directly against a departing employee who took your customer list is weaker than it should be. Make sure your entity is either a party to, or an expressly named beneficiary of, the confidentiality undertaking.

Moonlighting and conflicts

If exclusivity and outside-work restrictions matter to you, confirm they are in the EOR's standard contract at the standard you require. Vendor templates vary widely. Some are thin. Ask to see the template before you sign the master agreement, and negotiate amendments if the clauses do not meet your bar.

---

Data Privacy and Employee Data Under an EOR Arrangement

India has a data protection regime governing the handling of personal data, and employee data sits squarely inside it. The detail of applicability, notice, consent and cross-border transfer is evolving and rule-dependent, so treat the following as a checklist of questions to ask, not a statement of legal requirements. Confirm the current position with privacy counsel.

An EOR arrangement necessarily involves personal data moving in several directions: identity documents, bank details, salary information, tax declarations, health information for insurance, and performance-adjacent information flowing back to you.

Practical questions to settle before you sign:

• Who is the controller and who is the processor? Both parties handle employee data for different purposes. Your agreement should say who determines the purposes of processing for each category, and who is accountable for what.
• What data flows to you, and why? You need enough to manage people and reconcile costs. You probably do not need Aadhaar numbers or bank account details. Minimise deliberately.
• Where is the data stored and processed? Ask for the actual answer — vendor, sub-processor, cloud region — not a reassurance.
• What happens on cross-border transfer? If employee data leaves India to your systems abroad, understand the notice and safeguard expectations that apply.
• What notices does the employee receive? They should understand who is processing their data and for what. The EOR issues the notice as employer, but you should see it.
• Which sub-processors are involved? Payroll engines, benefits brokers, background verification vendors, insurers. Ask for the list and for a change-notification obligation.
• What are the security commitments? Access controls, encryption, breach notification timelines, audit rights, and certifications if any.
• What happens at exit? Retention periods, deletion obligations, and what you get back in what format when you leave the vendor.

If you are a European or UK company, your own GDPR obligations travel with you. India-based employee data processed for your purposes is likely in scope, and you will need appropriate transfer mechanisms and processing terms. Get that reviewed alongside the commercial contract, not after it.

---

Equity and ESOP Grants to EOR-Employed Staff

This is the second thing companies routinely get wrong, and it has no clean solution.

The difficulty is structural. Most equity plans are drafted to grant options to employees of the company or its subsidiaries. Someone employed by an unrelated EOR is neither. Your plan documents may simply not permit the grant.

The complications compound:

Plan eligibility. Check the actual definition of "eligible participant" in your plan. If it covers only employees and directors of the company and its subsidiaries, an EOR-employed person does not qualify. Some plans include consultants or service providers; some do not.

Indian regulatory dimensions. Grants of foreign securities to individuals in India, and the remittance flows involved when they exercise or sell, interact with exchange control rules. The employer-employee relationship matters to how some of these provisions are read. Do not assume the treatment that applies to a subsidiary's employees automatically applies here.

Tax treatment and withholding. Where an employer grants equity to an employee, there is generally a taxable perquisite event and an obligation to withhold. When the granting entity is not the employer, the mechanics of who reports what, and who withholds, become genuinely murky. The EOR may not be willing or able to process a perquisite it did not grant. Coordinating this needs your tax advisers and the vendor at the same table, early.

Vesting and continuity. If the person later transfers to your own India entity, does their vesting clock continue? If the equity was granted as an alternative instrument rather than a plan option, does it convert? Write the answer down at grant time, not at transfer time.

Practical alternatives. Companies commonly use cash-settled instruments — phantom equity, stock appreciation rights, or a contractual cash bonus tied to a liquidity event — for EOR-employed staff. These avoid the securities and exchange control complexity but change the economics and the tax profile for the employee, and they need clear documentation. Advisers should design the instrument; do not improvise it.

Communicate honestly. The worst version of this is telling a candidate "you'll get options" and then discovering nine months later that the grant cannot be made. If equity is genuinely part of the package, resolve the mechanism before the offer letter goes out. If it cannot be resolved yet, say so and commit to a defined alternative in writing.

If equity is central to how you attract senior talent in India, that fact alone is a strong argument for building your own entity sooner rather than later.

---

Vendor Due Diligence: What to Ask Before You Sign

Not all EORs are equivalent. The differences are mostly invisible in a sales deck and extremely visible eight months in.

Structure and substance

• Does the vendor own an Indian entity, or is it sub-contracting to a local partner? Many global platforms operate in India through a third-party partner. That is not automatically bad, but it adds a link to the chain. Ask who the actual employer on the contract will be, and get the entity name.
• How long has that entity operated in India, and how many employees does it carry? Longevity and scale correlate with process maturity.
• Which registrations does it hold, and in which states? If you plan to hire in a state where the vendor has no footprint, ask exactly how that will be handled.

Compliance track record

• Ask for the compliance calendar they run and evidence of filing discipline.
• Ask whether they will provide monthly or quarterly compliance evidence — challans, filing acknowledgements, register extracts — as standard.
• Ask what happens if they miss a filing. Who pays the penalty? Is there an indemnity, and is it capped at a level that makes it meaningless?

Employment contract quality

• Review the actual template before signing the master agreement.
• Check: notice period, probation, confidentiality scope and duration, IP assignment and onward assignment, non-solicitation, outside-work restrictions, governing law, and dispute resolution.
• Check whether you can negotiate role-specific variations, and whether that costs extra.

Payroll accuracy and service levels

• What is the committed payroll accuracy standard, and how is an error defined and remedied?
• What is the monthly cut-off date for inputs, and how rigid is it?
• What is the guaranteed salary credit date?
• Is there a named account manager, or a ticket queue?
• What are response and resolution times for employee queries — and can employees raise queries directly?

Insurance and benefits

• What is the standard group medical cover, and can you upgrade it?
• Are dependants covered? Parents? What are the sub-limits and waiting periods?
• How are premium increases at renewal handled and communicated?

Offboarding and termination

• What is the process and timeline for a termination, and what notice do they require from you?
• Do they require pre-funding of severance? How much and when?
• Will they support you through a contested exit, or will they hand you the problem?
• Is there a separate offboarding fee?

Data security

• Where is data hosted, and who are the sub-processors?
• What are the access controls and breach notification commitments?
• What certifications, if any, do they hold, and are they current?

The termination and transfer clauses — read these twice

This is where the leverage sits, and it is where standard vendor paper is often one-sided.

• What notice do you need to give to exit? Anything longer than 60 days for the master agreement is worth negotiating.
• Is there a conversion or transfer fee if you move an employee from the EOR to your own India entity? Some contracts contain substantial buyout clauses. Negotiate this at signature, when you have leverage — not at transfer, when you have none.
• Is there a non-solicitation clause that prevents you from hiring "your own" employee into your entity? This exists in real contracts. Strike it or carve out an exception for transfers to your own group entities.
• What data and documentation do you get on exit? You want employment records, payroll history, statutory filing evidence and leave balances, in usable format, at no extra charge.
• How is liability allocated for compliance failures that occurred during the EOR's tenure but surface after you have left?

Quick due-diligence scorecard

Ask for two references from clients of similar size and geography, and actually call them. Ask those references one question in particular: what went wrong, and how did the vendor handle it?

---

How to Exit an EOR and Move to Your Own India Entity

Most companies that use an EOR successfully will one day leave it. Handled well, employees barely notice. Handled badly, you get resignations, a gratuity dispute and a PF mess.

The core principle is continuity of service. When someone moves from EOR employment to your entity, they are technically resigning from one employer and joining another. Left alone, their service clock resets — which can affect gratuity eligibility, leave balances, notice periods and, more than anything, how they feel about the change. Plan the transfer so that nothing they have earned disappears.

Step-by-step transition plan

Step 1 — Decide and set the date (T-16 weeks). Fix a target transfer date. Align it to a month start, and preferably to the start of a financial quarter or the financial year to simplify tax and Form 16 handling. Confirm the EOR notice period required and work backwards.

Step 2 — Read the EOR contract properly (T-16 weeks). Notice period, transfer fee, non-solicit clause, data return obligations, final invoice and deposit refund mechanics. Resolve disputes here before you announce anything.

Step 3 — Incorporate and register (T-14 to T-6 weeks). Company incorporation, PAN, TAN, bank account, GST if applicable, professional tax registration in the relevant states, shops and establishments registration, and EPFO/ESIC registration. Timelines vary considerably by state and by how quickly documents and signatories move. Assume it takes longer than the optimistic estimate.

Step 4 — Design compensation and policy (T-10 weeks). Do not simply copy the EOR structure. This is your chance to design salary structuring, leave policy, notice periods and benefits the way you want them. Model the net pay impact for every employee — if anyone's take-home drops because of restructuring, fix it before you communicate, not after.

Step 5 — Set up your HRMS and payroll (T-8 weeks). You are about to own payroll, statutory computation, filings, leave, attendance and documentation. Get the system in place, configured and tested with parallel-run data before go-live. Do not plan to run the first payroll on your own entity in a spreadsheet.

Step 6 — Communicate (T-6 weeks). This is the step companies rush and regret. Tell people early, in person or on a call, then in writing. Explain what changes (the employer name, the payroll system, the payslip format, possibly the insurance policy) and what does not (their role, their manager, their salary, their team, their service continuity). Expect anxiety. Answer it directly.

Step 7 — Issue new offer letters and consents (T-5 weeks). New employment contracts with your entity, dated for the transfer. Include an express clause recognising prior service with the EOR for the purposes of gratuity, leave and notice, so continuity is documented rather than assumed. Have counsel draft this language; it is the crux of the whole exercise.

Step 8 — Handle leave balances (T-4 weeks). Two options: encash accrued leave at the EOR, or carry balances across. Carrying across preserves goodwill; encashing is administratively simpler. Whichever you choose, decide it as policy, communicate it clearly, and apply it consistently.

Step 9 — Handle gratuity (T-4 weeks). Coordinate between vendor and counsel. Depending on the arrangement, accrued gratuity may be settled by the EOR at exit, or prior service may be recognised by your entity with the liability transferring. Both are seen; the right answer depends on the contracts and the facts. Whatever you agree, document it, and tell the employee in writing what has been recognised.

Step 10 — PF continuity via UAN (T-3 weeks). This is usually the smoothest part. The employee's Universal Account Number stays with them across employers. Their new PF membership under your establishment code links to the same UAN, and past accumulations can be transferred online. Make sure exit dates are correctly marked by the EOR — an unmarked exit date is the single most common cause of transfer delays. Also confirm whether anyone was drawing a higher-than-statutory contribution, and replicate it if so.

Step 11 — Insurance transition (T-2 weeks). Your new group policy must be live from day one of the transfer, with no gap. Confirm waiting periods, pre-existing condition treatment and continuity credit with the insurer — a gap or a reset can be genuinely harmful for someone mid-treatment.

Step 12 — Final payroll and cutover (T-0). Run a clean final payroll with the EOR, including full-and-final settlement. Collect Form 16 or the part-year equivalent from the EOR so employees can file correctly. Ensure the employee's tax declarations for the year are carried forward so annual withholding is computed on total income, not restarted.

Step 13 — Close out with the vendor (T+2 to T+8 weeks). Recover deposits, obtain final compliance evidence and filing acknowledgements, collect the employee data package, and get written confirmation that the arrangement is terminated. Archive everything — you may need it in a diligence process years later.

Transition risk table

---

Implementation Timeline: EOR vs Own Entity

Elapsed times below are illustrative planning ranges, not commitments. Actual timelines depend on state, document readiness, signatory availability and vendor capacity.

The gap in the last row is the honest case for an EOR. If you have a candidate with a competing offer, months is not an option.

---

Common Mistakes With an Employer of Record in India

1. Treating the EOR as a compliance guarantee. The vendor administers compliance; the commercial and reputational consequences of failure still land on you. Ask for filing evidence monthly and actually look at it.

2. Never revisiting the decision. The most expensive EOR is the one you have been on for four years because nobody re-ran the numbers. Set a calendar reminder and a headcount trigger on day one.

3. Ignoring IP assignment. Covered at length above. It is the highest-severity, lowest-visibility mistake in this entire model.

4. Promising equity you cannot grant. Resolve the mechanism before the offer letter.

5. Comparing quotes on headline fee alone. Deposits, severance funding, gratuity treatment, offboarding fees, benefit margins and FX spread can change the ranking entirely. Compare fully loaded annual cost.

6. Signing a contract with a transfer buyout or a non-solicit that blocks your own exit. Read the clause. Negotiate it before signature.

7. Assuming the EOR solves permanent establishment risk. It does not, by itself. Get tax advice on the specific role, especially for sales and business development positions with contracting authority.

8. Skipping the employment contract template review. You are handing your people a contract you have never read. Read it.

9. Poor communication at transfer. Employees hear "you're being transferred to a different company" and update their CV. Explain continuity, in person, early.

10. Using an EOR to dodge obligations. It does not work that way. The obligations exist regardless; only the administration moves.

11. Letting the EOR own the employee relationship. People should feel they work for you. If the vendor becomes the face of HR, engagement suffers and so does retention.

12. No named internal owner. Somebody on your side must own the vendor relationship, check the invoices, verify the filings and manage the calendar. If it is nobody's job, it does not happen.

13. Forgetting state variation. India's employment landscape varies by state — professional tax, shops and establishments rules, leave entitlements, minimum wages. A policy that works in Karnataka may not be right in Maharashtra. Confirm state-specific applicability.

14. Not planning the exit at the start. Design the off-ramp when you sign the on-ramp.

---

When an Employer of Record Is the Wrong Answer

An honest guide has to include the cases where the answer is no.

When you already have an Indian entity. If you have a functioning entity with registrations, adding an EOR usually just adds cost and fragmentation. What you probably need is a good HRMS and payroll system, or a payroll processing partner — not a second employer.

When headcount will be substantial. Past a certain size, per-head fees dwarf entity overhead. If your plan says 25 people in India within 18 months, start the entity now and bridge with an EOR only for hires you cannot wait for.

When India is strategically central. Building a GCC, a primary engineering hub, or a business that will contract with Indian customers means you need your own presence anyway — for banking, for customer contracts, for employer brand, for statutory standing.

When you need a distinct employer brand. Senior candidates in competitive markets notice when the offer letter comes from a company they have never heard of. It is a real recruiting friction at the top of the market.

When equity is core to the package. The complications described above do not disappear with careful drafting; they are structural.

When the work is genuinely project-based and independent. If you need a specialist for a defined deliverable over three months, and they have other clients and control their own methods, a properly drafted contractor agreement may be the honest answer. Get counsel to confirm the classification holds on your facts.

When you need highly customised employment terms. Unusual notice periods, bespoke incentive structures, complex restrictive covenants — vendor templates often cannot accommodate these, and forcing them creates a contract nobody fully owns.

When cost is the only reason you are considering it. If you are choosing an EOR because it looks cheaper than an entity, model it properly first. Beyond a handful of people, it usually is not.

---

Frequently Asked Questions About Using an Employer of Record in India

Is using an employer of record in India legal?

Yes. Third-party employment arrangements are an established commercial practice in India, and the EOR is a properly registered Indian employer meeting statutory obligations for the employees on its rolls. What matters is that the arrangement is real: the EOR genuinely employs and pays the person, the statutory contributions are actually made, and the paperwork reflects the substance. Where the arrangement resembles supply of contract labour to your premises, additional regulatory requirements may apply — confirm the position for your specific setup with employment counsel.

How fast can an EOR onboard someone in India?

Once the master services agreement is signed and the employee's documents are collected, onboarding is typically measured in days rather than weeks. The slow parts are usually your own — contract negotiation, legal review, procurement and vendor security assessment. If speed is the reason you are choosing an EOR, start the contracting process before you have made the offer.

Does an EOR protect my company from permanent establishment risk in India?

Not automatically. An EOR removes the need for you to be a registered employer, but PE analysis turns on what the person actually does in India — whether they habitually conclude contracts for the foreign company, and whether a fixed place of business exists. A salesperson closing deals may create exposure regardless of who signs their payslip. This is a genuine tax question with real financial consequences, and it should be assessed by qualified Indian tax counsel against your specific facts and the applicable tax treaty.

Can I convert an EOR employee to my own entity later?

Yes, and most companies eventually do. The mechanics involve a resignation from the EOR and a fresh appointment with your entity, with prior service expressly recognised for gratuity, leave and notice purposes. PF continues seamlessly on the same UAN. Check your EOR contract before signing for transfer fees or non-solicitation clauses that could make this expensive or awkward, and negotiate them out at the start.

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

An EOR is the sole legal employer, so you do not need your own Indian entity. A PEO, in the classic co-employment sense, supports a company that already has its own entity and employer registrations. In practice, Indian vendors use both terms loosely. The clarifying question is always the same: whose entity signs the employment contract, and whose provident fund registration receives the contributions?

How much does an EOR cost in India?

Pricing is usually either a flat per-employee-per-month fee or a percentage of payroll, and it varies widely by vendor, headcount, salary level and contract term. We deliberately do not publish figures, because any number would mislead. What you should do is collect at least three quotes, convert them all to the same basis, and add the items that are not in the headline: deposits and pre-funding, benefit premiums, severance funding, gratuity treatment, statutory bonus, onboarding and offboarding charges, and FX cost. Compare fully loaded annual cost per employee, not the sticker rate.

Should an Indian company use an EOR for hiring in another state?

It can make sense, particularly for small or time-bound teams in states where you have no establishment and no registrations. The EOR already holds the state registrations and runs the filing calendar, so you get reach without adding a permanent compliance footprint. It stops making sense once headcount in that state grows enough to justify registering yourself, or once the location becomes strategically permanent. And it is never a legitimate way to reduce statutory obligations — those apply either way.

---

Making the Decision

Strip away the vendor marketing and the decision is not complicated.

Use an employer of record in India when you have no Indian entity, headcount will stay small for now, the time horizon is uncertain, speed matters more than cost, and the work is not the kind that creates your crown-jewel intellectual property. Use it as a bridge — deliberately, with a review date and a headcount trigger written into the plan.

Build your own entity when India is strategically important, headcount is heading past the crossover point in your own cost model, you need control over policy and contracts, equity is central to your offer, or the team is building the core of your product.

Do both when the answer is "entity, eventually" but the candidate you want starts next month. Run the EOR as a bridge while incorporation proceeds, then transfer people cleanly using the plan above. This hybrid is common and, for most growing companies, it is the right answer.

Whichever route you take, the same three disciplines separate the companies that do this well from the ones that do it painfully: read the contracts you sign, get IP assignment right on day one, and verify every tax, PE and employment-law question with advisers who know Indian law and know your facts.

Where CozyHR fits

CozyHR is not an employer of record. We are the HR and payroll system you run once you have your own India entity — and, for many teams, the system you run alongside an EOR to hold everything the vendor does not.

That means Indian payroll with statutory computation for PF, ESI, professional tax and TDS, payslips and Form 16, attendance and leave built for Indian state rules, employee records and documents, onboarding and offboarding workflows, expense and reimbursement handling, and self-service for your people.

If you are on an EOR today and planning your own entity, CozyHR is what you stand up in Step 5 of the transition plan — configured, tested and running in parallel before the cutover, so your first payroll on your own entity is uneventful. If you already run an Indian entity and are outgrowing spreadsheets and disconnected tools, it is the system of record your compliance calendar depends on.

Explore CozyHR and see how it fits your India setup. Bring your questions about the transition — we have watched a lot of teams make it.

This article is general information for HR and finance teams, not legal, tax or accounting advice. Employment law, exchange control and permanent establishment analysis in India are fact-specific and change over time. Verify your specific circumstances with qualified Indian legal and tax advisers before acting.