Consumer complaint received 2025-05-23 00:00:00
Product: Credit reporting or other personal consumer reports — Credit reporting
Issue: Improper use of your report — Reporting company used your report improperly
Company: Experian Information Solutions Inc.
State: LA

Complaint narrative:
Invalid and Inaccurate Reporting XXXX XXXX XXXX ( Collection on Equifax ) I am submitting this complaint regarding a collection account being reported on my Equifax credit report for the original creditor XXXX XXXX XXXX. The reporting contains several violations of the Fair Credit Reporting Act ( FCRA ) and the Fair Debt Collection Practices Act ( FDCPA ). 

Specifically : The account shows a " Date Opened '' and " Date Last Active '' in the future ( XX/XX/XXXX and XX/XX/XXXX ), which is impossible and violates FCRA XXXX ( b ). 

The balance equals the high credit, with no supporting detail or history to validate charges. 

There is no payment history, making it impossible to verify this debts origin or activity. 

The comment subject has not satisfied debt is ambiguous and misleading, violating FDCPA XXXX. 

I have not received validation of this debt, nor does the timeline make sense. I request the Consumer Financial Protection Bureau investigate this matter, and if the account can not be verified accurately and legally, I request its complete removal from my credit report. 

Thank you for your time and consideration. 

FCRA & FDCPA VIOLATIONS * XXXX. Impossible Timeline Date Opened & Last Active in the Future Date Opened : XX/XX/XXXX Last Active : XX/XX/XXXX Last Reported : XX/XX/XXXX Were currently in XX/XX/XXXX, so this timeline makes no sense. It suggests the account was opened and closed before it ever existed a violation of : * FCRA XXXX ( b ) Data must be accurate and timely. 

* FCRA XXXX ( a ) ( XXXX ) ( A ) Can not furnish knowingly inaccurate info. 

* XXXX. Balance = High Credit = {$1500.00} The balance should never be exactly the same as high credit in a collection without further breakdown ( fees, interest, etc. ). 

Raises red flags under FCRA XXXX ( b ). 

* XXXX. No Payment History There is no supporting payment history, which makes it difficult to validate this debt. 

* FCRA XXXX ( a ) ( XXXX ) Consumers are entitled to a full account history. 

* FDCPA XXXX ( b ) Debt collectors must verify the debt upon request and provide full details. 

* XXXX. Subject has not satisfied debt Ambiguous and Misleading Comment This vague phrasing may mislead lenders into believing legal action or garnishment is active. 

* FDCPA XXXX ( XXXX ) False implication of legal consequences. 

* FCRA XXXX ( a ) ( XXXX ) Unverified or outdated status. 


This Equifax-only tradeline may be : A duplicate of an earlier XXXX, XXXX, XXXX related medical collection with different labeling. 

Re-aged or assigned to another collector with a different name, but same balance or origin. 

Clue : Balance of {$1500.00} and collection/charge-off status from XXXX shows no meaningful activity history just a name swap or date push. 

- LAWS THAT PROTECT AGAINST DUPLICATE REPORTING - FCRA XXXX ( b ) Maximum Possible Accuracy Credit reporting agencies must ensure that the information in a consumers file is as accurate and up-to-date as possible. 

If the same debt is listed twice under XXXX different names or re-aged to look newer, that violates this section. 

- FCRA XXXX ( a ) ( XXXX ) Accurate Date of First Delinquency A furnisher must report the original date of delinquency accurately. 
If an account is re-aged ( i.e., new Date Opened in XXXX when the real delinquency started years ago ), it illegally extends the reporting life of the debt. 

- FDCPA XXXX ( XXXX ) ( A ) False Representation of Legal Status It is a violation to misrepresent the character, amount, or legal status of any debt. 
Reporting the same debt under a new agency name without removing the original is a deceptive collection tactic.

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