Employer of Record (EOR) in India: When SMBs Should Use One

Employer of Record (EOR) in India: When SMBs Should Use One

Employer of Record (EOR) services have moved from a niche workaround to a mainstream hiring route in India. Global companies use EORs to hire Indian talent without opening an entity; Indian startups use them to hire in states where they have no registrations, or to employ overseas staff without foreign subsidiaries. But an EOR is not a magic compliance eraser, and for many SMBs it is the more expensive option beyond a certain team size. This guide explains what an EOR actually is, how it differs from staffing agencies, PEOs, and contractors, what it costs, where the compliance risk really sits, and a practical decision framework for founders and HR managers deciding between EOR, direct employment, and building payroll in-house.

As always with statutory matters: rules, thresholds, and rates change. Treat the compliance descriptions here as orientation and verify current requirements with official sources or a qualified professional before acting.

What an Employer of Record Actually Is

An Employer of Record is a third-party organisation that becomes the legal employer of a worker on paper, while the worker performs day-to-day duties for you — the "client" company. The EOR:

• issues the employment contract in its own name;
• runs payroll and deposits statutory contributions (PF, ESI, professional tax, TDS on salary, and so on);
• administers benefits such as group health insurance and gratuity;
• handles statutory registers, filings, and labour law compliance for that employment;
• processes onboarding, leave records, payslips, and full-and-final settlement.

You retain direction and control of the work: what the person does daily, their targets, reviews, and tooling. You pay the EOR a monthly invoice covering the employee's gross cost plus the EOR's fee.

The key mental model: the EOR owns the employment; you own the work.

EOR vs PEO vs staffing agency vs contractor — the terms people mix up

Two clarifications that matter in India:

1. "PEO" in Indian sales conversations usually means EOR. The US-style co-employment PEO model doesn't map cleanly onto Indian law. Judge the offering by the contract: who signs the appointment letter, whose PF code is used, who deducts TDS.
2. Contract staffing under the CLRA framework is not the same as EOR. If workers are deployed at your premises through a contractor, principal-employer obligations can attach to you — licence checks, ensuring wage payment, and welfare provisions. Many EOR arrangements for white-collar remote staff sit outside classic CLRA territory, but the analysis is fact-specific. Take advice if your EOR-hired staff work at your physical site.

Why Companies Use EORs in India

Use case 1: Global company hiring Indian talent without an entity

Setting up an Indian subsidiary involves incorporation, PAN/TAN, GST where applicable, PF and ESI registrations, professional tax registrations state by state, a bank account, and ongoing secretarial compliance. That takes time and ongoing cost. An EOR compresses time-to-hire from months to days. This is the classic use case and the reason the category exists.

Use case 2: Indian SMB hiring in a new state

Professional tax, shops and establishments registration, and labour welfare fund obligations are state-specific. An SMB registered in Karnataka hiring one salesperson in West Bengal faces registrations for a single employee. Some companies use a domestic EOR to employ that one person until the team in the state grows enough to justify direct registrations.

Use case 3: Indian company hiring overseas

Hiring a designer in the Philippines or a sales rep in Dubai without opening entities there — a mirror image of use case 1, using a global EOR's local entities.

Use case 4: Trial and interim structures

Testing a market before committing to an entity; bridging employment while your own entity's registrations are in progress; employing people during an acquisition transition.

What an EOR does not solve

• Permanent establishment (PE) tax risk. If your EOR-employed team in India habitually concludes contracts or performs core revenue functions for a foreign company, tax authorities can still argue the foreign company has a taxable presence in India. The EOR does not immunise you; structure roles carefully and take tax advice.
• IP assignment nuances. IP typically flows employee → EOR → you via contract. Ensure the EOR agreement has watertight IP and confidentiality provisions naming you as beneficiary.
• Culture and management. The EOR does none of your performance management, engagement, or retention work.
• Data protection. You remain accountable for how employee personal data is processed across you and the EOR — align your contracts with current Indian data protection requirements.

What EORs Cost — and the Break-Even Math

