{"took":179,"timed_out":false,"_shards":{"total":5,"successful":5,"skipped":0,"failed":0},"hits":{"total":{"value":68,"relation":"eq"},"max_score":null,"hits":[{"_index":"complaint-public-v1","_id":"16538117","_score":29.043777,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Upon reviewing my credit report, I have identified specific Metro 2 compliance violations related to this account. The following data fields are either inaccurate, incomplete, or unverifiable under FCRA 1681i and Metro 2 standards : These include, but may not be limited to Accounts in Dispute : 1. Dept OF EDXXXX Account # XXXX Specifically - Failure to report the required Compliance Condition Code XB while account is under active consumer dispute - The Account Status Metro 2 Base 17A compliance violation - Current Balance Metro Base 12 compliance violation - Terms Metro 2 Base 13 compliance violations- Last Payment Date Metro 2 Base 17 compliance violation - Special Comment Metro 2 Base 19 compliance violation - Reporting Summary Metro 2 Base 18 compliance violation - K4/3 Segment Mero 2 compliance violation This complaint is a formal dispute under the Fair Credit Reporting Act ( FCRA ), 15 USC 1681, and a demand for Experian immediate investigation and correction or removal of inaccurate and unverifiable information currently being reported by your bureau. This request is also in reference to compliance with Metro 2 data reporting standards as prescribed by the XXXX XXXX XXXX XXXX ( XXXX ). \n\nI am disputing the accuracy, completeness, and verifiability of the following accounts appearing on my XXXX credit report. Which strongly suggests non-compliance and data inconsistency, violating Metro 2 formatting and FCRA requirements for accurate, consistent, and verifiable reporting. \nInconsistencies and unverifiable data of this nature fail to meet the required standards outlined in the Metro 2 Format and violate FCRA 1681e ( b ), which mandates data furnishers to ensure maximum possible accuracy. Furthermore, continued reporting of unverifiable or incorrect data after notice of dispute constitutes willful noncompliance, subject to civil liability under FCRA 1681n.","date_sent_to_company":"2025-10-13T21:13:14.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"30318","tags":null,"has_narrative":true,"complaint_id":"16538117","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-10-13T21:02:49.000Z","state":"GA","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Reporting company used your report improperly"},"highlight":{"complaint_what_happened":["Dept OF EDXXXX Account # XXXX Specifically - Failure to report the required <em>Compliance</em> Condition Code XB while account is under active consumer dispute - The Account Status <em>Metro</em> 2 <em>Base</em> 17A <em>compliance</em> <em>violation</em> - Current Balance <em>Metro</em> <em>Base</em> 12 <em>compliance</em> <em>violation</em> - Terms <em>Metro</em> 2 <em>Base</em> 13 <em>compliance</em> <em>violations</em>- Last Payment Date <em>Metro</em> 2 <em>Base</em> 17 <em>compliance</em> <em>violation</em> - <em>Special</em> Comment <em>Metro</em> 2 <em>Base</em> 19 <em>compliance</em> <em>violation</em> - Reporting Summary <em>Metro</em> 2 <em>Base</em> 18 <em>compliance</em> <em>violation</em> - K4/3 Segment Mero 2 <em>compliance</em>"]},"sort":[29.043777,"16538117"]},{"_index":"complaint-public-v1","_id":"16536763","_score":28.57724,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Upon reviewing my credit report, I have identified specific Metro 2 compliance violations related to this account. The following data fields are either inaccurate, incomplete, or unverifiable under FCRA 1681i and Metro 2 standards : These include, but may not be limited to : Accounts in Dispute : XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX Specifically, - Failure to report the required Compliance Condition Code XB while account is under active consumer dispute - The Account Status Metro 2 Base 17A compliance violation - Current Balance Metro Base 12 compliance violation - Terms Metro 2 Base 13 compliance violations- Last Payment Date Metro 2 Base 17 compliance violation - Special Comment Metro 2 Base 19 compliance violation - Reporting Summary Metro 2 Base 18 compliance violation - XXXX Segment Mero 2 compliance violation This complaint is a formal dispute under the Fair Credit Reporting Act ( FCRA ), 15 USC 1681, and a demand for Equifax immediate investigation and correction or removal of inaccurate and unverifiable information currently being reported by your bureau. This request is also in reference to compliance with Metro 2 data reporting standards as prescribed by the Consumer Data Industry Association ( CDIA ). \n\nAlso, I am disputing the accuracy, completeness, and verifiability of the following accounts appearing on my XXXX  credit report. Which strongly suggests non-compliance and data inconsistency, violating Metro 2 formatting and FCRA requirements for accurate, consistent, and verifiable reporting. \n\nInconsistencies and unverifiable data of this nature fail to meet the required standards outlined in the Metro 2 Format and violate FCRA 1681e ( b ), which mandates data furnishers to ensure maximum possible accuracy. Furthermore, continued reporting of unverifiable or incorrect data after notice of dispute constitutes willful noncompliance, subject to civil liability under FCRA 1681n.","date_sent_to_company":"2025-10-13T21:26:53.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"30318","tags":null,"has_narrative":true,"complaint_id":"16536763","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-10-13T21:19:35.000Z","state":"GA","company_public_response":null,"sub_issue":"Reporting company used your report improperly"},"highlight":{"complaint_what_happened":["<em>compliance</em> <em>violation</em> - Terms <em>Metro</em> 2 <em>Base</em> 13 <em>compliance</em> <em>violations</em>- Last Payment Date <em>Metro</em> 2 <em>Base</em> 17 <em>compliance</em> <em>violation</em> - <em>Special</em> Comment <em>Metro</em> 2 <em>Base</em> 19 <em>compliance</em> <em>violation</em> - Reporting Summary <em>Metro</em> 2 <em>Base</em> 18 <em>compliance</em> <em>violation</em> - XXXX Segment Mero 2 <em>compliance</em> <em>violation</em> This complaint is a formal dispute under the Fair Credit Reporting Act ( FCRA ), 15 USC 1681, and a demand for Equifax immediate investigation and correction or removal of inaccurate and unverifiable information currently"]},"sort":[28.57724,"16536763"]},{"_index":"complaint-public-v1","_id":"17116390","_score":28.24552,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Upon reviewing my credit report, I have identified specific Metro 2 compliance violations related to this account. The following data fields are either inaccurate, incomplete, or unverifiable under FCRA 1681i and Metro 2 standards : These include but may not be limited to Accounts in Dispute : 1. XXXX XXXX Account # XXXX XXXX. XXXX XXXX  Account # XXXX XXXX. XXXX XXXX XXXX Account # XXXX XXXX. XXXX  XXXX Account # XXXX Specifically - Failure to report the required Compliance Condition Code XB while account is under active consumer dispute - FCRA Compliance / Date of First Delinquency DOFD Metro 2 ( Base 25 ) compliance violation - The Account Status Metro 2 ( Base/17A ) compliance violation - Terms Duration Metro 2 ( Base/13 ) compliance violation - Portfolio Type Metro 2 ( Base/9 ) compliance violation - Date Open Metro 2 ( Base/10 ) compliance violation - Portfolio Type Metro 2 ( Base/8 ) compliance violation - Payment History Profile Metro 2 ( Field/18 ) compliance violation - Current Balance Metro 2 ( Base/12 ) compliance violation - ECOA Code Base/37 J1 & J2/10 - Last Payment Date Metro 2 ( Base/17 ) compliance violation - Special Comment Metro 2 ( Base/19 ) compliance violation - K1 Segment Metro 2 K1/3 - Re-Aging Issue the report DOFD has been unlawfully re-aged. This restarts the reporting period in violation of FXRA 605 ( c ) This complaint is a formal dispute under the Fair Credit Reporting Act ( FCRA ), 15 USC 1681, and a demand for Equifax immediate investigation and correction or removal of inaccurate and unverifiable information currently being reported by your bureau. This request is also in reference to compliance with Metro 2 data reporting standards as prescribed by the Consumer Data Industry Association ( CDIA ). I am disputing the accuracy, completeness, and verifiability of the following accounts appearing on my Equifax credit report. Which strongly suggests non-compliance and data inconsistency, violating Metro 2 formatting and FCRA requirements for accurate, consistent, and verifiable reporting. Inconsistencies and unverifiable data of this nature fail to meet the required standards outlined in the Metro 2 Format and violate FCRA 1681e ( b ), which mandates data furnishers to ensure maximum possible accuracy. Furthermore, continued reporting of unverifiable or incorrect data after notice of dispute constitutes willful noncompliance, subject to civil liability under FCRA 1681n.","date_sent_to_company":"2025-11-08T16:34:49.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"30135","tags":null,"has_narrative":true,"complaint_id":"17116390","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-11-08T16:16:46.000Z","state":"GA","company_public_response":null,"sub_issue":"Reporting company used your report improperly"},"highlight":{"complaint_what_happened":["/8 ) <em>compliance</em> <em>violation</em> - Payment History Profile <em>Metro</em> 2 ( Field/18 ) <em>compliance</em> <em>violation</em> - Current Balance <em>Metro</em> 2 ( <em>Base</em>/12 ) <em>compliance</em> <em>violation</em> - ECOA Code <em>Base</em>/37 J1 & J2/10 - Last Payment Date <em>Metro</em> 2 ( <em>Base</em>/17 ) <em>compliance</em> <em>violation</em> - <em>Special</em> Comment <em>Metro</em> 2 ( <em>Base</em>/19 ) <em>compliance</em> <em>violation</em> - K1 Segment <em>Metro</em> 2 K1/3 - Re-Aging Issue the report DOFD has been unlawfully re-aged."]},"sort":[28.24552,"17116390"]},{"_index":"complaint-public-v1","_id":"16602723","_score":28.097044,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Upon reviewing my credit report, I have identified specific Metro 2 compliance violations related to this account. The following data fields are either inaccurate, incomplete, or unverifiable under FCRA XXXX and Metro 2 standards : These include, but may not be limited to Accounts in Dispute : XXXX. XXXX XXXX Account XXXX XXXX XXXX. XXXX XXXX XXXX Account # XXXX XXXX. XXXX XXXX XXXX Account # XXXX XXXX XXXX XXXX XXXX Account # XXXX XXXX. XXXX XXXX XXXX Account # XXXX Specifically - Failure to report the required Compliance Condition Code XXXX  while account is under active consumer dispute - FCRA Compliance / Date of First Delinquency DOFD Metro 2 ( Base XXXX ) compliance violation - Portfolio Type Metro 2 ( Base XXXX ) compliance violation - Date Open Metro 2 ( Base XXXX ) compliance violation - Payment History Profile Metro 2 ( Field XXXX ) compliance violation - The Account Status Metro 2 Base XXXX compliance violation - Current Balance Metro 2 Base XXXX compliance violation - ECOA Code XXXX XXXX & XXXX - Last Payment Date Metro 2 Base XXXX compliance violation - Special Comment Metro 2 Base XXXX compliance violation - XXXX Segment Metro 2 XXXX - Re-Aging Issue the report DOFD has been unlawfully re-aged. This restarts the reporting period in violation of FXRA XXXX ( c ) - Medical Debt<XXXX  This is a medical collection reported within the 180 day grace period violating current credit reporting rules This complaint is a formal dispute under the Fair Credit Reporting Act ( FCRA ), 15 USC 1681, and a demand for TransUnion immediate investigation and correction or removal of inaccurate and unverifiable information currently being reported by your bureau. This request is also in reference to compliance with Metro 2 data reporting standards as prescribed by the XXXX XXXX XXXX XXXX ( XXXX ). \n\nI am disputing the accuracy, completeness, and verifiability of the following accounts appearing on my TransUnion credit report. Which strongly suggests non-compliance and data inconsistency, violating Metro 2 formatting and FCRA requirements for accurate, consistent, and verifiable reporting. \n\nInconsistencies and unverifiable data of this nature fail to meet the required standards outlined in the Metro 2 Format and violate FCRA XXXX ( b ), which mandates data furnishers to ensure maximum possible accuracy. Furthermore, continued reporting of unverifiable or incorrect data after notice of dispute constitutes willful noncompliance, subject to civil liability under FCRA XXXX.","date_sent_to_company":"2025-10-15T16:43:14.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"30135","tags":null,"has_narrative":true,"complaint_id":"16602723","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-10-15T16:35:50.000Z","state":"GA","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Information belongs to someone else"},"highlight":{"complaint_what_happened":["Balance <em>Metro</em> 2 <em>Base</em> XXXX <em>compliance</em> <em>violation</em> - ECOA Code XXXX XXXX & XXXX - Last Payment Date <em>Metro</em> 2 <em>Base</em> XXXX <em>compliance</em> <em>violation</em> - <em>Special</em> Comment <em>Metro</em> 2 <em>Base</em> XXXX <em>compliance</em> <em>violation</em> - XXXX Segment <em>Metro</em> 2 XXXX - Re-Aging Issue the report DOFD has been unlawfully re-aged."]},"sort":[28.097044,"16602723"]},{"_index":"complaint-public-v1","_id":"16602938","_score":27.754023,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Upon reviewing my credit report, I have identified specific Metro 2 compliance violations related to this account. The following data fields are either inaccurate, incomplete, or unverifiable under FCRA 1681i and Metro 2 standards : These include, but may not be limited to Accounts in Dispute : 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 XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX Specifically - Failure to report the required Compliance Condition Code XB while account is under active consumer dispute - FCRA Compliance / Date of First Delinquency DOFD Metro 2 ( Base XXXX ) compliance violation - Portfolio Type Metro 2 ( Base XXXX ) compliance violation - Date Open Metro XXXX ( Base XXXX ) compliance violation - Payment History Profile Metro 2 ( Field XXXX ) compliance violation - The Account Status XXXX XXXX Base XXXX compliance violation - Current Balance Metro 2 Base XXXX compliance violation - ECOA Code XXXX XXXX & XXXX - Last Payment Date Metro 2 Base XXXX XXXX violation - Special Comment Metro 2 Base XXXX XXXX violation - XXXX Segment XXXX XXXX XXXX - XXXX Issue the report DOFD has been unlawfully re-aged. This restarts the reporting period in violation of XXXX XXXX ( c ) - Medical XXXX This is a medical collection reported within the 180 day grace period violating current credit reporting rules This complaint is a formal dispute under the Fair Credit Reporting Act ( FCRA ), 15 USC 1681, and a demand for Equifax XXXX XXXX and correction or removal of inaccurate and unverifiable information currently being reported by your bureau. This request is also in reference to compliance with Metro 2 data reporting standards as prescribed by the XXXX XXXX XXXX XXXX ( XXXX ). \n\nI am disputing the accuracy, completeness, and verifiability of the following accounts appearing on my Experian credit report. Which strongly suggests non-compliance and data inconsistency, violating Metro 2 formatting and FCRA requirements for accurate, consistent, and verifiable reporting. \n\nInconsistencies and unverifiable data of this nature fail to meet the required standards outlined in the Metro 2 Format and violate FCRA 1681e ( b ), which mandates data furnishers to ensure maximum possible accuracy. Furthermore, continued reporting of unverifiable or incorrect data after notice of dispute constitutes willful noncompliance, subject to civil liability under FCRA 1681n.","date_sent_to_company":"2025-10-15T16:35:49.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"30135","tags":null,"has_narrative":true,"complaint_id":"16602938","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-10-15T16:28:10.000Z","state":"GA","company_public_response":null,"sub_issue":"Information belongs to someone else"},"highlight":{"complaint_what_happened":["First Delinquency DOFD <em>Metro</em> 2 ( <em>Base</em> XXXX ) <em>compliance</em> <em>violation</em> - Portfolio Type <em>Metro</em> 2 ( <em>Base</em> XXXX ) <em>compliance</em> <em>violation</em> - Date Open <em>Metro</em> XXXX ( <em>Base</em> XXXX ) <em>compliance</em> <em>violation</em> - Payment History Profile <em>Metro</em> 2 ( Field XXXX ) <em>compliance</em> <em>violation</em> - The Account Status XXXX XXXX <em>Base</em> XXXX <em>compliance</em> <em>violation</em> - Current Balance <em>Metro</em> 2 <em>Base</em> XXXX <em>compliance</em> <em>violation</em> - ECOA Code XXXX XXXX & XXXX - Last Payment Date <em>Metro</em> 2 <em>Base</em> XXXX XXXX <em>violation</em> - <em>Special</em> Comment <em>Metro</em> 2 <em>Base</em> XXXX XXXX <em>violation</em>"]},"sort":[27.754023,"16602938"]},{"_index":"complaint-public-v1","_id":"12962191","_score":22.22842,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX  FORMAL DISPUTE LETTER # # Medical Information Reporting & Metro 2 Format Violations XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXXXX/XX/year> Experian Dispute Department XXXX XXXX XXXX XXXX XXXX XXXX XXXXRE : Medical Data Reporting Violations - Account # : [ YOUR EXPERIAN FILE NUMBER ] ** To Whom It May Concern : I am writing to formally dispute improper disclosure of medical information on my consumer report maintained by Experian. This dispute is filed pursuant to the Fair Credit Reporting Act ( 15 U.S.C. 1681 et seq. ) and specifically addresses multiple Metro 2 Format violations as established by the XXXX XXXX XXXX XXXX ( XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \n\nAfter reviewing my Experian credit report, I have identified the following specific Metro 2 Format violations related to medical information : 1. **Improper Consumer Information Indicator ( CII ) Code Usage** : Metro 2 Format mandates the use of specific CII codes in positions 164-167 of the Base Segment for medical information. Specifically, code \" HB '' must be used to indicate accounts arising from the provision of medical services, products, or devices. Your report fails to properly code these accounts. \n\n2. **Non-Compliant Medical Information Disclosure** : Per FCRA Section 604 ( g ) and Metro 2 Format standards, medical information must be properly masked in furnisher name fields. Your notification states that \" Consumer statements included on your report at your request that contain medical information are disclosed to others, '' which directly violates Metro 2 requirements that ALL medical information should be masked with appropriate coding.\n\n3. **Improper Special Comment Code Implementation** : Metro 2 Format requires special comment codes in positions 391-410 for medical accounts, specifically using code \" CP '' ( medical collection ) for healthcare provider accounts in collection. Your report fails to properly apply these codes.\n\n4. **Absence of Required Identity Theft Indicator** : Medical information exposed without proper Metro 2 formatting presents heightened identity theft risks. Your report lacks the required Identity Theft indicator in positions 332-346 of the J2 Segment as required by Metro 2 Format when sensitive information is present.\n\n5. **Violation of Relationship Code Requirements** : Metro 2 Format requires specific ECOA Code designation in position 25 for medical debt, reflecting appropriate relationship attribution. Your report improperly assigns standard relationship codes to medical accounts. \n\nAs these violations constitute significant non-compliance with industry standards and federal law, I demand the following actions : 1. Immediate removal of all improperly formatted medical information from my consumer report 2. Full implementation of proper Metro 2 Format standards for any remaining medical information, including appropriate CII codes, Special Comment Codes, and Identity Theft indicators 3. Written confirmation of these corrections within 30 days as required by the FCRA 4. Provision of a corrected consumer report after your investigation is complete","date_sent_to_company":"2025-04-13T03:15:59.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"713XX","tags":null,"has_narrative":true,"complaint_id":"12962191","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-04-13T03:12:50.000Z","state":"LA","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Account information incorrect"},"highlight":{"complaint_what_happened":["As these <em>violations</em> constitute significant non-<em>compliance</em> with industry standards and federal law, I demand the following actions : 1. Immediate removal of all improperly formatted medical information from my consumer report 2. Full implementation of proper <em>Metro</em> 2 Format standards for any remaining medical information, including appropriate CII codes, <em>Special</em> Comment Codes, and Identity Theft indicators 3. Written confirmation of these corrections within 30 days as required by the FCRA 4."]},"sort":[22.22842,"12962191"]},{"_index":"complaint-public-v1","_id":"15908834","_score":22.056908,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"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 XXXX XXXX XXXX XXXXXX/XX/XXXX Experian Information Solutions , Inc . \nXXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX  am writing regarding systematic Metro 2 formatting violations and Fair Credit Reporting Act non-compliance related to the above-referenced account ( s ). My investigation has revealed material violations of industry standards and federal consumer protection law. \n\nI. METRO 2 CRRG FORMAT VIOLATIONS IDENTIFIED Your reporting contains the following technical violations of the Credit Reporting Resource Guide : 1. Base Segment Non-Compliance : Account Status Code [ X ] improperly maintained beyond charge-off date Missing Compliance Condition Code XB during dispute period Portfolio Type field misclassification affecting credit scoring 2. K1 Segment Omissions : Failure to include Special Comment Codes during dispute investigation Missing compliance condition markers required under EOSCAR standards 3. Data Element Inconsistencies : [ SPECIFIC FIELD VIOLATIONS WITH METRO 2 FIELD NUMBERS ] II. FCRA PROCEDURAL VIOLATIONS Your organization has violated the following FCRA provisions : 1681s-2 ( b ) - Furnisher Obligations : Failure to conduct reasonable reinvestigation upon notice of dispute Continued reporting of disputed information without proper investigation Inadequate review of consumer-provided documentation 1681i - Dispute Procedures : Investigation timeline exceeded statutory 30-day maximum Inadequate consumer notification of investigation results Failure to provide required consumer rights disclosures III. DAMAGES AND LIABILITY EXPOSURE These violations expose your organization to : Actual Damages : Credit denial, increased interest rates, employment consequences Statutory Damages : XXXX XXXXXXXX {$1000.00} per violation under 15 U.S.C. 1681n Punitive Damages : Willful non-compliance penalties Attorneys Fees : 15 U.S.C. 1681o costs and reasonable attorney fees Injunctive Relief : Court-ordered compliance procedures IV. DEMAND FOR CORRECTIVE ACTION IMMEDIATE REQUIREMENTS ( Within 10 Business Days ) : 1. Complete Account Deletion from all three credit reporting agencies 2. Written Confirmation of deletion with reference numbers 3. Internal System Correction to prevent future inaccurate reporting 4. Compliance Audit of Metro 2 formatting procedures ALTERNATIVE CORRECTIVE REPORTING ( If Account Verified ) : 1. Proper Metro 2 Formatting : Apply Compliance Condition Code XB if disputed Include appropriate K1 segment special comments Correct Account Status Code and Portfolio Type designation 2. FCRA Compliance Documentation : Provide complete investigation file Submit EOSCAR confirmation codes Include original creditor verification records V. SETTLEMENT OPPORTUNITY To resolve this matter without litigation, I demand : Monetary Compensation : $ [ AMOUNT ] for FCRA violations and credit damage Complete Account Deletion with confirmation letters Credit Monitoring Services for 12-month period Written Agreement preventing future reporting on this account VI. PRESERVATION NOTICE You are hereby notified to preserve all documents, electronic records, communications, and data related to this account and me, including but not limited to : Original creditor files and purchase documentation Internal investigation records and procedures EOSCAR/E-OSCAR system communications Employee training materials on Metro 2 compliance Audit records and compliance monitoring reports","date_sent_to_company":"2025-09-12T10:36:45.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"71457","tags":null,"has_narrative":true,"complaint_id":"15908834","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-09-12T10:36:16.000Z","state":"LA","company_public_response":null,"sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["<em>Base</em> Segment Non-<em>Compliance</em> : Account Status Code [ X ] improperly maintained beyond charge-off date Missing <em>Compliance</em> Condition Code XB during dispute period Portfolio Type field misclassification affecting credit scoring 2. K1 Segment Omissions : Failure to include <em>Special</em> Comment Codes during dispute investigation Missing <em>compliance</em> condition markers required under EOSCAR standards 3. Data Element Inconsistencies : [ SPECIFIC FIELD <em>VIOLATIONS</em> WITH <em>METRO</em> 2 FIELD NUMBERS ] II."]},"sort":[22.056908,"15908834"]},{"_index":"complaint-public-v1","_id":"15908833","_score":21.98162,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"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 XXXX XXXX XXXX XXXXXX/XX/XXXX Experian Information Solutions , Inc . \nXXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX  am writing regarding systematic Metro 2 formatting violations and Fair Credit Reporting Act non-compliance related to the above-referenced account ( s ). My investigation has revealed material violations of industry standards and federal consumer protection law. \n\nI. METRO 2 CRRG FORMAT VIOLATIONS IDENTIFIED Your reporting contains the following technical violations of the Credit Reporting Resource Guide : 1. Base Segment Non-Compliance : Account Status Code [ X ] improperly maintained beyond charge-off date Missing Compliance Condition Code XB during dispute period Portfolio Type field misclassification affecting credit scoring 2. K1 Segment Omissions : Failure to include Special Comment Codes during dispute investigation Missing compliance condition markers required under EOSCAR standards 3. Data Element Inconsistencies : [ SPECIFIC FIELD VIOLATIONS WITH METRO 2 FIELD NUMBERS ] II. FCRA PROCEDURAL VIOLATIONS Your organization has violated the following FCRA provisions : 1681s-2 ( b ) - Furnisher Obligations : Failure to conduct reasonable reinvestigation upon notice of dispute Continued reporting of disputed information without proper investigation Inadequate review of consumer-provided documentation 1681i - Dispute Procedures : Investigation timeline exceeded statutory 30-day maximum Inadequate consumer notification of investigation results Failure to provide required consumer rights disclosures III. DAMAGES AND LIABILITY EXPOSURE These violations expose your organization to : Actual Damages : Credit denial, increased interest rates, employment consequences Statutory Damages : XXXX XXXXXXXX {$1000.00} per violation under 15 U.S.C. 1681n Punitive Damages : Willful non-compliance penalties Attorneys Fees : 15 U.S.C. 1681o costs and reasonable attorney fees Injunctive Relief : Court-ordered compliance procedures IV. DEMAND FOR CORRECTIVE ACTION IMMEDIATE REQUIREMENTS ( Within 10 Business Days ) : 1. Complete Account Deletion from all three credit reporting agencies 2. Written Confirmation of deletion with reference numbers 3. Internal System Correction to prevent future inaccurate reporting 4. Compliance Audit of Metro 2 formatting procedures ALTERNATIVE CORRECTIVE REPORTING ( If Account Verified ) : 1. Proper Metro 2 Formatting : Apply Compliance Condition Code XB if disputed Include appropriate K1 segment special comments Correct Account Status Code and Portfolio Type designation 2. FCRA Compliance Documentation : Provide complete investigation file Submit EOSCAR confirmation codes Include original creditor verification records V. SETTLEMENT OPPORTUNITY To resolve this matter without litigation, I demand : Monetary Compensation : $ [ AMOUNT ] for FCRA violations and credit damage Complete Account Deletion with confirmation letters Credit Monitoring Services for 12-month period Written Agreement preventing future reporting on this account VI. PRESERVATION NOTICE You are hereby notified to preserve all documents, electronic records, communications, and data related to this account and me, including but not limited to : Original creditor files and purchase documentation Internal investigation records and procedures EOSCAR/E-OSCAR system communications Employee training materials on Metro 2 compliance Audit records and compliance monitoring reports","date_sent_to_company":"2025-09-12T10:36:45.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"71457","tags":null,"has_narrative":true,"complaint_id":"15908833","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-09-12T10:36:16.000Z","state":"LA","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["<em>Base</em> Segment Non-<em>Compliance</em> : Account Status Code [ X ] improperly maintained beyond charge-off date Missing <em>Compliance</em> Condition Code XB during dispute period Portfolio Type field misclassification affecting credit scoring 2. K1 Segment Omissions : Failure to include <em>Special</em> Comment Codes during dispute investigation Missing <em>compliance</em> condition markers required under EOSCAR standards 3. Data Element Inconsistencies : [ SPECIFIC FIELD <em>VIOLATIONS</em> WITH <em>METRO</em> 2 FIELD NUMBERS ] II."]},"sort":[21.98162,"15908833"]},{"_index":"complaint-public-v1","_id":"18296840","_score":20.564362,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"To the Consumer Financial Protection Bureau, I am submitting this formal complaint against Experian Information Solutions , Inc. for reporting multiple residential addresses that are inaccurate, unauthorized, and unverifiable, in direct violation of the Fair Credit Reporting Act ( FCRA ) and Metro 2 reporting standards. \n\nCorrect and Authorized Address : XXXX XXXX XXXX XXXX XXXX XXXX XXXX, NY XXXX Experian is currently reporting the following false addresses, none of which belong to me : XXXX XXXX XXXX XXXX, XXXX XXXX XXXX NY XXXX XXXX XXXX XXXX XXXX, XXXX XXXX XXXX NY XXXX XXXX XXXX XXXX XXXX XXXX, XXXX XXXX XXXX NY XXXX I have never resided at, received mail at, nor authorized the use of these addresses. \n\nLegal and Regulatory Violations : FCRA 607 ( b ) Failure to maintain reasonable procedures to assure maximum possible accuracy.\n\nFCRA 611 ( a ) ( 1 ) Failure to conduct a reasonable reinvestigation of disputed personal information.\n\nFCRA 623 ( a ) ( 1 ) & ( 3 ) Furnishing inaccurate information and failing to properly mark it as disputed. \n\nMetro 2 Violations including improper population of : Address Fields ( Base Segment Fields 3945 ), Address Indicator, Residence Code, Consumer Information Indicator, ECOA Code, while omitting mandatory Compliance Condition Codes and Special Comments during an active dispute. \n\nThese violations materially increase the risk of file contamination and mixed consumer files, resulting in ongoing harm.","date_sent_to_company":"2025-12-26T16:37:49.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"11372","tags":null,"has_narrative":true,"complaint_id":"18296840","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-12-26T16:23:55.000Z","state":"NY","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Personal information incorrect"},"highlight":{"complaint_what_happened":["<em>Metro</em> 2 <em>Violations</em> including improper population of : Address Fields ( <em>Base</em> Segment Fields 3945 ), Address Indicator, Residence Code, Consumer Information Indicator, ECOA Code, while omitting mandatory <em>Compliance</em> Condition Codes and <em>Special</em> Comments during an active dispute. \n\nThese <em>violations</em> materially increase the risk of file contamination and mixed consumer files, resulting in ongoing harm."]},"sort":[20.564362,"18296840"]},{"_index":"complaint-public-v1","_id":"12999633","_score":20.317667,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"COMPLAINT TO TRANSUNION VIA THE CONSUMER FINANCIAL PROTECTION BUREAU XXXX XXXX XXXXXXXX XXXX LA XXXX Date : XX/XX/XXXX To : TransUnion Consumer RelationsVia : XXXXonsumer Financial Protection BureauXXXX. XXXX XXXX XXXX, IA XXXX RE : URGENT - Metro 2 Format Violations & Fair Credit Reporting Abuses by XXXX  ( Account Last Reported XX/XX/XXXX ) To Whom It May Concern : I am filing this formal complaint to document critical and willful violations of credit reporting standards by XXXX. My comprehensive review has identified egregious technical violations of Metro 2 Format requirements that demonstrate a pattern of non-compliance with the Fair Credit Reporting Act ( FCRA ), Equal Credit Opportunity Act ( ECOA ), and Consumer Reporting Resource Guide ( CRRG ) standards. These violations constitute UNFAIR and DECEPTIVE practices that have materially damaged my credit profile, caused demonstrable harm, and systematically impeded my federally protected consumer rights. \nAccount Details ( Per Credit Report ) Collection Agency : XXXX Alleged Original Creditor : XXXX ( Same entity improperly listed twice ) Account Balance : {$1000.00} Account Opened : XX/XX/XXXX Last Reported : XX/XX/XXXX Status : Open/Placed for collection Consumer Dispute Status : Account information disputed by consumer ( Duplicated ) Specific Technical Metro 2 Format Violations Metro 2 Base Segment Violations 1. Segment Identifier Error ( Field 1 ) : XXXX has improperly coded the Base Segment Identifier by duplicating itself as both creditor and collection agency, violating Field XXXX technical specifications. \n2. Consumer Account Number ( XXXX XXXX  ) : The account identifiers are inconsistently applied between segments, evidenced by duplicate dispute reporting. \nXXXX. XXXX XXXX ( XXXX XXXX ) : No proper designation as specified in Metro 2 format requirements. \n4. Account Type ( XXXX XXXX ) : Completely missing value ( displayed as ), a critical mandatory field violation. \n5. Consumer Information Indicator ( XXXX XXXX ) : Improper coding as evidenced by the duplicate dispute remarks. \n6. Account XXXX ( XXXX XXXX ) : Incorrect status coding for an account under active dispute. \n7. Payment History Profile ( XXXX XXXX ) : Timeline inconsistencies suggesting improper retroactive reporting. \n8. Special Comment ( XXXX XXXX  ) : Failure to properly code disputed account status. \n9. Compliance Condition ( XXXX XXXX ) : Missing appropriate FCRA compliance codes. \n10. ECOA Code ( XXXX XXXX ) : Improperly coded during disputed status, violating ECOA requirements. \nAssociated Consumer Segment Violations 1. Consumer Dispute Information ( XXXX XXXXXXXX ) : Critical duplicate coding of disputed status demonstrates systemic Metro 2 formatting failures. \nXXXX XXXX XXXXt Relationship Error : XXXX has failed to properly distinguish collection agency vs. original creditor roles in the required XXXX segments. \nFCRA Section 605 ( a ) ( 5 ) Violations The account appears potentially re-aged based on date inconsistencies, potentially violating the 7-year reporting limitation. This constitutes a direct violation of Section 605 ( a ) ( 5 ) of the FCRA and demonstrates willful non-compliance.\n\nTechnical Access Barrier Evidence The persistent 411 Loading error preventing access to my account demonstrates systematic technological barriers to my federally protected rights to access and dispute information ( FCRA Section 609 ).\n\nFairness Impact Statement The technical violations detailed above demonstrate a pattern of unfair practices that directly harm me as a consumer in the following specific ways : 1. Credit Score Damage : These Metro 2 format violations have caused artificial reduction in my credit score through improper coding and duplicate negative reporting. \n2. Economic Hardship : These inaccuracies have directly resulted in denial of credit, increased interest rates, and reduced financial opportunities, causing quantifiable economic harm.\n\n3. Psychological Impact : The frustration and anxiety caused by being unable to access my own information ( 411 Loading error ) while negative information remains on my report constitutes emotional distress. \n4. Time Burden : I have spent countless hours attempting to resolve these issues, constituting a significant opportunity cost. \n5. Dispute Access Denial : The technical barriers prevent me from exercising my federally protected right to dispute inaccurate information.\n\nRequested Relief Based on the detailed technical Metro 2 format violations outlined above, I request the following specific remedies : 1. Immediate Removal : Complete deletion of the XXXX tradeline due to critical Metro 2 format violations rendering the entire reporting invalid. \n2. Statutory Damages : Payment of {$1000.00} per violation as provided under FCRA Section 616 for willful noncompliance, totaling {$10000.00} for the ten specific Metro 2 Format violations enumerated above. \n3. Civil Penalty Assessment : Investigation into pattern and practice violations under CFPB authority to assess civil penalties for willful non-compliance with XXXXetro 2 standards.\n\n4. Technical Compliance Audit : Full examination of XXXX Metro 2 compliance procedures and systems to identify systemic failures. \nXXXX. Restitution : Compensation for credit score damage, application denials, and increased interest costs directly resulting from these violations. \n6. Injunctive Relief : Order requiring XXXX to immediately fix technical barriers preventing account access. \nI have documented evidence of all violations cited, including screenshots of my credit report and the 411 Loading technical error. I stand ready to provide additional documentation supporting these claims.\n\nThe combination of technical Metro 2 violations, inaccurate reporting, and access barriers demonstrates a systematic disregard for consumer protection regulations that merits immediate and decisive enforcement action. \nRespectfully submitted, XXXX XXXX Enclosures : Credit report dated XX/XX/XXXX showing Metro 2 format violations Screenshots of 411 Loading technical access barrier Account statements showing dispute history cc : Federal Trade Commission ( FTC ) - Bureau of Consumer Protection National Credit Reporting Agencies ( XXXXXXXX XXXX, TransUnion ) Consumer Data Industry Association ( CDIA )- Metro 2 Format Standards Committee","date_sent_to_company":"2025-04-16T09:37:41.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"713XX","tags":null,"has_narrative":true,"complaint_id":"12999633","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-04-16T09:28:57.000Z","state":"LA","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Account status incorrect"},"highlight":{"complaint_what_happened":["<em>Special</em> Comment ( XXXX XXXX  ) : Failure to properly code disputed account status. \n9. <em>Compliance</em> Condition ( XXXX XXXX ) : Missing appropriate FCRA <em>compliance</em> codes. \n10. ECOA Code ( XXXX XXXX ) : Improperly coded during disputed status, <em>violating</em> ECOA requirements. \nAssociated Consumer Segment <em>Violations</em> 1. Consumer Dispute Information ( XXXX XXXXXXXX ) : Critical duplicate coding of disputed status demonstrates systemic <em>Metro</em> 2 formatting failures."]},"sort":[20.317667,"12999633"]},{"_index":"complaint-public-v1","_id":"16583670","_score":20.31738,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"CFPB / Metro 2Compliant Dispute & Complaint Consumer : XXXX XXXX XXXX Account : XXXX XXXX XXXX XXXX {$270.00} Subject : Inaccurate Late Payment Reporting / Metro 2 Compliance Violation Regulations Cited : 15 U.S.C. 1681s-2 ( b ) Duty to investigate and correct inaccurate information 15 U.S.C. 1681i Reinvestigation of disputed information 38 U.S.C. 5301 Protection of veterans benefits CDIA Metro 2 Format Standards ( Base Segment & Payment History Profile Fields ) Complaint Summary : I am filing this complaint because XXXX XXXX XXXX XXXX is reporting a {$270.00} account with an inaccurate late payment that does not comply with Metro 2 reporting standards. The payment history, status code, and date fields are not aligned with CDIAs Metro 2 Format, and the furnisher has failed to conduct a reasonable investigation as required under 15 U.S.C. 1681s-2 ( b ). \nThis inaccurate reporting continues to harm my credit profile and violates my rights under the Fair Credit Reporting Act ( FCRA ). Additionally, any portion of this alleged debt that involved veterans benefits is exempt from attachment, levy, or collection under 38 U.S.C. 5301.\n\nDispute Reason ( e-OSCAR AID Codes Embedded ) To ensure this dispute is read correctly by the automated e-OSCAR system, I am identifying the exact codes relevant to this dispute : Code Description 001 Not his/hers ( account does not belong to consumer ) 007 Claims paid account is reported as delinquent 103 Claims account information is inaccurate 112 Claims account is not past due 127 Disputes current payment status or payment history profile I am specifically asserting Code 007 and Code 127 the account was paid or current, and any reported delinquency or late payment is inaccurate under the Metro 2 Payment Rating field and Account Status field. \nRequest for Corrective Action : Conduct a reinvestigation consistent with 15 U.S.C. 1681s-2 ( b ) and 1681i, ensuring full compliance with Metro 2 fields : Base Segment Payment Rating Payment History Profile Account Status Special Comment Code Verify the accuracy of the Date of First Delinquency ( DOFD ) and ensure that no late payments are reported where no delinquency actually occurred. \nImmediately delete or correct the inaccurate tradeline if documentation can not verify accuracy. \nNotify all consumer reporting agencies ( Experian, Equifax, TransUnion ) within the 30-day reinvestigation period, pursuant to 15 U.S.C. 1681i ( a ) ( 5 ) ( A ).\n\nStatement for CFPB Review : I am a veteran, and this reporting interferes with protected federal benefits that are non-assignable and exempt from attachment under 38 U.S.C. 5301.\n\nI request CFPB oversight to ensure XXXX XXXX corrects or deletes the inaccurate data and that the credit bureaus comply with FCRA and Metro 2 standards.\n\nSupporting Documents : Metro 2compliant dispute letter ( attached ) Proof of veteran status Requested Resolution : Delete or correct the inaccurate late payment Confirm update to all CRAs within 30 days Provide written confirmation of compliance under FCRA 1681i ( a ) ( 6 )","date_sent_to_company":"2025-10-15T04:57:29.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"37040","tags":"Servicemember","has_narrative":true,"complaint_id":"16583670","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-10-15T04:45:28.000Z","state":"TN","company_public_response":null,"sub_issue":"Account information incorrect"},"highlight":{"complaint_what_happened":["CFPB / <em>Metro</em> 2Compliant Dispute & Complaint Consumer : XXXX XXXX XXXX Account : XXXX XXXX XXXX XXXX {$270.00} Subject : Inaccurate Late Payment Reporting / <em>Metro</em> 2 <em>Compliance</em> <em>Violation</em> Regulations Cited : 15 U.S.C. 1681s-2 ( b ) Duty to investigate and correct inaccurate information 15 U.S.C. 1681i Reinvestigation of disputed information 38 U.S.C. 5301 Protection of veterans benefits CDIA <em>Metro</em> 2 Format Standards ( <em>Base</em> Segment & Payment History Profile Fields ) Complaint Summary : I am filing this"]},"sort":[20.31738,"16583670"]},{"_index":"complaint-public-v1","_id":"16583776","_score":20.310219,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"CFPB / Metro 2Compliant Dispute & Complaint Consumer : XXXX XXXX XXXX Account : XXXX XXXX XXXX XXXX {$270.00} Subject : Inaccurate Late Payment Reporting / Metro 2 Compliance Violation Regulations Cited : 15 U.S.C. 1681s-2 ( b ) Duty to investigate and correct inaccurate information 15 U.S.C. 1681i Reinvestigation of disputed information 38 U.S.C. 5301 Protection of veterans benefits CDIA Metro 2 Format Standards ( Base Segment & Payment History Profile Fields ) Complaint Summary : I am filing this complaint because XXXX XXXX XXXX XXXX is reporting a {$270.00} account with an inaccurate late payment that does not comply with Metro 2 reporting standards. The payment history, status code, and date fields are not aligned with CDIAs Metro 2 Format, and the furnisher has failed to conduct a reasonable investigation as required under 15 U.S.C. 1681s-2 ( b ). \nThis inaccurate reporting continues to harm my credit profile and violates my rights under the Fair Credit Reporting Act ( FCRA ). Additionally, any portion of this alleged debt that involved veterans benefits is exempt from attachment, levy, or collection under 38 U.S.C. 5301.\n\nDispute Reason ( e-OSCAR AID Codes Embedded ) To ensure this dispute is read correctly by the automated e-OSCAR system, I am identifying the exact codes relevant to this dispute : Code Description 001 Not his/hers ( account does not belong to consumer ) 007 Claims paid account is reported as delinquent 103 Claims account information is inaccurate 112 Claims account is not past due 127 Disputes current payment status or payment history profile I am specifically asserting Code 007 and Code 127 the account was paid or current, and any reported delinquency or late payment is inaccurate under the Metro 2 Payment Rating field and Account Status field. \nRequest for Corrective Action : Conduct a reinvestigation consistent with 15 U.S.C. 1681s-2 ( b ) and 1681i, ensuring full compliance with Metro 2 fields : Base Segment Payment Rating Payment History Profile Account Status Special Comment Code Verify the accuracy of the Date of First Delinquency ( DOFD ) and ensure that no late payments are reported where no delinquency actually occurred. \nImmediately delete or correct the inaccurate tradeline if documentation can not verify accuracy. \nNotify all consumer reporting agencies ( Experian, Equifax, TransUnion ) within the 30-day reinvestigation period, pursuant to 15 U.S.C. 1681i ( a ) ( 5 ) ( A ).\n\nStatement for CFPB Review : I am a veteran, and this reporting interferes with protected federal benefits that are non-assignable and exempt from attachment under 38 U.S.C. 5301.\n\nI request CFPB oversight to ensure XXXX XXXX corrects or deletes the inaccurate data and that the credit bureaus comply with FCRA and Metro 2 standards.\n\nSupporting Documents : Metro 2compliant dispute letter ( attached ) Proof of veteran status Requested Resolution : Delete or correct the inaccurate late payment Confirm update to all CRAs within 30 days Provide written confirmation of compliance under FCRA 1681i ( a ) ( 6 )","date_sent_to_company":"2025-10-15T04:57:29.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"37040","tags":"Servicemember","has_narrative":true,"complaint_id":"16583776","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-10-15T04:57:03.000Z","state":"TN","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Account information incorrect"},"highlight":{"complaint_what_happened":["CFPB / <em>Metro</em> 2Compliant Dispute & Complaint Consumer : XXXX XXXX XXXX Account : XXXX XXXX XXXX XXXX {$270.00} Subject : Inaccurate Late Payment Reporting / <em>Metro</em> 2 <em>Compliance</em> <em>Violation</em> Regulations Cited : 15 U.S.C. 1681s-2 ( b ) Duty to investigate and correct inaccurate information 15 U.S.C. 1681i Reinvestigation of disputed information 38 U.S.C. 5301 Protection of veterans benefits CDIA <em>Metro</em> 2 Format Standards ( <em>Base</em> Segment & Payment History Profile Fields ) Complaint Summary : I am filing this"]},"sort":[20.310219,"16583776"]},{"_index":"complaint-public-v1","_id":"16583777","_score":20.247425,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"CFPB / Metro 2Compliant Dispute & Complaint Consumer : XXXX XXXX XXXX Account : XXXX XXXX XXXX XXXX {$270.00} Subject : Inaccurate Late Payment Reporting / Metro 2 Compliance Violation Regulations Cited : 15 U.S.C. 1681s-2 ( b ) Duty to investigate and correct inaccurate information 15 U.S.C. 1681i Reinvestigation of disputed information 38 U.S.C. 5301 Protection of veterans benefits CDIA Metro 2 Format Standards ( Base Segment & Payment History Profile Fields ) Complaint Summary : I am filing this complaint because XXXX XXXX XXXX XXXX is reporting a {$270.00} account with an inaccurate late payment that does not comply with Metro 2 reporting standards. The payment history, status code, and date fields are not aligned with CDIAs Metro 2 Format, and the furnisher has failed to conduct a reasonable investigation as required under 15 U.S.C. 1681s-2 ( b ). \nThis inaccurate reporting continues to harm my credit profile and violates my rights under the Fair Credit Reporting Act ( FCRA ). Additionally, any portion of this alleged debt that involved veterans benefits is exempt from attachment, levy, or collection under 38 U.S.C. 5301.\n\nDispute Reason ( e-OSCAR AID Codes Embedded ) To ensure this dispute is read correctly by the automated e-OSCAR system, I am identifying the exact codes relevant to this dispute : Code Description 001 Not his/hers ( account does not belong to consumer ) 007 Claims paid account is reported as delinquent 103 Claims account information is inaccurate 112 Claims account is not past due 127 Disputes current payment status or payment history profile I am specifically asserting Code 007 and Code 127 the account was paid or current, and any reported delinquency or late payment is inaccurate under the Metro 2 Payment Rating field and Account Status field. \nRequest for Corrective Action : Conduct a reinvestigation consistent with 15 U.S.C. 1681s-2 ( b ) and 1681i, ensuring full compliance with Metro 2 fields : Base Segment Payment Rating Payment History Profile Account Status Special Comment Code Verify the accuracy of the Date of First Delinquency ( DOFD ) and ensure that no late payments are reported where no delinquency actually occurred. \nImmediately delete or correct the inaccurate tradeline if documentation can not verify accuracy. \nNotify all consumer reporting agencies ( Experian, Equifax, TransUnion ) within the 30-day reinvestigation period, pursuant to 15 U.S.C. 1681i ( a ) ( 5 ) ( A ).\n\nStatement for CFPB Review : I am a veteran, and this reporting interferes with protected federal benefits that are non-assignable and exempt from attachment under 38 U.S.C. 5301.\n\nI request CFPB oversight to ensure XXXX XXXX corrects or deletes the inaccurate data and that the credit bureaus comply with FCRA and Metro 2 standards.\n\nSupporting Documents : Metro 2compliant dispute letter ( attached ) Proof of veteran status Requested Resolution : Delete or correct the inaccurate late payment Confirm update to all CRAs within 30 days Provide written confirmation of compliance under FCRA 1681i ( a ) ( 6 )","date_sent_to_company":"2025-10-15T04:57:29.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"37040","tags":"Servicemember","has_narrative":true,"complaint_id":"16583777","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-10-15T04:57:03.000Z","state":"TN","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Account information incorrect"},"highlight":{"complaint_what_happened":["CFPB / <em>Metro</em> 2Compliant Dispute & Complaint Consumer : XXXX XXXX XXXX Account : XXXX XXXX XXXX XXXX {$270.00} Subject : Inaccurate Late Payment Reporting / <em>Metro</em> 2 <em>Compliance</em> <em>Violation</em> Regulations Cited : 15 U.S.C. 1681s-2 ( b ) Duty to investigate and correct inaccurate information 15 U.S.C. 1681i Reinvestigation of disputed information 38 U.S.C. 5301 Protection of veterans benefits CDIA <em>Metro</em> 2 Format Standards ( <em>Base</em> Segment & Payment History Profile Fields ) Complaint Summary : I am filing this"]},"sort":[20.247425,"16583777"]},{"_index":"complaint-public-v1","_id":"13976471","_score":20.212269,"_source":{"product":"Credit card","complaint_what_happened":"XXXX XXXX XXXX XX/XX/XXXX To : Experian P.O. XXXX XXXX XXXX, TX XXXX RE : Urgent Request to Remove XXXX XXXX Charge-Off Identity Theft / FCRA & Metro 2 Violations Account # : XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXXXXXX To Whom It XXXX Concern : I am writing to formally dispute the accuracy and legality of a XXXX XXXX  charge-off account being reported on my credit file. I am the victim of identity theft and previously filed a formal FTC Identity Theft Report in XXXX, which was submitted to both Experian and XXXX XXXX. This account is fraudulent and should not be attributed to me. \n\nAs of XX/XX/XXXX, Experian responded to my Method of Verification ( MOV ) request stating I XXXX be a victim of identity theft, yet this account remains on my credit report in violation of the Fair Credit Reporting Act ( FCRA ) and Metro 2 compliance standards. \n\nThis letter serves as a final formal demand for deletion based on the following violations : Violations of the Fair Credit Reporting Act ( FCRA ) : XXXX Failure to block identity theft information within XXXX business days of receiving proper documentation 611 ( a ) ( 7 ) Failure to provide Method of Verification documents 623 ( a ) ( 6 ) Failure to mark the account as disputed or notify consumer accurately 623 ( a ) ( 1 ) ( A ) Continued furnishing of inaccurate information Metro 2 Compliance Violations : Failure to use Special Comment Code Z ( Confirmed Identity Theft ) Failure to apply Compliance Condition Code F ( Fraudulent ) Continued reporting of unverifiable, fraudulent data in violation of XXXX XXXX standards XXXX Requested : Immediately block and delete the XXXX XXXX tradeline from my credit report Send written confirmation of the removal within 15 calendar days Cease all future reporting of this tradeline under FCRA 623 ( a ) ( 2 ) I am prepared to escalate this matter to the Consumer Financial Protection Bureau XXXX Federal Trade Commission XXXX and pursue legal action in Texas XXXX XXXX XXXX XXXX FCRA 1681n and 1681o for statutory and punitive damages. \n\nSincerely, XXXX XXXX","date_sent_to_company":"2025-06-09T21:05:41.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"General-purpose credit card or charge card","zip_code":"752XX","tags":"Servicemember","has_narrative":true,"complaint_id":"13976471","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-06-09T20:35:05.000Z","state":"TX","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["This letter serves as a final formal demand for deletion <em>based</em> on the following <em>violations</em> : <em>Violations</em> of the Fair Credit Reporting Act ( FCRA ) : XXXX Failure to block identity theft information within XXXX business days of receiving proper documentation 611 ( a ) ( 7 ) Failure to provide Method of Verification documents 623 ( a ) ( 6 ) Failure to mark the account as disputed or notify consumer accurately 623 ( a ) ( 1 ) ( A ) Continued furnishing of inaccurate information <em>Metro</em> 2 <em>Compliance</em> <em>Violations</em>"]},"sort":[20.212269,"13976471"]},{"_index":"complaint-public-v1","_id":"12951299","_score":20.014385,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX XXXX XXXX XXXX XXXX XXXX, LA XXXX XXXX XXXX XX/XX/XXXX Experian Attn : Executive Customer Relations XXXX XXXX XXXX XXXX XXXX, CA XXXX **RE : Formal Dispute per FCRA Section 611 ( a ) - Metro2 Non-Compliance** **Consumer Name : ** XXXX XXXXr **Date of Birth : ** XX/XX/XXXX **SSN : ** XXXX **Special Comment Code : ** XXXX  ( Consumer Disputes Account Information ) To Whom It May Concern : This communication serves as my formal dispute under FCRA Section 611 ( a ) ( 2 ) regarding multiple accounts on my Experian credit report that fail to comply with Metro2 reporting standards as outlined in the XXXX 's Credit Reporting Resource Guide ( XXXX ). \n\nI am aware of the Consumer Financial Protection Bureau 's lawsuit against Experian ( Case Number : XXXX ) alleging systematic failures in Metro2 compliance verification during the dispute resolution process.\n\nThe following accounts contain Metro2 Format violations per the XXXX and FCRA Section 623 ( b ) : **1. XXXX - Account Condition Code : Currently showing Collection ( Code 97 ) - Portfolio Type : 31 - Balance : {$1000.00} as of XX/XX/XXXX - XXXX Code issue : Account incorrectly lacks Consumer Dispute Indicator ( XXXX  ) - Compliance Failure : Despite \" Under dispute '' marking, no Compliance Condition Code XC has been applied - Metro2 Correction Required : Apply XH ( Disputed Information ) indicator and correct Account Status code **2. XXXX - Account Status : Under dispute - Metro2 Compliance Issue : No Specialized Payment Indicator ( SPI ) code or Account Status ( 05 ) reflecting dispute - Required Action : Apply appropriate XXXX XXXX dispute indicators **3. Account with Negative Payment History** - Payment History Profile : Containing delinquencies for XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX - Metro2 Compliance Issue : Inaccurate Payment History Profile codes- Required Correction : Apply appropriate payment codes as per XXXX XXXX. Duplicate XXXX XXXXXXXX Accounts ( XXXX ) ** - Metro2 Violation : XXXX Section 6.8 prohibits duplicate account reporting - Account Corrections Required : Remove duplicate tradeline and retain single accurate account with proper Date Opened field Per FCRA Section 611 ( a ) and the E-OSCARXXXX requirements outlined in the XXXX, I formally request : 1. Full Metro2 compliance review including verification of all Base Segment fields and applicable Appendage Segments 2. Proper transmission of all dispute codes ( XXXX XXXX ) to data furnishers via XXXX 3. Verification of FCRA-compliant reinvestigation including all relevant Account Status Codes 4. Removal of all accounts that can not be verified in compliance with Metro2 Format requirements 5. Written confirmation that all disputed accounts have been properly coded with applicable XXXX XXXX XXXX XXXX  indicators 6. Notification of all corrections to data furnishers, including proper Metro2 compliance requirements This dispute requires your verification that all data furnishers are properly certified in Metro2 Format reporting per CDIA requirements and that all Account Status, Portfolio Type, and Consumer Information Indicator fields comply with current CRRG standards.\n\nUnder the FCRA, ECOA Regulation B, and CFPB guidelines, I expect a complete response within 30 days including verification that proper dispute codes have been applied to my consumer disclosure. \n\nSincerely, XXXX XXXX Enclosures : - Copy of Experian credit report with Metro2 compliance issues highlighted - Supporting documentation for disputed items","date_sent_to_company":"2025-04-12T01:15:30.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"713XX","tags":null,"has_narrative":true,"complaint_id":"12951299","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-04-12T01:10:41.000Z","state":"LA","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Reporting company used your report improperly"},"highlight":{"complaint_what_happened":["Duplicate XXXX XXXXXXXX Accounts ( XXXX ) ** - <em>Metro</em>2 <em>Violation</em> : XXXX Section 6.8 prohibits duplicate account reporting - Account Corrections Required : Remove duplicate tradeline and retain single accurate account with proper Date Opened field Per FCRA Section 611 ( a ) and the E-OSCARXXXX requirements outlined in the XXXX, I formally request : 1. Full <em>Metro</em>2 <em>compliance</em> review including verification of all <em>Base</em> Segment fields and applicable Appendage Segments 2."]},"sort":[20.014385,"12951299"]},{"_index":"complaint-public-v1","_id":"15536256","_score":18.966778,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"On XX/XX/XXXX, Experian denied my identity theft block request. In their email, they claimed that my request was either : made in error, based on a material misrepresentation, or that I knowingly obtained goods or services from the fraudulent transactions. \n\nThese claims are false, unsupported, and defamatory. Experian provided no evidence to support any of these allegations. They also failed to provide any explanation or documentation showing how they validated these claims. \n\nSpecifically, Experian did not : Provide any documents from the furnishers ( such as signed contracts, billing statements, or proof of my authorization ). \n\nProvide a description of their method of verification as required under FCRA 1681i ( a ) ( 7 ). \n\nExplain which furnisher ( s ) they contacted, if any, or what records they relied on in reaching their conclusion. \n\nDemonstrate compliance with FCRA 605B, which requires a block within four business days once valid police and FTC Identity Theft Reports are received. \n\nCorrect ongoing Metro 2 compliance violations, including missing Date of First Delinquency, Payment Rating, Compliance Condition Codes, and Special Comment Codes. \n\nInstead, Experian issued a form denial letter that ignores the evidence I provided, including a valid police report ( XXXX ) and FTC Identity Theft Report, which legally require them to block these fraudulent items. \n\nThis failure to act is a violation of FCRA 605B, 1681e ( b ), 1681i, and 1681i ( a ) ( 7 ), as well as CFPB Administrative Proceeding File No. XXXX, which requires full and detailed reinvestigations. \n\nI am requesting CFPB intervention to compel Experian to : Immediately block the fraudulent accounts in compliance with 605B, Provide the full method of verification under 1681i ( a ) ( 7 ), Delete unverifiable accounts and confirm they will not be reinserted.","date_sent_to_company":"2025-08-26T13:44:55.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"770XX","tags":null,"has_narrative":true,"complaint_id":"15536256","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-08-26T13:33:49.000Z","state":"TX","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["Demonstrate <em>compliance</em> with FCRA 605B, which requires a block within four business days once valid police and FTC Identity Theft Reports are received. \n\nCorrect ongoing <em>Metro</em> 2 <em>compliance</em> <em>violations</em>, including missing Date of First Delinquency, Payment Rating, <em>Compliance</em> Condition Codes, and <em>Special</em> Comment Codes."]},"sort":[18.966778,"15536256"]},{"_index":"complaint-public-v1","_id":"13559064","_score":18.766544,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Formal Dispute of Inaccurate Repossession Entry Demand for Immediate Deletion under FCRA, Metro 2, and CDIA Guidelines I am requesting a full investigation and immediate deletion of this account based on the following legal violations, Metro 2 noncompliance, and exploitable compliance gapss in your current reporting. \nXXXX XXXX XXXX XXXX XXXX  Identified Violations & compliance gaps XXXX XXXX XXXX XXXX XXXX XXXX. Missing or Inaccurate Date of First Delinquency ( DOFD ) Under 15 U.S. Code 1681c ( a ) ( 4 ) and Metro 2 standards, the DOFD must be accurately reported to ensure timely purging of obsolete negative data.\n\ncompliance gaps : Many furnishers fail to report this correctly or omit it entirely, which renders the account unverifiable and mandates deletion. \nXXXX XXXX XXXX XXXX XXXX. Improper Coding of Repossession Status Metro 2 requires the Special Comment Code \" R '' ( Repossession ) and specific Compliance Condition Codes ( e.g., \" XA '', \" XB '' ) to be used. If these codes are missing or misused, the entire entry is noncompliant with CDIA formatting rules. \ncompliance gaps : Improper status codes = violation of FCRA 1681e ( b ) ( maximum possible accuracy ) and grounds for deletion.\n\nXXXX XXXX XXXX XXXX 3. Re-aging of the Account If the account reflects recent payment activity or a re-aged delinquency, this could be a violation of FCRA 1681c, which limits how long negative information can remain. \ncompliance gaps : Any attempt to restart the clock on a repossession is illegal and requires immediate correction or deletion. \nXXXX XXXX XXXX XXXX XXXX. Missing \" Actual Payment History '' Grid ( Field 24A ) Metro 2 format requires a complete payment history grid. If its missing, incomplete, or doesn't align with the reported charge-off date or repossession, then the account is considered incomplete. \ncompliance gaps : Incomplete data = must be deleted under FCRA 1681i ( a ) ( 5 ) ( A ). \nXXXX XXXX XXXX XXXX  XXXX. Failure to Report a XXXX Balance Post-Repossession If the vehicle was sold and the debt was settled or satisfied ( whether paid or written off ), the account should reflect a {$0.00} balance, with accurate codes showing the deficiency ( if any ). \ncompliance gaps : Reporting a balance after collateral recovery may be considered deceptive or double jeopardy, especially if a 1099-XXXX was issued. \nXXXX XXXX XXXX XXXX  XXXX. No Legal Right to Report if Debt Was Sold If the account was sold to a third party, the original creditor may no longer have legal authority to continue reporting it. \ncompliance gaps : Both entities can not report the same debt without full validation and proof of ownership, which often doesnt exist. \nXXXX XXXX XXXX XXXX XXXX. No Proof of Contract or Permissible Purpose Under FCRA 1681b, the original furnisher must demonstrate a permissible purpose and maintain records verifying the debt. \ncompliance gaps : If they can not produce a signed agreement with full itemization, the debt is unverifiable and must be deleted. \n# # # # 8. CFPB Enforcement History Sham Investigations As you are aware, the CFPB has taken enforcement actions against Experian and Equifax for engaging in sham dispute investigations that violated consumer rights under the FCRA. \ncompliance gaps : If a real reinvestigation is not conducted, you are subject to further enforcement actions and civil liability under FCRA 1681n & 1681o. \n-- XXXX XXXX XXXX XXXX  DEMAND FOR REMOVAL In accordance with FCRA 1681i, 1681e ( b ), and 1681c, and pursuant to Metro 2 and CDIA standards, I demand the immediate deletion of this account due to multiple reporting deficiencies, lack of proper verification, and failure to meet lawful compliance standards. \nIf the account is not removed within the 30-day statutory period, I will escalate this matter to the Consumer Financial Protection Bureau XXXX CFPB ), Federal Trade Commission ( FTC ), and my state Attorney Generals office. I also reserve the right to pursue legal action under FCRA 1681n/o for willful or negligent noncompliance. \nPlease mail a new copy of my credit report showing the results of your reinvestigation and confirmation of deletion. \nSincerely, XXXX XXXX","date_sent_to_company":"2025-05-16T15:36:17.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"53144","tags":null,"has_narrative":true,"complaint_id":"13559064","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-05-16T15:28:01.000Z","state":"WI","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Reporting company used your report improperly"},"highlight":{"complaint_what_happened":["Formal Dispute of Inaccurate Repossession Entry Demand for Immediate Deletion under FCRA, <em>Metro</em> 2, and CDIA Guidelines I am requesting a full investigation and immediate deletion of this account <em>based</em> on the following legal <em>violations</em>, <em>Metro</em> 2 noncompliance, and exploitable <em>compliance</em> gapss in your current reporting. \nXXXX XXXX XXXX XXXX XXXX  Identified <em>Violations</em> & <em>compliance</em> gaps XXXX XXXX XXXX XXXX XXXX XXXX. Missing or Inaccurate Date of First Delinquency ( DOFD ) Under 15 U.S."]},"sort":[18.766544,"13559064"]},{"_index":"complaint-public-v1","_id":"13545686","_score":18.756987,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Formal Dispute of Inaccurate Repossession Entry Demand for Immediate Deletion under FCRA, Metro 2, and CDIA Guidelines I am requesting a full investigation and immediate deletion of this account based on the following legal violations, Metro 2 noncompliance, and exploitable compliance gapss in your current reporting. \nXXXX XXXX XXXX XXXX XXXX  Identified Violations & compliance gaps XXXX XXXX XXXX XXXX XXXX XXXX. Missing or Inaccurate Date of First Delinquency ( DOFD ) Under 15 U.S. Code 1681c ( a ) ( 4 ) and Metro 2 standards, the DOFD must be accurately reported to ensure timely purging of obsolete negative data.\n\ncompliance gaps : Many furnishers fail to report this correctly or omit it entirely, which renders the account unverifiable and mandates deletion. \nXXXX XXXX XXXX XXXX XXXX. Improper Coding of Repossession Status Metro 2 requires the Special Comment Code \" R '' ( Repossession ) and specific Compliance Condition Codes ( e.g., \" XA '', \" XB '' ) to be used. If these codes are missing or misused, the entire entry is noncompliant with CDIA formatting rules. \ncompliance gaps : Improper status codes = violation of FCRA 1681e ( b ) ( maximum possible accuracy ) and grounds for deletion.\n\nXXXX XXXX XXXX XXXX 3. Re-aging of the Account If the account reflects recent payment activity or a re-aged delinquency, this could be a violation of FCRA 1681c, which limits how long negative information can remain. \ncompliance gaps : Any attempt to restart the clock on a repossession is illegal and requires immediate correction or deletion. \nXXXX XXXX XXXX XXXX XXXX. Missing \" Actual Payment History '' Grid ( Field 24A ) Metro 2 format requires a complete payment history grid. If its missing, incomplete, or doesn't align with the reported charge-off date or repossession, then the account is considered incomplete. \ncompliance gaps : Incomplete data = must be deleted under FCRA 1681i ( a ) ( 5 ) ( A ). \nXXXX XXXX XXXX XXXX  XXXX. Failure to Report a XXXX Balance Post-Repossession If the vehicle was sold and the debt was settled or satisfied ( whether paid or written off ), the account should reflect a {$0.00} balance, with accurate codes showing the deficiency ( if any ). \ncompliance gaps : Reporting a balance after collateral recovery may be considered deceptive or double jeopardy, especially if a 1099-XXXX was issued. \nXXXX XXXX XXXX XXXX  XXXX. No Legal Right to Report if Debt Was Sold If the account was sold to a third party, the original creditor may no longer have legal authority to continue reporting it. \ncompliance gaps : Both entities can not report the same debt without full validation and proof of ownership, which often doesnt exist. \nXXXX XXXX XXXX XXXX XXXX. No Proof of Contract or Permissible Purpose Under FCRA 1681b, the original furnisher must demonstrate a permissible purpose and maintain records verifying the debt. \ncompliance gaps : If they can not produce a signed agreement with full itemization, the debt is unverifiable and must be deleted. \n# # # # 8. CFPB Enforcement History Sham Investigations As you are aware, the CFPB has taken enforcement actions against Experian and Equifax for engaging in sham dispute investigations that violated consumer rights under the FCRA. \ncompliance gaps : If a real reinvestigation is not conducted, you are subject to further enforcement actions and civil liability under FCRA 1681n & 1681o. \n-- XXXX XXXX XXXX XXXX  DEMAND FOR REMOVAL In accordance with FCRA 1681i, 1681e ( b ), and 1681c, and pursuant to Metro 2 and CDIA standards, I demand the immediate deletion of this account due to multiple reporting deficiencies, lack of proper verification, and failure to meet lawful compliance standards. \nIf the account is not removed within the 30-day statutory period, I will escalate this matter to the Consumer Financial Protection Bureau XXXX CFPB ), Federal Trade Commission ( FTC ), and my state Attorney Generals office. I also reserve the right to pursue legal action under FCRA 1681n/o for willful or negligent noncompliance. \nPlease mail a new copy of my credit report showing the results of your reinvestigation and confirmation of deletion. \nSincerely, XXXX XXXX","date_sent_to_company":"2025-05-16T15:36:17.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"53144","tags":null,"has_narrative":true,"complaint_id":"13545686","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-05-16T15:35:53.000Z","state":"WI","company_public_response":null,"sub_issue":"Reporting company used your report improperly"},"highlight":{"complaint_what_happened":["Formal Dispute of Inaccurate Repossession Entry Demand for Immediate Deletion under FCRA, <em>Metro</em> 2, and CDIA Guidelines I am requesting a full investigation and immediate deletion of this account <em>based</em> on the following legal <em>violations</em>, <em>Metro</em> 2 noncompliance, and exploitable <em>compliance</em> gapss in your current reporting. \nXXXX XXXX XXXX XXXX XXXX  Identified <em>Violations</em> & <em>compliance</em> gaps XXXX XXXX XXXX XXXX XXXX XXXX. Missing or Inaccurate Date of First Delinquency ( DOFD ) Under 15 U.S."]},"sort":[18.756987,"13545686"]},{"_index":"complaint-public-v1","_id":"12889954","_score":18.481554,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX XXXX XXXX XXXX XXXX XXXX, LA XXXX Phone : XXXX **Date : ** XX/XX/XXXX XXXX, XXXX Attn : Legal Department/Customer Disputes XXXX XXXX XXXX XXXX XXXX TN XXXX **RE : FORMAL NOTICE OF FCRA VIOLATIONS & DEMAND FOR IMMEDIATE DELETION** **Account # : ** [ YOUR FACTORTRUST REFERENCE NUMBER ] **Consumer : ** XXXX XXXX To Whom It May Concern : This correspondence serves as formal notice of multiple violations of the Fair Credit Reporting Act ( FCRA ), 15 U.S.C. 1681 et seq., in connection with my XXXX consumer report. I demand immediate investigation and deletion of all inaccurate information within the statutorily prescribed timeframe. \n\n# # NOTICE OF METRO 2 FORMAT COMPLIANCE VIOLATIONS I have identified the following entries in my XXXX consumer file that violate the Consumer Data Industry Association 's Metro 2 Format reporting standards and therefore constitute FCRA violations : 1. XXXX XXXX XXXX XXXX Reported XX/XX/XXXX ) - XXXX # : XXXX - Metro 2 Violation : Incorrect consumer identity information reported in Base Segment fields, constituting violation of Field 7 ( Identification Number ) and Field 10-11 ( Name ) requirements - FCRA Violation : 1681e ( b ) failure to follow reasonable procedures to assure maximum possible accuracy 2. *XXXX  XXXX XXXX Reported XX/XX/XXXX ) - XXXX XXXX XXXX XXXXXXXX - Metro 2 Violation : Failure to properly code Field 25 ( Terms Duration ) and Field 17-18 ( Consumer Information Indicator ) as disputed information - FCRA Violation : 1681i ( a ) failure to conduct reasonable reinvestigation of disputed information 3. XXXX XXXX XXXX Consumer Disputes** ( Reported XX/XX/XXXX ) - XXXX XXXX XXXX  XXXX - Metro 2 Violation : Improper Special Comment Code ( Field 19 ) indicating \" Echo information '' reflecting duplicative reporting - FCRA Violation : 1681s-2 ( a ) ( 1 ) ( B ) furnishing information known to be inaccurate 4. *XXXX XXXXXXXX XXXX Reported XX/XX/XXXX ) - XXXX XXXX XXXX XXXX - Metro 2 Violation : Improper Account Status ( Field 17A ) and Payment Rating ( Field 17B ) coding - FCRA Violation : 1681s-2 ( a ) ( 2 ) failure to correct and update information # # CORRECT CONSUMER IDENTIFYING INFORMATION The ONLY personal identifying information that should appear in my consumer file is : - **Correct Name : ** XXXX XXXX - **Correct Address : ** XXXX XXXX XXXX, XXXX, LA XXXX - **Correct Phone : XXXX XXXX","date_sent_to_company":"2025-04-10T12:47:59.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"713XX","tags":null,"has_narrative":true,"complaint_id":"12889954","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-04-10T00:42:36.000Z","state":"LA","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Information belongs to someone else"},"highlight":{"complaint_what_happened":["# # NOTICE OF <em>METRO</em> 2 FORMAT <em>COMPLIANCE</em> <em>VIOLATIONS</em> I have identified the following entries in my XXXX consumer file that <em>violate</em> the Consumer Data Industry Association 's <em>Metro</em> 2 Format reporting standards and therefore constitute FCRA <em>violations</em> : 1."]},"sort":[18.481554,"12889954"]},{"_index":"complaint-public-v1","_id":"13245993","_score":18.412441,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"CERTIFIED MAIL - RETURN RECEIPT REQUESTED XX/XX/year> Experian Attn : Metro 2 Compliance Department XXXX. XXXX XXXX XXXX, TX XXXX RE : Metro 2XXXX XXXX Dispute - Consumer Information Indicator ( CII ) Code ViolationsFile # XXXX : XXXX XXXX : XXXX : XXXX Address : XXXX XXXX XXXX, XXXX, LA XXXX XXXX ID : XXXX ( Activated XXXX XXXX To Whom It May Concern : This communication serves as a formal Metro 2 Format compliance dispute pursuant to the Consumer Reporting Resource Guide ( CRRG ) standards and Fair Credit Reporting Act ( 15 U.S.C. 1681 et seq. ). \nSTATUTORY DAMAGES NOTIFICATION I am seeking statutory damages of {$1000.00} per occurrence under FCRA Section 616 [ 15 U.S.C. 1681n ] for willful noncompliance with Metro 2 Format requirements after multiple unsuccessful dispute attempts. This letter constitutes formal notice that failure to correct these violations within 30 days will result in further legal action seeking maximum statutory damages. \nMETRO 2 FORMAT/CRRG SPECIFIC VIOLATIONS The following accounts contain specific Metro 2 Format violations as defined in CRRG : XXXX. XXXX ( Account # XXXX ) XXXX XXXX XXXX XXXXXXXX : Incorrect Account Status Code ( should be DA = Delete Account ) XXXX XXXX XXXX XXXX XXXX XXXX XXXX Code of Z for disputed account XXXX  XXXX : Missing CCC ( Consumer Account Number ) verification XXXX Segment : Missing required Consumer Dispute Indicator ( XXXX ) XXXX XXXX Address : XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXXor fraud investigation XXXX. XXXX XXXX XXXX ( Account # XXXX ) XXXX XXXX XXXX XXXX XXXX Incorrect Account Status Code ( reported as XXXX, XXXX ) XXXX  XXXX : Missing required XXXX Segment ( fraud investigation information ) XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX Special Comment Code XXXX  XXXX : Missing code AH for disputed account XXXX. XXXX  ( Account # XXXX ) XXXX  XXXX : Incorrect Account Status Code for collection account XXXX  XXXX : Incomplete Consumer Account Number reporting Base Segment XXXX  XXXX : XXXX XXXX XXXX XXXX XXXX for disputed account Segment XXXX : No proper dispute reason code of XXXX for identity theft UNAUTHORIZED LANGUAGE MANIPULATION VIOLATION Unauthorized XXXX  language setting constitutes : Metro 2 Format Violation : XXXX  XXXX ( Language Preference Indicator ) improperly set Base Segment XXXX  XXXX : Missing proper Consumer Information Indicator of XXXX XXXX  METRO 2 NON-COMPLIANCE Despite multiple previous disputes, the following Metro 2 non-compliance issues remain : XXXX. Security Alert ( ID # XXXX ) : Base Segment XXXX  XXXX : Missing requireXXXX XXXX XXXX XXXXXXXX on all trade lines XXXX Segment : Missing proper fraud investigation documentation XXXX Segment Field XXXX : Missing proper dispute reason code 2. Duplicate Account Identification Number : Multiple accounts sharing ID number XXXX ( invalid Metro 2 reporting ) XXXX XXXX XXXX XXXX : Incorrectly populated Account Number field CONSUMER INFORMATION DISPUTE ADDENDUM ( CIDA ) VIOLATIONS The following CIDA violations are present in my file : Failed implementation of CIDA A1 Segment for disputed accounts Improper Dispute Status Code indicators in XXXX XXXX XXXX Missing Dispute Resolution Date in XXXX XXXX XXXX Incomplete Dispute Resolution Code in XXXX XXXX XXXX PERSONAL IMPACT STATEMENT OF DAMAGES These XXXX XXXX Format violations have resulted in quantifiable damages : Denial of credit for essential family purchases ( XXXX for XXXX XXXX ) Lost opportunity costs from credit denials : $ XXXX Emotional distress requiring documentation : $ XXXX Time spent repeatedly disputing accounts : XXXX hours at $ XXXX : $ XXXX REMEDIATION REQUIREMENTS ( CRRG STANDARDS ) Under FCRA XXXX XXXX ( a ) and XXXX XXXX XXXX Format requirements, I demand : XXXX XXXX XXXX XXXX XXXX Fields XXXX correction on all listed accounts XXXX. Application of proper XXXX XXXX XXXX ( CII ) codes in XXXX XXXX XXXX. Complete XXXX Segments with proper dispute codes XXXX. XXXX Segment completion with required fraud investigation documentation XXXX. XXXX preference restoration to XXXX in XXXX XXXX XXXX. Written confirmation of all XXXX XXXX Format corrections within 30 days LEGAL NOTICE This letter constitutes formal notification under FCRA Sections XXXX [ XXXX XXXX. XXXX ] of intent to pursue maximum statutory damages of {$1000.00} per willful violation and actual damages for negligent noncompliance if these XXXX XXXX XXXX violations are not corrected within the statutory timeframe. \nSincerely, XXXX XXXX XXXX XXXX XXXX XXXX, LA XXXX XXXX Enclosures : Security Alert Documentation ( # XXXX ) Screenshots of Unauthorized XXXX  XXXX XXXX XXXX XXXX XXXX XXXX Format Field Violations Previous Dispute Documentation Report # XXXX ( Full Copy ) CC : Consumer Financial Protection Bureau Federal Trade Commission Attorney General, State of Louisiana","date_sent_to_company":"2025-04-30T06:00:56.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"713XX","tags":null,"has_narrative":true,"complaint_id":"13245993","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-04-30T04:37:23.000Z","state":"LA","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Difficulty submitting a dispute or getting information about a dispute over the phone"},"highlight":{"complaint_what_happened":["Missing proper Consumer Information Indicator of XXXX XXXX  <em>METRO</em> 2 NON-<em>COMPLIANCE</em> Despite multiple previous disputes, the following <em>Metro</em> 2 non-<em>compliance</em> issues remain : XXXX."]},"sort":[18.412441,"13245993"]},{"_index":"complaint-public-v1","_id":"16398297","_score":18.394056,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX XXXX XXXX XXXX XXXX XXXX XXXX, LA XXXX XXXX : XX/XX/XXXX SSN ( Last 4 ) : XXXX Phone : ( XXXX ) XXXX Email : XXXX Date : XX/XX/XXXX Experian Information Solutions , Inc . \nXXXX XXXX XXXXXXXX XXXX, TX XXXX Subject : Metro 2 Compliance and FCRA Dispute Request for Reinvestigation and Permanent Deletion of Non-Compliant Accounts This is a formal consumer dispute under the Fair Credit Reporting Act ( FCRA 15 U.S.C. 602 ( a ), 607 ( b ), 611 ( a ), and 623 ( a ) ), the Fair Debt Collection Practices Act ( FDCPA 807 ), and the Credit Data Industry Association ( CDIA ) Metro 2 Format / CRRG guidelines. I am disputing multiple items in my Experian credit file that contain outdated, inaccurate, incomplete, or otherwise non-compliant data fields. \n\nI request a full reinvestigation and verification of each accounts Metro 2 data structure, codes, and base-segment accuracy. Any information that can not be verified with documentation from the original furnisher must be permanently deleted under FCRA 611 ( a ) ( 5 ). \n\n\n\nXXXX. XXXX / XXXX The tradeline is shown as Paid / Closed Never Late, but its Metro 2 fields appear non-compliant : Account Status Code may be mis-reported ( code 13 = paid/closed ; verify date alignment ). \nPayment Rating should be blank for a closed account per CRRG 6.2.4.\n\nDate Closed and Date of Last Payment may not correspond per CRRG 2.3.2.\n\nCompliance Condition Code should be null because no dispute exists.\n\nUnder FCRA 607 ( b ) and CRRG standards, Experian must ensure maximum possible accuracy. If the furnisher can not supply verifiable documentation supporting these fields, this tradeline must be deleted. \n\n\n\nXXXX. XXXX XXXX The account reports Paid/ Closed Never Late, but multiple Metro 2 elements appear inaccurate or incomplete : Account Type Code and Portfolio Type may not match the actual product classification.\n\nECOA Code ( ownership type ) may be missing or miscoded, violating CRRG 2.3.2.\n\nPayment Rating and Current Balance fields appear populated on a zero-balance account. \nThese inconsistencies create factual errors and make the data unverifiable. If the furnisher can not correct and certify each field, Experian must delete the entire entry under FCRA 611 ( a ) ( 5 ). \n\n\n\nXXXX XXXX XXXX XXXX This account is listed as Paid / Closed but still shows Account in Dispute.\n\nConsumer Information Indicator should be removed once the dispute is resolved ( CRRG 6.4.1 ).\n\nSpecial Comment Code conflicts with the account status.\n\nDate of First Delinquency or Date of Status may be invalid or omitted.\n\nBecause these coding errors render the entry unverifiable, Experian must either correct them to full Metro 2 compliance or delete the record under FCRA 611 ( a ) and 623 ( a ) ( 1 ) ( A ).","date_sent_to_company":"2025-10-06T09:00:15.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"71457","tags":null,"has_narrative":true,"complaint_id":"16398297","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-10-06T07:19:14.000Z","state":"LA","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Account status incorrect"},"highlight":{"complaint_what_happened":["<em>Special</em> Comment Code conflicts with the account status.\n\nDate of First Delinquency or Date of Status may be invalid or omitted.\n\nBecause these coding errors render the entry unverifiable, Experian must either correct them to full <em>Metro</em> 2 <em>compliance</em> or delete the record under FCRA 611 ( a ) and 623 ( a ) ( 1 ) ( A )."]},"sort":[18.394056,"16398297"]},{"_index":"complaint-public-v1","_id":"4396068","_score":18.25903,"_source":{"product":"Credit reporting, credit repair services, or other personal consumer reports","complaint_what_happened":"I have asked numerous times to reinvestigate the following items listed below and you have failed to properly conduct a reinvestigation as required and responded with a notice providing all relevant information listed in my disputes. I have also requested the method of verification as listed under section 611 ( a ) ( 7 ) for the description of the reinvestigation procedure which is to be provided within 15 days of your investigation which you have also failed to provide me.\n\nResults provided to reinvestigation does not provide the relevant information listed in the disputes I have sent in and just states updated with no relevant information on what is being disputes as required by Furthermore, when using the E-Oscar system for verification it is required to follow the CDIA standards of Metro 2 to ensure it is maintaining accuracy, integrity and consistency of credit information for the consumer. Which Equifax has failed to do with multiple errors being reported in my reports even after the investigation Bankruptcy XXXX This account has been removed by XXXX. A copy of the report is included in this dispute. So how is this still being reported? \nPlease delete this bankruptcy immediately XXXX XXXX Disputed on XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX Activity designator showing transfer/sold with no close date as required or the name of who it was sold to as required by the CDIA metro 2 guidelines under segment K2 Field 3 and no Closed date field 26 as required.\n\nThis is a violation and must delete this erroneous account immediately Direct dispute was sent to XXXX on XX/XX/XXXX with a response that they no longer have the information to provide and there has been no compliance condition codification for dispute as required by the FCRA 623 ( a ) ( 8 ) ( B ) ( E ).\n\nThis is a violation and clear indication that no investigation has been done. Please delete this unverified immediately PORTFOLIO RC XXXX Disputed on XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX Consumer account number is inaccurate XXXX. Does not match what is being reported by the other credit bureaus and should not be reporting with embedded blanks or special characters. \nPlease delete this erroneous account Account, portfolio and account rating is inaccurate, causing inaccurate reporting of a collection account as a credit account which should not include a payment history profile. \nThis is a violation and the account must be removed immediately. \n\nXXXX XXXX Disputed on XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX, XX/XX/XXXX Date of last payment base segment field 27 is inaccurate reporting a date of XX/XX/XXXX but the payment history profile base segment field 18 is reporting an actual payment amount of {$72.00} on XX/XX/XXXX, XX/XX/XXXX and XX/XX/XXXX. \nAccount is reporting inaccurate and misleading information and must be deleted immediately Missing compliance codification for dispute as required by the FCRA 611 ( c ) and CDIA guidelines for Metro 2 reporting for a disputed account. \nThis is a violation and clear indication that no investigation has been done. Please delete this unverified immediately Date of First Delinquency Base segment Field 25 is inaccurate. How can the date of first delinquency be XX/XX/XXXX when the payment rating base segment field 17B reports 30 days late on XX/XX/XXXX. None of that adds up when it should be 30 days after the original missing payment date with the creditor, not the date it became 30 days late. Date of removal also reported on XXXX as XX/XX/XXXX showing Equifax reporting in inaccurate Your reporting of this account is misleading and re-ages the account. This is a violation and must be deleted immediately.","date_sent_to_company":"2021-05-21T20:10:05.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"33032","tags":null,"has_narrative":true,"complaint_id":"4396068","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2021-05-21T19:56:19.000Z","state":"FL","company_public_response":null,"sub_issue":"Account information incorrect"},"highlight":{"complaint_what_happened":["Account is reporting inaccurate and misleading information and must be deleted immediately Missing <em>compliance</em> codification for dispute as required by the FCRA 611 ( c ) and CDIA guidelines for <em>Metro</em> 2 reporting for a disputed account. \nThis is a <em>violation</em> and clear indication that no investigation has been done. Please delete this unverified immediately Date of First Delinquency <em>Base</em> segment Field 25 is inaccurate."]},"sort":[18.25903,"4396068"]},{"_index":"complaint-public-v1","_id":"13685301","_score":17.926493,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX XXXX XXXX XXXX XXXX XXXX XXXX, Fl XXXX XXXX Date : XX/XX/XXXX Subject : Formal Dispute of Inaccurate Repossession Entry Demand for Immediate Deletion under FCRA, Metro 2, and CDIA Guidelines To Whom It May Concern, This letter serves as my formal dispute regarding the alleged repossession account currently being reported on my credit file ( Name : XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXXXXXXXX/XX/XXXX XXXX XXXX XXXX XXXX  Account in Dispute : - Creditor Name : XXXX XXXX XXXX - Account Number : XXXX - Reporting Bureau : [ XXXX XXXX XXXX  / Equifax ] I am requesting a full investigation and immediate deletion of this account based on the following legal violations, Metro 2 noncompliance, and exploitable compliance gapss in your current reporting. -- - # # # Identified Violations & compliance gapss : # # # # 1. Missing or Inaccurate Date of First Delinquency ( DOFD ) Under 15 U.S. Code 1681c ( a ) ( 4 ) and Metro 2 standards, the DOFD must be accurately reported to ensure timely purging of obsolete negative data. compliance gaps : Many furnishers fail to report this correctly or omit it entirely, which renders the account unverifiable and mandates deletion. # # # # 2. Improper Coding of Repossession Status Metro 2 requires the Special Comment Code \" R '' ( Repossession ) and specific Compliance Condition Codes ( e.g., \" XA '', \" XB '' ) to be used. If these codes are missing or misused, the entire entry is noncompliant with CDIA formatting rules. compliance gaps : Improper status codes = violation of FCRA 1681e ( b ) ( maximum possible accuracy ) and grounds for deletion. # # # # 3. Re-aging of the Account If the account reflects recent payment activity or a re-aged delinquency, this could be a violation of FCRA 1681c, which limits how long negative information can remain. compliance gaps : Any attempt to restart the clock on a repossession is illegal and requires immediate correction or deletion. # # # # 4. Missing \" Actual Payment History '' Grid ( Field 24A ) Metro 2 format requires a complete payment history grid. If its missing, incomplete, or doesn't align with the reported charge-off date or repossession, then the account is considered incomplete. compliance gaps : Incomplete data = must be deleted under FCRA 1681i ( a ) ( 5 ) ( A ). # # # # 5. Failure to Report a Zero Balance Post-Repossession If the vehicle was sold and the debt was settled or satisfied ( whether paid or written off ), the account should reflect a {$0.00} balance, with accurate codes showing the deficiency ( if any ). compliance gaps : Reporting a balance after collateral recovery may be considered deceptive or double jeopardy, especially if a 1099-C was issued. # # # # 6. No Legal Right to Report if Debt Was Sold If the account was sold to a third party, the original creditor may no longer have legal authority to continue reporting it. compliance gaps : Both entities can not report the same debt without full validation and proof of ownership, which often doesnt exist. # # # # 7. No Proof of Contract or Permissible Purpose Under FCRA 1681b, the original furnisher must demonstrate a permissible purpose and maintain records verifying the debt. compliance gaps : If they can not produce a signed agreement with full itemization, the debt is unverifiable and must be deleted. # # # # 8. CFPB Enforcement History Sham Investigations As you are aware, the CFPB has taken enforcement actions against Experian and Equifax for engaging in sham dispute investigations that violated consumer rights under the FCRA. compliance gaps : If a real reinvestigation is not conducted, you are subject to further enforcement actions and civil liability under FCRA 1681n & 1681o. -- - # # # DEMAND FOR REMOVAL In accordance with FCRA 1681i, 1681e ( b ), and 1681c, and pursuant to Metro 2 and CDIA standards, I demand the immediate deletion of this account due to multiple reporting deficiencies, lack of proper verification, and failure to meet lawful compliance standards. If the account is not removed within the 30-day statutory period, I will escalate this matter to the Consumer Financial Protection Bureau ( CFPB ), Federal Trade Commission ( FTC ), and my state Attorney Generals office. I also reserve the right to pursue legal action under FCRA 1681n/o for willful or negligent noncompliance. Please mail a new copy of my credit report showing the results of your reinvestigation and confirmation of deletion","date_sent_to_company":"2025-05-23T13:02:13.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"33607","tags":null,"has_narrative":true,"complaint_id":"13685301","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-05-23T12:59:26.000Z","state":"FL","company_public_response":null,"sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["Account Number : XXXX - Reporting Bureau : [ XXXX XXXX XXXX  / Equifax ] I am requesting a full investigation and immediate deletion of this account <em>based</em> on the following legal <em>violations</em>, <em>Metro</em> 2 noncompliance, and exploitable <em>compliance</em> gapss in your current reporting. -- - # # # Identified <em>Violations</em> & <em>compliance</em> gapss : # # # # 1."]},"sort":[17.926493,"13685301"]},{"_index":"complaint-public-v1","_id":"13577825","_score":17.926493,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXXXXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX FL XXXX XXXX Subject : Formal Dispute of Inaccurate Repossession Entry Demand for Immediate Deletion under FCRA, Metro 2, and CDIA Guidelines To Whom It May Concern, This letter serves as my formal dispute regarding the alleged repossession account currently being reported on my credit file ( Name : XXXX XXXX, XXXXXXXX XXXX XXXX XXXX XXXX  ], XXXX XXXX XXXX XXXX XXXX XXXX \n# # # Account in Dispute : - XXXXXXXX XXXX XXXX XXXX XXXX Account Number : XXXX - Reporting Bureau : TransUnion I am requesting a full investigation and immediate deletion of this account based on the following legal violations, Metro 2 noncompliance, and exploitable compliance gapss in your current reporting. \n-- - # # # Identified Violations & compliance gapss : # # # # 1. Missing or Inaccurate Date of First Delinquency ( DOFD ) Under 15 U.S. Code 1681c ( a ) ( 4 ) and Metro 2 standards, the DOFD must be accurately reported to ensure timely purging of obsolete negative data.\n\ncompliance gaps : Many furnishers fail to report this correctly or omit it entirely, which renders the account unverifiable and mandates deletion. \n# # # # 2. Improper Coding of Repossession Status Metro 2 requires the Special Comment Code \" R '' ( Repossession ) and specific Compliance Condition Codes ( e.g., \" XA '', \" XB '' ) to be used. If these codes are missing or misused, the entire entry is noncompliant with CDIA formatting rules.\n\ncompliance gaps : Improper status codes = violation of FCRA 1681e ( b ) ( maximum possible accuracy ) and grounds for deletion.\n\n# # # # 3. Re-aging of the Account If the account reflects recent payment activity or a re-aged delinquency, this could be a violation of FCRA 1681c, which limits how long negative information can remain. \ncompliance gaps : Any attempt to restart the clock on a repossession is illegal and requires immediate correction or deletion. \n# # # # 4. Missing \" Actual Payment History '' Grid ( Field 24A ) Metro 2 format requires a complete payment history grid. If its missing, incomplete, or doesn't align with the reported charge-off date or repossession, then the account is considered incomplete.\n\ncompliance gaps : Incomplete data = must be deleted under FCRA 1681i ( a ) ( 5 ) ( A ). \n# # # # XXXX. Failure to Report a XXXX Balance Post-Repossession If the vehicle was sold and the debt was settled or satisfied ( whether paid or written off ), the account should reflect a {$0.00} balance, with accurate codes showing the deficiency ( if any ).\n\ncompliance gaps : Reporting a balance after collateral recovery may be considered deceptive or double jeopardy, especially if a 1099-C was issued.\n\n# # # # 6. No Legal Right to Report if Debt Was Sold If the account was sold to a third party, the original creditor may no longer have legal authority to continue reporting it.\n\ncompliance gaps : Both entities can not report the same debt without full validation and proof of ownership, which often doesnt exist. \n# # # # 7. No Proof of Contract or Permissible Purpose Under FCRA 1681b, the original furnisher must demonstrate a permissible purpose and maintain records verifying the debt.\n\ncompliance gaps : If they can not produce a signed agreement with full itemization, the debt is unverifiable and must be deleted.\n\n# # # # 8. CFPB Enforcement History Sham Investigations As you are aware, the CFPB has taken enforcement actions against Experian and Equifax for engaging in sham dispute investigations that violated consumer rights under the FCRA.\n\ncompliance gaps : If a real reinvestigation is not conducted, you are subject to further enforcement actions and civil liability under FCRA 1681n & 1681o.\n\n-- - # # # DEMAND FOR REMOVAL In accordance with FCRA 1681i, 1681e ( b ), and 1681c, and pursuant to Metro 2 and CDIA standards, I demand the immediate deletion of this account due to multiple reporting deficiencies, lack of proper verification, and failure to meet lawful compliance standards.\n\nIf the account is not removed within the 30-day statutory period, I will escalate this matter to the Consumer Financial Protection Bureau ( CFPB ), Federal Trade Commission ( FTC ), and my state Attorney Generals office. I also reserve the right to pursue legal action under FCRA 1681n/o for willful or negligent noncompliance.\n\nPlease mail a new copy of my credit report showing the results of your reinvestigation and confirmation of deletion.","date_sent_to_company":"2025-05-18T23:57:36.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"33607","tags":null,"has_narrative":true,"complaint_id":"13577825","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-05-18T23:57:13.000Z","state":"FL","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["Reporting Bureau : TransUnion I am requesting a full investigation and immediate deletion of this account <em>based</em> on the following legal <em>violations</em>, <em>Metro</em> 2 noncompliance, and exploitable <em>compliance</em> gapss in your current reporting. \n-- - # # # Identified <em>Violations</em> & <em>compliance</em> gapss : # # # # 1."]},"sort":[17.926493,"13577825"]},{"_index":"complaint-public-v1","_id":"13401644","_score":17.926493,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Subject : Formal Dispute of Inaccurate Repossession Entry Demand for Immediate Deletion under FCRA, Metro 2, and CDIA Guidelines To Whom It May Concern, This letter serves as my formal dispute regarding the alleged repossession account currently being reported on my credit file ( Name : [ XXXX XXXX XXXX ], XXXX : XXXX [ Last XXXX ], XXXX XXXX [ XX/XX/scrub>XX/XX/XXXXXXXX XXXX XXXX XXXX XXXX XXXX  Account in Dispute : - Creditor Name : [ XXXX XXXX XXXX - Account Number : [ XXXX ] - Reporting Bureau : [ TransUnion I am requesting a full investigation and immediate deletion of this account based on the following legal violations, Metro 2 noncompliance, and exploitable compliance gapss in your current reporting. -- - # # # Identified Violations & compliance gapss : # # # # 1. Missing or Inaccurate Date of First Delinquency ( DOFD ) Under 15 U.S. Code 1681c ( a ) ( 4 ) and Metro 2 standards, the DOFD must be accurately reported to ensure timely purging of obsolete negative data. compliance gaps : Many furnishers fail to report this correctly or omit it entirely, which renders the account unverifiable and mandates deletion. # # # # 2. Improper Coding of Repossession Status Metro 2 requires the Special Comment Code \" R '' ( Repossession ) and specific Compliance Condition Codes ( e.g., \" XXXX '', \" XXXX  '' ) to be used. If these codes are missing or misused, the entire entry is noncompliant with CDIA formatting rules. compliance gaps : Improper status codes = violation of FCRA 1681e ( b ) ( maximum possible accuracy ) and grounds for deletion. # # # # 3. Re-aging of the Account If the account reflects recent payment activity or a re-aged delinquency, this could be a violation of FCRA 1681c, which limits how long negative information can remain. compliance gaps : Any attempt to restart the clock on a repossession is illegal and requires immediate correction or deletion. # # # # 4. Missing \" Actual Payment History '' Grid ( Field 24A ) Metro 2 format requires a complete payment history grid. If its missing, incomplete, or doesn't align with the reported charge-off date or repossession, then the account is considered incomplete. compliance gaps : Incomplete data = must be deleted under FCRA 1681i ( a ) ( 5 ) ( A ). # # # # 5. Failure to Report a Zero Balance Post-Repossession If the vehicle was sold and the debt was settled or satisfied ( whether paid or written off ), the account should reflect a {$0.00} balance, with accurate codes showing the deficiency ( if any ). compliance gaps : Reporting a balance after collateral recovery may be considered deceptive or double jeopardy, especially if a 1099-C was issued. # # # # 6. No Legal Right to Report if Debt Was Sold If the account was sold to a third party, the original creditor may no longer have legal authority to continue reporting it. compliance gaps : Both entities can not report the same debt without full validation and proof of ownership, which often doesnt exist. # # # # 7. No Proof of Contract or Permissible Purpose Under FCRA 1681b, the original furnisher must demonstrate a permissible purpose and maintain records verifying the debt. compliance gaps : If they can not produce a signed agreement with full itemization, the debt is unverifiable and must be deleted. # # # # XXXX. CFPB Enforcement History Sham Investigations As you are aware, the CFPB has taken enforcement actions against Experian and Equifax for engaging in sham dispute investigations that violated consumer rights under the FCRA. compliance gaps : If a real reinvestigation is not conducted, you are subject to further enforcement actions and civil liability under FCRA 1681n & 1681o. -- - # # # DEMAND FOR REMOVAL In accordance with FCRA 1681i, 1681e ( b ), and 1681c, and pursuant to Metro 2 and CDIA standards, I demand the immediate deletion of this account due to multiple reporting deficiencies, lack of proper verification, and failure to meet lawful compliance standards. If the account is not removed within the 30-day statutory period, I will escalate this matter to the Consumer Financial Protection Bureau ( CFPB ), Federal Trade Commission ( FTC ), and my state Attorney Generals office. I also reserve the right to pursue legal action under FCRA 1681n/o for willful or negligent noncompliance. Please mail a new copy of my credit report showing the results of your reinvestigation and confirmation of deletion. Sincerely, [ XXXX XXXX XXXX ]","date_sent_to_company":"2025-05-08T15:26:28.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"34653","tags":null,"has_narrative":true,"complaint_id":"13401644","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-05-08T15:25:57.000Z","state":"FL","company_public_response":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":[": [ TransUnion I am requesting a full investigation and immediate deletion of this account <em>based</em> on the following legal <em>violations</em>, <em>Metro</em> 2 noncompliance, and exploitable <em>compliance</em> gapss in your current reporting. -- - # # # Identified <em>Violations</em> & <em>compliance</em> gapss : # # # # 1."]},"sort":[17.926493,"13401644"]}]},"aggregations":{"has_narrative":{"meta":{},"doc_count":68,"has_narrative":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":1,"key_as_string":"true","doc_count":68}]}},"product":{"doc_count":68,"product":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Credit reporting or other personal consumer reports","doc_count":62,"sub_product.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Credit reporting","doc_count":60},{"key":"Other personal consumer report","doc_count":2}]}},{"key":"Credit reporting, credit repair services, or other personal consumer reports","doc_count":4,"sub_product.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Credit reporting","doc_count":4}]}},{"key":"Credit card","doc_count":1,"sub_product.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"General-purpose credit card or charge card","doc_count":1}]}},{"key":"Student loan","doc_count":1,"sub_product.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Federal student loan servicing","doc_count":1}]}}]}},"issue":{"doc_count":68,"issue":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Incorrect information on your report","doc_count":29,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Account status incorrect","doc_count":12},{"key":"Account information incorrect","doc_count":11},{"key":"Information belongs to someone else","doc_count":5},{"key":"Personal information incorrect","doc_count":1}]}},{"key":"Problem with a company's investigation into an existing problem","doc_count":26,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Their investigation did not fix an error on your report","doc_count":23},{"key":"Difficulty submitting a dispute or getting information about a dispute over the phone","doc_count":2},{"key":"Problem with personal statement of dispute","doc_count":1}]}},{"key":"Improper use of your report","doc_count":11,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Reporting company used your report improperly","doc_count":11}]}},{"key":"Dealing with your lender or servicer","doc_count":1,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Don't agree with the fees charged","doc_count":1}]}},{"key":"Problem with a company's investigation into an existing issue","doc_count":1,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Their investigation did not fix an error on your report","doc_count":1}]}}]}},"timely":{"doc_count":68,"timely":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Yes","doc_count":68}]}},"company_response":{"doc_count":68,"company_response":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Closed with explanation","doc_count":44},{"key":"Closed with non-monetary relief","doc_count":24}]}},"submitted_via":{"doc_count":68,"submitted_via":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Web","doc_count":68}]}},"company":{"doc_count":68,"company":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","doc_count":23},{"key":"Experian Information Solutions Inc.","doc_count":21},{"key":"EQUIFAX, INC.","doc_count":18},{"key":"CORELOGIC INC","doc_count":1},{"key":"Fidelity National Information Services, Inc. (FNIS)","doc_count":1},{"key":"LEXISNEXIS","doc_count":1},{"key":"National Consumer Telecom & Utilities Exchange, Inc.","doc_count":1},{"key":"Nelnet, Inc.","doc_count":1},{"key":"SANTANDER HOLDINGS USA, INC.","doc_count":1}]}},"state":{"doc_count":68,"state":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"LA","doc_count":25},{"key":"FL","doc_count":15},{"key":"GA","doc_count":9},{"key":"WI","doc_count":5},{"key":"TX","doc_count":4},{"key":"CA","doc_count":3},{"key":"DC","doc_count":3},{"key":"TN","doc_count":3},{"key":"NY","doc_count":1}]}},"company_public_response":{"doc_count":68,"company_public_response":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Company has responded to the consumer and the CFPB and chooses not to provide a public response","doc_count":45}]}},"tags":{"doc_count":68,"tags":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Servicemember","doc_count":5},{"key":"Older American","doc_count":2}]}}},"_meta":{"license":"CC0","last_updated":"2026-07-14T12:00:00-05:00","last_indexed":"2026-07-14T12:00:00-05:00","total_record_count":16441818,"is_data_stale":false,"has_data_issue":false,"break_points":{"2":[17.93064,"13401644"],"3":[15.131125,"13202085"]}}}