HR Outsourcing in India That Includes the Employer

HR outsourcing gets sold as payroll processing, and payroll is genuinely the anchor, but the surface a foreign employer actually needs covered in India is four times wider. Here is the honest map, laid out by layer, so vendor scopes can be compared like for like instead of brochure to brochure.

📇 The distinction that sorts every vendor

One question separates the market: who is the legal employer of the people? If the answer is you, then you need an Indian entity and the vendor is processing on your behalf, that is a payroll bureau or classic HR outsourcing. If the answer is the vendor, on the vendor's registered Indian entity, that is an employer of record, and your need for an Indian entity disappears. Every acronym in this market, HRO, PEO, EOR, ASO, resolves to one side or the other of that question.

Foreign companies without an Indian entity are structurally on the EOR side whether they know it or not, because the other side requires the entity they do not have. Companies with an entity get the full menu and mostly need the processing layers. This article covers both, and flags which chapters apply to which side.

The vendor by vendor comparison for the processing side lives in our review of payroll outsourcing companies in India; the employer of record side is mapped on the EOR services page. Keep both open if you are still deciding which side you are on.

Indian payroll confuses foreign employers because the offer is quoted in CTC, cost to company, a number that includes the employer's own contributions. The employee's in hand salary can run 20 to 30 percent below the CTC headline, and candidates negotiate knowing this. Here is the machine, one pass, gross to net.

🧾 The structure of a salary

A CTC splits into Basic and DA, allowances, and employer contributions. The Labour Codes, operational since 21 November 2025, require Basic plus DA to be at least 50 percent of CTC, which standardised what used to be creative structuring. Everything statutory keys off Basic plus DA: PF at 12 percent from employer and 12 from employee, gratuity accruing at 4.81 percent, and ESI at 3.25 percent employer side for salaries within its threshold. TDS, income tax withheld at source, then applies on the taxable total per the employee's chosen tax regime.

⚠️ Where DIY payroll goes wrong

Four classics. Proration on mid month joiners computed on calendar days by one system and working days by another, producing payslip disputes in week one. Flexible benefit plans configured without the paperwork that makes them tax valid. Full and final settlements missing the 48 hour statutory window because nobody owned the checklist. And the wage definition rule applied to new offers but not old contracts, leaving legacy employees under provisioned on PF and gratuity. None of these are exotic; all of them are why the processing layer gets outsourced first.

The deeper statutory mechanics, thresholds, and the employer cost calculator sit on the EOR versus entity breakdown; the point of this chapter is that you can now read any vendor's payroll scope and know exactly which lines it does and does not cover.

Whoever runs your HR operations in India runs this calendar. It is worth reading once even if you outsource everything, because vendor accountability starts with knowing what the vendor is accountable for.

💰 The penalty asymmetry, again

The pattern worth internalising: deadlines touching employee money carry compounding penalties and personal director exposure, deadlines touching pure filings carry capped fees. PF is the sharpest edge, 12 percent annual interest plus damages scaling to 25 percent with delay, now enforced by systems rather than inspectors. A vendor's PF discipline is therefore the single best proxy for their overall quality, and it is verifiable: ask for six months of challans for the teams they run. Clean vendors produce the folder in a day. The other kind produce reasons.

🚧 The state layer is where scope quietly ends

National vendors handle national obligations well. The state layer, professional tax slabs, Shops and Establishments registrations and renewals, state leave rules, is where cheap scopes quietly stop, and a team spread across Karnataka, Maharashtra and Haryana is a three state surface. Ask any prospective vendor precisely which states their scope covers and who files the renewals. In our case the answer is all 28, in house, which is what India native means in practice rather than in marketing.

If you only audit one thing about your current setup after reading this page, audit the challans. Everything else in HR outsourcing is recoverable; years of quiet PF defaults are not.

With the layers and the calendar established, the model comparison becomes almost mechanical. Four ways to run HR in India, sorted by the question from chapter one: who employs the people?

