What Is International Staff-on-Payroll and How Is It Different from EOR?

A German industrial software client once asked us: "Why would we use an EOR when we could just put the engineer on our own payroll?" Both are legal ways to employ someone in India. What changes is who carries the compliance risk, how fast you can hire, and what it costs at scale. Understanding international staff-on-payroll and how is it different from EOR is the first decision we walk every client through before a single candidate is shortlisted.

What Does Staff-on-Payroll Actually Mean in Cross-Border Hiring?

Staff-on-payroll means the hiring company's own registered entity is the legal employer. The employee's contract, salary, statutory deductions, and compliance obligations all sit directly with that entity. This is different from contract hiring, where an individual is engaged for a defined scope or period without full employment benefits, and different again from full-time hiring, which comes with ongoing statutory entitlements like provident fund, gratuity, and paid leave under Indian law regardless of whether the employer is the company itself or an EOR.

Why Does This Decision Trip Up Even Experienced HR Teams?

The confusion starts because both models look identical on paper. The employee gets a payslip, tax is deducted, and work gets done. What differs is the legal structure underneath, and that structure decides who is liable if something goes wrong.

We see this most with European companies expanding into India for the first time. A Netherlands based logistics tech company assumed their Dutch entity could run payroll for engineers working from India. It cannot. Employing someone resident in India requires either an Indian entity of your own or an EOR registered in India acting as the legal employer.

This isn't rare. Foreign investment into India's IT and business services sector has stayed strong for years, and a large share of that comes from companies expanding headcount before resolving exactly this question. Entity setup in India typically takes six to eight weeks through the Ministry of Corporate Affairs, plus GST and Shops and Establishments registration. Talent in Bengaluru, Pune, and Hyderabad rarely waits that long.

Which Indian Talent Pools Fit International Staff-on-Payroll and EOR Hiring Best?

For roles typically hired under either model, software engineering, data, DevOps, and platform specialists, the deepest talent sits in Bengaluru, Pune, Hyderabad, and increasingly Chennai. Bengaluru's product company ecosystem produces engineers used to owning features end to end. Pune's automotive and manufacturing tech corridor is strong in systems level work.

Hyderabad's enterprise SaaS base runs deep in data engineering and cloud platforms.

What we consistently test for, regardless of city, is comfort with ambiguity. Engineers here are often excellent at execution but under practiced at pushing back on unclear requirements, a habit that costs nothing in a large in house team but is expensive when someone is the only offshore member on a distributed team.

We run live, unscripted technical conversations specifically to see whether a candidate asks clarifying questions before writing code, because that single behaviour predicts cross border success better than any test score. We also check comfort with two to three hours of daily overlap with European or US teams, since that, not skill gaps, is the most common reason distributed hires quietly disengage after a few months.

Interest in AI assisted development, cloud native architecture, and platform engineering has grown fast across these cities, and increasingly the strongest candidates come with hands on production experience using AI coding tools rather than just familiarity with them, which matters when clients are hiring for speed as much as headcount.

This talent depth is exactly why the international staff-on-payroll and how is it different from EOR question matters early: the faster route to hiring the strongest candidates is often the deciding factor, not just the legal structure itself.

Does India's Employment Law Treat Staff-on-Payroll and EOR Hiring Differently?

Whoever legally employs someone carries the statutory liability for that person, and this is the part of international staff-on-payroll and how is it different from EOR that most HR teams underestimate.

Under direct staff-on-payroll, your own Indian entity is the Employer of Record (EOR) and is directly responsible for compliance with the Employees' Provident Fund Act, the Employees' State Insurance Act where applicable, the Payment of Bonus Act, and the relevant state's Shops and Establishments Act, which governs working hours, leave, and termination notice. Get this wrong, commonly by misclassifying a full-time role as a contractor to avoid PF contributions, and penalties fall personally on registered directors, not an abstract corporate entity.

Under an EOR arrangement, the EOR is the legal employer on paper. It holds liability for PF, ESI, gratuity under the Payment of Gratuity Act, and Shops and Establishments registration, while you retain full functional control over the person's work, pay, and performance.

Companies used to contractor rules like the UK's IR35 sometimes assume India works similarly. It doesn't have a direct equivalent, but disguising a full-time role as consulting to sidestep gratuity and PF obligations is an active enforcement area for India's Provident Fund Organisation, and foreign companies have faced back payment orders after assuming distance meant less scrutiny.

Staff-on-Payroll vs EOR: The Side-by-Side Comparison

Criteria	Staff-on-Payroll (Own Entity)	EOR
Legal employer	Your registered Indian entity	The EOR provider
Setup time before first hire	Six to eight weeks	Five to ten business days
Compliance liability	Sits with your company and directors	Sits with the EOR
Minimum headcount to justify	Around 15 to 20 employees	Works from a single hire
Ongoing entity cost	Company secretary, audit, local finance staff	Included in EOR monthly fee
Control over work and pay	Full	Full
Best fit	Companies planning long term India entity or large teams	Companies testing India hiring or under 15 to 20 people

Seeing international staff-on-payroll and how is it different from EOR laid out side by side like this usually settles a hiring committee debate faster than another round of emails. The break even point across our mandates sits between 15 and 20 employees. Below that, entity maintenance usually costs more than an EOR premium. Above it, direct payroll is typically cheaper.

How Do We Run Staff-on-Payroll and EOR Hires in Practice?