EOR pricing is typically either a flat fee per employee per month or a percentage of gross salary. Flat fees for India commonly land in the range of a few hundred US dollars per employee per month for global providers, with domestic providers often cheaper; percentage models vary widely. On top of the fee, you fund the full employment cost: gross salary, employer PF contributions, gratuity accruals, insurance premiums, and any statutory bonus.

A simplified comparison for a foreign company employing five people in India (illustrative structure, not current market quotes):

The break-even intuition most CFOs land on: for small teams (roughly 1–10 people) or short horizons, the EOR usually wins; past 15–25 employees with a long-term commitment, an own entity usually becomes cheaper, because entity costs are largely fixed while EOR fees scale per head. Model your own numbers — the crossover depends on the EOR's pricing, your state footprint, and how much internal HR capacity you have.

Hidden costs to probe in EOR contracts:

• FX spreads on invoicing for cross-border arrangements.
• Deposit or advance requirements (often one to two months of payroll).
• Offboarding/termination administration fees and notice-period funding.
• Charges for benefits administration or non-standard benefits.
• Fees for supporting employee loans, visa letters, or verification requests.

Compliance: What Moves to the EOR and What Stays With You

A useful way to run this analysis is a responsibility matrix. In a well-drafted India EOR arrangement:

EOR is responsible for: appointment letters compliant with applicable shops and establishments rules; payroll processing; PF, ESI, professional tax, and LWF deposits and returns under its own registrations; TDS on salaries and Form 16; gratuity and statutory bonus administration; maternity benefits administration; leave records per applicable state law; POSH compliance machinery for its employees (though your workplace policies still apply to conduct within your teams); statutory registers; and full-and-final settlements.

You remain responsible for: day-to-day supervision and a safe working environment; anti-harassment culture and reporting channels in your teams; performance management and the decision to hire or exit (executed by the EOR); data protection for the information you process; expense policies; IP protection in the work product; and — critically — not treating the arrangement as a fiction. If you sign offer letters on your letterhead, pay allowances off the books, or promise employment terms directly, you create co-employment or sham-contracting risk where a court or authority may treat you as the real employer with all attendant liabilities.

Questions to ask any EOR before signing:

1. Do you employ through your own Indian entity, or subcontract to a local partner? (Subcontracting adds a layer of risk and margin.)
2. Under whose PF establishment code will contributions be deposited? Can we get contribution challans/ECR evidence monthly?
3. How do you handle state-specific items — professional tax slabs, LWF, leave rules — for remote employees in different states?
4. What is your process and SLA for full-and-final settlement on exit?
5. How are gratuity liabilities funded and what happens if we later migrate employees to our own entity?
6. Can employees be transferred to our entity later without breaking continuity of service for gratuity purposes? Get the mechanism in writing.
7. What insurance (employer liability, cyber) do you carry, and what indemnities do we get for compliance failures on your side?

Employee Experience Under an EOR — Don't Skip This

From the employee's perspective, EOR employment can feel second-class if handled carelessly: a payslip from a company they never interact with, confusion about who approves leave, and anxiety about what "employed by X, working for Y" means for home loans and visa applications. Mitigations:

• Explain the structure candidly in the offer conversation; banks and embassies deal with EOR letters routinely, and the EOR should provide employment verification letters promptly.
• Mirror your direct employees' benefits (insurance tiers, leave policy, holidays) so EOR staff aren't visibly worse off.
• Keep them inside your performance, recognition, and ESOP-equivalent frameworks (cash LTIPs or phantom stock are often used where direct ESOPs are impractical).
• Run onboarding yourself; the EOR does the paperwork, but the welcome is yours.
• Ensure a single HR point of contact on your side who owns EOR-employee queries so people don't ping-pong between two HR teams.

Attrition among EOR-hired staff is often driven less by the structure and more by ambiguity around career paths. Publish how and when EOR employees convert to direct employment if you build an entity.

Decision Framework: EOR vs Direct vs Contractor

Work through these five questions:

1. Do we have (or want) a legal entity where the person will be employed? No entity and no plans → EOR or contractor. Entity exists → direct employment is usually cheapest and cleanest.

