Metro 2 codes, in plain English
Your credit report is a translation. Lenders and collectors don't send the bureaus sentences; they send coded fields, and the bureaus turn those codes into the words you read. Here is what 103 of the most common codes mean and what to check when one shows up on your file.
What Metro 2 is
Metro 2 is the standard electronic format lenders, card issuers and collection agencies use to report accounts to the credit bureaus, usually in monthly batches. The Consumer Data Industry Association developed it, according to the CFPB's 2012 review of the credit reporting system, and keeps the full manual behind an access agreement for the companies that report data.
Each account becomes a record of coded fields: its status, balances, dates, who is responsible for it and up to 24 months of payment history. When a field is wrong, naming that exact field in your dispute gives the company something specific to check. Our guide to how Metro 2 works covers the format and the dispute system built on it.
Look up a code
Account status codes
Account status is the two-character code a lender or collector sends each month to say where the account stands: current, a certain number of days behind, paid and closed, transferred, or ended badly through collection, charge-off, repossession or foreclosure. It's the single field that most shapes how a tradeline reads. Some statuses describe the past as well as the present, such as paid but once charged off. Two values, DA and DF, aren't statuses at all. They're instructions to delete the account.
- 05Account transferred
- 11Current (0 to 29 days past due)
- 13Paid or closed, zero balance
- 61Paid in full, was a voluntary surrender
- 62Paid in full, was a collection
- 63Paid in full, was a repossession
- 64Paid in full, was a charge-off
- 65Paid in full, foreclosure was started
- 7130 to 59 days past due
- 7860 to 89 days past due
- 8090 to 119 days past due
- 82120 to 149 days past due
- 83150 to 179 days past due
- 84180 or more days past due
- 88Government claim filed
- 89Deed in lieu of foreclosure
- 93Collection
- 94Foreclosure completed
- 95Voluntary surrender
- 96Repossession
- 97Charge-off
- DADelete account (not fraud)
- DFDelete account (confirmed fraud)
Payment rating codes
Payment rating is a one-character companion to account status. It matters most when the status describes an ending rather than a monthly condition, such as transferred, paid or closed, deed in lieu or foreclosure. The status says what happened, and the payment rating says how far behind the account was at that moment. That's how a report can say an account is paid and closed and still show it was 60 days late when it closed. The values run from 0 for current through 6 for 180 or more days, plus G for collection and L for charge-off.
- 0Current when the status was reported
- 130 to 59 days past due when reported
- 260 to 89 days past due when reported
- 390 to 119 days past due when reported
- 4120 to 149 days past due when reported
- 5150 to 179 days past due when reported
- 6180 or more days past due when reported
- GIn collection when reported
- LCharged off when reported
Payment history profile characters
The payment history profile is a 24-character string, one character per month, that becomes the month-by-month grid on your report. The most recent month comes first. Each character records the account's condition that month: current, a band of days late, no data, or a severe outcome like collection or charge-off. Bureaus translate these characters into their own symbols, such as OK, 30, 60 or CO, so the labels you see won't match the raw codes, and they differ from bureau to bureau.
- 0Current that month
- 130 days past due that month
- 260 days past due that month
- 390 days past due that month
- 4120 days past due that month
- 5150 days past due that month
- 6180 or more days past due that month
- BNo history before this point
- DNo history reported this month
- EZero balance and current
- GCollection
- HForeclosure
- JVoluntary surrender
- KRepossession
- LCharge-off
ECOA codes
The ECOA code says how you're connected to an account and who is legally responsible for it. It's reported separately for each person on the account, which is why the same tradeline can show as individual on one person's report and authorized user on another's. The name comes from the Equal Credit Opportunity Act. A wrong code here can put someone else's debt on your file, or make a debt you co-signed look like it isn't yours. Two of the codes, T and Z, are instructions about a person's link to the account rather than descriptions of it.
Compliance condition codes
Compliance condition codes are the dispute and consumer-closure flags. They tell the bureau that you dispute the account under the Fair Credit Reporting Act or the Fair Credit Billing Act, that an investigation finished and you still disagree, or that you were the one who closed the account. They produce remarks like account information disputed by consumer. A code stays in place until the furnisher replaces it or sends XR to remove it, so a dispute flag can outlive the dispute if nobody clears it.
- XAClosed at consumer's request
- XBDisputed by consumer, investigation open
- XCDispute investigated, consumer disagrees
- XDClosed by consumer and disputed
- XEClosed by consumer, dispute investigated, consumer disagrees
- XFBilling dispute under the Fair Credit Billing Act
- XGBilling dispute resolved, consumer disagrees
- XHPreviously disputed, investigation complete
- XJClosed by consumer, billing dispute open
- XRRemove the last compliance code
Special comment codes
Special comment codes are short standardized remarks that explain something unusual about an account: a payment plan, a forbearance, a settlement, a loan modification, a transfer, or how the account was paid off. A furnisher can send only one per account each month, so it picks the most important. Some describe a temporary condition and should drop off when it ends; others describe how the account finished and stay. Bureaus print them as plain-language remarks, not codes. This list covers the most widely used codes that public furnisher documentation confirms.
- BPayments managed by a counseling program
- CPaid by co-maker or guarantor
- HLoan assumed by another party
- IElection of remedy
- MClosed by the credit grantor
- OTransferred to another lender
- SSpecial handling
- VAdjustment pending
- ABDebt being paid through insurance
- ACPartial payment agreement
- AHPurchased by another company
- AIRecalled to active military duty
- ALStudent loan assigned to the government
- AMPayments by wage garnishment
- APCredit line suspended
- ASClosed due to refinance
- ATClosed due to transfer
- AUPaid for less than the full balance
- AVFirst payment never received
- AWAffected by a natural or declared disaster
- AXPaid from collateral
- AZRedeemed repossession
- BATransferred to recovery
- BLCredit card lost or stolen
- BNPaid by the original seller
- BOForeclosure proceedings started
- BPPaid through insurance
- BTPrincipal deferred, interest-only payments
- CHGuaranteed or insured
- CIClosed due to inactivity
- CJCredit line closed, in repayment
- CKCredit line reduced, collateral lost value
- CMCollateral released, balance owing
- CNModified under a federal government plan
- COLoan modified
- CPAccount in forbearance
- CSChild support agency account
About these explanations
These explanations are ScoreTuner's plain-English summaries, written from public furnisher documentation, industry training material and bureau guidance listed on each code's page. The official specification is the CDIA Credit Reporting Resource Guide, which is copyrighted and not reproduced here. Each bureau translates codes into its own wording, so the words on your report may not match our labels exactly.
If a code on your report is wrong, you can dispute it with the bureau or with the company that reported it. Start with how to dispute a credit report error, then use the free letter builder to write it.
- Metro 2 Format for Credit Reporting, Consumer Data Industry Association
- Key Dimensions and Processes in the U.S. Credit Reporting System (December 2012), Consumer Financial Protection Bureau