EPF in 2026: The Compliance Traps Employers Still Don’t See Coming

PF compliance looks easy on a salary sheet. In practice some of the biggest liabilities come from assumptions made at joining, salary structuring, outsourcing and employee history.

By Pratik Vaidya

PF has always had a reputation for being relatively simple. There is a contribution to be made, an employer’s share too, due date and ECR to file. Do all these correctly every month and PF compliance should take care of itself.

I wish it were that simple.

I have been working with establishments on labour compliance for more than 20 years now and some of the harder PF problems don’t start with an employer deciding deliberately not to pay PF. They start with a small assumption.

An employee earning more than ₹15,000 is assumed to be outside PF. A contractor produces a challan and no one looks beyond it. Salary component is called allowance so it’s assumed to be outside PF. Employee doesn’t remember his old UAN so fresh one gets created.

Nothing looks particularly alarming at the time.

The problem comes three or four years later when the same assumption has travelled through payroll on hundreds of employees.

That is why 2026 is a good time to look at PF differently.

The Code on Social Security has been in force since November 21, 2025. Wages definition changed. EPFO systems are getting more connected with Aadhaar and UAN. Employment histories are easier to trace.

What was once buried inside payroll files is now data that can be compared.

And data has a rather inconvenient habit of remembering.

The ₹15,000 misunderstanding

Ask when PF becomes applicable and ₹15,000 will probably be in the conversation very quickly.

The number is what matters. The way it is sometimes understood is the problem.

Let’s say two employees join the same company at ₹40,000 per month. One has never been a PF member; the other worked elsewhere and is already one.

It’s easy to look at their current salaries and treat them all the same. Their PF position doesn’t have to be the same either.

Once an employee gets PF membership, crossing the wage ceiling does not make that membership disappear.

So one seemingly innocuous onboarding question is then extremely important: Have you been a PF member before?

Since UAN creates continuity across employment, employers need to look at an employee’s PF history (not just his current salary).

The allowance problem hasn’t disappeared

There was a time when salary structuring could be something of a naming exercise.

Keep basic salary low and distribute the rest among special allowance, conveyance etc. Anything outside “basic” was then assumed to be outside PF.

The Supreme Court’s 2019 decision in Regional Provident Fund Commissioner (II), West Bengal v. Vivekananda Vidyamandir and the related Surya Roshni matters should have put that simplistic view to rest.

The Court looked at the substance of the payment. An allowance which was ordinarily and uniformly paid could not necessarily escape PF because it had been given another name. Truly variable payments related to particular circumstances were a different matter.

Now we have another shortcut emerging from the Labour Codes: “basic salary has to become 50% of CTC.”

That too is an oversimplification.

The new definition works through inclusions and exclusions. Where specified exclusions exceed the statutory 50% limit then that excess is added back into wages.

That is quite different from opening an Excel sheet and making everyone’s basic salary exactly 50%.

Every salary component still needs to be understood as what it actually is.

The government has also said that the new wage definition can apply to EPF and EPS contributions where excluded allowances cross the permitted threshold.

For employers wage restructuring should not therefore be another game of find a clever salary formula. The structure has to be legally defensible, commercially sensible and understandable to employees.

If it takes three pages to explain why an allowance isn’t wages then there is probably a bigger question that needs to be asked.

“The contractor has a PF code, so we are covered”

This is another conversation I have heard many times before.

A company outsources security, housekeeping, logistics or other manpower. The contractor has PF registration. Every month somebody collects challan. Invoice gets cleared and everyone assumes PF compliance is done.

But what does that challan actually establish?

Let’s say a contractor has 600 employees on ten clients and fifty of them are at your place.

The question is not whether the contractor deposited some PF that month but whether those fifty people show up in ECR, whether their UANs are correct, whether their wages match deployment records and whether contributions were actually deposited for them.

A challan alone is not employee-level compliance verification.

This is why principal employers need stronger contractor governance.

At the same time there is another side to this coin. A principal employer should not automatically become the recovery mechanism whenever an independent contractor defaults. Where the contractor has its own establishment PF registration identifiable employees records etc responsibility has to be determined on facts and law applicable.

Worker protection is non-negotiable. A worker shouldn’t lose PF because two businesses are fighting about responsibility.

But good enforcement should also identify who actually committed the default.

The two principles can coexist.

UAN is no longer just a payroll number

Duplicate UANs were once largely viewed as an administrative annoyance.

An employee forgot his previous number. Aadhaar details didn’t match. Former employer entered name differently. Someone found it easier to create another record.

The environment around this is changing.

EPFO has been moving UAN generation and activation towards Aadhaar-based Face Authentication through UMANG. PF identity is more and more tied to individual rather than a particular employer’s payroll.

Suppose an employee joins above the wage ceiling and says he has never been a PF member. The employer relies on that declaration.

Years later his employment history proves otherwise.

