Metro 2 explained: the data format behind your credit report

Nobody at a credit bureau reads your credit card statement. What reaches Equifax, Experian and TransUnion each month is a structured record that your lender’s software generates from its own account system: a row of codes and numbers describing where your account stands as of a certain date.

That record format is called Metro 2. Once you see your report as a translation of coded fields, a lot of confusing things start to make sense. It explains why the same account can look slightly different at each bureau, why a paid collection can still read as a collection, and why a carefully written two-page dispute letter often gets a one-line answer.

Who writes the Metro 2 rules, and why you can’t read them

The Consumer Data Industry Association (CDIA), the trade group for the credit reporting industry, developed the Metro 2 guidelines in 1997 on behalf of the nationwide bureaus and Innovis, according to the CFPB’s 2012 white paper on the credit reporting system. Metro 2 replaced an older format, known just as Metro, that dated to the late 1970s.

The detailed instructions live in a manual called the Credit Reporting Resource Guide, usually shortened to CRRG. CDIA copyrights it and restricts access to employees of four kinds of organizations: furnishers (the lenders and collectors that send data), data processors, software vendors that build Metro 2 programs, and consumer reporting agencies. Each approved user has to accept an access agreement.

So this article does not reproduce the manual. What follows is a plain-English description built from public sources, mainly CDIA’s own public page and the CFPB’s analysis. If someone sells you a “Metro 2 letter” packed with field numbers, ask yourself how they got the guide and whether the codes they cite actually point to something wrong in your file.

What’s inside a Metro 2 file

Each monthly submission from a furnisher follows the same skeleton. The CFPB describes it as a header record, a series of base records for each borrower, supplementary segments where needed, and a trailer.

One gap surprises people. The CFPB found that Metro 2 has no field for the interest rate on a loan or card. A bureau knows your balance and limit but not your APR.

The scale is large. In that 2012 review, the CFPB reported that the nationwide bureaus received data from roughly 10,000 furnishers and that each kept more than 1.3 billion active tradelines, with furnishers typically sending updates monthly in batch files. Those figures are more than a decade old, but the monthly batch rhythm is why your report rarely changes the same day you pay.

The fields that decide how an account reads

You never see field names on a consumer report, but each line you read traces back to one. These are the ones that matter most in a dispute:

• Account status. This field says whether the account is current, how far behind it is (the CFPB lists bands such as 30 to 59 days, 60 to 89 days, up to 180 days or more), or how it closed: paid, voluntarily surrendered, repossessed, charged off, foreclosed.
• Payment history profile. A 24-month string, one character per month, that becomes the payment history grid on your report.
• ECOA code. Who is responsible for the account: you alone, you jointly, or you as an authorized user. A wrong code here can put someone else’s debt on your file.
• Date of first delinquency. The date that starts the seven-year reporting clock for most negative items. If it’s reported later than the truth, the item stays longer than the law allows. See how the date of first delinquency works.
• Special comment code. Short standardized remarks, such as an account closed at the consumer’s request or a payment arrangement.
• Compliance condition code. The field that flags an account as disputed under the FCRA, and later records that the dispute was resolved. The “consumer disputes this account” remark comes from this field, and it matters a lot to mortgage applicants.
• Balances and limits. Current balance, amount past due, and credit limit or highest credit.
• Key dates. Opened, last payment, closed, and the date the data was current.

How a dispute travels: e-OSCAR and the ACDV

The bureaus don’t phone your lender when you dispute. They use e-OSCAR, an electronic network the CFPB describes as built and owned by Equifax, Experian, Innovis and TransUnion. The bureau converts your dispute into an electronic form called an ACDV (automated consumer dispute verification) and routes it to the furnisher.

According to the CFPB’s 2012 paper, the bureau characterizes each dispute with one or two reason codes from a fixed list (29 codes at that time) and can attach up to 255 characters of consumer-supplied text. The furnisher checks its records and answers in codes: verified as reported, modified, or deleted. The bureau then updates your file and, under 15 U.S.C. 1681i, generally has 30 days from receiving your dispute to finish, with results due to you within 5 business days after it completes.

Here is what the CFPB reported about outcomes in that period:

These numbers are old, and the bureaus have changed their systems since then. They still show something useful: most disputes that reach a furnisher came back with some change, and “verified” was the minority answer.

Example: what survives when your letter becomes an ACDV

Say you write a careful 1,800-character letter about a collection whose date of first delinquency is wrong. If the free-text space is 255 characters, as the CFPB reported, the room for your own words is about 14% of what you wrote (255 divided by 1,800 is 0.14). The bureau can forward your documents as well, but the text field and the reason code are what frame the request.

Put the whole case in one plain sentence near the top of your letter, written so it could stand alone:

“The date of first delinquency is wrong. My first missed payment on this account was the June 2019 bill, not March 2021. Bank statements showing the missed June 2019 payment are enclosed.”

That’s under 200 characters. It names the field, gives the correct value, and points to proof. A furnisher employee comparing your claim to their records has something specific to check.

What this means when you dispute

The format rewards precision. A few habits follow from how the pipeline works:

• Dispute a field, not a feeling. “This account is wrong” gives the system nothing to compare. “The balance shows $2,340 but I paid it to zero in May, statement enclosed” does.
• Pick the right claim. “Not mine” and “inaccurate information” land in different reason codes, and the code tells the furnisher what to check. Use the one that’s true.
• Go to the source too. The bureau only relays your dispute. The furnisher holds the records and sends the data, so a direct dispute with the furnisher puts your full explanation in front of the company that can correct it at every bureau at once.
• Be skeptical of “not Metro 2 compliant” templates. A field that is genuinely wrong, like a sold account still showing a balance, is a real inaccuracy worth disputing. A letter that declares every account noncompliant without saying what’s wrong reads as boilerplate, and the bureau can treat it as frivolous.

Your next moves

1. Pull your reports from all three bureaus at AnnualCreditReport.com, which offers free weekly reports.
2. For each account you think is wrong, write down which field is off: status, dates, balance, responsibility, or ownership.
3. Gather the document that proves the correct value.
4. Draft a dispute that leads with one standalone sentence naming the field and the right answer. The free letter builder can help you structure it.
5. If the answer comes back “verified” and you have proof, read what to do after a verified dispute.