Growing businesses often expand their workforce beyond their home state. A new client in Pune, a delivery hub in Chennai, a sales team in Gurugram – each of these can look like 

 labour law obligations, and these have less to do with revenue targets and more to do with where your people are working. This is the part of expansion that gets the least a simple business decision. But every new state also brings a fresh set of statutory and attention, until it becomes a problem: a compliance process that works well in one state does not automatically apply to another.  

The Labour Codes backdrop 

This matters more today than it did even a couple of years ago. India’s four new Labour Codes – the Code on Wages, the Industrial Relations Code, the Code on Social Security, and the Occupational Safety, Health and Working Conditions Code, came into force nationally on 21 November 2025, replacing 29 older central labour laws. The Central Government then notified the final Central Rules on 8 May 2026, including the redefined 50% wage floor that now shapes CTC structuring, gratuity, and bonus computation nationwide. But labour sits on the Concurrent List of the Constitution, which means both the Centre and the states can make rules on it, so every state must also notify its own rules under each Code. 

As of August 2026, this state-by-state rule making is still under way. A handful of states have finalised rules across all four Codes; a larger group, including Karnataka, has notified rules for at least one; and several major industrial states are still at the draft stage. Because states are notifying Code by Code rather than all at once, a single company can hold a different compliance position for each Code, depending on where its people sit. 

Wage structuring largely follows the Central Codes directly, since pay, gratuity, and bonus arithmetic come from the Code itself, regardless of state. Registrations, licences, registers, and filings, on the other hand, follow whatever each state has notified – and that’s exactly the piece this article is about.  

In practice, the transition is not a clean switch from the “old law” to the “new law”. The four Labour Codes have been in force since 21 November 2025, and the Central Rules under them were notified on 8-9 May 2026. State rules, however, are still being notified. Until a State notifies its own rules under a Code, the rules, notifications and procedures made under the repealed enactments continue to operate, to the extent they are consistent with the Codes. An establishment may therefore be applying the Code, the Central Rules, any notified State rules and legacy State instruments at the same time. 

Two distinct principles operate within this framework, and they address different questions. The first is one of benefit. The Labour Ministry’s clarificatory FAQs indicate that where a State provision is more favourable to the worker than the Code, the worker is entitled to the benefit of the State provision to that extent. The second is one of jurisdiction. For certain provisions, the applicable Rules specify whether the Central or the State Government’s rules apply, depending on who is the “appropriate Government” as determined under the relevant Code. 

This is the landscape any company thinking about multi-state employment compliance must work with today: the law is more unified at the top but still fragmented in how it’s administered from state to state. 

With that backdrop in mind, here’s a look at the specific compliance risks that come up when a company scales its workforce across more than one state, and how to manage them. 

Where the Risks Show Up 

Shops and Establishments Compliance 

Every Indian state has its own Shops and Establishments law, and the procedures under each one differ, even when the underlying intent is the same. A company that has done everything right in its home state can still run into avoidable risk the moment it opens a second location, simply by assuming the same steps will apply. 

The specific risk areas include: 

• Registration/intimation requirements – timelines, documents, and the authority you file with all vary by state 
• Amendment of registration – a change in address, business activity, or employee count triggers different amendment processes in different states 
• Renewal requirements, wherever applicable – some states need periodic renewal, others don’t 
• Display of notices and certificates – the specific notices required at the workplace differ 
• Maintenance of prescribed registers and records – formats and how long you need to keep them are state-specific 

This is one of the more basic building blocks of state employment law compliance, because the Shops and Establishments certificate is an important establishment-level document and may also serve as supporting proof of the business’s name, address, and activity for certain registrations and processes. Get this one wrong, and it can create knock-on issues for other state labour law compliance requirements and establishment-level registrations. 

State-Specific Leave and Working Hours Requirements 

Employees usually expect the same leave policy no matter which office they sit in, but the law doesn’t work that way. Leave eligibility and entitlement differ from state to state, and applying one national leave policy without checking it against each state’s minimum requirement can quietly put you out of compliance. 

These differences commonly show up in: 

