Form 11, and the thirty seconds that prevent a duplicate UAN
The declaration every new joiner makes about previous PF membership — routinely treated as a formality, and routinely the reason a claim stalls two years later.
What it is
A declaration by a new employee about previous provident fund and pension scheme membership.
When
At joining, before the first contribution is made — not afterwards when something goes wrong.
The trap
Filing it unread. The whole point is the existing UAN it is supposed to surface.
Form 11 is the declaration a new employee makes about their previous provident fund membership: whether they have been a member before, their existing UAN and previous member ID, and details relevant to their pension scheme membership.
It is collected at joining, and in most companies it is collected as a formality and never read.
What it is actually for
The form exists to establish whether this person already has a provident fund account, so that the new employment attaches to the same UAN rather than generating a second one.
A duplicate UAN is not a paperwork problem. It splits somebody's retirement savings across two accounts, blocks transfers, and stalls withdrawals — and merging them afterwards is a slow process the employee has to pursue themselves.
All of which is prevented by reading the form at the point it is collected and acting on what it says.
The details have to match
Name, date of birth and father's or spouse's name must agree across the UAN record, Aadhaar and PAN. A middle name present in one and absent in another is enough to hold up a claim for months.
Onboarding is the cheapest possible moment to catch this, because the employee is in front of you with their documents. Every later moment is more expensive, and the most expensive is after they have left.
International workers
The form also captures whether the employee is an international worker, which carries a materially different set of provident fund rules — including the absence of the ordinary wage ceiling. Missing that at onboarding produces a contribution error that runs every month until somebody notices.
Keep it with the record
A signed Form 11 belongs in the employee's document file, retrievable. In a PF inspection or a dispute about which account contributions should have gone to, it is the document that shows what the employee told you and when.
EPF Form 11 FAQs
What if a joiner says they have no UAN but actually do?
You will generate a second one, and they will discover it when they try to transfer or withdraw. Asking for the number rather than a yes-or-no answer, and checking it against their documents, avoids nearly all of these.
Is Form 11 required for every joiner?
It is taken from new employees on joining as part of provident fund enrolment, including those who say they have never been a member — that declaration is precisely what the form records.
What if the details do not match Aadhaar?
Get them corrected before contributions build up against a mismatched record. A correction at onboarding is an administrative step; the same correction after two years of contributions is a much longer process.
Is Form 11 needed for every new joiner?
It is the declaration that establishes prior membership, so collect it at joining, before the first contribution. Collecting it later means guessing at exclusion status in the meantime.
What if the employee declares no prior PF membership?
Their eligibility on joining above the wage ceiling is treated differently from a continuing member. That declaration is precisely what the form exists to record — verbal assurance is not a substitute.
Does a wrong declaration protect the employer?
Not entirely. The obligation to enrol correctly sits with you, so an obviously implausible declaration is worth questioning rather than filing.
Stop working this out by hand
Klok applies these rules on every payroll run, from your own attendance and salary data, with the working shown.