Can I verify a candidate's employment history in India without their consent?

No. Under the DPDP Act, employment, identity, and financial records are personal data and need a lawful basis - in practice, the candidate's informed, purpose-specific consent. The reliable way to check EPFO/UAN history, PAN-linked tax records, or Aadhaar is to have the candidate share their own records after agreeing to the check. Aadhaar in particular cannot be mandated by a private employer.

How does EPFO and UAN help catch moonlighting or dual employment?

A UAN links all of a candidate's EPF accounts. If two different establishments are contributing to the same UAN in the same months, the person was formally employed in two places at once - the cleanest evidence of dual employment. Overlapping salary income reported against one PAN in Form 26AS or AIS is a second corroborating signal.

What does an EPFO check NOT prove?

EPFO only covers establishments within its scope. Very small companies, genuine contractors and consultants, government roles under separate schemes, and off-the-books pay will not appear. So missing EPFO records are not proof of a lie - that stretch of history just needs a different source. EPFO also records the employer and dates, not the exact job title or seniority.

How do I spot a fake experience certificate in India?

Cross-check the employer named on the certificate against the candidate's EPFO/UAN contribution history and confirm the dates match. Then verify the issuing company actually exists and operates using EPFO establishment search and its registration details. Fake certificates usually fail one of these: the employer never contributed to the candidate's PF, or the company cannot be found at all.

Does EnTeam verify employment history in the US?

Not yet. Government verification - PAN, Aadhaar, and EPFO employment history - is live for India today, with consent built into the flow. US verification is on the roadmap and not live; we will say so plainly when it ships. Interviews are currently English only.

How to Verify Employment History in India: EPFO, UAN, PAN, and Moonlighting Checks

If you hire in India, you already know the offer letter and the experience certificate are the easy part to fake. Learning how to verify employment history in India means going past what the candidate hands you and checking it against records they cannot edit: EPFO contribution history tied to their UAN, tax records linked to their PAN, and identity confirmed by Aadhaar. Done with consent, these government sources tell you whether the tenure on the resume actually happened, whether the employer was real, and whether two jobs were running at once.

This guide covers what each check proves, what it does not, how moonlighting and fake experience certificates surface, and the consent rules you have to follow under the DPDP Act. None of it is exotic. Most of it is free or cheap. It just takes time and discipline most hiring teams do not have.

The scale of resume fraud in India: what the data says

Resume fraud in India is common enough that “verify everything” is the sane default, not paranoia. Background-check vendors operating in the country routinely report employment-related discrepancies in a meaningful share of the checks they run - inflated titles, stretched dates to hide gaps, employers that turn out not to exist, and full experience certificates bought from operators who sell them as a service. Tenure padding is the most frequent: a candidate who worked somewhere ten months claims eighteen, or compresses a six-month stint that ended badly into “freelance.”

What this means for your reqs is simple. The cost of a bad verification is not abstract. You onboard someone whose “5 years on Java” was 5 years on paper and 18 months in practice, or who is quietly still drawing a salary somewhere else. The checks below are how you catch that before the offer, not after.

What EPFO and UAN reveal: tenure, employer records, and dual employment

For salaried roles, the Employees’ Provident Fund Organisation (EPFO) is the single most useful source. Every formal employee covered by EPF gets a Universal Account Number (UAN) - one number that stays with them for life and links every PF account across every employer.

When a candidate shares their UAN passbook or service history, you can see:

Each establishment (employer) name that contributed to their PF
Date of joining and date of exit per employer
Monthly contributions, which confirm the job was active, not just claimed
The sequence of jobs across their career, in the employer’s own filing

This is the closest thing to a verifiable career timeline India offers. If the resume says “Infosys, Jan 2020 - Mar 2023” and the passbook shows contributions from that establishment across those dates, the tenure is real. If the passbook shows the candidate exited eight months earlier than the resume claims, you have your answer.

The strongest signal EPFO gives you is overlapping contributions. If two different establishments are contributing to the same UAN in the same months, the person was formally employed in two places at once. That is the cleanest evidence of dual employment you will find.

The honest limit: EPFO only covers establishments within its scope. Very small companies below the employee threshold, genuine contractors and consultants, government roles under separate schemes, and people paid off the books will not show up. So an absence of EPFO records is not proof of a lie - it just means that stretch of history needs a different source.

What PAN and Aadhaar confirm - and what they don’t

