How Should Operations Leaders Manage India Payroll Remotely?

Every employee on an Indian payroll triggers a Provident Fund contribution of 12% of basic wages from the employer and 12% from the employee, due to the EPFO portal by the 15th of the following month. Miss that date and the company owes damages under Section 14B of the EPF Act, calculated on a sliding scale that can reach 25% per annum on the delayed amount. That single deadline, repeated every month across PF, ESI, Professional Tax, and TDS, is the real shape of the problem when operations leaders manage India Payroll remotely from a head office outside the country. This is a calendar and documentation problem, not a strategy problem, and it breaks in specific, predictable places.

What Laws Govern India Payroll for a Remote Team?

The starting point is knowing which laws actually apply, because "local labour law" is not specific enough to hand to a payroll vendor. India payroll runs on the Employees' Provident Fund and Miscellaneous Provisions Act, 1952 (EPF), the Employees' State Insurance Act, 1948 (ESI, for gross monthly wages at or below ₹21,000), the Payment of Gratuity Act, 1972, the Payment of Bonus Act, 1965, the Payment of Wages Act, 1936, and state-level Professional Tax and Shops and Establishments Acts.

India has also consolidated much of this under four new Labour Codes, being rolled out progressively through state notifications rather than one national switch date. The codes broaden the legal definition of "wages" for PF and gratuity calculations, which means a payroll structure built on the older definitions can quietly under-provision once a state fully adopts the new code. Operations leaders managing India Payroll remotely should ask their payroll vendor, every quarter, which of the four codes have been notified in each state where they employ people.

Contract Hiring vs Full-Time Hiring: How Payroll Obligations Differ

The compliance path changes completely depending on whether someone is engaged as a contractor or hired full-time, and treating the two as interchangeable is where most exposure starts.

A contractor engaged without an Indian entity carries no direct PF or ESI obligation for the hiring company, but it creates real misclassification risk if the relationship looks like employment in practice. Fixed working hours, a single client, company-issued equipment, and ongoing supervision are the factors Indian authorities examine when a contractor is challenged as a misclassified employee.

A full-time employee, by contrast, triggers the complete statutory stack: PF, ESI where applicable, gratuity accrual, bonus eligibility under the Payment of Bonus Act for those earning below the wage threshold, and TDS deduction under Section 192 of the Income Tax Act. Full-time hiring also carries a formal exit process, known as full and final settlement, which includes unused leave encashment and any accrued gratuity, and which most remote finance teams underestimate until an employee actually resigns.

How Do Operations Leaders Manage India Payroll Remotely Without a Local Team?

Under an Employer of Record (EOR), the EOR entity carries the statutory employer obligations, including PF, ESI, gratuity accrual, and TDS deduction, while the operations leader keeps day-to-day management control of the person's work. Under an owned entity, the company itself is the registered employer and holds the full compliance burden directly, including Shops and Establishments renewals in every state where it operates.

Most companies we work with start on EOR and move to their own entity once India headcount crosses roughly 40 to 50 people, the point where fixed entity compliance costs start running cheaper per employee than an EOR fee. That crossover shifts depending on salary bands and how many states the team spans.

This is usually the exact point where operations leaders manage India Payroll remotely for the first time without a person on the ground, and it's the point where the choice of model matters most. Two shifts are changing how this decision gets made.

First, payroll platforms increasingly run AI-assisted reconciliation, flagging wage-band changes, threshold crossings, and missed filing windows automatically instead of relying on a person remembering to check.

Second, as GCC hiring accelerates across Bengaluru, Pune, and Hyderabad, more companies are moving from EOR to a dedicated entity earlier than they used to, closer to 30 to 35 people, because direct control over compensation structure matters more once a team is running core engineering or analytics work rather than a pilot project. Cloud-based, multi-country payroll platforms have made this transition faster to execute than it was even a couple of years ago, since a company doesn't need to rebuild its entire payroll workflow from scratch when it switches structures.

If you want a compliance audit of your current India setup before you commit to either model, our team can walk through it with you here: Talk to AnjuSmriti Global about your India payroll.

A Compliance Checklist for Remote India Payroll

Use this as a working checklist against your current setup.

Requirement	Applies To	Filing Frequency	Common Miss
EPF registration and contribution	Full-time employees	Monthly, by the 15th	Missed threshold when a raise crosses a wage band
ESI registration and contribution	Employees earning ≤ ₹21,000 gross	Monthly	Not exiting the scheme after a raise crosses the threshold
Professional Tax	State-specific, all employees	Monthly, per state	Treating one state's slab as identical to another
Shops and Establishments registration	All employers with a physical or registered presence	Renewed periodically	Lapsed renewal with no new hires that quarter
TDS under Section 192	Full-time employees	Monthly deduction, quarterly return	Incorrect regime applied after a mid-year tax declaration change
Gratuity accrual	Full-time employees, post 5 years	Provisioned monthly, paid on exit	Not provisioning from year one
Full and final settlement	Departing full-time employees	On exit	Leave encashment miscalculated against the wrong policy year

Real Costs: What India Payroll Looks Like in Rupees