2. Is the role genuinely independent? If the person sets their own hours, uses their own tools, serves multiple clients, and delivers outcomes rather than attending your standups — contractor can be legitimate. If they work like an employee, classify them as one (via EOR or directly). Misclassification back-taxes and penalties outlast any short-term savings.

3. What is the time horizon and team-size trajectory? One to ten people, or a 6–18 month experiment → EOR. A committed multi-year build to dozens of employees → start entity setup now and use an EOR only as a bridge.

4. How exposed are we to PE/tax risk? Revenue-generating roles (sales closing contracts) for a foreign parent raise PE questions regardless of the EOR. Get tax advice before, not after.

5. Can our HR ops actually run direct employment well? Direct employment in India means PF/ESI/PT/TDS cycles, state-wise leave and holiday rules, and statutory registers. With a competent HRMS and payroll system this is very manageable for an SMB — but if you have zero HR ops capacity and need someone hired next week, the EOR buys you time.

Migration: moving from EOR to your own entity

When you cross break-even, plan the migration deliberately:

1. Incorporate and complete registrations (PF, ESI, PT, S&E) well before the target transfer date.
2. Negotiate tripartite transfer letters preserving continuity of service, leave balances, and gratuity accrual — or have your entity contractually recognise prior service.
3. Align compensation structure to your own salary template; explain any changes in take-home caused by different PF bases or benefit structures.
4. Move payroll history, investment declarations, and Form 16 responsibilities cleanly at a financial-year boundary if possible; mid-year transfers mean two Form 16s for employees.
5. Onboard everyone into your HRMS on day one — attendance, leave, payslips — so the experience improves visibly with the move.

Running the In-House Alternative Well

Since the EOR-vs-direct decision often hinges on how hard direct employment feels, it's worth stating: for white-collar teams, a modern HRMS with integrated payroll makes direct employment far less daunting than it looks. The monthly cycle — attendance and leave finalisation, payroll run, PF ECR upload, ESI contribution, PT payment, TDS deposit, payslip publication — is a repeatable checklist, most of which good software automates or reminds you about. The genuinely tricky parts (state-specific rules, year-end TDS, F&F) are exactly where software guardrails help a small HR team punch above its weight.

A pragmatic hybrid many Indian SMBs land on: direct employment in the two or three states where most of the team sits, EOR for the odd single hire in a far-flung state or country, and genuine contractors for genuinely independent work — each relationship papered correctly.

Selecting an EOR Provider: An Evaluation Scorecard

Once you've decided an EOR fits, provider selection determines whether the experience is smooth or a monthly firefight. Score candidates on six dimensions:

1. Entity model (weight: high). Own Indian entity beats a partner network. With subcontracted models, ask who actually signs the appointment letter and holds the PF code, and what happens to your employees if the partner relationship ends.

2. Compliance depth (high). Test them with specifics: How do you handle professional tax for an employee in Madhya Pradesh vs Maharashtra? What's your process when an employee's ESI eligibility changes mid-year due to a salary revision? How do you compute and fund gratuity? Vague answers to concrete questions are disqualifying.

3. Payroll accuracy and transparency (high). Ask for a sample invoice and a sample payslip. The invoice should break out gross salary, each employer contribution, insurance, and the fee — beware bundled "total cost" invoices that hide margins in statutory lines. Ask for their payroll error rate and correction SLA.

4. Employee experience (medium). What does onboarding look like for the employee? Is there a self-service portal for payslips, tax declarations, and leave? How fast are verification letters issued? Your employer brand rides on their responsiveness.

5. Commercials (medium). Fee structure, FX handling, deposit requirements, offboarding charges, price escalation clauses, and volume discounts. Flat per-employee fees are easier to forecast than percentage-of-salary pricing, which silently taxes your increments.

6. Exit and portability (high, and most often ignored). How easily can you move employees to your own entity or another provider? Look for contract terms on transfer cooperation, non-solicitation clauses that could block you from hiring "their" employees (negotiate these away — the talent is yours), and data handover formats.

Run a two-week pilot with one non-critical hire if the provider allows it. You will learn more from one payroll cycle than from ten sales demos.

Contract Clauses That Matter More Than the Fee

