The Four Labour Codes: Employer Implementation Guide 2026

The Four Labour Codes: An Employer's Implementation Guide for 2026

India's employment law landscape has changed more in the last year than in the previous three decades. The four Labour Codes — the Code on Wages, the Code on Social Security, the Industrial Relations Code, and the Occupational Safety, Health and Working Conditions Code — have consolidated a sprawling tangle of central labour statutes into a single, modern framework. For HR managers, founders, and payroll teams, this is not a theoretical policy shift. It changes how you define wages, how you structure salaries, how quickly you must settle exits, how you register your establishment, and how you document nearly everything you do.

This guide is a practical, India-focused implementation playbook for the four Labour Codes in 2026. It is written for small and mid-sized businesses (SMBs) that do not have a 40-person compliance department, and it focuses on what you actually need to do rather than on legislative history. Wherever specific rates, thresholds, or notification dates matter, treat the numbers here as directional and verify the current position with your state labour department or a qualified advisor, because rules under the codes are being operationalised through central and state notifications that continue to evolve.

What the four Labour Codes actually are

The four Labour Codes replace and consolidate a large number of older central labour laws. Rather than reading dozens of separate acts, employers now work primarily within four instruments, each covering a broad domain of the employment relationship.

The Code on Wages brings together the rules on minimum wages, payment of wages, bonus, and equal remuneration. Its single most consequential feature is a unified statutory definition of "wages" that applies across all four codes — a definition that directly reshapes salary structures.

The Code on Social Security consolidates provident fund, employees' state insurance, gratuity, maternity benefit, and related welfare schemes. It also creates a framework for extending social security to gig and platform workers, a genuinely new direction for Indian labour law.

The Industrial Relations Code governs trade unions, standing orders, conditions of service, and the procedures for layoff, retrenchment, and closure. It raises certain thresholds and formalises grievance and dispute mechanisms.

The Occupational Safety, Health and Working Conditions Code (the OSH Code) consolidates rules on working conditions, safety, welfare facilities, working hours, leave, and the licensing of establishments, contractors, and specific categories of workers.

Understanding which code governs which question is the first practical skill. When you ask "how should I structure salary?" you are in the Code on Wages. When you ask "how fast must I settle a departing employee?" you are looking at the wage payment provisions read with social security dues. When you ask "how many hours can someone work and what leave must I grant?" you are in the OSH Code. When you ask "what process must I follow before retrenching workers?" you are in the Industrial Relations Code.

Why 2026 is the year this becomes real

For several years the codes existed on paper but were not fully in force, because implementation depends on both central rules and state-level rules being notified. The practical reality for 2026 is that the codes have moved from "coming soon" to "operational," and the states are progressively aligning their own rules. That means the grace period many employers relied on is closing.

The risk profile has shifted accordingly. Where you might once have treated code readiness as a future project, non-compliance now carries live exposure: inspection findings, penalties, employee disputes, and — increasingly — reputational cost when candidates and current staff notice that payslips, PF contributions, or settlements do not match the new expectations. The employers who will navigate 2026 comfortably are the ones who treat the codes as a current operating requirement, not a planning exercise.

The wage definition: the change that touches everything

If you read only one section of this guide, read this one. The unified definition of wages under the Code on Wages is the pivot around which almost every payroll consequence turns.

Under the codes, "wages" is defined to include basic pay, dearness allowance, and retaining allowance, while specifically excluding a list of components such as house rent allowance, conveyance, certain bonuses, overtime, and employer contributions to provident and pension funds. Crucially, the definition contains a balancing rule: the excluded components, taken together, cannot exceed a specified proportion of total remuneration. When they do, the excess is added back and treated as wages.

The practical effect is what employers now call the 50% rule: as a working principle, the wage portion of pay (broadly basic plus dearness allowance) should be at least half of total remuneration. If your salary structures have historically kept basic pay low — say 30% to 35% of CTC — to reduce provident fund and gratuity liabilities, those structures no longer hold. The allowances you piled on top will be partly reclassified as wages for the purpose of calculating statutory dues.

This matters because so many downstream calculations are pegged to "wages":

• Provident fund contributions are calculated on wages, so a higher wage base raises both employer and employee PF outflow.
• Gratuity accrues on wages, so long-term gratuity liability increases.
• Leave encashment and several statutory settlements are computed on wages.
• Overtime, bonus eligibility and calculation, and maternity benefit all reference wage figures.

