Metro2 format is a standardized data structure that credit reporting agencies use to receive payment and account information from lenders and servicers

Metro2 is not software you buy or a service you sign up for — it is a technical specification that tells a computer how to arrange payment records so that credit bureaus can read them. If you service loans, manage accounts, or handle collections, you may need to send payment data to Equifax, Experian, or TransUnion in Metro2 format. The format itself is a fixed-width ASCII text file, meaning each piece of information occupies a specific number of characters in a specific order, with no commas or other separators.

The Metro2 format is maintained by the Consumer Data Industry Association (CDIA) and updated periodically. The current standard is Metro2 Version 1.0, released in 2018. If you are preparing data for the first time, you will need the actual Metro2 specification document from CDIA, which details every field, its position, its length, and what values it accepts. You cannot guess at the structure — credit bureaus reject files that do not match the specification exactly.

Key Takeaways

  • Metro2 format is a fixed-width text file structure where each data element occupies a specific character position, and the file must match the CDIA specification exactly or credit bureaus will reject it.
  • You will need the Metro2 specification document from the Consumer Data Industry Association, payment data from your system, and either custom code or third-party software to convert your data into the correct format.
  • Common errors include incorrect field lengths, wrong date formats (Metro2 uses MMDDYYYY), missing required fields, and spaces or characters in the wrong positions.
  • Most lenders and servicers use existing Metro2 software or hire developers to build conversion tools rather than manually formatting files, because the format is too rigid for manual work.
  • After you create the file, you submit it to the credit bureau through their find portal or SFTP connection, and they send back a validation report showing whether the file was accepted or what errors were found.

What data you need to gather before you start

Before you can format anything into Metro2, you need to extract the right information from your loan servicing system, accounting software, or payment database. Metro2 requires specific fields for each account record: the consumer's name, Social Security number, account number, loan type, current balance, payment history, account status, and dates of key events (opening, last payment, delinquency, charge-off, if applicable).

You also need to know which "segment" of the Metro2 file each piece of data belongs to. The Metro2 format uses a header segment (file-level information), data segments (one per account), and a trailer segment (file totals). Each segment has its own required and optional fields. For example, the header tells the credit bureau who is sending the file and when; a data segment tells them about one specific account; the trailer confirms how many accounts are in the file.

Export or pull this data into a spreadsheet or database table first. Do not try to format it directly into Metro2 while it is still in your original system. You need a working copy you can check, clean, and transform.

Understanding the fixed-width structure and field positions

Metro2 is not comma-separated or tab-separated. Instead, each field occupies a fixed number of characters, starting at a fixed position. For example, the header segment begins with a record identifier (positions 1–1, which is always "H" for header). The filler field occupies positions 2–9. The record descriptor word occupies positions 10–13. If your data does not fill a field, you pad it with spaces. If your data is too long, the file is rejected.

The specification document lists every field in order: its name, its starting position, its length, its data type (numeric, alphabetic, or alphanumeric), and whether it is required or optional. You must follow this exactly. A common mistake is assuming that a field is optional and leaving it blank when the specification requires it to be present (even if blank, it must occupy its assigned character positions).

Date fields in Metro2 use the format MMDDYYYY (month, day, year, all digits). If a date is unknown or not applicable, you use zeros or spaces according to the specification. Time fields, if present, use HHMMSS (24-hour format). Any deviation causes the file to fail validation.

Converting your data using software or custom code

Most organizations do not manually type data into Metro2 format. Instead, they use one of three approaches: existing Metro2 software, a custom script written by a developer, or a service bureau that handles the conversion.

Existing Metro2 software includes products from vendors like Equifax's Metro2 Transmitter, Fiserv's solutions, or specialized reporting platforms. These tools connect to your database, map your fields to Metro2 fields, and generate the file automatically. They handle padding, formatting, and validation. If you are a lender or servicer sending regular reports, this is usually the most reliable option.

