A manufacturing company in Faridabad with 85 workers received a Section 7A inquiry notice from EPFO in September 2024. The inquiry covered a three-year period. The core issue was simple: the company had been calculating PF on basic salary only not on basic plus HRA, as the EPFO enforcement officer argued was correct given the salary structure. The workers’ basic salary was set at a figure well below 50% of their total CTC, with HRA making up the balance. EPFO treated the HRA as an allowance forming part of basic wages for PF purposes, and calculated a demand accordingly. By the time the inquiry concluded, the demand covered three years of shortfall in contributions plus interest at 12% per annum under Section 7Q, plus damages at 25% of the arrears under Section 14B because the default exceeded six months. The total demand ran into several lakhs. The company had been paying PF every month, on time, without missing a single challan. They were not negligent. They were simply calculating incorrectly and they did not know it.
This is how PF and ESI compliance mistakes actually work in India. They are rarely dramatic failures of intent. They are quiet structural errors — a wage base calculated incorrectly, a new employee not registered within the prescribed window, a salary structure not updated after the Code on Wages came into force — that accumulate silently for months or years until an enforcement action makes them visible all at once.
This article covers the twelve most common PF and ESI compliance mistakes Indian employers make, the exact penalty that each one attracts, and what correct practice looks like for each. Read it as a compliance self-audit. Mark every mistake that applies to your current payroll setup. The score at the end will tell you what to do next.
Already concerned about your PF and ESI compliance?
Futurex provides a free PF and ESI compliance audit we review your wage base calculations, employee coverage, filing history, salary structure compliance, and identify every gap before EPFO or ESIC does. No commitment required.
What This Guide Covers
The PF penalty structure: exactly what each violation costs
The ESIC penalty structure: exactly what each violation costs
Mistake 1: Calculating PF on basic salary alone — ignoring allowances
Mistake 2: Not registering new employees within the prescribed window
Mistake 3: Keeping basic salary below 50% of CTC to reduce PF liability
Mistake 4: Excluding contract workers from PF and ESIC coverage
Mistake 5: Not updating employee wages in the ECR when salary revises
Mistake 6: Treating the ESIC wage ceiling as a reason not to register
Mistake 7: Not filing ESIC half-yearly returns on time
Mistake 8: Incorrect employee and employer contribution rate calculation
Mistake 9: PF non-deduction for employees who “opted out” without correct documentation
Mistake 10: Not maintaining prescribed registers and records
Mistake 11: Not registering when the threshold is crossed
Mistake 12: Ignoring ex-parte orders — the most expensive mistake
How Futurex manages PF and ESI compliance
The Penalty Structure: What PF and ESI Violations Actually Cost
Before going through the individual mistakes, understand the penalty framework. Many employers underestimate the cost of PF and ESI defaults because they think of the delay interest as a minor addition. The full penalty structure is more severe and more cumulative than most realise.
PF Penalty Framework Under the EPF Act, 1952
| Provision | Violation | Penalty / Consequence |
|---|---|---|
| Section 7Q | Late or short payment of PF contributions | Interest at 12% per annum from due date to actual payment date — calculated daily |
| Section 14B | Delayed payment of contributions damages levied on the principal arrear | 5% (up to 2 months delay), 10% (2–4 months), 15% (4–6 months), 25% (over 6 months) of arrears |
| Section 14(1A) | Default in payment of contributions criminal prosecution | Imprisonment up to 3 years + fine up to Rs. 10,000. Minimum 1 year imprisonment for repeat default. |
| Section 8F | Non-payment after demand notice | Recovery as land revenue attachment of bank accounts, immovable property, and movable assets |
| Section 7A | Quasi-judicial inquiry ex-parte order if employer does not appear | Demand determined solely on EPFO’s assessment — consistently higher than contested proceedings |
ESIC Penalty Framework Under the ESI Act, 1948
| Provision | Violation | Penalty / Consequence |
|---|---|---|
| Section 85(a) | Failure to register under the ESI Act | Fine up to Rs. 5,000 per day of default during which the offence continues |
| Section 85(b) | Failure to pay contributions | Interest at 12% per annum + additional penalty equal to the amount of contribution in arrear |
| Section 85(g) | Obstructing an inspector, failure to produce records | Imprisonment up to 2 years + fine up to Rs. 5,000 |
| Section 85(i) | Repeat offence after conviction | Imprisonment up to 5 years + fine up to Rs. 25,000 |
The Compounding Effect: Why Small Errors Become Large Demands
Most PF and ESI demands are not the result of recent errors — they are the accumulation of a small, consistent error repeated across dozens of employees over years. A contribution calculated on a slightly incorrect wage base, multiplied by 80 employees, across 36 months, plus 12% interest per annum, plus 25% damages — the final demand bears no resemblance to the small monthly discrepancy that caused it. This is why early detection and correction is always significantly cheaper than enforcement-triggered remediation.
The 12 Most Costly PF and ESI Compliance Mistakes
Calculating PF on Basic Salary Alone — Ignoring Allowances That Form Part of Basic Wages
Most Common. Most Expensive. Least Understood.
The EPF Act defines “basic wages” as all emoluments earned by an employee while on duty excluding HRA, overtime allowance, bonus, commission, and allowances that do not form part of basic wages. The critical phrase is “that do not form part of basic wages.” EPFO enforcement officers consistently argue and courts have upheld that allowances which are paid universally to all employees, which do not vary based on individual performance or circumstance, and which are not genuinely related to the purpose they claim, are part of basic wages for PF purposes.
The Supreme Court’s 2019 judgment in the Surya Roshni case and the subsequent Regional Provident Fund Commissioner v. Vivekananda Vidyamandir judgment established that allowances paid uniformly and universally to all employees must be included in the PF wage base unless they are genuinely special allowances tied to specific work conditions. An HRA paid identically to every employee regardless of whether they actually rent accommodation, or a “special allowance” that is simply the residual component after setting basic to a minimum — both are vulnerable to being treated as part of basic wages.
Penalty exposure:
Three years of PF shortfall on the incorrect wage base for all covered employees, plus 12% interest per annum under Section 7Q, plus 25% damages under Section 14B for defaults exceeding six months. For a business with 80 employees, this demand can reach several lakhs within three years.
Correct practice:
Review every salary component with a compliance specialist. Allowances that are universal, unconditional, and bear no genuine connection to the purpose they claim should be included in the PF wage base. The Code on Wages 2019 — effective November 2025 — now requires basic salary to be at least 50% of CTC, which further constrains the ability to use allowances to reduce the PF base below a defensible level.
Not Registering New Employees on the EPFO and ESIC Portals Within the Prescribed Window
Every Day of Delay Is a Day of Default
When a new employee joins, the employer must register them on the EPFO Unified Portal and generate their UAN within 30 days of joining. For ESIC, the new employee must be registered and issued an insurance number within 10 days of joining. These timelines are statutory — they are not administrative targets that can be addressed at the next convenient payroll processing date.
In practice, many businesses register new employees at month-end when the payroll run happens. An employee who joins on the 3rd of the month is registered on the 31st — a 28-day delay. For ESIC, that 28-day delay exceeds the 10-day registration window for the entire month. Across a growing business with frequent new joiners, the cumulative registration delays create a pattern of non-compliance that surfaces in an ESIC inspection as a consistent failure to register covered employees on time.
Penalty exposure:
For ESIC: Rs. 5,000 per day of default during which the unregistered employee remained unregistered under Section 85(a). For PF: the employer carries PF contribution liability from the date the employee joined, not the date they were registered — creating arrears for the gap period.
Correct practice:
Register new employees on both portals within their first week of joining. For ESIC, do not wait for the payroll cut-off. Registration and payroll processing are two separate actions that must run on separate timelines. Build a new joiner checklist that includes EPFO UAN generation and ESIC IP registration as Day 1 actions.
Keeping Basic Salary Below 50% of CTC Specifically to Reduce PF Liability
Now a Statutory Violation Under the Code on Wages 2019
For years, many Indian employers structured salary packages with a very low basic component — sometimes as low as 25% to 30% of total CTC — specifically to minimise PF contributions. Since PF is calculated as a percentage of basic plus DA, a lower basic means lower PF deductions from both the employee and the employer. The practice was widespread, and while EPFO pushed back on it through the allowance-inclusion argument, it was not explicitly prohibited by a single clear statutory provision.
That changed with the Code on Wages 2019, which took effect on 21 November 2025. Under the Code, the definition of “wages” requires that the total of exclusions from wages — allowances, HRA, bonuses, and similar components — cannot exceed 50% of total remuneration. In practical terms, this means basic salary must constitute at least 50% of the total CTC. A business with a 30% basic structure is now in direct statutory violation of the Code on Wages. Every month that passes without restructuring creates fresh non-compliance.
Penalty exposure:
Violation of the Code on Wages attracts a fine up to Rs. 50,000 for the first offence and up to Rs. 1 lakh for subsequent offences. Additionally, EPFO will use the correct wage base to recalculate PF contributions from November 2025, creating arrears for the gap between what was contributed and what should have been contributed.
Correct practice:
Immediately review every salary structure in the business. Any structure where basic salary is below 50% of gross CTC must be revised. The revision will increase PF contributions for both employer and employee — factor this into payroll budgets. Issue revised appointment letters or salary revision letters to all affected employees.
Excluding Contract Workers from PF and ESIC Coverage
The Principal Employer’s Liability Does Not End With the Contractor
Many businesses believe that contract workers housekeeping staff, security guards, delivery personnel, production line workers deployed through a contractor are not their compliance responsibility. The contractor is the employer, so the contractor handles PF and ESIC. This understanding is legally incorrect and regularly leads to enforcement action against the principal employer.
Under the Contract Labour (Regulation and Abolition) Act, and consistently upheld through EPFO enforcement practice, the principal employer carries ultimate liability for PF contributions of contract workers deployed on their premises if the contractor fails to make those contributions. EPFO enforcement officers during Section 7A inquiries routinely examine the total workforce on the employer’s premises — not just the direct employees on the payroll. Contract workers who are regularly working at the premises and who have a stable employment relationship are treated as employees for PF purposes if their arrangement is found to be a sham contracting arrangement rather than genuine outsourcing.
Penalty exposure:
PF and ESIC contributions for all contract workers found to be effectively employed by the principal employer — calculated from the start of the contracting arrangement — plus interest and damages. In businesses with large contract workforces, this demand can be significantly larger than the demand for direct employees.
Correct practice:
Verify that your contractors are depositing PF and ESIC for all workers deployed at your premises. Obtain monthly ECR acknowledgements and ESIC challan receipts from your contractors as a contractual condition. If a contractor is not making contributions, step in as the principal employer and make them — recovering from the contractor’s invoices.
Not Updating Employee Wages in the ECR After a Salary Revision
Old Wage = Wrong Contribution = Arrear Accumulating Every Month
When an employee receives a salary increment, the PF contribution must be calculated on the new, higher basic salary from the month the increment takes effect. If the payroll system or the ECR filing continues to show the old salary — because the salary master was not updated, or the revision was processed late — the PF contribution is calculated on the old base. The difference between the old and new contribution accumulates as an arrear every month until it is corrected.
This error is particularly common during the April increment cycle, when large numbers of employees receive revised salaries simultaneously. Payroll teams processing hundreds of revisions often miss individual employees, particularly those joining mid-year, those on variable pay, or those in departments where increment communications were delayed. The EPFO portal’s ECR data is compared against payroll data during inspections — wage discrepancies between successive months without a corresponding event (like a new joiner or exit) are flagged.
Correct practice:
After every increment cycle, reconcile the payroll system’s salary master against the previous month’s ECR. Every employee whose salary changed should show a corresponding change in the ECR. Run this reconciliation before closing the payroll for the increment month — not after filing.
Treating the ESIC Wage Ceiling as a Reason Not to Register Employees Above It
Coverage and Contribution Ceiling Are Two Different Things
ESIC coverage applies to employees earning up to Rs. 21,000 per month in gross wages (Rs. 25,000 for persons with disabilities). Many employers interpret this as follows: employees earning above Rs. 21,000 are not ESIC-covered and therefore do not need to be registered. This interpretation contains a critical error — the ESIC wage ceiling governs contribution eligibility at the current point in time, not the registration obligation across the employment period.
An employee who joins at Rs. 18,000 per month is covered by ESIC and must be registered. If their salary increases to Rs. 22,000 during the contribution period, they remain covered for the rest of that six-monthly contribution period. Their ESIC registration and contribution continue until the end of the contribution period even though their wage has exceeded the ceiling. Employers who stop ESIC contributions mid-contribution period when an employee’s salary crosses the ceiling are in default for those months.
Correct practice:
Register all employees earning up to Rs. 21,000 gross. When an employee’s salary exceeds the ceiling during a contribution period (April to September or October to March), continue ESIC until the period ends. From the next contribution period, the employee exits ESIC coverage. Document the exit clearly in the ESIC portal and retain records.
Missing the ESIC Half-Yearly Return Deadlines — Both of Them
Monthly Challans Are Not a Substitute for Half-Yearly Returns
ESIC-registered employers must file two half-yearly returns every year in addition to making monthly challan payments. The return covering the April to September contribution period is due by 11 October. The return covering the October to March contribution period is due by 11 April. These returns contain employee-wise contribution details for the entire six-month period and must be filed on the ESIC portal.
Many employers who make monthly ESIC challans diligently — and who therefore believe their ESIC compliance is complete — do not file the half-yearly returns. They assume that the monthly challan data automatically fulfils the return requirement. It does not. The challan payment and the return filing are two separate obligations. An employer who is current on challan payments but has not filed the half-yearly returns is technically non-compliant on the return filing obligation.
Penalty exposure:
Fine under Section 85(g) of the ESI Act for failure to furnish returns — up to Rs. 5,000. Additionally, ESIC inspectors treat missing returns as a signal of broader compliance gaps, often triggering a full inspection of contribution records.
Correct practice:
Add 11 October and 11 April to your compliance calendar as firm deadlines with a 30-day advance reminder. File the half-yearly return with employee-wise contribution data immediately after the challan for the last month of the contribution period is confirmed. The complete compliance calendar for Indian employers has both ESIC return deadlines prominently marked.
Using Incorrect Contribution Rates for PF or ESIC
One Wrong Rate Applied to Every Employee Every Month
The current PF contribution rates are 12% of basic plus DA from the employee, and 12% from the employer — of which 8.33% goes to the Employee Pension Scheme and 3.67% to the EPF account (for employees earning above Rs. 15,000 basic per month, the EPS contribution is capped at Rs. 1,250 per month and the remaining employer share goes to EPF). The ESIC contribution rates are 0.75% from the employee and 3.25% from the employer on gross wages.
Errors in applying these rates — using 12% for ESIC, confusing the EPS cap with the total PF cap, applying the reduced PF rate for sick industries to a healthy business, or failing to update when government revisions change the rates — create systematic under-contribution. Every month the wrong rate is applied, the arrear grows. The employer also deducts the wrong amount from employee salaries, which cannot be recovered retroactively without employee consent and EPFO coordination.
Correct practice:
Verify the contribution rates in your payroll software against the current EPFO and ESIC portal guidelines at least once per financial year. Do not assume that the rates in a system configured years ago are still current. When ESIC reduced the employer rate from 4% to 3.25% and employee rate from 1.75% to 0.75% in 2019, many payroll systems were not updated promptly and some businesses were over-deducting for months.
Not Deducting PF for Employees Who “Opted Out” — Without Proper Documentation
A Verbal Opt-Out Is Not a Legal Opt-Out
Under the EPF Act, an employee whose basic salary exceeds Rs. 15,000 per month is not automatically excluded from PF. They may choose to opt out of PF coverage if they are joining the PF scheme for the first time at that salary level — but this opt-out requires a written declaration in Form 11. An employer who does not deduct PF for a high-salary employee based on a verbal statement or an assumption that “they don’t want PF” is taking a risk that EPFO does not accept.
If EPFO later conducts a Section 7A inquiry and finds that PF was not deducted for an employee, the employer must produce a correctly completed Form 11 signed by that employee as evidence of the opt-out. Without it, EPFO treats the non-deduction as a default. The employer owes both the employee share and the employer share of PF for every month the employee worked without a valid Form 11.
Correct practice:
Collect Form 11 from every new employee at joining, regardless of salary level. For employees above Rs. 15,000 basic who choose to opt out, retain the signed Form 11 in their personnel file. For employees who were members of PF at a previous employer, they remain covered even above the Rs. 15,000 threshold Form 11 documents whether they were a previous member and what their choice is.
Not Maintaining Prescribed Registers and Records — or Maintaining Them Incorrectly
Absence of Records = Presumption of Non-Compliance
The EPF Act and ESI Act both require employers to maintain specific registers: the Register of Employees (showing name, father’s name, UAN, date of joining, wages, PF contribution), the Register of Contributions (monthly deductions, contributions, and challans), the Inspection Book (for inspector visits), and the Register of Damages (if any). These must be maintained in the prescribed format, kept current, and produced for inspection on demand.
Many businesses maintain informal records a spreadsheet here, an email trail there but do not maintain the specific statutory registers in the prescribed format. When a labour inspector or EPFO enforcement officer visits and asks for these registers, an inability to produce them in the correct format is treated as a failure to maintain records which attracts separate penalties under the relevant Act, independent of any compliance issues found in the inspection itself.
Correct practice:
Maintain all prescribed registers in digital format where the law permits (both EPF and ESI now accept digitally maintained records with appropriate access controls and audit trails). Verify the format against the current statutory requirements at least annually. When an inspector visits, produce registers promptly and completely delays or excuses attract suspicion that often leads to broader inquiries.
Not Registering for PF and ESIC When the Threshold Is Crossed
Liability Begins on the Date the Threshold Is Crossed Not the Registration Date
PF registration is mandatory for establishments employing 20 or more persons. ESIC registration is mandatory for establishments employing 10 or more persons. The obligation arises from the moment the threshold is crossed not from the date of registration. A business that crosses 20 employees in March and registers for PF in June has a PF contribution liability from March, not June.
Fast-growing businesses cross these thresholds without noticing, particularly when headcount growth includes contract staff, part-time workers, or seasonal employees. EPFO’s enforcement approach is to calculate contributions from the date the threshold was crossed — based on payroll records, attendance registers, and bank payment evidence and raise a demand for the entire period between threshold crossing and registration, plus interest and damages.
Correct practice:
Monitor headcount proactively not just permanent employees, but all workers whose presence on your premises is regular and ongoing. Build a threshold alert into your HR system: when total headcount approaches 10 or 20, initiate the ESIC and PF registration process immediately rather than waiting until after the threshold is crossed. Registration takes time; start it before you need it.
Ignoring a Section 7A Notice — Allowing an Ex-Parte Order to Pass
The Single Most Expensive Mistake. No Close Second.
When EPFO issues a Section 7A notice, it sets a hearing date before the Provident Fund Commissioner. The notice requires the employer to appear, produce documents, and present their position on the wage base and coverage questions. Section 7A(3A) of the EPF Act provides that if the employer does not appear at the hearing without sufficient cause, the commissioner may determine the amount due on the basis of the evidence available to them — without any input from the employer.
Ex-parte orders under Section 7A are consistently and significantly more unfavourable than orders reached after contested proceedings. Without the employer’s payroll data, actual wage registers, and documented coverage decisions, the commissioner calculates the demand based on EPFO’s own assumptions — typically using maximum possible wages and maximum possible coverage. The result is almost always a demand that substantially overstates the actual liability, plus full interest and damages because there was no mitigation evidence presented.
Setting aside an ex-parte order is possible under Section 7A(4), an employer can apply to have it set aside within three months — but the bar is high. The employer must demonstrate either that the notice was not properly served or that there was sufficient cause for the non-appearance. Simply being unaware of the notice, or having misaddressed correspondence, has not consistently been accepted as sufficient cause.
Correct practice:
Respond to every Section 7A notice. If the hearing date is inconvenient or you need time to gather documents, file a written adjournment request before the hearing date not after. Attend every hearing with complete payroll records, wage registers, ECR filings, and any other documentation relevant to the wage base and coverage questions. Professional representation at Section 7A hearings consistently produces better outcomes than self-representation.
For a complete guide on how to respond to labour law notices and Section 7A inquiries, see our detailed notice response guide.
Your Compliance Self-Audit Score
Count how many of the twelve mistakes above apply to your current payroll setup. Be honest. Many businesses discover mid-way through this exercise that their compliance position is weaker than they had assumed.
| Mistakes Identified | Risk Level | What It Means | Recommended Action |
|---|---|---|---|
| 0 to 1 | Low | Your PF and ESI compliance is well managed. Schedule an annual audit to confirm nothing has slipped. | Annual compliance health check. |
| 2 to 4 | Medium | Compliance gaps exist. Arrears may already be accumulating without your knowledge. Correction before enforcement is still possible. | Compliance audit within 30 days. Corrective action plan with priority ranking. |
| 5 to 8 | High | Significant liability is almost certainly accumulated. The business is vulnerable to a Section 7A inquiry or ESIC inspection producing a large demand. | Immediate compliance audit. Voluntary disclosure and correction before enforcement typically reduces total liability significantly. |
| 9 to 12 | Critical | The PF and ESI compliance function has failed. Undisclosed liability could be substantial. Enforcement action, when it comes, will be severe. | Call for urgent compliance assessment today. Do not wait for a notice to arrive. |
Frequently Asked Questions About PF and ESI Compliance
Can EPFO demand PF contributions for periods more than five years ago?
Under the EPF Act, there is no absolute limitation period on EPFO’s power to inquire under Section 7A. However, EPFO’s 2020 circulars provide that inquiries without evidence of prolonged default should not typically cover periods exceeding five years from the date of notice. In practice, inquiries triggered by specific events worker complaints, inspection findings, or data mismatches — can cover the period of the specific default, which may extend beyond five years if the default has been continuous. Businesses with a long history of incorrect wage base calculations are at risk of demands covering the full period of the error.
Is voluntary disclosure to EPFO of past errors better than waiting for an inspection?
Yes, in almost all cases. Voluntary disclosure before EPFO initiates a Section 7A inquiry allows the employer to control the scope of the assessment, present their own calculation of the arrear, and pay the amount with the minimum applicable interest and damages. An employer who discloses a two-month-old calculation error pays 5% damages under Section 14B. An employer who is found with the same error during a Section 7A inquiry — two years later when the default has aged to over six months pays 25% damages plus the two years of accumulated interest. The difference in total outflow can be several multiples.
We recently discovered we have been calculating PF on a lower wage base for two years. What should we do?
Do not delay. Calculate the shortfall for every month and every employee in the affected period. Determine the principal arrear, the Section 7Q interest at 12% per annum, and the applicable Section 14B damages rate based on the age of the default. Consult a compliance specialist before approaching EPFO the manner of disclosure and the documentation you bring affects the outcome significantly. In most cases, proactive disclosure with a self-calculated arrear and immediate payment is treated more favourably than an arrear discovered during an enforcement inquiry.
Does the 50% basic salary rule under the Code on Wages apply to all businesses?
Yes. The Code on Wages 2019, which came into force on 21 November 2025, applies to every establishment regardless of size, sector, or whether it was previously covered by the Minimum Wages Act, Payment of Wages Act, or Equal Remuneration Act. The requirement that wages as defined under the Code which includes basic salary and certain other components constitute at least 50% of total remuneration applies to every employer in India. There is no exemption based on business size or sector.
Avoid Costly PF and ESI Penalties Let Futurex Manage Your Compliance
The Faridabad manufacturer at the start of this article paid a heavy price for an error that could have been caught in a routine compliance review. Their PF was not missing. Their challans were not late. Their error was a wage base calculation that looked correct on the surface but was not defensible under EPFO scrutiny. By the time the Section 7A inquiry concluded, the demand was several times what a proactive correction would have cost.
Futurex Management Solutions manages complete PF and ESI compliance for businesses across India correct wage base calculation, monthly ECR filings, ESIC challans and half-yearly returns, new employee registrations, register maintenance, salary structure review for Code on Wages compliance, and representation support when notices arrive. Our team actively monitors every regulatory change wage ceiling updates, contribution rate revisions, new EPFO circulars and implements them before they become enforcement issues for our clients.