The question might then not be why two UANs exist. It could be whether PF should have been contributed from his date of joining.

UAN verification should therefore become part of serious employee onboarding, not an exercise undertaken after a problem has arisen.

Employees leave. Old PF mistakes don’t always leave with them.

An employee resigns, full-and-final settlement is done and file is archived.

Operationally the relationship has ended. A statutory liability under that period has not necessarily ended with it.

This gets really tricky when an enquiry comes years later. The HR manager has moved on, the contractor no longer exists, payroll software has changed and nobody remembers why a particular employee was excluded originally.

Meanwhile, the financial exposure continues.

In May 2026 the Central Government notified simple interest @ 12% per annum on amounts due from employers under Code on Social Security with effect from November 21, 2025.

This is what gives PF errors their multiplier effect.

A ₹1000 error does not sound scary. A ₹1000 error repeated monthly over hundreds of employees for several years certainly does.

The enrolment scheme was also a warning

The Employees’ Enrolment Scheme, 2025 gave employers six months (from November 1, 2025 to April 30, 2026) to bring certain previously omitted employees into PF coverage voluntarily subject to its conditions.

The window has closed but its existence tells us something.

Employees have been left outside PF across establishments because of incorrect classification, old practices, misunderstanding eligibility; contractor failures and in some cases deliberate non-compliance.

Employers who did not use the scheme should not assume that the underlying issue disappeared when the scheme ended.

It may be a good reason instead to look back.

Take a few historical payroll periods. Compare joining records with UANs. Look at employees treated as excluded. Take contractor deployment sheets and match employee by employee with ECR.

That exercise may tell you more than another compliance checklist.

PF isn’t only payroll’s responsibility

Perhaps this is where organisations make their biggest mistake.

Payroll deposits PF so PF becomes payroll department’s job.

But HR gathers info on previous employment. Compensation teams create salary structures. Procurement hires contractors. Ops confirms manpower deployment. Finance releases payments to contractors.

Payroll can therefore calculate everything perfectly on information that was wrong to begin with.

You can have a perfectly filed ECR and still have a PF problem.

If you have multiple locations (especially if outsourced manpower is involved) then reconciliation should become routine. Payroll, UAN records, employee masters, contractor deployment and ECR data should all tell the same story.

Where they don’t, somebody should ask why.

Preferably before EPFO does.

The next PF inspection may not begin with an inspector

This may ultimately be the biggest change.

India’s labour-compliance system was based on registers, returns and physical inspections. An officer asked for documents and discrepancies were found by looking at them.

More and more those records are already there electronically.

Employees have portable UANs. Identity is linked via Aadhaar. Contributions are electronic. Employment histories travel with individuals. Contractor information can be increasingly linked to principal employers.

Once information is structured data comparison becomes much easier.

The next PF query may therefore start not with an inspector entering the factory gate but two databases telling different stories about the same employee.

That is not necessarily a bad development.

Technology can make it much harder for a genuine worker to lose years of retirement savings because an employer or contractor didn’t enrol him.

But digitisation also needs administrative fairness. A data mismatch is something that needs looking at; it shouldn’t automatically become evidence of evasion. Employers need practical ways to correct genuine historical errors.

India needs stronger social-security compliance and sensible enforcement. They are not contradictory.

The real challenge

For years the PF compliance question was Have we deposited PF this month?

That question is no longer enough.

Employers now have to ask: Are we covering the right people? Are we contributing on the right wages? Did we check previous PF membership? Are contract workers appearing in deployment records as well as ECRs? Can we still explain decisions made three years ago?

For MSMEs it’s even more so. Smaller businesses don’t always have separate legal, HR payroll and compliance teams — what a large corporation can take in layers of advisers becomes a burden for a 100 employee enterprise.

The success of India’s social-security reforms therefore cannot be measured solely by how much additional PF is collected.

Compliance should become easier to understand, harder to evade and simpler to correct when a genuine mistake occurs.

The Labour Codes and EPFO’s digital transformation give India an opportunity to move in that direction.

Employers, in turn, need to move beyond the monthly challan and examine the information sitting behind it.

Because the most expensive PF problem in 2026 may not be a contribution an employer knowingly refused to pay.

It may be an assumption nobody thought to question.

────────

About the Author

Pratik Vaidya is Head & Convenor – HR, Compliance & Labour Committee, India SME Forum, and a National Executive Council Member of the Indo-American Chamber of Commerce (IACC). He is the Managing Director & Chief Visionary Officer of Karma Management Global Consulting Solutions Pvt. Ltd. (Karma Global).

With over two decades of experience in labour-law compliance, employment governance and workforce advisory, his work spans labour compliance, payroll governance, statutory audits, inspections and contractor compliance across India. He is also actively involved in using technology and AI to simplify labour-law compliance and make it more practical and accessible, particularly for MSMEs.

The views expressed are personal. This article is intended for general information and discussion and should not be construed as legal advice.