What is Metro 2?
The foundation of all credit reporting
Explained in plain English — no jargon, no confusion.
The simple explanation

Metro 2 is the rulebook that tells creditors exactly how to report information to credit bureaus. It was created by the Consumer Data Industry Association (CDIA) — the trade group that represents credit bureaus — and it sets the standard format, field definitions, and compliance rules every furnisher must follow when submitting data.

Analogy
Think of Metro 2 like a federal tax form. The IRS doesn't just let you write your income in any format you want — they give you a standardized form with specific fields, specific codes, and specific rules. If you fill in the wrong box, your return is wrong. Metro 2 works the same way. If a creditor puts the wrong code in the wrong field, their reporting is non-compliant — and under the FCRA, non-compliant reporting can be disputed and deleted.
Why Metro 2 matters for credit repair

Most people dispute credit items by saying "this isn't mine" or "this is wrong." That works sometimes. But Metro 2 compliance disputes are different — they attack the technical accuracy of HOW information was reported, not just WHAT was reported.

Standard dispute approach

"This account doesn't belong to me." Bureau verifies with creditor. Creditor confirms. Dispute denied.

Metro 2 compliance approach

"This account contains a Date of First Delinquency in Segment J2 that conflicts with the payment history grid in Segment K4 — a direct Metro 2 formatting violation." Much harder to verify. Frequently deleted.

Metro 2 disputes force the bureau and furnisher to verify not just that the account is yours, but that every data field is formatted correctly and internally consistent. Most creditors cannot — or will not — do this level of verification within the 30-day window.

The legal foundation: why this works

Metro 2 disputes are grounded in three laws that work together:

LawWhat it saysHow it applies
FCRA §611Bureaus must conduct a "reasonable investigation" of disputesA Metro 2 non-compliance dispute requires more than a creditor simply confirming the account exists
FCRA §623Furnishers must report accurate and complete informationMetro 2 non-compliance = inaccurate or incomplete reporting under this standard
FCRA §607(b)Bureaus must follow reasonable procedures for maximum accuracyAccepting non-compliant Metro 2 data without verification violates this requirement
The key insight

Under FCRA §611, if a bureau cannot complete a reasonable investigation within 30 days, the disputed item must be deleted. Metro 2 compliance disputes are intentionally detailed and technical — they are designed to be difficult to verify within the statutory window.

Metro 2 vs. Metro 1 — what changed

The original credit reporting format was called Metro 1 (or "tape to tape"). Metro 2 replaced it in 1997 and added hundreds of new data fields, compliance requirements, and standardized codes. The upgrade matters for credit repair because:

  • Metro 2 created specific field-level rules that Metro 1 never had — each field now has defined acceptable values
  • Any creditor still using Metro 1-era practices is automatically non-compliant with current standards
  • The more fields that exist, the more opportunities for inconsistencies to appear between them
  • Many smaller collection agencies and credit unions were slow to fully implement Metro 2 — their data is often the most vulnerable to compliance-based disputes
The Metro 2 data fields — explained simply
Every credit account is reported using these standardized segments and fields. Each one is an attack point.
How Metro 2 is structured

Metro 2 data is organized into segments — think of them like sections of a form. Each segment contains specific fields. The main segments used in credit reporting are:

SegmentPlain English nameWhat it contains
Base SegmentThe account summaryAccount number, consumer name/SSN/DOB, account type, balance, credit limit, payment status, open/close dates
J1 SegmentAssociated consumer #1Second person on the account (joint account holder or co-signer)
J2 SegmentDelinquency infoDate of first delinquency (DOFD) — the most disputed field in all of credit reporting
K1 SegmentPurchased portfolio infoOriginal creditor details when a debt has been sold/purchased
K2 SegmentMortgage infoProperty address and type for mortgage accounts
K3 SegmentOriginal creditor infoName and address of the original creditor before sale
K4 SegmentSpecialized payment infoPayment history for up to 24 months — the payment grid
L1 SegmentStudent loan infoLoan type, program, scheduled graduation date
N1 SegmentEmployment infoEmployer name, address, hire date (rarely used)
The critical fields — and why each one matters

These are the fields that appear in virtually every dispute. Understanding what each field is supposed to contain — and what counts as a violation — is the foundation of Metro 2 credit repair.

