
A candidate clears every interview round, the team is excited about the hire, and then the background verification report lands with a red flag. Now what?
This is one of the most common and most mishandled situations in HR. A background verification discrepancy does not automatically mean the candidate lied, and it definitely does not mean you reject them on the spot. But it does mean you need a clear process for what happens next.
Here is how HR teams should actually handle a failed background verification, step by step.
What Does “Failed” Background Verification Actually Mean?
First, let us clear up a common misconception. Background verification companies do not pass or fail candidates the way an exam does. What they do is verify the information the candidate provided and report back with one of three outcomes for each check:
Verified: The information matches what the candidate claimed. Everything checks out.
Unable to Verify: The source (a former employer, university, or database) could not confirm the information. This is not the same as the information being false. The institution may have closed, merged, or simply not responded.
Discrepancy Found (Flagged): The information the candidate provided does not match what the verification source confirmed. This is the “failure” that most people refer to, and it is where HR’s judgment becomes critical.
The important thing to understand is that a flag is a finding, not a verdict. The best background verification company will present the facts clearly and leave the hiring decision to the employer.
Common Reasons Candidates Get Flagged
Not all discrepancies are created equal. Some are genuine mistakes, and some are deliberate misrepresentations. Knowing the difference matters because your response should be proportional to the severity.
Minor discrepancies that usually have innocent explanations include slightly mismatched employment dates (a month or two off), a different job title than what HR records show (many companies use internal titles that differ from what employees put on their resume), a former employer that changed its name or merged with another company, and address mismatches due to relocation or outdated records.
Serious discrepancies that require deeper scrutiny include a degree or certification that the institution has no record of, employment at a company where nobody can confirm the candidate ever worked, an undisclosed criminal record, and significant inflation of job titles or responsibilities that misrepresent the candidate’s actual experience.
Unable to verify situations that need patience rather than panic include universities with slow or unresponsive registrar offices, former employers who have a policy of not disclosing employee details, very old employment records that may no longer exist, and small companies that have shut down without maintaining records.
What Should HR Do When a Discrepancy Is Found?
This is where most companies either overreact or underreact. Here is a structured process that keeps things fair, consistent, and legally defensible.
Step 1: Review the Finding in Detail
Read the full verification report, not just the summary. Understand exactly what was checked, what the candidate claimed, and what the verification source found. A “discrepancy” in a summary line could be anything from a one month date difference to a completely fabricated credential.
Step 2: Assess the Severity
Ask yourself three questions. Is this a minor administrative difference or a material misrepresentation? Is the discrepancy relevant to the role the candidate is being hired for? Could there be a legitimate explanation?
A project manager whose resume says “April 2019” when the employer records show “June 2019” is a very different situation from a finance professional who claims an MBA from an institution that has no record of them.
Step 3: Give the Candidate a Chance to Respond
This is not optional, it is essential. Before making any decision, share the specific finding with the candidate and ask for their explanation or supporting documentation. Many discrepancies get resolved at this stage. The company may have changed names, the university may have updated its records, or the candidate may have supporting documents that the verification team did not have access to.
Step 4: Make a Decision Based on Policy
Your company should have a written process of background verification policy that defines what types of discrepancies are deal breakers and what falls within acceptable limits. This policy should be applied consistently across all candidates. Different recruiters handling similar cases differently is a legal and fairness risk.
Step 5: Document Everything
Whatever the decision, document the finding, the candidate’s response, your assessment, and the final outcome. This protects both the company and the candidate if questions arise later.
What Are the Possible Outcomes?
Depending on the severity of the finding and the candidate’s response, there are typically four paths:
Cleared: The candidate provides a satisfactory explanation or documentation, and the discrepancy is resolved. The hiring process continues normally.
Conditional Offer: The company proceeds with the hire but with conditions, such as a probationary review, additional checks, or a requirement to provide specific documentation within a set timeframe.
Offer Withdrawn: The discrepancy is confirmed, material, and directly relevant to the role. The company withdraws the offer. This should always be communicated clearly and professionally, with a reference to the specific finding.
Existing Employee Flagged: If the candidate has already joined and a post employment check reveals a serious discrepancy, the company may initiate an internal review, reassign the employee, or in severe cases, terminate employment based on the terms of the employment contract.
Criminal Records Need Extra Care
Criminal background findings deserve a separate conversation because they carry more weight and more legal nuance than other discrepancies.
Before acting on a criminal record finding, verify that the record actually belongs to the candidate (common names produce false matches more often than you would expect), check whether it is a pending case, an acquittal, or a conviction (these are very different things), and consider whether the finding is relevant to the role. A decade old minor offence may have no bearing on the candidate’s ability to perform a desk job.
Blanket rejection policies for any criminal record are not just unfair, they can expose the company to legal challenges. A thoughtful, role relevant assessment is the better approach.
Mistakes HR Teams Should Avoid
Treating every flag as fraud. Most discrepancies have explanations. Assuming the worst before investigating damages the candidate relationship and your employer brand.
Inconsistent handling. If you let one candidate’s date mismatch slide but reject another for the same thing, you have a fairness and potentially a legal problem.
Relying only on candidate provided documents. If a candidate provides their own “proof” to resolve a discrepancy, verify that proof independently rather than accepting it at face value.
Not having a written policy. Making decisions on a case by case basis without a framework means every discrepancy becomes a debate. Write the policy before the first flag shows up.
Ghosting the candidate. If a background check leads to an offer withdrawal, communicate it. Candidates who are left without any explanation will assume the worst and share that experience publicly.
How to Build a BGV Policy That Works
If your company does not have a formal policy yet, here is what it should cover:
Which roles require background verification and what types of checks apply to each role category. What discrepancy levels are acceptable (minor date differences versus fabricated credentials). Who has the authority to make the final decision when a flag comes up. How candidates are notified about findings and given a chance to respond. Data retention and privacy practices in line with DPDPA 2023 requirements. A review cycle to update the policy as regulations and industry standards change.
Having this written down before you need it removes the pressure of making these decisions in the moment, and ensures that every candidate is treated consistently.
The Role of Technology in Handling BGV Discrepancies
Modern AI powered verification platforms have made it easier to handle discrepancies fairly and efficiently. Automated systems can flag inconsistencies instantly, provide clear categorization of findings (verified, flagged, unable to verify), maintain complete audit trails for compliance, and generate standardized reports that make it easier for HR to assess and compare findings.
IDA Analytics uses a hybrid model where AI handles document validation and database screening at speed, while human analysts conduct the checks that require judgment, like employment verification calls and reference interviews. This combination reduces false flags and gives HR teams cleaner, more actionable reports to work with.
Final Thought
A failed background verification is not the end of the conversation. It is the beginning of a review process that, when handled well, protects both the company and the candidate.
The companies that handle BGV discrepancies well are the ones that have a written policy, give candidates a fair chance to respond, and make decisions based on relevance and severity rather than blanket rejection. That approach is not just better for candidates. It is better for hiring outcomes.


