Naresh K Matta Senior HR & Business Advisor

India Entry

Hiring your first employees in India: what foreign companies get wrong

Contractor misclassification, salary structuring, contracts and statutory thresholds: what overseas companies get wrong, and what it costs.

The pattern is remarkably consistent. A company in the US, the UK, Germany or Singapore hires two engineers in Bengaluru. The contracts are adapted from the home-country template. Both are engaged as contractors, because that is administratively simpler. Salary is a single consolidated monthly figure.

Eighteen months later there are twenty-two people, and every one of those four decisions has to be unwound.

None of this is difficult to get right at the first hire. All of it is expensive to correct at the fiftieth. Here is what actually differs.

1. Contractor classification does not hold as long as you think

This is the single most common and most expensive mistake.

Engaging your India team as independent contractors is administratively attractive. No provident fund registration, no gratuity accrual, no statutory benefits, a simple invoice each month. Many companies start this way and never revisit it.

The difficulty is that classification is determined by the substance of the relationship, not by what the contract calls it. Where a person works full time, works under your direction, uses your systems, follows your working hours, is integrated into your team, and has no other clients, the contractor label does not reflect reality — and it does not protect you.

The exposure when this unwinds includes back-dated statutory contributions, and it applies to everyone hired on the same basis, not just the person who raised the question.

When contractor status is genuinely appropriate: short-term, project-scoped, genuinely independent work, where the person controls how and when they deliver and has other clients.

When it is not: a full-time member of your engineering team who happens to be in a different country.

2. Indian salary is built from components, not a single number

In most Western countries, a salary is one number. In India it is an architecture, and each component drives a different obligation.

A typical structure separates basic salary, house rent allowance, various allowances, and employer contributions to provident fund and gratuity. This matters because:

  • Provident fund contributions are calculated on defined wage components. How you structure salary directly determines the liability.
  • Gratuity accrues over service and becomes payable after a qualifying period. It is a real accruing liability, and companies that have never accounted for it are carrying an unrecognised one.
  • Bonus obligations apply within certain wage thresholds.

Paying a single consolidated figure is not illegal, but it makes structuring decisions by default rather than by design — and it is very difficult to restructure downward later without an employee-relations problem, because it looks like a pay cut regardless of how it is explained.

Get this right at the first offer and it costs nothing. Fix it at fifty employees and you are renegotiating fifty compensation packages.

3. Your employment contract will be signed, and will not do what you expect

A US or UK employment agreement will be executed without objection. It simply will not achieve the same effect.

At-will employment does not translate. India has statutory notice requirements and, for certain categories of employee, procedural protections around termination. A clause reserving the right to terminate at any time for any reason does not override them.

Non-compete clauses are treated very differently. Post-employment restraints on trade face significant limits on enforceability in India. A non-compete drafted with US enforceability in mind is likely to be substantially less effective here. Confidentiality and non-solicitation are on considerably firmer ground.

Statutory benefits apply regardless of contract. Provident fund, gratuity and statutory leave are not negotiable through drafting. A contract silent on them does not remove them.

Notice periods run both ways and are frequently longer than Western norms — one to three months is common for professional roles, which materially affects hiring timelines.

4. Statutory thresholds arrive earlier than you expect

Several obligations trigger at headcount or wage thresholds. Foreign companies routinely cross these without noticing, because nothing in their home experience signals that ten employees is a meaningful number.

The principal ones to track:

  • POSH Internal Committee — at ten employees. This requires a properly constituted committee including an independent external member. It is a statutory obligation, not a policy choice.
  • Provident Fund — registration is triggered at a defined employee threshold
  • ESI — applies at a defined threshold, for employees within a wage ceiling
  • Shops and Establishment registration — state-level, and required from the point you have an establishment
  • Professional tax — applicable in some states and not others

Thresholds and specifics vary by state and are revised periodically, which is exactly why it is worth confirming your position before you cross them rather than after.

5. State matters more than you would guess

India is not a single employment jurisdiction. Karnataka, Maharashtra, Telangana, Tamil Nadu and Delhi each have their own Shops and Establishments Act, their own minimum wage notifications, and their own registers and returns.

A company with people in Bengaluru and Pune is operating under two different regimes. One with a registered office in Delhi and staff in Gurugram and Noida is operating under three — because the National Capital Region spans Delhi, Haryana and Uttar Pradesh.

The common failure is applying the head-office state’s rules everywhere and quietly falling out of compliance at every other location.

Employer of Record, or your own entity?

There is no universal answer, but the trade-off is reasonably clear.

An EOR makes sense when you are making your first few hires, you want to move quickly, you do not yet know whether India is a long-term commitment, and you would rather not deal with registrations at all.

Your own entity makes sense when per-head EOR cost has overtaken what an entity plus compliance support would cost, you want direct control over employment terms and equity, you are building a team with its own culture rather than administering a payroll, or India is becoming central to your plans.

Most companies cross over somewhere between ten and twenty-five people — though headcount is the weaker signal. The stronger one is whether you have started wanting things the EOR arrangement will not let you do.


What to get right at hire one

If you do nothing else:

  1. Decide employee versus contractor honestly, based on how the person will actually work
  2. Structure salary properly from the first offer, so you never have to restructure downward
  3. Have the employment contract drafted for Indian law, not adapted from your home template
  4. Map the statutory thresholds you will cross in the next twelve months
  5. Confirm which state’s rules apply to each person you hire

That is perhaps a fortnight of work, once. It removes almost every expensive problem that would otherwise surface in year two.

The companies that struggle are rarely the ones that made a bad decision. They are the ones that never made a decision at all — they simply carried their home-country arrangement across, and discovered eighteen months later that it had never applied.

About the author

Naresh K Matta is a senior HR and business advisor based in New Delhi, with over two decades across manufacturing, solar EPC, cable and media, IT and ITeS, BPO and law firms. He works as a fractional CHRO, POSH external member and labour law advisor.

Call WhatsApp