UAN, and the second number you must not create
One permanent provident fund number per person, for life — where generating a duplicate at onboarding is the most common avoidable PF error.
What it is
A permanent 12-digit number linking all of an employee's PF accounts across employers.
What changes
The member ID changes with each job. The UAN does not.
The trap
Not asking a new joiner for their existing UAN, and generating a second one.
The UAN is a permanent 12-digit number that links all of an employee’s PF accounts across employers. It stays with the person for life; the member ID changes with each job. One person holding two UANs causes transfer and withdrawal problems.
How it works in practice
A new joiner who worked before should bring their existing UAN. Generating a second one because the first was not asked for is the most common avoidable PF error in SMB onboarding.
What to watch for
Names and dates of birth must match across UAN, Aadhaar and PAN, or claims stall for months.
How Klok handles it
Klok captures UAN during onboarding from the documents themselves, so it is asked for once and stored against the person.
UAN (Universal Account Number) FAQs
An employee has two UANs. What now?
They must be merged through the EPFO process, with the earlier account transferred. It is resolvable but slow, which is why asking at onboarding is worth the thirty seconds it takes.
Why do claims get rejected on name mismatches?
Because the details must agree across UAN, Aadhaar and PAN. A middle name present in one record and absent in another is enough to stall a claim for months.
Does the employee need to do anything at exit?
They should have the service marked as exited so the next employer can link the same UAN. An account left without an exit date is the usual cause of transfer problems at the next job.
An employee does not know their UAN. How do we find it?
It can be traced from their previous employment records or through the member portal with their identity details. What you should not do is issue a fresh one because tracing is inconvenient — that is how duplicates are created.
Two UANs already exist for one employee. What now?
They have to be merged, and the process is slower than creating them was. Until it is done, service history is split across both, which affects pension eligibility rather than just tidiness.
Does the UAN change when the employee changes jobs?
No — that is the entire point of it. It stays with the person and each employment links to it. Treating it as employer-issued is the misunderstanding behind most duplicates.
Stop calculating this by hand
Klok computes it from your own attendance and salary data, every month, with the working shown.