Consumer complaint received 2022-04-06
Company: EOS Holdings, Inc.
State: NJ
Product: Credit reporting, credit repair services, or other personal consumer reports
Sub-product: Credit reporting
Issue: Incorrect information on your report
Sub-issue: Account status incorrect

Complaint:
EOS - CCA I am XXXX XXXX, and I am the author of this complaint. No one is representing me for this issue, I just love XXXX XXXX. 

Please do not dismiss this, then - as such. 

Please let this dispute also serve as a DO NOT CONTACT notice, except for and then where allowed by law. 

This complaint is discoverable. 

First things first - The DOFD/FACRA date is wholly inaccurate on all reports, I don't have any XXXX account XXXX that went delinquent in XXXX. Additionally - its reported in the XXXX, with different dates. 

This complaint shall also serve as a validation of debt, and request to prove you - purchased this debt from someone/thing and as accurate. 

I have been in contact with your offices, and have spoken to at least 6 people, and all of them based outside of the US, the latest communication was yesterday.

None are familiar with US compliance issues, and specific to your reporting to a XXXX, or the XXXX  's. 

This complaint is specific - and, because the issues are well defined in FCRA and FDCPA. 


1. You, EOS - CCA, are a debt collector.

2. You are not a Credit Grantor 3. Legal Descriptive of the difference, can be found here - https : //www.ftc.govXXXX XXXX  XXXX ( 803 - Definitions section ) Understanding who you are, then - starting with what you then are governed to do, there are issues.

Because you are a Debt Collector - and as a Data Furnisher to XXXX  You are then expected to be in compliance The Data you store in your systems - is expected to be sent in an industry wide file/integration format That Format is XXXX See attached- where this the governance is expressed XXXX XXXX XXXX Reporting Requirements XXXX can only accept data in XXXX XXXX format*. Data providers must send data electronically in XXXX XXXX formatrequires XXXX XXXX for formatting. ( For more information on the XXXX XXXX format, please visit XXXX. 
Then - because the XXXX file is specific- you, as a Debt Collector, are then instructed/governed/mandated on which values you can actually send to a XXXX  XXXX XXXX XXXX XXXX - Rules, and then Your Data The Debt Collector Section - of the XXXX XXXX  XXXX, is attached This section - is dedicated to organization that function as you do every day This complaint has nothing to do with Header/Footer records- unless, this company is falsely self identifying itself as a Credit Grantor There are approx = 18 fields a Debt Collector can send - this does not fields for K segment details You- are sending much, much more - and as if you are a Credit Grantor There are no terms with a Debt Collector You are reporting M No such contract exists with your company You are then reporting this as in collections- with a 120- 150 past due value You are not authorized to create, report or publish such a value You are sending a payment rating - that too is not allowed Payment History - is on your file as well Your tradeline - looks like a Credit Grantors, and as if it is 120 days, late every month, and since you inserted it. 

If I am aware of the impact to scoring - you, XXXX XXXX- must know as well. 

Please remove this fraudulent entry. The penalties are more than the alleged debt. 

DEBT BUYER/THIRD PARTY COLLECTION AGENCY REPORTING GUIDELINES CREDIT REPORTING RESOURCE GUIDE 10-8 17. The following Base Segment fields are not applicable : Cycle Identifier ( Field 6 ) blank fill Credit Limit ( Field 11 ) zero fill Terms Frequency ( Field 14 ) blank fill Scheduled Monthly Payment Amount ( Field 15 ) zero fill Payment Rating ( Field 17B ) blank fill Payment History Profile ( Field 18 ) blank fill Experian Definition of a collection - what it should look like, https : //www.experian.com/blogs/ask-experian/credit-education/report-basics/understanding-your-experian-credit-report/ See attached EX -COLL

Company response to consumer: Closed with explanation