🤔 The PEO ambiguity, named

PEO is the market's fuzziest label. In the US it means co-employment, a real legal construct. India has no co-employment statute, so India PEO in practice means either an EOR wearing a different acronym or an HR admin service on top of your entity. Do not buy the label; ask the deciding question, whose entity employs the people, and price what you are actually getting. A vendor unclear on this in the sales call will be unclear on it during a labour inspection, which is a worse time.

📇 The shapes that fit each model

A US startup with no Indian entity hiring its first five engineers: EOR, no real alternative short of incorporating, and the crossover math says not yet. A mid market company with a 40 person subsidiary and a country manager: payroll bureau or PEO on top of the entity, with in-house HR from around 50 heads. A company mid transition, entity in flight, team already hired: EOR as the bridge, migrate on one payroll cycle when the PF code is live. The models are not competitors so much as stages, and the expensive mistake is occupying a stage you have outgrown, in either direction.

For the EOR stage specifically, the provider landscape, global platforms versus India native operators, is compared honestly in our review of EOR services in India, including where we sit in it and who should not pick us.

Pricing in this market comes in three shapes: per payslip for processing, per employee per month for fuller scopes, and percentage of payroll for vendors who like raises as much as you do. Here is the honest range table for 2026.

💸 The three quiet fee lines

One: FX spread. Vendors settling your payroll at bank retail rates absorb 3 to 5 percent of the flow invisibly; on a 50,000 dollar monthly payroll that is up to 2,500 dollars a month, dwarfing the visible fee. The clean standard is the RBI reference rate with zero spread, and any vendor who will not name their rate in writing has answered the question. Two: deposits. Some EORs hold one to two months of payroll as float; that is your working capital financing their balance sheet. Three: exit fees, per head off boarding charges and notice period minimums, which price the cost of leaving into the relationship exactly where you cannot see it on day one.

💰 Reading a quote like an operator

Take any quote and normalise it to: total cost per employee per year, all fees, at the RBI rate, including onboarding and exit, over a three year horizon with two salary raises. Percentage models and payslip models converge or diverge dramatically under that lens, and flat fee models stop looking expensive the moment salaries pass entry level. The arithmetic is five minutes; the vendors counting on you skipping it are the reason it is worth doing.

Then weigh fees against the penalty table from the calendar chapter: the cheapest vendor who misses two PF deadlines a year is the most expensive vendor on this page.

The same discipline as every chapter: real patterns, each with the question that catches it before the contract does.

❌ The scope gap discovered at exit

A vendor runs payroll beautifully for two years, then the first resignation lands and nobody owns the full and final settlement, due inside 48 hours, or the relieving letter the employee needs for their next job. Exits are the least automated, most deadline bound part of Indian HR, and cheap scopes exclude them precisely because of that. The question: walk me through your last exit, step by step, with the timestamps.

❌ The challan mismatch

Invoices show statutory amounts collected; the EPFO passbook shows deposits missing or late. The employee discovers it first, and the trust damage lands on you, not the vendor. The question: monthly challan copies as a contractual deliverable, with read access, not on request.

❌ The single spreadsheet operation

A boutique vendor runs forty clients on heroics and spreadsheets. It works until the one person who knows your account leaves during your appraisal cycle. The questions: how many clients per operations lead, what is in writing when that person is on leave, and can I see the runbook for my account.

❌ The ticket queue with an SLA

A global platform's India module answers a notice period question in four days via three time zones of escalation, for a decision the employee needed by Friday. India employment runs on Indian hours and Indian nuance. The question: who exactly answers my 8pm IST question on a Tuesday, name and city, and the honest test is to ask one before signing.

❌ The compliance theatre

Glossy dashboards, green ticks, and a Shops and Establishments registration that lapsed eight months ago in a state the vendor forgot they covered. Dashboards report what the vendor tracks, not what the law requires. The question: which of my registrations expire in the next 12 months, and who owns each renewal by name. A vendor who cannot answer from memory is reading the same dashboard you are.

