Hiring your first employee in India can feel simple until payroll day shows up. Suddenly you’re juggling statutory benefits, a salary structure that has real compliance consequences, and paperwork that needs to match local expectations.
That’s where India EOR hiring becomes practical. An Employer of Record (EOR) can act as the local employer on paper, so you can add headcount in India without setting up an entity, while still giving employees compliant contracts, payroll, and required benefits.
This guide breaks down the essentials that trip teams up most often: EPF and ESI basics, what an India offer letter should cover, and the payroll mistakes that cause the biggest mess later.
What an EOR actually does when you hire in India
Think of an EOR as the legal “rails” under your employment relationship. You still run day-to-day work, goals, performance, and team culture. The EOR handles the local employer obligations that create risk if they’re wrong or late.
In India, that typically includes issuing locally aligned employment documents, onboarding (collecting IDs and statutory declarations), running monthly payroll in INR, and managing statutory deductions and employer contributions. It also includes compliance tasks that are easy to underestimate, like keeping audit-ready payroll records, generating payslips, and managing offboarding in a way that matches notice pay rules and final settlement norms.
If you want a broader overview of how EORs fit into India expansion, this Employer of Record in India guide is a useful reference point for terminology and scope.
Why startups pick an EOR instead of setting up an entity
Entity setup is rarely “just paperwork.” You’re signing up for ongoing accounting, registrations, recurring filings, and local support costs. For a single sales hire or a small engineering pod, that can be like buying a whole building when you only need a desk.
An EOR lets you test India with less fixed overhead. It also reduces the chance that your first hire becomes your first compliance fire drill.
Where Expandbase fits for India hiring
Expandbase is one option teams use to hire employees in India and other markets through an EOR model. Its pitch is speed and lower admin load: you submit the role and compensation details, the platform produces a country-specific contract, and the employee completes digital onboarding with document upload and e-signature. After onboarding, payroll and benefits setup kick off automatically, and the first payroll can be processed in days rather than months.
For teams moving fast, that combination matters. The painful part of cross-border hiring is not the offer itself, it’s the operational chain that follows: statutory setup, monthly calculations, payslips, and clean reporting back to finance.
EPF and ESI basics for India payroll (and why salary structure matters)
EPF and ESI are two of the most common statutory programs that show up in India payroll conversations. They’re also where many foreign companies make early mistakes, because the rules depend on wage definitions, thresholds, and what counts as “eligible pay.”
A good first step is getting comfortable with the basics from a local payroll viewpoint. This PF and ESI compliance primer lays out how these programs work in practice.
Quick reference: EPF vs ESI
| Item | EPF (Provident Fund) | ESI (Employee State Insurance) |
|---|---|---|
| What it is | Retirement savings program (with linked pension components) | Health and social insurance program |
| Typical employee rate | 12% of eligible wages (commonly basic plus DA), subject to rules | 0.75% of eligible wages (when applicable) |
| Typical employer rate | 12% of eligible wages (commonly basic plus DA), subject to rules | 3.25% of eligible wages |
| Common wage ceiling used | INR 15,000 per month for mandatory coverage in many cases | INR 21,000 per month for eligibility |
Those figures are widely used in payroll operations as of early 2026, but always validate against the employee’s setup and current notifications, especially when you’re hiring across different Indian states or through different establishment registrations.
The salary split problem most teams don’t see coming
In India, “CTC” (cost to company) is a common way to talk about compensation, but how you split the CTC changes statutory costs. If you push too much into allowances and keep “basic” artificially low, you can end up in disputes later, or be forced to reclassify wages during audits and pay arrears.
On top of that, many companies are planning for the Labour Codes wage definition directionally, which has encouraged a “basic at around 50% of total pay” approach in some compensation designs. Even if your EOR is doing the calculations, you still want to understand the tradeoff: a higher basic can mean higher EPF contributions, but it also tends to be cleaner and easier to defend.
The practical takeaway is simple: don’t treat salary structure as a formatting exercise. Treat it like a compliance decision.
India offer letters: what to include so payroll and compliance don’t break
An India offer letter isn’t just a welcome note. It’s the first document that payroll, benefits, and future offboarding will depend on. If it’s vague, you pay for it later in back-and-forth emails, corrections, and sometimes legal disputes.
There’s no single mandatory template that fits every role, but strong offer letters usually cover the points below clearly, in plain language:
- Role basics: Job title, reporting line, start date, work location (and whether remote work is allowed).
- Employment terms: Full-time or part-time status, probation period (if used), confirmation process, and working hours.
- Compensation details: CTC plus a clear breakup (basic, HRA, allowances, variable pay, reimbursements). This is where PF and ESI assumptions start.
- Statutory benefits: EPF and ESI applicability, plus any employer-provided benefits the employee will actually see.
- Leave and holidays: Annual leave approach and any company-specific policies, aligned to local norms where needed.
- Notice and termination: Notice period from both sides, payout rules, and conditions for immediate termination (if any).
- Confidentiality and IP: Especially important for tech teams, since IP ownership needs to be explicit.
If you’re hiring through an EOR, the EOR will usually issue (or co-issue) employment documents that align with local labor law. That reduces risk, but you still need to review the offer details for business clarity, because the offer letter is where misunderstandings start.
A simple test helps: if your finance lead and your new hire interpret the same sentence differently, rewrite it.
Common India payroll pitfalls (and how an EOR helps you avoid them)
Payroll errors in India tend to fall into a few repeat patterns. They’re rarely malicious. They’re usually caused by missing context, manual spreadsheets, or assumptions imported from other countries.
Here are the ones that cause the biggest operational pain:
- Wage split that triggers rework: A low basic with high allowances can lead to EPF recalculations, policy changes, and difficult employee conversations later.
- Incorrect EPF or ESI eligibility: Teams sometimes assume everyone gets ESI or no one does, but eligibility depends on wage thresholds and setup.
- Late statutory payments and filings: Even small delays can create penalties and employee distrust, especially if the employee checks their PF status.
- State and location differences ignored: Minimum wages, Shops and Establishments rules, holidays, and local registrations can differ by state.
- Inconsistent payslip logic: Mismatched line items (CTC vs take-home, reimbursements, variable pay timing) create endless payroll tickets.
- Contractor conversions handled poorly: Moving a long-term contractor to employee status requires clean effective dates, updated IP terms, and correct statutory enrollment.
An EOR helps by standardizing the monthly workflow: compliant payslips, local currency payroll, statutory calculations, and records that can stand up to audits. Expandbase, for example, emphasizes guided onboarding, automated payroll setup after the employee signs, and recurring payroll runs that generate payslips and sync records back to HR and finance reporting. That kind of system reduces “tribal knowledge” risk, where only one person knows how payroll works.
If you’re comparing providers, it can help to scan an independent shortlist like this EOR options review for India, then pressure-test each one on India-specific scenarios (PF/ESI handling, salary structuring support, offboarding timelines, and payroll cutoffs).
Conclusion
India is a great place to hire, but the details matter. EPF and ESI rules, wage structure choices, and a well-written offer letter can decide whether your first hire feels smooth or stressful.
If you want speed without guessing, India EOR hiring through a provider like Expandbase can reduce admin load and help keep payroll compliant from the start. The smartest move is to treat payroll setup as part of hiring, not a task you can fix after the employee joins.
