Chat on WhatsApp
Home › Blog › How to Verify Past Employment in India: Steps and Red Flags

How to Verify Past Employment in India: Steps and Red Flags

A candidate’s employment history is the single most fabricated section of an Indian CV. Not the degree — degrees are hard to fake convincingly and easy to check with the university. The soft target is the middle of the career: a nine-month gap papered over with a company nobody has heard of, a “Senior Manager” title that was actually Assistant Manager, a last-drawn salary inflated by thirty per cent because the next offer will be benchmarked against it. None of it shows up in an interview. All of it shows up in the first quarter, when the person cannot do the job the CV described.

This guide deals only with employment verification — confirming that a person worked where they say they worked, when they say they worked there, in the role they claim. It sits inside the wider background verification process but deserves separate treatment, because the methods, the evidence and the failure modes are specific. As a recruitment agency in Mumbai that has completed 5,000+ placements since 2001, we have seen most variations. This is general guidance only, not legal advice.

Why employment fraud is so common in India

The incentives are badly aligned. Salary is benchmarked on last-drawn CTC, so inflating the previous figure inflates the next one. Titles inflate because Indian designation ladders vary wildly between companies — a “Vice President” in a 40-person startup and one in a multinational bank are different species. Gaps carry stigma, so candidates fill them rather than explain them. And a supporting industry exists: services that will sell an experience letter, a payslip PDF and a phone number that answers as “HR” for a modest fee.

The most common patterns, roughly in order of frequency:

The verification methods, ranked by what they actually prove

No single check settles everything. Documentary evidence proves payroll existed; human confirmation proves role and conduct. Use at least one of each.

Method What it proves Reliability Typical effort
UAN / EPFO passbook history Employer names and contribution months across the career, from the employer’s own filings Very high for PF-covered roles Low — candidate-shared, minutes
Form 16 / Form 26AS Employer TAN, salary paid and tax deducted for a financial year Very high Low — candidate provides
Payslips (3-6 months, with bank credits) Salary structure and that money genuinely arrived High when cross-checked against bank statement Low to medium
Official HR / payroll confirmation Dates, designation, exit reason, re-hire eligibility High, but response rates are patchy Medium — days to weeks
Background verification vendor All of the above, executed and documented at scale High, depends on vendor discipline Low for you, 5-12 working days
Reference call with ex-manager Actual scope, performance, working style Medium — informative but partisan Medium
MCA / GST check on the employer entity That the company exists, is registered and files High for existence, silent on the candidate Low — public databases
Experience / relieving letter alone Very little on its own Low — easiest artefact to forge Low

How UAN-based verification works

Every employee covered by the Employees’ Provident Fund scheme has a Universal Account Number that stays with them across jobs. The passbook, accessible through the EPFO member portal, lists each establishment that made contributions and the months in which they were made. Because the entries are generated by employers filing their own returns and paying real money, they are difficult to fabricate retrospectively.

Ask the candidate to share their service history or passbook view themselves, with consent, rather than attempting to access it on their behalf. In practice the cleanest request is a screen-share or a downloaded PDF during the offer stage.

What it proves: which establishments contributed for this person and over which months. That is enough to expose ghost employers, stretched tenures, hidden stints and most overlaps in one document.

What it does not prove: designation, reporting line, scope, performance or reason for exit — none of which EPFO records. Nor does it cover everyone. Small establishments below the coverage threshold, genuine consultants on professional-fee contracts, employees who joined above the wage ceiling and were never enrolled, and overseas stints will all show gaps that are entirely legitimate. A missing UAN entry is a question to ask, not a conclusion to draw. See our guide to PF, ESI and gratuity obligations for who is covered.

Please note: this article is general guidance for employers, not legal advice. Requirements around consent, data handling, background checks and employment records vary by state and by sector, and both the law and the underlying rules change over time. All thresholds, timelines and processes described here are indicative and current as written. Confirm your specific position with a qualified employment lawyer or compliance consultant before adopting or changing a verification policy.

Red flags worth pausing on

Handling a discrepancy fairly