At AnjuSmriti Global, staff-on-payroll mandates with an existing entity take three to four weeks for a single mid level hire and six to eight weeks for a batch of five to ten. EOR routed hires compress to ten to fourteen days since there is no entity dependency. Technical assessment is identical either way: a live pairing session rather than a take home test candidates now often complete with AI help, a systems design conversation scaled to seniority, and reference checks focused on communication under ambiguity.

A recent example: a roughly 200 employee US healthtech company wanted eight backend engineers within a quarter and had already started registering an Indian entity, assuming that was the only compliant path. It nearly went wrong when entity setup ran past its expected timeline while their hiring budget was already committed.

We moved the first four hires onto an EOR while entity setup continued in parallel, onboarded them in twelve business days, and transitioned them to direct payroll once the entity was live roughly ten weeks later. They hit their quarterly hiring number without losing candidates to slower competitors, and used the interim EOR period to decide, with real utilisation data, that the entity was worth maintaining long term.

This same international staff-on-payroll and how is it different from EOR decision applies whether the role is a fixed scope contract hire or a full-time position. Contract hiring under either model still requires PF and gratuity compliance once tenure and hours cross statutory thresholds, something companies used to shorter term contracting in Europe or the US frequently miss.

What Does It Actually Cost: Staff-on-Payroll vs EOR in India?

Cost is usually where international staff-on-payroll and how is it different from EOR stops being theoretical and becomes a spreadsheet decision.

Real numbers for a backend engineer, current market range, in INR:

Mid level (three to five years): gross salary 14 to 18 lakh per year. Employer PF and ESI contributions add roughly 13 percent. EOR fees typically run 8 to 15 percent of gross salary. Total cost under EOR: roughly 17 to 23 lakh per year.

Senior (six to nine years): gross salary 24 to 32 lakh. Total under EOR: roughly 29 to 41 lakh.

Lead or staff level (ten plus years): gross salary 38 to 55 lakh. Total under EOR: roughly 46 to 70 lakh.

Own entity costs run similar on statutory contributions, with an additional 6 to 10 lakh a year in entity maintenance spread across headcount. Clients typically reinvest savings from either model into one senior or lead hire for every three to four mid level hires, building an actual leadership layer in India rather than pure execution capacity.

Conclusion

Expect more companies to start with EOR for their first year of India hiring and convert to their own entity only once headcount and retention data justify it, a pattern already visible in several of our live mandates right now. Whichever path fits your plan, understanding international staff-on-payroll and how is it different from EOR before you sign anything is what keeps a hiring plan from becoming a compliance problem later. Get in touch with our team to map your hiring plan against both models.

---

Interesting Reads: EOR India for GCCs: Why Global Capability Centers Use Employer of Record

India EOR for SaaS Companies: How to Build a Remote Engineering Team

EOR India Contract Terms: What Your Employment Agreement Must Include

FAQs

1.Does an EOR in India still require PF contributions for employees?

Yes. Regardless of whether your own entity or an EOR is the legal employer, eligible employees must be enrolled under the Employees' Provident Fund Act. The EOR manages registration and monthly contributions on your behalf, but the underlying obligation itself doesn't disappear just because someone else administers it. This is one of the most common misunderstandings we see among companies hiring in India for the first time, and it's worth confirming with your provider directly.

2.At what headcount should we stop using an EOR and open our own entity?

Based on our mandates, the break even point is typically 15 to 20 employees. Below that, entity maintenance costs, audit, company secretary, and local finance staff usually exceed what you'd pay in EOR fees. Above 20, the per head EOR premium tends to cost more than running compliance in house. We recommend treating this as a number to revisit every two quarters as your headcount grows, not a one time decision made at the start.

3.Can employees move from an EOR to our own payroll later?

Yes, and it's a transition we run regularly for growing clients. Day to day work, reporting lines, and pay don't need to change at all. What changes is which entity is the legal employer named on the contract and payslip, with PF account continuity carried through the switch. Done properly, employees rarely notice a functional difference beyond a new company name appearing on their documents.

4.Who owns IP created by an engineer employed through an EOR?

IP is assigned to your company through a tri-party agreement between you, the EOR, and the employee, never to the EOR itself. This is standard practice in any properly structured EOR contract, but it's still worth verifying explicitly before signing, since a poorly drafted agreement can leave ambiguity around work completed outside standard hours or on personal devices during the engagement.

5.How does maternity leave work under an EOR versus our own entity?

Maternity benefits follow India's Maternity Benefit Act either way, giving eligible employees 26 weeks of paid leave for the first two children and shorter entitlements after that. Under an EOR, the provider typically administers and pre funds this leave as part of its statutory role, which can help companies unfamiliar with Indian leave rules avoid administrative missteps during a sensitive period for the employee.

6.Does hiring through an EOR block us from opening our own entity later?

No. There's no regulatory link between using an EOR and registering your own entity later. Many companies run both in parallel, hiring through an EOR while entity formation proceeds in the background, which is often the more practical sequence since it avoids delaying hiring until paperwork clears. Some clients never convert at all, and that's fine too.

7.What happens to notice period and severance under an EOR termination?

Termination still follows the relevant state's Shops and Establishments Act, generally requiring 30 days' notice or pay in lieu after probation, plus gratuity once someone crosses five years of service. The EOR executes the termination on your instruction and ensures statutory dues are calculated and paid correctly, while any severance beyond statutory minimums remains entirely your decision to make.

8.Does an EOR limit our ability to offer equity to Indian employees?

No, but it adds a layer of coordination worth planning for early. Equity is usually granted directly by the parent company under its own plan, independent of who runs payroll day to day. What needs separate attention is FEMA compliance for the employee receiving foreign equity, which is worth setting up correctly from the first grant rather than fixing it retroactively later.