Background Check Errors: Mixed Files, Wrong Person Matches, and How to Fix Them

A mixed file happens when a background check pulls a court record, an alias, or a credit history that belongs to someone else and attaches it to your applicant. It is one of the oldest and most persistent problems in consumer reporting, and it still shows up in hiring decisions today because so much of the industry relies on shallow database matching instead of verified identifiers. If you screen candidates, understanding how this happens and what the law requires when it does is not optional. It is the difference between a defensible hiring process and a costly one.

How a mixed file actually happens

Most mixed files trace back to one root cause: a background check company matched a record using too little information. Court systems, especially at the county level, often index cases by name and birth year rather than a full date of birth, Social Security number, or middle name. When a search engine or scraper pulls that record and hands it to a screening company, the matching logic has to decide whether “John A. Smith, born 1988” in the court database is the same “John A. Smith, born 1988” who applied for a job. If the screening company is matching on name and approximate age alone, it has a real chance of matching the wrong person.

A few conditions make this worse:

• Common names. Smith, Garcia, Johnson, Lee, Williams. The more common the name, the higher the odds that two or more people in the same county share it and were born in the same general window.
• Thin identifiers. Many court records simply do not carry a full SSN or complete date of birth in the public index, so the matching engine is working with less than it needs.
• Database-only searches. Some low-cost providers rely entirely on third-party aggregated databases that are compiled from bulk data purchases and never touch the actual courthouse record. Aggregated data can be stale, duplicated, or mismatched at the source, and by the time it reaches a report it has already passed through several hands with no verification at any step.
• Shared or reused identifiers. Family members with similar names (a father and son who share a name and live at the same address, for example) are a classic source of mixed files.

The legal standard: maximum possible accuracy

This is not a gray area under federal law. The Fair Credit Reporting Act requires that any consumer reporting agency preparing a report “follow reasonable procedures to assure maximum possible accuracy of the information concerning the individual about whom the report relates.” That language comes directly from 15 U.S.C. 1681e(b), and it is the legal backbone of every accuracy dispute in this industry. “Maximum possible accuracy” is a high bar. It does not excuse a report because the underlying public record was messy, and it does not excuse a screening company for passing along a database hit without verifying that the record actually belongs to the applicant.

For employers, this matters because you are the end user of that report and the one who acts on it. A hiring decision built on a mismatched record is a hiring decision built on someone else’s history, and that exposes you to negligent hiring and FCRA liability even though the error originated upstream.

Database-only matching versus verified matching

Not all background check processes carry the same risk of producing a mixed file. The table below shows the practical difference between a provider that relies on aggregated databases and one that verifies identity against primary sources before a record is reported.

No process eliminates mixed files entirely, because public records themselves are sometimes indexed poorly at the source. But the gap between a provider that stops at a database hit and one that verifies before reporting is the single biggest lever an employer has over this risk. It is also one of the reasons pricing varies across the industry. A background check package built around verified matching costs more to run than a raw database pull, and that cost difference is buying real accuracy work, not margin.

What happens when a candidate disputes a record

The FCRA gives every consumer, including your applicants, the right to dispute information they believe is inaccurate. That right and the process behind it come from 15 U.S.C. 1681i, and it is not optional for the reporting agency. Once a dispute is filed, the consumer reporting agency generally has 30 days to reinvestigate the disputed item, which typically means going back to the original source, such as the courthouse, to confirm whether the record actually matches the person. If the reinvestigation confirms the record is not a match, or that it is outdated, duplicated, or otherwise inaccurate, the agency has to delete or correct it and can no longer report it. The consumer also has the right to request the reporting agency notify anyone who received the report in roughly the prior two years so the correction follows the record.

For a mixed file specifically, this reinvestigation is usually straightforward once it is triggered, because the underlying court record either matches the applicant’s identifiers or it does not. The harder part is making sure disputes are actually caught and routed correctly in the first place, which is why a screening provider’s dispute intake process matters as much as its matching process. We cover the applicant-facing side of this in more detail in our guide to applicant disputes.

Your obligations as the employer during a dispute