Date of First Delinquency (DOFD)
The date you first missed a payment that led to the current delinquent status. This field sets the 7-year removal clock.
Attack: Wrong date, missing date, or date that contradicts the payment history grid
Account Status Code
A 2-digit code describing the current state of the account (e.g., 11=current, 64=collection, 97=charge-off).
Attack: Wrong status code, or status code that conflicts with other fields
Payment Rating
A single character indicating payment behavior (0=current, 1=30 days late, 2=60 days, etc.).
Attack: Rating inconsistent with payment history grid or account status code
Payment History Profile
A 24-month string of payment codes showing exactly what happened each month (B=no payment due, 0=current, 1=30 late, etc.).
Attack: History inconsistent with DOFD or dates, or contains improper codes
Current Balance
The amount owed as of the most recent reporting date. Must be $0 for charged-off accounts sold to a collector (original creditor).
Attack: Balance still showing at original creditor after being sold to collector
Date Opened
The date the account was originally opened with the original creditor. Cannot change when debt is sold.
Attack: Date changed when debt was sold — creates artificial account age manipulation
Date Closed
The date the account was closed. Must be present if account status indicates closed. Must be absent if account is open.
Attack: Missing when required, or wrong date that conflicts with status code
Account Type Code
2-digit code identifying the type of account (01=revolving, 26=auto loan, 18=mortgage, 02=open, etc.).
Attack: Wrong account type for the product reported (e.g., student loan coded as revolving)
Terms Duration / Terms Frequency
How many payments and how often (monthly, bi-weekly, etc.). Must be consistent with the account type.
Attack: Terms don't match account type, or show 0/blank for active installment accounts
Compliance Condition Code
Optional code used to explain special circumstances (XB=disputed, XH=in bankruptcy, XR=re-investigated).
Attack: Missing XB code when consumer has filed a dispute — bureau must flag it
Consumer Information Indicator
Code indicating the consumer's situation (Q=deceased, A=bankruptcy, H=ECOA-related, etc.).
Attack: Wrong code applied, or missing when required by law
Scheduled Monthly Payment Amount
The contractual minimum payment amount. Required for installment accounts. Must match original loan terms.
Attack: Shows $0 or blank for active installment accounts — Metro 2 violation
How credit reporting actually works
The lifecycle of a credit account from opening to reporting — and where compliance breaks down.
The reporting lifecycle — step by step
1
Creditor opens the account
When you open a credit card, loan, or line of credit, the creditor becomes a "data furnisher." They are now responsible for reporting your account to the credit bureaus monthly in Metro 2 format.
2
Monthly data submission
Each month, furnishers submit a data file to the bureaus (Equifax, Experian, TransUnion) containing every account they manage. Each account record must be formatted in Metro 2 compliant fields.
3
Bureaus receive and load the data
The bureaus have their own internal systems that parse the incoming Metro 2 data. They apply their own logic on top — but the raw data must arrive in compliant format or it creates errors in the consumer's file.
4
Consumer disputes — verification is triggered
When a consumer files a dispute, the bureau sends an "ACDV" (Automated Consumer Dispute Verification) request to the furnisher through a system called e-OSCAR. The furnisher has 30 days to verify or correct.
5
The Metro 2 compliance gap
Most furnishers respond to ACDVs by simply confirming the account belongs to the consumer — they do NOT perform a field-by-field Metro 2 compliance review. A detailed compliance dispute forces them to do this, which most cannot complete within 30 days.
6
30-day deadline → mandatory deletion
If the furnisher cannot verify every disputed field within 30 days (45 days if you provide additional information), the bureau must delete the item under FCRA §611. This is the engine that powers Metro 2 credit repair.
The e-OSCAR problem — why most verifications are inadequate

e-OSCAR is the electronic system bureaus use to send dispute verification requests to furnishers. Understanding it is critical to understanding why Metro 2 disputes work.

What e-OSCAR actually does

It sends a 2-digit dispute code to the furnisher. The furnisher's system automatically matches the account by number, confirms it exists, and sends a "verified" response — often in seconds, via automation. No human reviews the Metro 2 field compliance.

What a proper verification requires

Under FCRA §611, a "reasonable investigation" must actually examine the original records — the original contract, payment records, and Metro 2 data fields. Automated e-OSCAR confirmation does not meet this standard for a detailed compliance dispute.

Your leverage: the Method of Verification demand

After a "verified" response to your Metro 2 dispute, you can demand the Method of Verification (MOV) in writing. Ask: "What specific information was reviewed during this investigation?" If the answer reveals only an automated e-OSCAR match — with no review of Metro 2 field-level compliance — you have grounds to argue the investigation was unreasonable under FCRA §611, and to escalate to the CFPB.

Metro 2 compliance attack points
20 specific violations you can dispute for deletion. Click any attack point to expand the full strategy.
01
Date of First Delinquency (DOFD) — missing or wrong
Segment J2 | Base Segment field 25
High impactDeletion likely
►
What it is
The date you first missed a payment that led to the current delinquency. Metro 2 requires this field to be populated for any account in a delinquent status. It must also match the account's payment history grid.
The violation
(a) DOFD field is blank — required field missing. (b) DOFD date is more recent than the last on-time payment shown in the payment history grid. (c) DOFD has been updated/changed after the original delinquency (re-aging). (d) DOFD is the same as the charge-off date (it must precede the charge-off by approximately 180 days).
Why it works
A missing or wrong DOFD makes the account's 7-year expiration date unverifiable. Bureaus cannot confirm accuracy without a valid DOFD. Furnishers who re-aged the debt cannot produce original records that support the newer date.
Dispute language template

