.png)
What Happens If You Hire Developers in India Without Compliance Risk
- Saransh Garg
- 6 days ago
- 9 min read
To hire developers in India without compliance risk, every contributor needs to sit under a structure, whether that's a registered Indian entity, an Employer of Record (EOR), or a genuinely independent contractor arrangement, that satisfies the Code on Wages, the Code on Social Security, and state Shops and Establishments rules from the first day of work, not after a labour inspection or client audit catches the gap.
Most companies don't find their compliance gap while hiring. They find it when a fixed-term developer resigns after fourteen months and asks for gratuity, a right they didn't have under the old five-year rule but do have now under the Code on Social Security, 2020, which cut the qualifying period for fixed-term employees to one year of continuous service. We've had this exact conversation with three clients in the past two quarters, and none of them saw it coming.
What Does It Mean to Hire Developers in India Without Compliance Risk?
It means the gap between how a working relationship is written down and how a labour authority would actually classify it stays at zero. A "contractor" who works exclusively for you, uses your equipment, follows your reporting line, and takes daily task instructions looks like an employee to the Employees' Provident Fund Organisation regardless of the label on the contract. Misclassification like this is the single most common failure we see when foreign companies try to hire developers in India without compliance risk on their own, especially teams that scaled fast without an in-country HR function.
This isn't the same as permanent establishment risk, which is a tax exposure created when a foreign company's activity in India crosses a threshold that makes it liable for Indian corporate tax. PE risk concerns the company's tax footprint. Compliance risk concerns the individual's employment status. A business can get PE exposure fully managed and still carry unbudgeted gratuity or provident fund liability if the underlying classification of its developers is wrong.
Which Indian Laws Actually Govern Developer Hiring?
India consolidated 29 overlapping central labour statutes into four Labour Codes: the Code on Wages, 2019, the Industrial Relations Code, 2020, the Code on Social Security, 2020, and the Occupational Safety, Health and Working Conditions Code, 2020, all now in force. If your compliance paperwork still cites only the old Payment of Gratuity Act or Payment of Wages Act by name, it's outdated, and penalties under the new framework run well above what the old legislation carried.
Three provisions matter most right now. The 50% wage rule under the Code on Wages requires basic pay to make up at least half of total compensation, with any allowance above that threshold added back into "wages" for calculating provident fund and gratuity, often raising statutory costs on salary structures that were built to minimise them. Fixed-term employees now qualify for gratuity after one year of continuous service, payable pro rata if the contract ends early. And registration obligations under the Employees' Provident Funds Act, 1952 and the Employees' State Insurance Act, 1948 still apply in parallel wherever thresholds are met, alongside state-level Shops and Establishments registration for any place of business.
The mistake we see most: companies assume these obligations start only once they've incorporated in India. They don't. Liability attaches from the first day of an employment-like relationship, whether you're paying a developer directly, routing work through a functionally full-time "contractor," or using an Employer of Record (EOR) that hasn't updated its own templates for the current Codes. This is exactly why so many companies who try to hire developers in India without compliance risk end up outsourcing the classification decision rather than making it themselves.
Contract Hiring vs Full-Time Hiring: Which Carries Less Compliance Risk?
Neither is inherently safer. Each carries a different compliance profile, and the risk comes from mismatching the label to the actual working relationship.
Contract hiring works well for defined-scope, time-bound projects, a six-month migration, a specific feature build, a short-term skills gap. The developer should genuinely control their own hours, tools, and often work with other clients simultaneously. The moment a "contract" developer starts taking daily standup instructions, using company-issued laptops, and reporting to a manager the same way a permanent hire would, the classification test tips toward employment regardless of what the contract says.
Full-time hiring suits ongoing product work where a developer is embedded in the team long-term. It's more predictable from a compliance standpoint because the employment relationship is explicit from day one. Provident fund, ESI, and gratuity obligations apply on a known schedule, and there's no ambiguity for a labour authority to challenge later. Full-time hires also tend to hold institutional knowledge better on complex codebases, which matters more as teams increasingly rely on AI-assisted development tools that still need experienced engineers to review, prompt, and correct their output.
Companies weighing both options for AnjuSmriti Global clients often start with contract hiring to test a role or a market, then convert strong performers to full-time once the need proves durable. That conversion path only stays compliant if the original contract terms genuinely matched contractor status; converting a role that was already functionally employment just formalises a relationship that should have been compliant from the start.
How Do You Check If Your India Hiring Is Compliant?
Run this checklist before any offer goes out, not after.
Check | What it confirms |
Classification test | Does the role meet the independence tests, or does it show control, exclusivity, and daily supervision typical of employment? |
Wage structure | Does basic pay meet the 50% floor under the Code on Wages? |
PF and ESI registration | Are contributions registered and active wherever thresholds apply? |
Gratuity provisioning | Is the one-year fixed-term gratuity liability actually budgeted? |
Shops and Establishments registration | Is the employing entity registered in the correct state? |
Termination clause | Does notice match Industrial Relations Code requirements, not a generic template? |
State rule status | Has the relevant state notified final Code rules, or are transition provisions still active? |
State rule status matters more than most companies assume. As of the most recent tracking, states including Gujarat, Karnataka, Maharashtra, and Haryana had notified final rules under all four Codes, while several others were still running on transition-period provisions, meaning exact obligations for a Bengaluru hire and a hire in a slower-moving state aren't identical today.
What Does a Compliant Hiring Process Actually Look Like?
We run every developer engagement through a four-layer review: classification, wage structuring, statutory registration, and a 90-day post-placement audit. Across our last 60 developer placements run this way, median time from signed offer to a fully compliant first day was nine days, with zero placements flagged for misclassification in later client audits.
When we audited contractor agreements for a mid-sized US SaaS company that had been hiring Indian developers directly for two years, we found six of their eleven "independent contractors" met multiple tests for employment: exclusive engagement, company-issued equipment, fixed hours, and a direct reporting line to a US manager. They hadn't registered for PF or ESI anywhere.
We restructured five under an EOR arrangement and moved one to a genuine part-time contract with a client roster requirement, closing the exposure before any inspection occurred. Correcting the historical classification meant backdated PF contributions, which cost more than structuring it correctly the first time would have.
One thing we changed after that engagement: we now re-run the classification check at 90 days, not just at signing, because a contractor who starts with a defined scope often ends up embedded in daily sprint planning within a few months, quietly shifting their classification even when the paperwork stays the same.
What's Changing in India's Developer Hiring Market Right Now?
The Labour Codes coming into force is the biggest structural shift, replacing the statutes most existing contract templates were written against, with state-level rollout still uneven enough that the compliance baseline genuinely varies by location right now.
AI-assisted development is reshaping how companies evaluate Indian talent for this exact reason: teams that can effectively direct AI coding tools while still owning architecture, code review, and production judgment are commanding a premium, and clients are asking us to screen for that specifically rather than raw output speed. Cloud-native skills, particularly around cost optimisation and multi-cloud deployment, are following a similar pattern as companies move past simple lift-and-shift cloud adoption.
On the compliance side, Indian recruitment and EOR providers are rebuilding contract templates around the one-year gratuity trigger, and providers still running five-year-vesting templates have had to reissue every active fixed-term contract. Our own read from live mandates over the next 12 to 18 months: expect fewer companies relying on 11-month "renewal loop" contracts, a pattern historically used to dodge gratuity exposure, since the math no longer favours the workaround.
Conclusion
Hiring developers in India without compliance risk isn't a one-time legal review. It's a structure checked at hiring, adjusted where the Codes actually changed the math, and re-verified as working relationships evolve past their original terms. The single biggest shift right now is the one-year gratuity trigger for fixed-term employees, and any company still running templates written before the current Codes is very likely exposed. In our own mandates, the companies with the least risk are the ones treating classification as a recurring check rather than a signature on day one.
Ready to see where your own India hiring stands? Talk to our team.
Interesting Reads:
FAQs
1.Does the one-year gratuity rule apply to contractors or only fixed-term employees?
It applies only to workers classified as fixed-term employees under the Code on Social Security, not to genuine independent contractors. A developer misclassified as a contractor when they actually meet the employment tests could later claim this right retroactively, creating an unbudgeted liability. Relying on the contractor label without meeting the actual independence tests adds risk rather than removing it, which is why classification accuracy matters more than the paperwork label itself.
2.How is compliance risk different from permanent establishment risk?
Compliance risk is about whether a worker's classification matches how they're actually engaged. Permanent establishment risk is about whether the foreign company itself becomes liable for Indian corporate tax based on its activity. They can overlap, since a misclassified contractor behaving like an employee can strengthen a PE argument, but resolving one doesn't automatically resolve the other, so both need separate review.
3.Can a US or European company hire Indian developers without setting up a local entity?
Yes, through an Employer of Record, which legally employs the developer in India on the client's behalf and handles PF, ESI, gratuity, and Shops and Establishments compliance without requiring incorporation. This is the fastest route to a compliant hire and suits companies testing India as a talent source before committing to a full entity. The trade-off is an ongoing per-head fee that narrows the cost gap versus a mature in-house entity.
4.What actually counts as misclassification under Indian labour law?
Misclassification happens when a "contractor" meets the tests authorities use to identify employment: exclusive engagement, company-issued equipment, fixed hours, direct supervision, and integration into internal reporting. No single factor decides it; authorities weigh the overall pattern of control and dependency. A developer working full hours solely for one client, using their tools, and reporting to a named manager looks like an employee regardless of contract wording.
5.Does the 50% wage rule change what companies pay Indian developers?
It doesn't change gross pay, but it changes how that pay must be structured for statutory purposes. Basic pay must equal at least half of total compensation, and any allowance above that gets added back into wages when calculating PF and gratuity. Salary structures weighted heavily toward allowances, a common cost-optimisation pattern, are now seeing statutory contribution costs rise even with no change to the headline number.
6.How long does fixing a misclassification issue usually take?
Restructuring a genuinely misclassified contractor into a compliant EOR or direct-employment arrangement typically takes two to four weeks. Resolving any backdated statutory liability, like unpaid PF contributions, can take longer and usually costs more than structuring the engagement correctly from the start would have. The restructuring itself is rarely the hard part; reconciling historical contributions is what extends the timeline.
7.Do state-level differences in Labour Code rollout actually affect hiring decisions?
Yes. Several states have notified final rules under all four Codes while others are still operating under transition provisions, meaning exact statutory obligations aren't uniform across India right now. A company hiring across multiple Indian cities needs its compliance process to track this state by state rather than apply one national template, since the gap between fully notified and transition states affects real obligations.
8.Should a growing team choose contract hiring or full-time hiring for developers in India?
Contract hiring fits defined-scope, time-bound work where the developer genuinely controls their own hours and tools. Full-time hiring fits ongoing product work with predictable, explicit compliance obligations from day one. Many teams start with contract hiring to validate a role, then convert strong performers to full-time, but that conversion only stays compliant if the original contract terms genuinely matched contractor status rather than disguised employment.
Comments