How India’s New Labour Codes Are Changing Payroll and HRMS Compliance in 2026

Most HR teams know the four Labour Codes — the Code on Wages, Industrial Relations Code, Occupational Safety, Health and Working Conditions Code, and Code on Social Security.

But the practical challenge in 2026 is no longer simply understanding what the Codes say.

The bigger question is:

What do the Labour Codes actually change inside payroll, salary structures, statutory calculations and HRMS configuration?

For organisations managing payroll across multiple employees, entities or locations, the impact can be significant. The revised definition of “wages”, the 50% add-back mechanism, changes affecting social security and gratuity, and updated compliance requirements all need to be correctly reflected in payroll processes and HRMS systems.

The four Labour Codes came into force from 21 November 2025, making 2026 an important year for organisations to review their payroll and HRMS processes against the new framework. The Ministry of Labour and Employment has also issued FAQs and additional clarifications on the definition of wages and related calculations.

Quick Answer: What Do the Labour Codes Change for Payroll?

India’s Labour Codes introduce a common definition of “wages” across the four Codes.

Broadly, wages include basic pay, dearness allowance and retaining allowance, subject to specified exclusions. Where the relevant excluded components exceed 50% of remuneration, the excess amount is added back to wages for the purposes covered by the applicable provisions.

This means the 50% provision should not simply be understood as a rule saying that every employee’s Basic Pay must be 50% of CTC.

For HR teams, the practical impact is more important than the terminology.

Salary components need to be mapped correctly, the applicable wage base needs to be determined, and payroll systems need to apply the relevant statutory calculations consistently.

That can affect areas such as PF, ESI, gratuity, payslips, salary restructuring, payroll adjustments and full & final settlement, depending on the employee, compensation structure and applicable statutory provisions.

What Are the Four Labour Codes in India?

India consolidated several existing labour laws into four Labour Codes:

The four Codes were brought into force on 21 November 2025, replacing and rationalising provisions from 29 existing Central labour laws.

For payroll and HRMS teams, the Code on Wages and Code on Social Security are particularly important because they directly affect compensation mapping and statutory benefits.

The Ministry has also clarified that the definition of wages is relevant across the four Codes, while individual statutory provisions can have their own applicability, conditions and calculation requirements.

This is why labour codes 2026 in India should be viewed as both a legal-compliance requirement and a payroll/HRMS configuration exercise.

What Actually Changes in the Definition of “Wages”?

One of the most important changes for payroll teams is the revised definition of wages.

Under the Labour Codes, wages generally include:

• Basic pay
• Dearness allowance
• Retaining allowance, where applicable

The definition also contains specified exclusions.

However, where the relevant excluded allowances and benefits exceed 50% of remuneration, the amount exceeding that threshold is added back to wages. The Ministry's FAQ also clarifies that certain components, such as performance-based incentives, ESOPs, variable components and reimbursement-based payments, are not part of wages under the stated treatment.

This is an important distinction.

The rule is often simplified as:

“Basic Pay must be at least 50% of salary.”

That is not the most accurate way to explain the statutory mechanism.

The actual question is:

Do the relevant excluded components exceed the permitted 50% threshold?

If they do, the excess is added back to wages.

A Simple Example

The Ministry of Labour and Employment has provided an illustration using monthly remuneration of ₹76,000.

In this example, the relevant allowances exceed 50% of remuneration by ₹2,000.

That ₹2,000 is therefore added back to the wage base.

The important takeaway for HR teams is that the calculation depends on the actual salary components and the exclusions covered by the applicable provision.

It is not simply a matter of checking whether Basic Pay equals 50% of CTC.

Does Overtime Count in the 50% Calculation?

This is another area where payroll teams need to pay attention to the latest clarification.

The Ministry’s additional FAQ issued in March 2026 clarifies that overtime allowance forms part of the 50% wage calculation. It also provides clarification on the treatment of statutory components when determining remuneration for this purpose.

For payroll teams, this means overtime should not simply be treated as an unrelated payroll component when performing the calculation.

The relevant components need to be mapped according to the applicable statutory definition and the latest government clarification.

This is one reason why payroll software should not rely on a single hard-coded “50% Basic” rule.

The system needs to understand the underlying salary components and apply the appropriate statutory logic.

Why This Creates a Payroll Compliance Gap, Not Just a Paperwork Update

The risk is not that HR teams do not know the Labour Codes exist.

The bigger risk is that payroll systems often calculate PF, ESI, gratuity and other statutory components using salary-component mappings configured years ago.

If the underlying compensation structure and payroll configuration have not been reviewed against the applicable Labour Code provisions, the system may continue applying outdated calculation logic.

That creates several practical questions:

• Which salary components should form part of the wage calculation?
• Which components are excluded?
• Does the 50% add-back apply to the employee’s compensation structure?
• Has the applicable PF logic been reviewed?
• Has ESI applicability and wage mapping been reviewed?
• Has gratuity been recalculated using the applicable wage definition?
• Are payslips showing the correct components?
• Can the payroll system handle arrears or adjustments where required?
• Can different entities or locations be configured correctly?
• Can the company maintain an audit trail of payroll rule changes?

These are HRMS questions, not just legal questions.

An HRMS therefore needs to do more than store employee salary components.

It needs to support a statutory calculation framework that can apply the relevant rules consistently and maintain appropriate configuration as requirements change.

How Labour Codes 2026 Affect PF, ESI and Gratuity

The impact will depend on the employee’s compensation structure and the specific statutory provision being applied.

The revised wage definition should therefore be considered together with the applicable rules governing each statutory benefit.

PF Contributions

The revised definition of wages can affect the wage base relevant to provident-fund calculations where the applicable provisions and contribution rules require it.

However, HR teams should not assume that every employee will automatically have a higher PF contribution simply because their Basic Pay is below 50% of CTC.

The wage definition and the applicable PF contribution provisions need to be reviewed together.

For payroll teams, the practical questions are:

• Which components are currently mapped to the PF base?
• Which components are treated as wages under the applicable provisions?
• Does the existing configuration need to be changed?
• How will the system handle salary restructuring or arrears?
• Can payroll teams compare the previous and revised calculation?

The important point is that unchanged CTC does not necessarily mean unchanged statutory calculations.

ESI

The revised wage definition is also relevant to ESIC.

ESIC issued a communication stating that the new definition of wages under Section 2(88) of the Code on Social Security was implemented from 21 November 2025 and advised establishments to ensure compliance with the revised definition.

For employers, this means ESI should be reviewed from two perspectives:

First, the wage base used for the calculation.

Second, whether the revised definition affects employee coverage.

Payroll systems therefore need to identify employees who may be affected instead of relying entirely on historical ESI mappings.

Gratuity

The wage definition also matters for gratuity calculations.

The Ministry has stated that gratuity under the Code on Social Security applies from 21 November 2025.

For employers, this means the wage components used for gratuity calculations need to be reviewed and correctly mapped in payroll and HRMS systems.

The review should also consider:

• Employee eligibility
• Length of service
• Fixed-term employment, where applicable
• Wage components used for calculation
• Effective dates
• Full & final settlement
• Payroll adjustments

Do Employers Need to Restructure Salaries?

This is one of the most common questions HR teams have.

The answer should not be reduced to:

“Make Basic Pay 50% of CTC.”

Salary restructuring depends on the employee’s compensation structure, the components involved, and the applicable statutory provisions.

The first step should therefore be to audit the existing salary structure.

For example, an employer may have a compensation structure containing:

• Basic Pay
• HRA
• Special Allowance
• Conveyance or other allowances
• Bonus
• Employer contributions
• Other benefits

The HR team needs to determine how these components are treated under the applicable wage definition and whether the relevant exclusions exceed the 50% threshold.

Only after this exercise should the organisation decide whether salary restructuring is required.

What HR Teams Need to Verify Before Payroll Rollout

A successful Labour Code compliance exercise starts with reviewing the existing payroll structure.

1. Audit the Current Salary Structure

Review the composition of remuneration across employee bands.

Do not look only at Basic Pay.

Map:

• Basic Pay
• Dearness Allowance
• Retaining Allowance, where applicable
• HRA
• Special Allowance
• Other allowances
• Bonus
• Overtime
• Employer statutory contributions
• Gratuity
• Other relevant components

The purpose is to identify which components fall within the wage definition and how the 50% mechanism applies.

2. Review PF and ESI Configuration

Ask your payroll or HRMS team:

• Which components currently form the PF base?
• Which components form the ESI base?
• Has the revised wage definition been mapped?
• Are potentially affected employees being identified?
• Can the system apply the applicable rule without manual intervention?
• Can payroll teams compare the previous and revised calculations?

3. Review Gratuity Configuration

Verify:

• Wage components used for gratuity
• Employee eligibility
• Service-period calculation
• Effective date
• Treatment of fixed-term employees, where applicable
• Full & final settlement calculations

4. Review Payslips and Payroll Documents

Payroll components should be clearly identified and consistently mapped.

A component should not simply be renamed to appear compliant.

The underlying payroll calculation needs to support the applicable statutory definition.

5. Review State and Entity Requirements

Organisations operating across multiple locations should avoid assuming that one configuration automatically covers every compliance requirement.

The HRMS should be capable of maintaining applicable rules by entity, location and effective date where required.

What Should an HRMS Do Under Labour Codes 2026?

This is where payroll software becomes particularly important.

A modern HRMS should help HR teams move from manual compliance checks to controlled, auditable payroll processes.