"The Date of First Delinquency (DOFD) reported in Segment J2 of the Metro 2 data file for Account #[XXXX] is [blank / inconsistent with the 24-month payment history profile]. Under Metro 2 compliance standards, DOFD is a required field for any account reporting a delinquent status. The absence or inaccuracy of this field renders the account's reporting non-compliant with Metro 2 format requirements and FCRA §623(a)(1). I demand deletion or immediate correction with documented verification of the original DOFD date."

02
Payment history profile — inconsistency with account status
Base Segment fields 17B / K4 Segment
High impactDeletion likely
►
What it is
The payment history profile is a 24-character string showing monthly payment status for the past 2 years. Each character represents one month. Metro 2 codes: 0=current, 1=30 days late, 2=60 days, 3=90 days, 4=120 days, 5=150 days, 6=180+ days, B=no payment required, E=zero balance.
The violation
(a) History shows "current" payments in months that predate the reported DOFD — logically impossible. (b) History shows "B" (no payment due) during months when the account was clearly active. (c) History string contains codes that don't exist in the Metro 2 standard. (d) Account status code shows "charge-off" but history profile shows on-time payments in recent months.
Why it works
Internal inconsistency between the payment history string and the account status code is a clear Metro 2 formatting violation. The creditor cannot "verify" an account where the data contradicts itself.
Dispute language template

"The Payment History Profile (Base Segment field 17B) for Account #[XXXX] contains entries inconsistent with the reported Account Status Code and Date of First Delinquency. Specifically, the payment profile indicates [describe inconsistency] which is logically incompatible with [the reported status/DOFD]. This internal inconsistency constitutes a Metro 2 formatting violation and demonstrates the reporting is not 'complete and accurate' as required by FCRA §623(a)(1)."

03
Original creditor still reporting balance after debt sale
Base Segment — Current Balance field
High impactDuplicate violation
►
What it is
When a creditor sells a debt to a collection agency, Metro 2 requires the original creditor to update their reporting to reflect a $0 balance and a status of "transferred/sold." The collection agency then reports the new account separately.
The violation
Original creditor continues to report a non-zero balance after the debt was sold. Both the original creditor AND the collection agency are reporting a balance for the same underlying debt — this is double-reporting of the same amount, inflating the consumer's total reported debt and hitting the utilization/amounts owed factor twice.
Why it works
Metro 2 explicitly requires the selling creditor to zero out the balance and update the account status. Failure to do so is a direct Metro 2 violation AND results in inaccurate data being reported — both grounds for deletion of the original creditor's entry.
Dispute language template

"Account #[XXXX] with [Original Creditor] continues to report a balance of $[amount] despite this debt having been sold or transferred to [Collection Agency] on or around [date]. Under Metro 2 compliance standards, the selling furnisher is required to report a $0 balance and account status reflecting the transfer. Continued reporting of a balance by [Original Creditor] simultaneously with [Collection Agency]'s reporting constitutes duplicate reporting of the same debt — a direct Metro 2 violation and FCRA §623 inaccuracy. I demand deletion of [Original Creditor]'s entry."

04
Re-aging — DOFD updated after debt was sold
Segment J2 | Base Segment — DOFD field
High impactFCRA violation
►
What it is
Re-aging is when a debt buyer or collection agency reports a DOFD that is more recent than the original delinquency date — essentially resetting the 7-year clock. This directly extends how long a negative item can legally remain on a consumer's report.
The violation
The DOFD must always reflect when the consumer first went delinquent with the original creditor. Debt buyers are prohibited from reporting a new DOFD based on when they purchased the debt, when they first attempted to collect, or when the account was transferred to them. Any DOFD that is later than the last on-time payment to the original creditor is likely a re-aging violation.
How to detect it
Compare the collection account's DOFD against: (1) the original creditor's account opening and last payment dates, (2) the DOFD shown on the original creditor's entry if still on the report, (3) your own records of when you last made a payment. If the collector's DOFD is 6+ months later than the original, it's likely re-aged.
Dispute language template

"The Date of First Delinquency reported by [Collection Agency] for Account #[XXXX] is [date] — which postdates the last on-time payment to the original creditor and/or the DOFD reported by [Original Creditor]. Metro 2 standards and FCRA §605(c) require DOFD to reflect the consumer's first delinquency with the original creditor — not the date the debt was acquired by a subsequent collector. This constitutes illegal re-aging, which artificially extends the 7-year reporting window under FCRA §605(a). I demand immediate deletion."

05
Wrong account status code
Base Segment — Account Status field
Medium impactCorrection / deletion
►
What it is
Metro 2 uses specific 2-digit codes to describe account status. Common codes: 11=current, 71=30 days past due, 78=60 days, 80=90 days, 82=120 days, 83=150 days, 84=180 days, 97=charge-off, 64=collection/charge-off, 13=paid/closed, 62=paid collection.
The violation
(a) Status code 97 (charge-off) used for an account that was never formally charged off. (b) Status code 11 (current) used simultaneously with a non-zero payment rating indicating lateness. (c) Account shows status 13 (paid/closed) but still reports a balance. (d) Collection account using an account status code reserved for original creditor accounts. (e) Paid collection still showing status 64 instead of 62.
Dispute language template

