A new joiner has worked before. They already have a UAN — a permanent twelve-digit number that follows them for life, across every employer.
If nobody asks for it, a second one gets generated. And a second UAN is not a paperwork problem.
What it costs the employee
Their provident fund savings are now split across two accounts. Transfers between employers stop working. Withdrawal claims stall. Merging the two is a process they have to pursue, through the EPFO, over months.
They usually discover this at the worst possible time: when they need the money, or years later at retirement.
And it happened because a form was collected and not read.
Form 11 exists precisely for this
Every new joiner completes Form 11 — the declaration about previous provident fund membership, existing UAN and previous member ID.
In most companies it is collected as a formality, filed, and never looked at. The entire purpose of the form is to surface the existing UAN so the new employment attaches to it. Filing it unread defeats the point of collecting it.
Ask for the number, not for a yes or no
"Have you been a PF member before?" gets you an answer people are often unsure about, particularly if the earlier job was brief or years ago.
Ask for the number. If they do not know it, it is on their previous payslip or retrievable from the EPFO member portal, and thirty seconds at onboarding is a great deal cheaper than the alternative.
While you have their documents in front of you
Check the details match across UAN, Aadhaar and PAN. Name, date of birth, father's or spouse's name. A middle name present in one record and absent in another is enough to hold a claim for months.
This is the cheapest moment in the entire employment relationship to catch a mismatch, because the person is there with their documents. Every later moment costs more, and the most expensive is after they have left.
Check international worker status, which carries materially different provident fund rules including the absence of the ordinary wage ceiling. Missing it produces a contribution error that repeats every month until somebody notices.
Why reading the documents helps
When onboarding documents are read rather than transcribed, the UAN and the name spellings come off the document itself rather than out of a WhatsApp thread. The mismatch that causes the stalled claim usually originates in somebody typing quickly — which is a step worth removing entirely.