insight
Preparing for the Code on Wages: Actionable steps for payroll teams
Published on 26 May 2026 - Reading time: 8-9 mins
The Code on Wages, enacted in 2019 as part of India’s labour code framework, introduces a standard definition of wages that applies across minimum wages, statutory benefits and related payroll calculations. While the legislation itself is established, practical application depends on central rules and state‑level notifications, with implementation progressing through 2025 and 2026.
For payroll teams, this means preparation is no longer a future consideration. The focus shifts from understanding the law to ensuring payroll structures, systems and processes can support wage‑based calculations accurately and consistently as requirements are applied.
This guide sets out the practical steps payroll teams can take to prepare, focusing on execution, sequencing and operational readiness rather than legal interpretation.
Table of Contents
- Step 1: Establish a clear preparation baseline
- Step 2: Review pay‑head purpose and consistency
- Step 3: Check payroll system readiness
- Step 4: Model cost and liability impact before acting
- Step 5: Align cross‑functional ownership and assumptions
- When technology or managed payroll services can support preparation
- Preparation as an operating discipline, not a one‑off task
Step 1: Establish a clear preparation baseline
Before making any decisions, payroll teams need an accurate view of the current state. This baseline becomes the reference point for all further analysis and discussion.
At this stage, the goal is visibility, not judgement. Payroll teams should focus on understanding what exists today, rather than deciding what should change tomorrow.
What to do
- List all existing pay heads used across the organisation.
- Identify how each component is calculated, paid and recorded in payroll systems.
- Note variations by role, grade, business unit or location.
If a pay component is hard to explain today, it will be even harder to explain once rules change.
Step 2: Review pay‑head purpose and consistency
Once visibility is established, the next step is to review why each pay head exists and how consistently it is applied. The Code on Wages places greater emphasis on structure and intent, not just outcome.
This review does not require immediate restructuring. It requires payroll teams to ask basic, practical questions and document the answers.
Key questions to answer
- What is the intended purpose of this pay head?
- Is it fixed or variable in practice?
- Is it applied consistently to comparable employees?
- Is its treatment aligned across payroll, HR and finance systems?
Pay-head review snapshot:
|
Pay head |
Purpose |
Fixed / variable |
Paid to whom |
Current treatment |
|
Basic pay |
Core salary |
Fixed |
All employees |
Treated as wages |
|
House rent allowance |
Housing support |
Fixed |
Eligible employees |
Excluded |
|
Special allowance |
Residual pay |
Fixed |
Select roles |
Excluded |
|
Performance bonus |
Incentive |
Variable |
Eligible employees |
Included when paid |
|
Transport allowance |
Commute support |
Fixed |
All employees |
Excluded |
Step 3: Check payroll system readiness
Preparation under the Code on Wages depends heavily on whether payroll systems can support wage‑based calculations in a controlled way. System readiness is about capability, not technology replacement.
What payroll systems should support
- Consistent classification of wage and non‑wage components.
- Automatic recalculation of statutory bases when pay composition changes.
- Parallel or shadow payroll runs for impact testing.
- Clear reporting that shows how wages and deductions are derived.
If payroll relies on manual spreadsheets or offline workarounds, it becomes much harder to respond when new rules are introduced later, because every change requires manual re‑engineering and re‑checking. An integrated payroll system absorbs those changes more efficiently and leaves a clearer audit trail.
Confirm whether systems can support wage‑based calculations and testing:
|
Area to check |
Supported today |
Manual workaround |
|
Wage vs non‑wage classification |
Yes / No |
Yes / No |
|
PF / ESI base recalculation |
Yes / No |
Yes / No |
|
Parallel payroll runs |
Yes / No |
Yes / No |
|
Audit trail & reporting |
Yes / No |
Yes / No |
|
State‑specific rules |
Yes / No |
Yes / No |
Step 4: Model cost and liability impact before acting
Changes to wage definitions may affect more than monthly payroll outputs. Employer contributions, gratuity exposure and exit settlements can all be influenced by wage composition.
Payroll teams should work with finance to model scenarios before applying changes, using current data and realistic assumptions. This supports informed decision‑making and avoids last‑minute reactions.
Cost and liability impact – scenario view:
|
Salary structure |
PF base |
Gratuity base |
Employer statutory cost |
|
Current structure |
Lower |
Lower |
Baseline |
|
Revised structure (scenario A) |
Higher |
Higher |
Increased |
|
Revised structure (scenario B) |
Moderate |
Moderate |
Neutral |
Step 5: Align cross‑functional ownership and assumptions
Effective preparation requires alignment across payroll, HR and finance. Differences in interpretation or assumptions often create downstream payroll issues rather than calculation errors.
Areas that need alignment
- Which components are treated as wages for statutory purposes.
- How exceptions are defined, applied and documented.
- Who signs off structural or treatment changes.
- How decisions are explained to auditors and employees.
Cross‑functional alignment quick checklist:
|
Topic |
Owner |
Agreed position |
Documented |
|
Wage definition used |
Payroll |
Yes / No |
Yes / No |
|
Allowance exclusions |
HR |
Yes / No |
Yes / No |
|
Exception handling |
Payroll |
Yes / No |
Yes / No |
|
Approval authority |
Finance |
Yes / No |
Yes / No |
|
Audit explanation approach |
Joint |
Yes / No |
Yes / No |
When technology or managed payroll services can support preparation
As preparation progresses, internal capacity may become a constraint – particularly for organisations operating across multiple states or running complex pay structures.
Payroll technology can help by supporting modelling, consistent treatment and reporting. Managed payroll services can further reduce operational strain by monitoring regulatory updates, applying changes consistently and supporting testing and validation.
Preparation as an operating discipline, not a one‑off task
Preparing for the Code on Wages is not a single project with an end date. It is an operating discipline built on clarity, documentation and collaboration.
Payroll teams that focus on understanding current structures, testing impact carefully and aligning stakeholders are better positioned to respond confidently as implementation continues.
