Why Employees Fail Background Verification in India: 12 Common Reasons, What Triggers Red Flags, and How Employers Should Respond
Employees fail background verification in
India when the information they provided during the hiring process does not
match the records found in government databases, previous employer records, or
educational institution databases, with the most common failures being PAN name
or date of birth mismatches discovered through Income Tax Department database
checks, Voter ID discrepancies flagged through Election Commission database
verification, fabricated employment history exposed through UAN and EPFO
records, fake or exaggerated educational qualifications, and expired or
suspended driving licences found through transport authority database checks,
all of which can be identified in minutes through digital verification
platforms like Compose1 Verify.
If you are an employer running background
checks on new hires, you have encountered verification failures. Industry data
suggests that 10 to 25 percent of candidate profiles in India contain at least
one discrepancy that is flagged during background verification. Some of these
are innocent errors (a name spelled differently on two documents). Some are
deliberate fabrications (a fake degree certificate, an invented employer). Some
are omissions (an employment gap that hides a termination).
Understanding why employees fail
background verification helps employers in two ways. First, it helps you design
a verification process that catches the failures that matter. Second, it helps
you distinguish between honest mistakes and deliberate fraud, so you can
respond appropriately to each.
If you are a candidate who has failed or
is worried about failing a background check, this guide explains what triggers
failures and what you can do about genuine discrepancies in your records.
Reason 1:
PAN Card Name or Date of Birth Mismatch
How common: Very common. This is one of
the most frequently flagged discrepancies.
What
happens: The employer runs the candidate’s PAN
number through a verification platform like Compose1 Verify. The platform checks
the PAN against the Income Tax Department database. The name or date of birth
registered with the PAN does not match what the candidate provided on their
application or resume.
Why
it happens:
The candidate’s name on the PAN card was
registered years ago with a different spelling, a middle name, or a shortened
version. For example, the PAN shows “Rajeshwar Kumar Singh” but the candidate’s
resume says “Rajesh Singh.” Or the PAN shows “Mohammed Abdul Rasheed” but the
resume says “Abdul Rasheed.”
In some cases, the date of birth on the
PAN is different from what the candidate uses on other documents. This happens
when the PAN was applied for using a school certificate with an incorrect DOB,
while other documents use the correct DOB.
In deliberate fraud cases, the PAN
belongs to someone else entirely. The candidate borrowed or purchased a PAN
card to create a false identity.
How
employers should respond:
Minor spelling variations (Rajesh vs
Rajeshwar, missing middle name) are usually innocent. Ask the candidate to
explain the discrepancy. If the explanation is credible and Voter ID
verification confirms the same core identity, proceed with hiring.
A completely different name or DOB on the
PAN is a serious red flag. Cross-check with Voter ID verification through
Compose1 Verify. If both PAN and Voter ID show different identities, the
candidate is likely using fraudulent documents.
Reason 2:
Voter ID Cross-Record Mismatch
How common: Moderately common.
What
happens: The employer verifies the candidate’s
Voter ID through the Election Commission database on Compose1 Verify. The name, age, or
father’s name on the Voter ID does not match the information on the PAN or the
candidate’s application.
Why
it happens:
The Voter ID was registered at a
different life stage or address, with different name formatting. Father’s name
variations are common (initials vs full name, spelling differences).
In fraud cases, the Voter ID belongs to a
relative or is fabricated. The candidate uses one person’s PAN and another
person’s Voter ID to create a composite identity.
How
employers should respond:
Compose1 Verify’s cross-record analysis
automatically compares PAN and Voter ID results. When both databases confirm
the same person (matching name and approximate DOB), identity is established
despite minor formatting differences. When the two databases show fundamentally
different identities (different names, significantly different DOB), this is a
strong indicator of identity fraud.
Reason 3:
Fabricated Employment History
How common: Very common. This is one of
the top reasons for BGV failure across industries.
What
happens: The candidate claims experience at
companies they never worked for, or claims a higher designation or longer
tenure than actual. When the employer checks UAN records through Compose1
Verify, the EPFO database shows a different employment history than what the
candidate claimed.
Why
it happens:
Candidates add fake employers to fill
employment gaps. A candidate who was unemployed for 8 months adds a “consulting
assignment” at a company that does not exist.
Candidates inflate tenure. They worked at
a company for 11 months but claim 2.5 years to meet the “minimum experience”
requirement for the new role.
Candidates inflate designations. They
were a “Sales Executive” but claim “Regional Sales Manager” on their resume.
Candidates omit employers. They were
terminated from a job and leave it off their resume entirely, creating a gap
that they fill with a fake employer.
How
employers should respond:
UAN verification through Compose1 Verify
shows the candidate’s actual EPFO contribution history, including employer names
and contribution periods. Compare this against the resume. Look for: companies
on the resume that do not appear in UAN records, significant differences in
employment dates, and gaps in EPFO contributions that correspond to claimed
employment periods.
A candidate who inflated their
designation by one level but has the correct employer and tenure may be worth
retaining. A candidate who fabricated an entire employer is committing
deliberate fraud and should not be hired.
Reason 4:
Fake or Unverifiable Educational Qualifications
How common: Common, particularly for
degrees from smaller or less known institutions.
What
happens: The candidate provides a degree
certificate that cannot be verified because the institution does not exist, the
institution has no record of the candidate, or the degree itself is from a
recognised institution but was purchased rather than earned.
Why
it happens:
India has thousands of educational
institutions, and fake degree mills operate in many states. Candidates purchase
degree certificates for Rs 5,000 to Rs 50,000 from individuals or organisations
that produce realistic-looking documents with proper formatting, seals, and
registration numbers.
Some candidates graduated from an
institution that has since closed, making verification difficult.
Some candidates attended a legitimate
institution but did not complete the degree. They claim completion on their
resume and present a fake marksheet or certificate.
How
employers should respond:
While Compose1 Verify focuses on
government ID verification (PAN, Voter ID, UAN, DL), the identity verification
layer is the first defence against educational fraud. A candidate whose PAN and
Voter ID show a different name or DOB from their degree certificate has a
fundamental identity problem that goes beyond educational fraud.
For educational verification
specifically, contact the institution’s examination controller directly. Check
UGC’s list of fake universities. For professional degrees (medical,
engineering, law), check the relevant council’s (MCI, AICTE, BCI) database.
Reason 5:
Expired or Suspended Driving Licence
How common: Common for roles requiring
driving (delivery, logistics, field sales, transport).
What
happens: The employer verifies the candidate’s DL
through the transport authority database on Compose1 Verify. The licence has
expired, been suspended, or the licence class does not match the vehicle the
candidate will operate.
Why
it happens:
The candidate’s DL expired months or
years ago and was never renewed. The candidate provides a photocopy (not the
original) which does not show the current status.
The DL was suspended for a traffic
violation (drunk driving, reckless driving, repeated violations) and the
candidate does not disclose this.
The candidate holds an LMV (Light Motor
Vehicle) licence but the job requires HMV (Heavy Motor Vehicle) for truck
driving or transport roles.
How
employers should respond:
DL verification through Compose1 Verify shows the current
status (active, expired, suspended), licence class, and expiry date in 2 to 5
minutes. An expired licence is a correctable issue: the candidate can renew it.
A suspended licence is a serious concern for any driving role. A wrong licence
class means the candidate cannot legally operate the required vehicle.
For any role involving vehicle operation,
DL verification is mandatory before the first day of driving.
Reason 6:
Employment Gaps That Hide Terminations
How common: Moderately common.
What
happens: The candidate’s resume shows continuous
employment, but UAN verification reveals gaps where no EPFO contributions were
made. When investigated, the gap corresponds to a period of employment at a
company the candidate was terminated from and chose to omit from their resume.
Why
it happens:
Being terminated carries stigma.
Candidates who were fired for performance issues, misconduct, or policy
violations understandably want to avoid discussing it. They omit the employer
entirely and adjust dates at adjacent employers to close the gap.
How
employers should respond:
UAN verification through Compose1 Verify
reveals the gap. Ask the candidate directly about the period. Frame the
question neutrally: “Your UAN records show no EPFO contributions between March
2024 and November 2024. Can you help me understand this gap?”
The candidate’s response matters more
than the gap itself. A candidate who honestly explains a termination and what
they learned from it demonstrates integrity. A candidate who fabricates another
story to cover the gap is compounding the deception.
Reason 7: Multiple PAN
Cards
How common: Less common but very serious
when it occurs.
What
happens: During verification, it is discovered that
the candidate has more than one PAN card, potentially under different names or
with different DOB information.
Why
it happens:
Having multiple PAN cards is illegal
under Section 272B of the Income Tax Act (penalty of Rs 10,000). Some
individuals obtain multiple PANs to evade tax, operate under multiple
identities, or maintain separate financial lives.
In some innocent cases, a person applied
for a PAN as a minor and again as an adult, or applied through different
channels and received duplicate PANs unintentionally.
How
employers should respond:
If verification reveals that the
candidate’s PAN status shows “duplicate” or if cross-record analysis with Voter
ID suggests a second identity, this is a significant red flag. An employee with
multiple PANs is either evading tax or maintaining multiple identities, both of
which are concerns for any employer.
Reason 8:
Name Changes Without Updated Documents
How common: Common, especially for women
after marriage.
What
happens: The candidate’s current name (used on the
resume and in the interview) does not match the name on their PAN, Voter ID, or
UAN records because they changed their name (after marriage, for personal
reasons, or after a legal name change) but did not update all their identity
documents.
Why
it happens:
After marriage, many women adopt their
husband’s surname. The name on their PAN may still show their maiden name.
Their Voter ID may show either name depending on when it was last updated.
Their UAN records show the name registered by each employer, which may be
inconsistent.
Legal name changes (by court order or
gazette notification) do not automatically update all government databases. The
individual must separately update PAN, Voter ID, Aadhaar, DL, and other
documents.
How
employers should respond:
Name changes are usually innocent and
verifiable. Ask the candidate for their marriage certificate, gazette
notification, or court order supporting the name change. Run verification on
both the old and new names. If the underlying identity (DOB, father’s name)
matches across documents, the name change is confirmed and the candidate should
be cleared.
Reason 9: Address
Discrepancies
How common: Very common but usually low
severity.
What
happens: The address on the candidate’s Voter ID or
PAN does not match their current address or the address provided on the
application.
Why
it happens:
People move. A candidate’s Voter ID may
show their hometown address while they have been living and working in another
city for 5 years. PAN address may not have been updated after a move.
How
employers should respond:
Address discrepancy alone is rarely
grounds for rejection. Focus on identity verification (name and DOB matching
across PAN and Voter ID). Address is secondary to identity confirmation.
However, if the candidate claims to have been living and working in City A for
5 years but all documents show City B, and UAN records show no employer in City
A, the address discrepancy may indicate a broader fabrication.
Reason 10:
Criminal Record Discovery
How common: Relatively uncommon in
formal verification processes, but impactful when discovered.
What
happens: A check reveals that the candidate has a
criminal record, pending charges, or court cases that they did not disclose
during the hiring process.
Why
it happens:
Candidates with criminal records
understandably fear that disclosure will cost them the job opportunity. They
omit criminal history from applications and hope that the employer’s
verification process does not include criminal record checks.
How
employers should respond:
Criminal record checks require court record
searches and police verification, which are separate from the digital ID
verification offered by Compose1 Verify. However, the identity verification
layer (PAN + Voter ID) is essential for criminal checks to be effective. If the
candidate’s identity itself is false, a criminal check against that false
identity will return clean results even if the real person has a criminal
record.
Always verify identity first through Compose1 Verify, then run criminal checks
against the verified identity.
Reason
11: Inconsistent Employment Dates Across Documents
How common: Common.
What
happens: The employment dates on the candidate’s
resume, experience letters, and UAN records do not align. The resume says they
worked at Company X from January 2022 to March 2024, the experience letter says
February 2022 to February 2024, and UAN records show EPFO contributions from
March 2022 to January 2024.
Why
it happens:
Experience letters are sometimes issued
with approximate dates. EPFO contributions may start a month or two after
joining (due to payroll processing timelines) and end a month before the last
working day (final settlement processing). Candidates round dates on their
resumes.
In deliberate cases, candidates extend
their dates to inflate tenure or close gaps.
How
employers should respond:
Minor date discrepancies (1 to 2 months)
between resume, experience letter, and UAN are normal and should not trigger
rejection. Focus on whether the overall employment narrative is consistent. A
candidate who claims 3 years at Company X but UAN shows 11 months has a
significant discrepancy that requires investigation.
Reason 12:
Using Someone Else’s Documents
How common: Less common but the most
serious form of BGV failure.
What
happens: The candidate uses identity documents
(PAN, Voter ID, Aadhaar) belonging to another person: a relative, a friend, or
documents purchased from document brokers.
Why
it happens:
The candidate has a criminal record under
their real identity and uses someone else’s documents to start fresh. The
candidate was blacklisted by previous employers and cannot get hired under
their own name. The candidate is not legally authorised to work (age
restrictions, immigration status) and uses another person’s identity.
How
employers should respond:
This is identity fraud, a criminal
offence. Cross-record analysis through Compose1 Verify is the most effective
detection method. When PAN and Voter ID are checked against their respective
government databases and then compared against each other, a candidate using a
real person’s PAN and a different real person’s Voter ID will show mismatches
in name and DOB across the two databases. A candidate using completely
fabricated numbers will show “not found” results.
Either result is a clear rejection and
may warrant reporting to law enforcement depending on the circumstances.
How
Employers Should Design Their Verification Process
Step 1: Verify
Identity First
Before checking employment history,
education, or criminal records, confirm the candidate’s identity through PAN +
Voter ID verification on Compose1 Verify.
This takes 5 to 10 minutes and costs Rs 100 to Rs 400. If the identity itself
is false, every subsequent check is meaningless because it is being run against
a fake person.
Step 2: Cross-Record
Analysis
Compose1 Verify automatically compares
PAN and Voter ID results. Matching name and DOB across both databases
establishes identity with high confidence. Any mismatch requires investigation
before proceeding with the hire.
Step 3:
Role-Based Additional Checks
Based on the role, add UAN
verification (for experience-based hires), DL verification (for driving roles),
and manual checks (education verification, criminal record searches). Each
additional check is layered on top of the confirmed identity from Step 1.
Step 4:
Distinguish Errors from Fraud
Not every discrepancy is fraud.
Develop a clear policy that distinguishes innocent errors (name spelling
variations, minor date discrepancies, address differences) from deliberate
fabrication (fake employers, purchased degrees, someone else’s documents).
Respond proportionally to each.
Step 5:
Give Candidates a Chance to Explain
Before rejecting a candidate based on
a verification discrepancy, inform them of the finding and give them an
opportunity to explain or provide supporting documentation. A name mismatch may
have a simple explanation. An employment gap may have a legitimate reason. Fair
process protects both the employer and the candidate.
What
Candidates Should Do Before Background Verification
Update Your Documents
If your name is spelled differently
across PAN, Voter ID, and Aadhaar, update them to be consistent. If your DOB is
different on different documents, get it corrected. If you changed your name
after marriage, update all documents. These updates take time, so do them
proactively, not after a BGV failure.
Be Honest on Your Resume
Do not fabricate employers, inflate
designations, or extend employment dates. UAN verification through platforms
like Compose1 Verify checks your actual EPFO contribution history against your
claims. Fabrications that were undetectable 5 years ago are now caught in
minutes through digital verification.
Disclose Gaps Honestly
An employment gap is not a
disqualification. Candidates who honestly explain a gap (personal health,
family responsibility, career transition, layoff) are respected for their
honesty. Candidates who hide gaps by fabricating employers are caught during
verification and rejected for dishonesty, not for the gap itself.
Know Your UAN History
Check your own UAN records on the EPFO
portal before a background verification happens. Know what employers are
listed, what contribution periods are shown, and whether the information
matches your resume. If there are discrepancies (an employer that did not
deposit EPF, a period that shows differently), be prepared to explain them
proactively.
Frequently Asked
Questions
What is
the most common reason employees fail BGV in India?
PAN and identity document mismatches
are the most frequently flagged discrepancies, followed by fabricated or
inflated employment history. PAN verification through Compose1 Verify catches name and DOB
mismatches in 2 to 3 minutes. UAN verification exposes fabricated employers and
inflated tenure in 5 to 30 minutes.
Can a
candidate be rejected for a minor name spelling difference on PAN?
A minor spelling variation (Rajesh vs
Rajeshwar, missing middle name) should not be grounds for automatic rejection.
Cross-check with Voter ID verification. If both databases confirm the same core
identity (same DOB, matching base name), the spelling difference is likely
innocent. Ask the candidate to explain and provide supporting documents.
What
percentage of candidates fail background verification in India?
Industry estimates suggest 10 to 25
percent of candidate profiles contain at least one discrepancy. However, not
all discrepancies are disqualifying. Innocent errors (name spellings, minor
date differences) may account for half of flagged cases. Deliberate fraud (fake
employers, purchased degrees, false identity) accounts for 5 to 12 percent of
profiles, depending on the industry and role level.
How long
does background verification take in India?
Digital identity verification through
Compose1 Verify (PAN, Voter ID, DL) takes 2 to 10 minutes per check. UAN
employment history verification takes 5 to 30 minutes. Manual checks (education
verification, criminal record searches) can take 3 to 15 business days. A
complete verification combining digital and manual checks typically takes 5 to
10 business days.
Should
employers inform candidates before running BGV?
Yes. Under DPDP Act 2023 and general
fair employment practices, employers should inform candidates that background
verification will be conducted and obtain written consent before running
checks. Most employers include BGV consent in the offer letter or as a separate
consent form.
What
should a candidate do if they fail BGV?
Ask the employer for specific details
about which check failed and what discrepancy was found. If the discrepancy is
an innocent error (name spelling, date rounding), provide supporting documents
to explain. If the discrepancy is in your records (incorrect PAN DOB, outdated
Voter ID), take steps to correct the records through the relevant government
agencies. If the failure is due to a genuine fabrication on your part, learn
from the experience and be honest in future applications.
Can an
employer withdraw an offer based on BGV failure?
Yes. Most offer letters in India
include a clause stating that the offer is contingent on successful background
verification. If BGV reveals a material discrepancy (particularly deliberate
fraud), the employer can withdraw the offer. For minor discrepancies, employers
typically give candidates an opportunity to explain before making a decision.
Verification
Failures Are Preventable. For Both Sides.
For employers: digital verification
through Compose1 Verify catches the
most common failure reasons (PAN mismatches, Voter ID discrepancies, UAN
fabrications, DL issues) in minutes. Run identity verification before the
candidate’s first day, not after an incident reveals the problem.
For candidates: be honest. Update your
documents. Disclose gaps. The era of undetectable resume fraud is over. Digital
verification platforms check government databases in real time. The best
strategy is a clean, honest profile that passes every check.
PAN, Voter ID, UAN, and DL verification
in minutes. No subscription. No contract. Because knowing why BGV fails helps
you build a process that catches what matters.
Visit
compose1.com/verify to run employee background verification.
Digital identity checks in minutes. Catch discrepancies before they become
problems.