• Earned or privilege leave – the minimum number of days, and how soon a new employee becomes eligible, is set by each state 
• Casual and sick leave – separate entitlements with their own state-specific minimums, often lower than what companies assume 
• Leave accrual and carry-forward – how leave builds up over the year, and how much can carry into the next, is governed state by state 
• Working hours and spread-over – daily and weekly hour limits, and the total span of the workday, come with their own state-specific caps 
• Weekly offs – the mandated day(s) off and rules around compensatory offs follow local rules 
• Holiday requirements, including regional festivals – each state notifies its own list of mandatory paid holidays, so a single pan-India holiday calendar can miss a locally mandated one 

Professional Tax Compliance 

Professional Tax (PT) looks small – the amount is capped by law but it’s entirely state-run, and that’s exactly where it trips companies up. Some states, including Delhi, Uttar Pradesh, Haryana, Rajasthan and Punjab, don’t levy PT at all, while most others do, each with its own slab and filing schedule. A company that simply copies its home-state PT process into a new state rarely gets this right by default. 

Key risks include: 

• Missing employer registration or enrolment in a new state 
• Deducting PT where the state doesn’t levy it, or missing deduction where it does 
• Using the wrong slab for an employee’s salary band 
• Delayed payment and returns against a state’s filing calendar 
• Not adjusting when an employee is based in, or moves to, a different state — PT follows the employee’s work location, not the company’s registered office 

None of this can sit on a single default setting – multi-state payroll compliance means checking PT state by state and re-checking it every time a new state is added.  

Labour Welfare Fund (LWF) Compliance 

Labour Welfare Fund applicability also differs across states – some require it, some don’t, and where it does apply, the contribution structure and period is entirely local. Companies expanding into a new state often carry over their home-state assumption instead of checking fresh, which is exactly the kind of gap multi-state payroll compliance is meant to prevent. 

The risks here are simple but persistent: 

• Missing registration where a state does require LWF 
• Missing periodic contributions once registered 
• Wrong contribution amounts, where a state’s slab or frequency doesn’t match how payroll is currently set up 

It’s a small item in rupee terms, but treating it as an afterthought is how minor shortfalls quietly turn into avoidable liabilities across a growing state footprint.  

Minimum Wages and State Notifications 

Minimum wages in India aren’t one single number. They vary by state, by the type of scheduled employment or category of work, and by skill level within that category. A company hiring across states needs to track a whole matrix of numbers, not just one figure, across every location and role it employs people in.   

On top of this, most states revise these numbers periodically – often twice a year, tied to a Dearness Allowance or cost-of-living adjustment, through their own gazette notifications, on their own schedule and portal, independent of every other state.  

The Wages Code adds one more layer here: a national floor wage, below which no state can set its minimum wage. This is only a baseline, though, not a fixed rate. If a state’s own minimum wage is already higher, that higher rate still applies, following the same rule that whichever option is better for the employee should be used. So, the floor wage doesn’t replace the need to track each state’s rate. It’s simply one more number to check, on top of the matrix a multi-state employer already has to manage. 

This creates its own set of risks: 

• Continuing to pay last year’s rate for weeks after a state’s revision takes effect, simply because no one was tracking that state’s notification 
• Applying a rate to the wrong scheduled employment or skill category, especially after a state updates its classifications 
• Treating minimum wage compliance as a one-time check done at the time of hiring, rather than an ongoing part of multi-state HR compliance 

Left unmanaged, this is where the gap between the notified rate and the rate being paid quietly widens, not because the law is unclear, but because no one was tracking the notification.   

Statutory Registers, Notices and Records 

States prescribe different formats for the registers and notices employers must maintain, and this is one place where standardising everything – usually a sensible HR instinct, can work against you. 

The Codes are meant to ease this over time by introducing common registers and a single, simplified return in place of the separate registers as per the old laws. But that simplification is only as real as each state’s own notified rules: until a state adopts the common format, employers there are still expected to maintain registers in whatever format its pre-Code rules prescribe. 

The risks that show up here include: 

• Using one standard register format for every location, when states each prescribe their own format 
• Missing state-specific notices that are legally required 
• Incomplete employee records that don’t match what a particular state requires 
• Inadequate documentation during inspections, because the registers don’t reflect what the local authority expects to see 

For fast-growing companies, this is often where the gap between “we have a compliance process” and “we have a compliant process in this state” becomes visible. It’s a reminder that employee compliance across states depends as much on paperwork matching local format as it does on the underlying policy being correct.  

Local Registrations and Licences 

Depending on the nature of a company’s operations and its workforce in each state, additional registrations or licences may be required, such as: 

