Metro 2 Format: The Complete Guide for Data Furnishers

What Is the Metro 2® Format?

The Metro 2® format is the industry-standard data specification used by all four national credit bureaus — Equifax, Experian, TransUnion, and Innovis — to receive consumer credit account information from data furnishers. It was developed and is maintained by the Consumer Data Industry Association (CDIA) and documented in the Credit Reporting Resource Guide (CRRG®).

Every organization that reports consumer account data to a credit bureau must submit that data in Metro 2® format. This includes banks, credit unions, auto lenders, mortgage companies, buy here pay here (BHPH) dealers, property managers, student loan servicers, and any other entity that extends credit or reports payment history.

File Format: Fixed-Length vs. Variable-Length

Metro 2® files can be submitted in two formats:

Fixed-Length Format — Each record in the file occupies a fixed number of bytes, regardless of content. Fields that are shorter than their allocated size are padded with spaces or zeros. This is the most common format and is accepted by all four bureaus.

Variable-Length Format — Record lengths can vary. Each record begins with a 4-byte field that contains the total byte count for that record. This format is used when the data contains optional segments (J1, J2, K1–K4, L1, N1) that vary from record to record.

In both formats, the first 4 bytes of every record contain the record length — the total number of bytes in that record, including those 4 bytes themselves. If this length does not match the actual byte count of the record, the bureau will reject the file.

The Structure of a Metro 2® File

Every valid Metro 2® file has exactly three required components, in this order:

1. One Header Record — The first record in the file. Identifies the data furnisher, the reporting period, and the file date.
2. One or more Base Segments — The main data records. Each Base Segment contains the account information for one consumer.
3. One Trailer Record — The last record in the file. Contains summary counts and totals.

Between the Header and Trailer, each line must be at least 426 bytes for the Base Segment. Optional associated consumer segments (J1, J2) and supplemental segments (K1–K4, L1, N1) follow immediately after the Base Segment they belong to, on the same logical record or as continuation records depending on your format.

The Header Record

The Header Record is always the first record in the file. After the 4-byte record length field, the next field must begin with the characters HEADER. The Header Record identifies your organization to the bureau and provides context for the entire file.

Key fields in the Header Record include:

The Base Segment

The Base Segment is the core record for each consumer account. Every account you report must have exactly one Base Segment. The Base Segment must be at least 426 bytes in length.

The Base Segment contains the primary account information, including:

Account Identification Fields:

• Consumer Account Number — Your internal account identifier for this consumer. Must be unique within your portfolio.
• Portfolio Type — The type of account (Installment, Revolving, Mortgage, Open, Line of Credit).
• Account Type — A two-digit code identifying the specific type of credit (auto loan, credit card, student loan, etc.).

Consumer Identity Fields:

• Social Security Number — The consumer's SSN. Required for bureau matching.
• Date of Birth — The consumer's date of birth in MMDDYYYY format. Used for identity verification.
• Consumer Name — First name, middle name, last name, and generation code (Jr., Sr., etc.).
• First Line of Address — The consumer's street address. PO Box addresses are not accepted for the primary address field.
• City, State, Zip Code — Standard mailing address fields.

Account Status Fields:

• Account Status — A two-digit code indicating the current status of the account (current, delinquent, charged-off, paid, etc.).
• Payment Rating — Indicates the consumer's payment behavior relative to the terms.
• Payment History Profile — A 24-month history of payment status codes.
• Special Comment — Optional code for special circumstances (bankruptcy, natural disaster, etc.).
• ECOA Code — Indicates the relationship of the consumer to the account. Valid values for the Base Segment are: 1 (Individual), 2 (Joint Contractual), 5 (Co-Maker/Guarantor), 7 (Maker), T (Terminated), X (Deceased), Z (Delete Consumer).

Balance and Terms Fields:

• Current Balance — The outstanding balance as of the date of account information.
• High Credit or Original Loan Amount — The highest balance ever reached, or the original loan amount.
• Credit Limit — For revolving accounts, the maximum credit limit.
• Terms Duration — The number of months in the loan term.
• Scheduled Monthly Payment Amount — The required monthly payment.
• Actual Payment Amount — The amount actually paid in the most recent billing cycle.

Date Fields:

• Date Opened — When the account was opened.
• Date of Account Information — The "as of" date for this record — typically the last day of the billing cycle.
• Date of First Delinquency — For delinquent accounts, the date the account first became past due. This is one of the most scrutinized fields in Metro 2® compliance.
• Date Closed — For closed accounts, the date the account was closed.
• Date of Last Payment — The date the consumer made their most recent payment.

Optional Segments: J1, J2, K1–K4, L1, N1

Optional segments follow the Base Segment and provide additional information about the account or associated consumers.

J1 Segment — Associated Consumer (Same Address)

The J1 Segment is used to report an associated consumer who lives at the same address as the primary consumer. This is typically used for joint account holders or authorized users who share the same mailing address. The J1 Segment must be exactly 100 bytes, including the 2-byte segment identifier J1.

Valid ECOA codes for J1: 1, 2, 3, 5, 7, T, X, Z

J2 Segment — Associated Consumer (Different Address)

The J2 Segment is used to report an associated consumer who lives at a different address from the primary consumer. The J2 Segment must be exactly 200 bytes, including the 2-byte segment identifier J2.

Valid ECOA codes for J2: 1, 2, 3, 5, 7, T, W, X, Z

K1 Segment — Original Creditor Name

The K1 Segment contains the name of the original credit grantor, including any partnering affinity name and the creditor's classification. It is reported by collection agencies, debt buyers, check guarantee companies, student loan guaranty agencies, the U.S. Department of Education, and the U.S. Treasury. Must be exactly 34 bytes, including the 2-byte segment identifier K1.

K2 Segment — Purchased From / Sold To

The K2 Segment contains the name of the company from which an account was purchased, or the name of the company to which an account was sold. Must be exactly 34 bytes, including the 2-byte segment identifier K2.

K3 Segment — Mortgage Information

The K3 Segment contains the Fannie Mae or Freddie Mac loan number associated with a mortgage account and/or the Mortgage Identification Number (MIN) assigned by MERS. Must be exactly 40 bytes, including the 2-byte segment identifier K3.

K4 Segment — Specialized Payment Information

The K4 Segment contains additional account information on deferred payments or balloon payments. Must be exactly 30 bytes, including the 2-byte segment identifier K4.

L1 Segment — Student Loan Information

The L1 Segment contains additional information specific to student loan accounts. Must be exactly 54 bytes, including the 2-byte segment identifier L1.

N1 Segment — Employment Information

The N1 Segment contains the consumer's employment information. Must be exactly 146 bytes, including the 2-byte segment identifier N1.

The Trailer Record

The Trailer Record is always the last record in the file. After the 4-byte record length field, the next field must begin with the characters TRAILER. The Trailer Record provides summary statistics that the bureau uses to verify the integrity of the file.

Key fields in the Trailer Record include:

The Most Common Metro 2® Errors

Based on 38+ years of processing Metro 2® files for organizations of all sizes, these are the errors we see most frequently:

How Hutchins Systems Helps

Hutchins Systems has been processing Metro 2® files since 1986. Our software and services are designed to catch every one of the errors described above — and hundreds more — before your file reaches the bureau.

• Credit Time 2000© — Desktop Metro 2® software for Windows. Generates, validates, and submits Metro 2® files.
• e-CreditTime — Cloud-based Metro 2® software. Works on any device, no installation required.
• MORFi Web — Advanced cloud platform for organizations reporting 100 to 1,000,000 accounts per month.
• MORFi API — REST API for software vendors and SaaS platforms that need to embed Metro 2® processing.
• Stack Data Processing — Fully managed monthly submission service. We handle everything from file generation to bureau delivery.
• Compliance Audit Service — We audit your existing Metro 2® files and identify every error before they become bureau rejections.