UAN (Universal Account Number)

In brief: a UAN is the 12-digit Universal Account Number that EPFO assigns to members. It stays the same across jobs, which makes the UAN a strong anchor for checking employment history.

What is a UAN?

A UAN (Universal Account Number) is the twelve-digit number issued by the Employees’ Provident Fund Organisation to an employee covered by provident fund contributions. It is deliberately portable: the same UAN follows the individual across employers for the whole of their working life, with each job appearing as a separate member ID linked beneath it.

That portability is what makes the UAN useful outside payroll. It is one of the few identifiers in India that ties a person to a verifiable, dated employment history held by a third party the employee cannot edit.

UAN: a worker profile carrying one consistent ID badge across several company buildings

How to find your UAN

If you are an employee and don’t know your own UAN, the free Know Your UAN service on the EPFO Member Portal retrieves it. You need the mobile number registered with EPFO and one ID: Aadhaar, PAN or your PF member ID.

Businesses that need to confirm a candidate’s UAN and employment details for many people use a UAN verification API instead, with the candidate’s consent. If the candidate only knows their mobile number, a mobile to UAN lookup finds the UAN first.

What a UAN lookup can establish

UAN: a worker profile carrying one consistent ID badge across several company buildings

Why lenders and HR platforms use it

For an unsecured lender, employment is the underwriting variable most often misstated on an application — an inflated employer name, an exaggerated tenure, or a job that ended months earlier. A UAN check tests that claim against records the applicant did not create. For staffing and gig platforms it serves a different purpose: confirming a worker’s stated history during onboarding, and detecting duplicate or borrowed identities across a large contractor base.

Practical limitations

Where the applicant knows only their mobile number, a mobile-to-UAN lookup retrieves the number before the employment details are fetched.

UAN: an employment timeline linked to one person profile

Using the UAN in verification

Because a member keeps the same UAN when they change employers, the provident fund accounts from each job are linked to it. That makes the UAN useful for employment verification, for lenders assessing salaried applicants, and for HR teams confirming a candidate’s previous employers.

Finding the UAN

Many people do not remember their UAN. It appears on payslips and in EPFO’s member services, and it can also be found from the mobile number linked to it. Starting from the candidate’s mobile number removes a common source of friction in UAN-based checks.

What to check

Limits of UAN-based checks

Not everyone has a UAN. People who have only worked for employers not covered by EPF, the self-employed and many gig workers will not have one, and that is not a sign of a problem. Design your flow with an alternative route for them.

Consent

Explain to candidates and applicants why you are checking their UAN and what you will see, and record their consent. Official information about the UAN is on the EPFO website.

Where the number is used

The number follows an employee across every job covered by the provident fund scheme, so one account holds their contribution history even when they change employers. That continuity is exactly what makes it useful in verification: a single lookup can show whether someone has a formal employment history and which employers have contributed for them.

Employers generate the number for new members when they join, or link an existing one if the employee already has it. Employees can activate it, update their KYC details and view their passbook through the member portal. Linking bank account, PAN and Aadhaar details to the account is what allows smooth withdrawals and transfers later.

For businesses, the most common uses are employment verification during hiring, income and employment checks in lending, and background checks for gig and contract roles. Always ask for consent before checking, explain why you need it, and keep only the details your decision requires. Where a candidate has never been part of the provident fund system, treat a missing record as missing information rather than a negative signal, because many genuine workers are employed informally or by very small firms.

When the check is part of a lending decision, use it alongside other signals such as bank statements and income declarations rather than on its own. Employment records can lag behind real changes, for example when someone has just joined a new employer, so give applicants a simple way to explain gaps. Recording the date of each lookup also helps, because it shows what was known at the time the decision was made.

Privacy matters here too. Employment history is personal, so tell candidates exactly which details you will look at and why, and avoid collecting more than the role or loan requires. Restrict access to the results, delete them when they are no longer needed, and make sure anyone reviewing them understands how to read them fairly.

Finally, think about timing. Checking too early can put off good candidates who have not yet decided to apply, while checking too late can delay an offer. Many teams run the lookup once a candidate has accepted an offer in principle, or once a loan application has passed initial screening, so that the step adds value without slowing anyone down unnecessarily.

Common questions

Candidates sometimes ask whether a previous employer can see the lookup. They cannot; the check reads the record without notifying past employers. Explaining this up front reassures people who are still employed and have not yet resigned.

Another common question is what happens if the record shows a gap or a different employer name. Employer names often change after mergers or rebranding, and short gaps are normal between jobs. Give candidates a simple way to explain differences, and look at the overall picture rather than any single entry, so that genuine applicants are not penalised for ordinary career moves.

Before relying on employment lookups in hiring or lending, run a handful of real cases through your process: a candidate with a long history, one who has just changed jobs and one with no formal employment record. Seeing how each looks helps reviewers read results fairly, shows where guidance for applicants needs to be clearer, and makes sure nobody is rejected simply because their work history sits outside the provident fund system.

UAN: an employment timeline linked to one person profile

Verify it with Veriqos Technologies

Verify employment against EPFO records from inside your onboarding flow:

See how these checks are applied in Gig Economy & HR Platforms, Fintech & Digital Lending.

← Back to the verification glossary