For a mid-level engineer or payroll operations analyst, expect ₹14 to 20 lakh per annum (LPA) fixed cost to company. A senior engineer or payroll manager typically runs ₹28 to 38 LPA. A lead engineer or India payroll and compliance head commands ₹45 to 65 LPA, especially in Bengaluru and Hyderabad, where GCC demand for that seniority is highest.

On top of base salary, employer-side statutory costs add roughly 12% for PF, up to 3.25% for ESI where it applies, and an accrued 4.81% for gratuity, pushing true employer cost 15 to 20% above the stated CTC once these are provisioned correctly. An EOR relationship typically adds 8 to 15% of CTC or a flat monthly fee per head. A dedicated payroll vendor for an owned entity usually charges a flat per-employee fee that becomes cheaper than EOR percentages once headcount clears the range mentioned earlier.

At AnjuSmriti Global, we onboard new payroll accounts over four weeks: document and registration audit in week one, a reconciliation calendar mapped to the client's home-country fiscal close in week two, a parallel payroll run in week three to catch discrepancies before cutover, and full handover in week four with a compliance pack delivered five working days before month-end close.

In one account, a parallel-run audit caught nine employees in Bengaluru who should have exited the ESI scheme after a mid-year raise crossed the wage threshold; nobody had flagged it, and correcting it before an actual inspection avoided a penalty that would otherwise have run into several lakhs of rupees.

What's Next for Remote India Payroll

Over the coming months, expect the Labour Codes to keep rolling out state by state, which means the compliance baseline in Karnataka, Maharashtra, and Telangana will keep drifting apart rather than staying uniform. EOR-to-entity transitions are also happening earlier than before, as GCC competition pushes more companies to want direct control over India compensation sooner.

If you'd like our team to audit your current India payroll setup or build one from scratch, talk to us here: Get an India payroll compliance review.

---

Interesting Reads:

What Are India's Payroll Deadlines for Japanese Firms?

How Should Dutch Companies Approach EOR Hiring in India?

When 50+ India Employees Means You Need an Entity

FAQs

1.Does gratuity apply if our India team is on an EOR contract instead of our own entity?

Yes. Gratuity follows the employment relationship, not who processes the payroll. If the EOR is the registered employer, gratuity accrues under their entity and is usually built into the monthly fee. If you move from EOR to your own entity later, confirm continuity of service is documented in writing, since gratuity eligibility depends on five continuous years of service and a gap in the record can create a later dispute.

2.How do we handle Professional Tax across Karnataka, Telangana, and Maharashtra?

Each state requires a separate registration, filing portal, and deadline. Karnataka applies a flat rate, Telangana runs its own portal on a different renewal cadence, and Maharashtra uses a three-tier slab. Running three separate filing calendars manually from a foreign finance team is where most deadlines get missed. Most companies at this headcount move to one payroll vendor already registered in every state where they employ people.

3.What happens to ESI when an employee's salary crosses ₹21,000 mid-year?

The employee exits mandatory ESI coverage, but the exact timing depends on where the raise lands within ESI's fixed half-yearly contribution cycle, so a mid-cycle raise does not always trigger an immediate exit. This threshold event is one of the most commonly missed items in manual payroll processes, since nothing forces a review unless someone is actively tracking each employee's gross wage band.

4.Can TDS be deducted correctly without an Indian entity, using only an EOR?

Yes. The EOR entity is the registered employer of record and is responsible for deducting TDS under Section 192 of the Income Tax Act, based on the employee's declared tax regime and investment declarations, and for issuing Form 16 at year-end. This removes the TDS obligation entirely from your foreign payroll system and keeps the filing responsibility with a party that already holds the required registrations in India.

5.How early should we start provisioning for gratuity if we haven't been?

Immediately, regardless of current tenure levels. Gratuity is calculated on the last drawn basic salary at the time of exit, not the salary when the liability began, so unprovisioned gratuity grows through both tenure and salary increases at the same time. Most finance teams we work with start provisioning from an employee's first day at roughly 4.81% of basic wages, even though the payout itself only happens after five years.

6.Do the new Labour Codes change how we should run remote India payroll right now?

The four codes are notified state by state rather than on one national date, so the answer depends on which states your team is based in. They matter because the definition of "wages" used for PF and gratuity calculations has broadened under the new codes, and a payroll setup built on the older definition can quietly under-provision once a given state fully adopts the change.

7.What's the realistic timeline to set up compliant payroll for our first 10 India hires?

Through an EOR, compliant payroll can be running within 2 to 3 weeks of finalized offers, since the EOR's registrations already exist and only your employee records need to be added. Setting up your own entity instead typically takes 8 to 14 weeks for incorporation, PAN and TAN allotment, and PF and ESI establishment registration before the first payroll run can happen.

8.What documentation should we require monthly to stay audit-ready?

At minimum: PF challan copies with payment confirmation, ESI contribution summaries, Professional Tax payment receipts by state, a TDS deduction summary reconciled to quarterly returns, and a monthly gratuity accrual statement. Requiring this pack ahead of your month-end close, rather than on request, means your home-country finance team never has to chase a vendor for documentation partway through a close cycle.