Metro 2 Codes: The Complete Cheat Sheet
The Metro 2 format uses 12 coded fields, holding 195 distinct values in total. Each one occupies a fixed position in the Base Segment or a supplemental segment, and each has its own permitted values. This page lists every set in field order. Every code links to a full reference page covering what it means, when to report it, and which other fields it has to agree with.
Portfolio Types
One character that declares how an account behaves, and that every other Base Segment field has to agree with.
Account Type Codes
Identifies what kind of credit product the tradeline is, and pins it to a Portfolio Type.
Terms Frequency Codes
One character stating how often a payment is contractually due, and the unit that makes Terms Duration mean anything.
| Code | Meaning |
|---|---|
| D | Deferred |
| P | Single Payment |
| W | Weekly |
| B | Bi-weekly |
| E | Semi-monthly |
| M | Monthly |
| L | Bi-monthly |
| Q | Quarterly |
| T | Tri-annually |
| S | Semi-annually |
| Y | Annually |
Full terms frequency codes reference · Terms Frequency field spec
Account Status Codes
The state of the tradeline this cycle: current, delinquent by bucket, closed, charged off, or deleted.
Full account status code reference · Account Status field spec
Payment Ratings
Carries the account's delinquency level in the cycles where the Account Status describes a terminal condition instead of a payment condition.
Payment History Profile Codes
The fifteen single characters that make up the 24-month payment grid, one character per month, most recent first.
Full payment history profile codes reference · Payment History Profile field spec
Special Comment Codes
Adds a short standardized narrative to a tradeline explaining an unusual arrangement such as forbearance, a payment plan, a transfer, or a closure.
Full special comment codes reference · Special Comment field spec
Compliance Condition Codes
Signals a legal or dispute condition attached to the account for one reporting cycle.
Full compliance condition codes reference · Compliance Condition Code field spec
ECOA Codes
Declares each consumer's legal relationship to the account: who is liable, who merely has access, and who is being removed.
Consumer Information Indicators
Attaches a consumer-level condition such as bankruptcy, receivership, reaffirmation, or lease assumption to the tradeline, and changes how it purges.
Full consumer information indicators reference · Consumer Information Indicator field spec
Creditor Classification Codes
Two-digit code on the K1 segment naming the industry the original creditor operated in, so a purchased or placed debt can be recognised without naming the wrong party.
Full creditor classification codes reference · K1 Creditor Classification field spec
Residence Codes
An optional single character stating whether the consumer owns or rents the address reported on the record.
| Code | Meaning |
|---|---|
| O | Owns Residence |
| R | Rents Residence |
Codes that must agree with each other
A Metro 2 file can pass every structural check and still be wrong, because the codes are not independent. These are the cross-field conditions that cause most accepted-but-inaccurate records. They are the checks a validator has to run after the format check passes.
| Rule | What has to be true |
|---|---|
| Portfolio Type and Account Type | Every Account Type code belongs to a Portfolio Type. A mortgage account type reported under Portfolio Type R is a contradiction, not a rounding error. |
| Account Status and Payment Rating | When the Account Status describes a terminal or closed condition, the delinquency at that moment is carried by the Payment Rating. The pair has to describe the same account. |
| Payment Rating and Payment History Profile | Position 1 of the 24-character Payment History Profile must match the current Payment Rating, the profile fills from position 1 with no gaps, and history cannot improve after a charge-off. |
| Delinquency and Date of First Delinquency | Any delinquent status, non-zero payment rating, or delinquency value in the payment history implies a DOFD. The original DOFD must survive a dispute unchanged. Why it may not be re-aged. |
| Portfolio Type and Terms Frequency | An installment loan with no Terms Frequency and no Scheduled Monthly Payment is incomplete. Sub-monthly frequencies still report a monthly scheduled payment figure. |
| Compliance Condition Code persistence | A blank Compliance Condition Code does not clear the previous one. Clearing requires XR, which is why stale dispute flags are so common. |
| ECOA and the associated-consumer segments | Each associated consumer in a J1 or J2 segment carries its own ECOA code. A joint designation on the Base Segment with no associated consumer segment is a contradiction. |
| Bankruptcy indicator and dates | A bankruptcy Consumer Information Indicator freezes the DOFD for purging purposes and rides on the consumer, not the account, so a joint tradeline can carry it for one consumer and not the other. |
| Balances and limits | Current Balance above Credit Limit on a revolving account, Amount Past Due inconsistent with the status, and paid statuses reported with a non-zero balance are the three balance errors that recur every cycle. |
| K1 and purchased debt | When you are not the original creditor, the K1 segment carries the original creditor name and a Creditor Classification, and the K2 segment records the purchase or sale. |
The error and reject code library documents each of these as a specific check with the fix.
What changed in 2026
The CRRG is revised periodically and code sets do move. Two things are worth checking against your own copy of the current guide before your next mapping review:
- ECOA code X. The 2026 revision clarified reporting expectations for ECOA X. Confirm the current wording in your copy of the guide rather than relying on a mapping written against an earlier edition.
- Sub-monthly payment cadences. Pay-in-Four and other buy-now-pay-later products settle weekly or biweekly while Metro 2 assumes a monthly reporting cycle. See Terms Frequency for what the format does and does not resolve.
Where the published guidance is silent, this reference says so rather than guessing. Every code page names the CRRG artifact its meaning comes from.
The rest of the reference
See which of these codes are in your own file
Drop a .dat file into the free in-browser viewer and it decodes every segment against these code sets. No signup, and nothing is uploaded -- the file stays on your device.