• Shops and Establishments registration 
• Contract Labour registration or licence, where contract or outsourced workers are engaged 
• Factory-related registrations, where manufacturing or factory-classified work is involved 
• Other local registrations and permissions specific to that state or business 

These requirements must be reviewed separately for every new state, as the employee or contractor numbers that trigger them vary by location. Companies expanding quickly often discover they have already crossed the limit only after hiring has begun. 

This is also where the gap between intent and reality is currently widest. The government’s own plan is a single all-India registration: one Labour Identification Number issued through the revamped Shram Suvidha portal, replacing what could be 40 to 60 separate registrations for a company operating across several states.  

But state-level integration with that system is uneven: as of mid-2026, Karnataka has linked around 15 labour-related approvals to the national single-window system, Gujarat and Kerala show only two each, and states including West Bengal and Meghalaya show none. Many states also haven’t yet connected their Shops and Establishments, Professional Tax, or state Factories systems to the new ID at all. 

In practice, this means a company can hold a Labour Identification Number and still need to complete separate state-level registrations on top of it: the single-registration promise doesn’t yet remove the multi-state registration workload, it runs alongside it. For a company tracking employee compliance across states, that means budgeting for both processes until state systems catch up with the national one.  

Multiple Consultants and Lack of Centralised Control 

As companies enter new states, it’s common to bring on local consultants who know that state well. On its own, this makes sense. Without coordination, though, it creates its own problems. 

The issues that tend to come up include: 

• Duplication of work, where two consultants unknowingly cover the same filing 
• Missed compliances, where each consultant assumes the other is handling something 
• Conflicting advice on how a particular rule should be applied 
• Lack of visibility for management, who often only learn about the gaps after something has already gone wrong 

This isn’t really a legal risk on its own, it’s a structural one. It’s what turns individually manageable state labour law compliance requirements into a bigger, organisation-wide multi-state HR compliance problem.  

Penalties, Inspections and Employee Claims 

Non-compliance across states has real consequences, not just theoretical ones. It can lead to: 

• Financial penalties and interest on delayed or missed filings 
• Department notices and inspections, often triggered by an employee complaint or a routine audit 
• Employee claims and disputes, especially around leave, wages, or benefits that weren’t handled the way the applicable state requires 
• Reputational risk, particularly for companies whose growth story depends on being seen as a well-run employer 
• Higher costs to fix past non-compliance, which almost always costs more than getting it right the first time 

This is the part of state labour law compliance that tends to get attention only after it’s already expensive, which is exactly why the risks covered above are worth getting ahead of.  

How Companies Can Manage Multi-State Compliance Effectively 

Multi-state compliance becomes manageable when it is built into the expansion process rather than addressed after a notice, inspection or missed filing. A practical framework should cover seven areas: 

• Map requirements before expansion: Prepare a state-wise compliance matrix covering registrations, payroll, deductions, returns, notices and documentation before hiring begins. 
• Review continuously: Conduct compliance checks before entering a state and at regular intervals as headcount, locations and operations change. 
• Centralise tracking: Maintain one compliance calendar covering due dates, renewals, filings and payments across all locations. 
• Monitor regulatory changes: Track state notifications, revised rates, thresholds, exemptions and procedural changes that may affect payroll or employment practices. 
• Define ownership: Assign clear responsibility for each compliance requirement, both internally and with external consultants, with appropriate review controls. 
• Maintain state-specific records: Keep registers, employee records, payroll documentation and statutory evidence in the format and manner prescribed by each state, so records are ready for inspection. 
• Schedule periodic reviews: Review compliance across all locations on a defined schedule rather than only when entering a new state or responding to an issue. 

A centralised process, combined with state-specific controls and regular reviews, allows companies to manage multi-state payroll compliance as an ongoing business process rather than a series of reactive exercises. 

Conclusion 

Expansion is not just about hiring in a new state. It also requires a state-specific approach to employment law, because practices that work in one location cannot automatically be carried across another. 

This is more important with the Labour Codes now in force nationally, while state rules and implementation continue to progress at different speeds. Companies must also assess Central and State provisions to determine which provides the greater benefit to employees, while the promised single-window registration framework is still evolving across states. 

The practical challenge is therefore not simply knowing the law but identifying where Central and State requirements differ and addressing those differences before they become a compliance issue.