This is the difference between an HRMS that simply processes payroll and one that supports Labour Code compliance in practice.

Why Effective-Dated Statutory Rules Matter

One of the easiest areas to overlook is when a rule becomes applicable.

Payroll systems should not simply overwrite an old rule with a new one.

They should be able to identify:

• Which rule applied before the effective date
• Which rule applies from the new effective date
• Which employees are affected
• Whether previous payroll needs adjustment
• How the difference should be handled
• Which payroll records were generated under each rule

This becomes particularly important when a company has multiple payroll entities, locations or employee categories.

A good HRMS should therefore maintain statutory rules with clear effective dates instead of depending on manual spreadsheets and one-time payroll changes.

12 Questions to Ask Your HRMS Provider

Before accepting a “Labour Code compliant” claim, HR teams should ask the HRMS provider to demonstrate how the system actually handles the requirements.

Ask:

1. How is the revised definition of wages configured?
2. How does the system calculate the 50% add-back?
3. Which salary components are included in the calculation?
4. How are PF calculations handled under the applicable provisions?
5. How does the system determine ESI applicability and calculation?
6. How is gratuity calculated?
7. Can statutory rules be configured with effective dates?
8. Can the system process arrears and payroll adjustments?
9. Can different entities and locations have different applicable configurations?
10. Can the system generate payroll variance reports?
11. How are payslips and statutory reports updated?
12. How are future statutory changes delivered and implemented?

A useful test is to ask the vendor to demonstrate the calculation using an actual sample employee salary structure.

This allows HR and finance teams to see whether the system is applying the statutory logic correctly rather than simply displaying a “compliance” label.

Real Scenario: A Mid-Size Company Auditing Its Pay Structure

Consider a company with 200 employees where the compensation structure historically contains a relatively low Basic Pay component and a larger share of allowances.

Under the previous payroll configuration, the company may have calculated statutory components using its existing salary-component mapping.

Under the Labour Code framework, however, the HR team needs to examine whether the relevant excluded components exceed the applicable 50% threshold and whether any excess needs to be added back to wages.

This creates three separate tasks.

First, HR needs to audit the existing salary structure.

Second, payroll needs to determine the applicable statutory wage base.

Third, the HRMS needs to apply the relevant calculation consistently in future payroll runs.

Doing the first two steps manually may work for a one-time review.

But it does not solve the ongoing problem.

If the payroll system continues using outdated configuration in subsequent months, the organisation can recreate the same compliance issue every payroll cycle.

That is where payroll automation becomes valuable.

How VeSure HRMS Applies This in Practice

VeSure HRMS is designed to bring statutory payroll calculations into the same HRMS workflow rather than requiring HR teams to manually recalculate every affected employee whenever a statutory rule changes.

Where applicable Labour Code provisions require a different wage-base calculation, the payroll configuration can be aligned with the applicable rule and the resulting statutory calculations can be processed consistently.

For HR teams, the practical benefits include:

• Structured salary-component management
• Automated payroll calculations
• Statutory payroll processing
• Payslip generation
• Employee-level payroll records
• Multi-branch and multi-state employee management
• Centralised HR and payroll workflows
• Payroll reporting and reconciliation

The important point is that automation does not replace the initial HR review.

The compensation structure still needs to be mapped correctly.

Once that foundation is in place, an HRMS can reduce the ongoing manual effort involved in applying payroll rules consistently.

How to Get Started with Labour Code Compliance in 2026

A practical implementation approach can be kept simple.

Step 1: Audit Your Salary Structure

Identify employees and salary bands where allowances make up a significant portion of remuneration.

Step 2: Map Every Payroll Component

Document which components are included, excluded or potentially subject to add-back under the applicable wage definition.

Step 3: Validate PF, ESI and Gratuity

Compare your existing payroll calculations with the applicable Labour Code provisions and related statutory requirements.

Step 4: Test Your HRMS

Ask your HRMS provider to demonstrate how the system handles:

• Wage calculations
• 50% add-back
• PF
• ESI
• Gratuity
• Arrears
• Effective dates
• Multi-state payroll
• Payslips
• Full & final settlement

Step 5: Run a Parallel Payroll

Run sample payroll calculations using the existing and revised configurations.

Compare the results employee by employee before moving completely to the updated configuration.

Step 6: Maintain an Audit Trail

Keep documentation showing:

• What was changed
• Why it was changed
• The applicable effective date
• Which employees were affected
• How payroll was validated
• How any differences were reconciled

This makes future audits and internal reviews much easier.

Labour Codes 2026: Payroll Compliance Checklist

Before relying on your payroll system, HR and finance teams should verify the following:

