The Code on Wages, explained
One code replacing four wage laws: universal minimum wages, tighter payment timelines, and the 50% wage definition that quietly redesigned Indian salary structures. Here is what it says and what it changes.
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 Wages 2019 merges four statutes: the Payment of Wages Act, the Minimum Wages Act, the Payment of Bonus Act and the Equal Remuneration Act — into one framework covering every employee, organised sector or not. Its four pillars: a universal right to minimum wages (with a central floor wage concept beneath state-notified rates), timely payment obligations with defined cycles and exit timelines, bonus provisions carried forward from the bonus law, and equal-remuneration protections. Enacted in 2019, its operationalisation runs through central and state rules, a rollout that has proceeded state by state, which is why 'is it in force for me?' remains a state-specific question worth verifying at any given date.
The definition that matters most: wages at 50%
The Code's defined term 'wages' includes basic pay, dearness allowance and retaining allowance, and excludes a list (HRA, conveyance, overtime, commission and others) but with a proviso with teeth: if the excluded components exceed half of total remuneration, the excess counts back into wages. The practical effect is a floor — basic plus DA effectively cannot be engineered below 50% of the package for computation purposes. Because PF, gratuity and leave encashment ride on this wage definition as the codes operationalise, low-basic structures lose their arithmetic advantage: the statutory bases rise toward half the package regardless of how the components are labelled.
What employers should do about it
-
1
Audit structures against the 50% test
Sum each structure's basic + DA (+ retaining allowance) against total remuneration. Below half, the excess of exclusions counts back as wages anyway, so redesign deliberately rather than being redefined implicitly.
-
2
Re-check the statutory bases
Where wages rise under the definition, gratuity accrual, leave encashment and above-ceiling PF follow. Re-provision the liabilities on the new arithmetic before an auditor does it for you.
-
3
Map minimum-wage floors to categories
Match every role to its state, scheduled employment and skill category, and hold the notified floor against computed wages monthly, including piece-rate and daily-wage computations.
-
4
Tighten payment timelines
Set payroll and FnF calendars to the Code's cycles — month-end payment within the notified window, exit wages on the prompt-settlement standard, and document the standard you hold.
-
5
Watch the state rollout
Rules notify state by state and evolve. Keep treatment as dated configuration, brief leadership when your states move, and re-verify before every structural redesign.
A worked example
A ₹10,00,000 package structured the old way: basic ₹3,00,000 (30%), HRA ₹1,50,000, special allowance ₹5,50,000. Under the Code's definition, exclusions total ₹7,00,000 (70% of remuneration) so ₹2,00,000 of the excess counts back into wages, making the effective wage base ₹5,00,000 whether the payslip says so or not. Gratuity and encashment now accrue on the higher base; the labelling achieved nothing. The redesigned structure (basic ₹4,50,000, HRA ₹2,25,000, balance allowance) meets the definition honestly, prices the statutory layer correctly at offer time, and leaves nothing for an inspector to recharacterise.
Figures are illustrative, for mechanism only. Verify current rates and your own structure before relying on any number.
What the Code means for bonus and equal remuneration
Two carried-forward regimes deserve their own attention. Statutory bonus continues for employees within the notified wage threshold, computed on the Code's wage definition, which can pull more employees into eligibility than the old computation did; establishments that treated bonus as a legacy formality should recount. Equal-remuneration protections, same work, same wages, no gender discrimination in recruitment or conditions — now sit inside the same code as the wage machinery, which gives pay-equity questions statutory teeth and makes structure-level consistency (bands, not bespoke deals) the defensible design.
The honest state of the rollout
Between enactment and full state-level operationalisation sits a long, uneven middle; some states have notified rules, others draft, and the effective dates differ by provision. This creates a tempting gap: 'not yet notified here' as a reason to defer redesign. The gap is a trap. The definitions are public, the direction is settled, and structures take a full cycle to redesign cleanly, so establishments that align now convert a future compliance scramble into a past decision. Verify the current status for your states with your consultant; design as if the Code governs, because functionally, it already does.
Where disputes will move under the Code
The old wage laws generated disputes about applicability, which act covered whom. The Code's universality moves disputes to computation: was the wage definition met, was the floor applied to this category, was the exit paid on time. That shift favours employers with arithmetic trails and punishes those with assertions, a labour officer who can be answered with a computation log is a short meeting. Build for the computation dispute, because the applicability dispute is gone.
How payroll software applies this
PeopleDeck's structures make the Code's arithmetic visible: component composition against the 50% test, wage floors checked at computation for every category, payment calendars aligned to the notified cycles, and the registers and wage slips the framework expects generated from each approved run. Definition changes and state notifications land as effect-dated configuration: applied forward, with history preserved under the rules that governed it.
Go deeper: Labour law compliance · Salary structure · Statutory compliance
Primary sources: Ministry of Labour & Employment · India Code — Code on Wages 2019
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
Is the Code on Wages in force?
Enacted and operational in the framework sense, with rules rolling out across central and state jurisdictions on their own timelines. The compliant posture is to treat its definitions (especially the 50% wage rule) as the design standard now, and verify your states' notification status with your consultant at each structural decision.
What does the Code change about minimum wages?
It universalises them (every employee, not just scheduled employments) and layers a central floor wage under state-notified rates, which continue to vary by state, skill category and employment. States still notify and revise the operative numbers; see the minimum-wages guide for how to track them.
What are the timely-payment rules?
Wage periods and payment deadlines by cycle — monthly-paid employees within the notified days of month-end, and prompt settlement on exit, commonly read as two days for wages where rules are in force. The exit timeline is the one that changes FnF practice most.
Does the 50% rule increase my PF cost?
For employees whose PF computes on the ₹15,000 ceiling, nothing changes: the ceiling binds anyway. For above-ceiling structures contributing on actuals, and for gratuity and encashment (no ceiling), a raised wage base means raised outflow, which is precisely why structures got redesigned rather than merely relabelled.
What happened to the Payment of Bonus Act?
Its machinery lives inside the Code: bonus eligibility and computation thresholds continue per the wage definitions and notified limits. Establishments running statutory bonus should map their computation to the Code's terms as their states operationalise.
What records does the Code expect?
Registers of wages, attendance and deductions, wage slips issued, and the trail that shows floors and timelines were met — consolidated and simplified versus the old four-act paperwork, but expected consistently. Electronic records and slips are the standard.
Does the Code apply to small establishments?
Its wage and payment provisions are universal, no headcount floor exempts an employer from minimum wages or timely payment. Some machinery (bonus thresholds, registers' granularity) scales with size, but the core duties arrive with the first employee, which is precisely what 'universalisation' meant.
Structures that meet the definition, every month.
Applied on every payslip, files generated for upload — per employee, per month.
Start free