Consumer complaint received 2024-12-15 00:00:00
Product: Credit reporting or other personal consumer reports — Credit reporting
Issue: Incorrect information on your report — Account status incorrect
Company: Experian Information Solutions Inc.
State: TX

Complaint narrative:
To Whom it Concerns, Currently, You are reporting inaccurate and incomplete data in regards to the below noted student loan account ( s ). I demand that you contact the Reporting Data Provider ( s ), as I have already done, and demand a validation of the debt ( of course they can't provide the statement at this time ). Since they can not or will not provide an itemized statement for the services, they are clearly in violation of the FCRA and FDCPA. Please full your investigation of this unproven to be physically verifiable, valid, accurate, timely, mine, nor attestably Metro 2 Compliant as is mandatory each one to lawfully report and remove it because the provider can not validate the facts you are reporting on my credit report. REMOVE the following suspect allegation ( XXXX ) immediately and permanently : Name ALSO KNOWN AS : XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX Experian XXXX - Name ALSO KNOWN AS : D XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX Page XXXX of XXXX XXXX XXXX XXXX XXXX XXXX XXXX ***************************************************************************************************** REMOVE the display reported Name ALSO KNOWN AS ( XXXX ) XXXX and XXXX XXXX and REQUISITE REPORTED CURRENT CORRECT COMPLETE Name ALSO KNOWN AS is XXXXX. 
I DO NOT AUTHORIZE you to retain nor report any not proven true correct valid and required reported personal identifier information that is not in exact agreement with my submitted FACTUALLY CORRECT CURRENT PERSONAL IDENTIFIERS as indicated. 
***************************************************************************************************** CURRENT ADDRESS : XXXX XXXX XXXX XXXX, TX XXXX XXXX XXXX XXXX XXXX, TX XXXX Date Updated : XX/XX/XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX TX XXXX Personal XXXX XXXX Experian XXXX XXXX CURRENT ADDRESS : XXXX XXXX XXXX XXXX XXXX, TX XXXX XXXX XXXX XXXX XXXX XXXX, TX XXXX XXXX Updated : XX/XX/XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX, TX XXXX XXXX ***************************************************************************************************** REMOVE the display reported CURRENT ADDRESS ( XXXX ) of XXXX XXXX XXXX XXXX, TX XXXX and XXXX XXXX XXXX XXXX, TX XXXX XXXX Updated : XX/XX/XXXX and XXXX XXXX XXXX XXXX XXXX XXXX, TX XXXX XXXX my REQUISITE REPORTED CURRENT CORRECT COMPLETE Current Address is XXXX XXXX XXXX XXXX XXXX. I DO NOT AUTHORIZE you to retain nor report any not proven true correct valid and required reported personal identifier information that is not in exact agreement with my submitted FACTUALLY CORRECT CURRENT PERSONAL IDENTIFIERS as indicated. 
***************************************************************************************************** PREVIOUS ADDRESS : XXXX XXXX XXXX XXXX, TX XXXX XXXX XXXX XXXX, TX XXXX XXXX XXXX XXXX XXXX, TX XXXX XXXX XXXX XXXX, TX XXXX Date Updated : XX/XX/XXXX XXXX XXXX XXXX XXXX XXXX TX XXXX XXXX XXXX XXXX XXXX TX XXXX Personal Information XXXX Experian XXXX - PREVIOUS ADDRESS : XXXX XXXX XXXX XXXX XXXX XXXX TX XXXX XXXX XXXX XXXX XXXX TX XXXX XXXX XXXX XXXX XXXX XXXX XXXX TX XXXX XXXX XXXX XXXX XXXX TX XXXX Date Updated : XX/XX/XXXX I XXXX XXXX XXXX XXXX XXXX TX XXXX XXXX XXXX XXXX XXXX TX XXXX I ***************************************************************************************************** REMOVE the display reported PREVIOUS ADDRESS ( XXXX ) of XXXX XXXX XXXX XXXX XXXX TX XXXX XXXX XXXX XXXX XXXX TX XXXX and XXXX XXXX XXXX XXXX XXXX TX XXXX XXXX XXXX XXXX XXXX TX XXXX Date Updated : XX/XX/XXXX a XXXX d XXXX XXXX XXXX XXXX XXXX TX XXXX XXXX XXXX XXXX XXXX TX XXXX as my REQUISITE REPORTED CURRENT CORRECT COMPLETE Current Address is XXXX XXXX XXXX XXXX XXXX. I DO NOT AUTHORIZE you to retain nor report any not proven true correct valid and required reported personal identifier information that is not in exact agreement with my submitted FACTUALLY CORRECT CURRENT PERSONAL IDENTIFIERS as indicated. 
***************************************************************************************************** EMPLOYER : XXXXDate Updated : XXXX Updated : XX/XX/XXXX XXXXDate Updated : XXXX Updated : XX/XX/XXXX XXXXDate Updated : XXXXXXXX XXXXDate Updated : XX/XX/XXXX Personal Information XXXX Experian XXXX XXXX EMPLOYER : XXXX XXXXDate Updated : XXXX Updated : XX/XX/XXXX XXXX XXXXDate Updated : XXXX Updated : XX/XX/XXXX XXXX XXXXDate Updated : XXXX XXXXDate Updated : XX/XX/XXXX XXXX ***************************************************************************************************** REMOVE the displayed reported EMPLOYER ( XXXX ) of XXXXDate Updated : XXXX Updated : XX/XX/XXXX a XXXX XXXX XXXXDate Updated : XXXX Updated : XX/XX/XXXX a XXXX XXXX XXXXDate Updated : XXXX XXXXDate Updated : XX/XX/XXXX as I do NOT HAVE any REQUISITE REPORTED CURRENT nor Page XXXX of XXXX XXXX XXXX PREVIOUS EMPLOYER ( XXXX ) XXXX DO NOT AUTHORIZE you to retain nor report any personal identifier data of which is not EACH of being VERIFIABLE, TRUE, CORRECT, COMPLETE, TIMELY, or elsewise documented VALIDATED, so do NOT! 
***************************************************************************************************** DATE OF BIRTH : XXXX XXXX XXXX XXXX XXXX XXXX Experian XXXX XXXX DATE OF BIRTH : .. XXXX .. XXXX .. XXXX.. 
***************************************************************************************************** REMOVE the display reported DATE OF BIRTH ( XXXX ) of XXXX and XXXX and XXXX as my REQUISITE REPORTED CURRENT CORRECT COMPLETE DATE OF BIRTH : is XX/XX/XXXX. I DO NOT AUTHORIZE you to retain nor report any not proven true correct valid and required reported personal identifier information that is not in exact agreement with my submitted FACTUALLY CORRECT CURRENT PERSONAL IDENTIFIERS as indicated. 
***************************************************************************************************** CREDITOR NAME XXXX XXXX XXXX INQUIRY DATE XX/XX/XXXX XXXX XXXX XXXX XXXX incredulous on XX/XX/XXXX is an unconfirmed inquiry, not as of yet proven to be with the necessary adequate and needed achieved lawful Permissible Purpose, and or is not factually true adherent as it is currently reported. Please REMOVE from reporting promptly! 
***************************************************************************************************** CREDITOR NAME XXXX XXXX XXXX XXXX INQUIRY DATE XX/XX/XXXX XXXX XXXX XXXX XXXX XXXX professed on XX/XX/XXXX is an unconfirmed inquiry, not as of yet proven to be with the necessary adequate and preconditioned achieved lawful Permissible Purpose, and or is not testimonial docile as it is currently reported. Please DISLODGE from reporting rapidly! 
***************************************************************************************************** ***************************************************************************************************** Please utilize the following KEY to explain markings on the images of below-shown items being contested : * means REQUIRED ALWAYS ^ Required If Applies ~Industry-Specific Required BSCF Base Segment Character Format HRCF Header Record XXXX XXXX Segment XXXX XXXX Segment XXXX XXXX Segment XXXX XXXX Segment XXXX XXXX Segment XXXX XXXX Segment XXXX XXXX Segment XXXX XXXX Segment TRCF Trailer Record HRPF Header Record Packed Format BSPF Base Segment Packed Format TRPF Trailer Record Packed Format XXXX Data Furnisher # XXXX XXXX Data Furnisher # XXXX T XXXX XXXX essentially stands for Not XXXX Translated within Cra/and or is Unknown F XXXX XXXX Experian XXXX Missing but Required Reported XXXX Potential XXXX XXXX Inconsistent XXXX Not Available or Deceptive Q Questionable-conditioned? Questionable Mathematically D Deviant from standards U Unconfirmed or Uncertified Compliant Attack + Do Not Attack XXXX Mixed XXXX XXXX XXXX XXXX XXXX XXXX XXXX FCRA Fair Credit Reporting Act ***************************************************************************************************** XXXX XXXX The currently reported XXXX XXXX with account number displayed as this information is NOT REPORTED on XXXX XXXX in this reported claim on my XXXX XXXX report, shown as this information is NOT REPORTED on Experian in this reported claim on my Experian report, and alleged as this information is NOT REPORTED on XXXX in this reported claim on my XXXX XXXX XXXX of XXXX report. Any inconsistency, incompleteness, inaccuracy, or omission of the reported item serves as a peculiarity from the mandatorily utilized reporting industrys own XXXX XXXX Data-filled Field Formatted reporting compliance standards, of which there can be NO DEVIATION without JEOPARDIZING THE INTEGRITY OF THE DATA ( see XXXX XXXX XXXX ) and as so is lawfully questionable until evident confirmation of all aspect ( XXXX ) of claim ( XXXX ) are factually true, correct, complete, timely, physically verifiable, and elsewise undeniably valid particularly if not certifiably compliant in full according to the abovementioned Metro XXXX formatted industry requirements. With that in mind, please consider the following suspect reported data fields alleged for this now contested reported item of injury : ***************************************************************************************************** XXXX The currently reported XXXX with account number displayed as this information is NOT REPORTED on XXXX XXXX in this reported claim on my XXXX XXXX report, shown as this information is NOT REPORTED on Experian in this reported claim on my Experian report, and alleged as this information is NOT REPORTED on XXXX in this reported claim on my XXXX report. Any inconsistency, incompleteness, inaccuracy, or omission of the reported item serves as a anomaly from the mandatorily utilized reporting industrys own XXXX XXXX Data-filled Field Formatted reporting compliance standards, of which there can be NO DEVIATION without JEOPARDIZING THE INTEGRITY OF THE DATA ( see XXXX XXXX XXXX ) and as so is lawfully questionable until evident confirmation of all aspect ( XXXX ) of claim ( XXXX ) are factually true, correct, complete, timely, physically verifiable, and elsewise undeniably valid particularly if not certifiably compliant in full according to the above-mentioned Metro XXXX formatted industry requirements. With that in mind, please consider the following suspect reported data fields alleged for this now contested reported item of injury : ***************************************************************************************************** XXXX XXXX XXXX The currently reported XXXX XXXX XXXXXXXX with account number displayed as this information is NOT REPORTED on XXXX XXXX in this reported claim on my XXXX XXXX report, shown as this information is NOT REPORTED on Experian in this reported claim on my Experian report, and alleged as this information is NOT REPORTED on XXXX in this reported claim on my XXXX report. Any inconsistency, incompleteness, inaccuracy, or omission of the reported item serves as a deflection from the mandatorily utilized reporting industrys own Metro 2 Data-filled Field Formatted reporting compliance standards, of which there can be NO DEVIATION without JEOPARDIZING THE INTEGRITY OF THE DATA ( see CDIA CRRG 3-4 ) and as so is lawfully questionable until evident confirmation of all aspect ( s ) of claim ( s ) are factually true, correct, complete, timely, physically verifiable, and elsewise undeniably valid particularly if not certifiably compliant in full according to the abovementioned Metro 2 formatted industry requirements. With that in mind, please consider the following suspect reported data fields alleged for this now contested reported item of injury : ***************************************************************************************************** XXXX The currently reported XXXX  with account number displayed as this information is NOT REPORTED on XXXX XXXX in this reported claim on my XXXX XXXX report, shown as this Page XXXX of XXXX information is NOT REPORTED on Experian in this reported claim on my Experian report, and alleged as this information is NOT REPORTED on XXXX in this reported claim on my XXXX report. Any inconsistency, incompleteness, inaccuracy, or omission of the reported item serves as a deviation from the mandatorily utilized reporting industrys own Metro 2 Data-filled Field Formatted reporting compliance standards, of which there can be NO DEVIATION without JEOPARDIZING THE INTEGRITY OF THE DATA ( see CDIA CRRG 3-4 ) and as so is lawfully questionable until evident confirmation of all aspect ( s ) of claim ( s ) are factually true, correct, complete, timely, physically verifiable, and elsewise undeniably valid particularly if not certifiably compliant in full according to the abovementioned Metro 2 formatted industry requirements. With that in mind, please consider the following suspect reported data fields alleged for this now contested reported item of injury : ***************************************************************************************************** XXXX XXXX XXXXXXXX XXXX XXXX The currently reported CREDIT COLL with account number displayed as this information is NOT REPORTED on XXXX XXXX in this reported claim on my XXXX XXXX report , shown as this information is NOT REPORTED on Experian in this reported claim on my Experian report, and alleged as this information is NOT REPORTED on XXXX in this reported claim on my XXXX report. Any inconsistency, incompleteness, inaccuracy, or omission of the reported item serves as a discrepancy from the mandatorily utilized reporting industrys own Metro 2 Data-filled Field Formatted reporting compliance standards, of which there can be NO DEVIATION without JEOPARDIZING THE INTEGRITY OF THE DATA ( see CDIA CRRG 3-4 ) and as so is lawfully questionable until evident confirmation of all aspect ( s ) of claim ( s ) are factually true, correct, complete, timely, physically verifiable, and elsewise undeniably valid particularly if not certifiably compliant in full according to the abovementioned Metro 2 formatted industry requirements. With that in mind, please consider the following suspect reported data fields alleged for this now contested reported item of injury : ***************************************************************************************************** XXXX XXXX XXXX -- XXXX XXXX The currently reported XXXX XXXX XXXX with account number displayed as this information is NOT REPORTED on Trans Union XXXX this reported claim on my Trans Union report XXXX shown as this information is NOT REPORTED on Experian in this reported claim on my Experian report, and alleged as this information is NOT REPORTED on XXXX in this reported claim on my XXXX report XXXX Any inconsistency, incompleteness, inaccuracy, or omission of the reported item serves as a idiosyncrasy from the mandatorily utilized reporting industrys own Metro 2 Data-filled Field Formatted reporting compliance standards, of which there can be NO DEVIATION without JEOPARDIZING THE INTEGRITY OF THE DATA ( see CDIA CRRG 3-4 ) and as so is lawfully questionable until evident confirmation of all aspect ( s ) of claim ( s ) are factually true, correct, complete, timely, physically verifiable, and elsewise undeniably valid particularly if not certifiably compliant in full according to the abovementioned Metro 2 formatted industry requirements. With that in mind, please consider the following suspect reported data fields alleged for this now contested reported item of injury : ***************************************************************************************************** XXXX XXXX XXXX -- XXXX XXXX Page XXXX of XXXX The currently reported XXXX XXXX XXXX with account number displayed as this information is NOT REPORTED on Trans Union XXXX this reported claim on my Trans Union report XXXX shown as this information is NOT REPORTED on Experian in this reported claim on my Experian report, and alleged as this information is NOT REPORTED on XXXX in this reported claim on my XXXX report XXXX Any inconsistency, incompleteness, inaccuracy, or omission of the reported item serves as a idiosyncrasy from the mandatorily utilized reporting industrys own Metro 2 Data-filled Field Formatted reporting compliance standards, of which there can be NO DEVIATION without JEOPARDIZING THE INTEGRITY OF THE DATA ( see CDIA CRRG 3-4 ) and as so is lawfully questionable until evident confirmation of all aspect ( s ) of claim ( s ) are factually true, correct, complete, timely, physically verifiable, and elsewise undeniably valid particularly if not certifiably compliant in full according to the abovementioned Metro 2 formatted industry requiremeXXXX. With that in mind, please consider the following suspect reported data fields alleged for this now contested reported item of injury : ***************************************************************************************************** Conforming to my state 's reporting regulations and the applicable federal guidelines for lawful and compliant reporting of consumer credit, it is unlawful to assume report-ability of any claim without physically verified proof of fullness of truth, completeness of accuracy, timeliness of validity and or certifiable compliant reporting else wise to include but not limited to the standards and mandates described or hinted at via the applicable FCRA and FDCPA laws much less the standard of compliant reporting of the documented perfect and intact Metro 2 Format compliance of reporting! Your accepted reporting is significantly questionable and unproven to be certainly correct, correct, entire, timely, validated and or else wise certified compliant as related to the mandates and standards of lawful reporting By means of the applicable aspects of the FCRA and FDCPA to include but not limited to the mandatorily perfect and total certified Metro 2 format reporting! As you surely have noted, this is a request under FCRA 611 ( a ) ( 7 ) for a description of the procedure used by your agency in providing all to the creditor associated with my earlier dispute of the validity of the described late payments from my credit file your bureau provided to me. To be more specific, based on FCRA 611 ( a ) ( 2 ) ( B ), you were required to forward all of the relevant provided by you to the creditor for their investigation of my dispute. 
After contacting the creditor I have been led to believe that THIS did not take place. This is a clear violation of the FCRA and the FCBA. 
This letter is your formal note to Cease and Desist ALL activities in regards to the REPORTING of the above titled XXXX XXXX account. As your firm is well aware I have LEGALLY exercised my rights by disputing the validity of this debt. I have in writing and by phone demanded that you provide proved validation to me regarding how this item 's payment and conditions were verified and rumored, instead you have IGNORED my demands and violated 15 U.S.C.A. 1692g ( b ) - REQUIREMENT to Complete a timely investigation. I attempted to notify your compliance department officer of record in regards to the breech of regulatory requirements in your investigative efforts. This declaration was subsequently ignored. Therefore I am demanding that you CEASE ALL activities. Including but not limited to the reporting of the Student Loan in question and any further backdating of documents or records related to the alleged VERIFICATION of this account. Please be advised if have also notified Federal Regulators ( Consumer Financial Protection Bureau ), and the original creditor and furnisher of this of YOUR implicit regulatory failure in this matter. I will not hesitate to bring suit against your firm in this matter as in the example of XXXX XXXX XXXX aka XXXX XXXX XXXX Sincerely,

Company public response: Company has responded to the consumer and the CFPB and chooses not to provide a public response
Company response to consumer: Closed with explanation