What Should US Companies Check Before Running Payroll in India?

Miss the Professional Tax registration in even one Indian state and you're looking at penalties that start at ₹5 per day of delay, compounding fast once a labour inspector flags it during an audit. That's the kind of detail that trips up US companies the first time they run payroll in India, not the big, obvious things like PF or income tax, but the state level filings nobody warns them about. After correcting payroll for more than 40 US companies expanding into India, the same five or six gaps show up almost every time. Below is the checklist used with clients before their first payroll cycle runs, along with the reasoning behind each item, so it's clear why US companies check before running payroll in India in the first place.

Why Does Payroll Compliance in India Confuse US Companies at First?

India doesn't run payroll under one federal law the way a US company might expect coming from a single employer registration system. Payroll compliance here is layered: central acts like the EPF Act and ESI Act sit on top of state specific rules like Professional Tax and the Shops and Establishments Act, and that second layer changes depending on whether the team sits in Bengaluru, Pune, Hyderabad, or Delhi NCR. A Delaware C corp opening its first Indian entity in Bengaluru will register differently, and pay different professional tax slabs, than the same company opening in Pune six months later.

This confusion shows up most often with Series B and C US SaaS companies setting up their first India Global Capability Center (GCC). The founder or finance lead has usually handled contractor payments before, sometimes through a US payroll platform that simply doesn't have the statutory logic for Indian withholdings built in. The moment the team crosses from two or three contractors to a fifteen to twenty person entity, gaps appear: no ESI registration despite wages under the ₹21,000 per month threshold, PF contributions calculated on the wrong wage base, or gratuity liability not provisioned for at all because nobody expected a five year vesting obligation to matter for a startup.

There's also a timing mismatch that catches finance teams off guard. Indian statutory filings run on a monthly cycle, PF and ESI both need to be remitted by the 15th of the following month, and Professional Tax deadlines vary by state, sometimes falling as early as the 10th. A US finance team used to a bi weekly or semi monthly payroll cadence often builds its first India payroll calendar around US pay dates, then realizes the compliance deadlines don't line up only after the first missed filing. None of this is exotic, it's just unfamiliar, and unfamiliar becomes expensive when penalties are calculated per day of delay.

Which Indian Cities Add the Most Payroll Complexity for US Employers?

Not every Indian city adds the same payroll complexity, and this matters when deciding where to hire.

Bengaluru and Pune carry the highest density of US GCC payroll setups, and both fall under Karnataka and Maharashtra Professional Tax regimes respectively, two of the more aggressively enforced PT states in the country. Karnataka's PT slab tops out at ₹200 per month for anyone earning above ₹15,000 per month. Maharashtra caps annual PT at ₹2,500, split across an uneven payment schedule that isn't monthly like most other statutory dues. Get this schedule wrong and it shows up at the first compliance audit.

Hyderabad and Chennai are comparatively simpler on Professional Tax but bring their own Shops and Establishments Act variations. Telangana and Tamil Nadu each require separate state registration even if the company is already registered in Karnataka, something that trips up companies who assume one registration covers every India office.

Delhi NCR adds one more layer worth flagging: Haryana and Uttar Pradesh, both part of the NCR labour market, carry Professional Tax exemptions that Delhi itself doesn't. That means identical salaries paid to employees sitting twenty kilometers apart across state lines can carry different statutory deductions. Walking new clients through this map before their first hire lands on payroll is a standard first step, because it changes net pay calculations city by city.

What Indian Laws Actually Govern Payroll for a US Company?

Indian payroll compliance sits under multiple acts simultaneously, and missing any one of them creates real financial exposure, not just paperwork risk, which is exactly why US companies check before running payroll in India rather than assuming one registration covers everything.

The Employees' Provident Fund and Miscellaneous Provisions Act, 1952 (EPF Act) requires a 12% employer contribution and a matching 12% employee contribution on basic wages, mandatory once an India entity crosses 20 employees.

The Employees' State Insurance Act, 1948 (ESI Act) applies to employees earning up to ₹21,000 per month gross, requiring 3.25% employer and 0.75% employee contributions toward health and disability cover, a threshold easy to miss for companies who assume ESI only applies to blue collar staff.

The Payment of Gratuity Act, 1972 creates a liability of roughly 4.81% of basic pay per year of service, payable once an employee crosses five years with the company, and most US finance teams don't provision for it in year one because it feels distant, until an early employee hits year five.

