Labour Code Implementation in ERPNext HRMS Made Practical

1. Why This Guide, and What Changed on 21 November 2025

On 21 November 2025, the Government of India notified the four Labour Codes as effective law. Twenty-nine central labour laws stand repealed, including the Payment of Wages Act 1936, Minimum Wages Act 1948, Industrial Disputes Act 1947, Factories Act 1948, Trade Unions Act 1926, Payment of Bonus Act 1965, and the Employees' Provident Funds and Miscellaneous Provisions Act 1952. This is the largest operational change for HR and compliance teams in India in three decades.

Substantive provisions of the codes are now in force. Procedural provisions that explicitly require subsequent rules (wage ceilings, sector-specific exemptions, inspection procedures) remain inoperative until the central rules are finalised. Draft central rules were published on 30 December 2025 with consultation closing in February 2026. Final notification is expected around 1 April 2026, with state rules following thereafter.

Why HR teams cannot wait

Two parts of the codes do not depend on rules. The 50% wage rule under Section 2(y) of the Code on Wages is a self-executing statutory provision. The accelerated full and final settlement deadline of two working days is also operative. Both have direct ERPNext HRMS implications that need to be addressed in the next 60 to 90 days, well before central and state rules are notified.

Who this guide is for

• HR Heads and CHROs at mid-market Indian companies running ERPNext HRMS or planning to migrate.
• Founders and CFOs concerned about the commercial impact of statutory cost increases on PF, gratuity, and bonus.
• ERPNext implementation consultants advising clients on Indian payroll reconfiguration.
• Internal audit and compliance teams reviewing payroll controls under the new codes.

2. The Four Codes: A One-Page Map for HR Heads

Each of the four codes consolidates earlier legislation into a single framework. The map below summarises the laws subsumed, the substantive impact, and the part of ERPNext HRMS that needs reconfiguration.

What is in force, what is pending

In force from 21 November 2025: All substantive provisions that do not require subsequent rule-making. This includes the wage definition under Section 2(y), the 50% wage rule, gratuity for fixed-term employees, the 2-day full and final settlement deadline, and the framework for gig and platform worker social security.

Pending: Wage ceilings for ESI applicability, sector-specific exemptions, working time limits in specific industries, and inspection procedures. These await final central rules and state rules.

3. The 50% Wage Rule: The Single Biggest ERPNext Change

Section 2(y) of the Code on Wages defines wages as all remuneration in monetary terms, with a specific list of exclusions: bonus not forming part of wages, value of housing accommodation, employer PF and pension contributions, conveyance allowance, sum paid to defray special expenses, HRA, overtime allowance, gratuity, retrenchment compensation, and ex-gratia. The First Proviso then states that if these excluded components together exceed 50% of total remuneration, the excess is automatically deemed to be wages.

3.1 What this means in practice

Companies that have historically kept basic salary low (typically 30 to 40 percent of gross) to minimise PF liability now face a structural recalibration. PF, gratuity, bonus, leave encashment, and overtime are all calculated on the wage base. When the wage base grows to 50 percent of total remuneration, every one of these statutory liabilities increases.

Worked example: Rs. 50,000 per month CTC

Two strategic options for HR Heads

• Option A, hold CTC constant: Increase basic to 50%, reduce allowances proportionately. Take-home pay drops by approximately 2 to 5 percent. Employer cost is broadly stable. Communication risk is high. This is the dominant approach we are seeing in client engagements.
• Option B, hold allowances constant: Increase basic without reducing allowances. Take-home pay is preserved. Employer cost rises by 4 to 8 percent depending on the existing structure. This is the path of least employee resistance but requires budget approval.

Industry impact

IT and ITeS, BPO, retail, hospitality, and most service businesses face the highest restructuring impact. Manufacturing and construction often already have basic at or above 50 percent because their wage structures historically followed government wage schedules. A startup of 15 people is treated identically to a manufacturing unit of 5,000 people; the rule does not have a small-establishment exemption.

4. Code on Wages in ERPNext HRMS: Salary Restructure

