Consumer complaint received 2025-02-28 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:
I am filing this complaint against Experian, XXXX XXXX XXXX ( XXXX ), and XXXX XXXX XXXX ( XXXX ) due to inaccurate, unverifiable, and harmful reporting of collection accounts on my Experian credit report ( Report # XXXX, dated XX/XX/XXXX ). These accounts, which I believe are reported by XXXX and XXXX, 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 significant damage to my credit score and financial opportunities. 

On XX/XX/XXXX, I reviewed my Experian credit report and discovered that it lists " 8 Accounts '' in the Base Segment Summary ( Field XXXX, bytes XXXX ), but only three accounts were detailed. The remaining five accounts, including what I believe to be collections reported by XXXX and XXXX, were not fully provided due to truncation of the report after PAGE6. I am aware that XXXX, a debt collector, and XXXX, a subprime auto lender, are reporting negative information ( e.g., delinquencies, charge-offs, collections ) that I dispute as inaccurate and unverifiable. Below are the specific issues : 1. XXXX XXXX XXXX ( XXXX ) Collection Account : - Missing Base Segment ( Metro 2 XXXX, Field XXXX, bytes XXXX ) : Metro 2 XXXX requires a Base Segment for each account ( Field XXXX, bytes XXXX : " XXXX '' ). TSIs Base Segment is missing, preventing me from verifying critical fields like Field XXXX ( Account Status, byte XXXX ) and Field XXXX ( Current Balance, bytes XXXX ). This violates 15 USC 1681e ( b ) ( FCRA accuracy ), as Experian failed to ensure complete reporting. 

- Original Creditor Byte Omission ( Metro 2 XXXX, Field XXXX, bytes XXXX ) : Metro 2 XXXX mandates that XXXX report the original creditors name ( bytes XXXX ). Without this information, I can not identify the debts origin, violating my right to transparency under 15 USC 1681g ( a ) ( 1 ) ( disclosure of file contents ). 

- Potential Time-Barred Debt ( Metro 2 XXXX, Field XXXX, bytes XXXX ) : If XXXX is reporting a debt beyond New Jerseys 4-year statute of limitations ( UCC 2-725 ), bytes XXXX must reflect " DA '' ( statute expired ). XXXX history of collecting time-barred debts without disclosure ( Massachusetts AG XXXX settlement ) suggests this omission, violating 15 USC 1692e ( 8 ) ( FDCPA false reporting ). 

- Unverified Debt Reporting : XXXX has a documented history of pursuing unverified debts ( CFPB XXXX action ), violating 15 USC 1681s-2 ( b ) ( furnisher duties ). Without byte-level validation ( e.g., Field XXXX, byte XXXX : potentially " 93 '' for collection ), this reporting is inaccurate. 

2. XXXX XXXX XXXX ( XXXX  ) Negative Account : - Missing Base Segment ( Metro 2 XXXX, Field XXXX, bytes XXXX ) : XXXX Base Segment is also missing, violating Metro 2 XXXX. I can not verify Field XXXX ( byte XXXX, potentially " 97 '' for charge-off ) or Field XXXX ( Amount Past Due, bytes XXXX ), breaching 15 USC 1681e ( b ). 

- Charge-Off Byte Accuracy ( Metro 2 XXXX, Field XXXX, byte XXXX ) : If XXXX reports a charge-off ( byte XXXX : " XXXX '' ), Metro 2 XXXX requires validation. Without proof of non-payment or debt validity, this byte is inaccurate, violating 15 USC 1681s-2 ( b ). 

- Time-Barred Debt Omission ( Metro 2 XXXX, Field XXXX, bytes XXXX ) : If the auto loan is beyond XXXX 4-year statute, bytes XXXX must reflect " DA ''. Failure to report this violates Metro 2 XXXX and 15 USC 1692e ( 8 ). 

- Past Due Byte Breakdown ( Metro 2 XXXX, Field XXXX, bytes XXXX ) : If XXXX reports a past-due amount ( e.g., {$2500.00}, bytes XXXX : " XXXX '' ), Metro 2 XXXX requires a breakdown ( e.g., principal vs. fees ). Without this, the reporting is incomplete. 

Impact on Me : These inaccurate accounts have severely damaged my credit score, leading to denials of credit and loan applications. The presence of unverified collections has caused emotional distress, as I fear identity theft or mixed-file issues ( noted by an Arizona address and phone number Ive never used ). My financial stability is at risk, and Ive lost opportunities to secure housing and employment due to these negative marks. 

Attempts to Resolve : On XX/XX/XXXX, I sent a detailed dispute letter to Experian via certified mail, demanding a byte-by-byte investigation of XXXX and XXXX accounts under 15 USC 1681i ( a ) ( 1 ) ( A ). I cited specific Metro 2 violations ( XXXX, XXXX, XXXX, XXXX ) and USC laws ( 15 USC 1681e ( b ), 15 USC 1692e ( 8 ) ), requesting deletion of unverifiable bytes and a XXXX Segment investigation ( CII codes " XXXX '' for XXXX, " XXXX '' for XXXX, byte XXXX ). I provided copies of my identification ( New Jersey Drivers License # XXXX XXXX XXXX XXXX and Social Security Card ) to verify my identity. As of today, Experian has not responded, violating 15 USC 1681i ( a ) ( 6 ) ( 30-day investigation requirement ). 

Attachments : - Copy of Experian Credit Report ( Report # XXXX ) - Copy of Dispute Letter to Experian ( dated XX/XX/XXXX ) - Copies of Identification ( New Jersey Drivers License, Social Security Card ) I appreciate the CFPBs assistance in resolving this matter and 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