---
title: "FDIC Enforcement Actions: How to Track Bank Penalties"
description: "FDIC enforcement actions explained: how to find and read consent orders, civil money penalties and removal orders, and what the pattern says about a bank."
canonical_url: https://www.bankregreports.com/blog/fdic-enforcement-actions-api/
source: BankRegReports
published: "2026-09-25"
updated: "2026-10-28"
---

If you have ever sat through a regulatory exam exit meeting, you know the tone that follows a Matters Requiring Attention. The language is careful and the timeline is short.

Enforcement actions are what happens when that process breaks down. That usually means one of three things:

- the examination findings do not get remediated;
- BSA program gaps persist across multiple exam cycles;
- capital deterioration outpaces management's credibility with the primary regulator.

Tracking that enforcement activity at scale is hard. That is true if you build risk models, do competitive intelligence, or run a compliance program that extends beyond a single institution. The public data is there, but extracting it cleanly from raw FDIC sources is a project in itself.

## What Are FDIC Enforcement Actions?

FDIC enforcement actions are the formal actions the FDIC takes against state non-member banks and savings institutions under its supervisory authority. The FDIC publishes them, and the official source is the [FDIC](https://www.fdic.gov). They include:

- **Consent Orders**: negotiated formal agreements that carry the weight of a cease-and-desist without the adversarial process. These are public and indexed.
- **Civil Money Penalties (CMPs)**: dollar-denominated penalties, most commonly assessed for BSA/AML violations, TILA, RESPA, or flood insurance failures.
- **Orders to Cease and Desist**: the harder version. When a bank contests a finding, this is the result. Rare but significant.
- **Termination of Insurance (Section 8(a))**: proceedings to end a bank's deposit insurance, the most severe action the FDIC can bring against an institution. (Formal agreements, often confused with consent orders, are an OCC tool; the Federal Reserve's equivalent is the written agreement.)
- **[Prompt Corrective Action](/glossary/prompt-corrective-action/) (PCA) Directives**: capital-triggered, usually indicating the institution is undercapitalized. These tend to precede failures.
- **Removal and Prohibition Orders**: individual-level actions against officers or directors.

### Formal vs. informal actions

The distinction between formal and informal matters because informal actions (Memoranda of Understanding, board resolutions) are not disclosed publicly. What you see in the public enforcement database is a floor, not a ceiling. A bank can be operating under a significant MOU with no public signal outside the supervisory process.

### Why the public record still matters for models

For modeling purposes, the public record still carries meaningful signal.

- Consent orders often precede deterioration in credit metrics.
- PCA directives are typically leading indicators of failure or acquisition under duress.
- CMP frequency at an institution-type level tracks regulatory cycle intensity by compliance area.


<figure>
  <img src="/static/blog/figures/bank_failures_by_year.svg"
       alt="Bar chart of U.S. bank and thrift failures per year, 1970 to 2025"
       loading="lazy">
  <figcaption>Enforcement and failure are the tail of the same supervisory process. U.S. bank and thrift failures per year, 1970 to 2025, are the backdrop enforcement-action data fills in. <em>BankRegReports analysis.</em></figcaption>
</figure>

## Why Raw FDIC Data Is Difficult to Work With

The FDIC makes enforcement action data available through its website and bulk download files, but the raw format has real friction:

- Institution identifiers are inconsistent across vintages.
- Linking enforcement records to FFIEC [Call Report](/blog/what-is-a-bank-call-report/) data requires joining on FDIC certificate numbers. Those are not always cleanly present in the enforcement files.
- Date fields have formatting inconsistencies across years.
- Action type categorization has shifted over time.

If you want to do anything beyond a one-off lookup, you end up building a normalization layer before you can do any real analysis. Enterprise data platforms that package this data typically charge significant subscription fees. They still require internal wrangling to integrate with your own financial models.

[BankRegReports](https://www.bankregreports.com) handles the normalization layer. It links enforcement records to the broader regulatory data universe: Call Reports, UBPR ratios, Federal Reserve NIC entity data, NCUA 5300 filings, and SEC EDGAR disclosures. You can query enforcement history alongside balance sheet metrics without building that join infrastructure yourself.

## What to Look for in the Data

When you start working with FDIC enforcement actions data at scale, a few patterns become apparent quickly.

### Capital ratios at the time of action vary widely

**Capital ratios at the time of action vary more than you might expect.** PCA directives cluster around undercapitalized thresholds by definition. Consent orders and formal agreements, by contrast, appear across a wide range of capital adequacy. Compliance failures such as BSA, flood, and CRA do not discriminate by capital position. A well-capitalized community bank can receive a [consent order](/blog/bank-enforcement-actions-consent-orders/) for BSA program deficiencies without any financial distress signal in its quarterly metrics.

### Repeat actions are common

**Repeat actions are more common than single-event logic assumes.** Look at the enforcement history of institutions that ultimately failed or were acquired under distress. The modal pattern is not a single severe action. It is a sequence of informal actions (not visible publicly) followed by escalating formal actions as the situation deteriorates. The public record underrepresents this escalation path.

### Geographic clustering follows the regulatory cycle

**Geographic clustering is real and regulatory-cycle-driven.** CMP activity for flood insurance violations tends to spike after major weather events and subsequent OCC or FDIC horizontal reviews. BSA enforcement clusters around guidance updates and interagency examination priority cycles. If you are building a compliance calendar or resource planning model, the historical enforcement frequency by violation type and region is useful input.

### Orders against individuals are an underused signal

**Individual-level removal and prohibition orders are underused as a signal.** When senior officers or directors at a community bank receive prohibition orders, that institution's subsequent trajectory is worth tracking. Management quality is hard to quantify. Enforcement history against individuals is one of the few observable proxies.

### PCA Directives as a Failure Predictor

For credit analysts and anyone doing [bank failure](/blog/fdic-bank-failure-data/) modeling, PCA directives deserve particular attention. The FDIC's Prompt Corrective Action framework is capital-ratio-triggered. By the time a PCA directive is issued, the institution's capital position is already in the regulatory action zone. Historically, the distance from PCA directive to either failure or assisted acquisition has been short.

## Building a Monitoring Workflow

For ongoing surveillance across a peer group or portfolio, the practical approach is a scheduled pull of the FDIC's published enforcement decisions, filtered by date range. Say you monitor a set of institutions, such as a list of correspondent banking relationships or an investment portfolio of community bank equities. You can run this pull weekly and flag any new actions as they appear.

## Getting Started

FDIC enforcement actions data is one of the more underused public datasets in bank analysis. The signal is real. Enforcement history correlates with subsequent financial performance, failure probability, and management quality in ways that financial ratios alone do not fully capture. The barrier has been the normalization work required to use it alongside other regulatory data sources.

The data is there. The normalization work is already done.

## About this document

This is the markdown twin of the page named in `canonical_url` above. Source filings are public record; the cleaning, normalization, cross-source linkage, and derived metrics are BankRegReports' own. Attribute with a link to the canonical URL.

Markdown twins are published for editorial content only. Institution data pages do not have them. For data at scale use the API, which is documented at https://www.bankregreports.com/api/ and specified at https://www.bankregreports.com/openapi.json. It returns typed JSON with explicit units and periods, and one call replaces hundreds of page fetches.


## Sitemap

- [Glossary](https://www.bankregreports.com/glossary/): every metric, with formula and thresholds
- [Blog](https://www.bankregreports.com/blog/): analysis and explainers
- [API documentation](https://www.bankregreports.com/api/): the programmatic way to get this data
- [XML sitemap](https://www.bankregreports.com/sitemap.xml): the complete crawlable index