Consumer complaint received 2024-10-02
Product: Debt collection — Credit card debt
Issue: False statements or representation — Attempted to collect wrong amount
Company: WELLS FARGO & COMPANY (CA)

Subject : Request for Assistance in Removing Inaccurate Credit Report Information under FCRA XXXX XXXX XXXX XXXX XXXX Ca XXXX XXXX Dear CFPB, I am writing to formally request your assistance in addressing persistent and inaccurate credit reporting by XXXX XXXX XXXX XXXX to XXXX, XXXX, and XXXX regarding an account with Wells Fargo ( WFBNA CARD ). Despite multiple disputes filed over the past few years, this credit reporting agency continues to report conflicting, misleading, and erroneous information that has harmed my financial standing and violated my rights under the Fair Credit Reporting Act ( FCRA ). 

Inaccuracies and FCRA Violations The following inconsistencies appear in the reports provided by each agency, all of which violate 15 U.S. Code 1681a and related sections of the FCRA : Inconsistent Account Names : XXXX lists the account as WELLS FARGO CARD SER, while both XXXX and XXXX list it as WFBNA CARD. 
Violation : This inconsistency violates 15 U.S. Code 1681e ( b ), which requires credit reporting agencies to ensure maximum possible accuracy in their reports. The conflicting account names are likely to mislead potential lenders. 

Status Update Date : XXXX and XXXX both claim the status was last updated in XX/XX/XXXX, whereas XXXX lists the last update as XX/XX/XXXX. 
Violation : Reporting agencies must provide accurate and up-to-date information under 15 U.S. Code 1681e ( b ). The conflicting dates create confusion about the accounts current standing, negatively impacting my credit score. 

Number of Potentially Negative Months : XXXX reports XXXX potentially negative months, while XXXX lists 62.

Violation : This discrepancy violates 15 U.S. Code 1681e ( b ), as the number of negative months directly affects how lenders view my creditworthiness. 

Payment History : XXXX provides a detailed history of charge-offs, while XXXX lists partial data ( including " ND '' for No Data ), and XXXX offers XXXX payment history at all. 
Violation : This lack of consistent payment history across the three bureaus violates 15 U.S. Code 1681i ( a ) ( 1 ), which mandates credit agencies to reinvestigate and correct inaccuracies. The absence of complete information, especially after multiple disputes, shows noncompliance. 

Last Payment Date : XXXX lists the last payment date as XX/XX/XXXX, while XXXX and XXXX omit this crucial information. 
Violation : Under 15 U.S. Code 1681e ( b ), credit reports must provide accurate details like the last payment date. The omission of this information further undermines the accuracy of these reports.

Comments and Account Status : The comments provided on the account differ across the reports : XXXX says the account was " charged off '' and " closed by credit grantor, '' while XXXX says it was " closed at credit grantor 's request, '' and XXXX states it was " canceled by credit grantor. '' Violation : These conflicting comments violate 15 U.S. Code 1681e ( b ), which mandates accurate reporting. The discrepancies in the account status create confusion and misrepresent the actual condition of the account.

Erroneous Contact Information : The contact information across the reports shows another troubling inconsistency : XXXX lists XXXX XXXX XXXX XXXX with an address in XXXX XXXX, IA, and phone number ( XXXX ) XXXX. 
XXXX lists a XXXX XXXX XXXX XXXX, MN but provides an impossible phone number of ( XXXX ) XXXX, which is clearly erroneous and reflects the carelessness of the company in handling my information. 
XXXX also lists a XXXX, MN address but with a different phone number, ( XXXX ) XXXX. 
Violation : Providing incorrect contact information violates 15 U.S. Code 1681g, which mandates that consumers must be provided clear and accurate contact details for disputes. The ( XXXX ) XXXX number demonstrates the agencys lack of care in reporting critical information and further impedes my ability to resolve these issues.