The meta pattern: every failure lives in the gaps between scope lines. Buy fewer vendors with wider scopes and named owners, verify with documents rather than dashboards, and re-run the challan audit quarterly. Boring, and bulletproof.

Everything outsourced is a candidate to come home eventually, and pretending otherwise is vendor marketing. The honest framework: bring a function in-house when it becomes strategic to how you compete for people, and keep it outside while it is machinery.

🚀 The triggers, in the order they arrive

First trigger: an India leader exists. A country head or India HR lead changes the calculus, because the coordination overhead of vendors was half the outsourcing case. Second: headcount past 40 to 50, where a full time HR operations person costs less than the per head fees and earns her keep on retention alone. Third: differentiation, when your appraisal design, ESOP communication or culture programmes become how you win talent, generic vendor delivery starts costing more than it saves, invisibly, in offer acceptance rates.

🔁 What comes home first, and what never should

The sequence that works: talent operations first, recruitment coordination, engagement, policy, because they touch candidates and culture. Employment administration second. Payroll processing and statutory filings last, and honestly, for many companies, never: the compliance calendar from chapter three is pure machinery with penalty edges, exactly the work that specialist scale does better and cheaper than your first HR hire ever will. Plenty of 200 person subsidiaries run in-house HR on an outsourced statutory spine, and that hybrid is not a compromise; it is the optimum.

🤔 And if you are on an EOR?

The same logic maps to structure: the EOR stage ends at the entity crossover, 20 to 30 heads or an India leader hired, whichever lands first. The migration mechanics, same UANs, PF continuity, one payroll cycle, are covered in the entity vs EOR guide. What you should expect from your EOR at that moment is a graduation, not a retention fight: no exit fees, transfer letters ready, and your new payroll vendor briefed by theirs. How a vendor behaves when you leave is the truest data about them, which is why we set our own exit fees at zero and put it in writing.

Outsource the machinery, own the strategy, and re-decide the boundary once a year at budget time. That is the whole framework.

Most vendor evaluations test the wrong things. Founders compare dashboards and price sheets, sign with whoever demos best, then discover six months later that the demo never showed the part that matters: what happens when something goes wrong on the 14th of the month with PF due on the 15th.

Here is the evaluation that actually predicts the relationship.

🤔 Ask who does the work

The single most useful question in any HR outsourcing evaluation: who, by name, will run my payroll every month? A vendor that answers with a person is selling you an operator. A vendor that answers with a portal, a team, or a service level agreement is selling you a queue. Both can work, but they fail differently. The operator picks up the phone at 8 pm on filing day. The queue opens a ticket. If your India team is under 50 people, you want the operator, because at that size a single missed filing is a meaningful fraction of your compliance surface.

📇 Test the compliance depth, not the claim

Every vendor claims full statutory compliance. Test it with specifics. Ask which state Shops and Establishments registrations they currently hold. Ask how they handle professional tax for an employee in Karnataka versus one in Maharashtra, the rates and slabs differ, and a vendor that waves the question away runs one-size payroll. Ask what happened the last time they received a PF notice on a client's behalf and how it resolved. The answers do not need to be perfect. They need to be concrete, because concrete answers come from people who have done the work and vague ones come from people who have sold it.

🧾 Read the exit clause before the entry price

The pricing page tells you what the relationship costs. The exit clause tells you what it costs to leave, and vendors know that switching payroll providers mid-year is painful enough that most clients tolerate a lot before they do it. Look for exit fees, notice periods beyond 60 days, and data lock-in: will you get full payroll registers, Form 16 histories and challan records in a usable format when you go? A vendor confident in its service makes leaving easy. At Versatile the position is no setup fees and no exit fees, because a client held by a contract clause is not a client, it is a hostage.

⚠️ The red flags, plainly

