A Delhi-registered company hires a salesperson who works from home in Bengaluru. Payroll runs from the head office, the salary is correct, and everyone is satisfied until a Karnataka labor department notice arrives asking why no professional tax was deducted and no PTRC registration exists for the state.
Looking for HR software?
Check out Techimply's List of the Best HR Software in India for your business.
Nothing was stolen and nobody was underpaid. The company simply applied Delhi's rules to a Karnataka employee, and Delhi doesn't levy professional tax at all. That's multi-state compliance in one sentence: the salary can be right while the compliance is wrong.
This is a practical guide to what actually varies across states, what changed under the labor codes, and what your HR software genuinely needs to handle if you employ people in more than one state.
Why India Has Two Compliance Tracks
The structural fact that explains everything else: some labor obligations are central and some are state, and they run simultaneously.
Central obligations apply nationally with uniform rules. Provident Fund, ESI, TDS, and the four labor codes sit here. PF is mandatory at 20 or more employees with a ₹15,000 wage ceiling for mandatory coverage; ESI applies at 10 or more in most states with a ₹21,000 ceiling.
State obligations vary by state, and they derive from constitutional authority. Under Entry 60 of the State List and Article 276, states have their own power to tax professions and regulate establishments. Professional Tax, Labour Welfare Fund, Shops and Establishments registration, minimum wages, and state leave rules all live here.
This creates a genuinely dual-track obligation. A single formula cannot auto-switch between them, because they aren't variations of one rule. They're separate rule sets that both apply, and the state one is determined by where the employee physically sits.
The rule that catches everyone
State obligations follow the employee's physical work location, not the company's registered address.
A Delhi-registered company with staff in a Noida office deducts Uttar Pradesh rules for those employees. Staff in Gurgaon fall under Haryana. A remote employee in Kolkata is governed by West Bengal, regardless of where the payroll team sits.
This was manageable when offices were physical. With remote and hybrid work, a company that never opened a branch anywhere can accumulate obligations in six states because six people chose to live there. That's the compliance exposure most growing companies don't realize they've taken on.
Professional Tax: The Most Commonly Botched Item
PT is small in rupee terms and outsized in audit findings, which makes it worth understanding precisely.
The basics that are actually fixed
Article 276(2) of the Constitution caps professional tax at ₹2,500 per person per financial year. That ceiling has stood since the Sixtieth Amendment in 1988, and no state can exceed it regardless of salary. Maharashtra is the only state that reaches the full ₹2,500; most others cap between ₹1,200 and ₹2,400.
The full amount paid is deductible from gross salary under Section 16(iii) of the Income Tax Act, so getting it right is in the employee's interest too.
The part that varies
Not every state levies PT at all. Roughly 21 states and union territories do. Delhi, Haryana, Uttar Pradesh, Rajasthan, Punjab, Uttarakhand, and Goa do not.
That matters in both directions. Failing to deduct in a PT state is a compliance gap. Deducting in a non-PT state is an unauthorized deduction from an employee's salary, which is its own problem and requires a refund application to a state authority that never should have received the money.
Beyond applicability, slabs differ, the salary definition differs (most states reference gross, but confirm your state's act), and filing frequency differs. Some states collect monthly, while Tamil Nadu and Kerala work half-yearly.
PTEC and PTRC
Two registrations, and confusing them is the single most common audit finding. PTEC covers the company's own PT liability. PTRC covers the deductions you make from employees. You typically need both.
The threshold is the existence of a salaried employee in that state, not a headcount. One sales rep working from a home office in Bengaluru triggers both obligations for the employer.
What the Labour Codes Changed, and What They Didn't
India's four labor codes came into force on 21 November 2025, consolidating 29 older laws. Two clarifications matter for multi-state employers.
The codes did not eliminate state variation
This is the most common misconception. National codes exist, but professional tax, labor welfare fund, and minimum wages remain state-governed. The multi-state payroll tool didn't get simpler; it acquired a new central layer on top of the existing state layer.
State implementation is uneven, and that's the operational problem
Here's the detail that matters most right now: state-level implementation rules under the Codes are notified independently by each state, and coverage has been uneven.
The practical consequence is uncomfortable. Where a state hasn't updated its rules, the old state labor laws continue running in parallel. So a multi-state employer may be operating under the new Code framework in one state and the legacy framework in another, simultaneously, for the same policy.
This isn't a permanent condition, but it means the compliance management position is genuinely moving month to month. Any software that claims to have "the labor codes handled" as a static configuration is overselling. Verify current status against the Ministry of Labor and Employment and the relevant state labor department portal before payroll runs, at least while the transition continues.
The wage definition change
The Codes introduce a revised wage definition, commonly discussed as requiring basic pay to constitute at least 50% of total remuneration. This cascades into PF, gratuity, bonus, and overtime calculations, because all of them compute off the wage base.
For a multi-state employer, this interacts with minimum wages, which remain state-set and are typically revised twice yearly. A structure that satisfies the wage definition and clears the minimum wage in Maharashtra may not clear it in a different state with different rates for the same skill category.
Minimum Wages: The Variable Nobody Can Track Manually
Minimum wages vary by state, by skill category (unskilled, semi-skilled, skilled, highly skilled), by industry, and often by geographic zone within a state. Rates are typically revised around April and October.
Multiply that out. Three states, four skill categories, two revisions a year, plus industry variation, and you have a matrix that changes constantly and cannot be maintained by someone remembering to check.
Penalties under the Codes are meaningful, with fines up to ₹50,000 for a first offense in relation to wage payment failures. But the more common damage is quieter: applying the wrong state's rate produces back-pay liability discovered during an audit on every affected employee for every affected month.
What HR Software Actually Needs to Handle
With the landscape established, the requirements become concrete. Evaluate against these specifically rather than against a vendor's claim to be "compliance-ready."
State mapping at the employee level
Every employee record needs a work-location state that drives rule selection, and it must be distinct from the company's registered address and from the employee's postal address if they differ. This is the foundation. A system that assumes one state for the whole company cannot do multi-state compliance, no matter what else it offers.
Test it: change one employee's work location from Delhi to Karnataka and confirm PT starts applying automatically.
Automatic PT slab application by state
The system should apply the correct slab based on the employee's state, deduct nothing in non-PT states, use the right salary definition for that state, and produce challans on that state's calendar.
Minimum wage tracking with revision updates
Ask directly: When a state revises its minimum wage in April, who updates the software, and how quickly? If the answer is "you do," you've bought a spreadsheet with a login.
Shops and Establishments tracking
Registration renewals and working-hour rules by state. This is genuinely thin in most payroll-first platforms, which is worth knowing before you assume it's covered. Leave entitlements get the same jurisdiction-specific treatment and the same gap.
Labour Welfare Fund
Separate from PT, state-specific, with its own rates and frequencies. Frequently missed entirely because it's small.
A compliance calendar with escalation
Filing deadlines differ by state and by statute. The calendar should be jurisdiction-specific with automated escalation, not a single reminder list that assumes uniform dates.
Audit trails
Every action documented. When a labor department asks what you did and when, the answer should be a report.
Where Multi-State Compliance Actually Breaks
The remote employee nobody mapped One person moves to a new state, HR updates their address but not their work-location state, and payroll quietly applies the wrong rules for months.
PT deducted in a non-PT state Usually caused by a system configured for the head office state, applying that config to everyone.
PTEC registered, PTRC forgotten, or vice versa.
Minimum wage revisions were missed because nobody was watching the state gazette in April.
Assuming the labor codes standardized everything, they didn't, and where a state hasn't notified its rules, the old framework still applies.
Discovering a state during an audit. The satellite office or remote hire that never made it into the compliance scope. This is the expensive one, because liability is retrospective.
A Practical Approach
Start with an honest map: list every state where any employee physically works, including remote staff. This single exercise surfaces most of the exposure, and companies are routinely surprised by the answer.
For each state on that list, confirm PT applicability and slabs, LWF applicability, shops and establishments registration status, applicable minimum wages by skill category, and whether that state has notified its labor code rules yet.
Then configure the software to drive from the work-location state and test it by changing one employee's state and watching what happens.
Finally, put a recurring review on the calendar. April and October for minimum wage revisions. Quarterly state code notification status while the transition continues. This is a moving target, and the only reliable defense is a scheduled check rather than a hope that someone notices.
Conclusion
Multi-state compliance in India means running one payroll that simultaneously satisfies central statutes and a different set of state statutes for every state where someone physically works. The labor codes added a central layer; they did not remove the state layer. The single most important configuration in your HR software is work-location state at the employee level, because everything downstream keys off it, and the most common failure is a remote employee whose state nobody mapped. Professional Tax is capped at ₹2,500 a year by Article 276, several major states, including Delhi and Haryana, don't levy it at all; and deducting where you shouldn't is as much a problem as failing to deduct where you should. Minimum wages move twice a year and vary by skill and zone. And state implementation of the labor codes remains uneven, so verify current status per state rather than assuming a single national position. Map your states first. Everything else follows from getting that list right.
