EPFO has enabled UAN allotment and activation through the UMANG app using Aadhaar-based Face Authentication Technology for supported member journeys.
Rules
- EPFO has enabled UAN allotment and activation through the UMANG app using Aadhaar-based Face Authentication Technology for supported member journeys.
- The process depends on Aadhaar-linked identity data, mobile/OTP readiness and successful face authentication; mismatched demographic data can block or complicate onboarding.
- A worker who already has a UAN should avoid generating another UAN merely to bypass an identity or employer-data error because duplicate identities create transfer and claim problems.
- After UAN creation or activation, the member should verify name, date of birth, Aadhaar linkage, bank details and employment record before relying on the profile for transfer or withdrawal.
Practical analysis
EPFO’s current member journey has shifted UAN generation and activation to Aadhaar-based Face Authentication through UMANG. The official manual requires a valid Aadhaar, access to the Aadhaar-linked mobile for OTP and the Aadhaar Face RD app. The system checks whether the Aadhaar is already linked to a UAN before creating a new one, which is an important safeguard against duplicate member identities.
Face-authentication failure is usually a validation problem rather than a reason to create another UAN. Aadhaar demographic mismatch, mobile access, invalid UAN mapping or failed EPFO validation should be corrected through the appropriate identity/member process. From August 2025 EPFO made the face-authentication route central to UAN allotment/activation, so old portal screenshots can be misleading.
After activation, verify the member profile before the first claim or transfer. Name, date of birth, Aadhaar, bank details and employment/service history should agree. A UAN generated correctly but paired with a wrong joining date or bank account can still create claim friction; early cleanup is easier than correcting the record during a time-sensitive withdrawal.
EPFO’s current UAN journey uses Aadhaar-based face authentication through UMANG for direct allotment/activation. That makes the Aadhaar demographic record, Aadhaar-linked mobile access and face-authentication readiness practical prerequisites. A mismatch should be corrected at the source rather than bypassed through repeated submissions. Employees should also avoid creating a second UAN merely because activation of an existing identity has failed; duplicate-UAN correction is a separate process.
Decision table
| Fact pattern | Treatment |
|---|---|
| No UAN; Aadhaar not linked to another UAN | Use UMANG UAN Allotment and Activation with OTP and face authentication. |
| System says Aadhaar already linked | Recover/use the existing UAN; do not generate a duplicate. |
| Face/EPFO validation fails repeatedly | Correct the underlying Aadhaar/UAN data or contact support rather than repeated blind attempts. |
Worked examples
A worker without a UAN uses UMANG, Aadhaar-linked OTP and face authentication to generate/activate the UAN under the EPFO mechanism. Do not create a second UAN if Aadhaar is already mapped to one.
If the Aadhaar name and employer onboarding trace differ materially, resolve the identity data rather than forcing another registration. UAN Generation by Aadhaar Face Authentication conclusion: One clean member identity is the objective; duplicate UANs create downstream transfer/claim issues.
A new employee’s Aadhaar name contains a middle name that is absent from the employer’s onboarding record, and UMANG face authentication succeeds but the downstream UAN process flags demographic mismatch. The correct response is to reconcile the member/employer/Aadhaar data rather than generating another identity. Preserve the UMANG acknowledgement or error screen, confirm the Aadhaar-linked mobile is active and have the employer correct its joining record where necessary before repeating the UAN allotment or activation workflow.
Mistakes
- Creating a second UAN to bypass an identity error.
- Using a mobile number not linked to Aadhaar and expecting OTP verification to complete.
- Ignoring profile mismatches after UAN generation.
- Following obsolete direct-allotment portal instructions instead of the current UMANG face-auth route.
Documents
- Aadhaar and access to Aadhaar-linked mobile
- UMANG/face-auth acknowledgement
- UAN activation confirmation
- Member profile, bank KYC and employment/service record
Action steps
- Install/update UMANG and Aadhaar Face RD app.
- Use UAN Allotment and Activation only if no UAN exists.
- Complete OTP and face authentication.
- If existing UAN is detected, recover that account instead.
- Verify demographic, bank and service details after activation.
- Correct mismatches before filing transfer/claim requests.
FAQs
Can I still generate a UAN directly on the old member portal?
EPFO now directs members to Aadhaar-based face authentication through UMANG for UAN generation/activation.
What is needed for the face-auth process?
A valid Aadhaar, Aadhaar-linked mobile access for OTP and the Aadhaar Face RD app are core requirements.
What if Aadhaar is already linked to a UAN?
Use/recover the existing UAN rather than creating another one.
Why verify the profile after activation?
Incorrect bank, demographic or service data can block later transfers and claims even when the UAN itself is active.
Sources
- EPFO — User Manual for UAN Services on UMANG using Face Authentication — UAN allotment/activation and face-auth requirements.
- EPFO — Member Portal notice — Current instruction that UAN generation/activation is through UMANG face authentication.
Educational reference; verify the current official instrument and your facts.