Home Why Navora HR
Features Pricing About Blog
Get Started Free → No credit card · 14-day free trial
Compliance · 13 min read

Payroll Compliance Challenges Indian Businesses Face

Indian payroll broke in a specific way this year, and most teams haven't noticed. Two labour-law regimes and a new Income Tax Act went live within months of each other — here are the ten problems employers are actually hitting in 2026.

PS
Written by
Purnav Sawhney
Founder, NavoraHR
Aug 26, 2026

Indian payroll broke in a specific way this year, and most teams have not noticed yet.

The rules did not just change. Two sets of rules went live at once, and neither fully replaced the other.

The short answer

Payroll compliance in India means calculating and depositing provident fund, employees' state insurance, professional tax, labour welfare fund and tax on salary correctly, to five different authorities, on five different calendars. The hard part is not the arithmetic. It is that the inputs keep moving.

These are the ten problems Indian employers are hitting in 2026:

  • Two labour law regimes running at once
  • The 50% wage rule reset your statutory cost base
  • A new Income Tax Act arrived mid-cycle, with new forms
  • ESI is a timing rule that teams treat as a percentage
  • PF calculated on the wrong wage base
  • State fragmentation across professional tax, welfare fund and minimum wages
  • Attendance and leave data arriving as spreadsheets
  • Exit settlements calculated on retired assumptions
  • Payroll data became regulated data
  • Records that cannot survive an inspection

A capable payroll management system india employers can rely on solves seven of these outright. The other three are process problems that no software fixes on its own. This post is honest about which is which.

If you need the underlying rates, thresholds and filing calendar rather than the failure modes, our guide to PF, ESI and TDS compliance covers those in detail. What follows is what goes wrong in practice.

Why 2026 is harder than 2025

The four Labour Codes came into force on 21 November 2025, replacing 29 central labour laws. The Central Rules under all four were notified on 8 to 9 May 2026. But labour sits on the Concurrent List, so every state must notify its own rules, and most have not finished. An employer with offices in three states can face three different rule positions under one central law.

Separately, the Income Tax Act, 2025 replaced the Income Tax Act, 1961 from 1 April 2026. Salary TDS, the forms you file and the way tax years are named all changed on the same date.

So a payroll team closing an August 2026 cycle is applying a new tax statute, a new wage definition, central rules that are only three months old and state rules that in many places do not exist yet. That is the actual operating environment. Everything below follows from it.

1. Two labour law regimes running at once

The most common mistake right now is binary thinking. Teams either assume the Codes changed everything or assume nothing is enforceable until their state notifies rules. Both are wrong.

The Codes themselves are law and the repeal of the 29 earlier Acts has taken effect. What is uneven is the layer underneath: registration forms, licence procedures, leave registers, working hour limits and the portals you actually file on. Those come from state rules, and states are at different stages.

Practical position: payroll arithmetic mostly follows the central Codes, because the wage definition, gratuity and bonus calculations sit in the Codes themselves. Filing procedure often still follows legacy state rules.
What it costs: applying a state's draft rules as though they were notified, or ignoring a central change because your state has been quiet.
The fix: assign one named person to track the gazette for every state you employ in. This is not a software problem. No platform reads state gazettes for you, and any vendor claiming otherwise is overselling.

2. The 50% wage rule reset your statutory cost base

The Code on Wages requires basic plus dearness allowance to make up at least half of total remuneration. Most Indian salary structures were deliberately built the opposite way, with a small basic and large allowances, to hold down provident fund and gratuity liability.

That structure no longer works. As basic rises toward half of total pay, the base for provident fund, gratuity, bonus and leave encashment rises with it.

The quiet part: because the EPF ceiling is unchanged, take-home pay often barely moves, so nobody notices. Gratuity and leave encashment liability moves a lot, and it surfaces at exit or at audit.
What it costs: an understated provision that only becomes visible when someone resigns or a diligence process opens the books.
The fix: rerun your salary structures against the 50% floor and reprovision. If your payroll software still computes gratuity on a legacy basic figure, that is a configuration error, not a policy choice.