The net result for most employers is a 5% to 15% increase in statutory cost for employees whose structures were previously basic-light. You cannot make this disappear, but you can plan for it, phase it, and communicate it — which we cover in the salary restructuring section below.

A phased implementation roadmap

Trying to become "fully compliant" in a single weekend is how mistakes happen. A phased roadmap lets you sequence the work, protect cash flow, and keep employees informed.

Phase 1: Diagnose (weeks 1–2)

Start with an honest audit of where you stand.

Pull a full list of current salary structures and calculate, for each employee, what proportion of total remuneration currently counts as wages under the new definition. Flag everyone below the 50% threshold. Simultaneously, list every establishment registration, licence, and return your business currently holds, and map each to its equivalent under the codes. Finally, gather your existing policies — leave, working hours, overtime, grievance, exit — and note where each will need revision.

The deliverable from this phase is a gap register: a simple spreadsheet listing every gap, its owner, and its severity. This document becomes your project plan.

Phase 2: Redesign structures and policies (weeks 3–6)

With gaps identified, redesign. Rework salary structures so that the wage portion meets the threshold, modelling the cost impact before you commit. Update your leave policy, working-hours policy, overtime rules, and grievance mechanism to reflect the codes. Draft or refresh standing orders or their equivalent if your headcount brings you within scope.

This is also the phase to fix your documentation architecture — the registers, records, and returns the codes expect you to maintain. Building these as digital, always-current records rather than year-end scrambles is the single best investment you can make.

Phase 3: Communicate and transition (weeks 7–10)

Employees will notice changes to their payslips, particularly if net take-home shifts because of higher PF deductions. Communicate before the change lands, not after. Explain what is changing, why, and what it means for each person's monthly take-home and long-term benefits. Provide a worked example. Offer a channel for questions.

Transition payroll in a controlled cutover, ideally at the start of a financial period, and run a parallel calculation for at least one cycle so you can catch discrepancies before they hit real bank accounts.

Phase 4: Operate and monitor (ongoing)

Compliance is not a project you finish; it is a state you maintain. Build a recurring compliance calendar, assign owners, and review it monthly. Keep an eye on new state notifications, because minimum wages and several procedural rules are set at the state level and change frequently.

Salary restructuring under the codes

Restructuring salaries to satisfy the wage definition is the most visible and most sensitive part of implementation. Handle it well and employees will barely notice; handle it poorly and you will face a wave of "why is my take-home lower?" tickets.

The core move is to increase the basic (wage) portion so that basic plus dearness allowance reaches at least half of total remuneration, while rebalancing the remaining allowances. There are a few principles worth holding onto.

First, model before you move. For each affected employee, calculate the new PF and gratuity liability under the redesigned structure and quantify both the employer cost increase and the change to employee take-home. You need these numbers to make decisions and to answer questions.

Second, decide who absorbs the cost. When the wage base rises, employee PF deductions rise too, which reduces monthly take-home even though the employee's long-term retirement corpus grows. Some employers choose to protect take-home by grossing up; others let take-home adjust and lean on communication. There is no universally correct answer — it depends on your compensation philosophy and budget — but you should decide deliberately rather than by accident.

Third, phase where you can. If the cost increase is significant, consider aligning the transition with your annual increment cycle, so that raises partly cushion the take-home impact. This is a legitimate way to smooth the change, provided you are not using it to delay compliance indefinitely.

Fourth, respect the floor. Whatever you do, the redesigned wage portion must genuinely meet the statutory threshold. Cosmetic relabelling that keeps the real wage base low invites reclassification and penalties.

Social security: PF, ESI, gratuity, and beyond

The Code on Social Security consolidates the major welfare schemes, and while the underlying mechanics of provident fund and employees' state insurance remain broadly familiar, the wage base change flows straight through them.

For provident fund, the higher wage base means higher contributions. Make sure your payroll engine calculates PF on the redefined wage figure and that your monthly electronic challan-cum-return reflects it accurately.

For employees' state insurance, coverage continues to hinge on wage thresholds and applicable geographies; confirm which of your employees fall within scope and that contributions are remitted on the correct base.

