A candidate called Priya in tears on a Tuesday morning: “Your report says I was terminated for misconduct from my last company. That’s wrong. I resigned. I have the resignation acceptance email from my manager at Infosys.” Priya checked the BGV report. It clearly stated: “Employment terminated — misconduct.” She’d already sent the rejection email the previous evening.
The candidate posted the entire exchange on LinkedIn. The post got 4,700 reactions and 800+ comments, mostly from HR professionals expressing outrage. The company’s Glassdoor rating dropped from 4.1 to 3.6 in a month. Their offer acceptance rate fell 15% the following quarter — candidates were Googling the company and finding the LinkedIn post.
Cost of the error: one premature rejection email sent 12 hours too early.
Table of Contents
Why Disputes Will Happen — And Why Your Process Determines the Damage
BGV reports are not infallible. Previous employers misclassify resignations as terminations (especially in “managed exits” common at Indian IT companies). Universities transpose degree years. Court databases return false positives for common names like Rahul Kumar or Priya Sharma. Field agents visit the wrong address.
When a candidate disputes a finding, one of three things is true: the candidate is lying and the report is correct, the report is wrong and the candidate is truthful, or the truth is more nuanced than either version (the “managed exit” scenario).
Without a defined dispute process, you’re gambling every time.
Why This Is Now a Legal Obligation (Not Just Best Practice)
Under DPDPA Section 12, every Data Principal (which includes your candidates) has the right to correction and erasure of their personal data. If your BGV report contains information the candidate believes is inaccurate, they have a statutory right to challenge it. You have a legal obligation to have a process for receiving, investigating, and resolving these challenges.
This isn’t optional courtesy — it’s compliance.
The Six-Step Dispute Resolution Framework
Step 1: Accept the Dispute Formally (Within 24 Hours)
When a candidate disputes a finding — by email, phone, WhatsApp, or through their recruiter — acknowledge receipt within 24 hours. Provide: a specific point of contact (name, email, phone — not a generic inbox), a reference number for tracking, and a defined timeline for resolution (“We will investigate and respond within 7-10 business days”).
Template: “Dear [Name], We have received your dispute regarding [specific finding] in your background verification report (Ref: [number]). Your concern is being investigated. [Contact Name] will be your point of contact. You can expect a resolution update by [date, 7-10 business days]. We take accuracy seriously and appreciate your patience.”
Step 2: Pause Adverse Action (Immediately)
This is the step Priya skipped, and it cost her company dearly. Do NOT proceed with rejection or offer withdrawal while a dispute is pending. If you’ve already sent a rejection, contact the candidate immediately to inform them the decision is under review. The legal principle: adverse action taken before a dispute is investigated is procedurally unfair and challengeable.
Step 3: Investigate Through Your Vendor (Days 1-5)
Direct your BGV vendor to re-verify the specific disputed finding using an alternative channel. If the original verification was phone-based → request document-based re-verification. If the original was through a junior HR contact → request re-verification through a senior HR contact or direct manager. If it was a court record match → request full-name + father’s-name + DOB cross-reference to eliminate false positives. If the employer is Infosys, TCS, or Wipro → many large Indian IT companies now use automated verification portals. Check if the vendor accessed the portal vs. a potentially inaccurate phone response.
Step 4: Accept and Evaluate Candidate Evidence (Days 1-7)
If the candidate provides supporting documents — resignation acceptance email, full-and-final settlement statement, relieving letter, corrected degree certificate, court order showing case dismissal — these must be evaluated alongside the vendor’s re-verification findings.
Don’t dismiss candidate-provided evidence because it contradicts the vendor’s report. The vendor is not always right. Especially in the “termination vs. resignation” scenario — in Indian IT, many exits are negotiated. The company records it as “involuntary separation” for their internal dashboards while the employee genuinely resigned with a negotiated notice period.
Step 5: Communicate the Resolution (Day 7-10)
Regardless of outcome, inform the candidate in writing: what finding was disputed, what evidence was reviewed (vendor re-verification + candidate documents), what conclusion was reached, and what action follows (original finding upheld → adverse action proceeds with documentation | finding corrected → report updated and adverse action withdrawn).
If the original finding was incorrect: update the record, apologize sincerely, and — if the candidate was already rejected — reopen the offer process. Yes, this is awkward. It’s less awkward than a LinkedIn post that damages your employer brand for a year.
Step 6: Document Everything and Feed Back
Every dispute, every piece of evidence, every resolution. This documentation serves three purposes: legal defense if the candidate escalates further, process improvement data (are certain check types generating repeated disputes? Is a specific vendor consistently inaccurate?), and vendor accountability (if 5% of your vendor’s reports are disputed and 40% of disputes result in corrections, your vendor has an accuracy problem).
When the Dispute Reveals the Vendor Was Wrong
This happens more often than vendors admit. If re-verification proves the original report was incorrect, you should: require the vendor to issue a corrected report within 48 hours, document the error for your quarterly vendor review, and if the error rate exceeds a threshold (e.g., more than 3 errors per 100 checks), invoke your SLA remediation clause.
An inaccurate BGV report that causes a wrongful rejection is not just embarrassing — it’s a compliance failure under DPDPA and a potential legal liability for your company.
SpringVerify’s detailed discrepancy reports include the specific data points verified, sources used, and methodology — making dispute investigation faster and more transparent for HR teams, candidates, and legal reviewers.
Key Takeaways:
•DPDPA Section 12 gives candidates a legal right to dispute BGV findings — your process is a legal obligation, not courtesy
•ALWAYS pause adverse action while a dispute is pending — one premature rejection email can cost you 15% of your offer acceptance rate
•Investigate disputes through alternative verification channels — the original method may have produced the error
•The “termination vs. resignation” dispute is the most common in India — the truth is usually a negotiated exit that both sides describe differently
•Track dispute resolution data to hold your vendor accountable — if 40% of disputes result in corrections, your vendor has a problem
