UAN (Universal Account Number)

Before the UAN, an employee changing jobs got a new provident fund account each time, and the old balance sat where it was until they filed to move or withdraw it. Balances were routinely abandoned, because tracing one meant knowing which regional office held which account number.

The UAN puts one permanent number above all of them. EPFO allots it once, and every PF account the employee is later given hangs beneath it. The employee logs in to one place, sees every period of employment, and moves a balance without needing to know where it sits.

Worth being precise about its status. The fund, the contribution and the right to transfer now come from Chapter III of the Code on Social Security, 2020, which applies to every establishment with twenty or more employees. They used to come from the Employees' Provident Funds and Miscellaneous Provisions Act, 1952, which section 164(1) of that Code repealed with effect from 3 May 2023, earlier than the other eight enactments in the same repeal list. What became of the schemes framed under the 1952 Act is a savings question this entry does not answer, because section 164's savings sub-sections have not been read. The UAN itself is an administrative layer EPFO introduced to make that right usable. That distinction matters when something goes wrong: a UAN problem is an EPFO process problem, not a question of statutory entitlement, and the money is not at risk because the number is wrong.

These are confused constantly, including by payroll teams, and the difference explains most UAN trouble.

An employee with three past jobs has one UAN and four member IDs including the current one. Seeing several member IDs in the passbook is normal. Seeing several UANs is not.

Allotment happens through the employer. When a new joiner is enrolled, the employer either quotes the UAN the employee already has or, for a genuine first job, generates a new one through the EPFO employer portal.

Activation is the employee's own step and separate from allotment. Using the member portal with the UAN and the mobile number registered against it, the employee sets a password and gains access. Until that is done the number exists but does nothing.

What makes it useful is KYC seeding. Aadhaar, PAN and bank account with IFSC have to be linked and approved by the employer through the portal.

• Aadhaar seeding is what enables online claims without physical forms and employer attestation at each step.
• Bank details with matching IFSC determine where money lands, and a mismatch rejects the claim rather than misdirecting it.
• PAN affects tax treatment on withdrawal, since TDS under Section 192A applies at a higher rate where PAN is missing.

Seeding at onboarding costs a few minutes. Seeding during an exit, when the employee has already left and the employer has no incentive to chase it, is where claims stall for months.

A duplicate is created when an employer generates a fresh UAN for someone who already has one. That happens when the joiner does not know their number, gives it wrongly, or declares themselves a first time member because they assume a short or informal stint did not count.

Nothing announces the problem at the time. Contributions flow into the new number, the passbook looks correct, and the employee sees a balance. The failure surfaces at exit, when they try to consolidate or withdraw and find their service split across two identities, one of which may hold a period they need for a five year continuity test.

The fix is to have EPFO link the old UAN to the new one and transfer the account, either through the employer or by raising a grievance with EPFO directly. It is resolvable but slow, and it lands at the worst moment, when the person needs the money. The reliable prevention is at onboarding: ask every joiner for an existing UAN and treat a first job declaration as something to confirm rather than accept.

The member portal is where the practical work happens, and most of it does not need the employer once KYC is approved.

• View the passbook, with contributions from every member ID split into the employee share, the employer share and the pension share.
• File a transfer claim to move a previous employer's balance into the current account.
• File a withdrawal or advance claim, full or partial, against permitted grounds.
• Record and update a nomination, which decides who receives the balance and the EDLI benefit on death.
• Download the UAN card and check whether each period of service has been marked with an exit date.

The exit date deserves attention. An employer marks the date of exit against the member ID when someone leaves, and a claim will not process while the previous employment still reads as current. Employees who left months ago and cannot file usually find an unmarked exit rather than anything wrong with their balance.

Two checkpoints prevent nearly every UAN problem an employer will face.

At onboarding, collect the existing UAN before generating anything, verify the name and date of birth against Aadhaar since a mismatch blocks seeding later, and approve the KYC in the same week rather than leaving it pending. A name recorded as it appears on a school certificate rather than on Aadhaar is a common and slow to fix cause of rejected claims.

At exit, mark the date of exit against the member ID promptly and settle the final PF month in the correct return. Neither is difficult, and both are routinely skipped once the person is off the payroll, which is exactly when the employee has no way to get them done.