For gratuity, the code retains the broad eligibility architecture while the wage change increases accrual. If you carry gratuity as a funded liability, revisit your funding assumptions with your actuary or insurer.

The forward-looking element of the Social Security Code is its framework for gig and platform workers. If your business engages workers through aggregator or platform models, watch this space closely: the direction of travel is toward extending social security contributions and benefits to categories of workers who were previously outside the net.

Working hours, leave, and the OSH Code

The OSH Code consolidates the rules that govern the daily texture of work — hours, overtime, weekly rest, leave, and welfare facilities.

Working-hour and overtime provisions continue to cap normal hours and require premium pay for overtime, calculated on the wage base. If your business runs shifts, the interaction between shift design, overtime, and the wage definition deserves specific attention, because overtime is computed on wages and the wage base has risen.

Leave entitlements, including earned leave accrual and carry-forward, are set within the OSH framework and applicable state rules. Review your leave policy against current entitlement rules, and make sure your leave management system reflects accrual, encashment, and carry-forward correctly.

The OSH Code also formalises expectations around welfare facilities, safety, and — importantly for administrative teams — licensing and registration of establishments and contractors. If you engage contract labour, the tightening scrutiny of contractor and third-party staffing arrangements means you should verify that your contractors hold valid licences and that principal-employer obligations are being met.

The 48-hour exit settlement rule

One operational change deserves its own spotlight because it compresses a process many employers run slowly: the expectation that full and final settlement of wages is completed within two days of an employee leaving — whether through resignation, dismissal, removal, or retrenchment.

Historically, many organisations took weeks to close a final settlement, waiting for asset returns, manager sign-offs, and the next payroll cycle. Under the codes' faster settlement expectation, that timeline is untenable. To settle within roughly 48 hours, you need to be able to compute — in near real time — the departing employee's earned but unpaid salary, leave encashment, notice-period adjustments, statutory dues, and any recoveries.

This is difficult to do manually and straightforward to do with a payroll system that maintains a live view of each employee's leave balance, salary, and dues. The practical readiness test is simple: if an employee resigned this afternoon, could your team produce an accurate, defensible final settlement figure by the day after tomorrow? If the honest answer is no, this is a priority fix.

Registers, records, and returns

The codes lean heavily on documentation. Across the four instruments, employers are expected to maintain registers of employees, wages, leave, and related matters, to issue wage slips, and to file periodic returns. The codes also push toward electronic maintenance of records, which is good news: digital registers are easier to keep current, easier to produce during an inspection, and far less prone to the gaps that manual year-end reconstruction creates.

Practically, aim to maintain the following as living digital records: an employee master with statutory identifiers; a wage register capturing the wage components and totals used for statutory calculations; a leave register with accruals, availment, and balances; and an attendance record that supports overtime and wage calculations. When an inspector asks for records, the difference between a well-run establishment and a stressed one is whether these can be exported in minutes.

A practical compliance checklist for 2026

Use this as a working checklist. Adapt it to your headcount, state, and industry, and confirm specifics with your advisor.

• Audit every salary structure and identify employees below the wage threshold.
• Redesign structures so the wage portion meets the statutory floor, modelling cost and take-home impact first.
• Recompute PF, gratuity, and other wage-linked liabilities on the new base.
• Map every existing registration, licence, and return to its equivalent under the codes and re-register where required.
• Update leave, working-hours, overtime, and grievance policies to align with the codes and current state rules.
• Verify contractor licences and principal-employer obligations for any contract labour.
• Build the capability to complete full and final settlements within roughly 48 hours of exit.
• Move registers, wage slips, and returns to always-current digital records.
• Communicate payslip and take-home changes to employees before they land.
• Establish a monthly compliance calendar with named owners and track state notifications.

Common mistakes to avoid

The first mistake is treating the wage change as cosmetic — relabelling components without genuinely raising the wage base. Reclassification rules exist precisely to catch this, and the exposure is not worth the saved rupees.

The second is surprising employees. Payslip changes that reduce take-home without explanation generate mistrust and a flood of tickets. Over-communicate.

The third is ignoring state variation. Minimum wages and several procedural requirements are state-specific and change often. A structure that is compliant in one state may not be in another, and multi-state employers need to track each jurisdiction.

The fourth is leaving settlements slow. The faster exit-settlement expectation is easy to overlook until an inspection or a disgruntled ex-employee makes it expensive.

