UAN and EPFO records: what an employer can still see

What the record is

The Universal Account Number is a permanent number issued to an employee under the Employees' Provident Fund scheme. Its point, when it was introduced, was portability: instead of a new provident fund account at every employer, one number follows the person and the member IDs from each employer attach to it.

That produces something incidentally valuable for verification. Behind a UAN sits a record of which establishments made provident fund contributions for that person, and for which months. It is a history of formal employment, held centrally, that does not depend on any individual employer agreeing to co-operate.

Nothing else in Indian verification has that property. Every other employment record is held by the employer, which means it can be withheld, lost, or extinguished when the company closes.

What it confirms

• That the UAN exists and belongs to the candidate, matched against the identity details declared.
• Which establishments contributed, which is the employment history in the sense that matters here.
• The months contributions were made, which corroborates declared periods independently of the employer.

The third point is where most of the value sits. If a candidate declares a period at an employer and the contribution record shows that establishment contributing over roughly that period, the declaration has been corroborated by something that is not the candidate and not the employer.

What it does not confirm

Being precise about this matters, because the gap between what buyers expect and what the record holds is wide.

So it corroborates rather than replaces a standard employment verification. Where it becomes the primary evidence is when the standard check has nowhere to go.

The case where it does the most work

A candidate declares three years at a company that no longer exists. There is no HR desk, no successor entity anyone can name, and no route to a record holder. The employment check has nothing to ask.

The contribution record still shows that establishment contributing for that person over those months. The employment is corroborated, and it was corroborated by something that outlived the company.

The same applies to the employer that simply refuses to respond, and to the one that routes verification through a paid agency the client would rather not use. In all three cases the alternative to EPFO corroboration is an "unable to verify" that penalises the candidate for the administrative behaviour of an organisation they left years ago. That is the outcome worth avoiding, and it is why this record matters more than its dryness suggests.

Reading an overlap

Because the record lists every contributing establishment, two establishments contributing for the same months are visible. That is the basis of most moonlighting findings, and it needs care.

Overlaps are common and mostly innocent. A notice period served while a new employer has already begun contributing produces one. So does a slow exit closure, a group-entity transfer, or an agreed transition arrangement. A one or two month overlap at a job change is close to routine.

What is worth asking about is a sustained overlap, particularly with an employer the candidate did not declare. Even then it is a question, not a conclusion, and the candidate will usually be able to explain or document it within a day.

What has been changing

The broader direction over recent years has been towards tighter handling of member data and less unrestricted third-party visibility. That is consistent with what the DPDP Act expects of personal data generally, and it is the right direction: a person's employment and contribution history is sensitive, and it should not be casually queryable by anyone who has their number.

For an employer buying verification, the practical consequences are worth knowing.

• Consent matters more, not less. A UAN check runs on the candidate's consent like any other, and that consent should name it specifically rather than hide inside a general clause.
• The candidate's own view and a third-party check are not the same thing. A member can see things about their own record that a verification cannot confirm to an employer. If a provider is producing information that looks like a member's own view, it is worth asking exactly how they obtained it.
• Informal access routes are fragile. Any provider whose UAN capability depends on something other than a proper, consented, identified request is on a footing that can disappear without notice, and it takes your process with it when it does.

None of that changes what the record is worth. It changes how carefully the route to it has to be built, which is a question to put to a provider directly. It is question 2 in how to evaluate a provider: which of your checks are database lookups, and which are properly sourced requests.

How to use it well

1. Ask for the UAN on the submission form, as a distinct field. Most candidates in formal employment have one and can find it. It costs nothing and it is the difference between having a fallback and not.
2. Name it in the consent record alongside the other checks.
3. Use it as corroboration, not as the whole employment check, unless the employer genuinely cannot be reached.
4. Never read a gap as a finding. Ask about it if the period matters, and expect a mundane answer.
5. Treat a short overlap at a job change as normal. Reserve the question for a sustained one with an undeclared employer.

The check page itself is UAN verification.