Correcting the Error
Cost Him Five Points.

A federal court set down a man’s sworn account of fourteen months spent proving a mortgage was not his. Then it held that no reasonable jury could believe him, because deleting the false loan had lowered his credit score by five points.

Victor Manuel Ramirez Najera was thirteen years old when his father’s mortgage was opened. He and his father share a first name, a middle name and a last name; for a time they used the same address; and his father does not have, and has never had, a Social Security number for a matching system to check against. The loan, and the late payment history recorded against it, ended up on the son’s credit file and stayed there.

He disputed the file three times over roughly fourteen months: in March 2024, in July 2024, and again on May 28, 2025. Experian verified the account with the servicer each of the first two times and deleted it only on the third try, June 11, 2025, seven weeks after he had already sued. His FICO score, 645 on June 3, 2025, dropped to 640 the day the account came off his file.

That was the number the court used to end his claim for damages. “The falsely reported mortgage, albeit incorrect, actually helped Ramirez’s credit score,” the order reads. Correcting his file, not the error itself, was what had cost him. On that arithmetic, a federal judge held that no reasonable jury could believe his own sworn account of what fourteen months of this had done to him. His claims were dismissed with prejudice, on that ground and on others.

The rules a judge asked to see

The machinery is ordinary. Experian calls the system an algorithm, Find Consumer, that sorts through name, address, birth date and Social Security number, with “both automated and manual quality controls” built in to catch errors. His own appeal brief, citing testimony from two Experian witnesses taken in deposition, states the mechanism plainly: Find Consumer “can assign incoming data to an existing PIN based on a matching name and address; it does not require a matching Social Security number … or date of birth.”

A sworn declaration from one of his attorneys, filed to compel its production, places the rules governing that match in a Microsoft Word file on Experian’s internal servers, called the Find Consumer Detail Requirements and Design Document, or the DRDD. The same declaration describes deposing Timothy Sumida, a former Experian employee named as an inventor on several of the company’s matching patents, about how it works. Asked whether the DRDD held anything beyond the name of a code, Sumida testified: it “doesn’t really refer to the name of the code. It -- it provides the requirements, and then the code is intended to match the requirement … it doesn’t contain code.” The declaration goes further than the single filed page of testimony: “Beyond generalities, Sumida was unable to testify about why specific data would be matched to a consumer’s credit file.” The characterization is the plaintiff’s own counsel’s sworn account, not the witness’s own words and not a court’s finding.

On December 17, 2025, his lawyer wrote to counsel for Experian with an offer, telling her that Experian had already taken the position that it objected to producing the DRDD “under any circumstances.” His client would stop asking to see it, he proposed, if Experian would agree not to argue that the rules inside it achieve maximum possible accuracy. Counsel for Experian refused the same day. Disclosing the document posed a “risk of harm … not proportional to the needs of this case,” she wrote back. And in any case, she added, “I understand that Experian’s algorithm is designed to assure maximum possible accuracy” (the federal statute’s own standard for a credit bureau) “thus I cannot agree to what I understand to be an untrue … stipulation.”

Four days later, Experian moved for summary judgment on the reasonableness of the procedures those rules produce. Ninety-nine days after the refusal, the court granted it. Kimberly Cave, Experian’s Director of Litigation Support, testified that matching procedures need room to “accommodate and allow changes and variations in items of information” over a lifetime, or “millions of consumers would be likely to have incomplete or fragmented files.” The court agreed. The order runs nineteen pages; the DRDD, Find Consumer and Sumida appear in none. Eight days before it issued, a magistrate judge had ordered the document to chambers for in camera inspection. Two days after the production deadline, the court granted summary judgment and denied the motion to compel as moot.

The birth certificate

The refusal was not the first time evidence went the wrong way. On the second of his three disputes, he sent Experian a birth certificate and school records, to show he had been a minor when the mortgage was opened. “This information should have notified Experian that it needed to go beyond the ACDV system,” the court found. Instead Experian sent an automated verification request to Rushmore, the mortgage’s servicer, which verified the account again, and Experian kept reporting it. “Experian concedes that this should not have been the case,” the order states. The system is not blind in every direction: earlier in the same file, a second furnisher, PennyMac, had returned a Social Security number and birth date that did not match his, and Experian deleted that account without being asked twice. The system caught one furnisher’s mismatch and kept reporting his father’s mortgage as his own.

A federal regulator alleges the same pattern as standing practice. The Consumer Financial Protection Bureau sued Experian in January 2025, claiming the company “uncritically accepts the original furnisher’s response … even when that response was improbable or illogical on its face.” The case is pending; the Bureau’s claims have not been decided.

What was his, and what wasn’t

The record does not make him a clean casualty. Three other negative accounts on his file belong to him alone: a collection account, a past-due balance, one charged off. He also says the error cost him an apartment. He applied to rent one in Nashville while expecting a child, and was turned down. But he has no denial letter, only the credit report generated with the application, and the court found no evidence that Experian’s reporting caused it.

He gave the court his own sworn account of what those fourteen months had cost him, and the court had affidavits and corroborating testimony besides. The court set all of it down. It is the same court that, on the arithmetic above, held it could not be believed.

The Agentics read

Agentics reads this case through Digital Derangement Syndrome™ (DDS™): AI-mediated systems failing to recognize legitimate authority. No AI system is named in this record. The characteristic that fits is Contextual Ambiguity, with one clause of Trust Transfer Failure beside it. Edition No. 047 filed the same collision inside an answer engine. This one needed no answer engine at all.

Where the argument stops

He was not vindicated. The court found his file inaccurate and his second dispute inadequately investigated, and dismissed his claims with prejudice. His appeal is pending before the Fifth Circuit, No. 26-10290; no appellee brief appears on the public docket, which is not the same as saying Experian has not responded. The design document is not raised in his opening brief. The CFPB’s case against Experian is pending; its claims are allegations, not findings.

He has not spoken for himself here. What is attributed to him comes through his sworn testimony as the court summarized it, his lawyer’s filings, or a declaration on his behalf. The one deposition page filed with that declaration is the only place the former Experian employee speaks in his own words. The mapping to DDS™ is this record’s editorial reading, not a finding by any court.