The fifth is doing it once and forgetting. Compliance under the codes is a maintained state, not a completed task.

Frequently asked questions

Do the four Labour Codes apply to small businesses and startups? Applicability of specific provisions often depends on headcount and establishment type, and some obligations kick in only above certain thresholds. But the wage definition and its salary-structure consequences are broad, so even small employers should assume the core payroll changes apply to them and verify the finer thresholds for their situation.

Will the codes reduce my employees' take-home pay? For employees whose structures were previously basic-light, raising the wage base increases provident fund deductions, which can reduce monthly take-home even as long-term retirement savings grow. Whether take-home actually falls depends on how you choose to restructure and whether you gross up. Model it per employee before deciding.

What is the 50% rule in simple terms? As a working principle, the wage portion of pay — broadly basic plus dearness allowance — should be at least half of total remuneration. If excluded allowances collectively exceed the permitted proportion, the excess is treated as wages for statutory calculations.

How urgently do I need to complete full and final settlements now? Plan for a fast turnaround — on the order of two days from the exit — for the wage settlement. Build the capability to compute final dues quickly rather than relying on the next monthly cycle.

Do I need to re-register my establishment? Possibly. Registrations and licences under the older laws map to equivalents under the codes, and in some cases re-registration or migration is required. Map each of your current registrations to its code equivalent and act on any that need updating.

Are gig and platform workers covered? The Social Security Code introduces a framework for extending social security to gig and platform workers. If your business uses these models, expect contribution and benefit obligations to expand, and monitor notifications closely.

How often do the rules change? Central rules set the framework, but many operational details — especially minimum wages — are notified at the state level and change frequently. Build monitoring into your monthly compliance routine rather than treating the codes as a fixed target.

Can software really handle all of this? A capable HR and payroll platform handles the mechanical parts well: calculating wages and statutory dues on the correct base, maintaining digital registers, generating compliant payslips, and producing fast, accurate full and final settlements. It does not replace judgement on structure design or legal interpretation, but it removes the manual gaps where compliance usually breaks.

A worked salary restructuring example

Numbers make the wage definition concrete, so here is an illustrative example. The figures below are purely illustrative and rounded for clarity — they are not statutory rates, and you should run your own model with current rates for your state and situation.

Imagine an employee on a total fixed pay of ₹10,00,000 per year, structured the old way to keep the wage base low. Basic might sit at ₹3,20,000 (32%), with the balance spread across house rent allowance, special allowance, conveyance, and a few other heads. Under this structure, provident fund and gratuity accrue on a small base, which is precisely why employers favoured it.

Now apply the wage definition. The excluded allowances collectively exceed the permitted share of total remuneration, so the excess is added back into wages until the wage portion reaches roughly half of total pay — about ₹5,00,000. Provident fund and gratuity now accrue on that larger figure. The employee's retirement corpus grows faster, and the employer's statutory cost rises. Monthly take-home may dip slightly because the employee's own provident fund contribution is calculated on the larger base.

The lesson is not the exact rupee figures; it is the shape of the change. Every basic-light structure moves in the same direction: a bigger wage base, higher statutory contributions, a stronger long-term benefit for the employee, and a modest near-term take-home adjustment that is best handled with communication and, where budget allows, a cushioning increment.

The Industrial Relations Code in practice

The Industrial Relations Code is the one most SMBs think least about, because its heaviest provisions historically applied to larger establishments. That instinct is only partly right in 2026.

Two areas deserve attention even for growing companies. The first is standing orders — the formal statement of conditions of service that establishments above a headcount threshold must adopt. If your headcount is climbing, check whether you cross the threshold, and if you do, adopt model standing orders or your own certified version rather than leaving conditions of service informal.

The second is the process discipline around workforce reductions. The code sets out the procedure for layoff, retrenchment, and closure, including notice, compensation, and in some cases prior permission above certain size thresholds. Even if you are below the permission threshold, the notice and compensation architecture matters, and following a clean, documented process protects you if a separation is later disputed. The code also strengthens grievance-redressal expectations, so a functioning internal grievance mechanism is no longer optional hygiene — it is part of your compliance posture.

Fixed-term employment is also formalised across the framework, giving employers a legitimate route to time-bound engagements with pro-rated statutory benefits, without resorting to disguised contract arrangements that attract scrutiny.