Salary configuration in ERPNext HRMS lives in three doctypes: Salary Component (defines each earning or deduction line), Salary Structure (combines components with formulas), and Salary Structure Assignment (applies a structure to an employee with a base value). Restructuring under the Code on Wages touches all three.

4.1 Step 1: Audit current Salary Structures

Before changing anything, run an audit. In ERPNext, the Salary Structure doctype carries the formula for every component. The example below from the Frappe HR documentation shows the typical pre-Code formulas: Basic at Base * 0.4, HRA at B * 0.3, DA at B * 0.2.

Run the SQL or use the Salary Structure list view to identify every active structure where Basic is below 50 percent of Base. This is your restructuring universe.

4.2 Step 2: Reconfigure Salary Components

ERPNext Salary Components are the building blocks. Each component carries flags such as Is Tax Applicable, Depends on Payment Days, Is Flexible Benefit, and Is Statistical Component. For Code on Wages compliance, the critical settings are on the earning side.

Recommended Salary Component setup post-Code

4.3 Step 3: Update Salary Structure formulas

Open each affected Salary Structure and edit the Earnings table. Replace the old Base * 0.4 formula on Basic with Base * 0.5 (or higher) and recompute the formulas for HRA and Special Allowance so that the gross remains the desired value. ERPNext's Condition and Formula engine is shown below.

Sample formula recipe for the 50% rule

• Set Basic component formula to: base * 0.5
• Set DA component formula (if used): base * 0.05
• Compute wages_total = BS + DA
• Set HRA: min(BS * 0.5, base * 0.20) for metro; reduce for non-metro
• Set Special Allowance as balancing item: base - BS - DA - HRA
• Validate: every Salary Structure must satisfy (BS + DA) >= 0.5 * base

4.4 Step 4: Re-run Salary Structure Assignment

Once components and structures are updated, every active employee needs a fresh Salary Structure Assignment with an effective date of 1 April 2026 (or whichever date you choose for restructure go-live). ERPNext supports bulk assignment through the Salary Structure Assignment Tool. Always assign with an explicit From Date to preserve payroll history.

4.5 Step 5: Validate with a parallel run

Before going live, run a parallel payroll for one month using both old and new structures. ERPNext supports this through the Payroll Entry doctype: run the new structure as a test in a sandbox or non-production environment, then compare salary slips line by line.

Validation checks during parallel run

• Every salary slip shows BS plus DA at or above 50 percent of base.
• Employer PF contribution has increased in line with the higher wage base.
• Employee PF deduction has increased proportionately, reducing take-home.
• Gratuity provision in the Gratuity ledger reflects the new wage base.
• Statutory bonus calculation (where 8.33 percent applies) uses the new wages.
• Overtime calculation uses the new wage base (overtime forms part of the 50% test per MoLE FAQ).
• Leave encashment formulas use the new wage definition.

5. Code on Social Security in ERPNext: PF, ESI, Gratuity, Gig

The Code on Social Security 2020 consolidates nine earlier laws governing PF, ESI, gratuity, maternity benefit, and employee compensation. Most of the operational mechanisms (EPFO, ESIC) continue. The substantive changes that need ERPNext attention are in gratuity rules, fixed-term employment treatment, and the new framework for gig and platform workers.

5.1 Gratuity in ERPNext: pro-rata for fixed-term

Under the old Payment of Gratuity Act, an employee qualified for gratuity only after five years of continuous service (with limited exceptions). The Code on Social Security removes this five-year requirement for fixed-term employees: gratuity is payable on a pro-rata basis after one year of service, calculated as 15 days' wages for each completed year or part exceeding six months, based on last drawn wages.

ERPNext configuration changes for gratuity

• Open the Gratuity Rule doctype. Update the Calculate Gratuity Amount Based On field to use the new wage definition components.
• Create a separate Gratuity Rule for Employment Type = Fixed Term, with minimum service set to 1 year.
• Ensure the Salary Components feeding the Gratuity Rule include Basic plus DA plus retaining allowance per the new wage definition.
• Configure gratuity payment within 30 days of separation, with a workflow alert at day 25.
• Set up an actuarial provisioning report for the Finance team to update the Gratuity liability monthly.

5.2 PF and ESI: rule changes vs system changes