Walk away when you see any of these. Pricing that only appears after a sales call, opaque pricing at this size of decision means the price flexes to what you look able to pay. A contract that makes the vendor a processor with no liability for filing accuracy, you carry the penalties, they carry the keyboard. References only from companies much larger than yours, a 2,000 person client gets the A team, you will not. And any hesitation on the question of who holds the statutory registrations, because if the answer is unclear now, it will be very clear the day a notice arrives, and the name on it will be yours.

The switch itself is where outsourcing projects stumble, not because the work is hard but because it gets compressed. A payroll transition planned across four weeks is boring and smooth. The same transition attempted in the week before a payroll run is a scramble that burns trust on both sides. Here is the four week shape that works.

📇 Week one: the data handover

Everything starts with a clean employee master: names, PAN, Aadhaar linkage status, UAN numbers, bank details, CTC structures, date of joining, and current investment declarations. Pull the last three months of payroll registers and the last full year of challans, PF ECR, ESI, TDS. If your current arrangement is a spreadsheet and an accountant, this week is longer and that is fine. Bad data discovered in week one is an inconvenience. Bad data discovered on filing day is a penalty.

🧾 Week two: structure review

A competent vendor does not just replicate your current salary structures, it reviews them against the Labour Codes. The wage definition now requires Basic plus DA at a minimum half of CTC, and structures built in the old regime, thin basic, fat allowances, need rework because PF and gratuity both key off that base. This is the moment to fix them, because restructuring at transition touches every letter once, while restructuring later means a fresh consent cycle with every employee.

⏰ Week three: parallel run

The old process and the new vendor both compute the same payroll month, and you reconcile to the rupee. Differences will surface, they almost always trace to investment declarations, mid-year joiners, or professional tax slabs, and week three is exactly where you want them surfacing. A vendor that resists a parallel run is telling you how confident it is in its first attempt.

🚀 Week four: cutover and the first live month

Payroll runs on the new system, payslips go out, filings happen against the real deadlines: TDS by the 7th, PF and ESI by the 15th. Keep the old access alive for one more cycle as a fallback you never use. From the second month the rhythm takes over, inputs by a fixed date, outputs by a fixed date, filings confirmed with challan numbers you can see. That confirmation step matters more than any dashboard: a filing is done when the challan exists, not when the vendor says so.

One honest caveat on timing. If your India team is employed through an employer of record rather than your own entity, most of this chapter compresses to nothing, because the EOR is already the employer, already holds the registrations, and already runs the filings. The transition plan above is for companies with an entity and a payroll to move. If you are pre-entity, the shorter path is to not build the payroll in the first place.

Statutory compliance is the floor, not the offer. PF, ESI and gratuity make you legal; they do not make you competitive, and the gap between a legal offer and a winning one is where good HR operations earn their fee. Four pieces matter.

🏥 Group health, the real decider

ESI covers employees earning up to 21,000 rupees a month, which excludes essentially every tech salary. That means your team has no employer linked health cover unless you provide it, and in India, where private hospital costs are rising double digits annually, group health insurance is the benefit candidates check first. The market standard for tech roles is a group policy of 3 to 5 lakh per family, parents included as an upgrade option, premiums running roughly 8,000 to 20,000 rupees per employee per year depending on age mix and cover. A good HR partner brings a broker relationship and a claims support process; a great one gets a five person startup onto group rates at all, which solo policies cannot match.

🧾 Leave design that reads local

State Shops and Establishments law sets leave minimums, typically in the range of 18 or more days of earned leave plus casual and sick allowances depending on the state. A competitive tech offer runs above the floor: 24 or more total days is common, and the details signal more than the number. Carry forward rules, encashment at exit, both statutory expectations, and increasingly a real sick leave policy that does not require a certificate for a single day. The cheap signal that costs nothing: respect the festival calendar properly, with regional flexibility, because a Diwali week that requires negotiation reads as a company that has not thought about India.

💰 The pieces that round it out