"Account #[XXXX] is currently reporting with Account Status Code [XX], which is inconsistent with [the reported payment rating / current balance / payment history]. Under Metro 2 formatting standards, the Account Status Code must accurately reflect the current state of the account and must be internally consistent with all other status fields. This inconsistency constitutes inaccurate reporting under FCRA §623(a)(1). Please correct to [correct code] or delete."

06
Payment rating inconsistent with account status
Base Segment — Payment Rating field
Medium impactCorrection / deletion
►
What it is
The Payment Rating is a single-character field summarizing the current payment status. It must be consistent with the Account Status Code and the Payment History Profile. Codes: 0=current, 1=30 days, 2=60 days, 3=90 days, 4=120 days, 5=150 days, 6=180+ days, G=collection/charge-off, E=$0 balance.
The violation
Payment Rating of "0" (current) while Account Status Code shows past-due. Payment Rating of "G" (collection) while Account Status shows "11" (current). Payment Rating of "E" ($0 balance) while Current Balance shows a non-zero amount. Any combination where these three fields don't logically agree.
Dispute language template

"The Payment Rating field for Account #[XXXX] shows [value] while the Account Status Code shows [value] — these fields are logically inconsistent under Metro 2 standards. Payment Rating must be directly consistent with Account Status Code and Current Balance per Metro 2 field definitions. This internal data inconsistency is a Metro 2 compliance violation and renders the reporting inaccurate under FCRA §623."

07
Balance inflating after charge-off date
Base Segment — Current Balance / Charge-Off Amount fields
Medium impactViolation + re-aging
►
What it is
Once an account is charged off, Metro 2 requires the balance to reflect the charged-off amount. The balance should not increase after the charge-off date unless the creditor can document specific fees or interest that are legally allowed to accrue post-charge-off under the original agreement.
The violation
Creditor continues adding fees or interest after the charge-off date, causing the reported balance to increase month over month. Current Balance exceeds the Charged-Off Amount field. The "Amount Past Due" field continues to update with new amounts after the account is in charge-off status.
Dispute language template

"Account #[XXXX] was charged off on [date] with a reported charge-off balance of $[amount]. However, subsequent monthly reports show a Current Balance of $[higher amount] — an increase of $[difference] after the charge-off date. Metro 2 compliance requires that balances on charged-off accounts reflect the actual charged-off amount. Post-charge-off balance inflation without documented contractual basis constitutes inaccurate reporting under FCRA §623(a)(1)."

08
Date opened changed when debt was sold
Base Segment — Date Opened field
Medium impactProcedural violation
►
The violation
When a debt buyer acquires an account, they sometimes populate the "Date Opened" field with the date they purchased the debt rather than the original account opening date. This is a Metro 2 violation — the Date Opened must always reflect when the original account was opened with the original creditor.
Why it matters
Changing the Date Opened can make an old delinquency appear to be a newer account, potentially extending its impact. It also makes the account's 7-year removal date harder to calculate correctly.
Dispute language template

"The Date Opened field for Collection Account #[XXXX] with [Collector Name] reflects [date] — which appears to be the date this agency acquired the debt, not the date the original account was opened. Metro 2 requires Date Opened to reflect the original account opening date. I request verification of the original account opening date with [Original Creditor] and correction or deletion if the current date cannot be verified against original creditor records."

09
Missing compliance condition code XB during active dispute
Base Segment — Compliance Condition Code field
Medium impactProcedural violation
►
What it is
Metro 2 requires furnishers to add the Compliance Condition Code "XB" to an account's record when a consumer has filed a dispute and the investigation is in progress. This code notifies the bureaus and any reviewing lender that the accuracy of the account is under investigation.
The violation
After a consumer files a dispute, the furnisher continues to report the account without the XB code. Lenders who pull the consumer's report during this period see the disputed account without the "under dispute" flag — they may make lending decisions based on unverified data.
Dispute language template

"I filed a dispute regarding Account #[XXXX] on [date]. Despite an active investigation being in progress, [Furnisher] has continued to report this account without the Compliance Condition Code 'XB' required by Metro 2 standards to indicate a disputed account under investigation. Failure to apply this code during an active dispute violates Metro 2 compliance standards and FCRA §623(b)(1)(D), which requires furnishers to note an account as disputed during the investigation period."

