Getting approved to furnish data is the easy half. The hard half arrives every month. Your servicing data has to become a valid Metro 2 file. All three bureaus have to accept it. Most teams underestimate that step until the first submission bounces back.
Key takeaways
Metro 2 is a fixed-width record format, not a spreadsheet or a CSV export.
Furnishers typically generate and submit a new file once per calendar month.
Most companies either buy a furnishing service or build a mapping layer over their servicing database.
A file that passes format validation can still be rejected for logic errors inside the segments.
What is a Metro 2 file, and what does it actually contain?
Metro 2 is the standard reporting format the credit bureaus accept from data furnishers. It is a fixed-width text file, not a spreadsheet. Each record describes one account for one reporting period. The file bundles a header record and one base segment per account. Optional segments cover extra parties and addresses. A trailer record closes the file.
The base segment carries the account identifiers, the balance, the scheduled payment, the account status, and the payment history profile. Optional segments extend that picture. J1 and J2 segments add associated consumers. K segments add original creditor and purchase details. L segments handle account transfers. N segments carry employment data.
The format is unforgiving by design. Fields sit at fixed positions with fixed lengths. A value that lands one character off will corrupt everything downstream of it in that record.
What services, products, or libraries can compile Metro 2 files?
Three categories of tooling exist. Furnishing service providers convert your data and submit on your behalf. Servicing and loan management platforms sometimes include a Metro 2 export module. Open-source libraries and internal scripts generate the file from your own database, leaving submission and corrections to you.
Open-source options tend to be thin. They usually handle field padding and record layout. They rarely encode the reporting logic, and they almost never manage bureau credentialing, monthly transmission, or dispute handling. That gap is where most build projects stall.
The practical question is not which library writes the bytes. The question is who owns the mapping logic, the validation rules, and the monthly operational cycle. Those three things carry the real cost.
How do companies generate a Metro 2 file each month from internal data?
The monthly cycle follows a repeatable pattern. Teams freeze a reporting date and extract account and payment records. They map each internal field to its Metro 2 position. They run validation, then transmit the file to each bureau. Most furnishers repeat this once per calendar month, on a consistent cutoff date.
The mapping layer is where the work concentrates. Your servicing system stores a payment status in its own vocabulary. Metro 2 expects a specific account status code and a specific payment rating for that same account. Someone has to write and maintain that translation.
Consistency matters more than speed. Bureaus expect the same account to appear with the same identifiers month over month. Reporting an account under a new identifier can create a duplicate tradeline on the consumer’s file.
Build your own Metro 2 pipeline or use a furnishing partner
Both paths work. The right choice depends on engineering capacity, portfolio complexity, and how much regulatory exposure your team wants to absorb. Building gives you full control of the mapping. Buying moves credentialing, validation, transmission, and corrections to a partner who already runs that cycle every month.
| Consideration | Build in house | Furnishing partner |
|---|---|---|
| Field mapping and record layout | Your engineers own it | Handled by the provider |
| Bureau credentialing | You apply and negotiate with each bureau | Provider guides or manages enrollment |
| Monthly transmission | You build and monitor the job | Provider runs the submission cycle |
| Validation and error handling | You write the rules | Provider validates before submission |
| Disputes and corrections | Your team handles each one | Provider supports correction workflows |
| Time to first live file | Often months | Typically much faster |
| Ongoing maintenance | Continuous, as codes and rules change | Absorbed by the provider |
Teams with a large engineering bench and a simple, single product portfolio often build. Teams furnishing across multiple products, or reporting to all three bureaus, more often buy.
What should you check before you submit a file?
Validate structure first, then logic. Structural checks confirm record length, field positions, character encoding, and that the trailer totals match the record count. Logic checks confirm the harder things. An account status of paid should not carry a balance. A charge-off date should not precede the account open date.
Common failure points start with date fields in the wrong format. Portfolio type codes may not match the account type. Payment history profiles may contradict the current status. Consumer identifiers may shift between months. Each of those can pass a length check and still create a data quality problem on a real consumer’s file.
Accuracy is a legal obligation, not a nice to have. Furnishers carry accuracy and dispute investigation duties under the Fair Credit Reporting Act. A clean validation step protects both the consumer and your program.
How CRS supports Metro 2 furnishing
CRS built Data Furnishing for lenders, property managers, and financial services providers. They report payment data without standing up the pipeline themselves. CRS supports furnishing to Equifax, Experian, and TransUnion in Metro 2 format. Teams can send data through an API feed or an Excel file upload, depending on how their servicing stack works.
Onboarding is FCRA-aligned and includes testing and ongoing support. That matters because most rejected first files fail on logic, not on syntax. A team with over 25 years of credit industry experience reviews the mapping before it reaches a bureau.
Commercial lenders can furnish business loan payment data through a separate pipeline. That pipeline converts servicing data into bureau-ready and consortia-ready formats. Credentialing, corrections, and monthly submissions run through a SOC 2 Type II process.
Furnishing also connects to the rest of the lifecycle. The same FinStack platform that handles ordering, compliance oversight, and billing visibility for credit pulls covers your furnishing activity. Narrow resellers solve one workflow. CRS aggregates credit, identity, fraud, and public records through one integration, then adds furnishing on the back end.
Still working out approval and cost? Start with our guide on how companies furnish data to the credit bureaus. If you have already been approved, the next step is the file itself.
Talk with our credit and compliance experts to see how CRS is configured for your furnishing use case.
FAQ
How often do companies send Metro 2 files?
Most furnishers submit once per calendar month, using a consistent cutoff date. Reporting on a steady cadence keeps consumer files accurate and prevents gaps in payment history. Some furnishers report more frequently for specific products, but monthly remains the standard cycle across consumer tradeline reporting.
Can I build a Metro 2 file with an open-source library?
Yes, for the file structure. Open-source tools generally handle padding, field positions, and record layout. They rarely encode the reporting logic that bureaus expect, and they do not manage credentialing, transmission, or dispute handling. Most teams end up building or buying those pieces separately.
What happens if a Metro 2 file has errors?
Bureaus may reject the file, reject individual records, or accept records that contain inaccurate data. Rejections delay reporting. Accepted errors are worse, because they land on a real consumer’s credit file and can trigger disputes. Validating before submission avoids both outcomes.
Do I need to furnish to all three bureaus?
No, furnishing is voluntary and you can choose your bureaus. Reporting to all three gives consumers the most consistent benefit, since lenders pull from different sources. Many furnishers start with one bureau and expand, though each bureau requires its own enrollment and its own transmission.
How long does it take to go live with data furnishing?
Timelines vary with portfolio complexity, bureau enrollment, and test file results. Teams that build everything in house often spend months on mapping and validation alone. Working with a furnishing partner typically shortens the path, because credentialing, format handling, and test cycles are already in place.