Then there's the Income Tax Act, 1961, under which Section 192 makes TDS (tax deducted at source) on salaries mandatory, calculated against slab rates and remitted monthly through Form 24Q filings. Every state also layers its own Shops and Establishments Act registration and Professional Tax rules on top, neither of which is optional even for a small India headcount.

The mistake seen most often: US companies treat India entity registration, usually a Private Limited Company under the Companies Act, 2013, as the finish line, when it's actually the starting point for six or seven parallel compliance obligations that all activate the day payroll first runs. Companies that route payroll through an Employer of Record (EOR) instead of standing up their own entity push this compliance burden onto the EOR provider, which is exactly why EOR is often the faster path for companies not ready to manage Indian statutory filings directly.

What Belongs on the Pre Payroll Compliance Checklist for India?

This is the exact checklist run through with every new US client before their first Indian payroll cycle goes live. Treat it as a floor, not a ceiling, since state specific add ons apply depending on where a team sits.

List	Check	Why It Matters	Typical Deadline
1	PAN and TAN registration for the India entity	Required before any salary TDS can be deducted or remitted	Before first payroll run
2	EPF registration (mandatory above 20 employees)	12%+12% contribution on basic wages; retroactive penalties apply if delayed	Within 1 month of crossing threshold
3	ESI registration (if any employee earns ≤ ₹21,000/month gross)	3.25%+0.75% contribution for health cover	Before first eligible payroll
4	State specific Professional Tax registration	Varies by state; non compliance draws a daily penalty	Varies (state dependent)
5	Shops and Establishments Act registration	Required per state office location, not just per entity	Before opening an office in that state
6	Gratuity liability provisioning	4.81% of basic per year of service, vests at 5 years	Ongoing, from employee day 1
7	Form 24Q (quarterly TDS return) filing calendar	Mismatched with US payroll cadence if not planned	Quarterly
8	FEMA compliance for cross border fund transfer	Governs how the US parent funds the India payroll account	Set up before first remittance
9	POSH Act internal committee (if 10+ employees)	Mandatory internal complaints committee for workplace safety	Within 30 days of crossing threshold
10	Bank account and payroll software localized for INR statutory deductions	US built payroll tools often lack Indian statutory logic	Before go live

Most US companies get items 1, 2, and 7 right because their India entity setup lawyer flags them. Items 4, 5, and 9 are the ones most often found missing during a payroll health check, largely because they're state triggered rather than centrally triggered, and nobody outside India tends to track state by state variation. Running this list against a current setup before go live is the single highest leverage hour a finance team can spend, and it's a large part of what US companies check before running payroll in India when they've already had one bad experience.

Contract Hiring vs Full Time Hiring in India: What Should US Companies Choose?

This is one of the first decisions a US company makes, often before payroll even enters the conversation, and it shapes everything downstream.

Contract hiring works well for short term projects, specialist skills needed for a defined scope, or a first test of the India market before committing to a formal entity. Contractors are paid against invoices, don't trigger EPF, ESI, gratuity, or Shops and Establishments obligations, and can be onboarded within days. The trade off is legal exposure: if a contractor works fixed hours, reports to a manager, and functions like an employee in every practical sense, Indian labour authorities can reclassify the relationship, creating retroactive statutory liability plus penalties. This is a common gap in early stage GCC builds, where "contractor" on paper looks like "employee" in practice.

Full time hiring, whether through an owned entity or an EOR, brings the full statutory stack: PF, ESI where applicable, gratuity provisioning, Professional Tax, and Shops and Establishments coverage. It costs more to administer but it's the structure that scales, supports long term retention, and avoids the misclassification risk that contract arrangements carry once a working relationship starts to resemble employment. Most companies that plan to keep India talent for more than a year move from contract to full time within the first six to twelve months, once the role and the person are proven out.

Where Compliance Nearly Went Wrong: A Real Case

The onboarding process for a new US client starts with a two week compliance mapping phase before a single payroll run happens: confirming entity structure, mapping every state where employees sit, and cross checking EPF, ESI, and PT applicability against actual headcount and salary bands. From there, a monthly payroll calendar gets built around Indian statutory deadlines rather than US pay dates, and the first two cycles run in parallel with a compliance audit to catch anything the mapping phase missed.