10
Consumer identifying information mismatch
Base Segment — Name, SSN, DOB, Address fields
Medium impactIdentity / accuracy
►
The violation
Metro 2 requires that the consumer identifying information reported with each account matches the consumer's actual records: full legal name, SSN (full or partial), date of birth, and address. Any mismatch creates a question about whether the account actually belongs to the consumer — and makes "reasonable investigation" by the bureau more complex.
What to look for
Wrong middle name or initial. Name misspelling that differs from how other accounts report. SSN with a different digit. DOB off by a year or day. Address that is not and never was associated with you. These mismatches are common on collection accounts where the collector received incomplete data from the original creditor.
Dispute language template

"Account #[XXXX] reports consumer identifying information that does not match my verified personal information. Specifically, [describe mismatch: name/SSN/DOB/address]. Metro 2 requires that all identifying data fields match the consumer's actual records. This discrepancy raises questions about whether this account has been correctly attributed to me and renders the furnisher's reporting incomplete under FCRA §623(a)(1)(A)."

11
Wrong account type code for the product reported
Base Segment — Account Type field
Medium impactProcedural violation
►
Common account type codes
01=Revolving, 02=Open, 03=Installment, 07=Line of Credit, 12=Education loan, 18=Real estate mortgage, 19=Deed of trust, 26=Auto loan, 37=Student loans, 89=Medical. Each product type has a specific code — using the wrong one misrepresents the nature of the debt.
The violation
Student loan coded as revolving (01) instead of student loan type. Medical debt coded as auto loan. Collection account using an original creditor account type. Store card coded as mortgage. These errors misrepresent the type of obligation and affect how it's scored.
Dispute language template

"Account #[XXXX] is reported with Account Type Code [XX], which corresponds to [account type]. This account is actually a [actual account type], which under Metro 2 standards should be reported with Account Type Code [correct code]. Incorrect account type classification is a Metro 2 formatting violation that results in inaccurate representation of this obligation."

12
Scheduled monthly payment showing $0 on active installment account
Base Segment — Scheduled Monthly Payment Amount field
Lower impactAccuracy violation
►
The violation
Metro 2 requires the Scheduled Monthly Payment Amount to reflect the contractual payment amount for installment accounts. Reporting $0 or leaving this field blank for an active auto loan, personal loan, or mortgage suggests either that no payment is contractually required (which would be inaccurate) or that the data was not properly mapped from the creditor's system.
Why it matters
Lenders reviewing the full credit file (not just the score) use this field to calculate debt-to-income ratios. A $0 scheduled payment misrepresents the true monthly obligation and can cause issues in manual underwriting reviews.
Dispute language template

"Account #[XXXX] is an active [loan type] with a contractual monthly payment of approximately $[amount], yet the Scheduled Monthly Payment Amount field is reported as $0. Metro 2 requires this field to contain the actual contractual payment amount for installment accounts. A $0 reporting for an active installment account is factually inaccurate under Metro 2 standards."

13
Date of last activity / last payment inconsistency
Base Segment — Date of Last Payment field
Lower impactDate accuracy
►
The violation
Metro 2 tracks the Date of Last Payment separately from the Date of Last Activity. Some furnishers confuse these or leave them blank. The Date of Last Payment must reflect the actual last payment received — not the date the account was transferred, charged off, or sold.
Cross-reference opportunity
If the Date of Last Payment shown on your credit report is after the reported DOFD, this is an internal inconsistency. You cannot have made an on-time payment after the date of first delinquency — the account was already delinquent. This contradiction makes both dates unverifiable.
Dispute language template

"Account #[XXXX] reports a Date of Last Payment of [date], which is [before / after / inconsistent with] the reported Date of First Delinquency of [date] and/or the payment history profile. Metro 2 requires Date of Last Payment to accurately reflect the most recent payment received. This inconsistency indicates inaccurate reporting under FCRA §623."

14
ECOA code — incorrect designation of account responsibility
Base Segment — ECOA Code field
Lower impactDesignation error
►
What it is
ECOA (Equal Credit Opportunity Act) codes indicate your relationship to the account. Codes: 1=individual, 2=joint (contractual), 3=authorized user (AU), 4=joint (undesignated), 5=co-maker/guarantor, 7=maker, T=terminated/deceased, X=deceased.
The violation
Reporting you as the primary account holder (code 1) when you were only an authorized user (code 3). Reporting a joint account (code 2) without a joint holder present. Reporting an AU account with code 1 — this makes you appear fully responsible for a debt you may have no legal obligation to pay.
Dispute language template

"Account #[XXXX] is reported with ECOA Code [current code], indicating I am the [designation]. However, my relationship to this account is [actual relationship]. The ECOA Code should read [correct code] per Metro 2 definitions. Incorrect ECOA designation misrepresents my legal responsibility for this obligation and violates Metro 2 accuracy standards."

15
Portfolio type code — wrong designation for collection account
Base Segment — Portfolio Type field
Lower impactClassification error
►
What it is
Portfolio Type identifies the account as: C=credit card/revolving, I=installment, M=mortgage, O=open (paid monthly in full), R=revolving. This field must match the actual account type and the Account Type Code — they are redundant fields that must agree.
The violation
A collection account (which is technically an open account) reported with Portfolio Type "R" (revolving) or "I" (installment) — these belong only to the original creditor's account type. Collection agencies have a limited set of valid Portfolio Type codes. Using an incorrect code is a Metro 2 violation.
Dispute language template

