What an EPFO record actually proves about employment history

Most employment verification in India still runs on documents the candidate hands over: a relieving letter, an experience certificate, a payslip. All three are produced by the employer, held by the candidate, and trivially forgeable with an afternoon and a word processor.

The provident fund record is different. When an employer deducts PF, that contribution is filed against a Universal Account Number held by the Employees' Provident Fund Organisation. Neither the candidate nor a former manager controls that filing. It is, in practice, the closest thing India has to an independent employment ledger.

That makes it valuable. It also makes it easy to over-read.

What the record settles

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

Roughly when it started and ended. Contributions are monthly. The first and last filing bracket the employment to within a month.

Whether two employments overlapped. This is the one people underuse. Concurrent contributions from two establishments against the same UAN mean the person was on two payrolls simultaneously — which is how undisclosed second jobs surface without anyone having to go looking for them.

What the record does not settle

Designation. The EPFO filing carries no job title. A candidate who claims "Senior Engineer" and was recorded as "Engineer II" produces an identical PF trail either way. If a title matters to your decision, it has to come from the employer's HR desk, in writing.

Reporting line, scope, or performance. None of it is in the filing.

Exit reason. Resignation, redundancy and termination all look the same: contributions stop.

Anything about employment without PF. Establishments below the statutory headcount threshold are not required to contribute. Genuine employment at a small company, a startup pre-threshold, a proprietorship, or most contract and gig work may leave no PF trail at all. An absent record is not evidence of a false claim. Treating it as one produces exactly the wrong outcome: penalising candidates who worked at smaller firms.

Where dates disagree

The common discrepancy is not fabrication. It is a gap between the date a candidate remembers leaving and the date payroll stopped filing.

Someone serves notice through March, is relieved on the 31st, and the employer's final contribution posts against February. The candidate declares March. The record says February. Nobody lied.

The opposite also happens: a full-and-final settlement processed months after the last working day can leave contributions running past the real exit date.

This is why a date mismatch is a question, not a finding. The useful next step is to reconcile the PF trail against the relieving letter and, if they still disagree materially, ask the employer directly. A verification report that flags "declared exit differs from EPFO filing by four months" and stops there has done half the job.

Using it well

Treat the EPFO record as the spine of an employment check and not the whole of it:

• Use it to establish that the employment happened, and roughly when.
• Use it to detect overlaps, which little else will surface.
• Do not use it for designation or exit reason — go to the employer for those.
• Do not treat its absence as a red flag without asking why it might be missing.

The discipline that matters is separating what a source proves from what it merely suggests. A verification is only as defensible as the distance you keep between those two things.

• EPFO
• employment verification
• UAN