States delay labour code rules notification: steps

If you run payroll across more than one state, the staggered rollout of the four Labour Codes has turned routine compliance into guesswork. As of 2026, several states still have not notified rules, which means your playbook can change by pin code.

What exactly is delayed and why it matters

The four Labour Codes need both central notifications and state rules for full implementation. According to The Economic Times, only 10 states and union territories have formally adopted some of the Codes, while major states like Karnataka and Tamil Nadu have yet to notify their rules. Result: overlapping central provisions and older state statutes sit side by side, creating daily ambiguity for employers that operate across locations.

Source: Employers face compliance hurdles as states delay notification of Labour Code rules, The Economic Times. Link: https://m.economictimes.com/news/india/employers-face-compliance-hurdles-as-states-delay-notification-of-labour-code-rules/articleshow/134617026.cms

Practically, you must still meet current obligations under state Shops and Establishments Acts, existing minimum wages notifications, and Social Security schemes, while also preparing for the new definitions and formats in the Codes. Getting this sequencing wrong can create back pay exposure, inspection issues, or employee disputes.

Where employers feel the friction

• Wage definition vs CTC structure: The Wage Code definition and allowance cap collide with current state practices. If you rework CTC too early, you may overcommit. If you wait too long, you may face arrears once your state rules take effect.
• Registers and forms: Draft Code formats differ from many state-prescribed registers. Maintaining the wrong set during the interim can lead to procedural non compliance in inspections.
• Standing orders and HR policies: Thresholds and formats are expected to change under the Industrial Relations Code, but existing state rules still govern today. Rolling out a new template too soon can create contradictions.
• Contractors and principal employer duties: Licensing, wage payment timelines, and record keeping may shift under the Codes. Until your state notifies, the current Contract Labour rules apply.
• Floor wage vs state minimum wages: The floor wage concept sits on hold. For now, state minimum wages remain binding, and they continue to update independently.

Operator view: where payroll breaks first

Scenario 1: Your Mumbai and Bengaluru teams share one CTC policy. Maharashtra’s current wage notifications and formats continue to apply. Karnataka has not notified under the Codes yet. If you enforce a new Code-driven wage split across the board, your payslips and registers may mismatch Karnataka’s current requirements.

Scenario 2: A contractor supplies housekeeping staff in two cities. You switch to draft Code registers to be future ready. During an inspection in a state still under legacy rules, the officer expects state formats and timelines. You end up recreating old registers to avoid a notice.

Scenario 3: Finance requests a single pan India overtime policy. Under the Codes, harmonisation will be easier. Until then, overtime rates and caps follow state rules. A unified policy that ignores a stricter state rule creates back pay exposure.

What to do this month: a practical checklist

1. Map your footprint: List each state or union territory where you have employees or contractors. Note whether state rules for each Code are notified, draft, or absent. Keep a one line status per state with the latest gazette link.
2. Adopt a clear fallback: Until your state notifies and the relevant Code is brought into force, continue with existing state laws and notifications. Document this position in your compliance SOP.
3. Model the new wage definition, but do not roll it out prematurely: Rework CTC for different levels using the Wage Code definition as a shadow model so you can switch fast when notified. For structure clarity, see our guide on defining CTC in India.
4. Run dual readiness on records: Maintain current state registers for inspections. In parallel, prepare templates aligned to the Codes. Ensure payslip content meets today’s state requirements. If you distribute digital payslips, review this checklist: salary pay slip online guide.
5. Contractor agreements: Add change in law clauses, require statutory registers access, and align wage payment timelines to the stricter of state or central expectations until clarity arrives.
6. Budget scenarios: Estimate the impact of shifting to the Wage Code definition on leave encashment, overtime, gratuity basis, and variable pay. Keep a contingency line item for retro adjustments in the quarter when your state notifies.
7. Employee communication: Tell employees you are monitoring notifications and will implement changes once effective. Avoid pre announcing changes with dates. Promise and miss is worse than prepare and switch.
8. Track notifications weekly: Subscribe to state labour department updates and watchlists. For context on prior timelines, see this explainer on state notifications.
9. Separate ongoing ESI and PF compliance: The Social Security Code is not fully operational in many states. Continue current EPF and ESIC processes. For a quick refresher on benefits and eligibility, see ESIC benefits and claims.
10. Create an audit pack: Keep appointment letters, wage registers, attendance, overtime records, contractor licenses, and payment proofs together by location. Digital attendance helps. If you need to tighten time tracking, start with this attendance and time tracking guide.

Comparison: two implementation stances

Multi state playbook by footprint size

Single state employer

• Follow that state’s current laws until you see a formal notification and an effective date for the relevant Code.
• Prepare Code aligned policies that can be toggled on location wise.

Two to five states

• Pick your strictest state as the base rule for core wage and leave practices where feasible, without violating local rules elsewhere.
• Maintain state specific annexures for anything that cannot be standardised yet.

Pan India or distributed workforce

• Maintain a central policy with state schedules that override where required.
• Use a compliance calendar by state with renewal dates, inspections, and pending notifications.
• Keep professional tax, labour welfare fund, and shops and establishments registrations tracked location wise. If PT often trips your payroll, this note on professional tax problem areas can help you review edge cases.

FAQs operators ask

Do we need to change the wage definition now

No. Unless your state has notified and the Code is in force for your category, continue with current state requirements. Keep a ready to launch CTC mapping that aligns with the Wage Code definition so you can switch without back pay shocks.

Can I run one payslip format for all locations

Not safely until more states notify. Use a core payslip layout and bolt on state specific fields like local leave accruals or wage components required by that state’s rules. Review your format against your strictest inspection state.

How do we handle contractors during the interim

Insist on wage and register compliance that meets each deployment state’s current laws. Build audit rights into agreements and verify monthly. Pay at or above the highest applicable minimum wage across your locations for similar roles to avoid equal pay disputes.

Documentation that reduces risk

Good paperwork wins during inspections, especially while rules are in transition. Maintain these consistently by state:

• Signed appointment letters and policy acknowledgements
• Attendance and overtime records mapped to wage calculations
• Current state wage registers and Code style draft templates kept separately
• Contractor licenses, wage sheets, ESI and PF challans, and bank proofs
• Leave and holiday calendars with local public holiday notes. If you need a quick reference, see this leave and holiday management guide for 2026.

What stays the same right now

Until your state notifies and the Codes commence for your establishment class, your anchor is the existing state laws and central schemes that were already in force. Keep your statutory components current and documented. If you need a quick refresher on what to watch in payroll, see this overview of key statutory components in 2026.

Bottom line for 2026

Treat the delayed state notifications as a moving target. Keep operations anchored in current state laws, build shadow readiness for the Codes, and maintain pristine documentation. A small weekly discipline on tracking and scenario planning is your cheapest insurance against back pay, notices, and employee disputes.