Not every discrepancy is fraud. HR systems record a payroll designation that differs from the working title. A company changed its registered name after a merger. A candidate joined on 3 April and the record says 1 April. Treat the finding as an input, not a verdict.

  1. Verify the verification. Vendor errors are common — wrong entity, wrong spelling, contact who no longer works there. Re-run before acting.
  2. Put it to the candidate in writing. State precisely what was claimed, what was found, and give a reasonable window — three to five working days is customary — to respond with evidence.
  3. Assess proportionately. A title recorded as “Manager” instead of “Senior Manager” is not a payslip forged to inflate salary by 40 per cent. Grade the response to the seriousness and to the relevance of the role.
  4. Apply a consistent policy. Decide in advance which categories are disqualifying and apply the same rule to every candidate. Inconsistency is where discrimination claims start.
  5. Document the decision and the reasoning. Whatever you conclude, the file should show what you found, what the candidate said, and why you decided as you did.

If you do withdraw an offer, do it in writing, cite the specific ground, and keep the language factual. Avoid sharing adverse findings with third parties or informal industry networks.

Consent and privacy obligations

Verification runs on personal data, and increasingly on sensitive financial data. Written, informed consent should be obtained before checks begin — a signed authorisation naming the categories of check, who will conduct them, and how the results will be used and retained. Blanket consent buried in an offer letter is weaker than a separate, clearly worded form; make consent a distinct step in your recruitment process.

Beyond consent: collect only what the role justifies, restrict access to the file, retain results for a defined period rather than indefinitely, and impose written data-protection obligations on any vendor you use. India’s data protection framework continues to evolve, and sector regulators — banking and financial services in particular — layer their own requirements on top. Have your consent wording and retention schedule reviewed by counsel rather than copying a template.

Where verification fits in the hiring timeline

Run employment verification after the offer is accepted and before the joining date, with the offer expressly conditional on satisfactory checks. Starting earlier risks alerting a current employer; starting later leaves you discovering a problem on day one.

Build the calendar backwards. Verification typically takes five to twelve working days, and ex-employer responses are the slow leg. Against a 60 or 90-day notice period, that fits comfortably — but only if consent is signed the week the offer is accepted rather than a fortnight before joining. Sequence it alongside your offer letter issue, not after it.

Frequently asked questions

Can we verify a candidate’s UAN without their involvement?
The appropriate route is to ask the candidate to share their own passbook or service history under written consent. Accessing an individual’s records without informed consent raises data protection and privacy concerns. Candidates who have nothing to hide usually share readily; reluctance at this stage is itself informative. Take advice on your consent wording before making this a standard step.
A gap appears in the PF record but the candidate has an experience letter. What now?
Ask for the explanation first. Legitimate reasons are common — a small establishment outside PF coverage, a consultancy engagement, an overseas posting, or a period the employer failed to file for. Then seek a second, independent piece of evidence for that period: Form 16, Form 26AS, or bank credits matching salary. One unexplained gap with no corroborating document is a genuine concern; one explained gap with supporting evidence usually is not.
Is it lawful to withdraw an offer over a verification discrepancy?
Generally, where the offer was expressly conditional on satisfactory verification, the discrepancy is material, and the candidate was given a documented opportunity to respond. Withdrawing on a trivial or unrelated finding, or without following your own stated process, carries more risk. Because the position depends on your offer wording and the facts, confirm with an employment lawyer before withdrawing.
How far back should employment verification go?
Common market practice is the last two or three employers, or roughly seven to ten years, whichever is shorter — with the current and immediately previous employer always covered. Regulated sectors such as banking and financial services often require more. Set the scope by role and sector, write it into policy, and apply it consistently across candidates.
Should we still call the previous manager if the documents check out?
Yes, for mid-level and senior roles. Documents establish that employment happened; a reference call is the only practical way to learn what the person actually did, how they worked with others and why they left. Treat it as qualitative input rather than proof, ask about specific situations instead of general impressions, and weigh it knowing that referees are rarely neutral.

Getting verification right without slowing the hire

Employment verification fails in two directions. Skip it and you inherit a mis-levelled hire, a salary benchmarked on fiction, or a dual-employment problem. Over-engineer it and you lose good candidates to employers who moved faster. The balance is a defined scope, consent captured early, documentary and human evidence used together, and a written policy for handling discrepancies before you need one.

Ace Corporate Services has placed candidates for more than 500 client companies across 15+ industries since 2001, and verification discipline is built into how we run every mandate — from permanent staffing to executive search, where a mis-verified senior hire is the costliest mistake of all. To discuss your verification standards or hand the process to a team that runs it daily, call +91-22-67554705, email info@acecorpsers.com, or contact us.

Need hiring help right now?

Talk to a senior recruitment consultant today. Free consultation.

Post a Hiring Requirement →

Related reading

Leave a Reply

Your email address will not be published. Required fields are marked *