"Account #[XXXX] with [furnisher name] reports Portfolio Type Code [current code], which corresponds to a [type] account. However, this is a collection account which under Metro 2 standards requires Portfolio Type [correct code]. This misclassification constitutes a Metro 2 formatting violation and results in inaccurate reporting."

16
Charge-off amount missing when status is charge-off
Base Segment — Amount of Original Charge-Off field
High impactRequired field missing
►
The violation
When Account Status Code is 97 (charge-off), Metro 2 requires the Amount of Original Charge-Off field to be populated with the balance at the time of charge-off. If this field is blank or shows $0 while the account is in charge-off status, it is a required-field violation — the record is incomplete under Metro 2 standards.
Compound violation
When the Charge-Off Amount is blank but the Current Balance shows an amount, it's also impossible to verify whether the current balance is accurate relative to the original charge-off amount. Both fields together define the debt — missing one makes the other unverifiable.
Dispute language template

"Account #[XXXX] reports an Account Status Code of 97 (charge-off), yet the Amount of Original Charge-Off field is blank/zero. Metro 2 compliance requires the original charge-off amount to be reported whenever an account carries charge-off status. This missing required field makes the reported balance unverifiable and constitutes an incomplete Metro 2 record under FCRA §623(a)(1)."

17
Reporting beyond the 7-year statutory limit
FCRA §605 | Based on DOFD
High impactFCRA §605 violation
►
The violation
Under FCRA §605(a), most negative items may only be reported for 7 years from the DOFD. If the DOFD was, for example, March 2017, the item must be removed by March 2024. If it is still appearing after that date, it is being reported in violation of the statutory limit — regardless of whether the Metro 2 data itself is otherwise accurate.
How this connects to Metro 2
If the DOFD in the Metro 2 record is wrong (too recent), the 7-year clock appears to not have expired yet — even though the real DOFD was earlier. This is why DOFD accuracy is the most critical Metro 2 field. A re-aged DOFD doesn't just violate Metro 2 — it directly enables continued illegal reporting past the statutory limit.
Dispute language template

"Account #[XXXX] has a Date of First Delinquency of [date], making the statutory 7-year reporting period expire on [7 years + date]. This account continues to be reported as of [current date] — [X months] past its legal removal date under FCRA §605(a)(4). I demand immediate deletion of this item from my credit file at all three credit bureaus."

18
Original creditor name missing from collection account
K1 / K3 Segment — Original Creditor Name field
Medium impactRequired field missing
►
The violation
Metro 2 requires collection accounts to identify the original creditor — either in the K3 Segment or through the Original Creditor Name field. This allows consumers (and bureaus) to identify the debt, verify its origin, and check for duplicate reporting. A collection account showing "unknown" or leaving this field blank is non-compliant.
Why it matters for disputes
Without the original creditor identified, it is impossible for the consumer to verify the debt's origin, impossible for the bureau to cross-reference against the original creditor's account (if still reporting), and impossible to confirm whether the statute of limitations has expired. Missing required identification data = incomplete record.
Dispute language template

"Collection Account #[XXXX] with [Collector Name] does not identify the original creditor in the required K3 Segment or Original Creditor Name field — this field shows [blank / UNKNOWN]. Metro 2 compliance requires collection accounts to identify the original creditor. Without this required information, I cannot verify the debt's origin or confirm it belongs to me. This incomplete Metro 2 record violates FCRA §623(a)(1) accuracy and completeness standards."

