India Hire-to-Retire (H2R) Framework for Global Companies

Building an India team is not the hard part. Running the full employee lifecycle compliantly is.

Most global companies hire a few people in India fast, then discover the work only starts at the offer letter. Payroll has statutory layers with no US or UK equivalent. Exits carry obligations that trace back to how you wrote the contract. The pieces that break are the handoffs between recruiting, payroll, compliance, and IT.

A hire-to-retire (H2R) framework fixes that by treating the entire employee journey as one connected process instead of scattered HR tasks. This guide maps that framework onto India's specific realities, so a People or Ops leader can run it end to end with compliance built into every stage.

What is a hire-to-retire (H2R) framework?

A hire-to-retire (H2R) framework is a single, end-to-end view of the employee lifecycle, from the first interview to the final settlement, managed as one connected process rather than a set of disconnected HR functions.

Most companies run the lifecycle in pieces. Recruiting owns hiring, payroll owns salary, a vendor owns compliance, and IT owns access. Each works in isolation. The H2R model connects them so one event, like a new hire accepting an offer, automatically triggers the right actions downstream: contract, payroll setup, statutory enrollment, and system access.

The lifecycle has five core stages:

• Hire: workforce planning, sourcing, offer, and contract
• Onboard: documentation, statutory enrollment, and access provisioning
• Manage and develop: payroll, benefits, performance, and growth
• Move and grow: promotions, transfers, and role changes
• Offboard and retire: exit, final settlement, and knowledge transfer

The reason unified beats siloed is simple: the failures rarely happen inside a stage. They happen in the handoffs between them, where data gets re-entered, steps get missed, and accountability blurs. A new hire who waits a week for system access, or an exit that drags on because no one owns the settlement, are handoff failures, not stage failures.

For a global company, H2R is more than an HR model. It is a compliance and risk framework. Every lifecycle event in India also carries a statutory obligation, which makes the connected view a necessity rather than a nice-to-have.

That necessity is sharper in India than almost anywhere else, which is where the framework needs adapting.

Why does an India team need its own H2R approach?

India is not a country you plug into a global HR template. The lifecycle stages look familiar, but what each stage requires is different enough that a generic playbook quietly creates risk.

Start with why the talent is worth the effort.

• India produces over 2.5 million STEM graduates annually, the second-highest output globally, with 34% of all graduates in STEM fields (Source: Wisemonk India Investment Intelligence 2026).
• It is a durable bet, not a passing moment. India's working-age population (15-64) is roughly 68% of the total and stays above 67% through 2040, with a median age of 28.4 years, which means a sustained labor supply advantage for decades (Source: Wisemonk India Investment Intelligence 2026).

You are building on a talent base that will still be deep in fifteen years.

What trips up global employers is the statutory layer. India has mandatory contributions (Provident Fund, ESI), professional tax that varies by state, gratuity, and a full and final settlement process on exit. None of these have a clean US or UK equivalent.

The four Labour Codes add another shift. They consolidated 29 central laws, came into force in late 2025, and reset how compensation is structured, including a rule that wages must be at least 50% of total pay. Get the salary structure wrong and you raise statutory costs or underpay benefits without realizing it.

Location matters too. The talent is concentrated, so where you hire shapes cost, attrition, and compliance footprint across states. Bengaluru leads GCC office-space share at 27%, followed by Hyderabad at 17%, NCR at 12%, Pune at 11%, Chennai at 9%, Mumbai at 7%, and Tier-2 cities at 5% (Source: Wisemonk India IT Services Report 2026).

Here is the lifecycle mapped to what each stage actually triggers in India.

The takeaway: the framework is the same, but every stage needs an India-specific action attached to it. Skip that mapping and the gaps surface later as penalties or disputes.

The first place this plays out is the hiring decision itself.

How do you plan and hire your first India employees?

Hiring your first India employees starts with a decision most companies skip: how you will employ them at all. Get that wrong and every downstream stage inherits the mistake.

Begin with workforce planning. Decide the roles, the seniority, and the location, including whether people work on-site or remotely across different states, since that affects professional tax and registrations. The talent depth supports almost any plan.

A blended mid-level engineer in India costs roughly $20,000 a year versus about $130,000 in the US, a 6.5x cost ratio (Source: Wisemonk India IT Services Report 2026). Treat that as a budgeting input, not the reason to hire. The reason to hire is access to deep, durable talent that you intend to keep.

Next comes the structural question that gates everything: do you hire through your own entity, an employer of record (EOR), or as contractors? This is the decision we break down fully later, but it has to be made before the first offer, because it determines who the legal employer is and which contract you can issue.

Then the hiring mechanics themselves:

• Compliant offer and contract: mandatory terms, working-hour rules, notice period, and a realistic view of non-compete enforceability, which is weak in India.
• CTC structure preview: decide the salary structure early, since wages must be at least 50% of total pay under the Labour Codes, and this drives PF and gratuity.
• Background verification: education, employment, and identity checks.
• Document collection: PAN and Aadhaar, which you will need for statutory enrollment at onboarding.

