CFPB complaint data is useful for understanding issue patterns, but it is not a customer-satisfaction survey, a statistically representative sample, or a ready-made bank rating. OUSBI therefore treats it as a separate complaint-intelligence layer with explicit coverage limits.
Institution-level live complaint statistics are not enabled in this initial release. OUSBI publishes no institution complaint counts or comparisons based on unverified Company mappings. Official CFPB help and regulator sources remain available as ordinary authoritative references. Any future structured complaint view requires verified institution mapping, period, product scope and coverage.
What data is used
OUSBI may use structured fields such as date received, product/sub-product, issue/sub-issue, company, state/ZIP where appropriate, submitted channel, date sent to company, company response category, timely-response flag and complaint ID. Period, product and institution identity are kept explicit.
2026 narrative change
On August 14, 2026, CFPB stopped discretionary publication of consumer complaint narratives and visualizations in the current Consumer Complaint Database. The September 2026 API release notes confirm that complaint narratives were removed from the live database. Previously published narratives through August 14, 2026 are available separately through the CFPB FOIA Reading Room archive. OUSBI does not mix that historical narrative archive into current structured complaint counts as if the datasets were identical.
Coverage limitation for smaller depository institutions
CFPB states that complaints referred to other regulators—including complaints about depository institutions with less than $10 billion in assets—are not published in the public Consumer Complaint Database. Therefore a small credit union with few or no public CFPB rows cannot be described as having few or no consumer problems on that basis.
Why raw totals are misleading
Institution size, number of customers, product mix, complaint-routing rules and time period all affect complaint volume. OUSBI does not publish an invented CFPB score and does not rank a national bank against a small credit union simply by counting rows.
How OUSBI presents complaint intelligence
When enough data exists, OUSBI can show issue/sub-issue mix, response categories, timely-response rate or change over a defined window. The period and coverage caveat stay visible. The complaint layer is visually separate from official account rules and OUSBI Experiences.
What a complaint row does not prove
A complaint is an allegation/consumer report routed through the CFPB process; it does not by itself prove a legal violation, establish causation, or confirm that every factual assertion in a complaint is correct.
Sources and versioning
CFPB Consumer Complaint Database · CFPB August 14, 2026 narrative announcement · CFPB Complaint Database API release notes · CFPB narratives archive
This policy is reviewed when the evidence methodology, data coverage, moderation, commercial relationships or privacy practices change. The policy published at launch must describe the features and controls that are actually available.
Example: large bank vs smaller credit union
If a nationwide bank has thousands of public CFPB rows while a smaller credit union has few or none, OUSBI does not conclude that the credit union is safer or better. Company size and product mix differ, and CFPB explicitly says complaints referred to other regulators—including complaints about depository institutions under the Bureau’s publication threshold—are not published in the public database. A fair view must show coverage and period before counts.
Frequently asked questions
Are CFPB complaints verified violations? No. Does OUSBI read current complaint narratives? The live database no longer publishes narratives after the August/September 2026 change; historical narratives remain a separate FOIA archive. Can complaint volume rank banks? Not by itself. What can be compared? Issue mix, response category, timely-response field and trends within clearly defined windows, with coverage caveats. Does zero public complaints mean zero complaints? No.
Data-quality rules
Company matching uses institution-specific aliases and stable identity review rather than fuzzy brand guesses. Unmatched company values go to REVIEW. Period/product filters stay explicit. OUSBI will not blend historical narrative archives into current structured rows without a documented cutoff and separate dataset label.
Related guides
How OUSBI verifies banking information: /methodology/
Privacy and data handling: /privacy/