The Complete Metro 2 Field Reference: How Credit Reporting Errors Are Engineered

If the Fair Credit Reporting Act is the law, Metro 2 is the operating manual. Every furnisher signed it. Almost none of them follow it exactly. The gap between what they agreed to report and what they actually report is where every forensic dispute lives.

This is the technical reference Pinnacle Credit Management uses on dossier work. It is the document we wish had existed when we were learning, because the existing public material on Metro 2 either reproduces marketing copy from credit-repair sellers or buries the technical specifications behind a $1,200 CDIA license fee. What follows is field by field, code by code, and includes the contradictions that show up on more than half of consumer files we audit.

What Metro 2 actually is

Metro 2 is a fixed-format data reporting protocol developed by the Consumer Data Industry Association (CDIA), the trade group representing the major credit reporting agencies. The current specification is published in the CDIA Credit Reporting Resource Guide, updated annually. Every furnisher (banks, credit card issuers, auto lenders, mortgage servicers, student loan servicers, collection agencies, debt buyers) signs a Subscriber Agreement that contractually obligates them to report data in Metro 2 format.

The protocol replaced the older Metro 1 format in the late 1990s. Where Metro 1 used a variable-length character format, Metro 2 uses fixed-length records of 426 bytes each, organized into a header record (one per file), one or more base segments (one per consumer account), and optional appended segments (K-segments) carrying additional data. Each field has a defined position, a defined length, a defined data type, and in the case of coded fields, a defined set of permissible values.

The point is precision. Metro 2 is engineered so that no two valid combinations of fields can simultaneously be true. When a furnisher reports a combination the protocol does not allow, that is, by definition, a reporting violation. The dispute then ceases to be a subjective argument about what happened and becomes a technical argument about whether the data is structurally valid.

The CDIA, the bureaus, and what compliance means

A common misconception is that the three credit bureaus enforce Metro 2 unilaterally. They do not. The CDIA writes the protocol; the bureaus require it; and the furnisher contractually agrees to it via the Subscriber Agreement. The Fair Credit Reporting Act, 15 U.S.C. §1681 and following, then imposes additional federal duties on furnishers under §623(a) to report accurate, complete, and integrable information.

This creates three overlapping compliance regimes that every furnisher operates inside:

• Contractual Metro 2 compliance: Required by the Subscriber Agreement with each bureau. Violation can result in suspension of reporting privileges.
• FCRA §623 accuracy duty: Federal statutory duty to report accurate and complete information. Violation triggers private rights of action with statutory damages.
• FCRA §623(a)(8) reinvestigation duty: When a furnisher receives a direct consumer dispute, it must conduct a reasonable investigation and respond within 30 days. Violation also triggers private rights of action.

A Metro 2 violation is, in practical terms, prima facie evidence of an FCRA accuracy violation. When you cite Metro 2 in a dispute, you are demonstrating that the furnisher has reported data in a form the protocol does not allow, which is a form the FCRA does not permit either. The bureau cannot reasonably investigate a structurally invalid report and conclude it is accurate.

The header record: who is reporting and when

Every Metro 2 file begins with a single header record identifying the furnisher and the reporting period. The fields most relevant to disputes are:

The header is rarely the dispute target, but it sets context for everything that follows. When the Reporter Name and the consumer-facing brand do not match, this is the field that resolves the question.

The base segment: the core tradeline record

Every consumer account becomes a base segment. Each base segment is 426 bytes containing 50 defined fields. Of these, the dispute-relevant fields cluster around the status of the account, the timing of events, and the consumer's identifying information.

The five fields that produce the majority of Metro 2 violations on consumer files are Account Status, Payment Rating, Payment History Profile, Special Comment Code, and Date of First Delinquency. Each is documented in detail below.

Account Status codes: the heart of the violation surface

The Account Status field is a two-digit code describing the current state of the account. The CDIA defines a fixed set of valid values. The most common codes consumers encounter are listed below. Memorize these. They are the codes you will see on your file and the codes you will cite in disputes.

The forensic interest in Account Status codes is not the codes themselves but their combinations with other fields. Code 13 with a non-zero balance is a violation. Code 11 with a 30-day delinquency in the Payment History Profile is a violation. Code 97 (charge-off) reported month over month with an increasing balance is a violation, because by definition a charged-off account is no longer accruing interest in the way an open account does.

Payment Rating codes: the current cycle

Where Account Status describes the account's overall posture, Payment Rating describes the current reporting cycle's payment performance. The valid codes are short.