One trap to flag here: hiring people as contractors to move quickly. It feels faster, but if they work like employees, you carry misclassification and permanent establishment risk. We cover that in the risk section.

The practical takeaway is that hiring in India is a structural decision first and a sourcing exercise second. Lock the employment model, then the offer, and the rest of the lifecycle stays clean.

Once the offer is accepted, the work shifts to onboarding, where India's statutory enrollment begins.

What does compliant onboarding look like in India?

Onboarding in India is where the statutory lifecycle actually starts. The offer is signed, but now the employee has to be enrolled into government systems, structured correctly for pay, and covered by mandatory policies from day one.

A good onboarding flow moves from pre-boarding to a fully compliant active employee in the first few weeks. Digital documents and e-signatures are valid in India, so most of this can run before day one.

Here is what compliant onboarding covers.

Two points deserve attention. First, CTC structuring is not a formality. If basic pay sits below 50% of total compensation, you fall foul of the Labour Codes and understate PF and gratuity, which surfaces later as a correction with back payments. Second, the PoSH policy (Prevention of Sexual Harassment) is a legal requirement, not a nice-to-have, and an Internal Committee is mandatory once you cross ten employees.

This is also the original H2R automation point. When IT access is provisioned off the HR record rather than a manual ticket, the new hire is productive on day one and you avoid orphaned access later. The same connected record protects employee data, which matters under India's DPDP framework.

Done well, onboarding turns a signed offer into a compliant, productive, fully enrolled employee without loose ends.

With the employee active, the lifecycle moves into its longest phase: running payroll and compliance month after month.

How do you run payroll, benefits, and compliance day to day?

This is the part of the lifecycle that never stops. Every month, payroll has to run accurately, statutory deductions have to be deposited on time, and filings have to be made. It is also where most generic global-HR systems go quiet and where EOR pages are accurate but unstructured.

Having run monthly payroll and statutory compliance for 300+ companies and more than 2,000 employees across India, managing over $20M in annual payroll, here is where the real work sits.

Monthly payroll in India is not just salary in, salary out. Each run carries multiple statutory layers that must be calculated, deducted, and deposited, usually by the 15th of the following month.

Beyond deductions, there are filings and documents that have to be right: Form 24Q (quarterly TDS), Form 16 (annual), monthly payslips, and statutory registers. Benefits sit alongside this, including gratuity accrual, group health cover, maternity leave of 26 weeks, and the various statutory leave types.

State-by-state variation is the quiet complexity. Professional tax and Shops and Establishments rules differ across Karnataka, Maharashtra, Telangana, and the rest, so a distributed team means multiple state registrations and calendars. The widest gap most foreign employers underestimate is between revenue growth and headcount growth: timely payroll processing across states is an operational discipline, not a once-a-month task.

Run this well and payroll becomes invisible to the employee and predictable to finance. Run it loosely and it becomes the source of penalties and trust erosion.

How do you handle promotions, transfers, and role changes?

Role changes are the stage most competitors skip, yet they touch payroll, access, and compliance all at once. A promotion changes compensation, which means the CTC structure has to be re-run so basic stays at or above 50% of total pay. A transfer across states can change professional tax and registrations. Each change should also update system access automatically, the same connected-record logic from onboarding.

This is also where development belongs. Internal mobility and clear career paths are among the strongest retention levers in a market with high attrition. Skills are shifting fast: 63% of firms now require AI plus domain expertise hybrid profiles, making it the new hiring standard (Source: Wisemonk India IT Services Report 2026). Building those capabilities internally through structured learning is cheaper than re-hiring for them.

Handled cleanly, mover events keep comp compliant, access correct, and your best people growing instead of leaving.

When someone does leave, the lifecycle has one more demanding stage: a clean exit.

How do you offboard and run full and final settlement?

Offboarding is the stage almost no one structures, yet in India it carries hard obligations and a clear timeline. A messy exit is where withheld documents, disputes, and reputational damage in a tight talent market come from.

It starts with notice and termination rules. Notice periods are set in the contract, and termination has to respect the Industrial Relations Code and state Shops and Establishments rules. You cannot simply end employment at will the way a US employer often can.

The core of the exit is the full and final settlement, the consolidated payout that closes the employment relationship.

Alongside the money, the documentation has to be issued: the relieving letter, the experience letter, and Form 16. These matter more than they look. A withheld relieving letter can block the employee's next job, which is how clean exits turn into legal complaints.

Two operational pieces close it out. Knowledge transfer should be planned before the last day, not scrambled after. And system access has to be deprovisioned immediately on exit, the offboarding side of the connected HR record, so there are no orphaned accounts sitting open.

There is also an upside most companies ignore. A respectful exit builds an alumni network and keeps the door open for rehires, who onboard faster and cost less to bring back.

Handled well, offboarding protects your brand, closes your legal exposure, and leaves the relationship intact. Handled badly, it does the opposite, and the failure usually traces back to how the contract was written at hire.

That connection between stages is exactly why a lifecycle view matters, which becomes clearest when you map where compliance actually breaks.

