What Is a Metro 2 File?
A Metro 2 file is a structured text file that data furnishers — lenders, servicers, debt collectors, and others who extend credit — submit to the credit bureaus each month. It contains one Base Segment for each consumer account you are reporting. The file follows a strict format defined by the Consumer Data Industry Association (CDIA) in the Credit Reporting Resource Guide® (CRRG®).
The file is organized into segments — different types of records, each with a specific purpose. Every Metro 2 file must start with a Header Record, contain one Base Segment per account, and end with a Trailer Record. Additional segments (J1, J2, K1–K4) are added as needed for specific account types and associated consumers.
🔑 Important
File structure at a glance: Header → [Base + optional J1/J2/K-Segments] × number of accounts → Trailer. The Header identifies the reporter and reporting period. The Trailer contains the Base Segment count. J1 = associated consumer at same address. J2 = associated consumer at different address.
Header Record
Required — first record in every file
The Header Record is the first record in every Metro 2 file. It identifies who you are and what reporting period this file covers. The Header does not contain a count of accounts — that information belongs in the Trailer Record.
Think of the Header Record as the cover page of a report. It tells the bureau: "This file is from ABC Lending, covering January 2026." It does not tell the bureau how many accounts are inside — that is the Trailer's job.
Key Fields
Header Segment — Key Fields
Activity Date
The last day of the reporting period (e.g., 01312026 for January 31, 2026). Must be in MMDDYYYY format.
Date Created
The date you generated this file. Must match or be after the Activity Date.
Program Date
The date your Metro 2 software was last updated. Used by bureaus to verify you are running current software.
Program Revision Date
The revision date of your Metro 2 program. Must match the current CRRG® specification version.
Reporter Name
Your company's legal name as registered with the bureau. Must match exactly — even a comma difference can cause rejection.
Reporter Address
Your physical business address. Must match your data furnisher agreement.
Reporter Telephone Number
Your business phone number. Used by bureaus to contact you about file issues.
Software Vendor Name
The name of your Metro 2 software provider (e.g., Hutchins Systems, Inc.).
Software Version Number
The version of your Metro 2 software. Bureaus use this to verify CRRG® compliance.
Common Errors to Avoid
✕Activity Date in wrong format (YYYYMMDD instead of MMDDYYYY)
✕Reporter Name doesn't match the name on your data furnisher agreement
✕Missing or incorrect Program Identifier (your unique bureau ID)
✕Program Date is older than 12 months (indicates outdated software)
✕Assuming the Header contains an account count — it does not; account counts belong in the Trailer Record
Base Segment
Required — one per account
The Base Segment is the core record for each account you are reporting. Every consumer account gets exactly one Base Segment. This is where the actual credit data lives — account status, balance, payment history, and consumer identity.
The Base Segment is distinct from the J1 Segment: the Base Segment identifies the primary account holder, while J1 is a separate supplemental segment for an associated consumer at the same address.
If the Header is the cover page, the Base Segment is the individual account record card. One card per account. It contains everything the bureau needs to know about that specific account and the primary consumer who owns it.
Key Fields
Base Segment — Key Fields
Account Number
Your internal account identifier (up to 20 characters). Must be unique and consistent across all monthly submissions.
Portfolio Type
The type of credit: I = Installment, O = Open, R = Revolving, M = Mortgage.
Account Type
Two-digit code for the specific product (01 = Unsecured, 02 = Secured, 19 = Auto Loan, 47 = Rental Agreement).
Date Opened
The date the account was originated. Must be in MMDDYYYY format. Never changes after initial reporting.
Account Status
The current status of the account (11 = Current, 71 = 30–59 days past due, 78 = 60–89 days, 80 = 90–119 days, 82 = 120+ days, 97 = Charge-off, 13 = Paid/Closed).
Payment History Profile
A 24-character string representing the payment status for each of the last 24 months.
ECOA Code
The primary consumer's relationship to the account. Valid values: 1 = Individual, 2 = Joint Contractual, 5 = Co-maker/Co-signer, 7 = Maker, T = Terminated, X = Deceased, Z = Delete Consumer.
Social Security Number
The consumer's SSN (9 digits, no dashes). Critical for accurate credit file matching.
Date of Birth
MMDDYYYY format. Used for identity verification and fraud prevention.
Current Balance
The outstanding balance as of the Activity Date. For paid/closed accounts, report $0.
⚠️ Warning
Only the following ECOA codes are valid in the Base Segment: 1, 2, 5, 7, T, X, Z. ECOA code 3 (Authorized User) is NOT valid in the Base Segment — it is only valid in J1 and J2 segments.
Common Errors to Avoid
✕Account Status code doesn't match the Payment History Profile
✕Balance is non-zero on a fully paid account
✕SSN contains dashes or spaces
✕Date Opened changes between monthly submissions
✕Using ECOA Code 3 in the Base Segment (only valid in J1/J2)
✕Payment History Profile length is not exactly 24 characters
J1 Segment — Associated Consumer (Same Address)
Optional — associated consumer at same address
The J1 Segment is used to report an associated consumer who lives at the same address as the primary consumer on the account. It is a separate record from the Base Segment and follows the Base Segment it belongs to. Use J1 for joint account holders, co-signers, or authorized users who share the same address as the primary borrower.
If the primary borrower and their spouse both live at 123 Main Street and are both on the loan, the primary borrower gets the Base Segment and the spouse gets a J1 Segment — because they share the same address.
Key Fields
J1 Segment — Key Fields
Surname / First Name
The associated consumer's legal name.
Social Security Number
The associated consumer's SSN.
Date of Birth
The associated consumer's date of birth.
ECOA Code
Valid values for J1: 1, 2, 3, 5, 7, T, X, Z (note: code 3 = Authorized User is valid in J1 but not in the Base Segment).
Consumer Information Indicator
Used to flag special situations: A = Deceased, B = Active Military, C = Authorized User Dispute.
Common Errors to Avoid
✕Using J1 when the associated consumer lives at a different address — use J2 instead
✕Reporting a J1 Segment for an account with ECOA Code 1 (Individual) in the Base Segment
✕Using an invalid ECOA Code in J1 — only 1, 2, 3, 5, 7, T, X, Z are valid
✕Confusing J1 (same address) with J2 (different address)
J2 Segment — Associated Consumer (Different Address)
Optional — associated consumer at different address
The J2 Segment is used to report an associated consumer who lives at a different address from the primary consumer on the account. Like J1, it follows the Base Segment it belongs to. Use J2 when the co-borrower, co-signer, or authorized user has a different mailing address than the primary account holder.
If the primary borrower lives at 123 Main Street but their co-signer lives at 456 Oak Avenue, the co-signer gets a J2 Segment — because they live at a different address than the primary borrower.
Key Fields
J2 Segment — Key Fields
Surname / First Name
The associated consumer's legal name.
Social Security Number
The associated consumer's SSN.
Date of Birth
The associated consumer's date of birth.
Address
The associated consumer's address — which is different from the primary consumer's address in the Base Segment.
ECOA Code
Valid values for J2: 1, 2, 3, 5, 7, T, W, X, Z (note: W = Business/Commercial is valid in J2 but not in J1).
💡 Pro Tip
The key difference between J1 and J2 is the address. If the associated consumer shares the same address as the primary borrower → use J1. If they live at a different address → use J2. When in doubt, check the mailing address on the account application.
Common Errors to Avoid
✕Using J2 when the associated consumer lives at the same address as the primary — use J1 instead
✕Missing J2 Segment for a joint account where the co-borrower has a different address
✕Using ECOA Code W in J1 (W is only valid in J2)
✕Omitting the address fields in J2 (required since the address differs from the Base Segment)
K-Segments (Supplemental Data)
Situational — for specific account types
K-Segments provide additional account information that doesn't fit in the Base Segment. There are four K-Segments, each for a specific purpose. Not all accounts require K-Segments.
Think of K-Segments as attachments to a form. The main form (Base Segment) covers most situations, but some accounts need extra pages for specific details.
K1 — Original Creditor Name
The name of the original credit grantor, including any partnering affinity name and the creditor's classification. Used by: Collection agencies, debt buyers, check guarantee companies, student loan guaranty agencies, U.S. Department of Education, U.S. Treasury.
K2 — Purchased From / Sold To
The name of the company from which an account was purchased or the name of the company to which an account was sold. Used by: Any furnisher when a portfolio changes ownership.
K3 — Mortgage Information
The Fannie Mae or Freddie Mac loan number and/or the Mortgage Identification Number (MIN) assigned by MERS. Used by: Mortgage servicers and lenders.
K4 — Specialized Payment Information
Additional account information on deferred payments or balloon payments. Used by: Lenders with deferred payment or balloon payment structures.
Common Errors to Avoid
✕Omitting K1 Segment when reporting a collection account, debt buyer account, or student loan guaranty account
✕Using K2 to report the original creditor name — K2 is for purchased/sold portfolio tracking, not original creditor identity
✕Including K3 Segment on a non-mortgage account
✕Omitting K4 when reporting accounts with deferred payments or balloon payment structures
Trailer Record
Required — last record in every file
The Trailer Record is the last record in the Metro 2 file. It contains the total count of Base Segments being reported, so the bureau can verify the file was received completely and without corruption.
The Trailer Record is like the last page of a legal document that says "This document contains 340 accounts." If the bureau receives a file where the Trailer says 340 Base Segments but they only counted 339, they know something went wrong in transmission.
Key Fields
Trailer Record — Key Fields
Record Count (Total Base Records)
The total number of Base Segments being reported. Do NOT include the Header or Trailer records in this count. If you have 340 Base Segments, the Record Count must be exactly 340.
Block Count
The number of blocks on the file, if applicable. Only relevant when your bureau agreement requires block-level file organization. Only populate this field if your bureau agreement specifically requires it.
⚠️ Warning
A very common error: including the Header and Trailer records in the Total Base Records count. The Total Base Records field must contain only the count of Base Segments — not the Header, not the Trailer, and not any optional segments (J1, J2, K1–K4, etc.).
Common Errors to Avoid
✕Including the Header and/or Trailer in the Record Count — the Record Count contains Base Segments ONLY
✕Setting Record Count to the total number of all records in the file (including Header and Trailer)
✕Missing Trailer Record entirely (file appears truncated to the bureau)
✕Populating Block Count incorrectly — only use this field if your bureau agreement requires block-level organization
Aligned with the Current CRRG® Specification
This guide reflects the current edition of the Credit Reporting Resource Guide® (CRRG®) published by the Consumer Data Industry Association (CDIA). The CRRG® is updated periodically — Hutchins Systems monitors all updates and ensures our Metro 2 software (Credit Time 2000©, e-CreditTime, and MORFi) is always aligned with the latest specification. Our built-in compliance audit engine validates every field in every segment before your file reaches the bureau.