PF and ESI mechanisms continue under EPFO and ESIC. The arithmetic changes because the wage base changes. ERPNext's standard PF and ESI Salary Components remain the same; only the formula base changes. ESIC wage ceiling continues at Rs. 21,000 gross until further notification. Employees crossing this threshold after restructure may exit ESIC coverage.

Action items for PF and ESI in ERPNext

• Recompute Employee PF and Employer PF Salary Components on the new wage base.
• Run the ESIC Eligibility Report after restructure: any employee with gross newly above Rs. 21,000 needs ESIC exit; any new joiner below Rs. 21,000 needs ESIC enrolment.
• Update the EPF wage ceiling logic if your PF policy is wage-ceiling-based versus actual basic.
• Verify ECR (Electronic Challan-cum-Return) generation reflects new wages.

5.3 Gig and platform workers: a new ERPNext employee type

The Code recognises gig workers (those engaged outside a traditional employer-employee relationship) and platform workers as eligible for social security. The framework is acknowledged but the operational scheme is not yet notified. For ERPNext implementations that engage gig workers (consultants, freelancers, platform staff), the right approach today is to track them as a separate Employment Type so that future scheme contributions can be applied without re-classification.

• Create a new Employment Type called Gig Worker or Platform Worker.
• Use a separate Salary Structure with no PF or ESI components, just professional fee.
• Maintain a register of payments to gig workers, ready for the future scheme contribution rate (likely 1 to 2 percent of payments).

5.4 Other Social Security elements

6. Industrial Relations Code: Standing Orders, Fixed-Term, Exit

The Industrial Relations Code 2020 consolidates the Industrial Disputes Act, the Trade Unions Act, and the Industrial Employment (Standing Orders) Act. All provisions of the IR Code came into force on 21 November 2025. The headline operational changes are around standing orders, fixed-term employment, and the exit process.

6.1 Standing Orders: threshold raised to 300

Earlier, employers with 100 or more workers were required to formulate certified standing orders. The IR Code raises this threshold to 300 workers. Smaller establishments are now exempt from formal standing orders, though they still need terms of employment in writing. For mid-market clients in the 100 to 299 worker range, this is a real simplification.

ERPNext alignment

• If your Employee count crosses 300, formalise standing orders in line with the model standing orders.
• Capture standing-order acknowledgement in the Employee Onboarding workflow.
• Ensure HR Settings include a default Standing Orders document attached to Appointment Letter.

6.2 Fixed-term employment: now formal

The IR Code formally recognises fixed-term employment as a category, with the same statutory benefits as permanent employees on a pro-rata basis. This is the legal basis for the gratuity-after-one-year change in the Social Security Code. Fixed-term employees can be hired without compromising on social security.

ERPNext Employment Type configuration

• Use the Employment Type doctype to create or rename: Permanent, Fixed-Term, Probation, Apprentice, Contract Labour.
• Map each Employment Type to a default Salary Structure and a default Gratuity Rule.
• For Fixed-Term: ensure end date is mandatory in the Employee record, and the Employee Separation workflow auto-triggers on the end date.
• Build a Job Offer template for fixed-term employees that captures the term clearly.

6.3 Retrenchment and layoff thresholds

Establishments with 300 or more workers (raised from 100) need government permission for retrenchment or layoff. Below 300 workers, the employer can proceed with retrenchment subject to notice and compensation requirements. This is a significant easing for mid-market companies.

6.4 Two-day full and final settlement

This is one of the most operationally demanding changes. Section 17 of the Code on Wages requires that all wages due in full and final settlement be paid within two working days of the last day of employment. ERPNext's Full and Final Statement doctype already supports this workflow but the SLA needs aggressive automation.

ERPNext Full and Final automation checklist

• Configure a workflow on Employee Separation that triggers Full and Final Statement creation on the resignation acceptance date.
• Set Notification Rules: 5 days before last working day, 1 day before, on last working day.
• Pre-fill F&F with leave encashment, gratuity, notice pay, recoveries, and final salary.
• Use the Salary Slip generation as a sub-workflow inside F&F to ensure final pay is calculated.
• Build a Bank Payment Entry directly from F&F so payment can issue same-day or next-day.
• Generate Form 16 and PF transfer documents within the same workflow.