Payment Rating must be internally consistent with the Account Status field. A Payment Rating of 0 (current) cannot lawfully coexist with an Account Status of 97 (charge-off). A Payment Rating of L (charge-off) cannot lawfully coexist with an Account Status of 11 (current). When these contradictions appear, and they appear often on debt-buyer files after assignment, the tradeline is structurally noncompliant.

Payment History Profile: the 24-month grid

The Payment History Profile is a 24-character field where each character represents one month of payment history, going back two years from the Activity Date. Each character is a single-digit code describing that month's performance.

The Payment History Profile is one of the richest violation surfaces on a typical file. Common problems include: payment history strings showing "0" (current) for months the consumer was demonstrably delinquent; strings showing "1" or "2" for months when the consumer can prove the payment was made on time; gaps shown as "B" when the furnisher actually had data; and worst of all, strings showing payment activity for months after the account was charged-off and sold, which is structurally impossible.

Special Comment codes: the under-cited violation surface

Special Comment is a two-character field that adds descriptive context to the Account Status. The valid codes number in the dozens. The most common are:

The Special Comment Code creates contradictions when paired carelessly with the Account Status. AN (closed at consumer's request) on an account reporting Account Status 97 (active charge-off) is a violation: the account cannot simultaneously be closed by the consumer and reporting an active charge-off, because charge-off is a credit grantor decision. AU (settled for less than the full balance) on an account reporting a non-zero balance is a violation: a settled account has been satisfied per the settlement terms, and any remaining balance is forgiven debt that should not continue reporting as outstanding.

Date of First Delinquency: the most violated field on the protocol

The Date of First Delinquency (DOFD) is the single most consequential field in Metro 2 because it controls the seven-year reporting window under FCRA §605(c). The DOFD is, by statute and protocol, the date of the first delinquency that immediately preceded the account's transition to charge-off or collection status, without any subsequent cure.

This definition is precise on purpose. The DOFD does not advance when an account is transferred. It does not advance when a debt is sold. It does not advance when payments are made on a delinquent balance. It does not advance when the consumer enters a settlement agreement. The DOFD is anchored to the historical event of first non-cured delinquency, and once set, it determines exactly when the account must drop off all three reports.

Re-aging of the DOFD is the most aggressive and most common Metro 2 violation. It typically appears when a debt buyer purchases a charge-off, opens a new tradeline under their own name, and reports a DOFD corresponding to when the consumer first defaulted with the buyer (i.e., never, because the consumer never had a contract with the buyer). The lawful DOFD is the original creditor's DOFD. The unlawful DOFD is anything that extends the reporting window past the seven-year statutory limit.

Account Type and Portfolio Type: scoring downstream effects

Account Type and Portfolio Type are two-character codes describing the nature of the underlying credit relationship. Incorrect coding here distorts every credit score downstream because scoring algorithms weight installment debt, revolving debt, mortgage debt, and collection debt differently.

Inconsistencies between Account Type and Portfolio Type are common and rarely caught. A credit card account (Account Type 08) must have Portfolio Type R (revolving). When a credit card account is reported with Portfolio Type I (installment), the scoring downstream is wrong, and the field is structurally invalid.

Mutually exclusive field combinations: the violation matrix

The most efficient way to audit a tradeline for Metro 2 violations is to check it against the matrix of mutually exclusive combinations. Each row below describes a combination of fields that, by protocol, cannot coexist on the same tradeline in the same reporting cycle.

Any tradeline that satisfies a row of this matrix is structurally noncompliant. The forensic dispute names the specific row, cites the Metro 2 fields involved, and demands either correction to a lawful combination or deletion of the tradeline. Furnishers cannot reasonably defend a structurally impossible combination, which is why these disputes succeed where generic complaints fail.

The K-segments: appended data that often contradicts the base

Beyond the base segment, Metro 2 allows furnishers to append additional segments carrying supplementary data. The most important are:

• K1 Segment - Original Creditor Name: Required on collection accounts. Identifies who originated the debt before assignment to the current collector. Missing K1 segments on collection tradelines are a per se compliance violation.
• K2 Segment - Purchased Portfolio: Used when a debt is purchased. Identifies the prior owner. Required for chain-of-title transparency.
• K3 Segment - Mortgage Information: Mortgage-specific data including original loan amount, interest rate, and term.
• K4 Segment - Specialized Payment Information: Used for accounts with non-standard payment terms (deferred student loans, income-driven repayment, etc.).
• L1 Segment - Consumer Account Number Change: Tracks when an account number changes (typically after a balance transfer or account migration).
• N1 Segment - Employment: Optional employment data.

K-segments matter for disputes because they create additional fields that must be internally consistent with the base segment. A collection tradeline with a K1 segment naming "Original Creditor X" but a base segment Account Type that does not match the original creditor's business is contradictory. A K2 segment chain that has gaps in the ownership history is a chain-of-title defect that often makes the entire tradeline unverifiable.

How to cite Metro 2 in a dispute letter

The technical strength of a Metro 2 citation depends on specificity. A dispute that says "this account violates Metro 2" is barely better than a generic dispute. A dispute that names the field, the code value, the contradiction, and the protocol section is something the bureau cannot dismiss without examining the file. The format below is the structure Pinnacle uses on dossier work.

1. Identify the tradeline precisely Account name, partial account number as shown on the report, date of reporting being disputed. Leave no ambiguity about which item is at issue.
2. Name the specific Metro 2 field at issue For example: "the Account Status field is reporting Code 97, while the Payment Rating field is reporting Code 0."
3. State the protocol contradiction For example: "Under the CDIA Credit Reporting Resource Guide, Account Status Code 97 (charge-off) is mutually exclusive with Payment Rating Code 0 (current account, paid as agreed). The combination is structurally invalid."
4. Anchor to the FCRA For example: "The reporting of structurally invalid data fails the §623 accuracy and completeness duty. The reporting is therefore inaccurate as a matter of law, regardless of the underlying factual history."
5. Demand Method of Verification For example: "Under §611(a)(7), I request a description of the procedure used to verify this account, including the specific person contacted, the documents reviewed, and the basis on which a structurally invalid combination of fields was deemed accurate."
6. Demand correction or deletion For example: "I demand correction of the field combination to bring this tradeline into Metro 2 compliance, or deletion of the tradeline in its entirety. Failure to do either constitutes ongoing willful noncompliance under §616."

The bureau processor receiving this dispute has two options: examine the tradeline (which produces deletion, because the contradiction is real) or attempt to verify it (which produces a 30-day clock failure or a conclusory MOV response that becomes evidence in subsequent escalation). There is no third path. This is the mechanical reason Metro 2 disputes succeed.

Where Metro 2 compliance breaks down by furnisher type

Different categories of furnishers fail Metro 2 in different ways. Knowing the failure pattern helps target the audit.

Debt buyers and collection agencies

The highest failure rates. Common issues: missing K1 segments (no Original Creditor named), re-aged DOFDs, Account Type miscoding (often as a generic collection code that conflicts with the underlying debt type), and Payment History Profiles showing impossible payment activity post-assignment. Debt-buyer tradelines audit poorly because the data is often imported from prior owners with field-mapping errors.

Auto lenders

Common issues: deficiency balance reporting (the field continues showing the original loan balance instead of the deficiency after collateral sale), Voluntary Surrender (Payment History code J) reported as Repossession (code K) or vice versa, and Special Comment codes that conflict with the underlying transaction (e.g., AU when the account was actually repossessed rather than settled).

Student loan servicers

Common issues during the 2023 to 2024 reporting changes: continued reporting of forbearance-period delinquencies, incorrect Payment History during income-driven repayment, incorrect Special Comment codes for rehabilitated loans, and incorrect transfer reporting when servicing rights changed. The federal loan portfolio has been a Metro 2 disaster zone for two reporting cycles.

Mortgage servicers

Common issues: incorrect K3 segments, status confusion during loss-mitigation periods (modification under review, trial payment plan, completed modification), foreclosure timing errors, and incorrect DOFD propagation when the loan is transferred mid-delinquency.

Credit card issuers

Common issues: charge-off balance creep (the balance continues to grow month over month after charge-off, which is structurally invalid post charge-off), miscoded promotional balances (deferred-interest promotions reported as separate accounts), and Special Comment codes from prior account states that fail to clear.

Medical collection agencies

Following the 2022 to 2023 voluntary bureau changes, paid medical collections must be removed, unpaid medical collections under $500 may not be reported, and unpaid medical collections cannot be reported until at least 365 days after assignment. Many medical collection tradelines still in circulation violate one of these three rules. Although the rules are bureau policy rather than Metro 2 protocol, they intersect because reporting outside the policy is a per se reporting error subject to bureau correction.

Frequently asked questions