How should a furnisher report a replacement credit card or an account number change, and when should the L1 Segment be used instead of creating two separate tradelines?
Account number changes happen constantly: card replacements, system migrations, portfolio conversions, rebrands, security-driven reissuances. Under Metro 2, how you handle the number change determines whether the consumer ends up with one continuous tradeline (preserving all prior history) or two separate tradelines (one closed/transferred, one new). The wrong choice creates duplicate tradelines, lost history, inflated account counts, and consumer disputes. Metro 2 provides the L1 Segment specifically to handle number changes cleanly, and it should be the default approach in most scenarios.
Definitions and context
When a credit card or account number changes, the account itself may or may not change. The critical question for Metro 2 reporting is:
- Is this the same account with a new number? (Same obligation, same consumer, same Date Opened, just a different number.) If yes, the L1 Segment is the right tool.
- Is this a genuinely new account replacing a closed one? (New contractual terms, new Date Opened, no continuity of the old obligation.) If yes, two tradelines may be appropriate.
Most credit card replacements (expiring cards, damaged cards, routine reissuance, security upgrades) fall into the first category. The underlying account, credit limit, Date Opened, and payment history remain the same. Only the plastic and the number change.
The L1 Segment: preferred approach for account number changes
The L1 Segment (Account Number/Identification Number Change) is designed to tell consumer reporting agencies: “This is the same account, but the number has changed.” It preserves all prior history on one continuous tradeline.
How it works
- In the Base Segment, report the old Consumer Account Number (Field 7) and/or the old Identification Number (Field 5), exactly as previously reported.
- Append the L1 Segment with the new Consumer Account Number and/or new Identification Number.
- The Change Indicator (L1 Field 2) specifies what changed:
- 1 = Consumer Account Number change only
- 2 = Identification Number change only
- 3 = Both Consumer Account Number and Identification Number change
Timing
- Report the L1 Segment one time only, in the reporting period when the change occurs.
- In the following month’s reporting period, the new numbers should appear in the Base Segment. Do not report the L1 Segment again.
What is preserved
- Date Opened (unchanged)
- Payment History Profile (unchanged, continuous)
- All prior Account Status history
- Date of First Delinquency (unchanged, if applicable)
- Credit Limit, High Credit, and all other account-level fields
This is the cleanest approach because the consumer sees one tradeline with full history, and data users see continuous performance data.
Two tradelines: when it is appropriate (and when it is not)
The two-tradeline approach creates one “closed/transferred” tradeline and one new tradeline. This should only be used when:
- The old account is genuinely being closed and a new, separate obligation is being opened.
- Account history cannot be verified by the system or entity reporting the new account (for example, a servicing transfer where the new servicer cannot validate prior performance data).
Old account (reported as transferred)
- Scheduled Monthly Payment Amount: zero.
- Account Status: the appropriate code that specifies the status at the time of the change.
- Special Comment: report “AT” (Account closed due to transfer) for internal changes.
- Current Balance and Amount Past Due: zero.
- DOFD: if the account was delinquent at the time of the change, report the date of the first 30-day delinquency that led to the status being reported.
- Date Closed: the date the account was changed/transferred.
New account
- Consumer Account Number: the new number.
- Date Opened: the date the original account was opened (to maintain account age).
- Account Status: the status as of the Date of Account Information for the new account.
- Payment History Profile: report character “B” for months when the account was reported under the old number. Do not duplicate the prior account’s payment history. That history already exists on the old tradeline.
- DOFD: if the account is delinquent at the time the new number takes effect, report the date of the first 30-day delinquency that led to the status being reported.
Credit card replacement scenarios
Standard card replacement (expiration, damaged card, routine reissue)
- Use the L1 Segment.
- The account terms, Date Opened, credit limit, and history are unchanged.
- This is the same account. There is no reason to create two tradelines.
Lost or stolen credit card (consumer keeps the account, gets a new number)
- Preferred approach: use the L1 Segment to change the number. Continue reporting with the original Date Opened.
- If payment history is invalid during the period the card was compromised (for example, fraudulent charges created a false delinquency), correct the Payment History Profile for the affected months. If accurate history is unknown for those months, report “D” (no payment history available this month) for the unknown positions.
Lost or stolen credit card (consumer does not want a replacement, will pay off the existing account)
- Continue reporting the existing account normally.
- Report Compliance Condition Code XA (Account closed at consumer’s request) to indicate the account is closed to further use.
- When the balance reaches zero, report Account Status 13 with the applicable Payment Rating and Compliance Condition Code XA.
- Do not use Special Comment BL (Credit card lost or stolen) in this scenario, because the consumer is keeping and paying off the existing account.
Lost or stolen credit card (account closed, separate new account opened)
- Report Special Comment BL (Credit card lost or stolen), the appropriate Account Status (not DA or DF), and Current Balance = zero on the old account. Do not report this account on subsequent updates.
- If payment history is invalid during the compromised period, correct the PHP using “D” for unknown months.
- In the following month, report the new credit card as a separate account with a new Account Number, the same Date Opened as the original account, and the appropriate Account Status and Current Balance.
- Do not report the original account’s payment history under the new Account Number.
Compliance requirements (FCRA alignment)
Under the FCRA, furnishers must report information that is accurate and avoid creating misleading tradeline structures. Common compliance pitfalls with account number changes include:
- Duplicate tradelines from unnecessary two-tradeline reporting. If the account is the same obligation with a new number, using two tradelines inflates the consumer’s account count and can distort debt-to-income calculations.
- Lost history from skipping the L1 Segment. If you simply stop reporting the old number and start reporting the new number without an L1, the consumer reporting agencies may not connect the two, resulting in a “new” account with no history and an orphaned old account that never gets updated.
- Duplicated PHP across old and new tradelines. When two tradelines are used, the new account must not carry the old account’s payment history. That history already lives on the old tradeline.
- Failing to correct PHP when a card was compromised. If fraudulent activity created false delinquency, the PHP must be corrected. Leaving inaccurate history in place because “that is what was reported at the time” does not satisfy accuracy obligations.
Impact on consumers
Account number changes that are handled poorly can:
- Create the appearance of a new, thin account (lost account age and history)
- Show two tradelines for one obligation (inflated debt, higher utilization ratio)
- Leave inaccurate delinquency from a compromised period on the record
- Trigger disputes and reinvestigation cycles that are entirely preventable
The L1 Segment exists specifically to prevent these outcomes.
Conclusion (key takeaways)
For most account number changes (card replacements, system migrations, reissuances), the L1 Segment is the right tool. It preserves history, prevents duplication, and maintains account age. Two tradelines should only be used when the old and new accounts are genuinely separate obligations or when prior history cannot be verified. When a card is lost or stolen, correct the PHP for affected months and choose the reporting path (L1 vs two tradelines vs payoff of existing account) based on whether the consumer is keeping the account.