Previous employment verification: what it confirms and what it cannot

What it confirms

An employment verification is a question put to the organisation that employed the person. In India, the answer almost always covers three things.

Dates. The period the person was on the payroll. This is the most reliably answered field and the one most often out by small amounts, because a candidate remembers when they joined and payroll records when they were first paid.

Designation. The title on record. Worth noting that internal titles and the titles people use externally frequently differ, and that a mismatch here is usually a translation problem rather than an inflation problem. It is inflation when the gap is a level, not a wording.

Exit status. Whether the person resigned, was terminated, or left on other terms, and increasingly whether they would be eligible for rehire. This is the field with the most variation between employers, and the one buyers most often expect to get and do not.

Some employers will confirm more: reporting manager, work location, employment type, or last drawn compensation. Many will not. What comes back is set by the former employer's disclosure policy, and no provider can change that policy from the outside.

What it cannot confirm

Being precise about the limits of this check is the fastest way to stop it disappointing people.

• Performance. No employer will grade a former employee for a stranger. If you want a view on how someone worked, that is a reference check, which is a different check with a different method and a named referee.
• The full reason for an exit. Even employers who confirm "resigned" or "terminated" will rarely go behind that word.
• Anything undocumented. A warning delivered verbally, a project that went badly, an informal arrangement: none of it is on the record and none of it will come back.
• Employment that was never on the books. Cash-paid or informal work leaves no record for anyone to confirm. Its absence is not evidence that the candidate did not do it.

Why the candidate's documents are not the check

Nearly every candidate arrives with an offer letter, a relieving letter and a payslip or two. It is tempting to treat that as proof and skip the check. It is not proof, for a reason that has nothing to do with the candidate's honesty: documents in a candidate's possession are documents somebody could have produced.

Relieving letters and experience certificates are among the most commonly forged documents in Indian hiring, and the forgeries are frequently good. There is an entire cottage industry supplying them, complete with a phone number that answers as the HR department. Reading the letterhead tells you nothing that the letterhead did not intend to tell you.

What the documents are genuinely useful for is routing. An offer letter names the entity, the location and often an employee code, and that is what lets a verification reach the right HR desk at a company with fourteen registered entities. Use the documents to find the record holder, then ask the record holder.

Why some employers will not answer

This is the single largest source of delay and of "unable to verify" outcomes, and it is worth understanding because it is almost never about the candidate.

What matters here is what a provider does with the silence. The honest answer is to report it as unanswered, show the attempts made, and offer whatever independent corroboration exists. The dishonest answer, which does happen, is to mark it verified and move on. That is the difference the provider evaluation checklist is built to expose.

Where EPFO records change the picture

India has something most countries do not: a central, portable record of formal employment in the shape of the Universal Account Number and the EPFO member record behind it. For verification this is unusually valuable, because it is independent of the former employer's willingness to co-operate.

Where a candidate has a UAN, the member record can show which establishments made provident fund contributions on their behalf and for which months. That does three useful things at once. It corroborates dates without asking the employer. It survives the employer closing down. And, because it lists every contributing establishment, it can surface an employment the candidate did not declare, which is the basis of most moonlighting findings.

The limits matter too. It only covers establishments within the EPF scheme, so smaller employers below the threshold and genuinely informal work will not appear. A gap in contributions is therefore not evidence of a gap in employment. The detail is in UAN and EPFO records, and the check itself is UAN verification.

The current employer problem

Candidates routinely ask that their current employer not be contacted, and they are right to. Being asked about by a verification agency is how a resignation becomes public before the candidate is ready.

There are two workable answers. Verify the current employment after the candidate has resigned, which most employers accept as a condition of the offer. Or confirm it through EPFO contribution records, which shows the establishment and the period without anyone at the company being contacted.

What matters is that the consent record is explicit about it: which employers may be contacted, and at what point. A blanket consent that is silent on the current employer is the setup for the worst kind of avoidable mistake.

Deciding how far back to go

Most employers settle on the last two or three employers, or a fixed number of years. Both work. What matters is that the span is written down and applied to everyone considered for the role, for the same reason the whole package should be scoped by role rather than by candidate.

Going further back has diminishing returns. Companies close, records are archived, HR teams turn over, and the relevance of a role from a decade ago to the hire in front of you is limited. Each additional employer also adds a source that can be slow to answer, which slows the whole case.