Consumer complaint received 2022-04-22
Product: Credit reporting, credit repair services, or other personal consumer reports — Credit reporting
Issue: Incorrect information on your report — Account information incorrect
Company: EQUIFAX, INC. (NJ)

I am XXXX XXXX, and I am the author of this complaint. There are no additional parties involved in either the creation of this complaint, nor its contents. 

This is not a Validation of Debt Request- please don't reply with such details/attachments. 

Please do not dismiss this as such. Doing so is traceable and discoverable. 

Know- this is systematic, impacting a class of consumers. 

All of your accounts are a part of this dispute, and are in the same exact state. Please do not dismiss this as one - tradeline issue. 

First things first - I hereby dispute the FCRA date, and on all of your reported records on my consumer reports. Where you report - the dates are inaccurate, and - can not match. XXXX - XXXX are included in this complaint. 

XXXX XXXX XXXX ( XXXX ) is a Debt Collector. XXXX is not a Creditor/Credit Grantor, either by practice or by law. There is a clear delineation of these two types of entities. 

FTC - Legal Definition is found within the link below, and pasted for your convenience. 

Section 803-4,6 https : //www.ftc.gov/legal-library/browse/rules/fair-debt-collection-practices-act-text Understanding the separation, there are innate responsibilities a Creditor/Credit Grantor, or Debt Collector has in furnishing their data and to any CRA. 

All CRAs require consumer credit data to be submitted in ONE file format. That Format, is Metro2 ( CDIA ), links below - specifically direct DFs to publish files to a CRA in this format. 

https : //www.equifax.com/business/data-furnishers/consumer/ XXXX XXXX XXXX XXXX XXXX XXXX XXXX FormatRequirements The Metro2 File Specification, is called the Credit Reporting Resource Guide.

I have attached - the Directives ( file specification ), from this guide that governs your data furnishing responsibilities, and as a Debt Collector.

10.1 A Debt Collector leverages the same Portfolio Type - as a Creditor/Credit Grantor The Portfolio Type is = Other Debt Collectors however, are limited to about 19 fields for a Consumers record XXXX - Routinely, sends more than what is allowed by Metro2 PRAs Additional Data, Portfolio Type and repetition, create a false, misleading and fraudulent tradeline Terms, are never allowed by a Debt Collector on a Metro2 compliant file You are sending MONTHLY ( again ) Payment History - is never allowed on a Metro2 compliant file Pay Rating - is not allowed on a Metro2 compliant File XXXX is sending ( G ) Collection, every month, along with Balance History that can never apply XXXX is publishing this ( you have deleted - and then resent this, at least once ) Equifax - is then allowing you into section 5 Other Accounts This section, is for Creditors/Credit Grantors and even by their own description Your account also says - 'Closed '' Lacks a CLOSED DATE Lacks an Activity Designator Screen shots attached as Equifax 1** This can not be expected results, as any Tech team/forensic tech, could demonstrate its failure, and all of your files create the same data ( discoverable ) An actual Collection Account and then from Equifax - section 10, is also attached XXXX consumer reporting, results in their records establishing accounts as creditors, when its never ever possible to have this relationship with them The impact to a consumer score - is known Collections naturally age off on impact to consumer scores XXXX has anchored itself, to prevent any natural progression - ever, and while they reside on a consumers file PRAs tradeline is fraudulent, mimics a creditor and is knowingly published, monthly and to all CRAs FCRA - FDCPA, and other elements of governing law XXXX prohibit your reporting, tactics and impacts to the consumer. 

I forgot - I build interfaces regularly, and understand technical specs === plus i just love the data. 

Delete your fraudulent tradeline - know, if you delete it again - there are rules expected when you try to reinsert it.