Background Verification (BGV) in India: What Gets Checked and What Goes Wrong

Background verification is the least discussed way an Indian hire falls apart. The offer is signed, notice is served, the candidate resigns, and then a verification agency cannot reach a previous employer and the joining date slips by three weeks. Almost none of this is fraud. Nearly all of it is preventable admin.

What actually gets checked

Identity and address. Government ID, and sometimes a physical or digital address check. Usually the fastest component.
Education. Degree, institution and year, verified with the university or a records service. Older degrees and institutions that have since merged or closed are a common source of delay.
Employment. Dates, title and sometimes compensation, verified with each previous employer HR. This is where nearly all problems occur.
Criminal record. A court record search, increasingly standard for roles with financial or data access.
Sometimes more. Credit checks for finance roles, reference calls, and drug testing in specific industries.

The four things that actually go wrong

1. Date mismatches. A candidate writes the month they accepted; HR recorded the month they joined. Or they count their notice period as employment and the system does not. A one-month discrepancy gets flagged and reads as a red flag when it is a rounding difference.

2. Missing relieving letters. If a previous exit was handled badly, for example notice was not fully served or dues were disputed, the relieving letter may never have been issued. This is the single most common hard blocker, and it is why abandoning a notice period causes problems at the next job rather than the last one. See our notice period guide for how to exit cleanly.

3. Unresponsive or vanished employers. Startups that shut down, small firms with no HR function, or a company that simply ignores verification requests. The candidate did nothing wrong and can do nothing about it. Payslips, bank credits and Form 16 are the usual alternative evidence.

4. Title inflation. Someone called a Senior Manager day to day whose HR record says Assistant Manager. Extremely common in India, rarely dishonest, and it still generates a discrepancy flag.

Dual employment and moonlighting

Overlapping provident fund contributions from two employers are visible against a single universal account number, which is how dual employment is usually discovered. Most Indian contracts prohibit it outright, and it became a prominent issue in Indian IT once remote work made it easier to conceal.

Worth handling carefully though: an overlap of a few weeks is often a notice period running alongside an early joining date, which is a paperwork issue rather than moonlighting. Ask before concluding.

How to stop BGV costing you hires

Explain it at offer stage. Tell the candidate exactly what will be checked and which documents they will need. Surprise is what turns a small discrepancy into a defensive conversation.
Collect documents early. Relieving letters, payslips and Form 16 from previous employers, gathered before joining day rather than after.
Start as early as consent allows. Verification runs on other companies timelines, so the earlier it begins the less it delays joining.
Distinguish error from misrepresentation. Your process should allow a candidate to explain and evidence a mismatch. Auto-rejecting on any flag loses good people to admin.
Watch the notice-period window. BGV lands during the same 30 to 90 day gap in which counter-offers arrive, so a stalled check plus silence from you is a strong push back toward the current employer. See offer to join ratio.

For candidates

Keep a personal file: offer letter, relieving letter and Form 16 for every role, collected at the time rather than years later when the company may no longer exist. Write exact joining and last working dates from your documents rather than memory. If something in your history is genuinely complicated, raise it yourself early. A disclosed complication is a conversation; the same fact discovered by an agency is an investigation.

Know the joining timeline before you make the offer

Every sourced profile carries an estimated joining window and openness to move, so you can plan the notice period and verification runway instead of discovering them late. Two free searches, no card.

Start a free search →

Frequently asked questions

What is BGV and what does it check?

BGV stands for background verification. In India it typically covers identity and address, education credentials, past employment including dates and title, and often a criminal record check. Some employers add credit checks for finance roles and reference calls. It is usually run by a third-party agency, either before joining or in the first weeks after.

How long does background verification take in India?

Commonly one to three weeks, but the variance is enormous and it is almost always the previous employer that decides. Large companies with automated verification desks respond quickly; small firms, companies that have shut down, and employers with no HR function can take weeks or never respond at all. Start the process as early as the candidate consents to, rather than on joining day.

What are the most common reasons BGV fails in India?

Very rarely outright fabrication. The usual causes are date mismatches, where a candidate writes the month they accepted rather than the month HR recorded; a missing relieving letter because the previous exit was messy or notice was not served; an employer that has closed or will not respond; and title differences between what the candidate was called day to day and what appears in the system.

What is dual employment and why does it show up in BGV?

Dual employment means being on two payrolls at once. It surfaces because provident fund records are linked to a single universal account number, so overlapping contributions from two employers are visible. Most Indian employment contracts prohibit it, and it is the discovery route for moonlighting. Overlapping dates can also appear innocently when a notice period overlaps a new joining date, which is worth clarifying rather than assuming the worst.

Can you be rejected after joining because of BGV?

Yes. Offers and joining are usually conditional on satisfactory verification, so an adverse finding can lead to termination even after someone has started. That is precisely why the process should be front-loaded: a candidate who discovers a documentation problem in week three has already resigned elsewhere, which is a bad outcome for everyone.

How should recruiters handle a BGV discrepancy?

Treat it as a question first. Ask the candidate to explain, and ask for supporting documents such as payslips, offer and relieving letters or a Form 16. Genuine errors are common and easily evidenced. Reserve adverse action for deliberate misrepresentation of something material, and make sure your process distinguishes the two rather than auto-rejecting on any mismatch.