What Is EOR? India Hiring: Process, Costs, and Setup Steps

If you want to hire talent in India but setting up a local entity is too burdensome and outsourcing raises disguised-contracting risks, EOR (Employer of Record) is often the chosen solution. This article explains how EOR works, typical costs, and the implementation flow from a practical India hiring support perspective.
Contents
※Please be noted that this blog is translated automatically by AI
Conclusion Summary
What you’ll learn in this article:
What EOR (Employer of Record) means and how it’s used to hire talent in India
Typical monthly fees, setup costs, and commonly missed charges
Estimated time from contract to start (as fast as 2 weeks to 1 month)
Practical differences from contracting, staffing, and setting up a local entity
How to tell which companies fit EOR and which do not
What is EOR (Employer of Record)? — Definition and How It Works
EOR stands for Employer of Record. A local EOR provider becomes the legal employer and handles hiring, payroll, social insurance, and taxes.
A Japanese company signs a service agreement with the EOR provider, and the Japanese company gives the actual work instructions.
Its biggest advantage is that even companies without a local entity can hire talent in compliance with local laws.
Separation of the legal employer and operational command
In an EOR setup, employment and day-to-day work are separated.
Legal employer: EOR provider (handles payroll, social insurance, taxes, and labor management)
Work direction: Japanese company (handles tasks, deliverables, and evaluation)
This lets Japanese companies use talent as part of their team while avoiding direct handling of local labor laws and tax rules.
However, note that the employer name on the contract is the EOR provider.
If you want to treat the person as your employee long term, consider later moving to a local entity.
3 Reasons EOR Is Chosen for Hiring Talent in India
There are several options for using talent in India, such as contracting, offshore development, and setting up a local entity.
Among them, EOR is chosen mainly for these three reasons.
1. Hire without a local entity
Setting up a local entity (Private Limited Company) in India takes about 180 days from registration to start-up.
With EOR, operations can begin in as little as 2 weeks to 1 month.
You also avoid the upfront investment for incorporation (worth several million yen) and the burden of annual closing and tax filings.
2. Reduce compliance risk with Indian labor law and tax rules
In India, the four labor codes were enacted in 2020, and enforcement schedules and detailed rules differ by state.
Areas to handle include EPF (Employees' Provident Fund) contributions, gratuity (severance pay), and PoSH (prevention of workplace harassment) laws.
Japanese companies need specialist knowledge to handle these directly.
With EOR, the provider takes care of compliance with these laws.
3. Hire quickly, in a few weeks to one month
When using an EOR provider with candidate referral services, recruiting, employment contracts, and payroll can all be managed in one place.
This makes it possible to hire ahead of setting up a local entity when you need IT talent fast.
In particular, engineers from Tier 1 and Tier 2 universities often receive high-paying offers from U.S. Big Tech and Singapore companies.
When securing this talent, speed is a key differentiator.
EOR Cost Estimate — Monthly and Initial Fees
EOR costs mainly consist of monthly fees and initial costs.
Monthly fee market rates
Rates vary by provider, but are generally within the following range.
Fixed monthly: about JPY 30,000 to 80,000 per person
Salary-based: about 10% to 20% of the employee's monthly salary
Monthly fees generally include payroll, social insurance procedures, and tax processing.
However, local candidate screening, interview scheduling, and onboarding support are often extra or not included.
It is essential to confirm the scope of support before signing.
Initial costs and easy-to-miss expenses
Initial costs may include contract drafting, local government registration, and first-time hiring procedures.
In addition, these costs are often not included in monthly fees:
Travel and housing arrangements (if bringing candidates to Japan)
Extra medical insurance and benefits costs
Accruals equivalent to severance pay (gratuity)
Higher real costs due to exchange-rate fluctuations
For details on the cost structure and a total-cost comparison with direct employment, see the related article, "Is EOR really expensive? Cost blind spots revealed by comparing it with direct hiring."
Related articles
EOR is gaining attention as a fast way to hire overseas talent, but many companies find the cost higher than expected after implementation. This article breaks down why costs grow and the often-overlooked expense items, and explains practical decision criteria while comparing it with direct employment.
Implementation flow from contract to launch
The standard EOR implementation flow is as follows.
Step 1: Choose an EOR provider (1–2 weeks)
Compare candidate sourcing features, coverage areas (Bengaluru, Hyderabad, Pune, Chennai, etc.), contract terms, and pricing.
India's talent pool differs by region.
Bengaluru has a dense IT talent base and is highly competitive, Pune has many universities and suits fresh graduates, and Hyderabad tends to be more cost-efficient.
Step 2: Candidate selection and interviews (2–4 weeks)
Select candidates through the EOR provider or another recruiter, then conduct online interviews.
Engineers from Tier 1 universities (IIT, NIT, etc.) receive high-paying offers from U.S. Big Tech and Singapore companies.
Showing not just salary, but also growth opportunities and technical challenges is key to successful hiring.
In technical interviews, it is important to narrow the criteria to the skills needed for your business.
If you judge only by coding tests, you may miss differences in design ability, code review skills, and production experience.
Even Tier 1 graduates can differ greatly in onboarding speed depending on whether their background is research-oriented or product-development oriented.
To avoid mismatches, design the process to confirm hands-on experience directly tied to your tech stack and development phase, rather than focusing only on potential.
Step 3: Employment contract and salary setting (1 week)
The EOR provider and the Japanese company sign a service agreement, and the EOR provider and the candidate sign an employment contract.
Salaries are set to local market rates, and the EOR provider handles EPF and income tax withholding.
Step 4: Start work (immediately)
After the employment contract is signed, salary payments and work start at the same time. The Japanese company then gives instructions, tracks progress, and evaluates performance as usual.
If the employee will come to Japan, a Technical / Humanities / International Services visa application is required separately.
Differences from outsourcing, staffing, and local subsidiary setup
Let's organize how EOR differs from other contract types by key criteria.
Key differences
Outsourcing: A deliverables-based contract. Direction and control remain with the contractor. If prolonged, there is a risk of disguised subcontracting.
Dispatch: A system based on Japan's dispatch law. Applying it to overseas talent is difficult in practice.
Establishing a local entity: Your company becomes the legal employer. Setup takes about 180 days, initial investment is several million yen, and ongoing operations are also heavy.
EOR: The legal employer is the EOR provider, but it is an intermediate model that lets you use the talent as if they were your own.
Organizing the four models by each criterion makes their features clear at a glance.

EOR sits as a balanced middle option in cost, speed, compliance, and scale fit. A side-by-side comparison with outsourcing, dispatch, and local entity setup, plus details on cost structure, are covered in another article, "Comparison of India EOR and other contract types (outsourcing, dispatch, and incorporation)."
Criteria for judging disguised subcontracting risk
When you directly contract with an individual under an outsourcing agreement, there is a risk it may be deemed disguised subcontracting if the actual instructions are judged to be close to a direction-and-control relationship. In EOR, the employer is the EOR provider, while the Japanese company gives the work instructions, so the contract type does not fall under disguised subcontracting. However, if the EOR provider's management remains merely formal, it may still be regarded as effectively equivalent to disguised subcontracting, so contract terms and actual operations must be aligned.
Related articles
More Japanese companies want to tap top talent in India, but varied contract options can make decisions difficult. This article compares EOR with other contract models and clearly explains their pros and cons.
Companies that are and aren’t a good fit for EOR
EOR is not a one-size-fits-all option. Here are the criteria for companies it suits and those it doesn't.
How SMEs can use EOR to build a 'pseudo-GCC'
For SMEs, EOR can also serve as a 'virtual local base.'
A Global Capability Center (GCC), such as one a U.S. company sets up in India, is a model for internalizing headquarters functions locally.
However, building a GCC assumes a local entity, and launch requires tens of millions of yen in investment and more than a year of preparation.
For Japanese SMEs, setting up a local entity right away is too heavy, but using EOR to staff a small dedicated team can approximate GCC-style in-house capability building.
When the site grows later, a practical next step is to shift to a local entity.
Companies EOR suits
Companies in the test phase of the Indian market that want to start small, with a few people to under 10
Companies that need IT talent fast and cannot wait to set up a local entity
Companies without in-house experts in overseas HR and labor, and want to outsource compliance
SMEs that want to start overseas hiring while keeping initial costs low
Companies EOR doesn't suit
Companies planning long-term expansion of more than 20 people in India and aiming to build their own local base over 3-5 years
Companies that want their HR and evaluation systems strongly reflected in the local operation
Companies handling highly confidential R&D or IP management work and want to avoid splitting employer names
If you want to decide at the management-strategy level between EOR, offshore development, and domestic hiring (Engineer/Specialist in Humanities/International Services visa), see another article, 'Hiring Indian talent, or EOR/offshore? The key turning point in your strategy.'
Related articles
As Japanese firms speed up DX, using India’s advanced IT talent is now essential. Yet many companies mischoose between direct hiring, EOR, and offshore development, leading to higher costs and IP leakage. This article explains the best entry model for your company, based on India’s labor practices and legal regulations.
Common Pitfalls Often Overlooked in EOR Implementation
Problems after introducing EOR can be grouped into the following three cases.
1. Overestimating the support scope of the EOR provider
The scope of support varies greatly by EOR provider, including candidate referrals, technical screening, and onboarding support.
Many cases occur where a company signs believing “EOR = hiring agency,” but in reality the provider only handles payroll and labor procedures, leaving candidate selection to the company.
Before signing, it is important to clarify the support scope your company needs and agree in writing.
2. Misjudging candidate quality
When candidate referrals come through an EOR provider, it is essential to set salary offers that reflect competitiveness in the local hiring market.
Graduates of Tier 1 universities and senior engineers receive high-paying offers from U.S. Big Tech and Singapore companies, so standard Japanese-company pay levels may not attract applicants, or may only secure junior candidates from Tier 3 universities.
Salary design should be based on local market rates in India and the level of talent your company requires.
3. Failing to plan the transition to direct employment
If you want to directly hire people initially employed through EOR later at your local subsidiary or Japanese headquarters, the transition process should be designed in advance.
Changing the employer involves the employee’s consent, reissuing the contract, severance handling, and changes to visa status. The approach of “start with EOR for now, then incorporate once things are on track” is reasonable, but it is better to clarify the criteria for timing the move and the required procedures at the contract stage.
The failure patterns when using EOR together with offshore development are covered in a separate article, “Can EOR and offshore be used together? Explaining common failure patterns.”
Related articles
More companies are combining EOR and offshore, but if roles and responsibilities are not clearly defined, it often leads to lower quality and a heavier management burden. This article explains the structural differences between EOR and offshore, plus common pitfalls and practical design methods when using both.
Summary
EOR (Employer of Record) is an intermediate option for hiring Indian talent without a local entity.
Key points of this article are as follows.
EOR is a setup where a local EOR provider becomes the legal employer and handles payroll, social insurance, and taxes
Monthly fees are roughly JPY 30,000–80,000 per person, or 10–20% of salary, depending on provider, region, and role
From contract to start, it can take as little as 2 weeks to 1 month. Faster than setting up a local entity (about 180 days)
Best for companies testing the market with fewer than 10 people, or SMEs that need IT talent fast
Three common failure patterns are: overestimating support scope, misjudging candidate quality, and failing to plan for transition to direct employment
Phinx handles cross-border hiring end to end: from candidate selection using its local network in India, to travel and onboarding after EOR hiring, and support for future transition to direct employment.
Rather than just introducing EOR, it also organizes talent quality, retention after hiring, and future org design. That is a key feature of its role as an Indian talent recruitment provider.
Its basic policy is not mass referrals, but one-by-one matching based on each company’s hiring needs, talent level, and structure.
Even for first-time hiring in India, Phinx can support you from organizing the decision criteria onward.
Latest Articles
Stay up-to-date






