Consumer complaint received 2025-09-02 00:00:00
Product: Credit reporting or other personal consumer reports — Credit reporting
Issue: Incorrect information on your report — Information belongs to someone else
Company: Experian Information Solutions Inc.
State: NC

Complaint narrative:
ntroduction I am filing this complaint because multiple accounts and inquiries appearing on my Experian and Equifax credit reports are inaccurate, misleading, and in violation of the Fair Credit Reporting Act ( FCRA ), Fair Debt Collection Practices Act ( FDCPA ), and Metro 2 compliance reporting standards. These errors have caused substantial harm to my creditworthiness and ability to obtain housing, transportation, and credit. Below is a detailed account of the violations. 

Accounts on Experian 1. XXXX XXXX XXXX XXXX Acct # XXXX Violation : Appears on both Experian and Equifax for the same XXXX XXXX debt, while another collector also reports a XXXX XXXX account. This is duplicate reporting, violating FCRA 607 ( b ) and FDCPA 807 ( 2 ) ( A ).

Additional Issue : The account appears to have been re-aged with a newer date, which is unlawful under FCRA 623 ( a ) ( 5 ).

2. XXXX  Acct # XXXX Violation : This account appears obsolete and potentially beyond the 7-year reporting limit under FCRA 605 ( a ). If still reported, it is unlawfully re-aged.

3. XXXX XXXX XXXX XXXX Acct # XXXX Violation : Reported with a different balance on Experian than on Equifax. Inconsistent reporting across bureaus violates FCRA 607 ( b ) ( maximum possible accuracy ).

4. XXXX XXXX XXXX Acct # XXXX Violation : Reported derogatory when this product is marketed as a credit-building tool. Misclassification violates FCRA 623 ( a ) ( 1 ) and Metro 2 standards.

5. XXXX XXXX Acct # XXXX Violation : Telecom accounts are often resold to collectors, but if XXXX and a collection agency are both reporting, this is double jeopardy reporting, violating FCRA 607 ( b ) and FDCPA 807. 


Accounts on Equifax 1. XXXX XXXX XXXX  Acct # XXXX Violation : XXXX XXXX debt also reported by XXXX XXXX XXXX. This is duplicate collection reporting, violating FCRA 607 ( b ) and FDCPA 807 ( 2 ) ( A ). 
2. XXXX XXXX XXXX XXXX  Acct # XXXX Violation : Duplicate reporting across bureaus and possible re-aging. Same as noted in Experian. 
3. XXXX XXXX Acct # XXXX Violation : Reports a {$0.00} balance but remains derogatory. Per Metro 2 guidelines, this should be marked Paid/Closed. Misleading reporting violates FCRA 623 ( a ) ( 1 ).

4. XXXX XXXX XXXX Acct # XXXX Violation : If the debt is past the statute of limitations in North Carolina, continuing to report is misleading regarding enforceability, violating FDCPA 807 ( 2 ) ( A ).

5. XXXX XXXX XXXX XXXX Acct # XXXX Violation : Balance is inconsistent with Experians reporting. Conflicting data makes the account unverifiable, violating FCRA 607 ( b ).

Inquiries on Equifax 1. US Department of Education Violation : I did not authorize this inquiry. Accessing my report without a permissible purpose violates FCRA 604 ( a ).

2. XXXX XXXX ( XX/XX/year> & XX/XX/year> ) Violation : As a debt collector, XXXX XXXX likely lacks permissible purpose to pull my report. These inquiries violate FCRA 604 ( a ) ( 3 ).

3. Multiple Auto Finance Inquiries ( XXXX XXXX, XXXX XXXX, XXXX & XXXX XXXX, XXXX XXXX XXXX, XXXX XXXX ) Violation : These were made within a short time frame and should be counted as rate shopping inquiries. Reporting them individually artificially lowers scores and violates FCRA 607 ( b ).

Summary of Harms The above reporting practices are causing : Lowered credit scores from duplicate reporting and balance inconsistencies.

Extended derogatory history from re-aged accounts.

Damaging score impact from unauthorized inquiries.

Misrepresentation of account statuses under Metro 2 guidelines. I already tried reporting these negative items to the credit bureaus but no resolution

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