{"took":99,"timed_out":false,"_shards":{"total":5,"successful":5,"skipped":0,"failed":0},"hits":{"total":{"value":77,"relation":"eq"},"max_score":null,"hits":[{"_index":"complaint-public-v1","_id":"17506113","_score":27.265583,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"To Whom It May Concern : This is my formal dispute of multiple inaccurate or incomplete tradelines contained in my Experian credit file dated XX/XX/year>. These accounts contain Metro-2 structural defects, missing reporting fields, and cross-bureau inconsistencies. \n\nDisputed Accounts : XXXX. XXXX XXXX XXXX XXXXXXXX Payment history conflict Missing DOFD Missing Original Creditor XXXX. XXXX XXXX ( Closed XXXX ) Missing DOFD Incomplete and inconsistent bankruptcy coding Missing payment history grid XXXX. XXXX XXXX Public Record Linked accounts missing required Metro-2 fields Creates systemic inaccuracy connected to the public record Requested Actions : XXXX. Delete inaccurate accounts under 611 ( a ) ( 5 ). \nXXXX. Provide Method of Verification for each item. \nXXXX. Provide DOFD data under 623 ( a ) ( 5 ). \nXXXX. Correct or delete incomplete bankruptcy-linked data. \n\nSincerely, XXXX XXXX XXXX ( Signed ) To Whom It May Concern : I am disputing inaccurate, incomplete, and non-Metro-2-compliant information reported on my TransUnion file dated XX/XX/year>. \n\nDisputed Accounts : XXXX. XXXX XXXX Missing DOFD Incorrect bankruptcy coding Missing payment history XXXX. CB INDIGO / CCI Missing DOFD Payment history conflict Missing Original Creditor XXXX. XXXX XXXX Missing account type Missing DOFD Unknown payment history XXXX. XXXX XXXX XXXX  ( multiple ) No payment history Missing DOFD Missing Original Creditor XXXX XXXX XXXXXXXX XXXX XXXX  Missing DOFD Incorrect account type Missing collection reporting Requested Actions : XXXX. Delete all accounts listed under 611 ( a ) ( 5 ). \nXXXX. Provide full Method of Verification for each item. \nXXXX. Provide DOFD documentation under 623 ( a ) ( 5 ). \nXXXX. Correct or remove bankruptcy-linked accounts missing Metro-2 fields XXXX \n\nSincerely, XXXX XXXX XXXX ( Signed ) To Whom It May Concern : This letter serves as my formal dispute of multiple inaccurate, incomplete, and nonMetro-2-compliant accounts appearing on my Equifax file dated XX/XX/year>. These accounts contain structural reporting errors and missing fields that violate FCRA 607 ( b ), 611, 623 ( a ) ( 5 ), and Metro-2 reporting requirements. \n\nI dispute the following accounts : XXXX. CB INDIGO / CCI Status conflicts with payment history Missing DOFD Missing Original Creditor XXXX. XXXX XXXX XXXX  ( multiple ) Missing payment history Missing DOFD Missing Original Creditor XXXX. XXXX XXXX XXXX XXXX  Missing account type Missing balance/original balance Missing DOFD Missing payment history XXXX. XXXX XXXX XXXX XXXX  ( all ) Missing DOFD Missing account type and ECOA Missing original balance Missing payment history XXXX XXXX XXXXXXXX XXXX XXXX Missing DOFD Incorrect classification No collection history Requested Actions : XXXX. Delete all inaccurate accounts under 611 ( a ) ( 5 ). \nXXXX. Provide Method of Verification under 611 ( a ) ( 7 ). \nXXXX. Provide DOFD documentation for each account. \nXXXX. Correct or delete accounts where furnisher data is incomplete. \n\nSincerely, XXXX XXXX XXXX ( Signed )","date_sent_to_company":"2025-11-26T01:03:54.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"30016","tags":null,"has_narrative":true,"complaint_id":"17506113","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-11-26T00:52:40.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":"Account information incorrect"},"highlight":{"complaint_what_happened":["XXXX XXXX Public Record Linked accounts <em>missing</em> <em>required</em> <em>Metro</em>-2 <em>fields</em> <em>Creates</em> systemic inaccuracy connected to the public record Requested Actions : XXXX. Delete inaccurate accounts under 611 ( a ) ( 5 ). \nXXXX. Provide Method of Verification for each item. \nXXXX. Provide DOFD data under 623 ( a ) ( 5 ). \nXXXX. Correct or delete incomplete bankruptcy-linked data."]},"sort":[27.265583,"17506113"]},{"_index":"complaint-public-v1","_id":"17504364","_score":27.235073,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"To Whom It May Concern : This is my formal dispute of multiple inaccurate or incomplete tradelines contained in my Experian credit file dated XX/XX/year>. These accounts contain Metro-2 structural defects, missing reporting fields, and cross-bureau inconsistencies. \n\nDisputed Accounts : XXXX. XXXX XXXX XXXX XXXXXXXX Payment history conflict Missing DOFD Missing Original Creditor XXXX. XXXX XXXX ( Closed XXXX ) Missing DOFD Incomplete and inconsistent bankruptcy coding Missing payment history grid XXXX. XXXX XXXX Public Record Linked accounts missing required Metro-2 fields Creates systemic inaccuracy connected to the public record Requested Actions : XXXX. Delete inaccurate accounts under 611 ( a ) ( 5 ). \nXXXX. Provide Method of Verification for each item. \nXXXX. Provide DOFD data under 623 ( a ) ( 5 ). \nXXXX. Correct or delete incomplete bankruptcy-linked data. \n\nSincerely, XXXX XXXX XXXX ( Signed ) To Whom It May Concern : I am disputing inaccurate, incomplete, and non-Metro-2-compliant information reported on my TransUnion file dated XX/XX/year>. \n\nDisputed Accounts : XXXX. XXXX XXXX Missing DOFD Incorrect bankruptcy coding Missing payment history XXXX. CB INDIGO / CCI Missing DOFD Payment history conflict Missing Original Creditor XXXX. XXXX XXXX Missing account type Missing DOFD Unknown payment history XXXX. XXXX XXXX XXXX  ( multiple ) No payment history Missing DOFD Missing Original Creditor XXXX XXXX XXXXXXXX XXXX XXXX  Missing DOFD Incorrect account type Missing collection reporting Requested Actions : XXXX. Delete all accounts listed under 611 ( a ) ( 5 ). \nXXXX. Provide full Method of Verification for each item. \nXXXX. Provide DOFD documentation under 623 ( a ) ( 5 ). \nXXXX. Correct or remove bankruptcy-linked accounts missing Metro-2 fields XXXX \n\nSincerely, XXXX XXXX XXXX ( Signed ) To Whom It May Concern : This letter serves as my formal dispute of multiple inaccurate, incomplete, and nonMetro-2-compliant accounts appearing on my Equifax file dated XX/XX/year>. These accounts contain structural reporting errors and missing fields that violate FCRA 607 ( b ), 611, 623 ( a ) ( 5 ), and Metro-2 reporting requirements. \n\nI dispute the following accounts : XXXX. CB INDIGO / CCI Status conflicts with payment history Missing DOFD Missing Original Creditor XXXX. XXXX XXXX XXXX  ( multiple ) Missing payment history Missing DOFD Missing Original Creditor XXXX. XXXX XXXX XXXX XXXX  Missing account type Missing balance/original balance Missing DOFD Missing payment history XXXX. XXXX XXXX XXXX XXXX  ( all ) Missing DOFD Missing account type and ECOA Missing original balance Missing payment history XXXX XXXX XXXXXXXX XXXX XXXX Missing DOFD Incorrect classification No collection history Requested Actions : XXXX. Delete all inaccurate accounts under 611 ( a ) ( 5 ). \nXXXX. Provide Method of Verification under 611 ( a ) ( 7 ). \nXXXX. Provide DOFD documentation for each account. \nXXXX. Correct or delete accounts where furnisher data is incomplete. \n\nSincerely, XXXX XXXX XXXX ( Signed )","date_sent_to_company":"2025-11-26T01:03:52.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"30016","tags":null,"has_narrative":true,"complaint_id":"17504364","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-11-26T01:03:27.000Z","state":"GA","company_public_response":null,"sub_issue":"Account information incorrect"},"highlight":{"complaint_what_happened":["XXXX XXXX Public Record Linked accounts <em>missing</em> <em>required</em> <em>Metro</em>-2 <em>fields</em> <em>Creates</em> systemic inaccuracy connected to the public record Requested Actions : XXXX. Delete inaccurate accounts under 611 ( a ) ( 5 ). \nXXXX. Provide Method of Verification for each item. \nXXXX. Provide DOFD data under 623 ( a ) ( 5 ). \nXXXX. Correct or delete incomplete bankruptcy-linked data."]},"sort":[27.235073,"17504364"]},{"_index":"complaint-public-v1","_id":"12929370","_score":26.638449,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX XXXX XXXX XXXX XXXX XXXX LA, XXXX XXXX XX/XX/XXXX Equifax Information Services LLC XXXX XXXX XXXX XXXX, GA XXXX RE : FORMAL DEMAND FOR DELETION AND STATUTORY DAMAGES - WILLFUL METRO 2 FORMAT VIOLATIONS Account References : XXXX XXXX XXXX, XXXX XXXX XXXXXXXX XXXX, XXXXXXXX XXXX XXXX, XXXX XXXX XXXXXXXX, XXXX XXXX, XXXX, XXXX, XXXX NOTICE TO PRINCIPAL IS NOTICE TO AGENT To Whom It May Concern : This correspondence serves as my formal demand for ( 1 ) IMMEDIATE DELETION of multiple accounts with fatal Metro 2 Format defects from my credit report and ( 2 ) PAYMENT OF STATUTORY DAMAGES for each willful violation pursuant to 15 U.S.C. 1681n ( a ) ( 1 ) ( A ) which provides for damages of \" not less than {$100.00} and not more than {$1000.00} '' per violation.\n\nI have documented the following systemic and willful Metro 2 Format violations affecting multiple accounts in my credit file : 1. CRITICAL BASE SEGMENT FIELD OMISSIONS ( 79 Format Violations ) : Each account contains multiple missing required Base Segment fields, including : a ) XXXX XXXX XXXX - Missing Account Type ( Field 9 ), Terms Duration ( Field 11 ), Monthly Payment Amount ( Field 15 ), Last Payment Date ( Field 18 ) - 5 violations b ) XXXX XXXX XXXXXXXX XXXX - Missing Account Type ( Field 9 ), Terms Duration ( Field 11 ), Terms Frequency ( Field 12 ), ECOA Code ( Field 10 ), Credit Limit/Original Amount ( Field 7 ) - 6 violations c ) XXXX XXXX XXXX - Missing Last Payment Date ( Field 18 ) despite \" Last Payment '' header, Terms Duration ( Field 11 ), Monthly Payment Amount ( Field 15 ), ECOA Code ( Field 10 ) - 6 violations d ) Each additional account contains similar critical field omissions- 62 total violations 2. FATAL ACCOUNT STATUS CODE CONTRADICTIONS ( 26 Format Violations ) : a ) XXXX XXXX - Reports \" Derogatory '' status ( Code 97 ) with {$0.00} balance and closed account, while worst status is only \" Late 30 Days '' ( Code 30 ) - creating contradictory status designations- XXXX violations b ) XXXX XXXX XXXXXXXX - Reports \" Unknown '' worst status designation that does not exist in the Metro 2 Format Account Status field specification - 2 violations c ) Multiple accounts showing \" Closed '' or \" Paid '' status while simultaneously reporting serious delinquency codes- 21 violations 3. CHRONOLOGICAL SEQUENCING DEFECTS ( 14 Format Violations ) : a ) XXXX XXXX XXXXXXXX - Reports Date Closed as XXXX but Last Payment as XXXX, creating an impossible temporal scenario in Metro 2 Format that violates Field 18/Field 25 relationship requirements- 3 violations b ) XXXX - Reports improper date/status formatting that violates Base Segment field alignment requirements - 2 violations c ) Multiple accounts with improper Date Opened, Date Closed, Date Reported sequences- 9 violations 4. COLLECTION ACCOUNT XXXX SEGMENT VIOLATIONS ( 18 Format Violations ) : a ) XXXX XXXX  and XXXX XXXX XXXXXXXX - Report identical {$890.00} balances with generic \" XXXX  '' creditor designations that fail to meet XXXX Segment Original Creditor Name specificity requirements - 8 violations b ) XXXX XXXX XXXX Reports \" XXXX XXXX XXXXXXXX XXXX XXXX XXXX  with improper numeric prefix format for Original Creditor field - 10 violations 5. PAYMENT HISTORY PROFILE FIELD DEFECTS ( 36 Format Violations ) : a ) Multiple accounts report Late Payment Dates without proper Payment History Profile field population - 24 violations b ) Accounts show delinquency codes without mandated Payment Rating field synchronization - 12 violations 6. ACCOUNT IDENTIFICATION STANDARDIZATION FAILURES ( 16 Format Violations ) : a ) Accounts use inconsistent formats for account numbers, violating standardization requirements- 10 violations b ) Several accounts use improper alphanumeric prefixes ( XXXX ) that violate Account Number field specifications- 6 violations These 189 individually documented Format violations represent willful noncompliance with the Metro 2 Format specifications required by the XXXX XXXX XXXX XXXX XXXX XXXX ) and mandated by federal law. As the credit reporting industry 's designated standard, Metro 2 Format compliance is not optional but mandatory for accurate credit reporting under the FCRA.\n\nPer 15 U.S.C. 1681n ( a ), any person who \" willfully fails to comply with any requirement imposed under this subchapter with respect to any consumer is liable to that consumer '' for statutory damages of $ XXXX {$1000.00} per violation. Recent court decisions, including XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX ( XXXX XXXX. XXXX ), have confirmed that consumers can recover statutory damages without proving actual damages for willful FCRA violations.","date_sent_to_company":"2025-04-10T05:18:25.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"713XX","tags":null,"has_narrative":true,"complaint_id":"12929370","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-04-10T05:10:28.000Z","state":"LA","company_public_response":null,"sub_issue":"Information belongs to someone else"},"highlight":{"complaint_what_happened":["CRITICAL BASE SEGMENT <em>FIELD</em> OMISSIONS ( 79 Format Violations ) : Each account contains multiple <em>missing</em> <em>required</em> Base Segment <em>fields</em>, including : a ) XXXX XXXX XXXX - <em>Missing</em> Account Type ( <em>Field</em> 9 ), Terms Duration ( <em>Field</em> 11 ), Monthly Payment Amount ( <em>Field</em> 15 ), Last Payment Date ( <em>Field</em> 18 ) - 5 violations b ) XXXX XXXX XXXXXXXX XXXX - <em>Missing</em> Account Type ( <em>Field</em> 9 ), Terms Duration ( <em>Field</em> 11 ), Terms Frequency ( <em>Field</em> 12 ), ECOA Code ( <em>Field</em> 10 ), Credit Limit/Original Amount ( <em>Field</em> 7 )"]},"sort":[26.638449,"12929370"]},{"_index":"complaint-public-v1","_id":"12915897","_score":26.638449,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX XXXX XXXX XXXX XXXX XXXX LA, XXXX XXXX XX/XX/XXXX TransUnion Consumer Solutions XXXX XXXX XXXX XXXX, PA XXXX RE : FORMAL DEMAND FOR DELETION AND STATUTORY DAMAGES - WILLFUL METRO 2 FORMAT VIOLATIONS Account References : XXXX XXXX XXXX, XXXX XXXXXXXX XXXX XXXXXXXX, XXXX XXXX XXXX, XXXX XXXX XXXXXXXX, XXXX XXXX, XXXX, XXXX, XXXX NOTICE TO PRINCIPAL IS NOTICE TO AGENT To Whom It May Concern : This correspondence serves as my formal demand for ( 1 ) IMMEDIATE DELETION of multiple accounts with fatal Metro 2 Format defects from my credit report and ( 2 ) PAYMENT OF STATUTORY DAMAGES for each willful violation pursuant to 15 U.S.C. 1681n ( a ) ( 1 ) ( A ) which provides for damages of \" not less than {$100.00} and not more than {$1000.00} '' per violation.\n\nI have documented the following systemic and willful Metro 2 Format violations affecting multiple accounts in my credit file : 1. CRITICAL BASE SEGMENT FIELD OMISSIONS ( 79 Format Violations ) : Each account contains multiple missing required Base Segment fields, including : a ) XXXX XXXX XXXXXXXX - Missing Account Type ( Field 9 ), Terms Duration ( Field 11 ), Monthly Payment Amount ( Field 15 ), Last Payment Date ( Field 18 ) - 5 violations b ) XXXX XXXX XXXX XXXX - Missing Account Type ( Field 9 ), Terms Duration ( Field 11 ), Terms Frequency ( Field 12 ), ECOA Code ( Field 10 ), Credit Limit/Original Amount ( Field 7 ) - 6 violations c ) XXXX XXXX XXXXXXXX - Missing Last Payment Date ( Field 18 ) despite \" Last Payment '' header, Terms Duration ( Field 11 ), Monthly Payment Amount ( Field 15 ), ECOA Code ( Field 10 ) - 6 violations d ) Each additional account contains similar critical field omissions- 62 total violations 2. FATAL ACCOUNT STATUS CODE CONTRADICTIONS ( 26 Format Violations ) : a ) XXXX XXXXXXXX - Reports \" Derogatory '' status ( Code XXXX ) with {$0.00} balance and closed account, while worst status is only \" Late 30 Days '' ( XXXX XXXX ) - creating contradictory status designations- 3 violations b ) XXXX XXXX  XXXX - Reports \" Unknown '' worst status designation that does not exist in the Metro 2 Format Account Status field specification - 2 violations c ) Multiple accounts showing \" Closed '' or \" Paid '' status while simultaneously reporting serious delinquency codes- 21 violations 3. CHRONOLOGICAL SEQUENCING DEFECTS ( 14 Format Violations ) : a ) XXXX XXXX XXXXXXXX - Reports Date Closed as XXXX but Last Payment as XXXX, creating an impossible temporal scenario in Metro 2 Format that violates Field 18/Field 25 relationship requirements- 3 violations b ) XXXX - Reports improper date/status formatting that violates Base Segment field alignment requirements - 2 violations c ) Multiple accounts with improper Date Opened, Date Closed, Date Reported sequences- 9 violations 4. COLLECTION ACCOUNT K1 SEGMENT VIOLATIONS ( 18 Format Violations ) : a ) XXXX XXXX and XXXX XXXX XXXXXXXX - Report identical {$890.00} balances with generic \" XXXX '' creditor designations that fail to meet K1 Segment Original Creditor Name specificity requirements - 8 violations b ) XXXXXXXX XXXX - Reports \" XXXX CXXXX XXXX XXXX XXXX  '' with improper numeric prefix format for Original Creditor field - 10 violations 5. PAYMENT HISTORY PROFILE FIELD DEFECTS ( 36 Format Violations ) : a ) Multiple accounts report Late Payment Dates without proper Payment History Profile field population - 24 violations b ) Accounts show delinquency codes without mandated Payment Rating field synchronization - 12 violations 6. ACCOUNT IDENTIFICATION STANDARDIZATION FAILURES ( 16 Format Violations ) : a ) Accounts use inconsistent formats for account numbers, violating standardization requirements- 10 violations b ) Several accounts use improper alphanumeric prefixes ( XXXX ) that violate Account Number field specifications- 6 violations These 189 individually documented Format violations represent willful noncompliance with the Metro 2 Format specifications required by the XXXX XXXX XXXX XXXX XXXX XXXX ) and mandated by federal law. As the credit reporting industry 's designated standard, Metro 2 Format compliance is not optional but mandatory for accurate credit reporting under the FCRA.\n\nPer 15 U.S.C. 1681n ( a ), any person who \" willfully fails to comply with any requirement imposed under this subchapter with respect to any consumer is liable to that consumer '' for statutory damages of $ XXXX {$1000.00} per violation. Recent court decisions, including XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX ( XXXX XXXX. XXXX ), have confirmed that consumers can recover statutory damages without proving actual damages for willful FCRA violations.","date_sent_to_company":"2025-04-10T05:35:16.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"713XX","tags":null,"has_narrative":true,"complaint_id":"12915897","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-04-10T05:28:38.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":["CRITICAL BASE SEGMENT <em>FIELD</em> OMISSIONS ( 79 Format Violations ) : Each account contains multiple <em>missing</em> <em>required</em> Base Segment <em>fields</em>, including : a ) XXXX XXXX XXXXXXXX - <em>Missing</em> Account Type ( <em>Field</em> 9 ), Terms Duration ( <em>Field</em> 11 ), Monthly Payment Amount ( <em>Field</em> 15 ), Last Payment Date ( <em>Field</em> 18 ) - 5 violations b ) XXXX XXXX XXXX XXXX - <em>Missing</em> Account Type ( <em>Field</em> 9 ), Terms Duration ( <em>Field</em> 11 ), Terms Frequency ( <em>Field</em> 12 ), ECOA Code ( <em>Field</em> 10 ), Credit Limit/Original Amount ( <em>Field</em> 7 )"]},"sort":[26.638449,"12915897"]},{"_index":"complaint-public-v1","_id":"13896419","_score":26.229326,"_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 XXXX XXXX XXXX XXXXXXXX, TX XXXX ACCOUNT VIOLATION XXXX XXXX XXXX. Name Of Account : XXXX XXXX XXXX. Date Reported : Account Opened XX/XX/XXXX, Status as of XXXX XXXX. Metro 2 Compliance ( CRRG ) Violations : Violation A : Incomplete furnisher identification data - missing account identification number marked as No informado Violation B : Payment Rating code inconsistency with account status per CRRG guidelines requiring payment rating to reflect actual account standing 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 1 ) ( A ) - Furnishing inaccurate information when furnisher knows or has reasonable cause to believe that the information is inaccurate 5. Legal Description & Grounds : FCRA Section 623 ( a ) ( 1 ) ( C ) requires that if at any time a person who regularly furnishes information determines that the information provided is not complete or accurate, the furnisher must provide corrections. The incomplete account identification renders this tradeline unverifiable and demands PERMANENT REMOVAL under FCRA 611 ( a ) ( 5 ). \nACCOUNT VIOLATION XXXX XXXX XXXX. Name Of Account : XXXX XXXX. Date Reported : Account Opened XX/XX/XXXX, Status as of XXXX XXXX. Metro 2 Compliance ( CRRG ) Violations : Violation A : Current balance field showing No informado violates Metro 2 mandatory data field requirements Violation B : Account status code conflicts with payment history reporting structure 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 1 ) ( A ) - Reporting incomplete consumer information 5. Legal Description & Grounds : FCRA Section 623 ( e ) prohibits information furnishers from providing information to a CRA that they know or have reasonable cause to believe is inaccurate. Missing critical balance information makes this account unverifiable, requiring PERMANENT DELETION under FCRA 611 ( a ) ( 1 ) ( A ). \nACCOUNT VIOLATION XXXX XXXX XXXX  Name Of Account : XXXX. Date Reported : Account Opened XX/XX/XXXX, Status as of XXXX XXXX. Metro 2 Compliance ( CRRG ) Violations : Violation A : Account showing closed status but continuing monthly payment history reporting - violates Metro 2 account lifecycle reporting Violation B : Payment rating codes inconsistent with closed account status per CRRG standards 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 2 ) - Continuing to report on accounts after notification of inaccuracy 5. Legal Description & Grounds : FCRA 611 ( a ) requires agencies to conduct a reasonable reinvestigation to determine whether the disputed information is inaccurate and record the current status of the disputed information, or delete the item from the file. The contradictory account status information is factually impossible and demands IMMEDIATE PERMANENT REMOVAL. \nACCOUNT VIOLATION XXXX XXXX XXXX. Name Of Account : XXXX. Date Reported : Account XXXX XX/XX/XXXX, Status as of XXXX XXXX. Metro 2 Compliance ( CRRG ) Violations : Violation A : High balance amount ( {$400.00} ) conflicts with current balance reporting structure Violation B : Account conditions field marked No informado violates mandatory Metro 2 data completeness requirements 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 1 ) ( C ) - Failure to correct and update incomplete information 5. Legal Description & Grounds : FCRA Sections 623 ( a ) ( 1 ) ( A ) and ( a ) ( 1 ) ( C ) create Duty to Correct and Update Information requiring furnishers to provide complete accurate data. The incomplete and contradictory information violates accuracy standards and requires PERMANENT REMOVAL for non-compliance with federal reporting requirements.\n\nENFORCEMENT RECOMMENDATION : Each violation provides grounds for FCRA litigation under 15 U.S.C. 1681n ( willful non-compliance ) with statutory damages up to {$1000.00} per violation plus attorney fees. \nACCOUNT VIOLATION XXXX XXXX XXXX Name Of Account : XXXX XXXX. Date Reported : Account Opened XX/XX/XXXX, Status as of XXXX XXXX. Metro 2 Compliance ( CRRG ) Violations : Violation A : Account identification number field showing No informado violates Metro 2 mandatory data field requirements for subscriber identification Violation B : Current balance field marked No informado conflicts with Metro 2 balance reporting structure requirements 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 1 ) ( A ) - Furnishing incomplete information when furnisher has duty to provide complete and accurate data 5. Legal Description & Grounds : FCRA Section 623 ( a ) ( 1 ) ( C ) mandates furnishers must provide corrections when information is determined to be incomplete or inaccurate. The missing critical identification data renders this tradeline unverifiable and demands PERMANENT REMOVAL under FCRA 611 ( a ) ( 5 ) ( A ). \nACCOUNT VIOLATION XXXX XXXX XXXX. Name Of Account : XXXX XXXX Account # XXXX ) 2. Date Reported : Account Opened XX/XX/XXXX, Status as of XXXX XXXX. Metro 2 Compliance ( CRRG ) Violations : Violation A : Credit limit field showing No informado violates Metro 2 credit limit reporting requirements Violation B : Account identification structure contains non-standard alphanumeric format inconsistent with Metro 2 account number formatting standards 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 2 ) - Continuing to report incomplete consumer information after establishment 5. Legal Description & Grounds : FCRA 611 ( a ) requires complete reinvestigation when disputed information lacks verifiable data points. The incomplete credit limit information and non-standard account formatting violates accuracy standards requiring IMMEDIATE PERMANENT DELETION. \nACCOUNT VIOLATION XXXX XXXX XXXX. Name Of Account : XXXX XXXX ( Account # XXXX ) 2. Date Reported : Account Opened Ene 2025, Status as of XXXX XXXX Metro 2 Compliance ( CRRG ) Violations : Violation A : Account conditions field marked No informado violates mandatory Metro 2 account status reporting Violation B : Credit limit showing {$150.00} but current balance reporting structure shows conflicting payment history data 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 1 ) ( C ) - Failure to maintain complete and accurate account information 5. Legal Description & Grounds : FCRA Sections 623 ( a ) ( 1 ) ( A ) creates Duty to Provide Complete Information requiring all mandatory fields be populated with accurate data. The incomplete account conditions field makes verification impossible, requiring PERMANENT REMOVAL for Metro 2 non-compliance. \nACCOUNT VIOLATION # XXXX XXXX. Name Of Account : XXXXXXXX XXXX XXXXXXXX. ( Account # XXXX ) 2. Date Reported : Account Opened XX/XX/XXXX, Status as of XXXX XXXX. Metro 2 Compliance ( CRRG ) Violations : Violation A : Account identification field showing No informado violates Metro 2 subscriber identification requirements Violation B : Payment received field showing {$460.00} as of XX/XX/XXXX conflicts with standard Metro 2 payment amount formatting protocols 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 1 ) ( A ) - Reporting inaccurate consumer information with incomplete data fields 5. Legal Description & Grounds : FCRA Section 623 ( XXXX ) prohibits furnishers from providing information they know or have reasonable cause to believe is inaccurate. The missing identification data and non-standard payment formatting renders this account unverifiable, demanding PERMANENT DELETION under FCRA 611 ( a ) ( 1 ) ( A ). \nACCOUNT VIOLATION XXXX XXXX XXXX. Name Of Account : XXXX XXXX XXXX ( Account # XXXX ) 2. Date Reported : Account Opened XX/XX/XXXX, Status as of XXXX XXXX. Metro 2 Compliance ( CRRG ) Violations : Violation A : Current balance field showing No informado violates Metro 2 mandatory balance reporting requirements Violation B : Account responsibility field contains incomplete consumer status information 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 1 ) ( C ) - Furnishing incomplete information without proper correction procedures XXXX. Legal Description & Grounds : FCRA requires furnishers to provide complete and accurate information for all reported accounts. The missing balance information creates an unverifiable tradeline requiring PERMANENT REMOVAL for failure to meet federal reporting standards. \nACCOUNT VIOLATION XXXX XXXX XXXX. Name Of Account : XXXX XXXX Account # XXXX ) 2. Date Reported : Account Opened XXXX XXXX, Status as of XXXX XXXX. Metro 2 Compliance ( CRRG ) Violations : Violation A : Account identification field marked No informado violates Metro 2 subscriber identification protocols Violation B : Current balance field showing No informado conflicts with Metro 2 balance reporting structure 4. FCRA Violation : 15 U.S.C. 1681s-2 ( a ) ( 1 ) ( A ) - Systematic furnishing of incomplete consumer information 5. Legal Description & Grounds : FCRA Section 623 ( a ) ( 1 ) ( C ) creates mandatory duty to correct and update information when incomplete data is identified. The systematic absence of critical identification and balance data violates federal accuracy requirements, demanding IMMEDIATE PERMANENT DELETION under FCRA 611 ( a ) ( 5 ). \nTOTAL ENFORCEMENT SUMMARY : 10 accounts with multiple FCRA/Metro 2 violations providing grounds for statutory damages up to {$10000.00} plus attorney fees under 15 U.S.C. 1681n for willful non-compliance with federal reporting standards.","date_sent_to_company":"2025-06-04T12:20:32.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":"13896419","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-06-04T12:05: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":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["Legal Description & Grounds : FCRA Sections 623 ( a ) ( 1 ) ( A ) <em>creates</em> Duty to Provide Complete Information <em>requiring</em> all mandatory <em>fields</em> be populated with accurate data. The incomplete account conditions <em>field</em> makes verification impossible, <em>requiring</em> PERMANENT REMOVAL for <em>Metro</em> 2 non-compliance. \nACCOUNT VIOLATION # XXXX XXXX. Name Of Account : XXXXXXXX XXXX XXXXXXXX. ( Account # XXXX ) 2. Date Reported : Account Opened XX/XX/XXXX, Status as of XXXX XXXX."]},"sort":[26.229326,"13896419"]},{"_index":"complaint-public-v1","_id":"16207166","_score":25.81847,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"I am submitting this complaint because Equifax is inaccurately reporting a XXXX XXXX XXXX  account tradeline on my credit file. This tradeline is being reported only on Equifax and not on XXXX  or XXXX, which constitutes materially misleading and incomplete reporting. I feel like Equifax is taking advantage of me by ignoring my disputes and not fixing this error. \n\nThe Fair Credit Reporting Act ( FCRA ) requires credit reporting agencies to ensure the maximum possible accuracy of information ( 15 U.S.C. 1681e ( b ) ). Reporting a derogatory account to only one bureau creates inconsistency and violates the accuracy requirement.\n\nAdditionally, the Metro 2 format requires complete and uniform data. My forensic audit shows the following deficiencies : Missing fields : Account Type ( XXXX ), Portfolio Type ( XXXX ), Date Last Verified ( XXXX ), and Balance fields ( XXXX, XXXX ). \n\nContradictions : Creditor Remarks list Charged off account / transferred or sold, but no corresponding balance, terms, or payment history are furnished.\n\nDispute Code not reported : Despite my disputes under FCRA 611, the account is not marked as in dispute, which is a violation of Metro 2 and CFPB Regulation V ( 12 CFR 1022.42 ).","date_sent_to_company":"2025-09-26T12:56:50.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"46835","tags":null,"has_narrative":true,"complaint_id":"16207166","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-09-26T12:49:31.000Z","state":"IN","company_public_response":null,"sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["The Fair Credit Reporting Act ( FCRA ) <em>requires</em> credit reporting agencies to ensure the maximum possible accuracy of information ( 15 U.S.C. 1681e ( b ) ). Reporting a derogatory account to only one bureau <em>creates</em> inconsistency and violates the accuracy requirement.\n\nAdditionally, the <em>Metro</em> 2 format <em>requires</em> complete and uniform data."]},"sort":[25.81847,"16207166"]},{"_index":"complaint-public-v1","_id":"10825346","_score":25.01097,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"I am writing to formally dispute the inaccuracies and inconsistencies present in the reporting of the XXXX XXXX account ( # XXXX ) on my credit report. Upon careful review of my credit file, I have identified several Metro 2 compliance violations that require immediate rectification. \nIdentified Metro 2 Noncompliance Violations : 1. Incomplete Data Reporting : XXXX XXXX has omitted critical data fields such as balance, account status, payment frequency, and other required information. These omissions are in direct violation of the Metro 2 format and 15 U.S.C. 1681e ( b ), which mandates accurate and complete reporting. \n2. Inconsistent Reporting Across Bureaus : o Equifax reports the account status as \" Negative, '' while XXXX reports it as \" Positive. '' XXXX has failed to provide any status. This inconsistency is a violation of the FCRA and Metro 2 standards for uniformity in credit reporting. \n3. Incorrect Account Status : o Equifax reports a balance of {$2200.00}, which is missing from XXXX. This discrepancy fails to reflect accurate information and violates 15 U.S.C.\n\n1681e ( b ). \n4. Missing Payment Status : o XXXX has not provided any payment status, creating an incomplete and misleading representation of the account. \n5. Omission of \" Date of Last Activity '' and \" Date Reported '' : o XXXX has failed to include these crucial dates, violating Metro 2 guidelines and impacting the proper aging of the account for statute limitations. \n6. Non-Uniform Creditor Comments : o Equifax includes the comment \" Credit card, Amount in H/C column is credit limit, '' which is absent in XXXX and XXXX. This lack of uniformity misrepresents the account details and violates Metro 2 standards.","date_sent_to_company":"2024-11-16T22:05:14.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"91331","tags":null,"has_narrative":true,"complaint_id":"10825346","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2024-11-16T22:05:10.000Z","state":"CA","company_public_response":null,"sub_issue":"Information belongs to someone else"},"highlight":{"complaint_what_happened":["Upon careful review of my credit file, I have identified several <em>Metro</em> 2 compliance violations that <em>require</em> immediate rectification. \nIdentified <em>Metro</em> 2 Noncompliance Violations : 1. Incomplete Data Reporting : XXXX XXXX has omitted critical data <em>fields</em> such as balance, account status, payment frequency, and other <em>required</em> information. These omissions are in direct violation of the <em>Metro</em> 2 format and 15 U.S.C. 1681e ( b ), which mandates accurate and complete reporting. \n2."]},"sort":[25.01097,"10825346"]},{"_index":"complaint-public-v1","_id":"17245762","_score":23.905544,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"I am filing a complaint regarding the XXXX account reported on my credit file. The information that XXXX is furnishing is incomplete, inconsistent, and materially inaccurate under FCRA 623 ( a ) ( 1 ) ( A ) and Metro-2 guidelines. \n\nXXXX is reporting the account only to TransUnion, while Experian and Equifax show no data for the same account. This is inconsistent and creates an inaccurate consumer profile. \n\nXXXX is reporting the account as Collection/Chargeoff but still showing a balance owed ( {$22.00} ). A chargeoff can not legally be reported with an active balance unless they disclose the new owner of the debt, which they did not. \n\nThe account is missing critical dates, including no payment history, no date of first delinquency, no date of last payment, and no collection placement details. Many fields are reported as --. \n\nXXXX reports Placed for collection, but does not identify any collection agency, does not provide a transfer date, and does not show any validation or supporting information. \n\nBecause XXXX provides no payment history and no accurate chronological data, the derogatory reporting can not be verified. \n\nThe reporting is incomplete across all required fields in XXXX, making the derogatory status unverifiable and misleading. \n\nDue to these inaccuracies, the account appears as a derogatory collection account without the required supporting data, causing significant harm to my credit score.","date_sent_to_company":"2025-11-15T02:55:54.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"07501","tags":null,"has_narrative":true,"complaint_id":"17245762","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-11-15T02:45:28.000Z","state":"NJ","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":["The reporting is incomplete across all <em>required</em> <em>fields</em> in XXXX, making the derogatory status unverifiable and misleading. \n\nDue to these inaccuracies, the account appears as a derogatory collection account without the <em>required</em> supporting data, causing significant harm to my credit score."]},"sort":[23.905544,"17245762"]},{"_index":"complaint-public-v1","_id":"17244459","_score":23.896206,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"I am filing a complaint regarding the XXXX account reported on my credit file. The information that XXXX is furnishing is incomplete, inconsistent, and materially inaccurate under FCRA 623 ( a ) ( 1 ) ( A ) and Metro-2 guidelines. \n\nXXXX is reporting the account only to TransUnion, while Experian and Equifax show no data for the same account. This is inconsistent and creates an inaccurate consumer profile. \n\nXXXX is reporting the account as Collection/Chargeoff but still showing a balance owed ( {$22.00} ). A chargeoff can not legally be reported with an active balance unless they disclose the new owner of the debt, which they did not. \n\nThe account is missing critical dates, including no payment history, no date of first delinquency, no date of last payment, and no collection placement details. Many fields are reported as --. \n\nXXXX reports Placed for collection, but does not identify any collection agency, does not provide a transfer date, and does not show any validation or supporting information. \n\nBecause XXXX provides no payment history and no accurate chronological data, the derogatory reporting can not be verified. \n\nThe reporting is incomplete across all required fields in XXXX, making the derogatory status unverifiable and misleading. \n\nDue to these inaccuracies, the account appears as a derogatory collection account without the required supporting data, causing significant harm to my credit score.","date_sent_to_company":"2025-11-19T12:18:40.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"07501","tags":null,"has_narrative":true,"complaint_id":"17244459","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-11-15T02:55:25.000Z","state":"NJ","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":["The reporting is incomplete across all <em>required</em> <em>fields</em> in XXXX, making the derogatory status unverifiable and misleading. \n\nDue to these inaccuracies, the account appears as a derogatory collection account without the <em>required</em> supporting data, causing significant harm to my credit score."]},"sort":[23.896206,"17244459"]},{"_index":"complaint-public-v1","_id":"17813645","_score":23.384443,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX is furnishing information to Experian in a manner that is inaccurate, incomplete, and misleading under the Fair Credit Reporting Act ( FCRA ) and Metro 2 reporting guidelines. I am not disputing the balance owed. I am disputing the accuracy and integrity of the reporting fields that determine the age, timeline, and severity of the negative account history.\n\nThe payment history grid displays derogatory codes across multiple years that do not correspond to the actual timeline of the account. These codes appear in months where no payments were scheduled or due and do not match the accounts last actual activity. This creates a misleading depiction of the delinquency pattern, which does not comply with FCRA 623 ( a ) ( 1 ) ( A ), which prohibits furnishing information that is inaccurate or creates a materially misleading impression of the consumers credit history.\n\nIn addition, the tradeline does not include the required Date of First Delinquency ( DOFD ). Under FCRA 623 ( a ) ( 5 ), furnishers must report DOFD for accounts that have been charged off so the credit bureaus can correctly determine the reporting period. Without DOFD, the tradeline is incomplete and can not be evaluated for proper aging, which impacts the accuracy required under FCRA 602 ( a ) and the obligation to report complete information under FCRA 623 ( a ) ( 2 ).\n\nThe account also reflects a status updated date well beyond the actual last activity date, and the payment history structure appears to extend the delinquency period into later years in a way that does not match the factual progression of the loan. This creates an impression of more recent negative activity than actually occurred, which is misleading and harmful to my credit profile. Under FCRA 607 ( b ), information must be both accurate and presented in a manner that does not distort or misrepresent the timeline of events.\n\nBecause these issues relate to the structure of the reporting itself, including missing required fields, inaccurate payment history mapping, and misleading date progression, they can not be corrected through simple updates and am requesting deletion. These are systemic inaccuracies that affect fundamental fields used by the bureaus to calculate severity, recency, and scoring impact.","date_sent_to_company":"2025-12-07T20:39:37.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"22031","tags":null,"has_narrative":true,"complaint_id":"17813645","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-12-07T20:39:12.000Z","state":"VA","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":["Because these issues relate to the structure of the reporting itself, including <em>missing</em> <em>required</em> <em>fields</em>, inaccurate payment history mapping, and misleading date progression, they can not be corrected through simple updates and am requesting deletion. These are systemic inaccuracies that affect fundamental <em>fields</em> used by the bureaus to calculate severity, recency, and scoring impact."]},"sort":[23.384443,"17813645"]},{"_index":"complaint-public-v1","_id":"14080909","_score":22.849045,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"This is my third formal complaint regarding the inaccurate and misleading reporting of a tradeline from XXXX XXXX XXXX XXXX XXXX on my Equifax credit file. Despite two prior investigations, Equifax continues to report this account in a manner that is incomplete, ambiguous, and noncompliant with Metro 2 formatting requirements and federal law, including : FCRA 1681i ( a ) ( 5 ) ( A ) Failure to delete or correct inaccurate or incomplete information after reinvestigation FCRA 1681s-2 ( b ) ( 1 ) Furnishers failure to conduct a lawful and reasonable investigation FCRA 1681e ( b ) Failure to follow reasonable procedures to ensure maximum possible accuracy FTC Staff Commentary and Metro 2 guidelines, which require all data fields to be fully and accurately populated including current status, scheduled monthly payment, and worst delinquency history The Following Violations Persist on My Equifax Report XXXX Account reflects a {$0.00} balance with perfect payment history and no delinquencies, yet multiple fields are marked as No Info Account was reported closed as of XX/XX/XXXX with no reason given ( voluntary/involuntary/adverse/inactive closure unknown ) Missing values under key Metro 2 fields such as : Scheduled Monthly Payment ( Field Base Segment 66 ) Account Status ( Field Base Segment 17 ) Payment Rating ( Field 76 ) Payment History Profile ( Field 77 ) These empty fields violate Metro 2 compliance and create the appearance of derogatory activity or adverse action, even though the account had perfect performance Demand for Verification Disclosure ( per FCRA 1681i ( a ) ( 6 ) ( B ) ( iii ) ) : Under FCRA, I have the legal right to know how Equifax verified this information, and with whom . To date, no documentation has been provided by Equifax or the furnisher. I hereby demand : 1. A detailed description of the procedures used to verify this account, per FCRA 1681i ( a ) ( 7 ) 2. The name, address, and contact details of any furnisher ( s ) Equifax contacted 3. A copy of the verification documentation provided by the furnisher under 15 U.S.C. 1681s-2 ( b ) ( 1 ) ( B ) Failure to provide these constitutes willful noncompliance, and I reserve the right to pursue civil remedies under FCRA 1681n ( willful noncompliance ) and 1681o ( negligent noncompliance ).\n\nSupporting Case Law : Cushman v. Trans Union Corp., 115 F.3d 220 ( 3d Cir. 1997 ) Reinforces that CRAs can not merely parrot information from furnishers without independent investigation.\n\nDennis v. BEH-1, LLC, 520 F.3d 1066 ( 9th Cir. 2008 ) Confirms failure to provide a complete reporting profile constitutes inaccurate reporting.\n\nKoropoulos v. Credit Bureau , Inc., 734 F.2d 37 ( D.C. Cir. 1984 ) Data that is misleading, even if technically accurate, is still actionable under the FCRA.","date_sent_to_company":"2025-06-14T13:22:46.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"34743","tags":null,"has_narrative":true,"complaint_id":"14080909","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-06-14T13:04:03.000Z","state":"FL","company_public_response":null,"sub_issue":"Account information incorrect"},"highlight":{"complaint_what_happened":[") <em>Missing</em> values under key <em>Metro</em> 2 <em>fields</em> such as : Scheduled Monthly Payment ( <em>Field</em> Base Segment 66 ) Account Status ( <em>Field</em> Base Segment 17 ) Payment Rating ( <em>Field</em> 76 ) Payment History Profile ( <em>Field</em> 77 ) These empty <em>fields</em> violate <em>Metro</em> 2 compliance and <em>create</em> the appearance of derogatory activity or adverse action, even though the account had perfect performance Demand for Verification Disclosure ( per FCRA 1681i ( a ) ( 6 ) ( B ) ( iii ) ) : Under FCRA, I have the legal right to know how"]},"sort":[22.849045,"14080909"]},{"_index":"complaint-public-v1","_id":"17630785","_score":22.712439,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Complaint Against : Experian Information Services & XXXX Summary : I am filing this complaint because Experian and XXXX failed to conduct a reasonable reinvestigation under FCRA 611 ( a ), and the XXXX XXXX continues to reflect misleading and incomplete information that can not be verified. \n\nFull Description : I have disputed the XXXX tradeline with Experian twice due to inconsistent and incomplete reporting. Experian repeatedly marked the account updated and then remains without correcting any of the inaccurate fields or providing any evidence that a reasonable reinvestigation occurred, violating FCRA 611 ( a ). \n\nXXXX continues to report the account as charged off/sold to XXXX XXXX XXXX XXXX but XXXX XXXX has been removed from my credit report for inaccurate reporting and has no active tradeline, contact, or updated ownership information. This creates a materially misleading and incomplete status, violating FCRA 607 ( b ) and 623 ( a ) ( 1 ) ( A ). A furnisher can not direct consumers to a debt owner that does not appear anywhere on their credit report and can not be verified.\n\nDespite my disputes, Experian made no corrections, added no dispute notation, and did not address the missing, contradictory, or incomplete Metro 2 fields. XXXX also provided no documentation validating the accuracy of what they are furnishing, nor did they correct the misleading sold status after the buyers tradeline was removed. Both parties are continuing to furnish or confirm information that can not be properly certified as accurate or complete. \n\nThis is an unreasonable reinvestigation by Experian and an ongoing furnishing violation by XXXX. \nI am requesting CFPB intervention to ensure compliance with FCRA, Metro 2 guidelines, and to require deletion of this tradeline because it can not be accurately verified.","date_sent_to_company":"2025-12-02T15:01:33.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"33033","tags":null,"has_narrative":true,"complaint_id":"17630785","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-12-02T15:01:12.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":["This <em>creates</em> a materially misleading and incomplete status, violating FCRA 607 ( b ) and 623 ( a ) ( 1 ) ( A ). A furnisher can not direct consumers to a debt owner that does not appear anywhere on their credit report and can not be verified.\n\nDespite my disputes, Experian made no corrections, added no dispute notation, and did not address the <em>missing</em>, contradictory, or incomplete <em>Metro</em> 2 <em>fields</em>."]},"sort":[22.712439,"17630785"]},{"_index":"complaint-public-v1","_id":"15066133","_score":22.60896,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"To Whom It May Concern, I am filing a formal complaint and demanding immediate correction or deletion of the XXXX XXXX XXXX tradeline currently reported on my Equifax credit file. After reviewing the report, I have identified multiple violations of the Fair Credit Reporting Act ( FCRA ) and the Metro 2 reporting standards adopted by Equifax. \n\nACCOUNT DETAILS Furnisher : XXXX XXXX XXXX Original Creditor : XXXX XXXX XXXX XXXX. \n\nAccount Number ( Last 4 ) : XXXX Reported by : Equifax Date Opened : XX/XX/XXXX Date of First Delinquency : XX/XX/XXXX Reported Balance : {$620.00} Account Status : Closed / Collection Date of Last Activity : Missing VIOLATIONS 1. Metro 2 Violation Missing Date of Last Activity Equifax is reporting this account with no Date of Last Activity ( DLA ). DLA is a required XXXX XXXX field and is essential to properly age and score the account. Its absence makes the data materially incomplete, in direct violation of FCRA 623 ( a ) ( 1 ) ( A ) and 1681e ( b ).\n\nDespite the account being Closed, Equifax continues to report a recurring monthly balance with no DLA, which simulates new activity and is misleading.\n\n2. Metro 2 Violation Negative Available Credit on a Collection The report also shows a negative available credit ( - {$620.00} ) on this collection tradeline. Collection accounts should not report revolving fields like available credit, high credit, or credit limit these fields apply to active open-end credit products, not purchased charged-off debt. \n\nThis inflates my utilization ratio and is misleading to both scoring models and lenders. This violates Metro 2 guidelines and FCRA 623 ( a ) ( 1 ) ( A ).\n\n3. Metro 2 / FCRA Violation Monthly Balance Updates on a Closed Account Equifax is allowing this Closed collection account to update the same {$620.00} balance every month with no payments or activity. This is a form of re-aging and creates the false appearance of an active, recent debt, which is inaccurate and deceptive under FCRA 623 ( a ) ( 1 ) ( A ) and 1681e ( b ).\n\n4. False Last Payment Date Field Without Any Actual Payments The report shows a \" last payment date '' without documenting any payment history. No payment was made, and this field should be blank. This is a fabricated data point and violates the standard of maximum possible accuracy under FCRA 1681e ( b ). \nAdditionally, I request the method of verification for the continued reporting of this account per FCRA 1681i ( a ) ( 6 ) ( B ) ( iii ), including all documents, procedures, and data relied upon.\n\nPlease note that courts have held that inaccurate or incomplete credit reporting that misrepresents the nature or status of a debt is actionable under the FCRA, including when Metro 2 standards are ignored : Cushman v. TransUnion Corp., 115 F.3d 220 ( 3d Cir. 1997 ) : Credit reporting agencies must go beyond a mere parrot of the furnishers information ; failure to do so violates FCRA 1681i. \n\nSeamans v. Temple University, 744 F.3d 853 ( 3d Cir. 2014 ) : Furnishers may be liable under FCRA 1681s-2 ( b ) if they fail to correct inaccurate data after notice from a CRA.\n\nJohnson v. MBNA America Bank, NA, 357 F.3d 426 ( 4th Cir. 2004 ) : Furnishers and bureaus must conduct reasonable investigations including examining the specific disputes raised by the consumer. \n\nThese rulings establish that both data furnishers and CRAs can be held liable when they continue to report incomplete, inaccurate, or misleading information including violations of Metro 2 formatting that materially distort account data.","date_sent_to_company":"2025-08-05T01:04:17.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"77407","tags":null,"has_narrative":true,"complaint_id":"15066133","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-08-05T00:40:34.000Z","state":"TX","company_public_response":null,"sub_issue":"Account information incorrect"},"highlight":{"complaint_what_happened":["<em>Metro</em> 2 Violation <em>Missing</em> Date of Last Activity Equifax is reporting this account with no Date of Last Activity ( DLA ). DLA is a <em>required</em> XXXX XXXX <em>field</em> and is essential to properly age and score the account. Its absence makes the data materially incomplete, in direct violation of FCRA 623 ( a ) ( 1 ) ( A ) and 1681e ( b ).\n\nDespite the account being Closed, Equifax continues to report a recurring monthly balance with no DLA, which simulates new activity and is misleading.\n\n2."]},"sort":[22.60896,"15066133"]},{"_index":"complaint-public-v1","_id":"16577506","_score":22.052544,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"TransUnion Dispute Letter DEMAND FOR IMMEDIATE DELETION AND FORMAL CONSUMER DISPUTE & REINVESTIGATION REQUEST NON-COMPLIANCE NOTICE TO : TRANSUNION ( TU ) Pursuant to the Fair Credit Reporting Act ( FCRA ) Date : XX/XX/XXXX Consumer Identification Field Detail Consumer Name : XXXX XXXX XXXX XXXX of Birth : XX/XX/XXXX Address : XXXX XXXX XXXX, XXXX, TX XXXX Phone : XXXX Recipient ( Mailing Address ) TransUnion LLC Consumer Dispute Center XXXX XXXX XXXX XXXX XXXX, PA XXXX I. Controlling Law ( applies to all items ) Your obligations as a Consumer Reporting Agency ( CRA ) are non-delegable and mandatory.\n\nFCRA 607 ( b ) ( 15 U.S.C. 1681e ( b ) ) TransUnion must assure maximum possible accuracy and possess objective evidence of the information 's correctness.\n\nFCRA 611 ( a ) A reasonable reinvestigation is required and must not simply \" parrot '' a furnisher 's response ( XXXX XXXX Trans Union, XXXX XXXX XXXX ( XXXX Cir. XXXX ) ). The reinvestigation must be meaningful and objective ( XXXX v. XXXX, XXXX XXXX XXXX ( XXXX Cir. XXXX ) ). \nFCRA 611 ( a ) ( 5 ) If information is inaccurate, incomplete, or unverifiable through original-source documents, you MUST DELETE the disputed item immediately.\n\nFCRA 611 ( a ) ( 6 ) ( B ) ( iii ) You are mandated to disclose the Method of Verification ( MoV ), including the precise procedures and specific underlying records relied upon.\n\nFCRA 623 ( a ) ( 5 ) Furnishers must report the correct Date of First Delinquency ( DOFD ) for calculating the mandatory reporting period under FCRA 605 ( a ) & 605 ( c ). \nSepulvado v. XXXX, XXXX XXXX XXXX ( XXXX Cir. XXXX ) : XXXX based on conflicting or unreliable data is insufficient ; the CRA must have objective evidence to support the reported information.\n\nMetro 2 Data Fields : The accuracy of these fields is central to FCRA compliance : Field 25 ( DOFD ), Field 17 ( Account Status ), Fields 7173 ( Payment History Profile ), Field 11 ( Payment Rating ), Field 26 ( Past Due Amount ), Portfolio Type, and Date of Account Information.\n\n\nII. Disputed Items ( TransUnion ) & DEMAND FOR DELETION The burden of verification rests entirely upon TransUnion. Verification must be based on original source documents and a complete Metro 2 record. Absent this, you MUST DELETE the items as unverifiable. ITEM I NATLCRSYS ( Original Creditor : XXXX XXXX XXXX  ) Violations Misclassification / Missing DOFD / Data Integrity : This item is erroneously displayed as an Open account when the nature of the debt is a collection. This misclassification violates FCRA 607 ( b ) and 623 standards, as collections must be furnished with Portfolio Type = C and a valid Account Status ( Field 17 ). Critically, the DOFD ( Field 25 ) is missing, preventing validation of the 605 obsolescence period.\n\nDEMAND : DELETE this tradeline in its entirety under 611 ( a ) ( 5 ) if the furnisher can not provide contemporaneous original source documents establishing the amount, date, my agreement to pay, and the complete Metro 2 certification including : Portfolio Type C, Field 17 ( Account Status ), and Field 25 ( DOFD ).\n\nProvide the MoV ( 611 ( a ) ( 6 ) ( B ) ( iii ) ) detailing the exact name of the individual who conducted the review, the precise procedures used, and copies of all underlying documents and Metro 2 segments relied upon. \nITEM XXXX Synerprise Consulting ( XXXX XXXX XXXX XXXX Violations Misclassification / Missing DOFD / Impermissible Data : This is a third-party collection, yet it is reported as an Open account. The XXXX XXXX XXXX is not evidenced, which is a per se violation of 623 ( a ) ( 5 ). Furthermore, a third-party collection MUST NOT report a revolving/installment Payment History Profile ( Fields 7173 ) or a separate Past Due bucket ( Field 26 ). The reporting of an unsubstantiated debt with a flawed format constitutes willful noncompliance.\n\nDEMAND : IMMEDIATE DELETION under 611 ( a ) ( 5 ). The account is unverifiable if the furnisher can not substantiate my agreement to pay this specific amount, the original contract, and a corrected collection Metro 2 segment including XXXX XXXX XXXX and a documented Field 25 XXXX. \nProduce the complete e-OSCAR/ACDV/AUD logs covering this dispute and ALL prior updates, including message IDs, reason codes, and timestamps. \nITEM XXXX XXXX XXXXXXXX ( Closed Charge-Off ) Violations Past-Due Misuse / Cross-Bureau Conflicts/ Missing DOFD : The reporting of Past Due XXXX {$0.00} on a closed/charged-off account is a direct violation of Metro 2 standards, where Field 26 ( Past Due ) must be {$0.00} after charge-off.\n\nSignificant balance and date inconsistencies ( balance figures and DLP/DLA ) exist across bureaus, violating your duty of maximum possible accuracy under 607 ( b ). \nThe XXXX ( Field 25 ) is not disclosed, which is a non-negotiable requirement for consumer validation of the 605 reporting period.\n\nDEMAND : IMMEDIATE DELETION under 611 ( a ) ( 5 ) due to unresolvable accuracy issues and missing DOFD.\n\nAlternatively, provide a MoV with : the original account ledger showing the transaction history up to charge-off ; the corrected {$0.00} Past Due status ; and the documented Field 25 XXXX that matches all bureaus, or face liability for negligent/willful noncompliance. \n\nXXXX. REQUIRED DISCLOSURES WITH YOUR RESULTS For any item you decide to retain, you must provide the following objective evidence and documentation. A generic \" verified by furnisher '' response is insufficient and constitutes willful non-compliance per XXXX. \nMethod of XXXX ( XXXX ( a ) ( XXXX ) ( B ) ( iii ) ) : The name/title of the verifying party, the precise procedure used ( not XXXX ), and copies of the specific underlying source documents from the furnisher that you reviewed and relied upon for your conclusion. \nExact XXXX XXXX Data : Copies of the complete electronic file segment ( raw data ) on file with TransUnion and relied upon, specifically including : Fields 25, 17, 11, 26, 7173 ( if used ), Portfolio Type, Date of Account Information, and all Special Comment codes. \nXXXX XXXX XXXX : The entire e-XXXX XXXX XXXX ( message IDs, reason codes, timestamps ) for my disputes and all prior updates/changes since the tradeline 's inception. \nFurnisher Itemization : Documentary itemization from the original creditor ( OC ) or furnisher sufficient to establish the debt 's identity, amount, and aging ( e.g., XXXX XXXX, or for medical, claim number ( s ) and Date of Service no diagnosis/procedure data ). \nReinsertion Safeguards : If any item is deleted, you must secure the certification required by 611 ( a ) ( 5 ) ( B ) and provide written notice before any reinsertion attempt.\n\nIV. TIMING, PRESERVATION, AND REMEDIES This is my formal written dispute under FCRA 611 ( a ). You have 30 days from the date of receipt to complete a reasonable reinvestigation and mail your complete results and MoV to the address above. \nLITIGATION HOLD NOTICE : You are hereby notified to preserve all records related to these disputes, including all furnisher communications, Metro 2 file segments, internal investigation notes, e-OSCAR logs, and MoV disclosures. This preservation requirement is mandatory in anticipation of litigation.\n\nFailure to fully comply with your duties under the FCRA will result in the immediate filing of a CFPB complaint and an evaluation of claims for willful and/or negligent noncompliance under FCRA 616 and 617, which creates liability for actual damages, statutory damages, punitive damages, attorney 's fees, and costs. \nSincerely, XXXX XXXX XXXX Enclosures : Government ID ; proof of current address ; highlighted report pages ; any supporting itemization.","date_sent_to_company":"2025-10-14T11:36:30.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"77091","tags":null,"has_narrative":true,"complaint_id":"16577506","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-10-14T11:25:22.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":["<em>Metro</em> 2 Data <em>Fields</em> : The accuracy of these <em>fields</em> is central to FCRA compliance : <em>Field</em> 25 ( DOFD ), <em>Field</em> 17 ( Account Status ), <em>Fields</em> 7173 ( Payment History Profile ), <em>Field</em> 11 ( Payment Rating ), <em>Field</em> 26 ( Past Due Amount ), Portfolio Type, and Date of Account Information.\n\n\nII. Disputed Items ( TransUnion ) & DEMAND FOR DELETION The burden of verification rests entirely upon TransUnion. Verification must be based on original source documents and a complete <em>Metro</em> 2 record."]},"sort":[22.052544,"16577506"]},{"_index":"complaint-public-v1","_id":"14910687","_score":21.35939,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX XXXXXXXX XXXX XXXX XXXX XXXX il XXXX Date : XX/XX/XXXX RE : Formal Dispute of XXXX  ACCOUNT Metro 2 Compliance Demand Account Number : XXXX Reporting Creditor : XXXX TransUnion Report Date : XX/XX/XXXX To Whom It May Concern, This letter serves as a formal dispute under the Fair Credit Reporting Act ( FCRA ), Section 611 [ 15 U.S.C. 1681i ] and demands that you immediately remove or correct the XXXX account listed above due to violations of both Metro 2 reporting standards and the FCRA. \n\nUpon detailed review, the data being reported is factually and technically inaccurate, and you are currently in violation of Metro 2 data furnishing guidelines, which your company is required to adhere to under your credit data furnishing agreements and obligations under federal law.\n\nSpecific Compliance Failures Include : 1. Charge-Off Balance vs. High Balance Conflict : Reporting a charge-off with a balance of {$8700.00} while also stating the high balance as {$8100.00} is a direct contradiction and inconsistent with Metro 2 Field 17 & 18 requirements, which demand data accuracy and internal consistency. You can not report a charge-off amount greater than the high balance. This is materially misleading and creates a false impression of the consumers debt. \n2. Missing and Incomplete Payment History : According to Metro 2 Format Layout and FCRA 602 ( A ), furnishers must maintain complete and accurate reporting, including valid month-by-month payment history. The absence of data for multiple months and years ( N/A across XXXX ) violates the Metro 2 Base Segment Field 39 ( Account Status History ) and misrepresents the tradeline. \nXXXX. Failure to Report Accurate Delinquency Timeline ( Compliance Condition Codes ) : There is a discrepancy in delinquency reporting some months show no data, others show charged-off remarks. These contradictions indicate failure to furnish consistent Compliance Condition Codes, violating FCRA 623 ( a ) ( 1 ) ( A ) and Metro 2 Segment Field 25 ( Account Status Code ).\n\n4. Re-aging and Activity Date Manipulation : Your records reflect Last Activity as XX/XX/XXXX with a charge-off reported in XXXX more than 180 days after the initial delinquency, possibly violating the 7-year limit under FCRA 605 ( a ) if inaccurately re-aged. This behavior is flagged as abusive under CFPB guidance and undermines lawful consumer rights.\n\nDemand for Immediate Action : In accordance with 15 U.S.C. 1681i and Metro 2 Compliance Procedures, you are hereby notified to : 1. Immediately DELETE this XXXX  tradeline from my TransUnion credit file for failure to meet compliance and accuracy standards ; 2. Provide a full reinvestigation within 30 calendar days as mandated by the FCRA ; 3. Send me a copy of the results of your reinvestigation, including the data source, method used, and any documentation XXXX provided in support of the accounts accuracy. \n\nIf you fail to remove this account, I will file complaints with the Federal Trade Commission ( FTC ), and pursue legal action under FCRA 616 and 617, seeking statutory damages for your noncompliance.\n\nThis is your final opportunity to correct the illegal and misleading data being reported. Your failure to ensure full Metro 2 and FCRA compliance constitutes willful negligence. \n\nSincerely, XXXX XXXX","date_sent_to_company":"2025-07-27T16:04:42.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"60901","tags":null,"has_narrative":true,"complaint_id":"14910687","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-07-27T15:56:02.000Z","state":"IL","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>Missing</em> and Incomplete Payment History : According to <em>Metro</em> 2 Format Layout and FCRA 602 ( A ), furnishers must maintain complete and accurate reporting, including valid month-by-month payment history. The absence of data for multiple months and years ( N/A across XXXX ) violates the <em>Metro</em> 2 Base Segment <em>Field</em> 39 ( Account Status History ) and misrepresents the tradeline. \nXXXX."]},"sort":[21.35939,"14910687"]},{"_index":"complaint-public-v1","_id":"14910144","_score":21.34837,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX XXXXXXXX XXXX XXXX XXXX XXXX il XXXX Date : XX/XX/XXXX RE : Formal Dispute of XXXX  ACCOUNT Metro 2 Compliance Demand Account Number : XXXX Reporting Creditor : XXXX TransUnion Report Date : XX/XX/XXXX To Whom It May Concern, This letter serves as a formal dispute under the Fair Credit Reporting Act ( FCRA ), Section 611 [ 15 U.S.C. 1681i ] and demands that you immediately remove or correct the XXXX account listed above due to violations of both Metro 2 reporting standards and the FCRA. \n\nUpon detailed review, the data being reported is factually and technically inaccurate, and you are currently in violation of Metro 2 data furnishing guidelines, which your company is required to adhere to under your credit data furnishing agreements and obligations under federal law.\n\nSpecific Compliance Failures Include : 1. Charge-Off Balance vs. High Balance Conflict : Reporting a charge-off with a balance of {$8700.00} while also stating the high balance as {$8100.00} is a direct contradiction and inconsistent with Metro 2 Field 17 & 18 requirements, which demand data accuracy and internal consistency. You can not report a charge-off amount greater than the high balance. This is materially misleading and creates a false impression of the consumers debt. \n2. Missing and Incomplete Payment History : According to Metro 2 Format Layout and FCRA 602 ( A ), furnishers must maintain complete and accurate reporting, including valid month-by-month payment history. The absence of data for multiple months and years ( N/A across XXXX ) violates the Metro 2 Base Segment Field 39 ( Account Status History ) and misrepresents the tradeline. \nXXXX. Failure to Report Accurate Delinquency Timeline ( Compliance Condition Codes ) : There is a discrepancy in delinquency reporting some months show no data, others show charged-off remarks. These contradictions indicate failure to furnish consistent Compliance Condition Codes, violating FCRA 623 ( a ) ( 1 ) ( A ) and Metro 2 Segment Field 25 ( Account Status Code ).\n\n4. Re-aging and Activity Date Manipulation : Your records reflect Last Activity as XX/XX/XXXX with a charge-off reported in XXXX more than 180 days after the initial delinquency, possibly violating the 7-year limit under FCRA 605 ( a ) if inaccurately re-aged. This behavior is flagged as abusive under CFPB guidance and undermines lawful consumer rights.\n\nDemand for Immediate Action : In accordance with 15 U.S.C. 1681i and Metro 2 Compliance Procedures, you are hereby notified to : 1. Immediately DELETE this XXXX  tradeline from my TransUnion credit file for failure to meet compliance and accuracy standards ; 2. Provide a full reinvestigation within 30 calendar days as mandated by the FCRA ; 3. Send me a copy of the results of your reinvestigation, including the data source, method used, and any documentation XXXX provided in support of the accounts accuracy. \n\nIf you fail to remove this account, I will file complaints with the Federal Trade Commission ( FTC ), and pursue legal action under FCRA 616 and 617, seeking statutory damages for your noncompliance.\n\nThis is your final opportunity to correct the illegal and misleading data being reported. Your failure to ensure full Metro 2 and FCRA compliance constitutes willful negligence. \n\nSincerely, XXXX XXXX","date_sent_to_company":"2025-07-27T16:04:42.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"60901","tags":null,"has_narrative":true,"complaint_id":"14910144","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-07-27T16:04:15.000Z","state":"IL","company_public_response":null,"sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["<em>Missing</em> and Incomplete Payment History : According to <em>Metro</em> 2 Format Layout and FCRA 602 ( A ), furnishers must maintain complete and accurate reporting, including valid month-by-month payment history. The absence of data for multiple months and years ( N/A across XXXX ) violates the <em>Metro</em> 2 Base Segment <em>Field</em> 39 ( Account Status History ) and misrepresents the tradeline. \nXXXX."]},"sort":[21.34837,"14910144"]},{"_index":"complaint-public-v1","_id":"14910145","_score":21.313194,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"XXXX XXXXXXXX XXXX XXXX XXXX XXXX il XXXX Date : XX/XX/XXXX RE : Formal Dispute of XXXX  ACCOUNT Metro 2 Compliance Demand Account Number : XXXX Reporting Creditor : XXXX TransUnion Report Date : XX/XX/XXXX To Whom It May Concern, This letter serves as a formal dispute under the Fair Credit Reporting Act ( FCRA ), Section 611 [ 15 U.S.C. 1681i ] and demands that you immediately remove or correct the XXXX account listed above due to violations of both Metro 2 reporting standards and the FCRA. \n\nUpon detailed review, the data being reported is factually and technically inaccurate, and you are currently in violation of Metro 2 data furnishing guidelines, which your company is required to adhere to under your credit data furnishing agreements and obligations under federal law.\n\nSpecific Compliance Failures Include : 1. Charge-Off Balance vs. High Balance Conflict : Reporting a charge-off with a balance of {$8700.00} while also stating the high balance as {$8100.00} is a direct contradiction and inconsistent with Metro 2 Field 17 & 18 requirements, which demand data accuracy and internal consistency. You can not report a charge-off amount greater than the high balance. This is materially misleading and creates a false impression of the consumers debt. \n2. Missing and Incomplete Payment History : According to Metro 2 Format Layout and FCRA 602 ( A ), furnishers must maintain complete and accurate reporting, including valid month-by-month payment history. The absence of data for multiple months and years ( N/A across XXXX ) violates the Metro 2 Base Segment Field 39 ( Account Status History ) and misrepresents the tradeline. \nXXXX. Failure to Report Accurate Delinquency Timeline ( Compliance Condition Codes ) : There is a discrepancy in delinquency reporting some months show no data, others show charged-off remarks. These contradictions indicate failure to furnish consistent Compliance Condition Codes, violating FCRA 623 ( a ) ( 1 ) ( A ) and Metro 2 Segment Field 25 ( Account Status Code ).\n\n4. Re-aging and Activity Date Manipulation : Your records reflect Last Activity as XX/XX/XXXX with a charge-off reported in XXXX more than 180 days after the initial delinquency, possibly violating the 7-year limit under FCRA 605 ( a ) if inaccurately re-aged. This behavior is flagged as abusive under CFPB guidance and undermines lawful consumer rights.\n\nDemand for Immediate Action : In accordance with 15 U.S.C. 1681i and Metro 2 Compliance Procedures, you are hereby notified to : 1. Immediately DELETE this XXXX  tradeline from my TransUnion credit file for failure to meet compliance and accuracy standards ; 2. Provide a full reinvestigation within 30 calendar days as mandated by the FCRA ; 3. Send me a copy of the results of your reinvestigation, including the data source, method used, and any documentation XXXX provided in support of the accounts accuracy. \n\nIf you fail to remove this account, I will file complaints with the Federal Trade Commission ( FTC ), and pursue legal action under FCRA 616 and 617, seeking statutory damages for your noncompliance.\n\nThis is your final opportunity to correct the illegal and misleading data being reported. Your failure to ensure full Metro 2 and FCRA compliance constitutes willful negligence. \n\nSincerely, XXXX XXXX","date_sent_to_company":"2025-07-27T16:04:45.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"60901","tags":null,"has_narrative":true,"complaint_id":"14910145","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-07-27T16:04:15.000Z","state":"IL","company_public_response":null,"sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["<em>Missing</em> and Incomplete Payment History : According to <em>Metro</em> 2 Format Layout and FCRA 602 ( A ), furnishers must maintain complete and accurate reporting, including valid month-by-month payment history. The absence of data for multiple months and years ( N/A across XXXX ) violates the <em>Metro</em> 2 Base Segment <em>Field</em> 39 ( Account Status History ) and misrepresents the tradeline. \nXXXX."]},"sort":[21.313194,"14910145"]},{"_index":"complaint-public-v1","_id":"12455018","_score":20.52873,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"I am filing this complaint against Experian, Equifax, and TransUnion for failing to properly investigate, validate, and correct inaccurate and non-compliant information on my consumer credit report, in violation of the Fair Credit Reporting Act ( FCRA ) 15 U.S.C. 1681i ( a ) ( 5 ) and Metro 2 Compliance Standards.\n\nDespite multiple formal disputes sent to each bureau regarding inaccurate, unverifiable, and non-compliant negative accounts and personal identifier information, the credit bureaus have failed to provide documented proof of verification or remove the disputed information as required by law.\n\nSome of the issues that I am facing are : Inaccurate and Unverifiable Accounts Reporting Failure to Follow Metro 2 Compliance Standards Failure to Investigate and Correct Disputed Items Incorrect and Outdated Personal Identifiers Lack of Permissible Purpose for Certain Inquiries Failure to Provide Validation Under 15 U.S.C. 1681g Each credit bureau is reporting accounts that are inaccurate, outdated, or unverifiable, including : Accounts that are not mine or incorrectly attributed Accounts that are missing key verification details ( Metro 2 compliance ) Accounts reported as charged off or delinquent without sufficient validation Specific accounts in question include but are not limited to : Experian : XXXX XXXXXXXX XXXX  XXXX ( Reported charge-off, unverified ) XXXX XXXX XXXX XXXX ( Unconfirmed, inconsistent reporting ) XXXX XXXX ( Non-compliant reporting, missing Metro 2 required fields ) XXXX XXXX  ( Incorrect charge-off status, lacks proper verification ) Equifax : XXXX XXXX XXXX XXXX XXXX ( Reporting inconsistencies across bureaus ) XXXX XXXXXXXX XXXX XXXX ( Lack of permissible purpose , unverifiable status ) XXXX  XXXX ( Unverified reporting, inconsistent across credit bureaus ) TransUnion : XXXXXXXX XXXX XXXXXXXX XXXX  ( Incorrect account details , unverifiable ) XXXX XXXX XXXX  ( Failure to validate ownership, missing Metro 2 compliance ) XXXX XXXX XXXX XXXX ( Reported late payment ,\n\nlacks proper verification ) Under Metro 2 Reporting Guidelines issued by the Consumer Data Industry Association ( CDIA ), all credit data must be formatted, verified, and reported with the highest level of accuracy and completeness. The accounts listed above contain missing or inconsistent information, making them non-compliant with Metro 2 standards.\n\nPer CDIAs Credit Reporting Resource Guide ( CRRG ), any deviation from Metro 2 standards compromises data integrity. These credit bureaus are knowingly reporting inaccurate and incomplete information in violation of industry compliance rules.\n\nThe Fair Credit Reporting Act ( 15 U.S.C. 1681i ) requires credit bureaus to investigate disputes and correct any unverifiable information.\n\nDespite my formal disputes via certified mail, the credit bureaus have failed to : Provide verifiable documentation proving the accuracy of the reported items. Cor\nrect or remove unverifiable accounts within the 30-day FCRA timeframe.\n\nEnsure all data meets Metro 2 compliance standards.\n\nIf a credit bureau can not verify the accuracy of an account, it must be removed immediately under 15 U.S.C. 1681i ( a ) ( 5 ). \n\nEach credit bureau is reporting incorrect, outdated, or unauthorized personal identifiers, including : Incorrect Names ( e.g., XXXX XXXX XXXX instead of XXXX XXXX ) Incorrect Addresses ( Listings I never resided at or outdated locations ) Incorrect Employer Information ( Employers I never worked for or outdated records ) FCRA 1681b requires credit bureaus to ensure only accurate and relevant personal information is reported. The inclusion of outdated or incorrect identifiers creates potential fraud risks and negatively impacts my credit profile.\n\nE. Lack of Permissible Purpose for Certain Hard Inquiries There are unauthorized hard inquiries on my credit report that were conducted without my explicit permission or permissible purpose under 15 U.S.C. 1681b. \n\nExamples of Unauthorized Inquiries : Experian : XXXX XXXX  XXXX ( XX/XX/year> ), XXXX XXXX ( XX/XX/year> ) Equifax : XXXX ( XX/XX/year> ), XXXX XXXXXXXX ( XX/XX/year> ), XXXX ( XX/XX/year> ) TransUnion : XXXX XXXX ( XX/XX/year> ) If an inquiry was performed without my authorization, it must be removed immediately under FCRA rules.","date_sent_to_company":"2025-03-13T18:30:46.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"60620","tags":null,"has_narrative":true,"complaint_id":"12455018","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"Experian Information Solutions Inc.","date_received":"2025-03-13T18:07:50.000Z","state":"IL","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":["<em>missing</em> key verification details ( <em>Metro</em> 2 compliance ) Accounts reported as charged off or delinquent without sufficient validation Specific accounts in question include but are not limited to : Experian : XXXX XXXXXXXX XXXX  XXXX ( Reported charge-off, unverified ) XXXX XXXX XXXX XXXX ( Unconfirmed, inconsistent reporting ) XXXX XXXX ( Non-compliant reporting, <em>missing</em> <em>Metro</em> 2 <em>required</em> <em>fields</em> ) XXXX XXXX  ( Incorrect charge-off status, lacks proper verification ) Equifax : XXXX XXXX XXXX XXXX XXXX"]},"sort":[20.52873,"12455018"]},{"_index":"complaint-public-v1","_id":"12454783","_score":20.528149,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"I am filing this complaint against Experian, Equifax, and TransUnion for failing to properly investigate, validate, and correct inaccurate and non-compliant information on my consumer credit report, in violation of the Fair Credit Reporting Act ( FCRA ) 15 U.S.C. 1681i ( a ) ( 5 ) and Metro 2 Compliance Standards.\n\nDespite multiple formal disputes sent to each bureau regarding inaccurate, unverifiable, and non-compliant negative accounts and personal identifier information, the credit bureaus have failed to provide documented proof of verification or remove the disputed information as required by law.\n\nSome of the issues that I am facing are : Inaccurate and Unverifiable Accounts Reporting Failure to Follow Metro 2 Compliance Standards Failure to Investigate and Correct Disputed Items Incorrect and Outdated Personal Identifiers Lack of Permissible Purpose for Certain Inquiries Failure to Provide Validation Under 15 U.S.C. 1681g Each credit bureau is reporting accounts that are inaccurate, outdated, or unverifiable, including : Accounts that are not mine or incorrectly attributed Accounts that are missing key verification details ( Metro 2 compliance ) Accounts reported as charged off or delinquent without sufficient validation Specific accounts in question include but are not limited to : Experian : XXXX XXXXXXXX XXXX  XXXX ( Reported charge-off, unverified ) XXXX XXXX XXXX XXXX ( Unconfirmed, inconsistent reporting ) XXXX XXXX ( Non-compliant reporting, missing Metro 2 required fields ) XXXX XXXX  ( Incorrect charge-off status, lacks proper verification ) Equifax : XXXX XXXX XXXX XXXX XXXX ( Reporting inconsistencies across bureaus ) XXXX XXXXXXXX XXXX XXXX ( Lack of permissible purpose , unverifiable status ) XXXX  XXXX ( Unverified reporting, inconsistent across credit bureaus ) TransUnion : XXXXXXXX XXXX XXXXXXXX XXXX  ( Incorrect account details , unverifiable ) XXXX XXXX XXXX  ( Failure to validate ownership, missing Metro 2 compliance ) XXXX XXXX XXXX XXXX ( Reported late payment ,\n\nlacks proper verification ) Under Metro 2 Reporting Guidelines issued by the Consumer Data Industry Association ( CDIA ), all credit data must be formatted, verified, and reported with the highest level of accuracy and completeness. The accounts listed above contain missing or inconsistent information, making them non-compliant with Metro 2 standards.\n\nPer CDIAs Credit Reporting Resource Guide ( CRRG ), any deviation from Metro 2 standards compromises data integrity. These credit bureaus are knowingly reporting inaccurate and incomplete information in violation of industry compliance rules.\n\nThe Fair Credit Reporting Act ( 15 U.S.C. 1681i ) requires credit bureaus to investigate disputes and correct any unverifiable information.\n\nDespite my formal disputes via certified mail, the credit bureaus have failed to : Provide verifiable documentation proving the accuracy of the reported items. Cor\nrect or remove unverifiable accounts within the 30-day FCRA timeframe.\n\nEnsure all data meets Metro 2 compliance standards.\n\nIf a credit bureau can not verify the accuracy of an account, it must be removed immediately under 15 U.S.C. 1681i ( a ) ( 5 ). \n\nEach credit bureau is reporting incorrect, outdated, or unauthorized personal identifiers, including : Incorrect Names ( e.g., XXXX XXXX XXXX instead of XXXX XXXX ) Incorrect Addresses ( Listings I never resided at or outdated locations ) Incorrect Employer Information ( Employers I never worked for or outdated records ) FCRA 1681b requires credit bureaus to ensure only accurate and relevant personal information is reported. The inclusion of outdated or incorrect identifiers creates potential fraud risks and negatively impacts my credit profile.\n\nE. Lack of Permissible Purpose for Certain Hard Inquiries There are unauthorized hard inquiries on my credit report that were conducted without my explicit permission or permissible purpose under 15 U.S.C. 1681b. \n\nExamples of Unauthorized Inquiries : Experian : XXXX XXXX  XXXX ( XX/XX/year> ), XXXX XXXX ( XX/XX/year> ) Equifax : XXXX ( XX/XX/year> ), XXXX XXXXXXXX ( XX/XX/year> ), XXXX ( XX/XX/year> ) TransUnion : XXXX XXXX ( XX/XX/year> ) If an inquiry was performed without my authorization, it must be removed immediately under FCRA rules.","date_sent_to_company":"2025-03-13T18:30:46.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"60620","tags":null,"has_narrative":true,"complaint_id":"12454783","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-03-13T18:30:17.000Z","state":"IL","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":["<em>missing</em> key verification details ( <em>Metro</em> 2 compliance ) Accounts reported as charged off or delinquent without sufficient validation Specific accounts in question include but are not limited to : Experian : XXXX XXXXXXXX XXXX  XXXX ( Reported charge-off, unverified ) XXXX XXXX XXXX XXXX ( Unconfirmed, inconsistent reporting ) XXXX XXXX ( Non-compliant reporting, <em>missing</em> <em>Metro</em> 2 <em>required</em> <em>fields</em> ) XXXX XXXX  ( Incorrect charge-off status, lacks proper verification ) Equifax : XXXX XXXX XXXX XXXX XXXX"]},"sort":[20.528149,"12454783"]},{"_index":"complaint-public-v1","_id":"12467010","_score":20.520348,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"I am filing this complaint against Experian, Equifax, and TransUnion for failing to properly investigate, validate, and correct inaccurate and non-compliant information on my consumer credit report, in violation of the Fair Credit Reporting Act ( FCRA ) 15 U.S.C. 1681i ( a ) ( 5 ) and Metro 2 Compliance Standards.\n\nDespite multiple formal disputes sent to each bureau regarding inaccurate, unverifiable, and non-compliant negative accounts and personal identifier information, the credit bureaus have failed to provide documented proof of verification or remove the disputed information as required by law.\n\nSome of the issues that I am facing are : Inaccurate and Unverifiable Accounts Reporting Failure to Follow Metro 2 Compliance Standards Failure to Investigate and Correct Disputed Items Incorrect and Outdated Personal Identifiers Lack of Permissible Purpose for Certain Inquiries Failure to Provide Validation Under 15 U.S.C. 1681g Each credit bureau is reporting accounts that are inaccurate, outdated, or unverifiable, including : Accounts that are not mine or incorrectly attributed Accounts that are missing key verification details ( Metro 2 compliance ) Accounts reported as charged off or delinquent without sufficient validation Specific accounts in question include but are not limited to : Experian : XXXX XXXXXXXX XXXX  XXXX ( Reported charge-off, unverified ) XXXX XXXX XXXX XXXX ( Unconfirmed, inconsistent reporting ) XXXX XXXX ( Non-compliant reporting, missing Metro 2 required fields ) XXXX XXXX  ( Incorrect charge-off status, lacks proper verification ) Equifax : XXXX XXXX XXXX XXXX XXXX ( Reporting inconsistencies across bureaus ) XXXX XXXXXXXX XXXX XXXX ( Lack of permissible purpose , unverifiable status ) XXXX  XXXX ( Unverified reporting, inconsistent across credit bureaus ) TransUnion : XXXXXXXX XXXX XXXXXXXX XXXX  ( Incorrect account details , unverifiable ) XXXX XXXX XXXX  ( Failure to validate ownership, missing Metro 2 compliance ) XXXX XXXX XXXX XXXX ( Reported late payment ,\n\nlacks proper verification ) Under Metro 2 Reporting Guidelines issued by the Consumer Data Industry Association ( CDIA ), all credit data must be formatted, verified, and reported with the highest level of accuracy and completeness. The accounts listed above contain missing or inconsistent information, making them non-compliant with Metro 2 standards.\n\nPer CDIAs Credit Reporting Resource Guide ( CRRG ), any deviation from Metro 2 standards compromises data integrity. These credit bureaus are knowingly reporting inaccurate and incomplete information in violation of industry compliance rules.\n\nThe Fair Credit Reporting Act ( 15 U.S.C. 1681i ) requires credit bureaus to investigate disputes and correct any unverifiable information.\n\nDespite my formal disputes via certified mail, the credit bureaus have failed to : Provide verifiable documentation proving the accuracy of the reported items. Cor\nrect or remove unverifiable accounts within the 30-day FCRA timeframe.\n\nEnsure all data meets Metro 2 compliance standards.\n\nIf a credit bureau can not verify the accuracy of an account, it must be removed immediately under 15 U.S.C. 1681i ( a ) ( 5 ). \n\nEach credit bureau is reporting incorrect, outdated, or unauthorized personal identifiers, including : Incorrect Names ( e.g., XXXX XXXX XXXX instead of XXXX XXXX ) Incorrect Addresses ( Listings I never resided at or outdated locations ) Incorrect Employer Information ( Employers I never worked for or outdated records ) FCRA 1681b requires credit bureaus to ensure only accurate and relevant personal information is reported. The inclusion of outdated or incorrect identifiers creates potential fraud risks and negatively impacts my credit profile.\n\nE. Lack of Permissible Purpose for Certain Hard Inquiries There are unauthorized hard inquiries on my credit report that were conducted without my explicit permission or permissible purpose under 15 U.S.C. 1681b. \n\nExamples of Unauthorized Inquiries : Experian : XXXX XXXX  XXXX ( XX/XX/year> ), XXXX XXXX ( XX/XX/year> ) Equifax : XXXX ( XX/XX/year> ), XXXX XXXXXXXX ( XX/XX/year> ), XXXX ( XX/XX/year> ) TransUnion : XXXX XXXX ( XX/XX/year> ) If an inquiry was performed without my authorization, it must be removed immediately under FCRA rules.","date_sent_to_company":"2025-03-13T18:30:46.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"60620","tags":null,"has_narrative":true,"complaint_id":"12467010","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-03-13T18:30:17.000Z","state":"IL","company_public_response":null,"sub_issue":"Account information incorrect"},"highlight":{"complaint_what_happened":["<em>missing</em> key verification details ( <em>Metro</em> 2 compliance ) Accounts reported as charged off or delinquent without sufficient validation Specific accounts in question include but are not limited to : Experian : XXXX XXXXXXXX XXXX  XXXX ( Reported charge-off, unverified ) XXXX XXXX XXXX XXXX ( Unconfirmed, inconsistent reporting ) XXXX XXXX ( Non-compliant reporting, <em>missing</em> <em>Metro</em> 2 <em>required</em> <em>fields</em> ) XXXX XXXX  ( Incorrect charge-off status, lacks proper verification ) Equifax : XXXX XXXX XXXX XXXX XXXX"]},"sort":[20.520348,"12467010"]},{"_index":"complaint-public-v1","_id":"4564547","_score":19.98796,"_source":{"product":"Credit reporting, credit repair services, or other personal consumer reports","complaint_what_happened":"Please ensure that you, XXXX REPORT to the CRAs any details that need to be communicated, corrected or resolved. \n\nThe DO NOT CONTACT remains in place, and as per communications acknowledged by you XXXX. An attachment, that only I can see is not the expected result. If you can substantiate it you are then required to report it. \n\nXXXX account number is missing from Equifax, when derived from XXXX XXXX XXXXXXXX ( spaces intended ). The complaint, is regarding what XXXX reported as - Opened Date XX/XX/2017, Balance XXXX. \n\nFor this complaint, and then as allowed I would like both the method of investigation, and then a printed report, mailed to my address of record ( Equifax and XXXX ), and with the results. \n\nThis is not a validation of debt. Please do not respond as if it is, your IT departments can help translate the issues outlined in this complaint, logically laid out and for 1 account ( you have 4, and I will do one by one with each CRA ) you - XXXX reported, and Equifax and XXXXXXXX then loads, displays and reports. \n\nThis Complaint is about your DATA, XXXX how you chose/design/elect to report it, and specific to FDCPA/FCRA mandates. \n\nThis is also about the CRAs. how they accept/load/report the Data XXXX sends. Logical, and as demonstrated, the impact of this activity is the premise of this complaint. Technical reliance on METRO2, and the related FDCPA and FCRA compliance issues, then become the issue. \n\n*****This is MY intellectual/data, including all the attachments and they should be treated in this fashion, proprietary or/and otherwise. I do NOT, authorize any usage outside of this complaint. \n\nI am XXXX XXXX, and I am the author of this dispute. This is NOT a Duplicate complaint, please do not flag it as such. I am not a Credit Repair Organization, nor am I using one I just love the data. \n\nThe screenshots/attachments/data within this complaint - are pulled directly from XXXX, MyEquifax.com and XXXX with my PII data validated and ensured, for verification and for access to my own, Credit Reports. As such this experience has allowed me to explore Metro2, its intent, requirements, technical specifications, field definitions and usage and in Credit Reporting, and specific to Debt Collectors and the CRAs. \n\nThis complaint is a bit long, and detailed, with some technical details within it. But you are provided with logical, discoverable details and steps to see your data, its end state and its whole state of inaccuracy. \n\nAll the companies within this complaint have an IT team, and developers that created/manage the integrations, built/build or maintain the systems, or load the files from Data Furnishers. It is advised that IT assist in your response. \n\nThere is an existing complaint against XXXX and the complaint number is XXXX. \n\nThat complaint - if read, is/was not a simple request of Validation of Debt, it was detailed, and specific to a complaint to XXXX. and its compliance with Metro2, and its standards - and, then FCRA/FDCPA. While XXXX did make traceable changes in my records at the CRA, they also said that there was nothing wrong, and that they believed that everything was correct. Thank you for that and changing your ( XXXX ) Loan Type from : Factoring Company to Debt Buyer, as it assisted in the decision to dive deep, into the data - it was eye opening. \n\nThat data creation, storage, file production and load/reporting stream of activity that occurs, is in fact that of XXXX and EquifaxXXXX. When there is an error in data or a system at least in standard XXXX, the rules that govern Consumer Data/Data Furnishers/CRAs Requirements through to Expected Results, the tasks to resolve are in fact defined. When they are defined, they are the rules. Defects are Traceable and, remedied or not. \n\nI am attaching a few documents that will assist everyone, Legal, IT and the CFPB - with understanding entrance into this complaint. This complaint is segmented, but it is also extremely logical, using the systems of the CRA to demonstrate its data, and what it is is appearing as, and the impact to the algorithms that are used for scoring, summarizing and reporting Midlands data. \n1. Attached as CFPB Metro2 - Required by all 3 - Metro2, Directives from XXXX, EQ and XXXX to ONLY send Metro2 Compliant integrations/files 2. Attached then, is Metro 2 - DC Section ( Tech Specification for Metro2 ) defined for Debt Collectors, which specifies the Segments and then Fields or Valid Values that can be sent in compliance with Metro2 3. *****Header and/or Footer is neither keyed, nor specific, to a consumer excluded. \n4. Records for Debt Collectors and then identified for consumers are in Segments called/named/labeled Base and K segments, ONLY 5. Do Not Send Metro2 Specifies the Fields or Valid Values that Should NOT ever, be sent to a CRA in compliance with Metro2 6. There is a logical reason why a technical specification, used industry wide would call this out 7. There are a total of 17 ( or so ) identifiers/fields of values, address may extend the fields populated as an example but the record is not extended for the Consumer Debt Collectors record 8. I have mapped the to a TRUE Collection Account EQ and XXXX ( See XXXX Attachment - Tab in attachment XXXX XXXXEquifax Collection ) 9. Both are using the CRAs Verbiage/Directive/Instructions 10. Sample Debt Collectors exist in EQs reports. \n11. XXXX says it but, well. Either the documentation is all wrong or, the system is. \n12. XXXX  is sending fields Do NOT sen\n\nd Metro2 13. Metro2 offers NO Defaults. 14. If you see it in Equifax and XXXX and you are told NEVER to send it 15. XXXX/XXXX/Equifax - You have failed to remedy the end result, that you know is invalid. \n\nI am pasting below, a link to the responsibilities as a Data Furnisher - I am relying on ( XXXX ) XXXX XXXX XXXX? XXXX & XXXX For Federal Law - Definition of a Creditor and then a Debt Collector, I am relying on - 803 ( 4 ) and ( 6 ) XXXX XXXX XXXX  Equifax XXXX XXXX. Any algorithm using this data as it is reporting itself - is no doubt producing inaccurate data/results/reports to anyone who has access to this data. \n2. Your views demonstrate it ( Equifax/XXXX  ) 3. XXXX - is not a Creditor/Lender. \n4. XXXX is a Debt Collector 5. The result of all of this - is that XXXX is reporting as a Creditor/Lender, with attributes they are directed NOT to send. \n6. XXXX Data sent on their files, are outside of Metro2 Standard ( See Metro2 Mapped DC Tab ). \n7. Equifax/XXXX  BOTH, have Dedicated Section, for COLLECTION ( See 5. Collections vs. 10. Portfolio Tab and ) 8. That Section Labeled, Described and Published, by Equifax/XXXX - defines it usage for Debt Collectors. \nXXXX. That Section is 10. In Equifax published standards fail to be demonstrated by XXXX, in any consumer report/view/profile. \n10. XXXX  you say there is a Collection Section even with the fields map/match Metro2, but, have deleted/masked/removed it, if it exists somewhere please share it in your response. \n11. Those fields are consistent with Metro2 Guidelines when mapped to the accounts details and data you, XXXX have published. \n12. I have mapped it its attached, on the Metro Mapped DC Tab 13. Equifax has a Dedicated Section, for Accounts, Tradelines of Creditors and Lenders 14. That Section Labeled, Described and Published, by Equifax -defines it usage for Creditors/Lenders, that section is 5. \n15. In that section - 5.2, says 5.2 XXXX ( CLOSED ) 16. The Account is not CLOSED 17. Should XXXXEquifax say it is, where is the Date Closed/Activity Designator that is Required of this TYPE of Account? If its not correct this? \n18. Then There is no Account Number EQ Equifax 19. It actually has a Debt to Credit ratio, and at 100 %? It can not because it is not a Creditor. \n20. It escapes the Summary views with the CLOSED actually and literally, impossible 21. Account Status as per Metro2 this is an INVALID Value for Debt Collectors 22. Pay History Can not apply to a Debt Collector as there is no contract, and Metro2 forbids this from being sent. \nXXXX3. Balance History Can not apply to a Debt Collector as there is no contract, and Metro2 forbids this from being sent. But you, XXXX, send it. \n24. Rating History - Can not apply to a Debt Collector as there is no contract, and Metro2 forbids this from being sent. But you, XXXX, send it. Debt to Credit Ratio, Available Credit, Balance, Pay and Rating History - Can not apply to a Debt Collector as Per Metro2 25. Almost every field in the Account Details, can never Apply to a Debt Collector a. Loan Type Can not Apply as Per Metro 2 b. When reporting in this section Creditor Classification is allowing this XXXX XXXX  record, to report as a Bank Card -, from a Creditor c. Equifax because you are allowing it its then so impactful, even when paid- the damage is for the duration of the tradeline. \nd. Your algorithms pick this up it can be demonstrated. \n\nThere is so much more to what is occurring, I will/can demonstrate it, as it is needed. \nIf it is happening to me it is happening to all and is systematic. \nThis took me a while to figure out but now I get it. \nI hope/know everyone else does/will get it too.","date_sent_to_company":"2021-08-04T14:54:34.000Z","issue":"Incorrect information on your report","sub_product":"Credit reporting","zip_code":"XXXXX","tags":null,"has_narrative":true,"complaint_id":"4564547","timely":"Yes","company_response":"Closed with explanation","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2021-07-22T14:35:59.000Z","state":"NJ","company_public_response":null,"sub_issue":"Account status incorrect"},"highlight":{"complaint_what_happened":["Attached as CFPB <em>Metro</em>2 - <em>Required</em> by all 3 - <em>Metro</em>2, Directives from XXXX, EQ and XXXX to ONLY send <em>Metro</em>2 Compliant integrations/files 2. Attached then, is <em>Metro</em> 2 - DC Section ( Tech Specification for <em>Metro</em>2 ) defined for Debt Collectors, which specifies the Segments and then <em>Fields</em> or Valid Values that can be sent in compliance with <em>Metro</em>2 3. *****Header and/or Footer is neither keyed, nor specific, to a consumer excluded. \n4."]},"sort":[19.98796,"4564547"]},{"_index":"complaint-public-v1","_id":"17305089","_score":19.737886,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"I am filing this complaint because several collection agencies are reporting accounts that do not belong to me and none of these furnishers have provided any verified documentation after I disputed these items as identity theft. These accounts have damaged my credit and I am being denied fair and accurate reporting. I discovered these issues after reviewing my credit reports from all three bureaus. Each bureau shows inconsistent and conflicting information for the same accounts. For example, XXXX XXXX, XXXX XXXX, XXXX XXXX, XXXX XXXX XXXX, XXXX XXXX XXXX, and XXXX XXXX are all reporting data that does not match across Equifax, Experian, and TransUnion. Some bureaus show the accounts as closed or charged off while the same item is shown as open or placed for collection on another bureau. These inconsistencies appear throughout all of the uploaded bureau files. This violates the requirement of maximum possible accuracy under FCRA 607b and the duty of furnishers under FCRA 623a1 to report only verified and consistent information. None of these companies have provided any original source documents showing that I opened or authorized these accounts. I have never received a signed application, itemized statements, billing history, treatment records, policy documents, or anything that legally connects me to these alleged debts. This is a direct violation of the Fair Debt Collection Practices Act because the furnishers continued reporting without validating the debts after my disputes. My Experian, Equifax, and TransUnion reports all include irregularities such as missing original creditor information, different date opened fields, conflicting account statuses, incorrect date last active fields, and incomplete or missing data fields. This is specifically shown in the uploaded bureau records such as the Experian section for XXXX XXXX where the account is closed on Experian but open on TransUnion and the XXXX account where Experian shows closed and TransUnion shows open. These are clear examples of non compliant Metro2 reporting. I am a victim of identity theft. My personal information was confirmed to be impacted by the Equifax data breach as shown in the document on page 2 of my upload. Because my information was exposed, I can not confirm how my identity was used to create or attach me to these fraudulent accounts. However, I did not authorize any of these debts and the companies involved have failed to provide legally required validation. These inaccurate and fraudulent accounts are preventing me from securing housing and financial stability. I have repeatedly disputed these items with the bureaus and the furnishers and they continue to verify without providing proof. The bureaus are also violating FCRA 1681i by verifying accounts without conducting a reasonable investigation and by relying on unverified information from furnishers.","date_sent_to_company":"2025-11-17T15:18:50.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"46221","tags":null,"has_narrative":true,"complaint_id":"17305089","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","date_received":"2025-11-17T15:18:23.000Z","state":"IN","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":["My Experian, Equifax, and TransUnion reports all include irregularities such as <em>missing</em> original creditor information, different date opened <em>fields</em>, conflicting account statuses, incorrect date last active <em>fields</em>, and incomplete or <em>missing</em> data <em>fields</em>. This is specifically shown in the uploaded bureau records such as the Experian section for XXXX XXXX where the account is closed on Experian but open on TransUnion and the XXXX account where Experian shows closed and TransUnion shows open."]},"sort":[19.737886,"17305089"]},{"_index":"complaint-public-v1","_id":"17307000","_score":19.732533,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"I am filing this complaint because several collection agencies are reporting accounts that do not belong to me and none of these furnishers have provided any verified documentation after I disputed these items as identity theft. These accounts have damaged my credit and I am being denied fair and accurate reporting. I discovered these issues after reviewing my credit reports from all three bureaus. Each bureau shows inconsistent and conflicting information for the same accounts. For example, XXXX XXXX, XXXX XXXX, XXXX XXXX, XXXX XXXX XXXX, XXXX XXXX XXXX, and XXXX XXXX are all reporting data that does not match across Equifax, Experian, and TransUnion. Some bureaus show the accounts as closed or charged off while the same item is shown as open or placed for collection on another bureau. These inconsistencies appear throughout all of the uploaded bureau files. This violates the requirement of maximum possible accuracy under FCRA 607b and the duty of furnishers under FCRA 623a1 to report only verified and consistent information. None of these companies have provided any original source documents showing that I opened or authorized these accounts. I have never received a signed application, itemized statements, billing history, treatment records, policy documents, or anything that legally connects me to these alleged debts. This is a direct violation of the Fair Debt Collection Practices Act because the furnishers continued reporting without validating the debts after my disputes. My Experian, Equifax, and TransUnion reports all include irregularities such as missing original creditor information, different date opened fields, conflicting account statuses, incorrect date last active fields, and incomplete or missing data fields. This is specifically shown in the uploaded bureau records such as the Experian section for XXXX XXXX where the account is closed on Experian but open on TransUnion and the XXXX account where Experian shows closed and TransUnion shows open. These are clear examples of non compliant Metro2 reporting. I am a victim of identity theft. My personal information was confirmed to be impacted by the Equifax data breach as shown in the document on page 2 of my upload. Because my information was exposed, I can not confirm how my identity was used to create or attach me to these fraudulent accounts. However, I did not authorize any of these debts and the companies involved have failed to provide legally required validation. These inaccurate and fraudulent accounts are preventing me from securing housing and financial stability. I have repeatedly disputed these items with the bureaus and the furnishers and they continue to verify without providing proof. The bureaus are also violating FCRA 1681i by verifying accounts without conducting a reasonable investigation and by relying on unverified information from furnishers.","date_sent_to_company":"2025-11-17T15:18:50.000Z","issue":"Improper use of your report","sub_product":"Credit reporting","zip_code":"46221","tags":null,"has_narrative":true,"complaint_id":"17307000","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"EQUIFAX, INC.","date_received":"2025-11-17T15:12:11.000Z","state":"IN","company_public_response":null,"sub_issue":"Reporting company used your report improperly"},"highlight":{"complaint_what_happened":["My Experian, Equifax, and TransUnion reports all include irregularities such as <em>missing</em> original creditor information, different date opened <em>fields</em>, conflicting account statuses, incorrect date last active <em>fields</em>, and incomplete or <em>missing</em> data <em>fields</em>. This is specifically shown in the uploaded bureau records such as the Experian section for XXXX XXXX where the account is closed on Experian but open on TransUnion and the XXXX account where Experian shows closed and TransUnion shows open."]},"sort":[19.732533,"17307000"]},{"_index":"complaint-public-v1","_id":"14809971","_score":19.486782,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"Subject : Formal Request for Reinvestigation and Full Compliance Review under FCRA, TILA, FCBA, FDCPA, and Metro 2 To Whom It May Concern : This is a formal Reinvestigation Request and Notice of Dispute regarding the information your company is furnishing to the credit reporting agencies under my consumer file.\n\nPursuant to the Fair Credit Reporting Act ( 15 U.S.C. 1681s-2 ( b ) ), and the Fair Credit Billing Act, you are required to conduct a reasonable investigation upon receiving notice of a dispute. I am hereby demanding a reinvestigation of the item ( s ) listed below, and a comprehensive review of your reporting under XXXX XXXX compliance guidelines, including all data fields and condition codes. \n\nAccount Name/Number : XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX Date Opened : XX/XX/XXXX Nature of Dispute : The Date of Last Activity is inconsistent : XXXX  reports XX/XX/XXXX Equifax reports XX/XX/XXXXXXXX XXXX reports XX/XX/XXXX Violation of FCRA 607 ( b ) and Metro 2 Field 25 ( inaccurate and misleading reporting of aging ) Dispute Reason : The account is reported as closed under charge-off while still reflecting an outstanding balance, creating a potential contradiction. Additionally, the payment history shows inconsistent reporting patterns, which may lead to incorrect delinquency tracking and credit scoring discrepancies. \n\nThe account status conflicts : XXXX XXXX XXXX XXXX Charge Off- Collection/Charged Off XXXX : Open Collection/ Charge-off Violation of FCRA 623 ( a ) ( 1 ) ( A ) and XXXX XXXX Field 17 ( status codes must be consistent across CRAs ) The payment history is missing : XXXX XXXX XXXX shows No History Available Violation of XXXX XXXX reporting standards ( field omission reduces transparency and accuracy ) The charge-off date is suspiciously aged : Last activity in XXXX vs. XXXX may indicate artificial account extension Possible violation of FCBA and TILA, which govern aging and accurate charge-off practices This may indicate either : The debt is unverifiable and thus omitted by other CRAs. \nThe data furnisher failed to report uniformly, leading to incomplete data transmission in violation of FCRA 623 ( a ) ( 1 ) ( A ). \n\nAccount Name/Number : PORTFOLIO RC ( XXXX XXXX XXXX XXXX XXXX XXXX XXXX Date Opened : XX/XX/XXXX Nature of Dispute : The Date of Last Activity is inconsistent : XXXX reports XX/XX/XXXXXXXX XXXX XXXX XXXX reports XX/XX/XXXXXXXX XXXX reports XX/XX/XXXX Violation of FCRA 607 ( b ) and XXXX XXXX Field 25 ( inaccurate and misleading reporting of aging ) Dispute Reason : The account is marked as closed under charge-off, but a collection balance remains, creating a contradiction under XXXX XXXX reporting standards XXXX Moreover, the payment history shows gaps in reporting consistency, which may impact the correct calculation of the date of first delinquency and charge-off timing. \n\nThe account status conflicts : XXXX XXXX XXXX XXXX Charge Off- Collection/Charged Off XXXX  : Open Collection/ Charge-off Violation of FCRA 623 ( a ) ( 1 ) ( A ) and XXXX XXXX Field 17 ( status codes must be consistent across CRAs ) The payment history is missing : XXXX XXXX XXXX shows No History Available Violation of XXXX XXXX reporting standards ( field omission reduces transparency and accuracy ) The charge-off date is suspiciously aged : Last activity in XXXX vs. XXXX XXXX indicate artificial account extension Possible violation of FCBA and TILA, which govern aging and accurate charge-off practices This may indicate either : The debt is unverifiable and thus omitted by other CRAs. \nThe data furnisher failed to report uniformly, leading to incomplete data transmission in violation of FCRA 623 ( a ) ( 1 ) ( A ). \n\n\n\n\n\nAccount Name/Number : PORTFOLIO RC ( XXXX XXXX XXXX ) XXXX Date Opened : XX/XX/XXXX Nature of Dispute : The Date of Last Activity is inconsistent : XXXX reports XX/XX/XXXXXXXX XXXX XXXX XXXX reports XX/XX/XXXX XXXX reports XX/XX/XXXX Violation of FCRA 607 ( b ) and XXXX XXXX Field 25 ( inaccurate and misleading reporting of aging ) Dispute Reason : The account status reflects charge-off with a closed notation, while still showing a collection balance, which can be misleading under XXXX XXXX guidelines. Additionally, payment history inconsistencies may result in incorrect delinquency aging, potentially affecting score calculation negatively. \n\nThe account status conflicts : XXXX XXXX XXXX : Charge Off- Collection/Charged Off XXXX : Open Collection/ Charge-off Violation of FCRA 623 ( a ) ( 1 ) ( A ) and XXXX XXXX Field 17 ( status codes must be consistent across CRAs ) The payment history is missing : XXXX XXXX XXXX shows No History Available Violation of XXXX XXXX reporting standards ( field omission reduces transparency and accuracy ) The charge-off date is suspiciously aged : Last activity in XXXX vs. XXXX XXXX indicate artificial account extension Possible violation of FCBA and TILA, which govern aging and accurate charge-off practices This may indicate either : The debt is unverifiable and thus omitted by other CRAs. \nThe data furnisher failed to report uniformly, leading to incomplete data transmission in violation of FCRA 623 ( a ) ( 1 ) ( A ). \n\n\nAccount Name/Number : PORTFOLIO RC ( XXXX BANK ) XXXX Date Opened : XX/XX/XXXX Nature of Dispute : The Date of Last Activity is inconsistent : XXXX  reports XX/XX/XXXXXXXX XXXX reports XX/XX/XXXXXXXX XXXX reports XX/XX/XXXX Violation of FCRA 607 ( b ) and XXXX XXXX Field 25 ( inaccurate and misleading reporting of aging ) Dispute Reason : I am disputing the Portfolio RC account reporting on my XXXX credit report. There are inaccuracies in how this account is listed. The account balance, last activity date, and account status are inconsistent with other reports. Additionally, the payment history contains errors that do not accurately reflect my account status. Please conduct an investigation and correct or remove any inaccurate information. \n\nThe account status conflicts : TXXXX XXXX XXXX : Charge Off- Collection/Charged Off XXXX : Open Collection/ Charge-off Violation of FCRA 623 ( a ) ( 1 ) ( A ) and XXXX XXXX Field 17 ( status codes must be consistent across CRAs ) The payment history is missing : XXXX XXXX XXXX  shows No History Available Violation of Metro 2 reporting standards ( field omission reduces transparency and accuracy ) The charge-off date is suspiciously aged : Last activity in XXXX vs. XXXX XXXX indicate artificial account extension Possible violation of FCBA and TILA, which govern aging and accurate charge-off practices This may indicate either : The debt is unverifiable and thus omitted by other CRAs. \nThe data furnisher failed to report uniformly, leading to incomplete data transmission in violation of FCRA 623 ( a ) ( 1 ) ( A ).","date_sent_to_company":"2025-07-22T15:03:39.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"33023","tags":null,"has_narrative":true,"complaint_id":"14809971","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"Portfolio Recovery Associates, LLC","date_received":"2025-07-22T14:59:30.000Z","state":"FL","company_public_response":null,"sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["The account status conflicts : TXXXX XXXX XXXX : Charge Off- Collection/Charged Off XXXX : Open Collection/ Charge-off Violation of FCRA 623 ( a ) ( 1 ) ( A ) and XXXX XXXX <em>Field</em> 17 ( status codes must be consistent across CRAs ) The payment history is <em>missing</em> : XXXX XXXX XXXX  shows No History Available Violation of <em>Metro</em> 2 reporting standards ( <em>field</em> omission reduces transparency and accuracy ) The charge-off date is suspiciously aged : Last activity in XXXX vs."]},"sort":[19.486782,"14809971"]},{"_index":"complaint-public-v1","_id":"14806888","_score":19.431002,"_source":{"product":"Credit reporting or other personal consumer reports","complaint_what_happened":"To Whom It May Concern : This is a formal Reinvestigation Request and Notice of Dispute regarding the information your company is furnishing to the credit reporting agencies under my consumer file.\n\nPursuant to the Fair Credit Reporting Act ( 15 U.S.C. 1681s-2 ( b ) ), and the Fair Credit Billing Act, you are required to conduct a reasonable investigation upon receiving notice of a dispute. I am hereby demanding a reinvestigation of the item ( s ) listed below, and a comprehensive review of your reporting under Metro 2 compliance guidelines, including all data fields and condition codes.\n\nMidland Credit Management account because the original creditor information and charge-off details are inaccurate. The last activity date differs across bureaus, and the reporting does not align with FCRA standards. Please provide validation or remove the account if it can not be verified. \n\nAccount Name/Number : XXXX XXXX  XXXX XXXX XXXX  ) XXXX Date Opened : XX/XX/2021 Nature of Dispute : Nature of Dispute : This account is reflected as a collection tradeline on XXXX  yet it is completely absent from XXXX  and XXXX.\n\nSuch inconsistency creates data integrity issues, violating FCRA 607 ( b ) which requires furnishers to provide complete and accurate information.\n\nMetro 2 compliance standards mandate uniformity across all CRAs to ensure parity in consumer data reporting.\n\nIf a collection is valid and verifiable, it must be reported equally across all CRAs, or else it misrepresents the consumer 's financial history.\n\nPartial or selective reporting may also constitute unfair or deceptive practice under Dodd-Frank Act 1036, particularly if it results in disparate impact on the consumers creditworthiness.\n\nThe account is missing from XXXX  and XXXX  : Suggests selective or incomplete furnishing Violation of FCRA 602, DoddFrank Act ( UDAAP provisions ), and equal data furnishing standards This may indicate either : The debt is unverifiable and thus omitted by other CRAs. \nThe data furnisher failed to report uniformly, leading to incomplete data transmission in violation of FCRA 623 ( a ) ( 1 ) ( A ).","date_sent_to_company":"2025-07-22T17:01:42.000Z","issue":"Problem with a company's investigation into an existing problem","sub_product":"Credit reporting","zip_code":"70458","tags":null,"has_narrative":true,"complaint_id":"14806888","timely":"Yes","company_response":"Closed with non-monetary relief","submitted_via":"Web","company":"ENCORE CAPITAL GROUP INC.","date_received":"2025-07-22T16:56:39.000Z","state":"LA","company_public_response":null,"sub_issue":"Their investigation did not fix an error on your report"},"highlight":{"complaint_what_happened":["Pursuant to the Fair Credit Reporting Act ( 15 U.S.C. 1681s-2 ( b ) ), and the Fair Credit Billing Act, you are <em>required</em> to conduct a reasonable investigation upon receiving notice of a dispute. I am hereby demanding a reinvestigation of the item ( s ) listed below, and a comprehensive review of your reporting under <em>Metro</em> 2 compliance guidelines, including all data <em>fields</em> and condition codes."]},"sort":[19.431002,"14806888"]}]},"aggregations":{"has_narrative":{"meta":{},"doc_count":77,"has_narrative":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":1,"key_as_string":"true","doc_count":77}]}},"product":{"doc_count":77,"product":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Credit reporting or other personal consumer reports","doc_count":67,"sub_product.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Credit reporting","doc_count":67}]}},{"key":"Credit reporting, credit repair services, or other personal consumer reports","doc_count":8,"sub_product.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Credit reporting","doc_count":8}]}},{"key":"Debt collection","doc_count":2,"sub_product.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"I do not know","doc_count":2}]}}]}},"issue":{"doc_count":77,"issue":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Incorrect information on your report","doc_count":35,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Account information incorrect","doc_count":19},{"key":"Information belongs to someone else","doc_count":5},{"key":"Account status incorrect","doc_count":4},{"key":"Personal information incorrect","doc_count":3},{"key":"Public record information inaccurate","doc_count":3},{"key":"Information is missing that should be on the report","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":22},{"key":"Investigation took more than 30 days","doc_count":2},{"key":"Problem with personal statement of dispute","doc_count":1},{"key":"Was not notified of investigation status or results","doc_count":1}]}},{"key":"Improper use of your report","doc_count":10,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Reporting company used your report improperly","doc_count":10}]}},{"key":"Problem with a credit reporting company's investigation into an existing problem","doc_count":4,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Was not notified of investigation status or results","doc_count":3},{"key":"Their investigation did not fix an error on your report","doc_count":1}]}},{"key":"Attempts to collect debt not owed","doc_count":1,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Debt is not yours","doc_count":1}]}},{"key":"Written notification about debt","doc_count":1,"sub_issue.raw":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Didn't receive notice of right to dispute","doc_count":1}]}}]}},"timely":{"doc_count":77,"timely":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Yes","doc_count":77}]}},"company_response":{"doc_count":77,"company_response":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Closed with explanation","doc_count":41},{"key":"Closed with non-monetary relief","doc_count":36}]}},"submitted_via":{"doc_count":77,"submitted_via":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Web","doc_count":77}]}},"company":{"doc_count":77,"company":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"EQUIFAX, INC.","doc_count":31},{"key":"TRANSUNION INTERMEDIATE HOLDINGS, INC.","doc_count":23},{"key":"Experian Information Solutions Inc.","doc_count":15},{"key":"Bread Financial Holdings, Inc.","doc_count":1},{"key":"CBC Companies, Inc.","doc_count":1},{"key":"CCS Financial Services, Inc.","doc_count":1},{"key":"ENCORE CAPITAL GROUP INC.","doc_count":1},{"key":"LCI Acquisition Inc.","doc_count":1},{"key":"LEXISNEXIS","doc_count":1},{"key":"Portfolio Recovery Associates, LLC","doc_count":1},{"key":"SUNRISE CREDIT SERVICES, INC","doc_count":1}]}},"state":{"doc_count":77,"state":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"NJ","doc_count":10},{"key":"TX","doc_count":8},{"key":"LA","doc_count":7},{"key":"GA","doc_count":6},{"key":"IL","doc_count":6},{"key":"VA","doc_count":6},{"key":"MS","doc_count":4},{"key":"PA","doc_count":4},{"key":"FL","doc_count":3},{"key":"IN","doc_count":3},{"key":"MD","doc_count":3},{"key":"NC","doc_count":3},{"key":"NV","doc_count":3},{"key":"NY","doc_count":3},{"key":"OR","doc_count":2},{"key":"AR","doc_count":1},{"key":"AZ","doc_count":1},{"key":"CA","doc_count":1},{"key":"MO","doc_count":1},{"key":"RI","doc_count":1},{"key":"WA","doc_count":1}]}},"company_public_response":{"doc_count":77,"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":39},{"key":"Company believes it acted appropriately as authorized by contract or law","doc_count":1}]}},"tags":{"doc_count":77,"tags":{"doc_count_error_upper_bound":0,"sum_other_doc_count":0,"buckets":[{"key":"Servicemember","doc_count":1}]}}},"_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":[19.431002,"14806888"],"3":[14.777288,"8436714"],"4":[5.1644344,"15623837"]}}}