One case involved a US based fintech company, roughly 60 employees globally with 22 based across new Bengaluru and Pune offices, running India payroll through a generalist HR platform for eight months before switching. On paper their PF and TDS looked fine.

What almost went wrong: their Pune office had never registered under Maharashtra's Shops and Establishments Act, because the platform they used had only handled the Bengaluru registration and assumed one entity registration covered both cities. This surfaced during the onboarding compliance sweep, three weeks before their annual labour audit window opened.

Filing retroactively cost a modest compounding penalty, but had it surfaced during the actual audit instead, the exposure would have been materially higher and could have flagged the entity for closer scrutiny on every subsequent filing. AnjuSmriti Global rebuilt their payroll calendar, added the missing state registration, and they've since run 14 clean monthly cycles with zero compliance flags at their most recent audit.

For technical and mid management hires layered on top of payroll, the same team also runs a standard IT recruitment vetting process, so clients aren't just getting clean payroll, they're getting payroll built around a team that was properly assessed going in, which matters when gratuity and PF liabilities are calculated against tenure from day one.

What Does Payroll in India Actually Cost, Beyond the Headline Salary?

US finance teams budgeting for their first India payroll cycle usually anchor on the CTC (cost to company) figure and miss the statutory layer sitting on top of it.

Here's what that looks like for a typical mid size tech role across three seniority levels, all figures in INR per annum.

Mid level (3 to 5 years experience): ₹12,00,000 CTC, plus employer EPF (about ₹1,00,000), gratuity provision (about ₹57,700), and PT (about ₹2,400), bringing effective employer cost close to ₹13.6 lakh.

Senior (6 to 9 years experience): ₹22,00,000 CTC, plus employer EPF (about ₹1,80,000), gratuity provision (about ₹1,05,800), and PT (about ₹2,400), bringing effective employer cost close to ₹25.1 lakh.

Lead or Principal (10+ years experience): ₹35,00,000 CTC, plus employer EPF (about ₹2,80,000), gratuity provision (about ₹1,68,300), and PT (about ₹2,400), bringing effective employer cost close to ₹39.7 lakh.

On top of these, an EOR fee typically runs 8 to 15% of CTC for companies without their own entity, or a fixed monthly per employee fee for those maintaining one; recruitment fees sit separately, scoped per mandate rather than baked into payroll cost. Compared to the fully loaded cost of an equivalent US based mid or senior engineer, where base salary alone often exceeds $120,000 to $180,000 before any employer tax burden, most clients see a 55 to 65% reduction in fully loaded engineering cost.

What Trends Are Shaping India Payroll and Hiring Right Now?

More US companies are shifting from ad hoc contractor payroll to formal EOR or entity based payroll as India tightens enforcement on Professional Tax and Shops and Establishments registrations at the state level. Several states have digitized their inspection process, which means gaps that used to go unnoticed for years now surface within a single filing cycle.

AI adoption is also reshaping hiring plans for India GCCs. Roles that once needed large support teams, data annotation, first line QA, basic reporting, are being restructured around smaller teams supported by AI tooling, while demand grows for senior engineers who can build and manage that tooling. This shifts headcount plans toward fewer, more senior hires per function rather than large junior benches, which changes gratuity and PF liability math since senior hires accrue statutory cost faster.

Cloud infrastructure spend is also moving hiring decisions closer to where engineering talent already sits, with Bengaluru, Pune, and Hyderabad continuing to anchor most GCC builds because of established cloud vendor support and mature local vendor ecosystems. At the same time, remote first hiring is spreading hiring further into tier two cities, which introduces new state level Professional Tax and Shops and Establishments variations that many payroll setups haven't accounted for yet.

The companies getting the most value out of India payroll are the ones checking every layer, EPF, ESI, Professional Tax, gratuity, and state registration, before the first salary goes out, not after an audit flags a gap. That single habit, more than any platform or provider choice, is what separates a clean first year from a costly one.

Final Checklist: What US Companies Should Confirm Before Running Payroll in India

Before the first salary is processed, confirm entity structure and state registrations, wage band checks against EPF and ESI thresholds, a payroll calendar built around Indian statutory deadlines, gratuity provisioning from day one, and a funding structure that satisfies FEMA requirements. Getting this list right the first time is, in practice, the entire answer to what US companies check before running payroll in India, and it's far cheaper to confirm upfront than to correct after an audit.

