There’s a pattern that plays out in hiring teams across India, more often than anyone wants to admit.
A candidate comes in looking great on paper. Six years of experience, two solid companies, a title that fits the role perfectly. You send verification requests to both employers. One comes back incomplete. The other doesn’t come back at all. Three follow-up emails later, your hiring manager has already made the decision in their head, the candidate is getting impatient, and you’re sitting there hoping that no news is good news.
You approve the hire. Everything seems fine — until it isn’t.
This is not a failure of effort. It’s a failure of method. And it keeps happening because most employment verification in India still depends on one company asking another company a favour. When the favour doesn’t come through, corners get cut.
UAN-based employment verification exists to fix exactly this problem.
First, What Even Is a UAN?
UAN stands for Universal Account Number. It’s a 12-digit number that EPFO — the Employees’ Provident Fund Organisation — assigns to every salaried employee whose employer contributes to their Provident Fund.
Here’s the part that makes it powerful for verification: the UAN never changes.
A person can change jobs five times in ten years. Their designation changes. Their salary changes. Their employer changes. But the UAN stays the same — and every employer they’ve ever worked with gets linked to that same number through their PF contributions.
Think of it like a permanent employment ledger, maintained by the government, that records where a person worked and for how long — not based on what they told you, but based on what their employer actually paid into their PF account every month.
That distinction matters more than it sounds.
What Does a UAN Check Actually Reveal?
When a UAN-based employment verification is run — with the candidate’s consent — the system pulls their EPFO record and maps out their full employment history. What comes back includes:
Every employer linked to that UAN
The joining and exit dates at each company
The monthly contribution pattern — which reflects actual active employment
Whether there are any overlapping periods across two employers
That last point is where things get interesting.
If a candidate’s EPFO record shows contributions coming in from two different companies during the same months, that’s dual employment — right there in the data, no detective work required. No inference. No gut feeling. Just a clean flag that something doesn’t match what the resume says.
This became a particularly hot topic post-2022, when moonlighting started making headlines in India’s tech sector. UAN verification turned out to be one of the most reliable ways to catch it — because the PF data doesn’t lie, and it doesn’t wait for an HR team to respond.
Why Traditional Employment Verification Falls Short
The standard approach to employment verification in India goes something like this: reach out to the candidate’s previous employer, ask HR to confirm dates and designation, and wait.
The waiting is where everything falls apart.
Previous employers have no legal obligation to respond. Their HR teams are busy. Emails get lost. Some companies have a policy of not confirming anything in writing. And the smaller the company, the more likely it is that the HR contact from three years ago has long since moved on.
This creates a verification gap that’s wide enough to drive a fraudulent resume through.
UAN verification sidesteps all of that. It goes directly to a government database. There’s no intermediary to chase, no inbox to follow up on, no goodwill required. The data either matches or it doesn’t — and you know within seconds, not days.
The cost difference alone is significant. Traditional employer outreach — calls, emails, follow-ups — can cost several hundred rupees per employer, per candidate. UAN verification costs a fraction of that and takes a fraction of the time.
The Resume Fraud Problem Is Bigger Than Most Teams Acknowledge
Here’s an uncomfortable truth about hiring in India: resume inflation is common, resume fabrication is not rare, and most of it goes undetected because verification processes weren’t designed to catch it.
Dates get stretched. Gaps get hidden. Tenures get rounded up. A 14-month stint becomes “2019 to 2021.” A junior title becomes a senior one. Sometimes an employer is listed that the candidate barely worked at — or never worked at at all.
The reason this succeeds is simple. If verification depends on the previous employer confirming the dates, and that employer never responds, the candidate’s version of events stands by default.
UAN verification removes the candidate’s version from the equation entirely. The EPFO record is what it is. If someone claims they worked at a company from 2020 to 2023, but the PF contributions show they stopped in 2021, that discrepancy surfaces immediately — regardless of what the resume says, and regardless of whether anyone picks up the phone.
What UAN Verification Doesn’t Cover — And Why That Matters
Good verification is honest about its limits. UAN-based checks are powerful, but they’re not everything.
The EPFO database records employer names and tenure. It does not record designations. So if the question is whether someone actually held the title they’re claiming — Head of Product vs. Product Manager, for example — UAN verification alone won’t confirm that. You’d still need direct employer outreach for designation-level accuracy, especially for senior or client-facing roles.
Similarly, UAN data only covers employment in India. Candidates with stints abroad, or those who worked in the unorganised sector where PF wasn’t applicable, will have gaps in their EPFO record that don’t necessarily indicate fraud. Context matters.
The smart approach is to treat UAN verification as your first layer — fast, cheap, government-sourced — and use traditional verification selectively for the gaps and senior hires where designation confirmation is genuinely critical.
How This Changes the Hiring Process in Practice
For HR teams running high volumes, the operational impact of UAN verification is significant.
Instead of opening every candidate file with a series of emails going out and a waiting period beginning, you run the UAN check first. For the majority of candidates, it either confirms the history cleanly or flags a discrepancy immediately. Either way, you know where you stand within minutes.
The cases that need deeper investigation — date mismatches, overlapping employers, contributions that don’t add up — get identified early, before the candidate has progressed too far in the process. That saves time on both sides.
For the candidates who check out cleanly, the rest of the background verification can proceed without the employment history hanging as an unresolved variable.
It’s a small shift in sequence. The downstream impact on hiring velocity and accuracy is substantial.
The Larger Point About Trust in Hiring
Employment verification exists because hiring involves extending trust — to someone you’ve known for a few weeks, based largely on what they’ve told you about themselves.
The UAN is a check on that trust. Not a cynical one, not an adversarial one — just a factual cross-reference against a record that neither party controls. Most candidates have nothing to hide, and for them, it’s a formality that passes in seconds. For the ones who do, it’s the reason the process exists.
In a hiring landscape where resume fraud has become easier to commit and harder to catch the traditional way, having a government-sourced data point to anchor employment verification is not just useful — it’s increasingly necessary.
The information exists. It’s accurate. It’s accessible. The only question is whether verification processes are built to use it.
Leave a Reply