3. A new Income Tax Act arrived mid-cycle

This is the change most likely to be sitting unhandled in your system right now.

From 1 April 2026, salary TDS moved from Section 192 of the 1961 Act to Section 392 of the Income Tax Act, 2025. Form 16 became Form 130. Form 24Q became Form 138. The Assessment Year concept was removed and replaced by Tax Year, which equals the financial year.

The transition rule is what catches people. The governing law depends on the earlier of credit or payment. If that event falls on or before 31 March 2026, the 1961 Act applies. On or after 1 April 2026, the 2025 Act applies. So the Q4 return for FY 2025-26 still had to go on the old forms with old section codes, even though it was filed well after April.

Section codes: every code was reassigned. Filing a new-year return with old codes triggers validation errors.
Certificate timing: the annual salary TDS certificate is due by 15 June, and late issue attracts ₹100 per day per certificate.
Deposit timing: monthly TDS is due by the 7th of the following month, with March deductions due by 30 April.

What it costs: mismatches that surface in the employee's own tax records, which turns a filing error into a queue of employee complaints. An employee self service ESS portal that lets people pull their own certificate and declaration status absorbs most of that queue, but only if the underlying filing was correct.

The fix: confirm in writing that your payroll software has been updated for the new section codes and form numbers, and reconcile before filing rather than after.

4. ESI is a timing rule that teams treat as a percentage

The rates are easy: 3.25% from the employer and 0.75% from the employee, on gross wages, for employees earning up to ₹21,000 a month, and up to ₹25,000 for employees with disabilities.

The rule that gets missed is not a rate at all. ESI runs in two contribution periods, April to September and October to March. An employee who crosses the wage ceiling partway through a period stays covered until that period ends.

The classic error: stopping the deduction the month the increment lands. That creates a contribution gap that ESIC's own reconciliation flags automatically at the half-yearly return.
Second error: testing eligibility on basic salary instead of gross wages. Gross includes HRA and regular allowances, so an employee with a modest basic can still sit above the ceiling.
What it costs: a systematic monthly shortfall that shows up in every inspection, plus interest and prosecution exposure.
The fix: this one is purely a software test. Give a vendor an employee whose salary crosses ₹21,000 in July and check whether coverage continues to September.

5. PF calculated on the wrong wage base

The provident fund rate is not where teams go wrong. The wage base is.

Provident fund is calculated on basic plus dearness allowance, not gross, and is mandatory up to a wage ceiling of ₹15,000 a month. That ceiling has held since 2014 and remained in place through 2026, despite a Supreme Court direction in January 2026 asking the Centre and EPFO to decide on a revision within four months. Whether your company contributes on the ceiling or on actual basic is a policy choice, and it needs to be documented, because it changes both cost per head and take-home pay.

Layer the 50% wage rule on top and the base moves again.

Deposit deadline: the 15th of the following month.
Late payment: interest under Section 7Q plus damages under Section 14B, which scale from 5% to 25% depending on how long the default runs.
Registration trap: each branch generally needs its own registration, so a three-location company is running three compliance calendars.
The fix: reconcile the ECR against your salary register every cycle, not quarterly. Errors compound because each month's file feeds the next.

6. State fragmentation across professional tax, welfare fund and minimum wages

Professional tax is a state levy under Article 276 of the Constitution, capped at ₹2,500 per person per year. Some states levy it and some do not. Delhi, for instance, does not. Slabs, thresholds and filing frequency differ everywhere it does apply: Karnataka exempts monthly gross below ₹25,000, and Tamil Nadu and Kerala collect half-yearly rather than monthly.

The deadlines move too. Maharashtra shifted its monthly professional tax payment and return to the 15th of the following month following a February 2026 notification. Teams still working off last year's calendar are now filing late without knowing it.