Inspections under the facilitator model

The codes reframe the role of the inspector as an inspector-cum-facilitator, with an emphasis on web-based and randomised inspections and, in principle, a more advisory posture. Do not misread this as leniency. A facilitator model rewards employers who can produce clean, current digital records on demand and penalises those who cannot. The single best preparation for an inspection under this model is to keep your registers, wage slips, contributions, and returns continuously up to date and exportable — which, again, is where digital record-keeping earns its cost many times over.

Industry and headcount nuances

The codes apply across the economy, but the practical burden varies. A software services firm with salaried staff will feel the wage definition and settlement-speed changes most. A manufacturing or logistics business will additionally feel the OSH Code's working-condition, safety, and contractor-licensing provisions. A platform or aggregator business must watch the gig-worker social-security framework closely. And a rapidly hiring startup should monitor headcount thresholds, because obligations around standing orders and certain procedures switch on as you grow. Map your specific profile — sector, states of operation, headcount trajectory, and use of contract labour — and weight your implementation effort accordingly.

Building your 90-day project plan

If you want a single organising frame, run the transition as a 90-day project with a named owner and weekly checkpoints. Spend the first fortnight diagnosing and building your gap register. Use the next month to redesign structures and policies and to model cost impact. Use the following few weeks to communicate to employees and run a parallel payroll cycle. Reserve the final stretch for cutover, verification, and standing up your ongoing compliance calendar. Ninety days is enough to do this properly without heroics, provided the work starts now and someone genuinely owns it. What happens if an inspection finds gaps? Under the facilitator-oriented model, minor gaps may first draw guidance, but genuine non-compliance — wrong wage bases, missing contributions, absent records — can attract penalties and orders to remedy. The practical defence is clean, current, exportable digital records and correct statutory calculations, so that an inspection confirms good practice rather than uncovering problems.

Should I wait for more clarity before restructuring? The wage definition and its salary consequences are already operative, so waiting mainly increases your accumulated exposure. Where genuine ambiguity exists — often in state-specific procedural detail — track notifications and take advice, but do not let uncertainty at the edges delay the core structural work that is already clear.

Handling multi-state operations

If you operate across states, the codes add a coordination challenge rather than removing one. Minimum wages, professional-tax-style levies where applicable, leave rules, and several procedural requirements are set or adjusted at the state level, and the states are notifying their own rules on their own timelines. A salary structure that clears the wage floor everywhere still has to sit above the correct state minimum wage in each location, and your leave and working-hour policies may need state-specific variants.

The workable approach is a common national framework — one salary architecture, one set of core policies — with a thin layer of state overrides for minimum wages and any local procedural differences. Maintain a simple state matrix that records, for each state you operate in, the current minimum wage, the applicable local levies, and any notified rule differences, and review it every quarter. Trying to run each state as a wholly separate regime is unnecessary; ignoring state variation entirely is risky. The matrix is the middle path.

Turning compliance into an advantage

It is easy to frame the codes purely as cost and risk, but there is an upside worth naming. Employees increasingly value a larger, correctly-funded retirement corpus, transparent payslips, and fast, clean exits. Candidates notice when an employer's statutory hygiene is visibly in order. Getting the codes right is therefore not only about avoiding penalties; it is a signal of operational maturity that helps you attract and retain people. Employers who communicate the changes well — explaining that a slightly lower take-home today buys a materially larger provident fund tomorrow — often find that the transition builds trust rather than eroding it.

Conclusion

The four Labour Codes are the biggest shift in Indian employment law in a generation, and 2026 is the year they become an operating reality rather than a planning slide. The good news is that the work is finite and sequenceable: audit your structures, redesign to meet the wage definition, recompute statutory liabilities, tighten your records, speed up your settlements, and communicate honestly with your people. Employers who move deliberately will find the transition manageable; those who wait will find it expensive.

If you would rather not stitch this together across spreadsheets and manual registers, this is exactly the kind of change a modern HR and payroll platform is built to absorb. CozyHR helps Indian SMBs restructure salaries against the new wage definition, calculate statutory dues on the correct base, maintain always-current digital registers, and produce fast, accurate full and final settlements — so the codes become a background process rather than a monthly fire drill. If you are planning your 2026 compliance work, it is worth seeing how much of this a good platform can carry for you.