The word in the statute is reasonable. That one word carries an enormous load, and what it demands in a particular case is where credit reporting litigation actually lives. My cases turn on it far more often than they turn on whether the tradeline was wrong.
Two standards, one word
15 U.S.C. § 1681e(b) governs preparing a report:
Whenever a consumer reporting agency prepares a consumer report it shall follow reasonable procedures to assure maximum possible accuracy of the information concerning the individual about whom the report relates.
15 U.S.C. § 1681i(a)(1)(A) governs responding to a dispute: a free and reasonable reinvestigation to determine whether the disputed information is inaccurate, generally within 30 days of receipt, extendable by up to 15 days if the consumer supplies relevant information during the initial period.
Two more provisions do quiet work. Section 1681i(a)(4) says the agency shall “review and consider all relevant information submitted by the consumer.” And § 1681i(a)(5)(A) requires prompt deletion or modification of information found inaccurate or incomplete or that cannot be verified. That’s three triggers, and the third one never asks the consumer to prove the item false.
What the pipeline actually does
You can’t win a reasonableness argument on rhetoric. Knowing how the machine works is what turns it into evidence.
The CFPB’s December 2012 study of the credit reporting market laid out the process. A consumer’s dispute gets boiled down to one or two numeric reason codes drawn from a list of 29, then sent to the furnisher through the industry’s e-OSCAR system on an Automated Credit Dispute Verification form carrying up to 255 characters of free-form text. In 2011, free-form text was added to roughly 26% of transmissions. The bureaus resolved about 15% of trade line disputes internally and referred about 85% to furnishers. On the furnisher’s end, a representative typically compared the dispute against the furnisher’s own electronic records.
The CFPB’s January 2022 report to Congress under § 611(e) describes the same setup, noting that the ACDV includes a dispute code, narrative text, and — since 2013 — supporting documents provided by consumers.
Two numeric codes and 255 characters. Hold that up against “maximum possible accuracy” and, in certain kinds of cases, the argument writes itself.
The errors the system can’t find
Mixed files. If the account belongs to a different person with a similar name, the furnisher’s records show a real, genuinely delinquent account belonging to its actual customer. The verification comes back accurate as to the account and completely beside the point, because the live question is why that account is attached to my client’s file. Nothing in the pipeline asks it.
Re-aged collections. When the dispute is that the date of first delinquency is wrong, asking the furnisher to confirm the date in its own system just confirms the number the furnisher typed. Section 1681c(c)(1) pins the seven-year clock to the delinquency immediately preceding the collection activity or charge-off, and § 1681s-2(a)(5) requires the furnisher to report that month and year. A debt buyer that never held the original creditor’s records can’t verify the date by checking its own. It can only repeat itself.
Documentary disputes. Send a cancelled check, a settlement agreement, or a bankruptcy discharge, and the question becomes whether that document was reviewed and considered under § 1681i(a)(4), or whether the dispute got squeezed into a code that never told the furnisher a document existed at all.
Legal-status disputes. Whether a debt was discharged in bankruptcy, or whether a judgment was vacated, isn’t something a furnisher answers by checking that its balance field still says what it thinks it says.
The request almost nobody makes
The most under-used provision in this part of the Act is § 1681i(a)(6)(B)(iii): the results notice must advise that, on request, the agency will describe the procedure used to determine accuracy and completeness, including the business name and address of any furnisher contacted and its telephone number if reasonably available. Section 1681i(a)(7) requires that description not later than 15 days after the request.
Make that request promptly and you get a contemporaneous account of method, in the agency’s own words, naming who it actually contacted. In litigation, that puts the whole reasonableness fight on the agency’s own description instead of a reconstruction somebody pieces together two years later. I send it as a matter of course.
The rest of the record is boring, and it decides cases: dated reports from before and after, the disputes as sent, proof of delivery, everything received, and the envelopes. Whether a reinvestigation was reasonable gets judged on what the agency had sitting in front of it.
Reasonable is a process question
None of this makes the FCRA a guarantee of accuracy. Section 1681e(b) requires reasonable procedures, not perfect files, and it isn’t strict liability. An agency that ran a sound process and still got it wrong has a real defense, and I tell clients so.
That’s exactly why the interesting question is almost never whether the item was wrong. It’s whether what the agency did, given what it was told and what it was sent, was reasonable. That’s a question about process, and you prove it with documents. The documents worth having are the ones you can gather this week, before anybody files anything.
This article is general information about federal law, not legal advice, and reading it does not create an attorney-client relationship. Nothing here characterizes the conduct of any particular company or predicts any outcome. How we evaluate a disputed credit file.