Misapplied rule: professional tax follows the employee's work location, not the company's registered office. A company registered in one state with staff in another owes the second state's tax.
Layer two: labour welfare fund cycles and minimum wage notifications are also state-specific and revised on their own schedules.

This is sharpest in the National Capital Region, where a single company routinely spans three states with three different positions. Our payroll software in Delhi NCR guide works through that case in detail.

The fix: hold state as an attribute of the employee record rather than of the company, so the correct rules apply automatically. Then verify each state's current position against the state gazette rather than a vendor's slab table, because slab tables go stale quietly.

7. Attendance and leave data arriving as spreadsheets

Every payroll error caused by bad input traces back here. Loss of pay, overtime, late marks, comp offs and encashment all originate outside payroll, and if they arrive as a monthly export, someone is reconciling by hand under deadline pressure.

Overtime deserves specific attention this year. Because the wage definition changed, the base your overtime calculates on may have moved. A system still computing on a legacy basic figure understates the liability silently.

Regularisation gap: if corrections happen over email or chat, there is no defensible record of who approved what.
Sync gap: an attendance management system that exports to payroll is not the same as one payroll reads directly.
Policy gap: leave rules that live in a document rather than in leave management software get applied inconsistently by different managers.
The fix: apply two days of loss of pay in a test environment and check whether the salary output changes without a manual sync step. If it does not, you have found your monthly reconciliation.

8. Exit settlements calculated on retired assumptions

Full and final settlement is where every unresolved thing surfaces at once: notice recovery, leave encashment, gratuity, asset clearance, pending claims and final tax.

The Labour Codes changed the arithmetic here. Fixed-term employees now become eligible for gratuity after one year of continuous service rather than the longer qualifying period most policies were written around. Settlement templates built on the old threshold understate what is owed.

Data problem: if leave balances and attendance sit outside payroll, the settlement figure gets calculated manually and disputed later.
Tax problem: the final salary TDS position has to be closed under whichever Act governs the payment date.
The fix: run one resignation end to end through an employee separation management system and check whether any part of the settlement required a manual calculation. Whatever needed a spreadsheet is what will be disputed.

9. Payroll data became regulated data

The DPDP Rules were notified in November 2025, with substantive obligations applying in full from May 2027 and penalties reaching ₹250 crore for failing to maintain reasonable security safeguards. Employee data sits squarely inside scope: salary records, bank details, biometric attendance, health and insurance information.

Payroll is the highest-sensitivity data set most Indian companies hold, and it is often the least controlled. Salary registers circulate as email attachments. Full-access logins get shared during month-end. Ex-employee records sit in folders nobody owns.

Access control: permissions should be granular by role, not a blunt admin or non-admin split.
Audit trail: you need a log showing who viewed or edited a record and when.
Retention: statutory retention obligations under tax and provident fund law override erasure requests, so the policy has to reconcile both.
The fix: treat 2026 as the build year. Map where payroll data currently lives, then reduce the number of places it lives in.

10. Records that cannot survive an inspection

The final challenge is the least discussed. Compliance is not only doing the right thing, it is being able to prove you did it, years later, to an inspector who was not there.

That means salary registers, challans, returns, muster rolls and employee declarations retained for the statutory period, retrievable by employee and by month, and consistent with what was actually filed.

Common failure: the payroll was correct but the evidence is scattered across three former employees' inboxes.
Second failure: the register and the filed return disagree because a correction was made in one and not the other.

A single human resource management software platform holding the employee master, the attendance ledger, the payroll register and the filing history solves this by construction. Assembled stacks solve it only if someone maintains the joins.

Which of these software actually fixes

Being direct about this matters, because vendors are not.

  • Software solves: ESI period logic, provident fund wage-base calculation, state-specific professional tax and welfare fund application, attendance and leave flowing into payroll, exit settlement arithmetic, access control and audit trails, and record retrieval.
  • Software helps: the new Income Tax Act transition, which needs your vendor to have shipped the update and your team to reconcile before filing.
  • Software cannot: tracking state rule notifications under the Labour Codes, deciding your provident fund contribution policy, and reconciling data retention against erasure obligations. Those need a named owner.

