How should a furnisher report an account when a consumer disputes information directly to the furnisher, or when the account is temporarily unavailable because the furnisher is conducting an investigation (including potential identity theft)?
Consumer disputes filed directly with furnishers have grown substantially as consumers become more aware of their rights under the Fair Credit Reporting Act (FCRA). Metro 2 provides a structured, machine-readable way to communicate that an account is under investigation, that an investigation has concluded, or that confirmed fraud warrants deletion. This is not optional narrative commentary: Compliance Condition Codes are the standardized mechanism for signaling dispute status to consumer reporting agencies and downstream data users.
Definitions and context
Metro 2 separates dispute status (communicated through Compliance Condition Codes in Field 20) from account performance (Account Status, balances, PHP). The two operate independently:
- Compliance Condition Code (CCC): reflects whether the account is currently in dispute, whether that dispute has been resolved, or whether the consumer disagrees with the outcome.
- Account Status and other fields: continue to reflect the actual condition of the account as of the Date of Account Information, regardless of dispute status.
This separation ensures that dispute coding does not mask or alter the underlying performance data, which must remain accurate and supportable.
Step-by-step reporting standards
1) Consumer disputes directly to the furnisher (FCRA direct dispute)
When a consumer disputes the completeness or accuracy of account information directly to the furnisher under the FCRA:
- Report Compliance Condition Code XB to indicate the dispute is under investigation.
- Continue reporting all other account-level fields normally (Account Status, Current Balance, Amount Past Due, PHP, etc.) based on the Date of Account Information.
2) While the investigation is in progress
- Continue reporting CCC = XB each month (or allow it to retain per your reporting method).
- Do not suppress or freeze account-level reporting simply because the account is in dispute. Metro 2 guidance does not call for a “hold” on standard field updates during a direct dispute investigation.
3) When the investigation is complete
A. Investigation completed, information confirmed accurate:
- Report CCC = XR (removal code) to remove the dispute indicator, or
- Report CCC = XH to indicate the dispute was previously in dispute and the investigation is now complete.
B. Investigation completed, consumer disagrees with the outcome:
- Report CCC = XC to indicate the FCRA direct dispute investigation is complete but the consumer disagrees.
C. Investigation reveals an error:
- Correct the affected fields (Account Status, PHP, balances, or other data as needed).
- Report CCC = XR or XH to clear the dispute indicator after corrections are applied.
4) Confirmed fraud (identity theft investigation completed)
If the investigation determines the account was opened or used fraudulently:
- Report Account Status = DF (Delete entire account due to confirmed fraud).
- This removes the tradeline entirely.
Compliance requirements (FCRA alignment)
Under FCRA Section 623(b), furnishers who receive direct disputes must conduct a reasonable investigation and report results. Metro 2 Compliance Condition Codes are the operational implementation of that duty. Key compliance pitfalls include:
- Leaving XB indefinitely: Metro 2 guidance emphasizes that XB should not remain after the investigation concludes. Stale dispute codes suggest the furnisher never completed the investigation.
- Using XB in response to CRA-initiated disputes: Metro 2 guidance notes that Compliance Condition Codes should generally not be reported in response to consumer dispute investigation requests from the consumer reporting agencies (the e-OSCAR/ACDV process), except where a furnisher uses a CCC to satisfy a Fair Debt Collection Practices Act (FDCPA) obligation.
- Failing to correct errors identified during investigation: if the investigation reveals inaccurate data, the correction must be applied to the relevant fields (PHP, balances, Account Status) and not simply noted internally.
Impact on consumers
Dispute coding directly affects how lenders, landlords, and other permissible users interpret the tradeline. A properly applied XB signals that information is contested and under review. A stale XB, or one that is never removed, can create underwriting uncertainty or give the false impression that the furnisher has not completed its duties.
Conclusion
Report XB when a direct dispute is received, maintain accurate account-level fields during the investigation, and promptly update or remove the CCC when the investigation concludes. Use DF only when fraud is confirmed. Strong internal controls around dispute lifecycle timing (when XB is applied, when it is removed, and what corrections accompany resolution) reduce repeat disputes and support defensible FCRA compliance.