When the master services agreement lands, these are the clauses worth negotiating hard:

• Employment cost pass-through transparency: the right to audit statutory deposits made for your workers, with monthly evidence (ECR acknowledgements, PT challans, TDS returns relevant to salaries).
• Indemnity for compliance failures: if the EOR misses a deposit or files late, penalties and interest should sit with them, not you.
• IP and confidentiality flow-down: the employee's IP assignment and confidentiality obligations must be enforceable by you as a named third-party beneficiary, not just by the EOR.
• Termination mechanics: how much notice you owe the EOR to exit an employee, what costs you fund (notice pay, leave encashment, gratuity where applicable), and F&F timelines.
• Employee transfer rights: an explicit, pre-priced mechanism to convert employees to your entity with continuity of service and without "conversion fees" that feel like ransom.
• Data protection: processing roles, security standards, breach notification timelines, and data return/deletion on exit, aligned with current Indian data protection law.
• Liability caps: EORs will cap liability at a few months of fees; push for carve-outs on statutory non-compliance, employee claims caused by their errors, and confidentiality breaches.
• Insurance: evidence of employer liability and professional indemnity cover.

If a provider resists transparency or transfer clauses, that is signal, not noise.

A Worked Scenario: SaaS Startup, 12 Hires, 18 Months

Consider a UK SaaS company building an India engineering pod: 4 engineers now, scaling to 12 within a year, likely permanent presence if the pod works.

Months 0–3: EOR employs the first 4 engineers. Time-to-offer is days; the company validates delivery quality without touching Indian bureaucracy. Meanwhile it starts entity incorporation in parallel — because the trajectory (12+ people, permanent intent) already suggests the entity will win economically.

Months 4–9: Team grows to 9 under the EOR. The company negotiates its EOR contract with transfer clauses from day one, so no surprises later. It stands up PF, ESI, PT, and shops-and-establishments registrations under the new entity and selects an HRMS with integrated payroll, configuring salary structures to mirror what employees already receive.

Months 10–12: Tripartite transfer letters move all employees to the Indian entity at the financial-year boundary, preserving continuity of service and leave balances. Employees get a better self-service experience (payslips, tax declarations, leave, attendance in one app), and the monthly per-head EOR fee disappears.

Month 18: The pod is 14 people employed directly. Total cost is materially lower than staying on the EOR, and the company controls its own employment brand, ESOP grants, and policies.

The lesson: the EOR was the right first move and the wrong permanent one — and because the exit was planned at signing, the migration was administrative rather than dramatic.

Where Your HRMS Fits When Some Staff Are on an EOR

A subtle operational question for hybrid teams: the EOR has its portal for payslips and statutory documents, but your company still needs one source of truth for the work side of people operations. Most SMBs solve this by keeping every worker — direct, EOR, and contractor — inside their own HRMS for attendance, leave workflows, holiday calendars, org charts, goals and reviews, asset tracking, and document acknowledgements, while payroll executes in two lanes: your payroll engine for direct employees, and a monthly input file to the EOR for the rest.

Practical setup tips:

• Tag employment type (direct/EOR/contractor) as a custom field so reports can slice cost and headcount by lane.
• Run leave and attendance approvals in your HRMS and export the EOR's required inputs (LOP days, new joiners, exits, variable pay) as a monthly cut-off report — this prevents the classic error of the EOR paying full salary to someone on unpaid leave.
• Keep onboarding checklists unified so EOR hires get the same laptop, access, policy acknowledgements, and buddy assignment as direct hires.
• When employees migrate from EOR to direct, their history — leave balances, documents, review records — already lives in your system, making the switch invisible to them.

This "one HRMS, two payroll lanes" pattern keeps the employee experience consistent and your analytics whole, whatever the legal plumbing underneath.

Common Mistakes to Avoid