If planning a first India payroll cycle, get in touch and the same compliance mapping used with every new client can be run for your team.

---

Interesting Reads:

What Should US Companies Use Instead of PEO in India?

When Should You Hire Full-Time in India: Direct or EOR?

How Should You Scale an India Engineering Pod: Contractors or EOR?

FAQs

1.Does a US company need its own India entity before it can run payroll, or can it pay employees directly from the US?

No. A US company cannot legally pay India based employees directly from a US bank account as regular salaried staff without either an India entity or an Employer of Record arrangement. Direct payments to someone treated as an employee create FEMA remittance issues and a strong likelihood that Indian tax authorities treat the setup as an unregistered permanent establishment, triggering corporate tax exposure. Most companies incorporate a Private Limited subsidiary (4 to 6 weeks) or use an EOR, which can go live in under two weeks.

2.How does Professional Tax differ between Karnataka and Maharashtra, and does it matter for a small India team?

Yes, even for a 5 to 10 person team. Karnataka charges a flat ₹200 per month for anyone earning above ₹15,000 monthly, remitted monthly. Maharashtra caps Professional Tax at ₹2,500 per year but splits payments unevenly across the year rather than in equal monthly installments, which trips up systems built for flat monthly deductions. Neither registration transfers to a second state, and missing either draws a daily penalty that compounds the longer it stays unfiled.

3.When does gratuity liability actually become payable, and should it be provisioned from year one?

Gratuity becomes payable once an employee completes five continuous years of service, calculated at roughly 15 days of basic pay per completed year, about 4.81% of annual basic salary. Legally, payment is only owed at the five year mark or on termination after that point, but provisioning it as an accruing liability from day one avoids a sudden five figure INR payout appearing on the books in year five with no prior budgeting. EOR providers typically build this into their monthly fee automatically.

4.What happens if a company has been running India payroll without ESI registration and some employees fall under the ₹21,000 threshold?

This is one of the most common gaps found during compliance audits, since companies often assume ESI applies only to blue collar workforces. If any employee's gross monthly wage falls at or below ₹21,000, ESI registration and contribution (3.25% employer, 0.75% employee) becomes mandatory regardless of role or industry. Retroactive registration is possible but comes with backdated contribution liability plus interest, and repeated lapses can trigger closer scrutiny on other filings.

5.Can a US company run India payroll using its existing US payroll platform, or does it need India specific software?

Most US built payroll platforms, even well known global ones, don't have India's statutory logic built in natively. Correct EPF wage ceiling calculations, ESI eligibility checks, state specific Professional Tax slabs, and Form 24Q TDS filing formats all require India localized configuration or a dedicated India payroll module. It's possible to run payroll successfully on a global platform, but usually only after significant custom configuration with a local compliance partner, which is why many companies route payroll through outsourcing or an EOR instead.

6.How often do Indian payroll compliance deadlines fall compared to a typical US bi weekly cycle?

Indian statutory payroll compliance runs almost entirely on a monthly cycle, not bi weekly. EPF and ESI contributions must be remitted by the 15th of the following month, Professional Tax deadlines vary by state (some as early as the 10th), and TDS returns via Form 24Q are filed quarterly. Building a separate India specific compliance calendar rather than forcing Indian filings into a US pay schedule avoids the mismatch that causes most late filings in first year setups.

7.Do US companies need a POSH Act internal committee even for a small India team?

Yes. The Prevention of Sexual Harassment (POSH) Act, 2013 requires an Internal Complaints Committee once an India office crosses 10 employees, regardless of the parent company's location or existing US workplace policies. This is a commonly missed requirement because US companies assume existing US HR policies satisfy the obligation; they don't, since POSH requires a specific India registered committee structure with defined reporting timelines that most global HR handbooks don't cover.

8.Is it cheaper to set up an owned India entity or use an EOR when planning to hire 15 or more people?

At 15 or more employees, the math often favors entity setup, since EOR fees (typically 8 to 15% of CTC) scale linearly with headcount while entity and compliance costs are largely fixed once a team crosses a certain size. That "cheaper" only holds if the compliance overhead, EPF, ESI, Shops and Establishments, and POSH management, is budgeted for separately. Many companies run their first 12 to 18 months through EOR to validate the India team before switching to their own entity.