Consumer complaint received 2021-07-14 00:00:00
Product: Credit reporting, credit repair services, or other personal consumer reports — Credit reporting
Issue: Incorrect information on your report — Account status incorrect
Company: EQUIFAX, INC.
State: NJ

Complaint narrative:
This is not a duplicate complaint, please do not flag this as such. 

I am XXXX XXXX, and I alone, am submitting this complaint. 

I am not willing to be the middleman in this issue, as it is ultimately between you as a XXXX XXXX XXXX XXXX - XXXX ) and the CRAs. 

XXXX  - XXXX, is the Tradeline The request is to fix your data and in compliance with Metro2 data standards, so the record in your system - produces itself in a file then sent to a consumer profile/report correctly or delete it. 

Please let this complaint, reiterate the Do not Contact request previously supplied to you, except and as allowed through this portal, and then the laws that govern them. 

This complaint, nor the previous one - was never a request to validate any alleged debt. Instead, it is and was based on this Data Furnisher ( XXXX - XXXX ) reporting inaccurate, incomplete and then misleading data intentionally - to CRA 's, and have failed to respond to the noted issues. 

The responsibility of a Data Furnisher, I am relying on is based on FCRA FDCPA and e- cfr. 

https : //www.ecfr.gov/cgi-bin/text-idx? XXXX & XXXX & XXXX & XXXX For the CRA 's - Its simply FCRA. 

XXXX Score Calculations are based on 5 elements of a Tradeline, or Tradelines existing in/on a consumers profile/report. I have attached the description from XXXX  as XXXX  XXXX Ingredients, the source. XXXX Scoring calculations, are not different for each CRA. 
Payment History Amount of Debt Length of Credit History Amount of New Credit Credit mix Understanding this by then sending data to a CRA, maliciously / intentionally / or ignorantly data, that should be known with forethought, validation and oversight / QA, as the result becomes almost unreasonable to me, and then industry, governance, legal and compliance expectations. It is not until missed payments, collections and the like occur does the data go so far south that one must question its intent. 

IT testing, when files are sent or built, are part of a typical SDLC where expected results are defined. XXXX  - XXXX is in acceptance of the demonstrative issues in this complaint, or any previous as their normal standard of delivery - and standards. 

I will also share what I have learned, painfully, for and to all consumers who see your entity on their report for this journey. 

Please Fix the tradeline so that the data collected from your systems, is produced in a file that is Metro2 compliant, sent to a CRA, and then as a Debt collector - or delete it. 
The Data exchange between the OC and the CRA with due diligence, and or discovery can and will flush this out. 

XXXX in theory verifies the true expected results XXXX is saying is acceptable. 

See attached, for specific complaint details. 

This complaint is based on FCRA and FDCPA. 

Metro2 guidelines are the standard. 

DOFD/FACRA Date, FCRA - accuracy in reporting, Charge off balances, Pay History - Balance History and Rating History - and false/malicious data - being reported on my tradelines at all 3 CRA 's They are included in this complaint.

Company response to consumer: Closed with explanation