• Signing offer letters on your own letterhead "just to move fast" while the EOR papers catch up. You may have just become the legal employer.
• Paying allowances or bonuses directly to EOR employees off-invoice. All compensation must flow through the EOR's payroll, or you create tax and co-employment exposure.
• Ignoring state-level details for remote hires. An EOR employee in Kolkata triggers West Bengal professional tax and LWF rules regardless of where your office is; confirm your provider handles the employee's actual work state.
• Treating the EOR fee as the whole cost. Gratuity accrual, statutory bonus where applicable, insurance, and employer PF sit on top of gross salary — budget total cost of employment, not CTC-as-quoted.
• Forgetting POSH and workplace policies. The EOR runs statutory machinery for its employees, but conduct inside your team is your culture and, in practice, your problem. Extend your policies, training, and reporting channels to EOR staff explicitly.
• No exit plan. Migrating 20 people off an EOR without transfer clauses, at mid-year, with gratuity continuity disputes, is a project nobody enjoys. Plan the exit when you sign the entry.

Frequently Asked Questions

1. Is using an EOR legal in India? Yes — third-party employment arrangements are lawful when structured properly. The risks are in the details: sham contracting, contract-labour obligations for on-premises deployment, and tax/PE exposure for foreign companies. Paper the arrangement correctly and take advice for your specific facts.

2. Who handles PF and ESI for EOR employees? The EOR, under its own registrations. Ask for monthly evidence of deposits (ECR acknowledgements, challans). If contributions are missed, the practical pain lands on your team members — so verify, don't assume.

3. Can an EOR employee get ESOPs in our company? Directly granting ESOPs to someone who isn't your employee is legally awkward in many structures. Companies typically use phantom stock, SARs, or cash long-term incentives for EOR staff, converting to real options when the person moves to a direct entity. Take advice on your plan documents.

4. What happens if we want to terminate an EOR employee? You decide; the EOR executes per Indian law and the employment contract — notice or pay in lieu, F&F settlement, and any state-specific requirements. You fund the costs. Ensure the EOR contract has clear SLAs, because a botched exit is your reputational problem.

5. Does an EOR protect a foreign company from permanent establishment risk? No. PE analysis looks at what your people actually do in India, not who signs their payslip. Sales and contract-concluding roles need tax structuring regardless of the EOR.

6. EOR vs contractor for a single hire in another state — which is safer? If the person will work like an employee, EOR (or direct employment with the extra registrations) is safer than a contractor arrangement that misclassifies them. Contractor status is for genuinely independent work, not a cost-saving label.

7. How quickly can an EOR onboard someone in India? Established providers routinely issue compliant offer letters within days once background checks and documents are in. Your bottleneck is usually candidate notice periods, not the EOR.

8. Will EOR employment hurt an employee's home loan or visa applications? Generally no — lenders and consulates see EOR arrangements regularly. What matters is clean documentation: employment verification letters, payslips, and Form 16, which a competent EOR provides promptly.

Quick Glossary

• EOR (Employer of Record): third party that legally employs workers who perform work for your company.
• PEO (Professional Employer Organization): in strict usage, a co-employment model; in Indian sales usage, often a synonym for EOR — verify contractually.
• CLRA: India's contract labour regulation framework governing workers deployed through contractors, with principal-employer obligations.
• PE (Permanent Establishment): a taxable presence a foreign company can acquire in India based on its activities — not cured by using an EOR.
• Tripartite transfer: an agreement between employee, EOR, and your entity moving employment while preserving continuity of service.
• F&F (Full and Final settlement): the closing payroll computation on exit — dues, leave encashment, recoveries, gratuity where applicable.

Conclusion

An EOR is a tool, not a strategy. It shines when speed matters and headcount is small: hiring across borders or state lines without building registration infrastructure for a handful of people. It fades as teams grow, where its per-head fees outrun the fixed costs of doing employment properly yourself. The winning pattern for most Indian SMBs is deliberate: use EORs narrowly and temporarily, classify contractors honestly, and build direct employment muscle — a clean payroll cycle, state-aware leave and attendance, statutory filings on time — for the core team.

When you're ready to run that core team in-house, CozyHR gives you the payroll engine, attendance and leave management, statutory compliance reminders, and employee self-service that make direct employment feel as light as an EOR invoice — without the per-employee fee. Take a look, and keep the EOR for the edge cases.

This article is general information, not legal or tax advice. Verify current rules, rates, and structures with qualified professionals before deciding.