A dispute does not just create work for the consumer reporting agency. It creates specific obligations for you as the employer, particularly if the disputed record was the basis, or part of the basis, for a decision to not move forward with a candidate. If you have already sent a pre-adverse action notice based on a report that is now under dispute, the safest and most defensible course is to pause the process and wait for the reinvestigation to conclude before finalizing an adverse action. Moving forward with a decision while the very fact underlying it is actively disputed is difficult to justify later, particularly since the applicant has already exercised a right the law specifically gives them.

This sits inside the broader adverse action framework that governs every FCRA-based hiring decision, from the initial notice and copy of the report through the waiting period to the final notice. We walk through each of those steps in our breakdown of the adverse action process, and it is worth having that sequence documented in your hiring procedures before you ever need it, not while a dispute is actively open.

Regulatory attention on background check accuracy

Accuracy in consumer reporting, including employment background checks, has drawn sustained attention from federal regulators. The Consumer Financial Protection Bureau has specifically flagged background check accuracy as an enforcement and guidance priority, addressing issues including incomplete records, outdated information, and records that were never properly matched to the correct individual. The Bureau’s own public statement on this, covering both background check accuracy and related credit file handling failures, is available directly from the CFPB newsroom. The Federal Trade Commission, which enforces the FCRA alongside the CFPB for many businesses, also publishes direct guidance for employers on their obligations when using consumer reports, available through the FTC’s business guidance resources. Neither agency treats a mixed file as a minor technical error. Both treat it as exactly the kind of harm the maximum possible accuracy standard was written to prevent.

What separates a rigorous screening process from a risky one

The practical takeaway for an employer choosing or evaluating a screening partner is that identity matching is not a back-office detail. It is the mechanism that determines whether the report you are about to act on actually describes the person who applied. A quality process treats every ambiguous match, meaning a common name, a thin identifier set, or conflicting address history, as a reason to slow down and verify rather than a reason to report and move on. It also means a dispute intake process that routes a challenged record back to the original source quickly instead of letting it sit, and documentation practices that let you show, if it is ever questioned, exactly how a record was matched to your candidate.

None of this eliminates risk entirely. Public records will always carry some ambiguity, and no matching process is perfect. But the gap between a provider that stops at a database hit and one that verifies before it reports is the difference between an occasional, quickly corrected error and a pattern of mixed files that eventually draws regulatory or legal attention.

Frequently asked questions

What is a mixed file on a background check?

A mixed file is a report that combines information from two or more people, usually because a name and partial identifiers matched more than one person in a court or database record. The result is that a record belonging to someone else, often a criminal case, appears on your applicant’s background check.

Who is responsible for fixing a mixed file error?

The consumer reporting agency that prepared the report is responsible for reinvestigating and correcting a disputed record under 15 U.S.C. 1681i. The employer is responsible for pausing any adverse action decision that relied on the disputed information until the reinvestigation is resolved.

How long does a background check dispute take to resolve?

Under the FCRA, a consumer reporting agency generally must complete its reinvestigation within 30 days of receiving the dispute, though this can extend in specific circumstances such as when the consumer provides additional relevant information during that window.

Can an employer make a hiring decision while a dispute is pending?

An employer can continue a hiring process, but should not finalize an adverse action based on a specific record that the candidate has actively disputed until the reinvestigation concludes. Doing so undermines the very process the FCRA sets up to protect against inaccurate reporting.

How can employers reduce the risk of mixed files in the first place?

Choosing a screening provider that verifies identity against primary sources, rather than relying solely on aggregated third-party databases, is the most effective way to reduce mixed file risk before a report is ever generated.

Related Reading

• Affordable vs. Cheap Background Checks: What Employers Should Know Before Choosing a Screening Provider
• Alias and Maiden Name Searches: How Background Checks Handle Name Changes
• When an Applicant Disputes a Background Check
• Background Check Red Flags: How Employers Should Read Results Without Overreacting

This article is general information, not legal advice. Background check accuracy obligations and dispute procedures involve federal and state law that applies differently depending on your situation, and you should consult qualified counsel before making hiring decisions based on a disputed or contested record.