19
Special comment code inconsistency
Base Segment — Special Comment field
Lower impactSupplemental violation
►
What it is
Special Comment codes provide additional context about an account's situation. Common codes: AC=paying under partial agreement, AI=account closed at consumer's request, AH=purchased by another company, AP=account payment arrangements, AU=account closed at grantor's request, BO=account involved in bankruptcy.
The violation
Special Comment code "BO" (bankruptcy) on an account not included in any bankruptcy filing. Code "AI" (closed at consumer's request) when the consumer never requested closure. Code "AH" (purchased by another company) when no sale occurred. Any Special Comment code that doesn't match the actual account circumstances is a Metro 2 accuracy violation.
Dispute language template

"Account #[XXXX] carries Special Comment Code [code], which denotes [meaning]. This designation is inaccurate because [reason — e.g., this account was not included in any bankruptcy / I did not close this account / this debt was not sold]. Inaccurate Special Comment codes misrepresent the account's history and circumstances under Metro 2 field standards."

20
Cross-bureau inconsistency — same account, different Metro 2 data
All Segments | Cross-bureau comparison
High impactMulti-bureau attack
►
What it is
The same account is reported to all three bureaus from the same data file. If the data is accurate, it should be identical at all three bureaus. When it's not — different balances, different DOFDs, different status codes, different payment history profiles — at least one bureau is receiving inaccurate Metro 2 data.
The violation
Same account showing balance of $2,400 at Equifax, $1,890 at TransUnion, and $2,650 at Experian. Same account showing DOFD of March 2021 at Equifax but August 2022 at TransUnion. Status showing "collection" at two bureaus but "charge-off" at the third. Any material difference between bureaus for the same account and same time period.
Why this is powerful
Under FCRA, all reporting must be accurate. If the same account has different data at different bureaus, the data cannot be accurate at all three simultaneously. Disputing the inconsistency at all three bureaus forces each one to verify against the others — and forces the furnisher to explain the discrepancy, which they often cannot do within 30 days.
Dispute language template

"Account #[XXXX] with [Furnisher] is reporting the following information at [Bureau A]: [data]. However, the same account at [Bureau B] reports: [different data]. Under Metro 2 standards, all bureaus receive the same data file — material discrepancies between bureaus indicate that at least one bureau is receiving inaccurate information. Per FCRA §623(a)(1), furnishers must report complete and accurate information. I am filing simultaneous disputes at [Bureau A] and [Bureau B] and request deletion at both pending resolution of this inconsistency."

Top 5 deletion winners
If you only use 5 Metro 2 attack points — use these. Highest deletion rate, most widely applicable.
#1
DOFD missing or inconsistent with payment history
Attack Point 01 — Segment J2
Highest deletion rate

DOFD is the most important and most commonly violated field in credit reporting. Many furnishers — especially smaller collection agencies and debt buyers — do not correctly populate this field or maintain consistency between it and the payment history profile. A missing DOFD makes the entire account's 7-year window unverifiable. When a furnisher cannot prove the DOFD within 30 days, deletion follows.

Best used on

Collection accounts, charged-off accounts, any account where the DOFD appears to conflict with the payment history months or is suspiciously recent compared to the last on-time payment date.

#2
Re-aging — DOFD updated by debt buyer
Attack Point 04 — FCRA §605(c)
FCRA + Metro 2 violation

Re-aging hits two legal standards simultaneously — it's both a Metro 2 compliance violation AND a direct FCRA §605(c) violation. The combination creates a two-front attack that is extremely difficult for furnishers to defend. When you can show that the debt buyer's reported DOFD is later than the original creditor's DOFD (or your own payment records), you have strong grounds for immediate deletion.

Best used on

Collection accounts, especially those owned by third-party debt buyers who purchased the account years after the original default.

#3
Original creditor still reporting balance after debt sale
Attack Point 03 — Duplicate reporting
Double entry attack

This is the most clearly identifiable Metro 2 violation — you can see it just by looking at your credit report. If the original creditor and a collection agency are both showing a balance for the same underlying debt, that's a violation you can dispute immediately at all three bureaus simultaneously. The original creditor entry is almost always the one that gets removed.

Best used on

Any account where both the original creditor and a collection agency appear on your report for the same debt — extremely common, and very disputable.

#4
Payment history profile inconsistency
Attack Point 02 — Base Segment field 17B
Technical data conflict

The payment history grid is a 24-month string of codes that must be internally consistent with the account status, DOFD, and payment rating. Finding a single month in that string that contradicts another field — like a "current" payment code in a month that should be delinquent based on the DOFD — creates a technical data conflict that is almost impossible to "verify" through e-OSCAR automation.

Best used on

Accounts where you can carefully compare the payment history months against the reported DOFD. If month 14 shows "current" but the DOFD was 16 months ago, that's an internal conflict.

#5
Cross-bureau data inconsistency
Attack Point 20 — Multi-bureau comparison
Simultaneous 3-bureau attack

Comparing the same account across all three bureaus takes 10 minutes and can reveal significant discrepancies that create powerful simultaneous disputes. When the same furnisher reports different balances, different DOFDs, or different statuses to different bureaus, at least one bureau has inaccurate data by definition. Filing simultaneous disputes at all three creates a workload the furnisher often cannot complete within the 30-day window.

Best used on

Any account, especially after pulling all three reports. Start here — compare the same negative account side by side across bureaus before building your dispute strategy.

Dispute language templates
Ready-to-use Metro 2 dispute language. Combine with specific account details before sending.
How to structure a Metro 2 dispute letter
1
Opening: identify the specific account
Account name, last 4 of account number, furnisher name, and the bureau you're disputing with. Never dispute multiple accounts in the same letter.
2
Cite the specific Metro 2 field(s) at issue
Name the specific segment and field (e.g., "Date of First Delinquency in Segment J2"). This demonstrates you know the technical standard and forces a field-level review.
3
State the specific violation
Describe exactly what is wrong — don't just say "this is inaccurate." Say "the DOFD field shows [X] which contradicts the payment history profile showing on-time payments in [month]."
4
Cite the legal standard
Reference FCRA §623(a)(1) for furnisher accuracy obligations, §611 for bureau investigation requirements, and §605 for reporting period violations where applicable.
5
State your demand clearly
"I demand deletion of this account" OR "I demand correction of [specific field] to [correct value] with documented verification." Be specific about what you want.
6
Send certified mail, return receipt requested
Creates a documented paper trail. The 30-day investigation clock starts when the bureau receives your dispute. Certified mail proves receipt date.
The Metro 2 dispute opener — use this on every letter
Standard Metro 2 opening paragraph

"I am writing to dispute information appearing on my credit report pursuant to my rights under the Fair Credit Reporting Act (FCRA). This dispute is based on Metro 2 compliance violations — specifically, one or more data fields in the credit reporting record for the account identified below do not comply with the Metro 2 Credit Reporting Resource Guide published by the Consumer Data Industry Association (CDIA), which establishes the technical standards all furnishers must follow when submitting data to consumer reporting agencies. Under FCRA §623(a)(1), furnishers are required to report complete and accurate information. Non-compliant Metro 2 data is, by definition, neither complete nor accurate."

After the "verified as accurate" response — the escalation letter
Method of Verification demand (send after "verified" response)

"On [dispute date], I submitted a Metro 2 compliance dispute regarding Account #[XXXX]. Your response dated [date] states the account has been 'verified as accurate.' Under FCRA §611(a)(7), I hereby formally request the Method of Verification used to investigate my dispute. Specifically, please provide: (1) the name, address, and telephone number of any person contacted during the investigation; (2) all documentation reviewed during the investigation; (3) confirmation of whether the specific Metro 2 data fields identified in my dispute were individually reviewed for compliance with CDIA Metro 2 format standards. An automated e-OSCAR match confirming account ownership does not constitute a 'reasonable investigation' of Metro 2 field-level compliance disputes under FCRA §611(a)(1). If the investigation consisted solely of automated verification without field-level Metro 2 compliance review, I will be filing a complaint with the Consumer Financial Protection Bureau."

Metro 2 quick-reference cheat sheet
Print this page. Use it every time you audit a credit report.
The 5-minute Metro 2 audit — run this on every negative account
CheckWhat to look forAttack point if wrong
Is DOFD present?Field should show a date for any delinquent account#01 — Missing DOFD
Does DOFD match payment history?No "current" payments after DOFD date#02 — History inconsistency
Is DOFD same at all 3 bureaus?Pull all 3 — dates must match#20 — Cross-bureau inconsistency
Is original creditor AND collector both showing?Both should not have non-zero balances#03 — Duplicate reporting
Has the DOFD moved since the debt was sold?Compare collector's DOFD to original creditor records#04 — Re-aging
Does status code match payment rating?Status 11 (current) + Rating 1 (late) = impossible#05/#06 — Code inconsistency
Is balance increasing post-charge-off?Charge-off balance should be static or reducing#07 — Post-CO balance inflation
Is it past the 7-year window?DOFD + 7 years = required removal date#17 — Reporting beyond statutory limit
Is identifying info correct?Name, address, DOB vs. your records#10 — Identifying info mismatch
Is original creditor identified on collections?Should not show "unknown"#18 — Missing original creditor
Key Metro 2 status codes
CodeMeaning
11Current — paid as agreed
13Paid / closed
62Paid collection
64Collection / charge-off
7130 days past due
7860 days past due
8090 days past due
82120 days past due
97Charge-off
Key compliance condition codes
CodeMeaning
XBDisputed — under investigation
XHAccount in bankruptcy
XRRe-investigated — no change
XCCompleted investigation, info deleted
XDReinsertion after deletion
XFPositive data — account closed
Critical rules — never forget these
The 30-day window rule

Bureaus have 30 days to complete a reasonable investigation (45 if you submit additional info). If they cannot verify Metro 2 field-level compliance in that window — the item must be deleted. This is your enforcement mechanism.

One account per dispute letter

Always dispute accounts one at a time, in separate letters. Disputing multiple items in one letter can be classified as "frivolous" by bureaus. Separate letters = separate 30-day windows = more leverage.

Dispute with furnisher AND bureau

File simultaneously with the bureau (FCRA §611) and the furnisher directly (FCRA §623). This creates two independent 30-day windows and two separate obligations to respond. Double the pressure.

CFPB is your nuclear option

After a failed Metro 2 dispute, file a CFPB complaint citing the specific field violations. Bureaus must respond within 15 days of a CFPB complaint. CFPB complaint data is public — bureaus don't want patterns.

Created & Curated By
Dunia Merci
Credit Strategist · Funding Architect · Educator

Follow along for daily credit strategy, dispute walkthroughs, funding tactics, and behind-the-scenes wins from students putting this guide into practice.

📣 Tag Dunia With Your Wins
Used this guide to delete a tradeline, win a dispute, or rebuild your score? Share your win on any platform above and tag @duniamerci — featured wins regularly make it into Shorts and Reels.