Universal Account Number (UAN) Registration

The Universal Account Number (UAN) is the 12-digit permanent identifier that the Employees’ Provident Fund Organisation (EPFO) issues to every provident fund member in India. Introduced in October 2014, it exists to solve one problem: before the UAN, an employee accumulated a fresh PF account with every job change, and consolidating them was slow, manual and frequently unsuccessful. The UAN stays with the individual for life. Employment changes; the number does not.

One thing has changed fundamentally, and it catches employers out. Since 1 August 2025, under an EPFO circular dated 30 July 2025, both the allotment and activation of a UAN happen exclusively through Aadhaar-based Face Authentication Technology (FAT) on the UMANG app. The employee does it themselves, on their own phone. Direct UAN allotment through the EPFO member portal has been discontinued, and the employer-driven generation route survives only for a narrow set of exceptions.

If your onboarding checklist still says “HR will generate the new joiner’s UAN,” it is out of date.

Who does what now – the short version

The employee downloads two apps, scans their own face, and receives their UAN. For most new joiners, the employer plays no part in creating the number at all.

The employer no longer generates the UAN, but is far from off the hook. You still have to collect and validate it, link it to employment, report it to EPFO within statutory timelines, and – under the Employees’ Provident Funds Scheme, 2026 – facilitate UAN generation where the employee has not done it themselves. The obligation moved; it did not disappear.

The exceptions are International Workers and citizens of Nepal and Bhutan, who typically cannot complete Aadhaar face authentication. For these members, the older employer-driven UAN generation process continues to apply. If you employ inbound assignees, this exception is the part of the rule you actually need.

The six stages of UAN registration

Stage 1 – Allotment

The employee installs the UMANG app (Unified Mobile Application for New-age Governance) and the Aadhaar Face RD app, both free from the Google Play Store or Apple App Store. The Face RD app never gets opened directly – it runs in the background during the scan, but it must be installed or the process stalls.

Within UMANG, the path is EPFO services → UAN Services Through Face Auth → UAN Allotment and Activation. That single option handles both a fresh allotment and the activation of an existing number.

Stage 2 – Aadhaar verification and the face scan

The employee enters their Aadhaar number and their Aadhaar-linked mobile number, gives consent for Aadhaar-based verification, and submits the OTP they receive. A live face scan then authenticates them against the UIDAI database.

The mobile number is the single most common point of failure. It must be the one registered against Aadhaar – not a newer number, not a work number. If the two do not match, the OTP never arrives and the process cannot proceed.

Stage 3 – Issue of the number

On successful authentication, EPFO sends the UAN and a temporary password by SMS. Because details are pulled straight from the Aadhaar database rather than typed in by a payroll administrator, the member’s name, date of birth, photograph and address are populated from a verified source. This is the whole point of the redesign: the historic driver of duplicate UANs, rejected claims and endless correction requests was manual data entry mismatches, and face authentication removes that step entirely.

Stage 4 – KYC seeding

A UAN that exists but is not seeded is of limited use. Under the EPF Scheme, 2026, every member must furnish their Aadhaar with an Aadhaar-seeded bank account, their PAN, and their UAN. Filing an e-nomination is also mandatory under the 2026 scheme, and can be filed and updated throughout the service period.

Treat all of this as an onboarding-stage control. Incomplete KYC does not announce itself – it surfaces months later, when an employee’s withdrawal claim is rejected and the query lands with HR.

Stage 5 – Linking the UAN to employment

This is where the employer’s real work sits. Within 15 days of the close of each month, you must electronically upload details of employees qualifying as fund members for the first time, employees joining by transfer from another establishment – done by linking their existing UAN – and employees who left during the preceding month.

Two operational notes. The ECR is now UAN-based, without the legacy member ID, following EPFO’s database consolidation and software upgrade. And EPFO has introduced upfront UAN allotment, so the number is expected to exist before contributions flow rather than being generated retrospectively from the challan.

Stage 6 – Portability and exit

When an employee changes jobs, they hand the same UAN to the new employer, who links it. Past balances transfer online through the EPFO member portal without loss of accrued interest or service continuity. Nothing is reissued.

The reason this matters commercially: an employee who ends up with a second UAN has effectively fragmented their own retirement record, and untangling it consumes HR time at both the old and new employer.

