Consumer complaint received 2025-03-03 00:00:00
Product: Credit reporting or other personal consumer reports — Credit reporting
Issue: Problem with a company's investigation into an existing problem — Their investigation did not fix an error on your report
Company: Experian Information Solutions Inc.
State: NJ

Complaint narrative:
Credit Report : Experian, Report Number XXXX I am filing this complaint against Experian due to inaccurate, incomplete, and unverifiable reporting of negative accounts on my credit report ( Report # XXXX, dated XX/XX/XXXX ), as well as Experians failure to conduct proper investigations into my disputes. Experians actions violate Metro 2 reporting standards ( XXXX Metro 2 Format for Credit Reporting ) and multiple provisions of the Fair Credit Reporting Act ( FCRA ) and Fair Debt Collection Practices Act ( FDCPA ), causing severe damage to my credit score and financial opportunities. Additionally, Experians history of sham investigations ( CFPB enforcement action, XX/XX/XXXX ) and their lack of meaningful investigation into my dispute exacerbate these violations. 

On XX/XX/XXXX, I reviewed my Experian credit report and identified several issues : incorrect personal information ( name and address ), unverifiable negative accounts, and a significant mismatch in payment history for one account. My legal name is XXXX XXXX, and my address is XXXX XXXXXXXX XXXX XXXX XXXX XXXX XXXX XXXXXXXX, as confirmed by my identification ( Social Security Number ending in XXXX ). However, Experian reports my name as both " XXXX XXXX '' ( ID # XXXX ) and " XXXX XXXX XXXX '' ( ID # XXXX ) in Field XXXX ( bytes XXXX ), with byte XXXX incorrectly showing " R '' instead of a space, and my address as XXXX XXXX XXXX, XXXXXXXX XXXX XXXXXXXX in Field XXXX ( bytes XXXX ), with incorrect bytes XXXX ( " XXXX " ) and bytes XXXX ( " XXXX '' ) that should be " XXXX M '' and " XXXX ". This violates Metro 2 XXXX ( consumer identification accuracy ) and 15 USC 1681e ( b ) ( FCRA accuracy ), suggesting a potential mixed file or identity theft. 

The report lists 11 accounts, with three marked as " Potentially Negative '' : XXXX XXXX XXXX ( Secured Loan ), XXXX XXXX ( Secured Card ), and XXXX XXXX XXXX ( Auto Loan ) . Below are the specific violations : 1. XXXX XXXX XXXX XXXX Metro 2 XXXX requires XXXX bytes of payment history in XXXX XXXX ( bytes XXXX ). Bytes XXXX are blank, despite the account being open since XX/XX/XXXX ( Field XXXX, bytes XXXX : " XXXX '' ) and {$50.00} past due ( Field XXXX, bytes XXXX : " XXXX '' ). Byte XXXX ( XX/XX/XXXX ) should be " XXXX '', and bytes XXXX ( XXXX XXXX ) should reflect statuses. 
- Metro 2 XXXX requires terms frequency in XXXX XXXX ( bytes XXXX ), but bytes XXXX are blank ( should be " M " ). 
- Metro 2 XXXX requires a past-due breakdown in XXXX XXXX ( bytes XXXX : " XXXX '' ), but no breakdown ( e.g., principal vs. fees ) is provided. 
- Metro 2 XXXX requires the highest balance in XXXX XXXX ( bytes XXXX ), but bytes XXXX are blank, despite an original balance of {$300.00} ( Field XXXX, bytes XXXX : " XXXX '' ). 
- These violations breach 15 USC 1681e ( b ) ( FCRA accuracy ). 

2. XXXX XXXX ( Secured Card, Acct # XXXX ) : - Metro 2 XXXX requires XXXX bytes of payment history in Field XXXX ( bytes XXXX ). Bytes XXXX are blank, despite the account being open from XX/XX/XXXX ( Field XXXX, bytes XXXX : " XXXX '' ) to XX/XX/XXXX ( XXXX XXXX, bytes XXXX : " XXXX '' ). 
- Metro 2 XXXX requires a " Potentially Negative '' flag to be supported by derogatory bytes. Field XXXX ( byte XXXX : " XXXX '' for paid/closed ) shows no derogatory status ( e.g., " XXXX '' for charge-off ), and XXXX XXXX lacks payment history delays, making the flag unverifiable. 
- Metro 2 XXXX requires terms in XXXX XXXX ( bytes XXXX ), but bytes XXXX are blank. 
- Metro 2 XXXX requires the date of last payment in XXXX XXXX ( bytes XXXX ), but bytes XXXX are blank. 
- These violations breach 15 USC 1681e ( b ). 

3. XXXX XXXX XXXX - Metro 2 XXXX requires accurate payment history in XXXX XXXX ( bytes XXXX ). Experian reports " XXXX '' in bytes XXXX ( XXXX XXXX ), " XXXX '' in byte XXXX ( XX/XX/XXXX ), and " XXXX '' in byte XXXX ( XX/XX/XXXX ), but my payment records show on-time payments in XXXX XXXX ( bytes XXXX should be " '' ), a payment in XX/XX/XXXX ( byte XXXX should be " '' or " XXXX '' ), and a payment in XX/XX/XXXX ( byte XXXX should be " XXXX '' ). This violates 15 USC 1681e ( b ). 
- Metro 2 XXXX requires a charge-off status ( " XXXX '' ) in Field XXXX ( byte XXXX ) if unpaid 120 days post-repossession. Byte XXXX shows " XXXX '' ( repossession ) since XX/XX/XXXX, but with {$7000.00} past due ( Field XXXX, bytes XXXX : " XXXX '' ) and no payments since, byte XXXX should be " XXXX '' as of XX/XX/XXXX. 
- Metro 2 XXXX requires a past-due breakdown in XXXX XXXX ( bytes XXXX ), but none is provided. 
- Metro 2 XXXX requires " XXXX '' ( statute expired ) in XXXX XXXX ( bytes XXXX ) if time-barred. The account opened XX/XX/XXXX ( Field XXXX, bytes XXXX : " XXXX '' ), with delinquencies from XX/XX/XXXX ( byte XXXX : " XXXX '' ). NJs 4-year statute ( UCC 2-725 ) suggests its time-barred as of XXXX XXXX XXXX are blank, violating 15 USC 1692e ( 8 ) ( FDCPA false reporting ). 
- Metro 2 XXXX requires the date of last payment in XXXX XXXX ( bytes XXXX ), but bytes XXXX are blank. 

Impact on Me : These inaccuracies have severely damaged my credit score, leading to denials of credit and loan applications. The incorrect name ( " XXXX XXXX XXXX '' ) and address ( XXXX XXXX XXXX ) suggest a mixed file or identity theft, causing emotional distress and fear of further financial harm. The XXXX XXXX payment history mismatch has falsely portrayed me as delinquent, costing me housing and employment opportunities. 

Attempts to Resolve : On XX/XX/XXXX, I sent a detailed dispute letter to Experian via certified mail, demanding a byte-by-byte investigation under 15 USC 1681i ( a ) ( 1 ) ( A ). I cited Metro 2 violations ( XXXX, XXXX, XXXX, XXXX, XXXX, XXXX ), USC laws ( 15 USC 1681e ( b ), 15 USC 1692e ( 8 ) ), and provided my payment history for XXXX XXXX, proving Experians reporting is incorrect. I also requested correction of my name and address and a mixed-file review. Experian has not responded, violating 15 USC 1681i ( a ) ( 6 ) ( 30-day investigation requirement ). Given Experians history of sham investigations ( CFPB enforcement action, XX/XX/XXXX ), where the CFPB found Experian systematically failed to investigate disputes, often closing them without review, I believe Experians lack of investigation here continues this pattern of noncompliance. 

Requested Resolution : I request that the CFPB investigate Experian for Metro 2 and FCRA/FDCPA violations, including their lack of investigation into my dispute, which aligns with their documented sham investigation practices. I demand immediate deletion of the negative accounts ( XXXX XXXX XXXX, XXXX XXXX XXXX XXXX XXXX XXXX ) , correction of my name to " XXXX XXXX XXXX and address to " XXXX XXXXXXXX XXXX XXXX XXXX XXXX XXXX XXXX '', and a full mixed-file review. I seek monetary compensation under 15 USC 1681n ( willful noncompliance ) for damages, including emotional distress and financial losses, and regulatory action against Experian for their ongoing noncompliance. 

Attachments : - Copy of Experian Credit Report ( Report # XXXX ) - Copy of Dispute Letter to Experian ( dated XX/XX/XXXX ) - Copies of Identification ( Social Security Card ) - XXXX XXXXXXXX Payment History Records I appreciate the CFPBs assistance in protecting my consumer rights.

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