By CA Surekha Ahuja
For HR heads, CFOs and manpower companies, a routine payroll change has quietly become a P&L question. “The most expensive labour cost is not the one you fail to calculate. It is the one you calculate correctly — but fail to price.”
The shortcut everyone trusted
For years, payroll operated on a familiar rule:
Overtime → PF: No
Overtime → ESI: Yes
Under the earlier separate PF and ESI frameworks, that treatment had a sound legal basis.
The Labour Codes have not simply reversed this rule. They have made it insufficient.
The Code on Social Security, 2020 excludes overtime allowance from “wages”. But that exclusion operates within the 50% mechanism: where specified exclusions exceed 50% of remuneration, the excess is added back.
The Ministry of Labour’s 16 March 2026 Additional FAQs clarify that overtime allowance is included while applying this 50% test. So the new payroll logic is:
Exclude → 50% test → Add-back, if applicable → Final statutory wage
That is the real change.
One employee. One salary. Different economics.
Consider:
| Component | ₹ |
|---|---|
| Basic + DA | 12,000 |
| HRA | 7,000 |
| Other allowance | 5,000 |
| Overtime | 6,000 |
| Total remuneration | 30,000 |
Specified exclusions = ₹18,000
50% of remuneration = ₹15,000
Excess = ₹3,000
Illustrative statutory wage:
₹12,000 + ₹3,000 = ₹15,000
The ₹3,000 is not simply “PF on overtime”. It is the add-back triggered because specified exclusions crossed the 50% threshold.
Actual PF/ESI impact will depend on the applicable provisions, coverage, contribution rules and limits.
But the management lesson is bigger:
Gross remuneration ≠ statutory wage ≠ fully loaded employer cost
Two employees earning the same ₹30,000 can therefore have different employment economics depending on their pay structure.
Salary structure has become a cost-engineering issue.
From payroll line to P&L line
Assume an illustrative additional employer cost of just ₹500 per affected employee per month.
- 1,000 employees → ₹5 lakh/month
- 10,000 employees → ₹50 lakh/month
- 10,000 employees → ₹6 crore/year
At scale, a payroll calculation becomes a P&L calculation.
And for manpower companies, it becomes a pricing problem.
Manpower companies sell labour - they do not merely consume it
A normal employer absorbs employment cost:
Employee cost → Business cost
A manpower company operates differently:
Employee cost + statutory cost + overheads + margin = Client price
If cost rises but price does not, only three things can happen:
Client pays more.
Margin falls.
Contract is renegotiated.
There is no economic fourth option. This creates an important distinction:
A company can be fully payroll-compliant and still be commercially underpriced.
The payroll may be correct. The contract may still be wrong.
The “overtime at actuals” trap
A staffing contract may say: “Overtime shall be reimbursed at actuals.”
But actuals of what?
- OT paid to the employee?
- OT plus statutory cost?
- Fully loaded OT cost?
- Additional cost arising from the wage calculation?
If the contract does not define this, the company may recover the visible overtime payment while absorbing the statutory shadow cost.
That is margin leakage with a compliant paper trail.
The same analysis should be applied to minimum-wage revisions and other statutory cost changes.
For manpower companies:
A change-in-law clause is a margin-protection mechanism, not boilerplate.
The ₹500 → ₹1.80 crore problem
₹500 × 10,000 employees × 12 months × 3 years = ₹1.80 crore
If that cost is not contractually recoverable, it can come directly out of margin.
Not because the company failed compliance.
Because it priced labour using yesterday’s cost.
The bigger question: why is overtime being bought?
If a client consistently requires heavy overtime, do not ask only: “What does OT cost?”
Ask: “Why is the client buying overtime instead of additional capacity?”
Compare the fully loaded economics of:
Overtime vs additional headcount vs additional shift vs productivity improvement.
This moves the discussion from payroll to workforce economics.
And it changes the KPI.
Cost per employee is not enough.
For labour-intensive businesses, the better measure is:
Fully loaded cost per productive hour
For manpower companies:
Fully loaded cost per billable hour
The employee is the resource. The hour is the economic unit.
Who needs to do what?
| Function | New management question |
|---|---|
| HR | Is the Basic-versus-allowance structure still appropriate? |
| Payroll | Does the system correctly perform the 50% test and add-back? |
| Finance | What is the annualised cost by employee, location and client? |
| CFO | What happens to EBITDA and margin? |
| Commercial | Which contracts permit cost recovery? |
| Legal | Does the change-in-law clause cover wage-definition changes? |
| Operations | Is recurring OT cheaper than additional capacity? |
| CEO/Promoter | Has the economics of existing contracts changed? |
The implementation checklist
For HR / Finance - Total remuneration → exclusions → OT included in 50% test → add-back → final statutory wage → applicable PF/ESI → fully loaded cost
Then roll it up: Employee → Department → Location → Business → Client → Contract
That is where a small employee-level impact becomes a material commercial exposure.
For manpower companies
Review every major contract for:
- change-in-law protection;
- wage-definition changes;
- statutory cost recovery;
- minimum-wage revisions;
- OT reimbursement;
- rate-revision mechanisms;
- client-wise fully loaded margin.
The question is not: “Is overtime reimbursed?”
It is: “Is the full economic cost of overtime recoverable?”
The question to ask your payroll vendor
Do not ask: “Have you updated the overtime rule?”
Ask: “Show me an employee with high overtime and allowances. Show me the exclusions, 50% test, add-back, contribution calculation and finally the fully loaded employer cost.”
That final number belongs before the CFO and commercial team.
The real change
The old model was: Employee → Payroll → Compliance
The new management model needs to be:
WAGE → COST → HOUR → PRICE → CONTRACT → MARGIN → PROFIT
The Labour Codes may have changed a wage formula.
But its commercial impact can travel through salary structures, employment costs, billing rates, contracts and margins.
So the question is no longer simply: “Is overtime subject to PF or ESI?”
It is: “What does one hour of labour really cost — and are we still selling it at the right price?”
For HR, it is a cost question.
For Payroll, a calculation question.
For Finance, a forecasting question.
For the CFO, a margin question.
For Commercial, a pricing question.
For Legal, a contract question.
For a manpower company, a business-model question.
And for the promoter: A profitability question -The most expensive mistake may not be getting overtime wrong.
It may be: SELLING LABOUR TODAY AT A PRICE CALCULATED ON YESTERDAY’S COST.
That is where compliance ends — and commercial intelligence begins.
Figures are illustrative. Actual statutory impact depends on the applicable provisions, remuneration structure, PF/ESI coverage, contribution rules, statutory limits and other relevant facts. Payroll configuration, remuneration restructuring and contractual recovery should be validated before implementation.