Three more items appear in almost every winning offer at the mid and senior level. Personal accident and term life cover, cheap riders on the group policy that families notice. A flexible benefits basket inside the CTC, meal cards, fuel and telecom allowances, structured to be tax efficient under the regime the employee picks. And an internet plus device allowance for remote roles, which has moved from perk to expectation. None of these are legally required. All of them show up in counter offers, and losing a strong candidate over 1,500 rupees a month of structure is an expensive way to save nothing.

The operational point: every benefit above the floor is one more thing to administer, renewals, claims, exit proration, and this entire layer is part of what you are buying when you outsource HR properly. On the employer of record model it comes bundled: the group health policy, the leave engine and the flexible structuring already exist, and your first India hire lands inside a benefits stack that normally takes a 200 person company years to assemble.

🤔 Is employee data safe with an Indian HR vendor?

India's DPDP Act now imposes real obligations on anyone processing personal data, with meaningful penalties, so the statutory floor rose. The practical audit is short: where is payroll data hosted, who has access by role, is transfer to your systems encrypted, and does the contract carry breach notification timelines. Serious vendors answer in one email with an annex. The red flag is not a modest security stack; it is improvisation on the answer.

🤔 What insurance and benefits do Indian employees expect?

Group health insurance covering the employee and usually family is the baseline expectation for white collar roles, typically 5 to 10 lakh cover; accident cover is common, and gratuity plus PF are statutory rather than perks. The competitive edge in 2026 offers: parental top ups, mental health cover, and clean ESOP communication. A vendor running benefits for many clients gets group pricing your five person team cannot, one of the quieter arguments for the EOR stage while you are small.

🤔 How do notice periods really work in India?

Sixty to ninety days is standard for mid and senior roles, thirty for juniors, and buyouts, the employee paying or the new employer funding the unserved notice, are routine. What foreign employers underestimate: enforcing a notice period on a resigned employee is theoretically possible and practically pointless, so design retention on engagement rather than contract clauses. Your HR vendor should be advising you on exactly this kind of gap between law on paper and practice on the ground; that advice is half the fee.

🤔 How painful is switching HR vendors?

Payroll processing switches are a data migration plus one parallel run cycle, best done at fiscal year start in April. EOR to EOR switches are heavier, tripartite letters and PF transfers, but run to a checklist. In both cases the incumbent's cooperation is the variable, which is why exit terms belong in the entry negotiation. Ask for the off boarding runbook before you sign the onboarding one; the good vendors have both documents and no discomfort sharing them.

🤔 We already have an entity. Is an EOR still relevant?

Two cases, yes. Expansion into states or employment types your current setup handles badly, fixed term staff, a second city pod, while your entity stays lean. And the reverse bridge: some companies wind their entity down at a low headcount and move remaining staff to an EOR rather than carrying 15,000 dollars a year of overhead for four people. Structure should follow headcount both directions; the guide for that math is EOR vs entity in India.

⭐ The position, once and plainly. Decide which side of the entity question you are on, because it decides your menu: no Indian entity means the EOR side; entity means bureaus and PEOs are on the table. Outsource the machinery layers, payroll and statutory, early and without guilt, they are penalty edged plumbing. Keep talent strategy close, and bring HR home in stages once an India leader exists and headcount passes 40 or 50. Judge every vendor on challans, exits and FX rate, in that order, and normalise every quote to three year cost per employee at the RBI rate.

And the disclosure that is also the pitch. I run Versatile, an India native EOR. For companies without an Indian entity we are the employment layer end to end: your team on our registered entity, PF, ESI, TDS and gratuity run in house across all 28 states, exits settled inside the statutory 48 hours, 149 dollars per employee per month, 129 past 20, first month free, no setup or exit fees, and payroll at the RBI reference rate with zero FX spread. The challans are yours to read monthly, because that is the standard this article just told you to hold everyone to. If any of this maps to your next quarter, the EOR services page has the machinery, or use the form on this page and I will reply personally.