Where does compliance break at each stage of the lifecycle?

Most compliance failures are not random. They cluster at predictable points in the lifecycle, and they compound when the stages are run in isolation rather than as one connected process.

These are not hypotheticals. Across 300+ companies and more than 2,000 employees, with $20M+ in annual payroll under management, these are the breakpoints we see foreign employers hit most often.

The pattern is consistent: each stage has a signature failure mode, and each one carries a real consequence for a foreign company.

Two risks deserve extra weight for global employers. Misclassification is the one that feels harmless and is not: if a contractor works like an employee, Indian authorities can reclassify the relationship, and a fixed place of business or dependent agent can trigger permanent establishment, which exposes your company to Indian corporate tax. The second is data handling. Employee records fall under India's DPDP framework, so loose data management is its own compliance risk.

The deeper point is that fragmented handling multiplies these risks at scale. Ten employees managed across a spreadsheet, an accountant, and a Slack channel might survive. Fifty cannot, because the handoffs that fail quietly at small scale fail loudly at larger ones.

Seeing the risks laid out this way reframes the real question. It is not whether to run an H2R framework, but who should run it for you.

Should you go in-house, set up an entity, or use an EOR?

This is the decision that shapes everything else, and it usually comes down to three models: run it in-house through your existing global HR, set up your own Indian entity, or use an employer of record (EOR). Each owns compliance differently.

We have operationalized this decision for 300+ companies and more than 2,000 employees, running over $20M in annual payroll management, so the breakeven logic below comes from what actually plays out, not theory.

The trade-offs sort cleanly across cost, speed, compliance ownership, and how well each model scales.

The breakeven logic is about commitment and headcount, not just price. Below roughly 15 to 25 employees, or when you are still testing the market, an EOR is almost always the right call: fast, compliant, and reversible. As the team grows large and clearly permanent, the per-employee EOR fee starts to rival the fixed cost of your own entity, and that is the point to evaluate a switch.

This path is well-trodden. India hosts over 1,700 GCCs employing 1.9 million professionals and generating $64.6 billion in revenue, accounting for nearly 40% of total office space absorption (Source: Wisemonk India Investment Intelligence 2026). Many of those started on an EOR and moved to their own entity once scale justified it.

Honest answer: most global companies entering or scaling in India should start with an EOR and revisit the entity question at scale. It removes the compliance burden while you build the team, and it keeps the decision reversible.

That is exactly the role an India-specialist partner plays across the full lifecycle.

How can Wisemonk help you build your first India teams?

Wisemonk is an India-native Employer of Record and Agent of Record, helping global companies hire, pay, and manage India teams without setting up a local entity.

Most global companies lose three to six months to entity incorporation before they can make a single hire. We take that wait off the table. Your first hires go live within 48 hours through our EOR while your GCC entity registration runs in parallel, then move into your captive center once the entity is live.

Our infrastructure is SOC 2 and ISO 27001 certified, and we have been recognized for both Fastest Implementation and Best Relationship.

Here is how we support each route into India:

• Employer of Record at $99 per employee per month for day-one hiring, covering compliant contracts, PF, ESI, TDS, gratuity, and state-level compliance across all 28 Indian states.
• Managed Payroll from $49 per employee per month for companies that already hold an entity, aligned with the Income Tax Act 2025 that takes effect in April 2026.
• Company registration and GCC entity setup spanning SPICe+ filing, FEMA, FC-GPR, PAN, TAN, GST, and DPDP readiness.
• India-based recruiters who source engineering, AI, product, analytics, and operations talent across tier I and tier II cities.
• Agent of Record and vendor payments for compliant contractor management and cross-border remittances.
• CTC tax optimization that raises employee take-home pay by 10 to 15%, which feeds directly into retention.
• Dedicated HR business partners, real named people on your account instead of ticket queues or chatbots.
• Data residency that meets DPDP Act requirements.
• Equipment procurement and delivery for laptops, phones, and peripherals anywhere in India.

Why global companies choose Wisemonk over global EOR platforms

Global platforms spread across 90 to 150 countries, and that breadth thins out their India expertise. We work in India alone and go deep, from Karnataka GCC Policy filings to the Maharashtra professional tax slabs that change mid-year.

That depth scales with you. Whether you are launching a 10-person pilot or running a 500-member GCC, companies that start on our EOR move to wholly owned subsidiaries once their India operations stabilize, and we carry that shift through without re-hiring or contract disruption.

What our clients say

“I've been working with Wisemonk as an EOR employee for past two years. The onboarding call was really good and they even helped my team onboarding as well. They helped me with the macbook, iphone devices procurement. Their interface is good and I can manage my team in a single interface” - Felix S. Senior Software Development Engineer Read the full review on G2 →

“Wisemonk was instrumental in identifying and assisting in the recruitment of three successful senior executives. The team took a hands-on approach to solving the client's needs, and Wisemonk iterated multiple approaches to problem-solving based on the client's needs and directional shifts.” - Hariher B Co-Founder, BuyEazzy Read the full review on Clutch →