Before you choose a financial company, the CFPB Consumer Complaint Database can give you a quick view into how that company has handled consumer complaints. Used carefully, it can show patterns in products, issues, and response timing. Used carelessly, it can mislead. The key is to read the fields as a record of published complaints, not as a full report card on a company.
The database is public, searchable in a browser, and downloadable for deeper review. It generally updates daily. That sounds simple, but the way complaints enter the system matters. A complaint is published only after the company responds or after 15 days, whichever comes first. That timing can make a recent complaint look incomplete when it is simply not yet public.
Start with what the database actually is
The CFPB launched the Consumer Complaint Database in 2012, beginning with credit card complaints. Since then, it has become a large public record of complaints about financial products and services. The Bureau says the database lets people view and download complaints and see how companies respond. That makes it useful for screening, but not for drawing final conclusions about a business.
One reason is that the database is filtered. Complaints that the CFPB sends to other regulators are not published. The Bureau gives one example, complaints about depository institutions with less than $10 billion in assets. So if a company seems oddly absent, that may reflect how the CFPB routes complaints, not a perfect record of consumer experience.
Another reason is timing. The CFPB screens each complaint for completeness and sends it to the company through a secure portal. The company then reviews the complaint and may communicate with the consumer. The published record is the result of that process, not a raw intake log. That structure makes the database easier to search, but it also means the public is seeing only part of the process.
Read the numbers with company size in mind
Complaint volume is the first number many people notice, and it is also the easiest number to misuse. The CFPB says the database is not a statistical sample of consumers’ experiences, so the complaints are not representative of all customers. A high count can point to a problem, but it can also reflect a company that serves many more people than its peers.
That is why size matters. A company with a large customer base may naturally generate more complaints than a smaller one. For location-based views, population matters too. A ZIP code with more residents may show more complaints simply because more people live there. Raw counts need context before they mean much.
The CFPB also reports that 99% of complaints sent to companies get timely responses. That figure is about response timing, not consumer satisfaction. A timely response does not tell you whether the company fixed the issue, acknowledged fault, or gave the consumer the outcome they wanted.
Focus on the fields that tell you where the problem sits
The published record includes date received, product, sub-product, issue, sub-issue, and the company’s optional public response. Those fields are the best place to begin. If you are researching a mortgage company, for example, the mortgage product field matters more than the overall complaint total. The issue and sub-issue fields can narrow the concern further, such as billing, payment processing, or account management.
That structure is useful because it lets you compare like with like. Two companies can both have a lot of complaints, but the mix may be different. One may have many complaints tied to servicing errors, while another may have more complaints about fees. The database can help you spot those differences if you avoid reading one number in isolation.
The company response field needs caution too. Companies can choose whether to provide a public response, and the CFPB says the response comes from a preset list of categories. The sources do not explain what each category means for the consumer, so it is a mistake to treat a response label as a promise of a specific outcome. Read it as process data, not a guarantee.
Do not overread complaint narratives
For years, the database also included consumer complaint narratives and related visualizations. Starting August 14, 2026, the CFPB said it will stop publishing those narratives. The Bureau cited concerns that they are unverified, one-sided, and non-representative, and that they can create confusion and reputational harm. For anyone comparing companies now, the structured fields and downloadable data matter more than story text.
Because complaints are not verified allegations, a single complaint should be treated as one consumer’s account, not as a finding that a company broke the law.
That shift also changes how older records should be handled. Previously published narratives are still treated as public under FOIA and are being disclosed through the CFPB’s FOIA Reading Room. The narrative archive files cover complaints received from December 1, 2011 through August 14, 2026. If you are trying to inspect an older narrative, the sources point to those routes, but they do not lay out a simple one-step search path.
The bigger lesson is to stop treating the narrative as the centerpiece. A compelling consumer story can be memorable, but the database works best when you use the fields that can be sorted, filtered, and compared across companies.
Use a short checklist before you decide
A practical review does not need to be complicated. Start with the product and sub-product, then look at the issue and sub-issue. Ask whether the complaint count makes sense next to company size and market share. Then check whether the company published a response and whether that response was final within the required timeline.
That timeline matters because companies must respond within 15 calendar days. If the response is not final, they have up to 60 more calendar days to provide one. A response that is still in process tells you something different from a final response. It can signal that the company is still reviewing the case, or that the public record has not yet reached the final stage.
It is also worth asking what may be missing. Some complaints are referred to other regulators and never appear in the database. That means a company with few published complaints is not automatically trouble-free. It may simply be operating in a category where more complaints go elsewhere.
Know the limits before you rely on the file
The database can help you compare companies, but it cannot tell you everything. It does not show whether a complaint was resolved to the consumer’s satisfaction. It does not prove a legal violation. It does not cover every kind of consumer dispute, including complaints about credit bureaus or how to dispute credit report errors. For those topics, the relevant agencies and bureau pages are the better starting point.
That is why the safest reading is a narrow one. Use the database to spot patterns, not to make a final judgment from one number or one complaint. A company with many complaints may deserve a closer look, but so may a company with very few published complaints if the data is being routed elsewhere. The most useful question is not whether the company has complaints. It is what kind, how many, and how it responded.
In that sense, the CFPB database works like a screening tool. It can help you narrow a shortlist before you compare terms, service, and complaint patterns side by side. It cannot choose for you, and it should not be read as a full picture. Used with context, though, it can save you from making a decision in the dark.
Please seek a professional. This article is general information, not financial, tax or insurance advice. Please seek a licensed financial, tax or insurance professional about your own situation.
