A 17-Year EPF Enrolment Window Closes 31 October: Run the Audit Before It Becomes an EDLI Claim

The Employees' Enrolment Campaign 2026 came into effect on 29 June 2026 and gives an establishment a one-time route to declare workers who stayed outside EPF coverage at any point between 1 April 2009 and 31 March 2026. That is a seventeen-year lookback, and it closes on 31 October 2026.

The terms are narrow enough to plan around:

• Eligible workers must be alive and in active employment with the establishment on the date of declaration. A worker who has left, or who has died, cannot be regularised through the campaign.
• The employee's share is waived where it was never deducted from wages in the first place. The employer's share still has to be paid.
• Every declared employee needs a UAN generated through face authentication on the UMANG app, and remittance goes through the ECR platform in the normal way.
• Employers have been asked to run internal audits of their own employment and wage records to identify who qualifies.

That last instruction is the part most finance teams skim. It is also the part that decides whether the declaration is complete or whether it leaves a second population sitting outside the net after October.

Enrolling a worker in EPF does not only start a retirement contribution. It brings the Employees' Deposit Linked Insurance (EDLI) scheme with the worker. EDLI is death-in-service cover attached to EPF membership, funded by an employer contribution, and paid to the nominee when a member dies while in employment.

Press reporting on 10 July 2026 confirmed that the EDLI cover of Rs 7 lakh stays in place under the 2026 scheme structure, with a PF-linked assurance benefit of up to Rs 1 lakh introduced alongside it. So the arithmetic of the campaign runs both ways. Declaring two hundred previously unenrolled workers costs the employer's share of past contributions. It also switches on a statutory death benefit for two hundred families that did not have one the day before.

Every risk manager should read that as a signal about their own member data. If two hundred workers were invisible to EPF, ask the obvious follow-up question: were they visible to the group personal accident policy? To the group mediclaim census? To the workmen's compensation declaration? In practice the same population goes missing from all of them, because they enter the establishment through the same door, which is usually a contractor, a manpower agency, a seasonal roster or a probation payroll that sits outside the main HRIS.

The campaign audit is therefore the cheapest member-data reconciliation an employer will ever run, because someone else has already mandated it and given it a deadline.

Build one worker-level table and pull four sources into it. Match on a stable key, ideally Aadhaar-seeded UAN where it exists, and on name plus date of birth plus date of joining where it does not.

1. Payroll and wage registers, including the contractor wage registers you receive as principal employer, muster rolls, and any payment made against a labour bill rather than a salary run.
2. EPF member data, taken from the ECR filings and the establishment's member list rather than from memory.
3. ESIC contribution records, which often carry workers that EPF does not, and vice versa, because the two coverage tests differ.
4. Insurer and TPA member lists for group mediclaim, group personal accident, group term life and the compensation declaration, taken from the insurer's current statement rather than from the last file HR sent.

The mismatches that matter are the asymmetric ones. A worker present in payroll and absent from EPF is a campaign candidate. A worker present in EPF and absent from the GPA member list is an uninsured accident exposure sitting inside a policy the employer already pays for. A worker present in the contractor's wage register and absent from all three is the one who costs the most when something happens, because there is no statutory benefit, no policy line and no clean record of the relationship.

Reconcile headcount at the same time as identity. A GPA policy written on a declared headcount of 1,400 while the reconciled worker population is 1,780 is not merely under-declared. It exposes the employer to an average-style reduction argument at claim stage if the wording ties the premium to a declared number, which is why the sum insured and headcount basis in the policy wording deserves a read before the file is corrected.

Sort every exception into one of five buckets and give each a named owner and a date. Do not leave a residual category called "to be reviewed".

In payroll, missing from EPF. Test eligibility against the campaign terms: alive, in active employment on the declaration date, and outside coverage in the 1 April 2009 to 31 March 2026 window. If eligible, declare. Compute the employer's share for the uncovered period and confirm whether the employee's share was ever deducted, because the waiver only applies where it was not. Generate the face-authentication UAN through UMANG before the file is built, since that step gates the ECR remittance and takes longer than teams expect at volume.

In EPF, missing from the insurer member list. This is a pure endorsement. Add the member to the group mediclaim and group personal accident lists with a joining date that matches the employment record, and check whether the insurer will accept a retrospective effective date or only prospective cover. Most wordings allow addition from the date of joining if the endorsement is raised within a stated window, commonly 30 days, and force a prospective date after that.

In contractor wage registers, missing from everything. Decide first whether the worker is on your books or the contractor's. Then either enrol and insure them directly, or obtain the contractor's own EPF and ESIC compliance evidence plus a certificate confirming their group personal accident and compensation cover, with the principal employer named. Verbal assurance from a site supervisor is not evidence.

