Most payroll teams discover multi-state compliance the same way: a notice arrives from a state labour department for a state the company doesn't have an office in.
Looking for payroll software?
Check out Techimply's List of the Best Payroll Software in India for your business.
It's usually one remote employee. Somebody hired a developer in Bengaluru, payroll kept running from the Gurgaon head office, and nobody realized that hiring one person in Karnataka created registration and deduction obligations in Karnataka.
The salary was correct. The compliance wasn't. That gap is what changes when your people stop sitting in one state.
The Structural Reason This Is Hard
India runs two parallel compliance tracks, and they don't merge.
Central statutes apply the same everywhere: Provident Fund at 20 or more employees with a ₹15,000 wage ceiling, ESI at 10 or more in most states with a ₹21,000 ceiling, TDS, and the Labour Codes.
State statutes vary by state, drawing authority from Entry 60 of the State List and Article 276 of the Constitution: professional tax, labor welfare fund, shops and establishments, minimum wages, and state leave rules.
One payroll run has to satisfy both, and the state half changes depending on where each person physically works. This isn't a formula with a variable in it. It's separate rule sets applying to different employees in the same payroll. Businesses managing employees across multiple locations often rely on global payroll software to automate jurisdiction-specific payroll calculations and reduce compliance errors.
The rule that determines everything
State obligations follow the employee's physical work location, not the company's registration.
A Delhi-registered company with staff in Noida applies Uttar Pradesh rules to them. Staff in Gurgaon fall under Haryana. A person working from home in Kolkata is in West Bengal.
The company's registered address is irrelevant to this question. So is the employee's postal address if they work somewhere else.
Professional Tax: Where Most Errors Land
PT is the smallest number on the payslip and the largest share of multi-state audit findings.
What's fixed
Article 276(2) caps PT at ₹2,500 per person per financial year. That ceiling has held since the Sixtieth Amendment in 1988. Maharashtra is the only state that reaches it; most others land between ₹1,200 and ₹2,400.
The amount paid is deductible from gross salary under Section 16(iii) of the Income Tax Act.
What varies, and how badly
Not all states levy it. Roughly 21 states and union territories do. Delhi, Haryana, Uttar Pradesh, Rajasthan, Punjab, Uttarakhand, and Goa do not.
This cuts both ways, and both cuts hurt:
- Not deducting in a PT state is a compliance gap with retrospective liability.
- Deducting in a non-PT state is an unauthorized deduction from salary. You've taken money from an employee and remitted it to an authority that had no claim to it, and recovering it means a refund application to that state.
Slabs differ. So does the salary definition, though most states reference gross. Check your specific state's act rather than assuming.
Filing frequency differs. Monthly in most states, half-yearly in Tamil Nadu and Kerala.
PTEC and PTRC
Two registrations are routinely confused. PTEC is the company's own PT liability. PTRC is for the tax you deduct from employees. Most employers need both.
The trigger is the existence of one salaried employee in the state. Not ten, not an office. One.
Minimum Wages Across States
Minimum wages are state-set and vary along four axes at once: state, skill category (unskilled, semi-skilled, skilled, highly skilled), industry, and often geographic zone within the state. Revisions typically land around April and October.
Three states with four skill categories and two revisions a year is twenty-four data points that change annually, before industry variation. Nobody tracks this reliably by memory, and the failure mode is quiet: you keep paying last year's rate, and the shortfall accumulates per employee per month until an inspection finds it.
Under the labor codes, penalties for wage payment failures reach ₹50,000 for a first offense, but the back-pay liability is usually the larger number.
Labour Welfare Fund
Separate from PT, state-specific, small, and forgotten more often than anything else on this list. Different states have different rates, different frequencies, and different applicability. It's forgotten precisely because it's small, and the penalty for a missed small contribution is disproportionate to the amount.
What the labor codes did and Didn't Change
The four labor codes came into force on 21 November 2025. Two clarifications matter here.
They did not remove state variation
The most common misreading. Professional Tax, Labour Welfare Fund, and minimum wages remain state-governed. Multi-state payroll didn't simplify; it gained a central layer above the state layer that was already there.
State implementation is uneven
This is the live operational issue. State-level rules under the Codes are notified independently by each state, and coverage has been patchy.
Where a state hasn't notified its rules, the earlier state laws continue to apply. So a multi-state employer can genuinely be operating under the new framework in one state and the legacy framework in another, at the same time, for the same policy question.
That means the compliance position moves month to month. Verify status per state against the Ministry of Labor and Employment and the relevant state labor department before relying on a fixed configuration.
The wage definition
The Codes bring a revised wage definition, widely discussed as requiring basic pay to be at least 50% of total remuneration. It cascades into PF, gratuity, bonus, and overtime, since all compute off the wage base. Modern Payroll & Benefits Software helps organizations calculate statutory deductions, employee benefits, and salary components under changing wage regulations.
For multi-state employers this interacts awkwardly with minimum wages. A structure that satisfies the wage definition and clears the minimum wage in one state may not clear a different state's rate for the same skill category.
What Your Payroll System Must Do
Work-location state at the employee level. A field distinct from the company's registered state and from the employee's postal address, driving rule selection. Without this, multi-state compliance is manual, whatever else the software offers.
Test it during evaluation: change one employee's work-location state from Delhi to Karnataka and check whether PT starts applying on its own.
Automatic PT by state, applying the right slab, deducting nothing in non-PT states, using the correct salary definition, and generating challans on that state's calendar.
Minimum wage tracking with updates. Ask directly who updates rates when a state revises in April. If the answer is you, the software isn't doing this.
LWF by state, with the right rate and frequency applied automatically rather than tracked on the side by someone who remembers it exists.
A jurisdiction-specific compliance calendar. Deadlines differ by state and statute. One reminder list assuming uniform dates will be missed.
Many organizations also use compliance management software to monitor statutory deadlines, maintain audit trails, and reduce the risk of missing state-specific filings.
Multi-state reporting and registers, so you can produce what a specific state's inspector asks for without reassembling it.
Where This Actually Breaks
The employee who moved. Someone relocates from Gurgaon to Bengaluru. HR updates the address. Nobody updates the work-location state. Payroll runs Haryana rules for a Karnataka employee for eleven months.
Relocation is a payroll event, not an address change. That distinction needs to exist in your process. Integrating payroll with HR software ensures employee transfers, remote work locations, and organizational changes automatically flow into payroll records.
Head office configuration applied to everyone. The most common systemic error produces both failure modes at once: no PT for employees who owe it and PT for employees who don't.
One registration obtained, the other forgotten. PTEC without PTRC, or the reverse.
Minimum wage revisions are missed because nobody watches state gazettes in April and October.
A state discovered during an audit. The remote hire who never entered the compliance scope. Expensive, because liability is retrospective from the date the obligation arose, not the date you noticed.
Assuming the codes standardized everything. They added a central layer; the state layer is still there and still varies.
A Practical Sequence
Map your states honestly. List every state where any employee physically works, including remote staff and anyone who moved. Most companies are surprised by this list, and the surprise is the point.
Per state, establish: PT applicability and slabs, LWF applicability, shops and establishments status, minimum wages by skill category, and whether the state has notified its labor code rules.
Register where required. PTEC and PTRC, where PT applies, and shops and establishments, where required.
Configure work-location state per employee and test that rules follow it.
Make relocation a tracked event with a payroll implication, not an HR data update.
Schedule reviews. April and October for minimum wages. Quarterly for state code notification status while the transition runs.
Conclusion
Multi-state payroll means one payroll run satisfying central statutes plus a different set of state statutes for every state where someone physically sits. Central rules are uniform. State rules aren't, and the labor codes didn't change that. The single configuration that matters most is work-location state per employee, because everything downstream depends on it and the most common failure is a remote employee nobody mapped. Professional Tax is capped at ₹2,500 a year, several major states, including Delhi and Haryana, don't levy it, and deducting where you shouldn't is as much a problem as failing to deduct where you should. One employee in a state triggers registration. Minimum wages move twice a year across four dimensions. And labor code implementation remains uneven by state, so verify per state rather than assuming one national position. Map the states first. The rest is configuration.
