A Universal Account Number (UAN) is a 12-digit identification number issued by the Employees' Provident Fund Organisation (EPFO) to every Indian employee covered under the Provident Fund. The UAN stays with the employee for their entire career, regardless of how many times they change jobs. Each new employer links its PF account, called a Member ID, to the same UAN, so the contributions, balance, and service history all consolidate under one number. UAN is the backbone of online PF withdrawals, transfers, KYC, and e-passbook access.
What does UAN do?
- Links all PF Member IDs: every PF account opened by a current or past employer for the same person rolls up under one UAN.
- Powers the e-passbook and balance view: employees can log in to the EPFO unified portal to view contributions, balance, and service history.
- Enables one-click PF transfers: when an employee changes jobs, PF can move from the old Member ID to the new one without a fresh claim, provided KYC is in order.
- Anchors KYC: Aadhaar, PAN, bank account, and mobile number are all seeded against the UAN and verified by the employer.
- Required for online withdrawal: online PF claims for advance, withdrawal, or pension are filed against the UAN with Aadhaar-based authentication.
How is the UAN generated?
- First-time employment: when the first employer registers the employee with EPFO, a UAN is generated automatically against the new PF Member ID.
- Self-generation via Aadhaar: employees can also generate a UAN themselves on the EPFO unified portal using Aadhaar-based OTP verification.
- Reuse, do not duplicate: if the employee has worked before, the existing UAN must be reused; a new UAN should not be created.
UAN at onboarding: what HR needs to do
- Collect existing UAN: ask new joiners for their existing UAN as part of the onboarding paperwork, before opening a new PF account.
- Link, do not create: link the new PF Member ID to the existing UAN; creating a second UAN causes downstream issues for transfers and claims.
- Activate and KYC: the employee should activate the UAN on the EPFO portal; the employer must then verify Aadhaar, PAN, and bank details as part of KYC.
- Confirm data consistency: name, date of birth, and father or spouse name should match across Aadhaar, PAN, and EPFO records to avoid claim rejections later.
Common UAN issues
- Multiple UANs for one employee: usually because a new UAN was created at a later employer; resolved by raising a merger request through EPFO.
- Name or DoB mismatch: Aadhaar and EPFO data not aligned, which blocks online claims; corrected by filing a joint declaration with the employer.
- Pending KYC approval: KYC documents are uploaded but the employer has not yet approved them in the EPFO portal, blocking transfers.
- UAN not Aadhaar-seeded: without an Aadhaar link, online claims and pension benefits cannot be processed; resolved by completing Aadhaar verification in the portal.
Done correctly, UAN management is a small but critical part of Indian payroll. Done sloppily, it shows up years later as failed PF transfers, blocked withdrawals, and unhappy ex-employees calling the HR team for help long after they have left.
Setting up Indian PF and UAN compliance?
Wisemonk handles UAN registration, KYC, PF compliance, and payroll for global companies hiring in India, without the need to set up a local entity.
Ready to build your India team?
Tell us who you're looking to hire. We'll walk you through exactly how the setup works for your company, your timeline, and your budget.