PAN and Aadhaar are about identity and income, not directly about your job title.

PAN (Permanent Account Number) confirms the person’s tax identity is real and valid, and that the name matches. More usefully, the candidate’s own tax records - Form 26AS and the Annual Information Statement (AIS) - show TDS deducted by employers and salary income reported against their PAN. When a candidate shares these, two employers paying salary in the same financial year is another corroboration of overlapping employment, and the figures give you a sanity check on claimed compensation.

Aadhaar confirms the person is who they say they are. It does not say anything about where they worked. It is an identity anchor, not an employment record.

Check	What it confirms	What it does NOT confirm
UAN / EPFO	Employers, joining/exit dates, active tenure, overlapping jobs	Roles outside EPF scope; exact job title or seniority
PAN (26AS / AIS)	Tax identity, salary/TDS by employer, overlapping income	Job title; non-salaried or cash income
Aadhaar	Identity of the person	Anything about employment

Notice the gap none of them closes on their own: job title and seniority. EPFO records the employer and the dates, not whether someone was a “Lead” or a “Senior.” For that you still need the experience letter, reference checks, and an interview that actually probes the work.

Catching moonlighting and fake experience certificates against government records

Here is a practical sequence for a moonlighting check in India and for testing an experience certificate against records the candidate cannot rewrite.

Step-by-step verification checklist:

Collect with consent. Ask the candidate to share their UAN service history / passbook and, where relevant, Form 26AS or AIS. Record that they agreed and why.
Match employer names. Cross-check every employer on the resume and on each experience certificate against the establishment names in the EPFO history.
Match the dates. Confirm joining and exit dates line up with contribution months. Flag any stretch with no records for a separate explanation.
Scan for overlaps. Look for two establishments contributing in the same months (EPFO) or two employers reporting income in the same year (26AS/AIS). That is your dual-employment signal.
Verify the employer exists. Use EPFO’s establishment search and the company’s own registration details to confirm the issuer of an experience certificate is a real, operating entity - a common tell for fake certificates is an employer with no findable footprint.
Reconcile the story. Where records and resume disagree, ask the candidate directly. Sometimes there is a clean explanation (a consulting stint, a company below EPF scope). Sometimes there is not.

A fake experience certificate usually fails at step 2 or step 5: the named employer never contributed to the candidate’s PF, or the company cannot be found at all. Moonlighting shows up at step 4. The method is unglamorous, but it works because it compares the candidate’s claims to filings made by someone else.

Consent and DPDP: why verification must be consent-based

You cannot just pull these records. India’s Digital Personal Data Protection (DPDP) Act treats employment, financial, and identity data as personal data that requires a lawful basis - in practice, the candidate’s informed consent for a stated purpose. Verification has to be consent-based, the candidate has to know what you are checking and why, and you should hold the data only as long as you need it.

A specific point that trips people up: Aadhaar cannot be mandated by a private employer as the price of being considered. Its use is voluntary and consent-driven, and you should offer alternatives. Build verification so the candidate opts in and shares their own records, rather than you reaching around them. That is both the compliant path and, conveniently, the one that actually gives you authentic data.

A short compliance baseline:

Get explicit, purpose-specific consent before any check.
Tell candidates which sources you will use (EPFO/UAN, PAN, Aadhaar) and why.
Do not make Aadhaar mandatory; offer another way to confirm identity.
Limit access, store securely, and delete when the purpose is done.

Or stop running it yourself: a shortlist that’s already government-verified

All of the above is doable in-house. It is also slow, and it competes with every other thing a recruiter has to do that week. The realistic failure mode is not getting the method wrong - it is skipping it under deadline pressure.

That is the gap EnTeam closes. Hand over a role and its requirements, and the candidates that reach your req arrive already screened against your rubric, AI-interviewed under proctoring (our integrity checks flag tools like Cluely, Parakeet, and screen-reader assistants), and government-verified in India today - PAN, Aadhaar, and EPFO employment history, with consent built into the flow. So the tenure, the identity, and the dual-employment check are done before you read the shortlist. US verification is on the roadmap, not live yet - we will say so plainly when it ships. Interviews are English only today.

If you want to see what a government-verified shortlist looks like on one of your live roles, Cohort 02 includes 25 free pilot interviews, and after that it is pay-as-you-go, billed per completed interview. No long-term contract to find out whether the candidates hold up.