[Analysis] Labour Code Implementation Roadmap under the Code on Wages 2019 – Day 0 Decisions | 30-60-90 Day Plan | Implementation Checklist
- Blog|Labour & Industrial Laws|
- 15 Min Read
A 30-60-90 day plan for labour code implementation under the Code on Wages 2019: Day 0 decisions, owners and outputs, risks and the test of completion.
- By Taxmann
- |
- Last Updated on 16 November, 2026

Table of Contents
- Why is labour code implementation different from knowing the law?
- Is the new labour code implemented in India?
- What should management decide on Day 0?
- What does the 90-day plan cover?
- What happens in the first 30 days?
- What should be ready by Day 60?
- What does Day 90 stabilisation require?
- Who does what, and which risks need watching?
- What changes for small and large employers?
- When is implementation complete?
- Quick answers
1. Why is labour code implementation different from knowing the law?
Because the Code on Wages, 2019 becomes meaningful only when it is translated into systems (para 13.16). Taxmann’s HR Guide to Code on Wages puts the practical question for an HR manager, payroll head, finance controller or business owner as how the Code should be reflected in appointment letters, salary structures, attendance systems, payroll software, contractor bills, wage slips, registers and management reports (para 13.1).
The reason is the reach of the law. The Code affects job classification, salary design, wage period, minimum wage mapping, overtime calculation, deductions, contractor payments, wage slips, records and claims handling. Payroll can pay every salary correctly and still carry compliance risk if it does not capture the correct wage period, attendance, overtime, deductions and wage slip details (para 13.1).
Chapter 34 therefore says implementation should be handled as a practical payroll transformation project, not a one-time legal circular, with HR, payroll, finance, legal, IT, admin, procurement, operations and internal audit working together (para 34.1). Chapter 1 adds that the Code should be implemented as a payroll governance law, not merely as a labour law to be filed in the legal department (para 1.5).
The objective is simple to state (para 13.1): every employee correctly classified, every wage component correctly mapped, every payment traceable, every deduction authorised, every wage slip agreeing with payroll records and every management decision leaving a reliable audit trail. For management, the book calls this a shift from reactive compliance to system-based compliance (para 13.16).
2. Is the new labour code implemented in India?
The book refers to 21 November 2025 as the date of implementation of the Codes, in reporting the Additional FAQ dated 16 March 2026, under which gratuity based on the revised definition of wages applies from that date (para 24.15).
Section 1(3) of the Code provides that it comes into force on such date as the Central Government may notify in the Official Gazette, and different dates may be notified for different provisions. The book therefore advises reading the Act and the Rules with the latest commencement notifications applicable on the date of implementation, and verifying three things before implementation: the Code, the applicable Central or State Rules, and the latest notifications relevant to the establishment (para 1.4). For that check, Taxmann.com | Premium brings Research, Practice and Learning under one search.
Which Rules apply depends on the sphere. For Central sphere establishments, the Wages (Central) Rules, 2026 must be read along with the Code. For State sphere establishments, the corresponding State Rules, minimum wage notifications and local instructions must also be checked before implementation (para 13.1).
Commencement is a legal question. Whether an organisation has implemented the Code is a separate one, and the book judges it by what payroll can show every month (para 34.2).
3. What should management decide on Day 0?
Who runs the project, and ten decisions that shape it. The book’s first step is for management to appoint a small implementation team (para 34.3):
| Role | Responsibility |
|---|---|
| Project sponsor | CEO, CFO, CHRO or managing partner |
| Project owner | HR Head or Compliance Head |
| Payroll lead | Payroll process and system configuration |
| Finance lead | Cost, PF, gratuity, bonus, provisions and payments |
| Legal lead | Interpretation, policies, contractors and deductions |
| IT lead | Payroll configuration, audit logs and reports |
| Operations lead | Attendance, shifts, overtime and work allocation |
| Admin or procurement lead | Contractor records and invoice controls |
| Internal audit lead | Gap review and implementation validation |
In a smaller organisation the same person may handle several roles, but ownership should still be clear. Before implementation starts, management should then decide the following (para 34.4):
| Decision point | Management decision |
|---|---|
| Scope | Only Code on Wages or all labour codes |
| Entities | Single entity or group-wide |
| Locations | All locations or phased rollout |
| Workforce | Employees, workers, contractors and consultants |
| Salary restructuring | CTC-neutral or cost-adjusted |
| Take-home protection | Full, partial or case-wise |
| Contractors | Included from Day 1 or phased |
| Payroll system | Existing system, new system or interim Excel control |
| Communication | Employee FAQ, email, meeting or handbook |
| Approval | Who signs off policy and payroll changes |
These decisions should be documented in a one-page kick-off note. The scope row decides whether the project covers only the Code on Wages or becomes a wider labour codes implementation. The restructuring and take-home rows carry cost, and the book asks finance teams to model the impact of the wage definition on statutory liabilities. If wages increase because excluded allowances exceed the permitted threshold, there may be a direct impact on gratuity, provident fund and other wage-linked benefits, depending on the applicable law (para 13.12).
The payroll system row matters where the existing system cannot yet support the 50 per cent wage rule. The book’s risk register pairs that risk with interim Excel validation and system enhancement (para 34.14).
4. What does the 90-day plan cover?
Three blocks of 30 days, each built around one question and one key output (para 34.5):
| Timeline | Main question | Key output |
|---|---|---|
| First 30 days | What is the current exposure? | Diagnostic and gap report |
| First 60 days | Have policies and systems been changed? | Updated policies and payroll configuration |
| First 90 days | Is compliant payroll operating with evidence? | Audit report, dashboard and management sign-off |
The book allows the roadmap to be shortened for small employers and expanded for large multi-State employers. Its summary sets the focus of each block (para 34.21): diagnosis first, covering workforce mapping, wage component classification, the 50 per cent wage rule, minimum wages, deductions, overtime, bonus, full and final settlement (F&F) and contractor risks; then implementation through policies, payroll software, salary structures, wage slips, registers, contractor controls and employee communication; and finally stabilisation, from the first compliant payroll run to internal audit, the management dashboard and sign-off.
Chapter 13 makes the same case: a phased approach works better than a one-time legal circular. Its ten-phase sequence, which may be adopted, ends with a payroll dry run with exception testing and a quarterly compliance review placed before management (para 13.13). In the book’s view, the easiest way to avoid the common implementation mistakes is to use the 30-60-90 roadmap as a project plan (para 34.20).
5. What happens in the first 30 days?
Diagnosis of the current position. The objective is to identify where the organisation is exposed, and each task has an owner and an output (para 34.6):
| Action | Owner | Output |
|---|---|---|
| Collect employee master, salary structures and payroll data | HR/Payroll | Data repository |
| Identify entities, establishments and locations | HR/Legal | Applicability matrix |
| Map employees, workers, fixed-term employees and contractors | HR | Workforce classification |
| Classify salary components | Payroll/Finance/Legal | Component mapping |
| Run 50% wage rule test | Payroll/Finance | Wage rule exception report |
| Prepare State and skill-wise minimum wage matrix | HR/Compliance | Minimum wage report |
| Review deductions | Payroll/Finance | Deduction risk report |
| Review overtime and attendance | HR/Operations | Overtime gap report |
| Review F&F cases | HR/Payroll | F&F delay report |
| Review bonus eligibility | Payroll/Finance | Bonus exposure report |
| Review contractor compliance | Admin/HR/Finance | Contractor risk report |
| Present findings to management | Project owner | 30-day diagnostic report |
The 30-day review should not attempt to solve every issue; it should identify issues clearly. By Day 30, management should receive twelve deliverables, including a contractor compliance report on wage proof, PF, ESI and licence gaps, a payroll system gap report and a management risk summary in Red, Amber and Green (para 34.7). The most important Day 30 output, in the book’s words, is a risk-rated gap report.
Chapter 13 explains why the employee master is the starting point for every payroll control. An error in designation, category, location, employment type or wage rate in the master flows into minimum wage checking, overtime, wage slips, final settlement, contractor verification and annual returns (para 13.2). Component names are not decisive either: calling an amount “special allowance” or “flexi allowance” will not decide its treatment under section 2(y) (para 13.3). Where a component or an establishment does not fit a category cleanly, the question can be put to Taxmann AI, a legal research and drafting assistant that answers questions against the law.
6. What should be ready by Day 60?
Updated policies plus payroll configuration, which the book calls the most important Day 60 output (para 34.8). The objective of the next 30 days is to change policies, payroll configuration and monthly controls:
| Action | Owner | Output |
|---|---|---|
| Approve implementation priorities | Management | Approved action plan |
| Finalise wage component classification | Payroll/Legal/Finance | Final component master |
| Revise salary structures where required | HR/Finance | Revised salary annexures |
| Amend HR policies | HR/Legal | Updated policies |
| Configure payroll system | Payroll/IT | Payroll rule update |
| Configure minimum wage validation | HR/Payroll/IT | Minimum wage engine |
| Configure deduction cap and carry-forward | Payroll/IT | Deduction control |
| Configure F&F two-working-day alert | HR/IT | F&F workflow |
| Configure wage slips and registers | Payroll/IT | Wage slip and register output |
| Set up contractor monthly verification | Admin/HR/Finance | Contractor checklist |
| Create bonus eligibility tracker | Payroll/Finance | Bonus register |
| Conduct UAT | HR/Payroll/IT | UAT sign-off |
| Train HR, payroll, finance and managers | Project owner | Training note |
| Issue employee communication | HR | Employee FAQ |
The 60-day checklist makes the output concrete (para 34.9). Its eighteen items, each marked Done or Pending, are ten document and policy updates, from the appointment letter and salary annexure to the record retention policy, and eight system settings, from the wage component master to audit logs. Its last line is that policy, payroll configuration and employee communication should be aligned.
Chapter 13 shows what alignment means in practice. Where salary is expressed as CTC, the appointment letter should separately identify gross wages, employer contributions, reimbursements, variable pay and statutory benefits, and a policy that says management may deduct any amount from salary at its discretion is not aligned with the Code (para 13.11).
Payroll teams should also verify whether their software can handle the 50 per cent test, wage component classification, overtime, the deductions ceiling, statutory registers, wage slips and final settlement timelines. If it only processes salary and cannot generate statutory records, manual dependency will continue (para 13.12). Where the updated policies have to become written SOPs and the payroll rules have to be configured in the ERP, Taxmann Advisory offers implementation support, including compliance SOPs and ERP automation for compliances.
7. What does Day 90 stabilisation require?
A first payroll under the new configuration, tested with evidence. The final 30 days should test whether the implementation works in actual payroll, and their objective is to confirm that compliant payroll can be processed with evidence (para 34.10):
| Action | Owner | Output |
|---|---|---|
| Process first payroll under new configuration | Payroll | Trial or live payroll |
| Review exception reports | HR/Payroll | Exception closure report |
| Validate minimum wage, 50% rule and deduction cap | Internal audit | Compliance test report |
| Verify wage slips and bank proof | Payroll/Finance | Payment evidence |
| Test F&F process | HR/Payroll | F&F validation report |
| Verify contractor invoice control | Admin/Finance | Contractor compliance report |
| Conduct internal audit review | Internal audit/advisor | Audit observations |
| Correct remaining gaps | Project team | Corrective action tracker |
| Present report to management | Project owner | 90-day report |
| Approve steady-state controls | Management | Governance sign-off |
The most important Day 90 output is an audit-backed management report. The book then sets the conditions on which implementation may be treated as stabilised (para 34.11):
| Success criterion | Target |
|---|---|
| Employees mapped to State and skill category | 100% |
| Salary components classified | 100% |
| 50% wage rule report generated | 100% |
| Minimum wage exceptions reviewed | 100% |
| Wage slips issued | 100% |
| Bank payment proof preserved | 100% |
| F&F two-working-day tracker active | 100% |
| Deduction cap configured | 100% |
| Overtime workflow active | 100% |
| Bonus eligibility tracker active | 100% |
| Contractor compliance checklist active | 100% |
| Registers generated | 100% |
| Audit logs enabled | 100% |
| Monthly dashboard reviewed | 100% |
Where 100 per cent is not achieved, exceptions should be recorded with owner and due date. After Day 90, the book suggests a board or management note on implementation status for Day 1 to Day 90, with a status and key remarks for each area from employee classification to residual risks (para 34.17). It asks management to approve the residual corrective actions, the monthly compliance dashboard, a quarterly internal audit review, the contractor invoice hold mechanism and the closure of the employee communication and policy rollout.
The suggested sign-off certificate records that the initial implementation review has been completed and that the exceptions identified are in the corrective action tracker, assigned to responsible owners. HR, payroll, finance and management should sign it, and internal audit may countersign after review (para 34.18).
8. Who does what, and which risks need watching?
The book gives a simple responsibility matrix for twelve activities and a register of ten implementation risks (paras 34.13 and 34.14). In the matrix, a blank cell means the book shows no role for that function in the activity:
| Activity | HR | Payroll | Finance | Legal | IT | Admin | Internal audit |
|---|---|---|---|---|---|---|---|
| Workforce classification | Lead | Support | Review | Test | |||
| Salary component mapping | Support | Lead | Lead | Review | Configure | Test | |
| 50% wage rule | Support | Lead | Lead | Review | Configure | Test | |
| Minimum wage matrix | Lead | Support | Review | Configure | Test | ||
| Policy amendment | Lead | Support | Support | Lead | Review | ||
| Payroll configuration | Support | Lead | Support | Review | Lead | Test | |
| Deduction control | Support | Lead | Lead | Review | Configure | Test | |
| Overtime workflow | Lead | Lead | Review | Configure | Support | Test | |
| F&F workflow | Lead | Lead | Support | Review | Configure | Support | Test |
| Bonus tracker | Support | Lead | Lead | Review | Configure | Test | |
| Contractor compliance | Support | Support | Review | Lead | Test | ||
| Dashboard | Lead | Lead | Support | Configure | Review |
Internal audit tests ten of the twelve activities and reviews the other two, and IT configures eight of them and leads payroll configuration. Not involving IT and the payroll vendor is one of the common implementation mistakes the book lists, alongside treating implementation as only legal review, not including contractors, updating policy but not payroll software, updating payroll software but not training managers, and not preserving evidence (para 34.20). For smaller organisations, the matrix should be simplified.
The risk register pairs each risk with its impact and a control, and it should be reviewed every fortnight during implementation (para 34.14):
| Risk | Impact | Control |
|---|---|---|
| Salary restructuring affects take-home | Employee dissatisfaction | Simulate impact and communicate |
| Payroll system cannot support wage rule | Recurring non-compliance | Interim Excel validation and system enhancement |
| Minimum wage data incomplete | Wage shortfall | State-wise notification tracker |
| Contractor refuses worker-wise proof | Principal employer exposure | Invoice hold clause |
| F&F delayed due to asset return | Wage claim | Separate wage payment from asset recovery |
| Managers do not approve overtime | Unpaid overtime | Training and workflow |
| Bonus missed for resigned employees | Bonus claim | Bonus tracker including exits |
| Deductions exceed 50% cap | Illegal deduction dispute | Payroll cap and carry-forward rule |
| Records lost during migration | Claim defence failure | Migration archive plan |
| Employees misunderstand restructuring | Employee relations issue | FAQ and HR communication |
The overtime row is the one that depends on line managers. Where managers do not approve overtime, the impact is unpaid overtime and the control is training and workflow. Chapter 13 adds that many wage disputes begin with operational decisions, such as asking employees to work late, approving unpaid leave, imposing informal penalties or withholding final settlement (para 13.12). For that training, Taxmann.com | Learning runs webinars, workshops and masterclasses, live or recorded, in subject areas that include Labour Laws, and sessions can be arranged for an organisation.
9. What changes for small and large employers?
The three blocks stay, but their depth changes. For MSMEs and smaller establishments the roadmap can be simplified, and for large and multi-State employers implementation should be project-managed (paras 34.15 and 34.16):
| Block | Small employer (para 34.15) | Large or multi-State employer (para 34.16) |
|---|---|---|
| First 30 days | Prepare employee list; map work location and skill category; check minimum wages; review salary components; identify contractors; review wage slips and payment proof; review deductions and F&F cases | Multi-location data extraction; State-wise minimum wage mapping; salary structure and wage definition simulation; employee category mapping; contractor risk segmentation; payroll system gap assessment |
| First 60 days | Update appointment letter; create wage register and attendance register; start wage slip issue; create deduction register; create contractor monthly file; update payroll spreadsheet or software; train owner, HR and accountant | Policy rollout; payroll configuration; UAT across employee categories; manager training; contractor compliance integration; employee communication; finance impact modelling |
| First 90 days | Run first compliance payroll; check minimum wage and deductions; verify bank payment proof; archive monthly records; review contractor wage proof; prepare management checklist | Parallel payroll validation; first compliant payroll run; internal audit; contractor invoice gate validation; board or audit committee dashboard; corrective action closure |
Small employers need not create complex dashboards, but they must maintain evidence. Large employers should not rely on manual checks alone, and their final 30 days include parallel payroll validation and a board or audit committee dashboard.
A simpler track is not an exemption. MSME registration does not automatically remove obligations under the Code, and an MSME should still check whether minimum wages are paid, wage periods are fixed, salary is paid within time, deductions are lawful, wage slips are issued, records are preserved, wages payable on exit are paid within two working days, eligible employees are considered for statutory bonus and contractor workers are paid properly (para 22.4). For the evidence, Chapter 22 suggests that instead of many scattered records an MSME can maintain five core monthly files: an employee and wage master, an attendance and overtime file, the wage register and wage slips, a bank payment and deduction file, and a contractor and F&F file (para 22.33).
10. When is implementation complete?
Only when compliant payroll can be processed, evidenced, reported and audited every month, which is the book’s core implementation principle (para 34.2). A policy document alone is not implementation, and neither is a payroll configuration alone or a checklist alone. The organisation has to be able to show the evidence for each requirement:
| Requirement | Evidence |
|---|---|
| Employees are classified correctly | Employee master |
| Wages are legally mapped | Component mapping |
| Minimum wages are checked | Minimum wage report |
| 50% wage rule is tested | Wage rule report |
| Deductions are controlled | Deduction cap report |
| Overtime is captured | Overtime register |
| F&F is timely | Exit settlement tracker |
| Bonus is tracked | Bonus eligibility report |
| Contractors are verified | Contractor compliance file |
| Wage slips are issued | Wage slip archive |
| Registers are maintained | Statutory registers |
| Payroll changes are traceable | Audit logs |
Annexure 9, the book’s Implementation Checklist for Companies, is a labour code implementation checklist for management, HR, payroll, finance, IT and compliance teams, which should be used before go-live and then as a monthly compliance review tool. Each of its twenty-seven areas has a status (Done or Pending), an owner and the evidence. Its areas also include the wage period being fixed and communicated, notice board display of minimum wages, working hours, wage period, payment date and Inspector-cum-Facilitator details, a recovery schedule for salary advances and loans, a separate show cause and valuation process for damage recovery, and wage records preserved for at least five years. It also has 30-day, 60-day and 90-day checklists, a monthly compliance dashboard and a management sign-off format.
The test is monthly, and so are the controls that follow the project. After 90 days, implementation should move into steady-state compliance, with twelve monthly controls, from the minimum wage exception report to the audit log review, becoming part of monthly payroll closure (para 34.19). The management dashboard should also continue, with a target of nil for every metric except employees failing the 50 per cent wage rule test, where it is nil or approved action (para 34.12). The monthly routine is covered in the post on monthly payroll compliance.
Annexure 9 closes with its final implementation rule. The company should treat implementation as complete only when:
- Payroll can validate compliance before payment.
- Wage slips and registers are generated.
- Contractor invoices are linked to wage compliance.
- F&F cases are tracked separately.
- Deductions are capped and documented.
- Bonus eligibility is tracked.
- Management receives a monthly exception dashboard.
Its closing note makes the same point: implementation is not complete when policies are drafted.
11. Quick answers
Is the new labour code in force?
Taxmann’s HR Guide to Code on Wages, reporting the Additional FAQ dated 16 March 2026, refers to 21 November 2025 as the date of implementation of the Codes. Because section 1(3) of the Code on Wages, 2019 allows different dates for different provisions, the book advises checking the Code, the applicable Central or State Rules and the latest notifications relevant to the establishment before implementation.
How should an employer implement the Code on Wages?
As a payroll transformation project rather than a one-time legal circular, with HR, payroll, finance, legal, IT, admin, procurement, operations and internal audit working together. Taxmann’s HR Guide to Code on Wages sets a 30-60-90 day roadmap that diagnoses the exposure in the first 30 days, changes policies and payroll configuration by Day 60 and runs compliant payroll with evidence by Day 90.
What should management decide first?
Before implementing the Code on Wages, 2019, management should appoint a small implementation team and decide the scope, entities, locations and workforce covered, whether salary restructuring is CTC-neutral or cost-adjusted, how far take-home pay is protected, when contractors are included, the payroll system, the communication route and who approves policy and payroll changes. These Day 0 decisions should be documented in a one-page kick-off note.
What does the 90-day implementation plan cover?
In the 30-60-90 day roadmap in Taxmann’s HR Guide to Code on Wages, the first 30 days diagnose the current exposure and produce a risk-rated gap report. The next 30 days update policies and payroll configuration, and the final 30 days run and audit the first payroll under the new configuration, ending with an audit-backed management report and governance sign-off.
What differs for a small employer?
For MSMEs and smaller establishments, the 30-60-90 day roadmap for the Code on Wages, 2019 can be simplified, and one person may handle several roles, though ownership should still be clear. Small employers need not create complex dashboards, but they must maintain evidence, and MSME registration does not automatically remove obligations under the Code.
When is labour code implementation complete?
Only when compliant payroll can be processed, evidenced, reported and audited every month, which is the test Taxmann’s HR Guide to Code on Wages sets. A policy document, a payroll configuration or a checklist on its own is not implementation.
What happens after the first 90 days?
After the 90-day project, implementation of the Code on Wages, 2019 should move into steady-state compliance. Monthly controls such as the minimum wage exception report, the deduction cap report and the two-working-day full and final settlement report should become part of monthly payroll closure, and management should keep receiving a monthly dashboard.
This article draws on Chapter 34 of Taxmann’s HR Guide to Code on Wages by CA Venugopal Gella (2026 Edition), which sets out the management implementation roadmap with Day 0 decisions, owners and outputs for each 30-day block, 90-day success criteria, a responsibility matrix, a risk register, separate roadmaps for small and large employers, a board note and a sign-off certificate. It also draws on Annexure 9, the implementation checklist for companies, with 30-, 60- and 90-day checklists, a monthly compliance dashboard and the final implementation rule, and on Chapter 13, which translates the Code into HR and payroll practice. Law stated as updated till August 2026. The wider position across all four labour codes is covered in Taxmann’s Employer-Employee’s Guide to New Labour Laws.
Labour law Acts and Rules, case laws, circulars and notifications are available on Taxmann.com | Research under Labour Laws.
Related reading: the complete guide to the Code on Wages, 2019 · section 69 and what survives the repeal · equal remuneration under sections 3 and 4.
More in this series: full and final settlement under the Code on Wages · wage slip format under the Code on Wages · statutory bonus calculation · new labour code salary structure · deductions from wages and the 50% limit · payment of wages: wage period and time limits · overtime rules under the Code on Wages · minimum wages as per the new labour code · principal employer and contractor wage compliance · 34 common payroll mistakes · monthly payroll compliance.
Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.
The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:
- The statutory material is obtained only from the authorized and reliable sources
- All the latest developments in the judicial and legislative fields are covered
- Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
- Every content published by Taxmann is complete, accurate and lucid
- All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
- The golden rules of grammar, style and consistency are thoroughly followed
- Font and size that’s easy to read and remain consistent across all imprint and digital publications are applied


CA | CS | CMA