Someone Else's Debt Is Mixed Into My Credit File

A mixed file is not a data-entry typo — it is a structural failure by a credit bureau to keep your records separate from a stranger’s. When a bureau’s matching system incorrectly links two consumers’ files, the merged result can carry someone else’s collections, charge-offs, foreclosures, or judgments directly under your name. Because the FCRA requires bureaus to maintain accurate files, a mixed file is an actionable violation from the moment it exists — not only after you dispute it.

The harm is concrete. Lenders, landlords, and employers pulling your report see only what the bureau provides. They cannot tell the accounts are not yours. A single merged collection account can drop your score far enough to cost you a mortgage, an apartment, or a job offer.

How Bureau Matching Logic Merges the Wrong Files

Each of the three major bureaus — Equifax, Experian, and TransUnion — assigns incoming data to existing consumer files using a probabilistic matching algorithm. When a lender or debt collector reports a new account, the bureau compares it against its database using identifiers: name, Social Security number, date of birth, and address history. If the incoming data matches an existing file on enough fields, the bureau routes it there rather than opening a new file.

Mixed files most commonly affect consumers who share a name with a close relative — a parent and child with the same name and a different suffix (Jr./Sr.), or siblings with near-identical names. A single transposed digit in a Social Security number can also trigger a merge. People who have lived at the same address as a relative, or who share a former address, face elevated risk even if their names are quite different.

The bureau does not alert you when a merge occurs. Your file simply grows new unfamiliar accounts, often from creditors you have never dealt with, in states where you have never lived.

The Federal Accuracy Duty That a Mixed File Breaches

The FCRA imposes a clear standard on consumer reporting agencies. Under 15 U.S.C. § 1681e(b), a bureau must “follow reasonable procedures to assure maximum possible accuracy of the information concerning the individual about whom the report relates.” A file that contains another person’s accounts is not maximally accurate by definition.

Courts have consistently held that § 1681e(b) is not satisfied merely by showing that the bureau’s algorithm was technically within industry norms. If the algorithm produces recurring, identifiable errors for consumers with common names or minor identifier variations, and the bureau has declined to implement known corrective measures, a jury can find that the procedures were not reasonable. Several courts have gone further and found willfulness where a bureau continued merging files after receiving repeated complaints about the same pattern.

For a broader overview of what the FCRA requires, see our guide to your rights under the FCRA.

Isolating the Foreign Accounts Before You Write a Single Letter

Effective dispute preparation starts well before you draft anything. Pull all three bureau reports and go through every line. For each account, public record, or inquiry you do not recognize, document:

• The creditor name, account number (even partial), and the date opened
• The billing address or state associated with the account
• Whether the name on the account matches yours exactly or carries a different suffix, middle initial, or spelling
• Any SSN digits that are visible and whether they match yours

Save dated copies. Certified printed reports from AnnualCreditReport.com create a cleaner evidentiary record than screenshots, but screenshots with timestamps are acceptable as a supplement. The goal is to establish, with precision, what was in your file and when — information you will need if the dispute fails and the matter proceeds to litigation.

If you can see that your file contains two different Social Security numbers, even partially masked, note that explicitly. Two SSNs in one file is among the clearest markers of a bureau-level mix.

Why Mixed-File Disputes Demand More Documentation Than Routine Ones

An ordinary dispute — a balance reported higher than the actual figure — can often be resolved with a short letter identifying the account and the discrepancy. A mixed-file dispute is structurally different because the bureau’s standard reinvestigation process can actually confirm the error: the bureau forwards your dispute to the furnisher, whose records correctly show a debt owed by the other consumer, and the furnisher verifies it. The bureau leaves the account in place.

Under 15 U.S.C. § 1681i(a)(1), the reinvestigation must be “reasonable.” Mechanically forwarding a dispute to a furnisher whose data is accurate for a different person — without any inquiry into whether the account belongs to the disputing consumer — is arguably not a reasonable investigation for a mixed-file claim.

To break the cycle, your dispute letter should explicitly state that the account belongs to a different person, not merely that it is “inaccurate.” Include copies of your government-issued ID, Social Security card, and a current utility bill or bank statement showing your correct identifying information. Point to any discrepancy visible on the foreign account — a different suffix, a different address state, different SSN digits. Request that the bureau flag your file to prevent future merging.

Send the letter by certified mail, return receipt requested, to each bureau’s dedicated dispute address. Online dispute portals can limit what supporting documentation you are able to attach. Keep the green card. If the bureau deletes the accounts and they reappear, that reinsertion triggers separate procedural requirements under § 1681i(a)(5)(B), and each improper reinsertion is its own violation.

Furnisher Obligations After a Mixed-File Dispute Is Filed

When you dispute a mixed account with the bureau, the bureau notifies the furnisher that reported it. Under 15 U.S.C. § 1681s-2(b), that furnisher must then conduct its own investigation, review all relevant information transmitted by the bureau, and report its findings back. The furnisher cannot simply re-verify that the account exists in its system — it must investigate whether the account was correctly attributed to the disputing consumer.

In a genuine mixed-file case, a diligent furnisher investigation would reveal that its customer records show a different address, a different phone number, or a different SSN than the disputing consumer’s. A furnisher that fails to examine those underlying identifiers and simply confirms the account without investigation has breached § 1681s-2(b). You may also send a written dispute directly to the furnisher, which triggers the same investigation obligation independently of the bureau process.

What Makes a Mixed-File Claim Actionable Rather Than Academic

Mixed-file claims vary significantly in strength. The factors that tend to make one actionable:

Concrete adverse consequences. A denied mortgage, a rejected rental application, a higher-rate auto loan, or a rescinded job offer creates measurable harm that supports meaningful damages. Anxiety and inconvenience alone rarely drive a case to resolution.

Bureau conduct after dispute. A bureau that corrects the file on the first try and keeps it clean has substantially lower exposure than one that reinstates the accounts, ignores the dispute, or re-mixes the file within months of correcting it.

Willfulness evidence. Under 15 U.S.C. § 1681n, a willful violation entitles you to statutory damages between $100 and $1,000 per violation — without proving a dollar of actual loss — plus punitive damages and attorney’s fees. Evidence that the bureau knew its algorithm produced mixed files for consumers with common names and declined to fix it supports a willfulness argument.

A documented paper trail. Certified-mail receipts, dated report copies showing the foreign accounts, adverse-action notices from lenders, and any written responses from the bureau are the foundation of a winnable case. Start preserving that record the day you find the error.