The Code on Social Security, explained
Nine social-security laws folded into one code, the 2026 wage-ceiling notification that anchored PF under it, and the first statutory framework for gig and platform workers. What changed, what didn't, and what to do.
Rates and thresholds re-verified 27 July 2026. Statutory figures change by notification, so always confirm against the current official source before acting.
What the Code consolidates
The Code on Social Security 2020 merges nine statutes: the EPF Act, the ESI Act, the Payment of Gratuity Act, the Maternity Benefit Act, the Employees' Compensation Act and others — into one framework administering provident fund, insurance, gratuity, maternity and related benefits. The machinery employers know continues: EPFO and ESIC administer their schemes, contribution mechanics persist, and the familiar artifacts (ECR, contribution periods, gratuity formula) carry forward under the Code's chapters. The consolidation's practical significance is definitional and administrative: one wage definition (the same 50% logic as the Code on Wages) across benefits, and a single framework under which thresholds are notified, as happened on 29 May 2026, when the ₹15,000 EPF wage ceiling was formally notified under Chapter III.
The genuinely new part: gig and platform workers
The Code creates, for the first time in Indian law, the categories of 'gig worker' and 'platform worker', and builds them a social-security architecture: registration, schemes funded partly by aggregator contributions computed on turnover within notified bounds, and state-by-state operationalisation that is still hardening. Inter-state migrant workers likewise enter the framework with portability intentions. For conventional employers this chapter changes little directly; for platforms and businesses using gig arrangements, it converts an informal engagement model into a registrable, contribution-bearing one, on a rollout schedule that rewards early structuring and punishes discovered-later informality.
What carried forward, what changed
| Area | Under the Code | Employer action |
|---|---|---|
| EPF mechanics | 12% + 12%, EPS split capped ₹1,250, ceiling ₹15,000 — notified 29 May 2026 under Chapter III | None beyond continued correctness; cite the Code as the operative source |
| ESI mechanics | 0.75% + 3.25% to ₹21,000, contribution periods intact | Continue; watch threshold notifications |
| Gratuity | 15/26 formula, 5-year gate; fixed-term pro-rata provided for | Update FnF treatment for fixed-term staff per current rules |
| Wage definition | The 50% logic shared with the Code on Wages | Audit structures; redesign low-basic packages |
| Gig & platform workers | Defined categories, registration and aggregator-funded schemes, state rollout ongoing | Classify honestly; build records and contribution hooks as states notify |
| Maternity & compensation | Frameworks folded in, entitlements continue | No change to obligations; one code to cite |
Status as re-verified July 2026: the gig-worker provisions in particular are activating state by state; verify your states’ current notifications.
A worked example
A quick-commerce company runs three populations: 400 warehouse employees (EPF and ESI as always, now cited under the Code's chapters), 60 fixed-term seasonal packers (gratuity accruing pro-rata, settlements computing at term close), and 900 delivery riders engaged gig-style. Under the nine-act regime the riders sat in a legal void; under the Code they are a defined category with registration and scheme contributions activating as the company's states notify rules. The establishment that mapped its riders, built the records and watched the notifications converted each state's activation into a configuration date: its competitor, discovering the category at a compliance notice, converted it into a project.
Figures are illustrative, for mechanism only. Verify current rates and your own structure before relying on any number.
Why the consolidation matters even where numbers didn't move
One code means one wage definition, one amendment surface and one citation path, which sounds bureaucratic until you need it. Under the nine-act regime, a single structural question (does this allowance attract contributions?) could have three inconsistent answers across PF, ESI and gratuity; under the Code, the definition converges, and the answer designed once holds across benefits. It also means changes arrive as notifications under one framework (the 2026 ceiling notification being the template) so watching the Code's notification stream is now the whole job of staying current, rather than tracking nine acts' amendment histories.
The gig chapter as a signal, not just a rule
Beyond its specific provisions, the gig-worker chapter signals where Indian social security is heading: coverage following work rather than employment form. Businesses at the boundary — delivery fleets, marketplace workforces, franchise-adjacent staffing — should read the direction, not just the current text: arrangements designed today to sit outside the framework are likely to be pulled inside it by future notification, and the cheap time to build honest records is before the rule, not after the notice. The establishments that navigated GST's arrival best were the ones whose books were already clean; the same will be true here.
Fixed-term employment under the Code
The Code's recognition of fixed-term employment matters beyond gratuity: fixed-term employees are entitled to parity with permanent counterparts in wages and benefits, with gratuity accruing pro-rata per current rules rather than waiting for five years. For seasonal and project-based workforces this converts the fixed-term contract from an informality workaround into a proper statutory category — cheaper than misclassification and cleaner than perpetual 'temporary' status. Encode end dates and let settlements compute at term close.
How payroll software applies this
PeopleDeck anchors its statutory engine to the current notifications under the Code: the ceiling and rates as notified, the contribution periods, gratuity computation including fixed-term treatment, and distinct record-keeping for gig-shaped engagements so state activations land as configuration rather than crisis. When a notification moves a number, the change applies from its effective date with history preserved, which is exactly the trail the framework expects.
Go deeper: PF & ESI compliance · Labour law compliance · PF calculation guide
Primary sources: Ministry of Labour & Employment · EPFO · ESIC
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
Did PF and ESI rates change under the Code?
No: the familiar mechanics carried forward: EPF at 12% + 12% with the EPS split and ₹1,250 cap, ESI at 0.75% + 3.25% to the ₹21,000 ceiling with its contribution periods. What the Code changed is the legal architecture those numbers live in, and the wage definition beneath them.
What did the 29 May 2026 notification actually do?
It formally declared ₹15,000 as the wage ceiling for EPF purposes under the Code's Chapter III — anchoring the operative ceiling in the new framework. The number matched existing practice; the significance is that the Code, not the old Act, is now the operative source.
Who counts as a gig or platform worker?
The Code defines gig workers as earners outside traditional employer-employee relationships, and platform workers as those working through digital platforms. The distinction from employees matters enormously: misclassifying employees as gig workers does not escape PF and ESI — substance governs over label.
What do aggregators have to contribute?
The framework provides for aggregator contributions toward gig-worker schemes computed on turnover within notified percentage bounds, activating as rules notify. Platforms should track their states' notifications; the design decision is building the registration and contribution plumbing before it is compulsory.
Does gratuity change under the Code?
The 15/26 formula and five-year eligibility continue, with the Code providing for fixed-term employees' pro-rata gratuity per its rules. The wage definition beneath the computation is where structures feel the difference.
What should a conventional employer actually do?
Three things: ensure structures meet the 50% wage definition (the same audit the Code on Wages demands), keep contribution treatment anchored to current notifications rather than folklore, and if any part of the workforce is gig-shaped, classify honestly and track the state rollout, with records ready either way.
Where do EPFO and ESIC portals fit under the Code?
Unchanged as the operational interfaces — ECR uploads, contribution payments and registrations continue through the same portals, administered by the same bodies, now exercising powers under the Code's chapters. The practical stack (compute → generate → upload → pay by the 15th) is untouched; the legal citation beneath it moved.
Contributions anchored to the current framework.
Applied on every payslip, files generated for upload — per employee, per month.
Start free