Search for patterns, not verdicts
The CFPB Consumer Complaint Database lets you filter and download information about eligible complaints involving financial products and services. It is useful for finding repeated issues, reviewing how a company categorized its response, and building a documented research set.
It is not a customer-satisfaction survey, a complete register of every complaint, or proof that a company violated the law. The CFPB explicitly says the database is not a statistical sample representative of all consumer experiences. A raw total without company size or market share can mislead more than it informs.
Know what reaches the public database
The Bureau routes a submitted complaint to a company when appropriate. Complaints sent to companies are eligible for publication after the company responds and confirms a commercial relationship, or after 15 days, whichever happens first. Complaints referred to some other regulators are not published in this database.
The public data omits directly identifying information such as names, account numbers, Social Security numbers, contact details, and supporting documents. Geographic detail can also be reduced or blank. A missing ZIP value is not evidence that the consumer omitted an address.
In September 2026, the CFPB announced that it would cease discretionary publication of consumer narratives and associated visualizations. That is a material interface change. Older articles that center their workflow on reading narrative text may describe a historical version rather than the current public product.
Build a reproducible search
Before touching filters, write the question in one sentence. “Show mortgage complaints” is too broad. “Show complaints received from January through June 2026 about mortgage closing, grouped by company response” is auditable.
Use this sequence:
- Set a defined received-date range.
- Select one product and, when relevant, a sub-product.
- Select an issue and sub-issue only if the taxonomy supports your question.
- Add a company filter after checking the exact public company name.
- Add state or ZIP only when geography matters and disclose blank or reduced ZIP fields.
- Export the filtered rows and preserve the retrieval date.
- Record the filter values and the number of rows before calculating percentages.
The database taxonomy changes over time. CFPB preserves the product and issue labels selected when historical complaints were submitted. Two similar labels from different periods should not be silently collapsed unless you document the mapping.
Read the fields without adding a conclusion
| Field | What it supports | What it does not prove |
|---|---|---|
| Date received | When CFPB received the complaint | When the underlying event occurred |
| Product, sub-product, issue, sub-issue | Categories selected in the complaint workflow | An audited diagnosis of the problem |
| Company | Company the complaint concerns | The current legal entity for every brand or affiliate |
| Date sent to company | Routing date | Date the company first learned of the issue through another channel |
| Company response to consumer | Standardized disposition category | That the consumer agreed or the CFPB endorsed the response |
| Timely response | Whether the response met the program's timing field | That the substantive resolution was fair or complete |
| Complaint ID | Unique identifier for the complaint record | A court case, account number, or enforcement matter |
If a brand name and the database company name differ, use business entity search to understand the legal-name distinction. Do not merge affiliates based only on a shared logo.
Compare companies without making a false league table
Suppose Company A has 8,000 complaints and Company B has 1,500. Without knowing customer counts, transaction volume, product mix, states served, and the period each company operated, the larger number does not establish worse service.
A defensible comparison does four things:
- uses the same date window and product category;
- reports raw counts as counts, not rates;
- states that a market-share or customer denominator is unavailable when it is unavailable;
- separates response timeliness from complaint substance.
Avoid a “complaints per company” chart that quietly mixes nationwide credit bureaus, regional lenders, debt collectors, and fintech apps. Their exposure and products are different. If you calculate a share of complaints within a filtered dataset, call it exactly that. It is not market incidence.
Distinguish a database search from filing a complaint
Searching the public database does not submit a complaint or update an existing one. The CFPB complaint process has its own stages: submission, routing, company response, publication when eligible, and consumer review. Companies generally respond within 15 days and may provide a final response within 60 days in some cases.
When filing, provide account-specific information through the official complaint channel, not a public comment or social-media post. Public datasets do not publish account numbers and attachments. If the issue involves identity theft or a credit-report file, the FCRA guide and credit freeze guide explain separate rights and prevention steps.
Troubleshoot a surprising result
No company match: Try the legal company name, parent, servicer, or prior name. Verify the relationship rather than broadening to a partial word that captures unrelated firms.
A sudden drop in results: Check the date range, product-taxonomy update, and 2026 narrative change before describing a behavioral trend.
Duplicate-looking rows: Complaint IDs are unique. Similar dates and issues can represent different consumers. Do not deduplicate solely on company and category.
Missing local institution: The CFPB says complaints referred to other regulators, including certain complaints involving smaller depository institutions, are not published here. Absence is not a zero-complaint certificate.
A response label sounds conclusive: “Closed with explanation” describes the response category. It does not mean an independent adjudicator found the explanation correct.
Publish a responsible finding
A good summary names the source, retrieval date, filters, row count, and limitation. For example: “The filtered CFPB dataset contained N complaints received in the selected period under this product and issue. Counts are not adjusted for company size, and the database is not representative of all customer experiences.”
That sentence is less dramatic than a ranking, but it preserves what the public record can actually support. Lookup Plainly does not submit complaints, resolve disputes, or rate financial companies.
