Reading an EPFO record properly

Employment verification in India usually runs on artefacts the candidate supplies: a relieving letter, an experience certificate, a payslip. All three are produced by the employer, held by the candidate, and forgeable in an afternoon.

The Employees' Provident Fund Organisation record is different in kind. When an employer deducts provident fund, that contribution is filed against a Universal Account Number under an establishment code. The candidate does not control the filing, and a former manager cannot amend it after the fact. It is the closest thing India has to an independent employment ledger.

That independence is exactly why it gets over-read. A record this reliable invites conclusions it cannot support.

What the data actually is

A UAN is a permanent number issued to an employee, stable across employers. Under it sit member IDs, one per establishment. Each member ID carries monthly contribution entries and a date of joining, with a date of exit once the employer files one.

Three properties matter for interpretation:

Contributions are monthly, not daily. The finest resolution you get is a month. A record showing contributions from April to September establishes employment across those months, not that the person started on 1 April.

Exit dates are filed by the employer, and often late. A missing exit date does not mean the person is still employed. It very often means nobody at the previous employer completed the filing.

Not every employment appears. Establishments below the statutory employee threshold are not covered. Nor are most genuine contractors, employees drawing above the wage ceiling whose employer chose not to enrol them, and much of the informal economy. Absence from EPFO is not absence of employment.

That last point is the single most common misreading, and the one that does the most damage to candidates.

What the record settles

That an employment relationship existed. A contribution filed by an establishment against a UAN is strong evidence that the establishment was paying that person, and it is hard to fabricate.

Approximately when it started and ended. The first and last contributions bracket the employment to within a month either way.

Whether two employments overlapped. This is the finding documents cannot produce. Concurrent contributions from two establishments in the same months is a factual overlap, visible on the record, invisible on any letter either employer would write.

What it does not settle

Designation. There is no job title in the record. A candidate who claims to have been a Senior Engineering Manager and was in fact a Senior Engineer has made a claim EPFO cannot test.

Reason for exit. Resignation, redundancy and termination for cause look identical. Nothing in the filing distinguishes them.

Actual compensation. The wage on which PF is calculated is capped and frequently reported at the statutory ceiling rather than at real salary. Reading it as salary produces a wrong number with an authoritative source, which is worse than having no number.

Whether the person did the job well, or at all. A contribution proves payroll, not performance.

Reading the signals without over-reading them

A gap. Employment gaps in the record are common and mostly uninteresting. They can mean unemployment, but they equally mean a period at an uncovered establishment, genuine contracting, study, illness, or caregiving. Treat a gap as a question for the candidate, never as a finding.

An overlap. Concurrent contributions are a real signal and worth pursuing, but the innocent explanations are ordinary: a notice period served while the new employer had already started contributing, or a late exit filing overlapping the next joining. An overlap of one or two months at a job boundary is usually administrative. A sustained overlap across many months, at two unrelated establishments, is dual employment and worth a direct conversation.

A missing exit date. Nearly always an unfiled exit, not ongoing employment. Confirm against the next employer's first contribution rather than treating it as a discrepancy.

A tenure shorter than declared. The most common genuine finding. A candidate who declares three years where the record shows fourteen months of contributions has a real gap to explain — though check first whether the first months fell under a different member ID, which happens when an establishment restructures.

No record at all. Not a finding. It means EPFO cannot verify this employment, and the check has to move to a second channel: employer outreach, or documentary evidence corroborated some other way. Reporting "not found" as "not verified" implies a conclusion the data does not support.

Consent, and what you are actually allowed to pull

Access to UAN-linked data requires the candidate's participation and their specific consent — under the DPDP Act, consent to this purpose, not a blanket authorisation in an offer letter. The candidate supplies the UAN and authenticates. There is no legitimate route that bypasses them, and a vendor offering one is describing a data source you should ask hard questions about.

Practically, this means the check has a candidate-side step that can stall. Design for it: a candidate who has not authenticated is an insufficiency to chase, not a red flag to record.

How to write the finding

The output of an EPFO check should distinguish three things, and most reports collapse them into one:

• Declared: what the candidate stated.
• Verified: what the contribution record shows, with the establishment name and the month range.
• Discrepancy: the difference, if any, described precisely enough that someone can act on it.

"Employment not verified" is not a finding. "Declared April 2019 – March 2022; contributions filed by the establishment from September 2019 to March 2022; five months at the start of the declared period are not covered by any filing" is. The first invites the reader to invent a reason. The second tells them exactly what to ask the candidate.

That distinction is the whole discipline. The record is unusually good evidence. It deserves to be reported as evidence, not as a verdict.

• EPFO
• UAN
• employment verification
• technical