Your dispute becomes a three-digit code. Here is the machine.

You mailed your dispute. What arrived at the other end was not your letter — it was a reason code. This page is the machine that sits between the two, and what the law actually requires to move through it.

What e-OSCAR is, and who owns it

e-OSCAR stands for Online Solution for Complete and Accurate Reporting. It is the system the credit bureaus use to move disputes and account updates between themselves and the companies that report data — the furnishers. It is not a government system and it is not a consumer tool: it is bureau-owned infrastructure, shared by Equifax, Experian and TransUnion, and the people who touch it are employees of bureaus and furnishers.

That single fact explains most of what feels wrong about the dispute process. Your letter is not read as correspondence. It is data entered into a form.

The path your letter actually takes

The route is short and entirely mechanical:

  1. Your letter arrives at the bureau. A person — or an intake process — reads it only far enough to decide what is being disputed and why.
  2. That "why" becomes a reason code. e-OSCAR carries a fixed list of three-digit dispute codes. Code 001 means "not his/hers". Others cover balances, dates, duplicated tradelines, account status. The nuance in your letter gets compressed into one of them.
  3. A code creates an ACDV — Automated Consumer Dispute Verification — and the ACDV is what gets forwarded to the furnisher.
  4. The furnisher answers the ACDV, usually through the same system, usually by picking from a short set of responses.
  5. The answer comes back and the bureau closes the dispute: verified, modified, or deleted.

A code is not a lie and the system is not a conspiracy. It is a compression step, and compression is exactly where a general dispute loses its teeth: if your letter says "this is inaccurate," the code that reaches the furnisher can be as vague as the letter was.

What "verified" means in practice

When a dispute comes back verified, most consumers read it as "a human checked my file and determined the item is right." What it usually means is that the furnisher answered the ACDV and said so. That is the whole chain of events.

This is why the answer so often ignores the specific thing you raised. If you wrote that a payment shows late in March while your statement shows it posted in February, and the ACDV that reached the furnisher only says "disputed — inaccurate," the reply can honestly be "we confirm this account is being reported correctly," without anyone looking at March.

What a verification does not prove: that the furnisher compared your documentation to its own records, or that the specific field you challenged was re-checked. It proves an answer was given.

What the law does require — Section 611(a)(2)

Under Section 611(a)(2) of the Fair Credit Reporting Act, when you send a dispute the bureau must forward it to the furnisher — and not just the dispute. It must include all relevant information you provided, in the time the statute allows: five business days.

That sentence is the practical reason your supporting documents matter. The CFPB's 2013 bulletin on credit report accuracy says the furnisher must review all relevant information the bureau passes along. If the bureau only forwards a reason code and you never sent anything else, then nothing else was ever going to be reviewed. A payoff statement, a statement showing the actual posting date, a copy of the identity theft report: these change what the furnisher is obligated to look at, because they change what is in the record.

What the law does not require

The clock is 30 days for the reinvestigation (45 if you send additional relevant information during that window). The furnisher has no extension of its own. If the disputed information cannot be verified, Section 611(a)(5)(A) says it must be deleted or modified.

The limits are just as real, and worth saying plainly:

Why generic letters die

Two rules do most of the killing.

The first is Section 611(a)(3): a dispute that is frivolous or irrelevant can be closed quickly, with reasons. Volume mailings that raise nothing specific — "this item is inaccurate, please remove it" — are the ones that get read that way.

The second is Regulation V, Section 1022.43(b)(2). For a direct dispute sent to a furnisher, the furnisher is not required to investigate if it reasonably believes the dispute was prepared on the consumer's behalf by a credit repair organization, or submitted on a form one supplied. A letter that arrives with a company logo, on familiar template language, looking like part of a bulk run, can be set aside on that ground alone. It is a legal excuse, and it is granted by how the letter looks.

That is why the letter has to sound like the person who signed it, and why it has to name something specific: an account, a field, a date, an amount.

What changes your case

The system you are feeding is a code-matching system, so the leverage is specificity — the more concrete the claim, the less room the code has to swallow it.

An honest limit. None of this guarantees an outcome. A bureau may verify, a furnisher may answer with a code, and an item that is accurate and inside its reporting window will stay. What the process can do is make the dispute specific enough that the answer has to address it — and leave you a record either way.

Where this fits in the product

CreditAuditAI audits the report PDF you upload, flags the items that may be inaccurate, outdated or unverifiable, and cites the section that governs each one. It then drafts the dispute letter in your own words, per item, per bureau — a letter you review, sign, and mail yourself. The audit is free and asks for no card; you pay only if you decide to keep using the tooling.

Illustrative excerpts shown anywhere on this site come from synthetic report data, never from a customer file.