In insurer lists, missing from payroll. These are ghosts: exited employees never deleted. They inflate premium, distort the age band mix at renewal, and occasionally produce a claim from someone who left eighteen months ago. Delete them and claim the pro-rata refund into the CD account.

Present everywhere, but with wrong data. Wrong date of birth, wrong wage, wrong relationship code on a dependant, wrong nominee. These do not surface until a claim is rejected. Fix them in the same pass, because you have already assembled the reconciled table and will not assemble it again this year.

A campaign-driven audit does not add three joiners. It adds a block, sometimes several hundred people in one movement, and group policies are not administered for that shape of change.

The cash deposit (CD) account is the pre-funded float from which the insurer debits pro-rata premium for mid-term additions. Insurers process additions only against a positive balance. A block addition of 300 members on a group mediclaim policy with a per-member premium in the thousands can exhaust a float sized for ordinary attrition in a single endorsement, and the workers named in the request that failed for want of funds have no cover during the gap. Fund the account before the file goes in, not after the insurer bounces it. The mechanics of that float, and how pro-rata debits are calculated, are set out in our note on group mediclaim administration and CD account endorsements.

Three sequencing points decide whether this goes cleanly:

1. Send one consolidated file, not a trickle. Insurers price and load a single block endorsement faster than they process forty separate requests, and one effective date is far easier to defend at claim stage than forty.
2. Confirm the effective date in writing before remitting. Ask the insurer to state the date cover attaches for the block, and keep that confirmation with the endorsement.
3. Check the waiting-period treatment. On group mediclaim, a large mid-term block may attract different treatment for pre-existing conditions or maternity than the original census received at inception. Read the endorsement terms rather than assuming parity.

Ask what happens when a contract worker who appears in no register is killed or seriously injured on your premises.

The employer's position is weak on every front at once. There is no EPF membership, so no EDLI death benefit reaches the family. There is likely no ESIC coverage, so no statutory medical or dependants' benefit either. The worker is not on the group personal accident member list, so the policy that should have absorbed the loss does not respond. What remains is a statutory compensation liability that attaches to the principal employer under contract labour and employee compensation law, a common-law negligence claim, and a set of records showing that the worker was present, paid and undeclared.

That last element does the most damage. It removes the defence that the worker was the contractor's responsibility, because the establishment's own wage registers and gate records place the worker inside the establishment. It also supplies an inspection trail across EPF, ESIC and contract labour compliance simultaneously.

Insurance treatment follows the same logic. An employers' liability or workmen's compensation policy responds to the insured's legal liability to its employees, and the definition of who counts as an employee is set by the wording read against the facts. A worker the employer never declared, never enrolled and never listed still creates the liability. The recovery is what becomes uncertain. Reviewing the employers' liability definition alongside the reconciled worker table is the practical way to find out whether your programme covers the population you actually employ.

The campaign window makes this cheaper to fix than it will be at any point afterwards, because the employee's share of past contributions is waived where it was never deducted.

Roughly eight weeks separate the start of September from 31 October 2026. Work backwards from the deadline.

1. Weeks one and two: assemble the table. Pull payroll, EPF, ESIC and insurer member data as of a single freeze date. Agree the matching key. Publish the exception counts by bucket to the CFO and the HR head so the size of the problem is a shared number rather than an HR problem.
2. Week three: classify and decide. Run each exception into one of the five buckets. Get a written position from legal on any contract-labour population where the employment relationship is genuinely arguable.
3. Weeks four to six: generate UANs. Face authentication through UMANG for every declared employee is the slowest step at scale, because it needs the worker present with a working device and a successful biometric match. Schedule it in shifts and build in re-attempts.
4. Week seven: file the declaration and remit through ECR. Keep the computation sheet showing the employer's share for each declared period and the basis for treating the employee's share as waived.
5. Week eight: run the insurance endorsements. Fund the CD account, send one consolidated addition file per policy, obtain written effective dates, and delete the ghosts.

What matters after October is that the reconciliation becomes a standing control rather than a one-off. Run the same four-way match monthly against joiners and leavers, tie the insurer member list to the payroll close, and make contractor compliance evidence a condition of the labour bill rather than an annual formality. The cost of the campaign is a known number. The cost of the population you did not declare is decided by whichever claim arrives first.

Sarvada Intelligence reads group policy wordings at the clause level, so a broker or risk manager can compare how member addition windows, retrospective effective dates and employee definitions differ across insurer forms before the block endorsement goes in.