Consumer complaint received 2025-11-24 00:00:00
Product: Credit reporting or other personal consumer reports — Credit reporting
Issue: Incorrect information on your report — Account information incorrect
Company: LEXISNEXIS
State: CA

Complaint narrative:
I. EXHIBIT XXXX REVEALS A SYSTEMIC FAILURE ONLY POSSIBLE WHEN LEXISNEXIS IDENTITY GRAPH COLLAPSES Exhibit XXXX is an internal XXXX  backend page containing non-consumer-visible dispute codes, routing logic, identity-cluster references, and automated decision signatures. 

This one page exposes a catastrophic multi-CRA contamination event that can originate only from the entity that supplies identity, public-records, SSN clusters, and bankruptcy linkages to all CRAs : LexisNexis Risk Solutions XXXX 

The page includes repeated backend flags : THE DISPUTED ITEM IS NOT CURRENTLY REPORTING ON THE XXXX  CREDIT FILE. 

Yet XXXX  still processed disputes, still routed investigations, and still produced results proving a procedural impossibility unless the CRA was receiving contradictory or corrupted source data from LexisNexis. 

XXXX. THE INTERNAL DISPUTE CODES ON EXHIBIT XXXX PROVE WILLFUL MISREPORTING AND IDENTITY CONTAMINATION BY LEXISNEXIS Exhibit XXXX includes multiple internal S-codes and routing signatures : H Historical/Closed Applied even though LN was still furnishing active tradeline identifiers. 

XXXX Collection/Charge-Off Classification Despite IRS 1099-C income classification and no ownership chain. 

G Dispute Not Supported This confirms that the dispute result was decided before investigation an FCRA 1681i violation. 

J Bankruptcy/Judgment Flag The smoking gun. 
This proves LexisNexis injected bankruptcy contamination into my identity file, despite all four NDCA petitions being dismissed and despite PACER-certified records having been provided.

K Permanently Deleted This confirms identity fragmentation : some internal nodes show deletion while consumer-facing data still shows the accounts. 

These S-codes only appear when a consumer file is splintered into multiple identity sub-graphs caused by defective data supplied by the identity-provider LexisNexis. 

XXXX. THE IDENTITY CLUSTER NAMES PROVE MIXED-FILE CORRUPTION CAUSED BY LEXISNEXIS Exhibit XXXX displays multiple backend identity-routing signatures including : Name : XXXX Name : XXXX Name : XXXX  XXXX Name : XXXX XXXX XXXX Name : XXXX  These are not names they are internal LN/CRA identity-graph nodes generated when the upstream identity provider ( LexisNexis ) furnishes inconsistent or mismatched : SSN headers name/alias pairs bankruptcy identifiers address histories public-record linkages This is direct proof of a mixed-file event and a failure of LexisNexis identity-resolution system, in violation of : FCRA 1681e ( b ) CCRAA 1785.14 ( a ) Cal. Civ. Code 1798.93 ( identity theft classification ) IV. LEXISNEXIS VERIFIED ACCURATE LETTER IS NOW PROVEN FALSE BY EXHIBIT XXXX LexisNexis sent me a letter stating : Our investigation has determined your bankruptcy record to be accurate. 


Exhibit XXXX now proves : XXXX  internally flagged J ( bankruptcy ) without any valid PACER match multiple accounts were not currently reporting but still processed my identity file split across multiple routing nodes bankruptcy contamination persisted despite legal dismissals. 

This establishes : Willful misrepresentation under 15 U.S.C. 1681n Failure to correct inaccurate public records under 1681i and CCRAA 1785.25 ( a ) Failure of identity verification controls under 1681b It also reflects reckless disregard for the accuracy requirements in FCRA 607 ( b ). 

V. EXHIBIT XXXX + Multi-CRA Conflicts = A CFPB SENTINEL NETWORK EVENT Exhibit XXXX conclusively ties together : XXXX  deletions XXXX public-record sourcing conflict Equifax backend corruption LexisNexis identity-graph failure Furnisher misrouting Incorrect bankruptcy coding IRS 1099-C inconsistencies StudentAid.gov contradictions Fraudulent verified results This satisfies multiple CFPB Sentinel escalation triggers : 1. Cross-bureau identity inconsistency 2. Cross-bureau bankruptcy contradiction 3. Systemic furnisher verification failures 4. Consumer unable to verify identity due to LN contamination 5. Downstream harm affecting all three CRAs simultaneously 6. Public-record misreporting originating from LexisNexis 7 . Federal-level discrepancies ( IRS & DOE ) This is the textbook definition of a system-wide data integrity breakdown and qualifies for immediate Sentinel escalation, mandatory supervisory examination, and cross-agency referral. 

VI. SUPPLEMENTAL RELIEF REQUESTED Because Exhibit XXXX constitutes direct proof of multi-system contamination by LexisNexis, XXXX request : 1. Immediate Sentinel Network escalation 2. Supervisory examination of LexisNexis Risk Solutions under CFPB authority 3. Deletion of all LexisNexis-sourced identity, public-record, and bankruptcy data 4. Audit of all public-record sourcing, PACER data pulls, and bankruptcy matching logic 5. Full identity-graph reconstruction XXXX. Cross-agency referral to XXXX, SEC Structured Finance , FTC Sentinel , and CA XXXX XXXX. Penalties for willful violations under FCRA 1681n and CCRAA 1785.25 ( a ) SUPPLEMENTAL INFORMATION EXHIBIT XXXX ( Critical New Evidence ) : This filing supplements my existing complaint with newly identified evidence ( Exhibit XXXX ) that was included in the XXXX Settlement Notice already mailed to LexisNexis. Exhibit XXXX contains internal LexisNexis/CRA furnisher-classification codes ( including the sequential scan ID, account-tier routing markers, and recycled/legacy bankruptcy-petition misclassification flags ) that directly contradict the data LexisNexis has been supplying to Equifax, TransUnion, and Experian. These codes prove that LexisNexis internally retained and propagated inaccurate petition counts and obsolete furnisher segments even after receiving : ( 1 ) IRS-verified 1099-C acceptance for XXXX, XXXX, and XXXX, ( XXXX ) federal deletion events in StudentAid.gov, and ( 3 ) multiple CFPB complaints establishing identity-theft contamination of my consumer file. This page alone demonstrates that LexisNexis maintained shadow-tier bankruptcy indicators, incorrect petition lineage, and derogatory stabilization codes that were never disclosed to me and never correcteddespite being legally required under 15 U.S.C. 1681e ( b ), 1681i, 1681s-2, 12 C.F.R. Part 1022, and Californias Civ. Code 1785.10, 1785.14, 1785.16. 

I am requesting that CFPB treat this as a formal Sentinel Network enhancement trigger, because Exhibit XXXX indicates an active systemic furnisher failure, improper internal classification of deleted federal loan data, and false petition propagation that has already caused material harm ( credit denials, account closures, and regulatory inconsistencies ). This supplemental evidence is being added to ensure full supervisory review and to prevent further dissemination of inaccurate or unlawful data by LexisNexis. 

XXXX. STATEMENT OF TRUTH Exhibit XXXX was submitted as part of my 7-Day Settlement Notice to LexisNexis via XXXX and is incorporated here as critical evidence of systemic misconduct. 

Everything in this supplemental statement is true, accurate, and supported by documentation. 

Respectfully submitted, XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX

Company response to consumer: Closed with non-monetary relief