.png)
Which EOR Providers Are Best for US Companies Hiring in India?
We have sat across the table while a US company signed with an EOR provider quoting $199 a month per employee, only to find out three months later that the provider had misclassified a Bengaluru based engineer under a state Shops and Establishments registration that didn't cover software services, triggering a retroactive compliance notice. Across 500 plus cross border mandates our team has run, the gap between the cheapest EOR quote and the one that actually holds up under an Indian labour audit is rarely about price.
It's about which EOR providers are best for US companies hiring in India on the dimensions that matter: statutory registration depth, payroll accuracy, and how fast a provider responds when a state labour inspector shows up.
Why Can't US Companies Just Pick the Cheapest EOR Provider?
Most US founders and HR leads land on this decision after collecting three EOR quotes that look nearly identical on paper: same monthly fee, same "we handle compliance" language, same generic onboarding deck. What the quotes don't show is that India's employment compliance isn't one national law. It's a patchwork. The Shops and Establishments Act is administered state by state, so a Karnataka registration covering Bengaluru doesn't automatically extend to a hire in Telangana (Hyderabad) or Tamil Nadu (Chennai).
A provider only properly registered in one or two states will either quietly skip registration elsewhere, a risk flagged in at least six client reviews over the past two years, or route the employee through a generic pan India shell entity that doesn't hold up during a Provident Fund inspection.
The market has also shifted underneath this decision. India's Global Capability Centers (GCC) ecosystem now employs close to 2 million professionals across more than 1,800 centers, and hiring inside those centers has moved from volume driven to capability led, with sharp focus on AI, cybersecurity, cloud, and product engineering roles.
That skills gap is pulling smaller US companies toward EOR too, because incorporating a wholly owned subsidiary in India still takes 10 to 16 weeks through the Ministry of Corporate Affairs, plus GST and Professional Tax registration, versus 5 to 10 business days to onboard through an established Employer of Record (EOR) That speed gap is why EOR remains the default entry point for testing India as a hiring market before committing capital to a local entity.
Providers that do this well specialize by region instead of claiming blanket national coverage. A provider strong in Bengaluru's tech corridor may have thin bench strength in Pune's manufacturing adjacent IT sector, and vice versa. Asking for the actual PF establishment code and ESI registration number by state, not just a claim of "pan India compliance," is the fastest way to separate a serious operator from a reseller sitting on top of someone else's payroll infrastructure. Among EOR providers for US companies hiring in India, this single check filters out most of the risk before a contract is even signed.
What Actually Separates the Best EOR Providers for US Companies Hiring in India From a Risky One?
The biggest differentiator isn't legal coverage, most established providers do have the paperwork. It's payroll accuracy and how edge cases get handled: a bonus structured to stay tax efficient under Indian rules, a resignation with a 60 day notice clause, or a mid year salary revision that needs to flow correctly into Form 16 at year end.
Clients have switched providers mid contract because payroll was technically compliant but consistently late by 3 to 5 days each cycle, which in Indian tech hiring is enough to trigger attrition. Bengaluru and Hyderabad engineers rarely lack alternative offers and read payroll delays as a sign the employer relationship is unstable.
The second differentiator is background verification depth. A provider running only an identity and address check is not the same as one verifying prior employment, education credentials, and, for senior technical hires, actual code contribution history. Candidates with fabricated employment gaps have shown up at two separate EOR routed hires in the last 18 months, both caught only because a screening layer sat on top of the EOR's baseline check.
What Indian engineers coming through generic staffing channels often lack, compared with those sourced through a specialized international recruitment firm is prior exposure to US client communication norms: async standups, written PR review culture, and disagreeing directly with a US based manager without routing it through a local team lead. AnjuSmriti Global tests for this in a structured 30 minute call before any technical round, not after an offer is extended.
Cities matter too. Bengaluru and Pune have the deepest bench for cloud native and DevOps adjacent roles. Chennai and Hyderabad are stronger for SAP, enterprise integration, and increasingly AI infrastructure work tied to the GCCs based there, alongside tier two hubs now competing for the same talent pool as metro costs climb. An EOR provider without local sourcing relationships in your target city falls back on a generic national candidate pool, and the quality drop shows up within the first two or three profiles sent.
How Are AI and Contract Hiring Changing Which EOR Providers Are Best for US Companies Hiring in India?
The mix of roles moving through EOR arrangements is changing fast. Demand for AI, machine learning, and cloud infrastructure talent in India now outstrips supply by a wide margin, and GCCs compete directly with well funded startups for the same senior engineers, often losing candidates to equity heavy offers rather than base pay alone. An EOR provider sourcing only generalist backend or QA profiles is a poor fit for mandates that include MLOps, applied AI, or platform engineering roles, where qualified candidates move fast between offers.
At the same time, contract based hiring through EOR structures is growing as a share of total hiring, as companies build in flexibility before committing to full time headcount, particularly for project based AI initiatives. This is where the legal difference between contract and full time EOR hiring matters. A full time EOR hire sits under the Shops and Establishments Act, the EPF Act, and the Gratuity Act, with statutory benefits accruing from day one.
A contract hire through the same EOR may additionally trigger the Contract Labour (Regulation and Abolition) Act, 1970 once headcount through a single EOR crosses roughly 20 workers at one location, a threshold most US companies don't hit with a handful of contractors but reach quickly once a project scales. Choosing the wrong hiring type for the wrong stage of a project is a common, avoidable compliance gap.
If you're weighing this tradeoff for your own hiring plan, our team can walk your shortlist of EOR providers against your specific state and role requirements. Start that conversation through our intake form.
Which Laws Actually Govern EOR Hires in India?
Understanding which EOR providers are best for US companies hiring in India starts with understanding that no EOR relationship is legally clean unless it's anchored in the right statutes, and this varies by whether the hire is full time, contract, or fixed term.
For full time employees, the framework includes the Employees' Provident Fund and Miscellaneous Provisions Act, 1952 (12% employer contribution once monthly basic pay crosses ₹15,000, a threshold most tech salaries exceed), the Payment of Gratuity Act, 1972 (payable after 5 years of continuous service, accrued at roughly 4.81% of basic pay), and the state specific Shops and Establishments Act, which governs working hours, leave, and termination notice.
For contract arrangements, the Contract Labour (Regulation and Abolition) Act, 1970 applies once the headcount threshold described above is crossed. Income tax withholding runs under Section 192 of the Income Tax Act, 1961, and the EOR is legally the deductor of record, not the US company, which is exactly why provider choice matters so much. A compliance failure here exposes the Indian employee to a tax notice, not the US company directly, but it destroys trust in the arrangement fast.
The mistake seen most often: US companies assume "EOR" means the provider absorbs all legal risk, then stop reviewing contracts after signing. If the EOR misclassifies a role, misses a PF deposit deadline, or under registers gratuity liability, the exposure surfaces as a compliance notice that can freeze payroll for that employee, which the US company experiences simply as "our engineer suddenly can't get paid," with no warning. Every client should see the EOR's actual PF and ESI compliance certificate, not a summary, before signing.
How Should You Evaluate and Compare EOR Providers?
Use this checklist on the next three vendor calls when you're deciding which EOR providers are best for US companies hiring in India for your specific roles and states.
Evaluation Criterion | What to Ask For | Red Flag |
State level registration | PF establishment code and ESI number per state | Claims "pan India" with no state specific proof |
Payroll cycle history | Last 3 months of processed payroll dates for existing clients | Any pattern of delays beyond 1 to 2 days |
Background verification depth | Sample report including employment and education checks | Identity or address check only |
Contract termination clauses | Actual notice period and severance in a sample offer letter | Vague "as per company policy" language |
Statutory bonus and gratuity handling | Written explanation of tax efficient bonus structuring | No mention of Payment of Bonus Act applicability |
IP and confidentiality assignment | Sample clause naming the US entity as beneficiary | Clause names only the EOR, not your company |
Escalation response time | Written SLA for compliance issue resolution | No SLA, or "case by case" |
Local sourcing depth by city | Number of active candidates in your target city and role | Single national database with no city filter |
The clause most companies miss entirely is IP assignment. Because the EOR is technically the legal employer in India, its default contract template may name the EOR, not your US company, as beneficiary of any code, design, or invention the employee creates. This has been corrected in a dozen contracts before signing; catching it after an employee has already built product is a much harder conversation.
A Real Example: What Actually Went Wrong Once
For a mid size US fintech client (Series B, roughly 90 employees globally) scaling a Bengaluru based backend team from 4 to 14 engineers in under four months, candidate sourcing and technical vetting ran in parallel with the client's chosen EOR handling payroll and statutory compliance.
Week six into the ramp, the EOR's payroll cycle slipped by four business days for the entire cohort due to a banking file error on their end. Candidates began asking their recruiter of record what was going on, since the EOR had no direct relationship with them beyond a payslip. Two of the fourteen engineers began actively interviewing elsewhere within a week.
The client was notified immediately, the EOR was pushed for same week resolution and a written explanation to employees, and the client renegotiated the SLA to include automatic penalties for future payroll delays. Both engineers who'd started interviewing stayed once payroll stabilized. The client finished the 14 hire ramp in 15 weeks against a 16 week target, with zero attrition after month two.
The lesson: the recruitment partner and the EOR provider need a direct line to each other, not just to the client, because employees surface problems to whichever party they trust most, and that's rarely the payroll vendor they've never spoken to.
Real Cost Breakdown: Salaries, EOR Fees, and What You're Actually Paying
For a mid level backend or DevOps engineer (3 to 5 years) in Bengaluru or Pune, expect a gross annual salary between ₹14,00,000 and ₹20,00,000, roughly $16,800 to $24,000. A senior engineer (6 to 9 years) typically lands between ₹22,00,000 and ₹32,00,000, or $26,400 to $38,400. A lead or staff level engineer (10 plus years) runs ₹35,00,000 to ₹55,00,000 plus, with top tier candidates in platform engineering or ML infrastructure sometimes exceeding this range as AI talent shortages push premiums higher.
Budget for employer statutory contributions on top: roughly 13% for PF, 4.81% accrued for gratuity, and 0.75% to 3.25% for ESI where applicable (most tech salaries exceed the ESI wage ceiling above mid level). EOR provider fees for India based hires typically range from $199 to $650 per employee per month depending on compliance depth: the lower end means bare minimum payroll processing, the higher end adds dedicated HR support and faster compliance resolution.
Add a recruitment fee, which through a specialized offshore channel typically runs 12% to 18% of first year gross salary versus 20% to 33% charged by generalist staffing firms.
Clients who run this math against a US based hire for the equivalent role, where fully loaded cost including benefits and overhead often runs $140,000 to $220,000 annually, typically reinvest the difference into doubling team size or funding a second India based hire within the same fiscal year.
Conclusion
The market for EOR providers for US companies hiring in India is consolidating around providers with genuine multi state registration depth, as more clients get burned by "pan India" claims that don't survive a compliance audit. Clients switching EOR providers mid relationship has become one of the fastest growing categories of work we see.
If you'd like AnjuSmriti Global to run this evaluation alongside your shortlist of EOR providers, reach out through our intake form and we'll walk you through it before you sign anything.
Interesting Reads:
FAQs
1.Does an EOR provider in India need to register separately in every state where I hire?
Yes. India's Shops and Establishments Act is administered at the state level, so a registration covering Karnataka (Bengaluru) doesn't extend to Telangana (Hyderabad) or Maharashtra (Pune) automatically. A provider claiming blanket "pan India" coverage without state specific PF and ESI registration numbers is a warning sign. Ask for the actual establishment code for the specific state before signing, not a generic compliance summary.
2.Who is legally responsible if an EOR provider misses a Provident Fund deposit deadline?
The EOR, as the legal employer of record, carries direct statutory liability under the Employees' Provident Fund and Miscellaneous Provisions Act, 1952. The US company feels the fallout indirectly, since a compliance notice can freeze payroll for the affected employee, showing up as an unexplained payment delay. Build an SLA into the contract requiring immediate written notice if any deposit is missed.
3.Can a US company own the IP created by an engineer hired through an Indian EOR?
Only if the employment contract names your US entity, not the EOR, as beneficiary of any code, design, or invention created. Because the EOR is the legal employer under Indian law, its default template may assign IP to itself unless specifically amended. This is one of the most commonly missed items in EOR onboarding, and it's far harder to correct after product has already been built.
4.How does gratuity work for an EOR hired employee who leaves before 5 years?
Under the Payment of Gratuity Act, 1972, gratuity becomes payable only after 5 years of continuous service, so most EOR hired engineers who leave earlier aren't owed a payout. Compliant providers still accrue roughly 4.81% of basic pay against gratuity liability from day one, which affects true fully loaded cost even if it's never paid. Confirm whether this accrual is already included in the quoted fee.
5.What happens to an EOR hired employee if we set up our own India entity later?
Most established providers support a structured transition where the employee's contract is novated from the EOR to your newly incorporated subsidiary, preserving continuity of service for gratuity and leave purposes. This typically takes 3 to 5 weeks once your entity's PF and ESI registrations are active. Confirm this transition process explicitly before signing, since not every provider supports a clean novation.
6.Do EOR providers in India handle full time and contract hires the same way?
No. Full time hires fall under the Shops and Establishments Act, the EPF Act, and the Gratuity Act. Contract hires may additionally trigger the Contract Labour (Regulation and Abolition) Act, 1970 once headcount through one EOR at a single location crosses roughly 20 workers. A provider treating every hire type identically, without flagging when this threshold applies, isn't giving you the full picture.
7.How quickly can an EOR provider onboard a new hire compared with setting up our own entity?
An established EOR can typically complete onboarding, including PF and ESI enrollment, offer letter issuance, and first payroll setup, within 5 to 10 business days of a signed offer. Setting up a wholly owned subsidiary through the Ministry of Corporate Affairs generally takes 10 to 16 weeks including GST and Professional Tax registration, which is why most companies start with an EOR before direct incorporation.
8.Why do EOR hired engineers sometimes leave faster than direct hires in the US?
It's rarely about the EOR structure itself, it's about payroll reliability and communication. Bengaluru and Hyderabad engineers have consistent access to competing offers, especially in AI and cloud roles where demand outpaces supply, and even a short payroll delay can read as a sign the employer relationship is unstable. Direct, proactive communication from the client during any disruption is the most effective retention lever available.
Comments