When a candidate's PF record is the only thing holding up an offer.
Background verification flags a PF service overlap, a UAN mismatch, or a date-of-joining/exit that doesn't match what the candidate stated. Before that becomes a rejection: these are usually genuine EPFO record issues, not evidence of dishonesty — and they're fixable through EPFO's own correction process, without your team needing to get involved in the paperwork.
Why these flags happen — and why they're usually not what they look like
Handling this at company level rather than case by case? Our employer compliance services cover PF/EPFO, ESI, labour law and licences end to end — including bulk correction of employee records that keep producing these flags.
The same handful of record issues account for most PF-related BGV flags. None of them require the candidate to have done anything wrong.
Employer name doesn't match
Mergers, acquisitions, and rebrands mean the legal entity name on an EPFO record can differ from the brand name on a résumé. Usually just needs an explanation, not a correction.
Dates don't match what was stated
The recorded date-of-joining or date-of-exit differs from what the candidate stated — sometimes a genuine error, often just an employer who never updated an exit date.
A past job doesn't show up at all
If a previous employer never properly enrolled the candidate, or used a different name or UAN, that employment can be invisible in their PF history.
A wrong or duplicate member ID appears
Someone else's — or a fraudulent — entry linked to the candidate's UAN can make their history look inconsistent to a verification check.
Overlapping dates between two employers
Two employers' contributions overlapping in EPFO's records, usually because a previous UAN was never properly delinked — the same issue that also blocks transfers and claims.
Why referring is usually the better call
These are clerical or system issues, not proof of dishonesty
A mismatched date or an overlap is almost always a record-keeping gap on someone else's end — a past employer, or EPFO's own systems — not something the candidate fabricated.
Rejecting means losing a candidate who cleared every other stage
By the time BGV runs, the candidate has already passed interviews and an offer decision. Losing them over a fixable government-record issue is a real cost.
The correction happens through EPFO's official process — not through you
Neither your team nor your BGV vendor needs to interpret PF records or chase a regional EPFO office. The candidate handles it directly, through the same portals EPFO itself uses.
No company data or liability is involved
The candidate works with us on their own UAN and records. Nothing about your systems, your BGV vendor's process, or your data is part of it.
What NidhiSetu doesn't do: I don't alter, hide, or manipulate any record to help someone "pass" a background check. What I do is help candidates correct records that are genuinely wrong through EPFO's own official routes — nothing more. NidhiSetu is an independent consultant, not affiliated with EPFO or any government body, and never asks for a UAN password, OTP, or bank login.
Have a flagged candidate?
Share the relevant guide with them directly, or reach out yourself first if you want to understand what's involved before deciding whether to refer.