Make talent quality your leading analytic with skills-based hiring solution.
Identity verification confirms that a candidate is a real, unique person who matches the ID document and face they submitted. A background check searches public and institutional records to see what that already confirmed person has actually done. They answer two different questions, and most hiring processes that only run one of them have a gap. For the large majority of roles, especially remote or high trust positions, the honest answer is yes, you need both.
That answer sounds simple, but the reason it matters is that “background check” has become a catch all term in recruiting conversations, and a lot of TA leaders assume it already includes identity verification. It usually does not. Understanding exactly where the line falls between the two is the difference between a screening process with a real hole in it and one that actually covers the risk.
Identity verification confirms that the person applying is a real, unique individual and that they are the same person named on their submitted documents, not whether that person has a clean record. In practice, an identity verification step like Glider’s ID Verify typically checks:
None of that involves a criminal record, an employer, or a school. It is entirely about confirming the person is who the documents say they are, right now, in real time. That is the exact function Glider’s identity verification product is built around, and why it typically runs early in the funnel, often before an interview is even scheduled.
A background check assumes the identity is already correct and instead investigates that person’s history and record. A standard employment background check usually covers some combination of:
Every one of those searches depends on one input being correct: the name, date of birth, and identifying details the candidate provided. If that input is wrong, either through an honest clerical error or deliberate fraud, the background check runs a clean search against the wrong person’s history, or against no real history at all, and comes back looking clean.
The overlap is narrower than most hiring teams assume. Both processes touch a government issued ID at some point (identity verification analyzes the document itself, while a background check uses the details on it as a search input), and both are usually run as a condition of a formal offer. Beyond that, they are checking almost entirely different things. Identity verification is a moment in time confirmation of a person’s identity. A background check is a retrospective look at that person’s documented history. Treating them as interchangeable, or assuming one covers the other, is where the real risk shows up.
A background check cannot catch a candidate who is not who they claim to be, because it is built to search records under a name, not to confirm a face matches a document. This is exactly the blind spot behind several well documented fraud cases. In one incident Glider has written about, a company nearly hired a fraudulent candidate tied to a North Korea based scheme using a stolen or borrowed identity, a case where standard background checks did not flag anything because the underlying documents and search inputs looked legitimate on paper.
Remote hiring has also opened the door to a newer version of this same blind spot: deepfake generated candidates who use real time face swapping or synthetic video during interviews to present as someone they are not, sometimes so that one person can be paid for a role while a different, less qualified person actually shows up and does the work. A background check run on the name that person supplied will often come back clean, because the records are real, they just belong to someone who is not the person actually being hired.
Identity verification confirms a person is real and matches their ID, but it says nothing about what that real person has actually done. A confirmed, genuine identity can still belong to someone with an undisclosed felony conviction, a fabricated resume, a revoked professional license, or a history of terminations for cause. None of that shows up in a face match or a document scan. This is exactly why a bank recruiting fraud case that Glider covered in a case study on hiring fraud in banking required looking at both layers, the identity of the candidate and their actual employment and conduct history, to catch the full scope of the problem.
Yes, for most roles the two checks are complementary, not redundant, and skipping either one leaves a specific, predictable gap. A useful way to think about sequencing:
The cost argument against running both rarely holds up once a single fraud incident is weighed against it. Rerunning a background check after discovering an identity was fabricated, dealing with the fallout of an unqualified or malicious hire, or explaining to leadership why a role went to someone who was never actually vetted, all cost far more than the incremental price of an identity check on the front end.
Glider treats identity verification and background style screening as two connected layers of the same underlying question: is this candidate actually who and what they claim to be? ID Verify handles the identity layer with document authenticity checks, biometric face matching, and liveness detection built directly into the hiring workflow, so the confirmation happens before a company invests recruiter time or background check spend in a candidate.
From there, standard background and reference checks can run against a confirmed identity, closing the loop rather than operating in isolation. Read the full ID Verify FAQ for process and cost details beyond what is covered here.
Not on its own. A background check searches records using the name and details a candidate provides, but it does not confirm that the person supplying those details is who they claim to be. That confirmation is the job of identity verification.
Yes, if the fake identity is built well enough that the search inputs (name, date of birth, document numbers) resolve to real records, either their own under a different context or a fabricated but internally consistent identity. This is the core reason identity verification and background checks need to run together.
Identity verification checks document authenticity, biometric face match, and liveness in real time, confirming the actual person is real and matches their ID. A background check does not perform any of those checks, it only investigates history once identity is assumed to be correct.
For most roles, yes, especially remote, financial, healthcare, and other high trust positions. Identity verification and background checks cover different risks, and using only one leaves a specific gap that fraud cases have repeatedly shown to be exploitable.
Ideally early, at application or before an interview is scheduled, so recruiting effort and background check spend are directed at a confirmed real person rather than a potentially fabricated one.
Requirements vary by jurisdiction and industry, and some regulated sectors like banking and healthcare have specific identity confirmation obligations. Even where it is not strictly mandated, it is increasingly treated as a baseline best practice given the rise in remote hiring fraud.
Identity verification is typically a lower cost, faster check than a full background check, since it is a single point in time confirmation rather than a multi source records search. Most organizations find the added cost small relative to the cost of a single hiring fraud incident.
Verifying candidates across borders means confirming that a job applicant is who they claim to be even when their government issued ID, home country, time zone, and native language are all different from the recruiter reviewing their application. It is harder than domestic verification because there is no single ID format, no shared database, and […]
Synthetic identity fraud in hiring happens when someone builds a job candidate instead of being one, blending a real Social Security number or stolen document with a fabricated name, a generative AI face, and a scripted background, so the “person” who interviews and gets hired never actually existed as a single, real individual. It is […]
A diploma mill is an unaccredited operation that sells degrees or certificates for a flat fee, little or no coursework, and almost no academic oversight, and the fastest way to catch one is to verify education claims directly with the issuing school rather than trusting the document a candidate submits. Fake degrees are no longer […]
