And How EOR Prevents Every One of Them
India is one of the most attractive hiring markets in the world. Deep technical talent, strong execution culture, competitive salaries relative to Western markets. The case for hiring in India is easy to make.
The execution is where global companies consistently stumble — not because India is uniquely difficult, but because it is different in ways that are not obvious until you are already inside the process. The mistakes below are not edge cases. They are patterns. Most happen before the first payslip is issued. Several surface months or years later when the damage is already done.
| MISTAKE 1 Hiring Indian Talent as Contractors When the Work Requires Employees |
The scenario: A US SaaS company needs a senior backend engineer in Bengaluru. Legal suggests a contractor agreement to keep things simple. The engineer works exclusively on company tools, joins all-hands, manages a junior developer. Eighteen months in, a Labour Commissioner complaint is filed. A tax inquiry follows.
Contractor misclassification is the single most common India hiring mistake — and the most expensive to unwind.
In India, the employment test is not what you call the arrangement — it is the substance of it. Exclusive engagement, company direction, company tools, no independent client base: Indian law treats this as employment regardless of what the contract says. The consequences are retroactive — unpaid PF contributions, ESI, gratuity accrual, and TDS liability, all calculated back to day one. At 12% p.a. interest on delayed statutory deposits, the bill compounds fast.
| HOW EOR PREVENTS IT | Paybooks EOR establishes compliant employment from day one — correct CTC structure, statutory registrations, employer contributions in place. No contractor grey area. The relationship is clean, documented, and legally defensible from the moment the offer is signed. |
| MISTAKE 2 Underestimating the Hiring Timeline — Then Improvising |
The scenario: A European fintech identifies a strong candidate in Hyderabad. The engineering head wants her to start in two weeks. The company has no India entity. Someone says they can sort the legal structure later. She starts working. Three months on, she still has no compliant employment structure and has not received a single statutory benefit.
Setting up an Indian entity — the path most companies assume is their only option — takes a minimum of three to six months: MCA registration, PAN and TAN applications, EPFO and ESIC registration, Shops and Establishments Act registration, bank account under FEMA. Sequential, government-dependent, nothing compressible.
Companies that bridge this gap informally — paying the person as a vendor, using a foreign payroll, deferring the employment structure — create retroactive liability across tax, statutory benefits, and employment law. The improvisation costs more than the entity.
| 7–14 | business days: the typical Paybooks EOR onboarding timeline from signed engagement to compliant, onboarded employee. Entity setup: 3–6 months minimum. |
| HOW EOR PREVENTS IT | Paybooks is already registered and holds active compliance registrations in every major Indian hiring city. A candidate can be onboarded in 7–14 business days from the moment offer details are confirmed. No entity, no waiting, no improvisation. |
| MISTAKE 3 Getting the Salary Structure Wrong Before the Offer Goes Out |
The scenario: A US company offers a Bengaluru engineer ₹30 lakh per annum. That number goes into the offer letter. Nobody understands CTC vs gross vs basic vs in-hand. The engineer joins and receives a net figure significantly below expectations. The complaint arrives in week three.
Cost to Company is not take-home pay. It includes employer PF, gratuity provision, insurance premiums, and allowances — all of which reduce net-in-hand significantly. A ₹30 lakh CTC does not mean ₹2.5 lakh hits the bank account each month.
Basic salary is the foundation of statutory calculations. Set it too low and PF contributions are under-calculated — a compliance violation that employees notice immediately. The standard is basic at 40–50% of gross CTC. Get the offer letter wrong and the fix is not simple: a salary structure change that reduces take-home pay requires written employee consent and creates dispute risk.
| HOW EOR PREVENTS IT | Paybooks structures every CTC correctly before the offer is issued — basic salary ratio, HRA, allowances, variable pay, statutory components. Employees receive a payslip that matches expectations. No week-three surprises. No mid-year corrections. |
| MISTAKE 4 Treating India as a Single Compliance Jurisdiction |
The scenario: A Singapore company hires in Bengaluru, Pune, and Chennai simultaneously using one employment contract template. Three months later: Professional Tax is wrong in all three states, Shops and Establishments registration is missing in Tamil Nadu, and LWF has not been set up in Maharashtra.
India is not a single employment jurisdiction. It is 28 states and 8 union territories, each with the authority to legislate on labour matters. For a foreign employer, compliance in Bengaluru is materially different from Mumbai, Hyderabad, or Chennai. A company with employees in four states using one national template has four separate compliance gaps — each with its own penalties and its own remediation.
| State | PT Applies? | LWF Applicable? | S&E Registration? |
| Karnataka | Yes — up to ₹200/month | Yes | Yes |
| Maharashtra | Yes — up to ₹200/month | Yes | Yes |
| Tamil Nadu | Yes — up to ₹208/month | Yes | Yes |
| Telangana | Yes — up to ₹200/month | No | Yes |
| Delhi (NCT) | Not applicable | No | Yes |
| HOW EOR PREVENTS IT | Paybooks holds active registrations across India’s major hiring states and configures compliance separately per employee location. Multi-city hiring means state-specific contracts, PT registrations, LWF contributions, and S&E filings wherever your people are based. |
| MISTAKE 5 Treating Resignation as the End of the Relationship |
The scenario: A senior engineer resigns with one month’s notice. The foreign employer, used to two-week US notice periods, treats the last day as the conclusion. The engineer requests a Full-and-Final settlement and a relieving letter. Neither arrives. Six weeks later a Labour Commissioner complaint is filed. The engineer’s new employer puts the offer on hold pending BGV clearance.
Exit is the most compliance-dense phase of Indian employment — and the one foreign employers are least prepared for.
Notice periods run long. Thirty days is a floor for most professional roles; sixty and ninety days are common at senior levels. Indian professionals take notice periods seriously and new employers confirm via BGV that notice was served. Full-and-Final settlement is a legal obligation, not a courtesy — earned leave encashment, notice period pay or recovery, bonus pro-ration, gratuity if the employee has five-plus years of service, and correct TDS on all components. Target: 30–45 days from last working day.
Relieving and experience letters are non-negotiable. Every employer conducting BGV requires them. Withholding them, even in a dispute, creates a separate legal exposure and damages your employer brand in a talent market where word travels fast.
| HOW EOR PREVENTS IT | Paybooks manages the complete exit process: F&F settlement, notice period tracking, leave encashment, TDS adjustment, relieving and experience letters — within defined SLAs. Offboarding starts from USD 50 per exit and covers the full statutory process. |
| MISTAKE 6 Choosing an EOR Based on the Lowest PEPM Quote |
The scenario: A UK company picks the lowest EOR quote for their first India hire. Eight months in, a TDS error creates a discrepancy. The employee cannot file their ITR correctly. The EOR’s India support response time is 48–72 hours. The employee escalates to the UK head of HR. The relationship breaks down.
EOR is not a commodity. The cheapest PEPM is almost never the cheapest engagement. What separates providers is what is inside the fee — some quote low management fees and bill statutory contributions as pass-throughs, some do not provision gratuity, some operate India as one of 150 countries with no local compliance team and support routed through a global queue.
| Ask this | Strong answer | Red flag |
| Are statutory contributions in your fee or pass-throughs? | Itemised: management fee separate, pass-throughs listed | Bundled answer without breakdown |
| How do you handle multi-state PT compliance? | Separate registration per state, active in your cities | ‘We handle it nationally’ — PT has no national structure |
| What is your F&F settlement SLA? | Committed 30–45 day SLA from last working day, in writing | ‘We aim to do it quickly’ — no defined timeline |
| Who handles employee queries in India IST hours? | Named India-based team, direct contact, defined escalation | Global helpdesk, no India-specific routing |
| HOW EOR PREVENTS IT | Paybooks is India-specialist with 12+ years of payroll and compliance depth, now part of TransPerfect. Every engagement has a named India-based team. Pricing is transparent: management fee from USD 199/employee/month, onboarding from USD 50, offboarding from USD 50. What you see is what you pay. |
| MISTAKE 7 Using EOR as a Permanent Structure Without a Transition Plan |
The scenario: A US company builds an India team of 60 engineers over three years, all on EOR. In year four they want to offer ESOPs as part of a retention drive. They discover ESOPs cannot be granted under Indian law through an EOR structure. They also need a local bank account for client payments. They need an entity — but now have 60 active employees to migrate and no plan.
EOR is a powerful starting structure. It is not a permanent one for every company. As India headcount grows, the commercial equation shifts. At 80–100 employees, the EOR management fee approaches the cost of running your own compliance infrastructure. And there are structural things EOR cannot provide regardless of headcount: Indian-law ESOPs, direct revenue generation, local banking, full HR policy ownership.
The companies that navigate this well treat EOR as Phase 1, not the destination. They start with EOR, validate the India model, then begin entity planning in parallel around the 12–18 month mark — continuing to hire on EOR uninterrupted. The transition happens over 60–90 days with proper statutory handover. No hiring gap. No compliance scramble.
| Phase | Timeframe | What to do |
| 1 | Month 1–18 | Hire via EOR. Validate India model. Zero entity overhead. |
| 2 | Month 12–24 | Begin entity setup in parallel. Continue EOR hiring uninterrupted. |
| 3 | Month 18–30 | Transition employees from EOR to entity over 60–90 days. EOR manages statutory records transfer. |
| 4 | Month 30+ | Full subsidiary operations. ESOPs live. Local banking active. |
| HOW EOR PREVENTS IT | Paybooks supports the full lifecycle — from first EOR hire through entity transition. We help clients plan the crossover point, manage the employee migration, and ensure no compliance gap between structures. EOR is where you start. The transition is part of the plan from day one. |
The Common Thread
Every mistake above shares the same root cause: India was treated like a market the company already understood. The employment law felt familiar enough. The shortcuts seemed reasonable enough.
India rewards companies that do the work upfront. The compliance framework is clear, the statutory obligations are defined, the timelines are known. None of this is unknowable — it just requires local knowledge applied before the first hire, not after the first problem.
| The mistake | When it surfaces | EOR prevention |
| Contractor misclassification | 6–18 months in | Compliant employment from day one |
| Improvising while entity is set up | Immediately | 7–14 day onboarding, no entity needed |
| Wrong CTC structure in offer letter | Month one | CTC structured correctly before offer |
| One template for all states | First compliance audit | State-specific compliance per location |
| Informal exit handling | Within 60 days of resignation | Full F&F and relieving letter within SLA |
| Choosing EOR on PEPM price alone | First compliance event | India-specialist team, transparent fees |
| No EOR-to-entity transition plan | Year 3–4 | Lifecycle support from EOR to subsidiary |
Most of these mistakes are not recoverable cheaply. The retroactive PF liability from misclassification, the legal cost of a disputed termination, the talent damage from a delayed F&F settlement — all of these are multiples of what a well-structured EOR engagement costs from the start.
| Hiring in India? Start without the mistakes. Paybooks EOR specialists work with global companies before the first hire — helping you avoid every pattern on this list from day one. paybooks.in/eor | info@paybooks.in | +91 80 4710 7171 |
