How to Create a Metro 2 File from Your Payment Data (Step-by-Step)

What a Metro 2 file actually is

A Metro 2 file is a fixed-width text file that reports consumer account data to the credit bureaus in the format defined by the CDIA's Credit Reporting Resource Guide (CRRG). Every file has the same skeleton: a Header Record that identifies you as the furnisher and the reporting period, one Base Segment per account (the core tradeline data), optional appendage segments (J1/J2 for additional names, K segments for original creditors and purchased portfolios, L1 for account-number changes, N1 for employment), and a Trailer Record with file-level totals that must balance.

Each Base Segment is a single line of a fixed length — either the 366-character or the 426-character layout — where every field sits at an exact byte position. Getting a consumer's name, account number, balance, Account Status, and dates into the right positions, in the right format, is the entire job. The steps below walk through how to go from a spreadsheet or database export to a file the bureaus will accept.

What you need before you start

Three things should be in place before you build a file. First, your account data: a clean export of the loans, leases, or accounts you intend to report, with balances and payment status as of a single cycle date. Second, your subscriber/program codes from each bureau you'll report to — you cannot submit until you've been approved as a data furnisher and have the credentials and SFTP details for Equifax, Experian, TransUnion, or Innovis. Third, the Date of First Delinquency (DOFD) for any delinquent or charged-off accounts, since that date is immutable once set and anchors the seven-year reporting window.

If you have not yet been approved to furnish, that process (applying for subscriber codes, meeting minimum-record thresholds, and submitting test files) comes first and runs in parallel with getting your data ready.

Step 1 — Export your payment data (CSV, Excel, or API)

Pull your accounts from wherever they live — a loan origination or servicing system, a property-management platform, a collections system, or a database — into a structured export. CSV and Excel are the most common starting points; an API feed works too. Use a single as-of date for the whole batch so balances, statuses, and past-due amounts all reflect the same point in the cycle. Mixing periods within one file is a frequent source of inconsistency.

Step 2 — Map your columns to Metro 2 fields

This is the step where most systematic errors are introduced. Your export's column names ("customer_name", "balance", "status") have to be translated into specific Metro 2 fields at fixed byte positions, in the right data type and code set — for example, your internal status values have to become a valid Account Status code, and your portfolio type, account type, and terms have to map to the CRRG's permitted values. Build the mapping once, document it, and reuse it every cycle. A drag-and-drop field mapper (as in Metro2's sandbox) turns this into a visual step and flags columns that don't map cleanly.

Step 3 — Validate against the CRRG before you submit

Before generating anything for the bureaus, run your mapped data through validation. The CRRG defines hundreds of edits — required fields by portfolio type, status/past-due alignment, date logic, balance relationships, and cross-segment dependencies — and the bureaus run their own checks on every file you send. Catching errors here, rather than after submission, is what keeps your rejection rate low. Metro2's validation engine runs CRRG-aligned checks (700+) and surfaces the exact field and reason for each issue so you can fix the source data.

Step 4 — Generate the file (366 vs 426 layout)

Once the data is mapped and clean, generate the fixed-width file. The Metro 2 format comes in two layouts: the 366-character and the 426-character record. The 426 layout adds fields and is the more complete, widely used option; confirm which layout each bureau expects. The Header and Trailer are written automatically, and the Trailer's record counts and totals must match the segments in the file exactly — a mismatch will cause the whole file to be rejected.

Step 5 — Deliver the file to the bureaus over SFTP

Each bureau receives files over secure SFTP on the schedule you've agreed to (monthly is standard). You can upload manually using the credentials each bureau issues, or automate delivery so the file is transmitted to each bureau on a set schedule without manual steps. Automated delivery removes the most common operational failure — a missed or late submission — and is one of the reasons furnishers move off manual desktop workflows.

Step 6 — Read the bureau response and fix any rejects

After a file is processed, bureaus return a response indicating which records were accepted and which were rejected, with reason codes. Parse that response, correct the underlying data, and include the fixes in your next cycle (or a corrected resubmission). This is ordinary data-quality maintenance — keeping your reporting accurate over time. (Note: responding to consumer disputes is a separate obligation handled through the bureaus' e-OSCAR platform, not part of generating your monthly file.)

Doing this by hand vs. with software

You can build Metro 2 files by hand — writing code against the CRRG spec to assemble fixed-width records, maintaining the validation edits yourself, and keeping up with annual CRRG changes — but it is a real engineering project, and a single wrong byte position or status code can get a file rejected. Metro 2 software handles the mapping, validation, file generation, and delivery for you. Metro2's plans start at $19/month, and you can map a CSV and watch it validate in the free sandbox before paying anything.

FAQ

How often do I have to file? Most furnishers submit a monthly batch reflecting account activity as of a cycle date. You agree on a schedule with each bureau when you onboard.

Is there a minimum number of records? Each bureau sets its own minimums and requirements when you apply as a furnisher; thresholds vary by bureau and account type. Confirm the current requirement with each bureau during onboarding.

Can I start with a small number of records? Yes — Metro2's entry plan covers up to 100 records, so small furnishers and pilots can begin without committing to a large volume. Bureau minimums still apply for direct furnishing.

Do I need to know how to code to create a Metro 2 file? No. With field-mapping software you map your existing CSV or Excel columns to Metro 2 fields visually; no programming is required. An API is available if you do want to automate.