HR Advisory · Compliance

Multi-State Labour Compliance: Why One Policy No Longer Fits All

Labour is a concurrent subject, so each state notifies its own rules under the central codes. A tech company in Karnataka faces different requirements than one in Maharashtra. For pan-India employers, that is the real complexity.

There is a comforting story about India's labour reform — that consolidating 29 laws into four codes makes compliance simpler. For a single-state employer, broadly true. For a company operating across several states, the reality is more complicated, and the complication is structural: labour sits on the Concurrent List of the Constitution, which means both the central government and each state government make rules. The four codes set the national framework; each state notifies its own implementing rules. The result is that the same code can mean meaningfully different obligations in Bengaluru, Mumbai and Kochi.

Where the variation shows up

State-level differences are not trivial edge cases — they hit everyday HR operations:

• Leave entitlements. Earned-leave entitlements differ by state — for example, earned-leave days vary between states under their respective rules, so a uniform national leave policy may under- or over-comply depending on location.
• Shops and Establishments Acts. Day-to-day operations of offices, retail and IT are governed by state-level Shops and Establishments legislation, which sets working hours, holidays and registration requirements differently across states.
• Rule notification timing. States notify their rules on different schedules. Some — Karnataka, Maharashtra, Kerala among them — have notified; others are still in progress. Where final rules are notified, compliance is immediately mandatory; where they are pending, some ambiguity remains.
• Registration and filing. Thresholds and processes for PF, ESI and state registrations can vary in application.

Why "wait for clarity" is the wrong instinct

A tempting response to this complexity is to wait until every state has notified before acting. That is risky. Courts can enforce code provisions even where state rules are pending, and the cost of non-compliance — retrospective PF dues, gratuity shortfalls, inspection penalties — grows with every payroll cycle. The better posture is to comply with the central framework now and layer state-specific rules in as they are notified, rather than treating uncertainty as permission to delay.

Building a compliance system that holds

1. Map your footprint. List every state where you have employees, and treat each as a distinct compliance jurisdiction.
2. Track notifications per state. Maintain a live watch on which states have notified rules and what they specify. This is an ongoing task, not a one-time check.
3. Configure policies by location. Leave, working hours and entitlements may need to vary by state. A single hard-coded national policy will be wrong somewhere.
4. Digitise records. Inspection-ready digital records are now expected, and they are also what lets you demonstrate compliance across multiple jurisdictions efficiently.
5. Centralise oversight, localise application. One team owning the compliance picture, with policies that flex by state, beats either a rigid national policy or fragmented local guesswork.

The bottom line

For multi-state employers, the labour codes did not remove complexity — they relocated it from the central laws to the state rules. The companies that manage this well build a system designed for variation: a clear footprint map, a live notification tracker, location-flexible policies, and digital records. The ones that assume "four codes means one rulebook" will discover the gaps the hard way, one state inspection at a time. This is the operational backbone behind the whole Labour Codes transition.