Multiple UAN Numbers? How to Merge PF Accounts

Having more than one UAN usually happens by accident, most often when a new employer generates a fresh UAN instead of correctly linking to your existing one, especially if your Aadhaar or PAN wasn't provided accurately at onboarding. The result is two active identities in EPFO's system for the same person, each tracking a separate slice of your service and contribution history.

EPFO does provide a defined process to merge duplicate UANs into one, and getting it resolved matters more than it might initially seem, since a fragmented record can complicate transfers, withdrawals, and continuous service calculations down the line. The earlier it's caught, the simpler the eventual merge tends to be.

Why This Matters

A duplicate UAN doesn't just create administrative confusion, it can genuinely reduce the benefits you're entitled to. Continuous service calculations, which determine tax-free withdrawal eligibility and pension timelines, are calculated per UAN unless the accounts are merged, meaning a split record can understate how long you've actually been contributing to EPF overall. It can also complicate a future claim, since EPFO may need to verify which account holds which portion of your history before processing a withdrawal or transfer cleanly.

Understanding the Problem

Duplicate UANs typically arise when a new employer's onboarding process generates a fresh UAN rather than correctly retrieving and linking your existing one, often due to a mismatched or missing Aadhaar or PAN at the time of enrollment. Once two UANs exist, each accumulates its own separate contribution and service history, and neither shows the complete picture until they're formally merged into a single active account. The longer the duplicate goes unnoticed, the more contribution history accumulates on the wrong account, which is part of why an early check is worth the small effort involved.

Step-by-Step Solution

Step 1: Identify that you have more than one UAN

Use the 'Know Your UAN' lookup on the EPFO portal with your Aadhaar or PAN to check whether more than one UAN is associated with your identity.

Step 2: Determine which UAN should remain active

Generally, your most recent UAN, linked to your current employer, is retained as the active one, while the older UAN is merged into it.

Step 3: Raise a merge request through the grievance portal or your employer

Since there's no fully automated self-service merge option for most cases, this typically involves raising a request through EPFO's grievance portal (EPFiGMS) or working with your current employer's HR to formally flag the duplicate.

Step 4: Provide supporting documents establishing both UANs belong to you

Aadhaar, PAN, and details of both UANs are typically required to establish that the duplicate accounts belong to the same person before EPFO will process a merge.

Step 5: Wait for EPFO to consolidate the service and contribution history

Once approved, EPFO merges the balance and service record from the older UAN into the retained one, which can take time depending on how much history needs to be reconciled.

Step 6: Verify the merge by checking your consolidated passbook

After processing, check that your retained UAN's passbook reflects the combined contribution history from both accounts, confirming the merge has fully gone through.

Common Mistakes to Avoid

• Not checking for duplicate UANs proactively and only discovering the issue years later when filing a claim or transfer that requires a complete service history.
• Assuming a duplicate UAN will resolve itself automatically over time, when it actually requires an explicit merge request to consolidate.
• Providing incomplete documentation that doesn't clearly establish both UANs belong to the same person, causing the merge request to be sent back for more evidence.
• Continuing to use both UANs interchangeably at different points, such as providing the wrong one to a new employer, which can create a third duplicate account.
• Not following up on a submitted merge request, assuming EPFO will proactively notify you the moment it's resolved.
• Overlooking that a merge can affect a pending claim or transfer already in progress on one of the UANs, and not checking for this before initiating the merge.
• Not informing a new employer that an older UAN exists, which can lead to a third duplicate being created instead of the existing ones being properly merged.

Quick Recap

Duplicate UANs are more common than most employees realise, and they quietly fragment your service history until formally merged. Checking for duplicates early, rather than discovering the issue when you're mid-claim, and providing clear supporting documentation up front are what keep the merge process moving without unnecessary delays.

Frequently Asked Questions