What Metro2 format is and why lenders use it
Metro2 is a standardized data format that lenders, servicers, and collection agencies use to report payment history and account status to the three major credit bureaus—Equifax, Experian, and TransUnion. Instead of each creditor sending information in their own way, Metro2 creates a uniform structure so the bureaus can read and store the data consistently.
If you work in lending, collections, or credit management, you may need to compile your payment records into Metro2 format before submitting them to the bureaus. The format specifies exactly where each piece of information goes: account number, payment amount, payment date, account status, and dozens of other fields. A single misplaced character or wrong date can cause the bureau to reject the entire file or record the account incorrectly.
Metro2 is maintained by the Consumer Data Industry Association (CDIA) and updated periodically. The current version is Metro2 Version 1.0, released in 2015, though some bureaus still accept earlier versions. Before you begin compiling data, confirm which version your bureau requires—this is usually stated in your submission agreement or on the bureau's data submission portal.
Key Takeaways
- Metro2 is a fixed-field format where each data element occupies a specific column position; moving information to the wrong column will cause the bureau to reject or misread the record.
- You must obtain or create a Metro2 specification document from the Consumer Data Industry Association (CDIA) or your credit bureau to know the exact column positions, field lengths, and valid values for each data element.
- Payment data must include account identifiers, current balance, payment history, account status codes, and consumer contact information, all formatted according to the bureau's requirements.
- Most lenders and servicers use dedicated Metro2 software or export tools built into their loan management systems rather than manually typing data into a text file.
- Test your file with a validation tool before submitting to the bureau; rejected files delay credit reporting and may trigger compliance issues.
Understanding the Metro2 file structure and field positions
Metro2 is a fixed-field format, meaning each piece of information must start and end at a specific column position in the file. Unlike a spreadsheet where you can put data in any cell, Metro2 requires exact placement. For example, the account number might occupy columns 1 through 20, the payment amount columns 21 through 29, and the payment date columns 30 through 37. If you put the payment amount in the wrong columns, the bureau's system will either reject the file or read the data as gibberish.
The Metro2 specification document lists every field, its column range, its length, its data type (numeric, alphabetic, or alphanumeric), and the valid values it can contain. For instance, account status codes are numeric and limited to specific numbers: 0 for current, 1 for 30 days past due, 2 for 60 days past due, and so on. If you enter a status code that is not in the approved list, the bureau will flag it as invalid.
A Metro2 file typically contains three types of records: header records (which identify the sender and file), data records (which contain account and payment information), and trailer records (which summarize the file contents). Each record type has its own field layout. You must include all three, in the correct order, and with the correct number of records so the trailer matches the actual data.
Obtaining the Metro2 specification and validation rules
The official Metro2 specification is published by the Consumer Data Industry Association (CDIA). You can purchase or download the specification from the CDIA website, though it may require membership or a fee. The specification includes the complete field layout for all three record types, definitions of all valid codes and values, and examples of correctly formatted records.
Your credit bureau may also provide a specification document or data submission guide that clarifies which version they accept and any local variations they require. Equifax, Experian, and TransUnion each have data submission portals where you can download their specific requirements. Do not assume all three bureaus accept identical formats; they often have minor differences in field lengths, required fields, or acceptable status codes.
Many bureaus also provide a validation tool—software that checks your Metro2 file for format errors before you submit it. These tools catch common mistakes like incorrect field lengths, invalid status codes, missing records, or mismatched trailer counts. Running your file through validation before submission saves time and prevents rejection.
Compiling payment data from your loan or servicing system
Most lenders and servicers do not manually type Metro2 files. Instead, they export payment data from their loan management system, accounting software, or servicing platform into a format that can be converted to Metro2. Common source formats include CSV (comma-separated values), fixed-width text files, or direct database exports.
The data you need to extract includes: account number, consumer name and address, loan type and amount, current balance, payment history (dates and amounts of the last 24 months of payments), current account status, date of last payment, and date of last account activity. Some bureaus also require employment information, phone numbers, or Social Security numbers, depending on the account type.
If your system has a built-in Metro2 export function, use it. Most modern loan servicing platforms (such as Fiserv, Fidelity National Information Services, or Black Knight) include Metro2 export tools that handle field positioning and validation automatically. If your system does not have this function, you will need to use a third-party Metro2 conversion tool or hire a developer to build a custom export script.
Mapping your data fields to Metro2 columns
Once you have extracted your payment data, you must map each field from your system to the correct Metro2 column position. Create a mapping document that lists each Metro2 field, its column range, the data type it expects, and the corresponding field in your source data. For example:
| Metro2 Field | Columns | Data Type | Your System Field |
|---|---|---|---|
| Record Identifier | 1–1 | Numeric | Record Type (Header = 1, Data = 2, Trailer = 3) |
| Account Number | 2–21 | Alphanumeric | Loan ID |
| Consumer Name | 22–61 | Alphabetic | Borrower Last Name + First Name |
| Current Balance | 62–71 | Numeric | Outstanding Principal |
| Payment Amount | 72–80 | Numeric | Last Payment Amount |
| Payment Date | 81–88 | Numeric (MMDDYYYY) | Last Payment Date |
| Account Status | 89–90 | Numeric | Account Status Code |
Pay special attention to date formats. Metro2 typically requires dates in MMDDYYYY format (for example, 01152024 for January 15, 2024). If your system stores dates as YYYY-MM-DD or any other format, you must convert them. Similarly, numeric fields must be right-justified and padded with leading zeros if necessary. A balance of $5,000 might need to be formatted as 0000500000 (10 digits) depending on the field length.
Testing and validating your Metro2 file before submission
Before you send your Metro2 file to the credit bureau, run it through a validation tool to catch errors. Most bureaus provide a free validation tool on their data submission portal. Upload your file, and the tool will check for format errors, invalid codes, missing required fields, and mismatched record counts.
Common validation errors include: incorrect field lengths (data that is too long or too short for its column), invalid status codes (a code not in the approved list), missing header or trailer records, mismatched record counts (the trailer says 500 records but the file contains 502), and invalid date formats (dates that do not exist, like 02302024).
If validation fails, the tool will usually tell you which record and which field caused the error. Go back to your mapping and source data, correct the error, and revalidate. Do not submit a file that fails validation; the bureau will reject it, and your payment data will not be reported to the credit bureaus.
Submitting your Metro2 file and tracking confirmation
Once your file passes validation, submit it through your bureau's data submission portal. Most bureaus accept files via SFTP (secure file transfer protocol), web upload, or API integration. Your submission agreement will specify which method to use and any naming conventions the bureau requires for the file.
After submission, the bureau will send you a confirmation receipt that includes a file ID, submission timestamp, and record count. Keep this receipt for your records. The bureau will then process your file, which typically takes one to three business days. During processing, the bureau runs its own validation checks and loads the data into its database.
If the bureau finds errors during processing, it will send you a rejection report that lists the problematic records and the reason for rejection. Common rejection reasons include duplicate account numbers, invalid consumer identifiers, or data that conflicts with existing records in the bureau's system. You will need to correct the errors and resubmit the file.
Common mistakes and how to avoid them
One of the most frequent errors is using the wrong account status code. Each code represents a specific payment condition: 0 is current, 1 is 30 days late, 2 is 60 days late, and so on. If you report an account as current (0) when it is actually 60 days past due (2), the credit bureau will report it incorrectly, which can harm the consumer's credit score and may violate Fair Credit Reporting Act (FCRA) requirements.
Another common mistake is inconsistent date formatting. If some records use MMDDYYYY and others use MM/DD/YYYY, the bureau will reject the file or misinterpret the dates. Establish a single date format for your entire file and stick to it.
Truncating or padding data incorrectly also causes problems. If a consumer's name is longer than the field allows, do not simply cut it off; check the bureau's rules for how to handle long names. If a numeric field is shorter than required, pad it with leading zeros, not spaces.
Finally, do not submit a file without running it through validation first. Validation catches 90 percent of format errors before they reach the bureau, saving you time and preventing delays in credit reporting.
Frequently Asked Questions
What software can I use to create a Metro2 file if my loan system does not have an export function?
Several third-party tools can convert CSV or fixed-width data into Metro2 format, including Equifax's Metro2 Creator, Experian's Data Delivery System, and independent tools like Metro2 Converter. Some are free; others charge a fee. Alternatively, you can hire a developer to write a custom script that reads your data and outputs Metro2-formatted records. The cost depends on the complexity of your data and the volume of records.
Can I submit Metro2 files to all three bureaus at once, or do I need separate files for each?
You can submit the same Metro2 file to all three bureaus if your data meets all three bureaus' requirements. However, each bureau has its own submission portal and may have slightly different field requirements or validation rules. Check each bureau's data submission guide before submitting. Some lenders use a third-party aggregator service that accepts one file and distributes it to all three bureaus, handling any format differences automatically.
What happens if I report a payment date that is in the future?
The bureau will reject the record or flag it as invalid during validation. Payment dates must be in the past and must match actual payment activity in your system. If you are preparing a file for future submission (for example, preparing next month's data in advance), do not include future payment dates; submit the file only after the payments have actually been received and posted.
How often should I submit Metro2 files to the credit bureaus?
Most lenders and servicers submit Metro2 files monthly, typically within 30 days of the end of the month. Some high-volume servicers submit weekly or even daily. Your submission agreement with the bureau will specify the required frequency. More frequent submissions mean more current credit reporting, which is generally better for consumers and reduces disputes.
What should I do if the bureau rejects my file after I submit it?
The bureau will send you a rejection report that identifies which records failed and why. Review the report, correct the errors in your source data or mapping, regenerate the Metro2 file, run it through validation again, and resubmit. Keep copies of all rejection reports and resubmission files for compliance and audit purposes. If you receive repeated rejections for the same reason, contact the bureau's data support team for clarification.