Metro 2 Segments Explained in Plain English
Every Metro 2® segment explained clearly: Header, Base, J1, J2, K1–K4, and Trailer records with real-world field examples and common errors to avoid. Updated 2026.
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.
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
Common Errors to Avoid
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
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
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
Common Errors to Avoid
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
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
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.
Common Errors to Avoid
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
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
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.
Get your reporting path
Tell us what you report, who you serve, and where you are in the process. We will route your inquiry to the most relevant Hutchins workflow discussion.
Get Your Reporting PathMore in Metro 2 Format
Choose the reporting, compliance, or API path that matches your current need.