Any payroll software india vendor promising full automation of the third group is describing something that does not exist.

Where to start if you are behind

Three checks, in order, each of which takes an afternoon.

  • Wage structures: confirm basic plus dearness allowance meets the 50% floor and that gratuity and encashment are provisioned on the revised base.
  • Tax transition: get written confirmation that your system is updated for the new section codes and form numbers, and reconcile your last filed return.
  • State coverage: list every state you employ in and confirm the current professional tax, welfare fund and minimum wage position for each against the state source.

Closing the gap

Most payroll compliance failures are not caused by teams misunderstanding a rule. They are caused by a correct rule applied to a stale input: last year's slab table, a legacy basic figure, an attendance file that arrived as a spreadsheet.

The fix is structural. Hold the employee record once, let the rules read from it, and make the evidence retrievable afterwards.

Frequently asked questions

What are the main payroll compliance requirements in India?
Indian employers must calculate, deduct, deposit and report provident fund, employees' state insurance, tax on salary, professional tax where the state levies it, and labour welfare fund contributions where applicable. Provident fund and employees' state insurance are due by the 15th of the following month, salary tax by the 7th, and returns run on quarterly and annual cycles. Minimum wages, bonus and gratuity obligations sit alongside these under separate legislation.
What changed for payroll compliance in India in 2026?
Two things, on separate dates. The four Labour Codes took effect on 21 November 2025 and the Central Rules under them were notified on 8 to 9 May 2026, with state rules still being notified unevenly. Separately, the Income Tax Act, 2025 replaced the 1961 Act from 1 April 2026, which changed the section governing salary tax, replaced Form 16 with Form 130 and Form 24Q with Form 138, and replaced the Assessment Year concept with Tax Year.
What happens if PF or ESI is deposited late?
Late provident fund payment attracts interest under Section 7Q along with damages under Section 14B, which scale from 5% for a short default up to 25% for defaults running beyond six months. Employees' state insurance carries interest and prosecution exposure under Section 85. Both are calculated from the due date, so a delay of a few days on a large payroll is not a rounding error.
Does a payroll management system in India handle multi-state compliance?
A capable platform holds the state as an attribute of the employee record, applies the correct professional tax and welfare fund rules by work location, and still produces one consolidated register for finance. What it will not do is track state rule notifications under the Labour Codes for you. Ask any vendor to produce a single payroll register covering employees in two states with different professional tax positions before believing a multi-state claim.
Do we still file Form 24Q and issue Form 16?
Not for periods from April 2026 onward. Form 24Q was replaced by Form 138 as the quarterly salary tax return, and Form 16 was replaced by Form 130 as the annual certificate, from Tax Year 2026-27. Returns covering periods up to 31 March 2026 still use the old forms and old section codes, even if you file them later, because the governing law follows the payment or credit date rather than the filing date.
How long do we need to keep payroll records?
Retention periods are set by the individual statutes rather than by one rule, and provident fund and tax records carry the longest obligations. The practical standard most Indian employers work to is retaining salary registers, challans, returns and employee declarations for at least seven years, retrievable by employee and by month. Note that these statutory retention obligations override an employee's erasure request under the data protection framework.

Bring your own messy month into a trial: the mid-month joiner, the employee whose increment crosses the ESI ceiling, the resignation with pending claims. Start a free trial and check the output against your last manual run before you decide anything.

More from the blog

Compliance

Payroll compliance in India: a 2026 guide to PF, ESI & TDS

Jun 8, 2026 · 9 min read
HR Strategy

15 features every modern HRMS should have

Aug 10, 2026 · 14 min read
Payroll

Why integrated HR & payroll software delivers better business outcomes

Jul 23, 2026 · 11 min read

HR insights, straight to your inbox.

One email a week. No fluff. Unsubscribe anytime.