A packaging manufacturer in Tamil Nadu brought us in as its third contractor in four years. Our onboarding checks found that about a third of the crew had more than one Universal Account Number, so their provident fund service was split across accounts that did not know about each other. Over six months the records were merged onto one UAN each, and the next changeover was set up so it could not happen again. This is a representative composite; no single client is described.
The situation
The plant cut, printed and folded cartons for consumer-goods customers, and most of its contract crew had stayed through both earlier changes of contractor [VERIFY: composite]. On paper every worker was enrolled in EPF and every month's ECR was filed. The problem only showed when we searched the EPFO portal for each worker's existing UAN against their Aadhaar before enrolling anyone, as we do at every onboarding. Long-serving workers turned up with two or three UANs, each holding a short stretch of service.
The rules expect one number for life. The EPF Scheme 2026 defines the UAN as an identity number allotted to an employee "on a permanent basis" (para 2(1)(q)). An employer enrolling someone who comes from another establishment uploads them "by way of linkage of UANs" (para 24(2)(ii)), and generates a new UAN only where the employee fails to (para 24(2)(iii)). The EPFO's own guidance names the usual causes of a second UAN: the previous employer never filing the date of exit, or a new number being generated at joining [VERIFY: EPFO UAN and KYC FAQs; the documents could not be opened this run].
Why a split record costs the worker
Each account looked healthy on its own; the cost sits in everything that depends on length of service. We set out what the split put at risk for the site's HR head:
| What depends on service | The rule | What a split record does |
|---|---|---|
| EDLI death benefit | Twelve months' continuous employment brings the 35-times-wages formula and the ₹2.5 lakh floor; services with different employers are added, ignoring gaps of up to 60 days (EDLI Scheme 2026, para 21(4) and proviso) | The service still counts in law, but the family has to establish it across accounts that are not linked [VERIFY: EPFO practice on EDLI claims across unlinked UANs] |
| Pension | A monthly pension needs ten years of eligible service [VERIFY: EPS 2026, G.S.R. 527(E), not opened; ten years under the 1995 scheme] | Several short pension histories instead of one long one |
| Partial withdrawals | Eligibility turns on the period of membership, computed under para 47 of the EPF Scheme 2026 | Each account shows only part of the membership [VERIFY: how EPFO applies para 47 across unlinked UANs] |
| Nomination | The PF nomination is also the EDLI nomination (EDLI Scheme 2026, para 22) | An old account can carry an old nomination, or none |
None of this shows on a payslip or an ECR. A worker finds out when they apply for a withdrawal and are told they have not served long enough, and a family finds out at the worst possible time.
What we did
- Chose one surviving UAN per worker. The EPFO's guidance is to keep the current KYC-compliant UAN and move earlier services onto it [VERIFY: EPFO FAQ]. For each of the 37 we identified the number seeded with Aadhaar and a bank account, and linked our new member ID to that one. No new UAN was generated for anyone with prior service.
- Filed the transfers. Each earlier account was moved across through the member's transfer application on the portal (EPF Scheme 2026, para 43(1)). Where online confirmation of identity failed, which happened mostly on name or date-of-birth mismatches between the old record and Aadhaar, we forwarded the application as employer after confirming identity, as para 43(3) provides [VERIFY: composite].
- Reported the duplicates. Each worker's earlier numbers were reported to the EPFO for blocking once their services were moved, so nothing else could be credited to them [VERIFY: EPFO procedure for blocking a previous UAN].
- Fixed the root cause with the old contractors. Most of the second UANs traced to missing exit dates [VERIFY: composite]. Through the site, we asked both earlier contractors to upload the exit dates para 24(2)(v) required of them; one did, and the other's gaps were closed through the members' own requests [VERIFY: composite].
- Moved the nominations. Every worker's e-nomination was checked on the surviving UAN, and filed again where it existed only on an old account.
What changed
| Measure | At onboarding | Six months later | Notes |
|---|---|---|---|
| Workers with more than one UAN | 37 | 3 | The three are waiting on name corrections to old records [VERIFY: composite] |
| New UANs generated for workers with prior service | Not checked | None | A portal search against Aadhaar runs before every enrolment |
| Nominations on the surviving UAN | Not known | All 37 | Composite [VERIFY] |
| Exit dates from the outgoing contractor | Not asked for | A named item in the site's handover evidence pack | Ties to para 24(2)(v) of the EPF Scheme 2026 |
The lasting change was in the site's contract template. The exit clause now requires an outgoing contractor to show that it has uploaded every leaver's exit date before its last bill is released, and the onboarding clause requires an incoming one to enrol returning workers on their existing UAN. The duplicates came from two handovers that each looked clean at the time.
The lesson carries to any site that changes contractors with the same crew. A split PF record is invisible in the monthly filings and costs nothing until a worker or family needs their full service. How a particular worker's benefit is decided is a matter for the EPFO on that worker's record. This composite describes a method, not an outcome.
How Velura Services helps
At onboarding we search the EPFO portal for every worker's existing UAN and check it against Aadhaar before anyone is enrolled, so a returning worker is linked, not registered again. Where a record is already split, our payroll team files the transfers, forwards them as employer where online identity checks fail, and confirms the nomination sits on the surviving UAN. At handover we ask for the outgoing contractor's exit-date uploads as part of the evidence pack.
Sources
- Figures are a representative composite drawn from our own deployments; no single client is described. Founder to confirm or replace before publish.
- Employees' Provident Funds Scheme, 2026, G.S.R. 525(E) dated 29 June 2026, mirrored copy of the Gazette. Paragraphs cited: 2(1)(q) (UAN allotted on a permanent basis), 24(2)(ii), (iii) and (v) (joiners linked by UAN; UAN generated only where the employee fails to; leavers uploaded within fifteen days), 43(1) and (3) (transfer; employer forwards where online identity is not confirmed), 47 (period of membership). Opened and read [VERIFY: against the e-Gazette original].
- Employees' Deposit-Linked Insurance Scheme, 2026, G.S.R. 526(E) dated 29 June 2026, mirrored copy of the Gazette. Paragraphs cited: 21(4) and proviso (twelve-month test; services added; sixty-day gaps ignored), 22 (PF nomination applies). Opened and read [VERIFY: against the e-Gazette original].
- EPFO, Frequently Asked Questions: UAN and KYC and EPFO, Information booklet for EPF members. Causes of a second UAN; keeping the current UAN and transferring earlier services; blocking the previous UAN. Not opened: the EPFO site returned errors this run [VERIFY: wording and currency of both documents].
- Employees' Pension Scheme, 2026, G.S.R. 527(E) dated 29 June 2026 [VERIFY: not opened; the ten-year pension threshold is taken from the 1995 scheme].