When registration fails – and what it usually is

The OTP never arrives. The mobile number is not the one linked to Aadhaar. Fix the Aadhaar record first; nothing downstream will work until then.

The face scan will not complete. The Aadhaar Face RD app is missing, or the environment is wrong. Adequate lighting and a steady frontal camera position resolve most cases.

The app reports that the UAN is already activated. The employee has an earlier UAN from a previous job they have forgotten about. Retrieve it rather than creating a new one – generating a second UAN is the problem, not the solution.

An inbound assignee cannot authenticate at all. Expected. International Workers and Nepali and Bhutanese citizens fall under the employer-generation exception.

Contributions appear briefly missing from the passbook. EPFO has flagged posting delays connected to its revamped ECR ledger and database consolidation. Confirm the challan and ECR were accepted before treating it as a remittance failure.

Why UAN discipline matters to employers

The UAN looks like an administrative detail and behaves like a control point. Without an active, correctly seeded UAN, an employee cannot access their passbook, file a claim, or transfer a balance – and the resulting queries route straight to HR. On the employer side, weak UAN hygiene produces ECR rejections, avoidable correction cycles, questions during EPFO inspections, and exposure on incentive-linked schemes that depend on accurate member reporting.

The 2026 framework tightens this further. Aadhaar, PAN and UAN are now express member obligations, filings are electronic-only, and the employer carries a positive duty to facilitate generation where the employee has not acted. For multinationals, the added wrinkle is that the self-service route your Indian hires will use is the one route your inbound assignees cannot.

How Mercans supports UAN and EPFO compliance in India

Mercans is a global leader in payroll technology and Employer of Record services, operating across 160 countries through proprietary SaaS platforms and in-country delivery teams. Mercans runs its own legal entity in India, which keeps statutory filing in-house rather than routed through an aggregator.

On UAN specifically, Mercans validates UAN and KYC completeness at onboarding, manages employer-side generation for International Workers and other exception cases, links transfers-in and reports joiners and exits within EPFO’s 15-day window, files the UAN-based ECR, and keeps records audit-ready across PF, ESI, TDS, Professional Tax and gratuity.

Related reading: the Mercans statutory alert on India’s new EPF, EPS and EDLI Schemes 2026, Mercans’ India payroll and EOR capabilities, global payroll outsourcing, local statutory compliance services, the HR Blizz platform, and the full statutory alerts library.

Frequently Asked Questions (FAQs)

1. Does the employer still generate the UAN for new employees?

Generally no. Since 1 August 2025, UAN allotment and activation are done by the employee through Aadhaar-based Face Authentication on the UMANG app, and direct allotment via the EPFO member portal has been discontinued. The employer-driven route survives only for exceptional cases – International Workers and citizens of Nepal and Bhutan. Employers still collect and validate the UAN, link it to employment, report it within EPFO timelines, and under the EPF Scheme, 2026 must facilitate generation where the employee has not completed it.

2. What does an employee need in order to register a UAN?

Their Aadhaar number, a mobile number registered against that Aadhaar, and two apps – UMANG and Aadhaar Face RD. The flow is EPFO services → UAN Services Through Face Auth → UAN Allotment and Activation, then Aadhaar details, consent, OTP, and a live face scan. The UAN and a temporary password arrive by SMS. The mismatched-mobile-number problem accounts for most failed attempts, so it is worth checking before the employee starts.

3. What happens to the UAN when an employee changes jobs?

Nothing – that is its purpose. The same 12-digit number carries across employers for life. The employee provides it to the new employer, who links it while reporting the joiner, and the previous balance transfers online through the EPFO portal without losing accrued interest or service continuity. A new UAN should never be generated for someone who already has one; duplicate UANs fragment the member’s record and take considerable effort to merge.

4. Is an unactivated UAN a compliance problem for the employer?

It becomes one. An unactivated or unseeded UAN blocks the employee from passbook access, claims and transfers, and it undermines the accuracy of your member reporting – with knock-on effects for ECR acceptance, EPFO inspections and eligibility under incentive-linked schemes that rely on verified member data. Under the EPF Scheme, 2026, Aadhaar, PAN and UAN are express member obligations and the employer has a positive duty to facilitate generation. The practical answer is to make UAN status and KYC completeness a gate in onboarding rather than an annual clean-up exercise.