What is Metro 2?
Metro 2® is the standardized credit reporting format developed and maintained by the Consumer Data Industry Association (CDIA). It defines how furnishers—banks, credit card companies, lenders, and other creditors—transmit consumer credit information to the three major credit reporting agencies: Equifax, Experian, and TransUnion.
Think of Metro 2 as the "language" of credit reporting. Just as HTML provides structure for web pages, Metro 2 provides structure for credit data. Every piece of information on a credit report—from account balances to payment history to account status—originates from Metro 2-formatted data files submitted by furnishers.
The current version, Metro 2® Format, replaced the older Metro 1 format and provides more detailed data fields, better handling of complex account types, and improved mechanisms for reporting disputes and special circumstances.
Why Metro 2 Matters in Litigation
Understanding Metro 2 is critical in FCRA cases because errors often occur at the data coding level—before information ever appears on a credit report. A furnisher might report incorrect account status codes, miscalculate payment history profiles, or fail to update critical fields. These technical errors can have devastating consequences for consumers.
Who Uses Metro 2?
Metro 2 is used by virtually all entities that report consumer credit information to the major credit bureaus. This includes:
Primary Furnishers
- Banks and Credit Unions: Reporting checking accounts (when negative), savings accounts, and lines of credit
- Credit Card Issuers: Reporting revolving credit accounts, balances, payment history, and credit limits
- Mortgage Servicers: Reporting first mortgages, second mortgages, home equity lines of credit (HELOCs)
- Auto Lenders: Reporting auto loans, lease agreements, and payment performance
- Student Loan Servicers: Reporting federal and private student loans
- Personal Loan Companies: Reporting installment loans and personal lines of credit
Secondary Furnishers
- Collection Agencies: Reporting collection accounts after charge-off or placement
- Utility Companies: Sometimes reporting utility accounts (typically only when delinquent)
- Telecommunications Providers: Reporting cell phone and internet service accounts
- Medical Billing Companies: Reporting medical debt (subject to special rules)
Each of these entities must format their data according to Metro 2 specifications. When they fail to do so correctly—or when they report inaccurate information in the correct format—FCRA violations can occur.
Structure of Metro 2 Reporting
Metro 2 files are structured as fixed-length records transmitted electronically to credit bureaus. Each file contains multiple segments that provide different types of information about consumer accounts.
Base Segment
The Base Segment is the core of every Metro 2 record. It contains fundamental account information including:
- Consumer identification (name, address, Social Security number)
- Account identification and type
- Account status (open, closed, paid, etc.)
- Balance and payment information
- Payment history profile (24-month grid)
- Date of first delinquency (DOFD)
- Account open date and last activity date
J1 Segment (Optional)
The J1 Segment provides additional account details including:
- Specialized payment information
- Original creditor information (for collection accounts)
- Agency identifier
- Original charge-off amount
J2 Segment (Optional)
The J2 Segment handles multiple scenarios including:
- Multiple surnames or addresses
- Generation codes (Jr., Sr., III)
- Additional consumer identification
Technical Note
Metro 2 uses fixed-length fields, meaning each piece of data occupies a specific position in the file. For example, the account status code might always appear at positions 20-21. This structure allows for efficient processing but also means that errors in field positioning or data formatting can cause significant problems.
Key Data Fields in Metro 2
Understanding the key data fields in Metro 2 is essential for identifying reporting errors and FCRA violations. Here are the most critical fields:
Account Status (Field 3)
Two-character code indicating the current status of the account (e.g., 11 = current, 13 = paid or closed, 64 = charge-off, 97 = unpaid balance reported as a loss). Misreporting this field can make accounts appear delinquent when they're current, or vice versa.
Payment History Profile (Field 8)
24-character field showing the last 24 months of payment performance. Each position represents one month, with codes like C (current), 1 (30 days late), 2 (60 days late), 3 (90 days late), etc. This field has enormous impact on credit scores.
Date of First Delinquency (Field 28)
The date the account first became delinquent and was never again current. Critical for determining how long negative information can remain on a credit report. Incorrect DOFD can result in "re-aging" violations.
Special Comment Code (Field 6)
Two-character code providing additional context about the account (e.g., AI = account information disputed by consumer, AU = authorized user, BK = bankruptcy). Failure to include appropriate codes can violate FCRA.
Compliance Condition Code (Field 7)
Two-character code indicating special circumstances affecting the account (e.g., XB = affected by natural disaster, AW = forbearance, AM = loan modification). Essential for properly reporting accounts during hardship periods.
Current Balance (Field 22)
The outstanding balance on the account. Must be accurate and updated regularly. Reporting stale or incorrect balances is a common FCRA violation.
Amount Past Due (Field 23)
The amount currently past due on the account. Must be zero if the account is current. Reporting a past-due amount when none exists can cause significant credit damage.
How Credit Bureaus Interpret Metro 2 Data
Credit reporting agencies receive Metro 2 files from furnishers and process them to create consumer credit reports. Understanding this interpretation process is critical for identifying where errors occur.
Automated Processing
CRAs use automated systems to:
- Match incoming Metro 2 records to existing consumer files (using name, address, SSN, date of birth)
- Create new tradelines or update existing ones
- Calculate credit scores based on the reported data
- Generate consumer credit reports for users with permissible purpose
Common Interpretation Issues
Several problems can arise during the interpretation process:
- Matching Errors: CRAs may incorrectly match data to the wrong consumer, creating mixed files
- Duplicate Accounts: The same account may appear multiple times if matching logic fails
- Stale Data: If a furnisher stops reporting updates, old information may remain on the report
- Code Translation: CRAs translate Metro 2 codes into consumer-facing language, sometimes inaccurately
Critical Point for Litigation
In FCRA disputes, it's essential to determine whether an error originated with the furnisher (incorrect Metro 2 data) or the CRA (incorrect processing of accurate data). This distinction affects liability and the appropriate legal claims.
Common Metro 2 Reporting Errors
Metro 2 reporting errors are a frequent source of FCRA violations. Here are the most common issues:
Incorrect Account Status Codes
Reporting an account as delinquent when it's current, or vice versa. This is one of the most damaging errors.
Payment History Profile Errors
Incorrectly coding late payments, failing to update the rolling 24-month history, or reporting late payments that never occurred.
Date of First Delinquency (DOFD) Errors
Reporting an incorrect DOFD, which can result in negative information remaining on a credit report longer than legally permitted.
Missing Special Comment Codes
Failing to include dispute indicators (AI code) or other required codes like bankruptcy (BK) or authorized user (AU).
Balance and Payment Reporting Errors
Reporting incorrect balances, past-due amounts, or payment amounts. These errors can make accounts appear worse than they are.
Failure to Update After Dispute Resolution
After a dispute is resolved in the consumer's favor, furnishers must update their Metro 2 reporting. Failure to do so is a common violation.
Duplicate Reporting
Reporting the same debt multiple times (e.g., by both the original creditor and a collection agency) without proper coding.