Overview
Identity verification is the step that makes every other part of a background check work. It establishes who the person is and where they have lived, which determines which courts get searched and under which names.
It is also the most commonly misunderstood component, because it looks like a test the candidate can pass or fail. It is not. It is a scoping tool, and treating its output as a finding is the source of most of the trouble it causes.
Throughout this page, “screening company” refers to the outside firm an employer hires to run the check. In the law it is called a consumer reporting agency, or CRA.
What an Identity Check Confirms
A typical identity component returns:
- Names associated with the Social Security number, including former and alternate names
- Address history, usually with approximate date ranges
- Date of birth confirmation, where available
- The year and state the Social Security number was issued
- Flags, such as a number never issued or one associated with a deceased person
What it produces is a map. The names tell a screening company which names to search under. The addresses tell it which counties and states to search. Nothing more is being claimed.
The Three SSN Services and How They Differ
Three different things get called “SSN verification,” and they are not interchangeable. Two come from the Social Security Administration and one does not touch the SSA at all.
| SSN Trace | Not an SSA service. Draws on identifying information compiled from credit file headers and other commercial sources. Returns names and addresses associated with the number. Used to decide where to search. Verifies nothing. |
| SSNVS | The SSA’s Social Security Number Verification Service. Free to registered employers through Business Services Online. Confirms whether a name and number match SSA records. Restricted to wage reporting, and must not be used for pre-employment screening. |
| CBSV and eCBSV | The SSA’s Consent Based verification services. Fee based, require the number holder’s signed consent, and return a yes or no match on name, date of birth, and number, plus a death indicator where SSA records show one. |
The SSN Trace
The trace is the one that appears on nearly every background check, and it is the most misread. Three corrections matter.
An SSN trace does not verify identity, and it does not confirm the number belongs to the person. It reports which names and addresses have been associated with that number in commercial records. Someone using another person’s number consistently over years will produce a clean trace. The trace tells you where to look, not who someone is.
It is not a credit check. The trace uses identifying information from the header of a credit file, not the account data. No score, no balances, no payment history, and no effect on the candidate’s credit.
It is a starting point, not a result. Its entire job is to produce the list of names and places the rest of the check will search.
SSNVS Is for Payroll, Not Hiring
The SSA offers registered employers a free service confirming that an employee’s name and number match its records. It exists so that W-2 filings are accurate, and the SSA restricts it to that purpose. Using it to screen applicants before hire is a misuse of the service, and a mismatch is not evidence of anything about work authorization.
CBSV and eCBSV Require Consent
Where an employer or screening company genuinely needs SSA confirmation, the consent based services are the route. The original service uses a signed paper consent form. The newer electronic version, created by federal banking legislation in 2018, accepts electronic consent and runs through an interface, but it is limited to entities permitted under that legislation.
Both return the same narrow answer: whether the name, date of birth, and number match, and whether SSA records show the holder as deceased.
The SSA is explicit about the limits. Its own guidance states that consent based verification does not verify identity, citizenship, or employment eligibility, and does not interface with the Department of Homeland Security verification system. A CBSV result does not satisfy Form I-9 requirements. A match confirms only that the name and number pair exists in SSA records.
Why It Comes First
Criminal records are searched jurisdiction by jurisdiction, and there is no national index a private employer can rely on. So the question of which jurisdictions to search has to be answered before any searching happens.
The address history answers it. A candidate who lived in 3 counties across 2 states over the past 7 years generates a search list. A candidate whose application lists only their current address, with no trace run, generates a search of 1 county.
This is why an accurate identity component contributes more to the completeness of a background check than buying additional searches does. Searching the wrong county thoroughly finds nothing.
How the Search List Actually Gets Built
The output of the trace becomes the input to everything else, through a sequence worth understanding:
- Names become search terms. Every name the trace returns, plus every name the candidate discloses on the authorization form, becomes a name the court indexes are searched under. Court records are indexed by name, so a name nobody searched returns nothing.
- Addresses become jurisdictions. Each address is resolved to its county, and each county becomes a search. A candidate with 5 addresses across 3 counties generates 3 county searches, not 1.
- Date ranges set the scope. The approximate dates attached to each address determine which counties fall inside the lookback period the employer has chosen.
- The candidate fills the gaps. Commercial data lags and misses short stays, which is why the authorization form asks for address history directly rather than relying on the trace alone.
Two things follow. A name omitted from the form is a name not searched, and a county missing from the address history is a county not searched. Neither omission hides a record from anyone, it just makes the report less complete than it appears.
Names, Aliases, and Why They Matter
Court records are indexed by name. A record filed under a name nobody searched will not be found, and the reasons a person has more than one name are almost always ordinary:
- Marriage, divorce, or remarriage
- A legal name change
- A middle name used as a first name
- Hyphenated or compound surnames recorded inconsistently
- Anglicized or transliterated spellings
- Generational suffixes, where a father and son share a name
The word “alias” carries an unfortunate implication. On a background report it means nothing more than an additional name associated with the record. A maiden name is an alias. So is a misspelling introduced by a data entry clerk in 2009.
How This Differs From I-9 and E-Verify
These get conflated constantly, and the distinction is legal rather than technical.
| Identity Verification | Part of a background check. Establishes names and addresses so records can be located, and where a consent based service is used, confirms a name and number match SSA records. Requires the candidate’s authorization. Confirms nothing about the right to work. |
| Form I-9 | A federal employment eligibility form every U.S. employer must complete for every new hire. It confirms identity and authorization to work. Not a background check and not run by a screening company. |
| E-Verify | A federal government system that compares I-9 information against government records. Mandatory for some employers and voluntary for others. Also not a background check. |
A screening company does not perform an I-9 or an E-Verify query as part of a background check, and a clean identity component says nothing about whether someone is authorized to work. This holds even for a consent based SSA verification, which the SSA states does not verify citizenship or employment eligibility and does not satisfy I-9 requirements. Employers that assume otherwise end up with an I-9 compliance problem they did not know they had.
What Identity Verification Cannot Do
- It cannot detect a well maintained false identity. Consistent use of another person’s number over time produces a consistent trace.
- It misses recent moves. Commercial data lags, so an address occupied for 3 months may not appear at all.
- It misses people with thin files. Someone young, recently arrived in the country, or living outside the credit system may generate almost no address history. That is not suspicious, but it does mean the search list has to be built another way.
- It cannot confirm a person is who they say in the room. Matching a document to a face is an in person task, not a database one.
The Rules Employers Must Follow
Three rules apply. Each has its own page on this site, so this is the summary.
Get Written Permission First
The identity component is part of a consumer report. The employer must give a standalone written disclosure and obtain written authorization before requesting it. See our FCRA overview.
Keep the I-9 Process Separate
Work authorization is a distinct legal obligation with its own forms, deadlines, and penalties. It is not satisfied by a background check, and a background check does not substitute for it.
Follow the Steps Before Rejecting Someone
If something in the report is going to cost the candidate the job, the employer must send a preliminary notice with a copy of it, allow time to respond or correct an error, and only then issue the final decision. See the adverse action process.
For Applicants
- List every name you have used. Maiden names, former married names, and legal changes all belong on the form. Leaving one off does not hide anything, it just means a county gets searched under the wrong name.
- Give a full address history for the period requested. Gaps slow the check down and can require you to be contacted mid process.
- A thin trace is not a problem. If you are young, recently arrived, or have avoided credit, your address history may be sparse. Say so and supply the addresses directly.
- A number issued in a state you never lived in is normal. Numbers have been issued at birth for decades and reflect where a parent applied, not where you grew up.
- A deceased flag is fixable. Records get mismarked. It is alarming and it is also an error with a correction process.
- If the report is wrong, dispute it. Our guide to disputing a background check covers the process.
Best Practices
- Run the identity component first and use its output to build the search list
- Ask candidates for former names on the authorization form rather than relying on the trace to find them
- Treat a sparse address history as a scoping problem, not as a finding about the candidate
- Never use the identity component as a proxy for work authorization
- Search every county the address history returns for the period you have committed to checking
- Ask before acting on a mismatch, since name and address data carries meaningful error rates
- Apply the same lookback period to every candidate for the same role