Consumer complaint received 2025-11-06 00:00:00
Product: Credit reporting or other personal consumer reports — Credit reporting
Issue: Incorrect information on your report — Public record information inaccurate
Company: LCI Acquisition Inc.
State: AL

Complaint narrative:
I am submitting this complaint because XXXX, LCI, and the three major credit bureaus have collectively engaged in unlawful reporting and redistribution of unverifiable bankruptcy data that does not originate from any court-certified source. The record being reported as Federal Bankruptcy Case # XXXX ( filed XX/XX/XXXX ) appears differently across all repositories, confirming that it is not verifiable, not uniform, and not lawfully sourced. 

XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXXXX/XX/XXXX U.S. Bankruptcy Court These conflicting entries violate FCRA 607 ( b ) ( failure to maintain maximum possible accuracy ) and Metro2 Section 6.3, which mandates identical field reporting across all consumer repositories. 

Evidence of Systemic Noncompliance 1. XXXX Admission ( CFPB Case # XXXX ) XXXX confirmed in its official CFPB response that it does not receive bankruptcy data directly from the U.S. Bankruptcy Court , but instead pulls information from PACER, a public access system. The company admitted it cross-matches consumers to bankruptcy cases using address and SSN fragments, not certified records. 

XXXX obtains data from PACER, not the U.S. Bankruptcy Court PACER is not a government data furnisher but a public access platform. 

This means XXXX is a secondary reseller, not an authorized data furnisher, and therefore can not lawfully verify bankruptcy records under FCRA 611 ( a ) or 623 ( a ) ( 1 ) ( A ). 

2. LCI Admission ( CFPB Case # XXXX ) Lundquist Consulting Inc. , the vendor feeding bankruptcy data to XXXX, admitted it has no verification authority and does not validate or authenticate any information it provides. 
In its CFPB response, LCI stated : LCI does not have the ability to change, amend, or delete court record information LCI provides bankruptcy information to XXXX for inclusion in its sole discretion. 

LCI further acknowledged that it only distributes publicly available bankruptcy information and relies entirely on court record aggregationnot original certification. 
This confirms that TransUnions verification was based on unverified secondary data, violating : FCRA 623 ( a ) ( 1 ) ( A ) : Furnishing information known or expected to be inaccurate FCRA 604 : No permissible purpose for publishing unverifiable public data FCRA 611 ( a ) ( 1 ) : Failure to perform a reasonable reinvestigation 3. Credit Bureau Accountability Despite receiving multiple disputes and supporting documentation proving XXXX and LCIs lack of authority, XXXX XXXX XXXX XXXX XXXX XXXX continue to report inconsistent versions of the same record. 
This constitutes : FCRA 607 ( b ) : Failure to maintain maximum possible accuracy FCRA 611 ( a ) : Failure to reinvestigate with verifiable evidence Metro2 Section 6.16.3 : Failure to ensure data uniformity across bureaus These CRAs have knowingly relied on secondary vendors in violation of CFPBs XXXX Consent Orders, which explicitly prohibit the use of unverified third-party public record vendors for bankruptcy data. 

Legal Violations and Basis for CFPB Enforcement XXXX : Violated FCRA 604, 607 ( b ), 611 ( a ), 623 ( a ) ( 1 ) ( A ) by reselling unverifiable data and failing to ensure maximum accuracy. 

LCI : Violated FCRA 607 ( b ) and 623 ( a ) ( 1 ) ( A ) by furnishing unverified, inconsistent data to TransUnion. 

Credit Bureaus : Violated FCRA 607 ( b ), 611 ( a ), and CFPB Consent Orders by continuing to publish and verify non-source data. 

All parties participated in a circular verification process XXXX and LCI supplied PACER data to the CRAs, who then confirmed the same unverifiable data back to the vendors creating a self-reinforcing loop of inaccuracies with no original verification.

Company response to consumer: Closed with explanation