The four codes, payroll-first
Twenty-nine laws became four codes. This guide reads them the way a payroll team must: what changes in the wage base, the contributions, the timelines and the records, and the preparation order that actually works.
Rates and thresholds re-verified 27 July 2026. Statutory figures change by notification, so always confirm against the current official source before acting.
The four codes in one view
India consolidated its central labour law into four codes: the Code on Wages 2019 (minimum wages, timely payment, bonus, equal remuneration), the Code on Social Security 2020 (PF, ESI, gratuity, maternity, gig workers), the Industrial Relations Code 2020 (standing orders, disputes, retrenchment) and the Occupational Safety, Health and Working Conditions Code 2020 (hours, overtime, leave floors, working conditions). Enactment is complete; operationalisation runs through central and state rules on a state-by-state schedule that remains uneven, which is why every serious answer about 'when' is a state answer. Payroll feels the first two codes directly and the other two at the edges: exits, overtime and hours.
The single biggest change: what counts as wages
All four codes share one definition of wages — basic plus DA plus retaining allowance, with excluded components capped in effect at half of total remuneration. Where exclusions exceed 50%, the excess counts back into wages. Every downstream number rides on this base: gratuity accrual, leave encashment, retrenchment compensation, above-ceiling PF where establishments contribute on actuals. The era of the ₹8,000 basic inside a ₹40,000 package is arithmetically over, not because a inspector objects, but because the definition recharacterises it automatically.
What changes on each payroll surface
Wage base: rises toward 50% of package in low-basic structures, lifting gratuity, encashment and actual-wage PF. Take-home: can dip where PF outflow rises, an employee-communication event, not just a computation. Timelines: wage payment windows tighten and exit settlements move toward the two-day standard. Overtime: the OSH code's hours and double-rate overtime discipline demands clean attendance capture. Records: consolidated registers and slips, electronic-friendly, expected consistently. None of these is exotic; together they are a systems upgrade wearing a legal costume.
The preparation sequence that works
-
1
Audit every structure against the 50% test
Composition of basic+DA against total remuneration, per structure template. This is the binding constraint — do it first, and price the statutory consequences of each redesign.
-
2
Model the money
For each redesigned structure: the PF delta (both sides), the gratuity and encashment provision delta, and the take-home effect per employee band. Give finance the annualised number and HR the per-payslip one.
-
3
Fix the clocks
Payment cycles, exit-settlement standards and overtime computation against the codes' timelines; then write the standard down, because a documented standard met is a defence, and an undocumented one is a negotiation.
-
4
Upgrade the records
Registers, wage slips and computation trails in the consolidated formats, generated from the payroll run rather than assembled beside it. Electronic is standard; reconstructable-only is the thing to eliminate.
-
5
Stage the communication
Employees read the codes as 'my take-home changes'. Brief managers first, then staff, with per-band examples: the establishments that communicated early turned a grievance wave into a shrug.
A worked example
A 120-person services firm audits its structures: 70 employees sit on a 35%-basic template. Redesigning to 50% basic lifts the gratuity provision by ₹11 lakh annually and raises employer PF outflow for the 22 above-ceiling employees contributing on actuals; take-home for those 22 dips by ₹900-2,400 a month, moving to their EPF. Finance re-provisions, HR briefs the affected band with before/after payslips, and payroll applies the new templates from April 1 with effect dates. Total elapsed time: one quarter. The alternative — waiting for the state notification and doing all of it in a compliance scramble — prices the same work at panic rates.
Figures are illustrative, for mechanism only. Verify current rates and your own structure before relying on any number.
The IR and OSH codes: payroll's supporting cast
The Industrial Relations Code touches payroll at exits — retrenchment compensation computing on the shared wage definition, notice and dispute procedures shaping how terminations document, and through standing orders for larger establishments, which formalise the attendance and conduct rules payroll executes. The OSH code owns hours, leave floors and overtime, plus appointment letters as a duty. Neither needs a payroll team to become expert; both need the payroll record to be consistent with what the establishment's policies claim, because inspections read across.
Reading the rollout without whiplash
The codes' rollout has been announced, deferred and partially notified enough times that fatigue is rational, and dangerous. The working posture: ignore headlines, watch notifications. Assign one owner (internal or consultant) to track your states' rule-making; treat every 'codes effective from...' story as unverified until the notification exists; and keep design aligned to the definitions regardless, because they are the settled part. Establishments that did this spent the uncertainty years accumulating readiness; the headline-followers spent them oscillating.
How payroll software applies this
PeopleDeck keeps every code-sensitive surface as configuration: structure templates auditable against the 50% composition, wage floors checked at computation, overtime at the statutory rate from captured hours, exit settlements on your documented standard, and registers generated from each approved run. When your state notifies, the change is an effect-dated update — history stays correct under the rules that governed it.
Go deeper: Labour law compliance · Salary structure · Statutory compliance
Primary sources: Ministry of Labour & Employment · India Code
Maintained by Databus Technology Solutions against the source notifications; the verification date above is refreshed whenever a figure changes. This guide explains rules and mechanics; it is not legal or tax advice. PeopleDeck applies statutory rates and generates upload-ready files; it never files returns on your behalf, and positions on contested questions belong with your consultant.
Frequently asked questions
Are the labour codes in force right now?
Enacted fully; effective provision by provision as central and state rules notify, an uneven, ongoing rollout. Treat the definitions as your design standard today and verify your states' notification status with your consultant before each structural decision; this page's status line is dated for exactly that reason.
Will employee take-home really fall?
Where a low-basic structure gets redesigned to meet the wage definition and PF rides the higher base, monthly PF outflow rises and take-home can dip, with the money moving to retirement savings, not vanishing. Model it per structure, and communicate before the first changed payslip, not after.
What happens to gratuity under the codes?
The formula stands; the base widens under the wage definition, and fixed-term employees accrue pro-rata. Net effect: liabilities rise in redesigned structures — re-provision before the auditor asks.
Do the codes change working hours and overtime?
The OSH code standardises the hours framework and keeps overtime at double the ordinary rate with capped hours — making attendance capture and OT computation a compliance surface, not just an operations habit.
What should small businesses do first?
The structure audit; it is cheap, it is the binding constraint, and everything else (provisioning, communication, payroll configuration) flows from it. A fifty-person establishment can complete the whole preparation in a quarter.
Where do the old acts stand meanwhile?
They continue to govern until superseded provision by provision as rules notify, which is why payroll systems keep treatment as dated configuration: old months computed under old rules stay correct, new rules apply from their effective dates.
How do the codes affect contractors and gig workers on our sites?
Contract labour counts toward your establishment's compliance surface as principal employer, and the Social Security Code's gig provisions add a registrable category where your model uses platform-style engagement. The payroll-adjacent duty is evidence: contractor contribution proofs collected monthly, gig engagements recorded distinctly, both cheap to maintain and expensive to reconstruct.
Ready before the notification, not after.
Applied on every payslip, files generated for upload — per employee, per month.
Start free