7. OSH Code: Hours, Leave, Women, Multi-State Registration

The Occupational Safety, Health and Working Conditions Code 2020 consolidates 13 earlier laws including the Factories Act, Mines Act, Contract Labour Act, Inter-State Migrant Workmen Act, and the Building and Other Construction Workers Act. The OSH Code harmonises working conditions across sectors and modernises several outdated provisions.

7.1 Single registration for multi-state employers

Earlier, an employer operating in multiple states had to obtain registration under each state's Shops and Establishments Act, plus separate registrations under the Factories Act and Contract Labour Act where applicable. The OSH Code provides for a single common registration. Where state rules are notified, this consolidates significantly.

ERPNext Branch master implications

• Ensure each operating location is captured as a Branch in ERPNext with state, address, and registration number.
• Maintain registration documents in the Branch master Attachments.
• Update the Sales Invoice naming series and address fields to reflect single OSH registration where applicable.

7.2 Working hours, overtime, leave

7.3 Women in night shifts

With written consent and prescribed safety arrangements, women may now be employed for night work across all sectors covered by the OSH Code. This is a significant change for manufacturing and warehousing businesses. ERPNext should capture consent as a one-time document in the Employee record and link it to Shift Assignments.

Implementation steps

• Add a custom field Night Shift Consent on the Employee doctype: Yes / No / Not Applicable.
• Build a workflow on Shift Assignment: if shift_type is Night and employee is female, validate Night Shift Consent equals Yes.
• Maintain a Consent Form in Frappe documents, generated as an attachment to the Employee record.
• Confirm employer-side prerequisites: transport, security, and grievance redress mechanisms.

7.4 Health, safety, and grievance

The OSH Code requires safety committees, occupational health centres for hazardous units, and a grievance redress mechanism. ERPNext's Issue / Helpdesk module can be configured as the grievance channel. For occupational health, integrate the Employee Health Insurance doctype with a periodic medical check-up workflow.

8. Implementation Roadmap: 60 Days, Step by Step

A 60-day window is realistic for most mid-market ERPNext implementations. Manufacturing and multi-state operations may need 90 days. The roadmap below sequences the work so that statutory risk is contained early and configuration follows.

Phase 1, Days 1 to 10: Diagnostic and Inventory

• Map every active Employee to current Salary Structure and Employment Type.
• Calculate current Basic as a percentage of gross CTC for every employee.
• Identify the restructuring universe (employees where Basic is below 50%).
• Inventory all state registrations, factory licences, and labour returns.
• Document current standing orders, fixed-term contract templates, and F&F SOPs.

Phase 2, Days 11 to 25: Design and Approval

• Model the financial impact of Option A vs Option B (Section 3) and present to Finance.
• Get CEO and CFO sign-off on the chosen restructuring approach and effective date.
• Draft revised Salary Components, Salary Structures, and Gratuity Rules in a sandbox ERPNext site.
• Draft updated Appointment Letter, fixed-term contract, and F&F templates.
• Prepare employee communication: rationale, take-home impact, FAQ.

Phase 3, Days 26 to 45: Configure and Test

• Reconfigure Salary Components in production ERPNext (with audit log).
• Update Salary Structures and assign to employees with effective From Date.
• Update Gratuity Rule with new wage base.
• Update Leave Type, Holiday List, and Shift Type per OSH Code provisions.
• Run a parallel payroll for one month: compare salary slips line by line.
• Test the F&F workflow end-to-end against the 2-day SLA.

Phase 4, Days 46 to 60: Go-live and Communication

• Issue revised Salary Structure assignments effective the chosen go-live date.
• Communicate to employees: 1:1 for sensitive cases, town hall for the rest.
• Run first month's payroll on the new structure with HR and Finance review.
• Generate first F&F under the 2-day SLA and review for any process gaps.
• Hand over to BAU operations with a documented runbook and escalation matrix.

10. Governance Checklist for HR Heads, CFOs, and Consultants

This checklist consolidates the controls a steering committee should expect to see operating after Labour Code go-live. Use it during quarterly HR-Finance reviews.