• Salary components have been mapped against the revised wage definition.
• The 50% allowance/add-back calculation has been tested.
• Overtime treatment has been reviewed.
• PF configuration has been reviewed.
• ESI applicability and wage mapping have been reviewed.
• Gratuity calculations have been reviewed.
• Fixed-term employee treatment has been checked where applicable.
• Payslip components have been reviewed.
• Payroll documents have been checked.
• Employee records and appointment documentation have been reviewed.
• Full & final settlement calculations have been tested.
• State/entity-specific requirements have been identified.
• Effective dates are supported by the HRMS.
• Payroll variance reports are available.
• Parallel payroll testing has been completed.
• Historical payroll impact has been reconciled where required.

Frequently Asked Questions

What is the new definition of “wages” under the Labour Codes?

The Labour Codes use a common definition of wages based primarily on basic pay, dearness allowance and retaining allowance, subject to specified exclusions.

Where the relevant excluded allowances and benefits exceed 50% of remuneration, the excess amount is added back to wages for the purposes covered by the applicable provisions.

Is Basic Pay required to be exactly 50% of CTC?

Not necessarily.

The 50% provision is an add-back mechanism, not simply a rule saying that every employee’s Basic Pay must equal 50% of CTC.

The actual calculation depends on the remuneration and the components covered by the applicable statutory definition.

Does overtime count in the 50% calculation?

Yes, the Ministry’s March 2026 additional FAQ clarifies that overtime allowance forms part of the 50% wage calculation.

Payroll teams should therefore include the applicable treatment of overtime when mapping remuneration for the 50% provision rather than treating overtime as automatically outside the calculation.

How do Labour Codes affect PF contributions?

The revised wage definition can affect the wage base relevant to PF calculations where the applicable provisions require it.

However, employers should review the wage definition together with the applicable PF contribution rules rather than assuming that every employee’s PF contribution will automatically increase.

Does the new wage definition affect ESI?

Yes.

The revised wage definition under the Code on Social Security is relevant to ESIC. Employers should review both ESI wage mapping and employee coverage against the applicable provisions.

Does gratuity calculation change under the Labour Codes?

The Code on Social Security changes the statutory framework for gratuity, including the wage definition relevant to applicable calculations.

The Ministry has stated that gratuity under the Code applies from 21 November 2025.

Employers should therefore review the wage components used for gratuity calculations and ensure that the HRMS configuration reflects the applicable requirements.

Do companies need to restructure employee salaries?

Not automatically.

The requirement depends on the employee’s compensation structure and how the relevant components are treated under the applicable wage definition.

Employers should first conduct a salary-component audit before deciding whether restructuring is required.

Are Labour Codes 2026 only a payroll issue?

No.

The changes can affect:

• Payroll
• Salary structures
• Employee records
• Appointment documentation
• PF
• ESI
• Gratuity
• Working conditions
• Statutory reporting
• Full & final settlement
• HRMS configuration

Can an HRMS automatically update Labour Code calculations?

An HRMS can automate statutory calculations when its payroll engine has been correctly configured and updated for the applicable rules.

However, HR teams still need to review compensation structures, validate the configuration and confirm that the system is applying the correct rules for their employees and locations.

What should companies ask their HRMS provider?

Companies should ask their provider:

• How is the new wage definition configured?
• How does the system calculate the 50% add-back?
• How are PF, ESI and gratuity affected?
• Can statutory rules be effective-dated?
• Can the system handle payroll arrears or adjustments?
• Can different entities and locations have different configurations?
• Can the system provide payroll variance reports?
• How are payslips and statutory reports updated?
• How are future statutory changes delivered to customers?

These questions help HR teams evaluate whether their HRMS is actually prepared for labour codes 2026 in India, rather than simply being marketed as “compliance-ready”.

Conclusion

The Labour Codes are not a one-time compliance exercise that HR teams can complete by changing a few payroll labels.

For 2026, the bigger task is making sure that the legal framework is correctly translated into salary structures, statutory calculations, employee records and HRMS workflows.

The revised wage definition and 50% add-back mechanism are particularly important because they can change the wage base used for applicable statutory calculations.

At the same time, PF, ESI, gratuity, payslips, employee documentation and multi-location payroll processes all need to be reviewed against the applicable requirements.

For HR teams, the practical approach is straightforward:

Audit the salary structure → map the wage components → validate statutory calculations → test the HRMS → run a parallel payroll → maintain an audit trail.

An HRMS that keeps statutory rules and payroll calculations aligned can remove much of the repetitive manual work.

But the foundation still comes from getting the compensation structure and statutory mapping right in the first place.

If your payroll structure has not yet been reviewed against the Labour Code framework, explore VeSure HRMS or book a demo to see how payroll and HR compliance can be managed through a unified HRMS workflow.

Official resources: Ministry of Labour & Employment – Labour Code FAQs | ESIC – Official Website