Consumer complaint received 2025-05-07 00:00:00
Product: Credit reporting or other personal consumer reports — Credit reporting
Issue: Incorrect information on your report — Account status incorrect
Company: Experian Information Solutions Inc.
State: TX

Complaint narrative:
* Subject : Formal Dispute and Request for Removal of Inaccurate Collection Account ( Account # XXXXXXXX XXXX XXXX XXXX  To Whom It May Concern : I am writing to formally dispute the validity of the collection account listed under my name ( Account # XXXX ) and request its immediate removal from my credit report. The account, reported by your agency, violates Metro 2 Credit Reporting Standards and the Fair Credit Reporting Act ( FCRA ) due to multiple inaccuracies and procedural errors. Below are the discrepancies identified : 1. * * Future Dates * * : - The " Date Opened '' ( XX/XX/year> ), " Status Updated '' ( XX/XX/year> ), and " Balance Updated '' ( XX/XX/year> ) are all future dates. Reporting hypothetical or projected dates is prohibited under Metro 2 guidelines. 

2. * * Premature Collection Reporting * * : - The account is labeled as a " Collection account '' in XX/XX/year> but claims a delinquency in XXXX 2025. This timeline is illogical, as collections can not precede the delinquency date. 

3. * * Missing Payment History * * : - No payment history or collection activity ( e.g., " Placed for collection '' ) is provided, violating Metro 2 requirements for transparency.

4. * * Incomplete/Inaccurate Fields * * : - " Highest Balance, '' " Recent Payment, '' and " Monthly Payment '' fields are blank or improperly marked.

- The " On Record Until '' date ( XX/XX/year> ) does not align with the 7-year reporting period mandated for collections.

5. * * Irrelevant Terms * * : - The " Terms '' field ( 1 Month ) is irrelevant to a collection account and misleading. 

Additionally, your agency is not the original creditor, and I have not received validation of this debt as required under the FDCPA. I demand proof of your legal authority to collect and report this account, including : - A copy of the original creditors agreement assigning this debt to your agency.

- Documentation verifying the debts amount and my liability.

* * Request for Action * * : - Immediately delete this account from all credit bureaus to which you reported it.

- Provide written confirmation of the deletion within 30 days. 

If you fail to respond or correct these inaccuracies, I will escalate this matter to the Consumer Financial Protection Bureau ( CFPB ), Federal Trade Commission ( FTC ), and state regulators.

Identified Discrepancies by Metro 2 Standard 1. Account Number Reported Data : XXXX : Blank Experian : Partially masked ( XXXXXXXX XXXX XXXX XXXX XXXX ) XXXX  : Blank Discrepancy : The account number is not consistently reported across all bureaus. Experian provides a partially masked number, while XXXX and XXXX  leave it blank. 
Metro 2 Reference : Field 2 - Account Number Explanation : Metro 2 requires consistent reporting of account identifiers to ensure accurate tracking and matching of accounts across bureaus. The absence or inconsistency can lead to identification issues.

2. Account Type Reported Data : XXXX : Not specified Experian : Collection Equifax : Collection Discrepancy : XXXX does not specify the account type, while Experian and XXXX  report it as Collection. 
Metro 2 Reference : Field 5 - Account Type Explanation : Metro 2 mandates uniform reporting of the account type across all bureaus. The omission on XXXX violates this requirement and may affect categorization and scoring.

3. Bureau Code Reported Data : XXXX : Not specified Experian : Individual XXXX : Not specified Discrepancy : Experian reports Individual, while XXXX and XXXX leave this field blank. 
Metro 2 Reference : Field 4 - Consumer Information Indicator Explanation : This field should be consistently populated ( e.g., I for Individual ) across all bureaus per Metro 2 standards. The inconsistency could confuse the accounts ownership or type. 
4. Account Status Reported Data : XXXX : Not specified Experian : Derogatory XXXX : Not specified Discrepancy : Experian reports Derogatory, while TransUnion and XXXX do not provide a status. 
Metro 2 Reference : Field 13 - Payment Status Explanation : Metro 2 requires the current payment status to be reported consistently. Missing data on XXXX XXXX XXXX  misrepresents the accounts standing. 
5. Monthly Payment Reported Data : XXXX XXXX Not specified ( assumed dash based on context ) Experian : Dash ( - ) XXXX : Dash ( - ) Discrepancy : All bureaus report a dash ( - ) instead of {$0.00} for a collection account with no payment plan. 
Metro 2 Reference : Field 16 - Scheduled Monthly Payment Amount Explanation : Metro 2 specifies reporting {$0.00} for collection accounts with no scheduled payments, not a dash. This is a minor formatting issue but deviates from the standard. 
6. Date Opened Reported Data : XXXX : Not specified Experian : XX/XX/year> XXXX XXXX Not specified Discrepancy : Experian reports a future date ( XX/XX/year> ), illogical for a report dated XX/XX/year>, while XXXX XXXX XXXX leave it blank. 
Metro 2 Reference : Field 7 - Date of Account Information Explanation : Metro 2 requires a valid past or present date. A future date is invalid, and blank fields on TXXXX XXXX XXXX indicate incomplete reporting. 
7. Balance Reported Data : XXXX : Not specified Experian : {$790.00} XXXX : {$790.00} Discrepancy : XXXX does not report a balance, while Experian and XXXX report {$790.00}. 
Metro 2 Reference : Field 69- Current Balance Explanation : Metro 2 requires consistent balance reporting across all bureaus. The omission on XXXX could affect perceived debt load. 
8. No. of Months ( Terms ) Reported Data : XXXX  : Not specified ( assumed dash based on context ) Experian : Dash ( - XXXX XXXX XXXX Dash ( - ) Discrepancy : All bureaus report a dash ( - ) instead of 0 for a collection account with no terms.

Metro 2 Reference : Field 18 - Terms Duration Explanation : Metro 2 recommends reporting 0 when terms are inapplicable, not a dash. This is a minor discrepancy but should align with the standard. 
9. High Credit Reported Data : XXXXXXXX XXXX  Not specified Experian : {$790.00} XXXX XXXX {$790.00} Discrepancy : XXXX lacks high credit data, while Experian and XXXX report {$790.00}. 
Metro 2 Reference : Field 66 - High Credit Explanation : Metro 2 requires this field to be populated ( typically the highest balance or original amount ). Missing data on XXXX could impact credit utilization calculations.

10. Past Due Reported Data : XXXX : Not specified ( assumed dash based on context ) Experian : Dash ( - ) XXXX XXXX Dash ( - ) Discrepancy : All bureaus report a dash ( - ) instead of {$0.00} for the past due amount.

Metro 2 Reference : Field 65 - Amount Past Due Explanation : Metro 2 requires reporting the past due amount or {$0.00} if none, not a dash. This is a minor formatting issue. 
11. Payment Status Reported Data : XXXX XXXX Not specified Experian : Collection/Chargeoff XXXX XXXX Not specified Discrepancy : Experian reports Collection/Chargeoff, while XXXX XXXX XXXX leave this blank XXXX 
Metro 2 Reference : Field 13 - Payment Status Explanation : Metro 2 mandates consistent payment status reporting. The omission on XXXX  and XXXX  could confuse the accounts delinquency status. 
12. Last Reported Reported Data : XXXXn : Not specified Experian : XX/XX/year>XXXX XXXX XXXX Not specified Discrepancy : Experian reports a future date ( XX/XX/year> ), inconsistent with the report date, while TransUnion and XXXX  leave it blank. 
Metro 2 Reference : Field 9 - Date of Last Activity Explanation : Metro 2 requires a valid past or present date. A future date is invalid, and blank fields indicate incomplete reporting. 
13. Comments Reported Data : XXXX  : Not specified Experian : Customer disputed account - reported by subscriber XXXX  : Not specified Discrepancy : Experian includes a dispute comment, while XXXX XXXX XXXX do not. 
Metro 2 Reference : Field 10 - Consumer Dispute Indicator Explanation : Metro 2 requires consistent reporting of dispute indicators. Missing information on XXXX XXXX XXXX could affect dispute resolution processes. 
14. Date Last Active Reported Data : XXXX XXXX Not specified Experian : XX/XX/year>XXXX XXXX : Not specified Discrepancy : Experian reports a future date ( XX/XX/year> ), illogical for the report date, while XXXX XXXX XXXX  leave it blank. 
Metro 2 Reference : Field 9 - Date of Last Activity Explanation : Metro 2 requires a valid date. A future date is invalid, and blank fields indicate incomplete data. 
15. Two-Year Payment History Reported Data : XXXX XXXX XXXX for all months Experian : Blank XXXX  : Blank Discrepancy : TransUnion reports XXXX consistently across all months ( likely an error ), while Experian and XXXX report blank. 
Metro 2 Reference : Field 14 - Payment History Profile Explanation : Metro 2 requires accurate payment history or a clear indication of no activity ( e.g., B for blank ). The 25 entries are likely erroneous and do not align with standard codes, while blank fields on Experian and XXXX are consistent with no history but should align with XXXX intent. 

Summary Table of Discrepancies

Company public response: Company has responded to the consumer and the CFPB and chooses not to provide a public response
Company response to consumer: Closed with explanation