Automating background verification can either significantly reduce one’s workload or increase it drastically. While the concept of HR tools for this process sounds good on paper, it does not often stand up to its potential for many reasons, including but not limited to India’s decentralised databases as well as the lies and/or exaggerations hidden within the layers of legitimacy.
AuthBridge’s Annual Trends Report 2024, drawn from over 20 million background checks, recorded a 44% spike in employment verification discrepancies across six major sectors in FY2023-24, with the pharma sector at 17.1% and telecom at 18.2%. The tools now catch forged experience letters, fake employers staged to vouch for candidates, and misstated tenures. What they consistently miss is the gaming that happens inside legitimate paper trails, and the Indian hiring reality where many legitimate employers aren’t in any database the tools can query.
What Automated BGV Tools Can Actually Catch
Modern BGV tools reliably catch forged documents, mismatched employment records, dual UANs, inflated or fake education claims, and employers set up specifically to vouch for candidates. The capability stack has moved well beyond the paper-chase era.
“Automated checks are only as reliable as the databases feeding them. In India, a huge number of small and mid-sized companies simply aren’t in those databases. No record is not equal to fake experience; it could just mean the tool has no data,” Akhilesh Agrawal, Independent HR Consultant at LatchQ Semiconductor, pointed out.
“While a phone call to the reporting manager or HR of the previous company still beats a database ping. I’ve had “verified” candidates whose actual role bore no resemblance to what a quick call revealed. A tool tells you a company existed, while a call tells you what the person actually did there.”
Today’s tools cross-reference candidate claims against government-issued data, run document forensics on uploaded letters, and conduct employer-identity checks that catch the cheapest shortcuts. The accuracy depends almost entirely on whether the source being queried is a primary source or a candidate-submitted document.
Aditi Mohan, HR Consultant, Vigyapan Mart, lays out how a good tool structures the match: “A good BGV tool captures the candidate’s declared employer, designation, dates, and CTC in a structured format, then matches it line by line against what the employer confirms. It flags mismatches automatically and cross-checks independent sources such as UAN/EPFO history, Form 16, and DigiLocker or university records. Document forensics and employer-identity checks (free email domains, shared phone numbers) help catch forged letters and fake employers. HR still has to interpret the flags, since a title mismatch can be an internal restructure rather than fraud.”
Employment History
The Universal Account Number tied to EPFO contributions is now the backbone of employment verification in the organised sector. A single UAN pull reveals every employer that has deposited provident funds for the candidate, with dates. Dual UANs with overlapping dates are how most moonlighting cases get caught, including the Wipro episode that triggered 300 terminations in September 2022. Form 16 cross-checks the declared CTC against what the previous employer reported to the Income Tax Department, which catches CTC inflation that resumes have carried for years without consequence.
Education and Identity
DigiLocker has reshaped education verification in India. The platform issues documents directly from CBSE, state boards, and UGC-regulated universities, and a shared DigiLocker document is treated as legally equivalent to the original under Section 9A of the IT Act, 2000. AuthBridge’s integration data suggests turnaround time drops by roughly 80% when the candidate’s institute is on DigiLocker. Aadhaar and PAN cross-checks catch identity mismatches older systems missed entirely.
Document and Employer Forensics
Image-level forensics scans uploaded experience letters for metadata inconsistencies, cloned templates, and signature mismatches. Employer-identity checks flag companies whose “HR” references come from free webmail domains, phone numbers shared across multiple fake employers, or Udyam/MCA registrations that don’t actually exist. These catch the volume-fraud operations that mass-produce fake credentials for a fee.
Where the Technology Quietly Fails
The real problem isn’t what BGV tools can’t verify. It’s what organisations assume the “verified” tick confirms.
Akhilesh puts the frame bluntly: “Honestly, the biggest limitation isn’t the technology. It’s what people assume the technology is doing. A BGV tool checks if a record exists. It doesn’t check if the record means what the candidate said it means. That distinction has burned more hiring managers than any actual database gap.”
A persistent pattern surfaces in his experience. The gaps aren’t technical. They sit in the space between a verified record and a true one.
Title Inflation
Title inflation is where every record checks out, but the role described never actually existed at that scope. Everything on paper can be real, and the hiring decision can still be wrong.
“From an HR lens, the most frequent issue is inflation rather than outright fabrication: stretched tenures to hide gaps, upgraded designations, and overstated CTC,” said Aditi.
“We also see doctored experience letters and payslips, fake employers backed by accomplices posing as HR contacts, and degrees from unrecognised institutions or marked “completed” when backlogs are still pending. The subtle cases are the ones most likely to slip through a resume screen.”
Reference Gaming
Reference gaming is the deliberate version of the same gap. A verification tool calls the number listed as the reporting manager and gets confirmation. Nobody checks whether the person on that number actually was the reporting manager:
“I’ve come across cases, not hypothetical, actual cases, where the ‘manager’ being called was a friend briefed in advance. The system did exactly what it was designed to do,” Akhilesh shared. “It called a number and got an answer. It just wasn’t the right person answering.”
Tools that run reference calls at scale can’t easily distinguish a legitimate senior from a friend with a convincing phone voice. Candidates who understand how BGV workflows run can exploit that gap deliberately, and the ones who do it well leave no trace in any report.
The India-Specific Blind Spot
Automated BGV assumes a digital footprint. A huge share of India’s workforce doesn’t have one. Unorganised retail, small manufacturing, tier-2 and tier-3 city employers, kirana-scale operations, and family-run businesses rarely digitise employment records. When a tool returns “unable to verify,” most recruiters treat that as a soft red flag. Agrawal’s take:
“A massive part of our workforce- unorganised retail, manufacturing, gig-adjacent roles, tier-2/tier-3 city employers- simply has no digital footprint to cross-check against. When a tool comes back with ‘unable to verify,’ most recruiters read that as a soft red flag. It’s often nothing more than ‘this employer never digitised their records.’ Treating absence of data as evidence of fraud is its own kind of risk,” explained Akhilesh.
“You end up penalising honest candidates from unorganised-sector backgrounds while sophisticated fakers, who know exactly how to build a paper trail, sail through.”
The absence of a central Indian criminal database compounds the problem. As the coverage of the Indian BGV process notes, criminal checks still run on a jurisdiction-by-jurisdiction basis, and employers who skip the human verification layer end up with gaps they can’t see from the BGV report alone.
Reading a Discrepancy Flag Without Making a Lazy Call
A flagged BGV report isn’t a verdict. It’s the start of a different conversation. Akhilesh’s rule for handling a discrepancy with an explanation attached.
“Don’t dismiss it, and don’t auto-reject either. Treat it like any other red flag: verify the explanation, don’t just accept it because it sounds reasonable,” Akhilesh laid out.
“If someone says ‘the company got acquired, that’s why the name doesn’t match,’ that’s checkable in five minutes. If they say ‘my manager left, so there’s no one to confirm,’ that’s also checkable; companies keep HR records even after someone exits. The candidates worth worrying about are the ones whose explanations can’t be verified by anyone, ever. That pattern itself is the answer.”
Like any HR tool, background verification cannot be done without a human touch, especially when a negative flag comes up. Rather than assuming a discrepancy to be accurate, refer to this quick decision table for the discrepancy categories recruiters what you should ideally check before escalating the situation:
| Discrepancy Type | Common Legitimate Cause | First Check Before Escalating |
| Employer name mismatch | Acquisition, legal entity vs brand name | MCA records, press coverage |
| Dates off by weeks | Notice period rounding, calendar vs financial year | UAN deposit dates |
| Designation mismatch | Internal restructure, revised titles | Call a colleague, not the listed manager |
| CTC gap | Variable not disclosed, hike withheld | Form 16 cross-check |
| “Unable to verify” | Employer not digitised, HR unresponsive | Human verification layer, in-person check |
| Education “incomplete” marked complete | Backlog pending at graduation | University registrar confirmation |
A single discrepancy shouldn’t override an otherwise strong hire without a conversation, and a smooth explanation shouldn’t override a strong discrepancy without digging in. Agrawal’s words: both are lazy decisions dressed up as diligence.
What a Mature BGV Workflow Looks Like
The BGV report is an input, not a decision. The workflow around it decides whether the input gets used well or ignored.
“Prioritise tools that verify at the primary source (employers, universities, EPFO, DigiLocker) instead of accepting candidate-submitted documents. The report should show claimed versus verified data with severity ratings, not just a pass/fail,” Aditi emphasised.
“Make sure there is a trained human verification layer for hard-to-reach employers and edge cases, plus candidate consent and DPDP-compliant data handling. Reasonable turnaround time and ATS/HRMS integration keep the process from slowing down hiring.”
Severity ratings and the human verification layer are what deserve underlining. The pass/fail model collapses a reasonable explainable discrepancy and a fundamental credential fraud into one tick, which is how legitimate candidates get rejected and sophisticated fakers get through. Human verification layers handle the long tail of Indian employers that don’t surface in any database, which automation still handles poorly.
The compliance side has also sharpened. The Digital Personal Data Protection Act 2023 and its operational Rules treat every employer as a data fiduciary, which means consent, purpose limitation, retention policy, and vendor accountability all sit with HR rather than the BGV vendor. Penalties for significant non-compliance run up to Rs 250 crore. A process that ran on verbal consent two years ago must run on documented, revocable consent today, and that affects which vendors can serve Indian employers in 2026.
In the End…
A good BGV tool does not work around the discussed limitations. Rather, it works with them to create the most comprehensive report possible. Many background reports aren’t black-and-white, and a good BGV tool should know that. Even more than that, constant human supervision and intervention can truly optimise the results.
A tool tells you a company existed and a record matched. A fifteen-minute phone call to someone who worked near the candidate tells you what the person actually did there. The combination catches almost everything. Either one alone leaves obvious gaps that sophisticated candidates have learned to walk through.
Shift to a vendor that reports severity ratings instead of pass/fail. Make at least one informal reference call non-negotiable for every mid-senior hire, regardless of what the BGV comes back with. Audit how your current vendor treats “unable to verify” results against candidates from unorganised-sector backgrounds. Refresh your consent and data-retention paperwork against the DPDP Act’s operational rules.
The gap between a verified tick and a verified hire closes with human judgement, not better software. The teams that remember this get the hires that stay.
FAQs
What can automated BGV tools reliably detect?
Modern BGV tools reliably catch forged experience letters, mismatched employment records, dual UANs that indicate undisclosed overlapping jobs, inflated or fabricated education claims, and employers set up only to vouch for a candidate. Accuracy depends on whether the source being queried is a primary source such as EPFO, DigiLocker, or the Income Tax Department, or a candidate-submitted document.
Why does a BGV report say “unable to verify” for Indian candidates?
A large share of India’s workforce in unorganised retail, small manufacturing, and tier-2 or tier-3 city employers has no digital footprint for a tool to query. “Unable to verify” usually means the employer never digitised its records, not that the candidate lied. Treating absence of data as evidence of fraud penalises honest candidates from unorganised-sector backgrounds and should be routed to a human verification layer instead.
How does UAN or EPFO data verify employment history in India?
The Universal Account Number tied to EPFO contributions anchors employment verification in the organised sector. A single UAN pull returns every employer that has deposited provident funds for the candidate, with dates. Dual UANs with overlapping dates are the standard tell for moonlighting cases, including the Wipro episode in September 2022 that triggered 300 terminations.
What is reference gaming in background verification?
Reference gaming is when a candidate lists a friend’s phone number as the reporting manager and briefs that person in advance. The BGV tool calls the number and gets a clean confirmation, but the person answering was never the actual manager. Automated reference calls at scale cannot easily tell a legitimate senior apart from a prepared accomplice, and candidates who understand BGV workflows exploit the gap deliberately.
How does the DPDP Act 2023 change background verification in India?
The Digital Personal Data Protection Act 2023 and its operational Rules treat every employer as a data fiduciary. Consent, purpose limitation, retention policy, and vendor accountability now sit with HR rather than the BGV vendor, and penalties for significant non-compliance run up to Rs 250 crore. Processes that ran on verbal consent earlier must now run on documented, revocable consent, which affects which vendors can serve Indian employers in 2026.