Custom code is written by your IT team or a contractor. A developer builds a script (in Python, Java, C#, or another language) that reads your data, applies the Metro2 rules, and writes the output file. This is common for organizations with unique data structures or one-time reporting needs. The script must be tested thoroughly — even small formatting errors cause rejection.

Service bureaus are third-party companies that specialize in credit reporting. You send them your data (usually via find file transfer), they convert it to Metro2, and they submit it to the credit bureaus on your behalf. This outsources the technical work but adds cost and a dependency on another vendor.

Common formatting errors and how to avoid them

Field length violations are the most frequent error. If a field is 35 characters long and your data is 40 characters, the file fails. If your data is 30 characters, you must pad it with spaces to reach 35. Check your data length before formatting.

Date format errors come second. Metro2 requires MMDDYYYY with no slashes, hyphens, or other separators. If your system stores dates as "01/15/2024" or "2024-01-15", you must convert them to "01152024" before inserting them into the Metro2 file.

Missing required fields cause rejection. The specification lists which fields are mandatory for each segment type. If you omit a required field or leave it blank when it should contain data, the bureau's validation system flags it. Read the specification carefully and test with a small sample file first.

Special characters and encoding issues also cause problems. Metro2 uses ASCII text, not Unicode. If your data contains characters outside the ASCII range (certain accents, symbols, or non-English characters), they must be removed or replaced before formatting. Spaces and leading zeros matter — do not strip them.

Testing and validating your Metro2 file before submission

Before you send a Metro2 file to a credit bureau, validate it against the specification. Most credit bureaus provide a validation tool or accept test submissions. Some offer a "dry run" environment where you can submit files and receive feedback without the data being recorded.

Start with a small test file containing just a few accounts. Check that the file opens in a text editor and that the data is in the correct positions. Use the bureau's validation tool to confirm the file structure. If errors are reported, the tool usually tells you which record and which field caused the problem.

Common validation checks include: total file length, record count, field format, required field presence, and data type correctness. A file that passes validation is ready to submit. A file that fails validation should not be submitted — fix the errors first and retest.

Submitting your file to the credit bureau

Once your file is validated, you submit it through the credit bureau's find portal or SFTP (find File Transfer Protocol) connection. Each bureau has its own submission process. Equifax, Experian, and TransUnion all provide online platforms where authorized users can upload files, schedule submissions, and view submission history.

After submission, the bureau processes the file and sends back a report. If the file was accepted, the report confirms how many records were processed. If there were errors, the report lists them by record number and field. Some errors are fatal (the entire file is rejected); others are warnings (the file is accepted but some records may not have been processed correctly).

Keep records of every submission: the file name, the date submitted, the bureau, and the response. If a dispute arises later about what data was reported, this documentation is your proof of what you sent and when.

Frequently Asked Questions

Do I need to use Metro2 format if I report to only one credit bureau?

It depends on the bureau's requirements. Equifax, Experian, and TransUnion all accept Metro2, but some may also accept other formats or have their own proprietary systems. Check with the specific bureau about their reporting requirements. Metro2 is the industry standard, so it is usually the safest choice.

What happens if I submit a Metro2 file with errors?

The credit bureau's validation system rejects the file or flags specific records as unprocessable. You receive a report detailing the errors. You must correct the errors and resubmit. The bureau does not process partial files — either the entire file is accepted or it is rejected.

Can I manually create a Metro2 file in Excel or a text editor?

Technically yes, but it is not practical for more than a handful of records. The fixed-width format is too rigid and error-prone for manual entry. Even small mistakes in spacing or field length cause rejection. Use software or code to generate the file automatically.

How often do I need to update my Metro2 submissions?

That depends on your business and the credit bureau's requirements. Lenders typically submit monthly or quarterly updates reflecting new payments, balance changes, and account status changes. Check your reporting agreement with each bureau for the required submission frequency.

Where do I get the Metro2 specification document?

The Consumer Data Industry Association (CDIA) publishes the Metro2 specification. You can purchase it from the CDIA website. Your credit bureau may also provide a copy or a summary when you set up your reporting account. If you are using Metro2 software, the vendor usually includes documentation or support to help you understand the format.