Federal banking enforcement - agency split
Who Polices the Banks: 4,954 Federal Enforcement Orders, Split Almost Evenly.
Of 4,954 federal banking enforcement-order rows in the 2026-02-25 committed snapshot, 2,514 are Federal Reserve rows (50.7%) and 2,440 are OCC rows (49.3%). The page is aggregate-only and names no institution, consumer, or individual.
Key findings
federal banking enforcement-order rows are in the committed 2026-02-25 snapshot from OCC EASearch CSV and Federal Reserve enforcement JSON.
of the orders are Federal Reserve rows: 2,514 of 4,954 total orders.
of the orders are OCC rows: 2,440 of 4,954 total orders.
federal regulators carry the entire count in this snapshot. The page reports institution-level enforcement-order records as aggregate agency counts only.
At a glance
By federal regulator
The table keeps the study at the agency level. The source table contains institution and party fields for ingestion and provenance, but this public research artifact exports only regulator, source-agency code, order count, and share of total.
| Agency | Source code | Enforcement orders | Share of total |
|---|---|---|---|
| Federal Reserve | federal-reserve | 2,514 | 50.7% |
| OCC | occ | 2,440 | 49.3% |
What this means
The Federal Reserve and OCC split the public banking-enforcement order count almost evenly in this snapshot. That matters for research and monitoring because a one-agency source pull misses roughly half of the federal order corpus represented here. The count is descriptive; it does not compare severity, monetary amount, or legal outcome.
What this counts - and what it does not
- Counts enforcement-order rows. The total is a row count in
public.federal_banking_enforcement_actions, not a count of unique institutions. - Agency split only. The public artifact groups by
agencyand exports no institution, party, person, or document fields. - No consumer surface. These are federal banking enforcement public records, not consumer eligibility reports, risk scores, or dossiers.
- No conduct finding by Fonteum. The study reports source-published order rows and makes no determination about any institution or party.
Methodology
The study aggregates public.federal_banking_enforcement_actions, a warehouse table populated from OCC EASearch CSV and Federal Reserve enforcement JSON feeds. It filters to current rows in the 2026-02-25 source snapshot and groups by agency.
The figures on this page are baked into a committed TypeScript snapshot. The source snapshot is signed, attested, chained, and re-checkable through Fonteum's snapshot process; the page itself does not query a live database at request time.
Reproduce this
Re-run this aggregate query against the federal banking enforcement table:
-- Who Polices the Banks: 4,954 Federal Enforcement Orders, Split Almost Evenly.
-- Source: public.federal_banking_enforcement_actions
-- Source families: OCC EASearch CSV + Federal Reserve enforcement JSON.
-- Snapshot date: 2026-02-25.
-- Aggregate-only: this query selects agency counts and does not select party,
-- institution, document, or consumer fields.
WITH agency_counts AS (
SELECT
agency,
count(*)::int AS enforcement_orders
FROM public.federal_banking_enforcement_actions
WHERE valid_to IS NULL
AND snapshot_date = DATE '2026-02-25'
GROUP BY agency
),
totals AS (
SELECT sum(enforcement_orders)::int AS total_orders
FROM agency_counts
)
SELECT
CASE agency
WHEN 'federal-reserve' THEN 'Federal Reserve'
WHEN 'occ' THEN 'OCC'
ELSE agency
END AS agency,
agency AS source_agency,
enforcement_orders,
round((enforcement_orders::numeric / total_orders) * 100, 1) AS share_pct
FROM agency_counts
CROSS JOIN totals
ORDER BY enforcement_orders DESC;
-- Expected rows from the 2026-02-25 committed snapshot:
-- Federal Reserve | federal-reserve | 2,514 | 50.7
-- OCC | occ | 2,440 | 49.3
-- Total | | 4,954 | 100.0
Re-check the source snapshot
The study is tied to the committed 2026-02-25 aggregate snapshot. Re-checking means re-running the SQL against that source snapshot or a newer one, then comparing the agency counts.
Re-check a signed snapshot -> or inspect the source-family registry at /sources.
How to cite this
Fonteum (2026). Who Polices the Banks: 4,954 Federal Enforcement Orders, Split Almost Evenly. Derived from OCC EASearch CSV and Federal Reserve enforcement JSON, snapshot 2026-02-25. https://fonteum.com/gov/research/federal-banking-enforcement-split-2026
Canonical URL: https://fonteum.com/gov/research/federal-banking-enforcement-split-2026 · License: U.S. Government Works (public domain; 17 U.S.C. §105)
Related government evidence
Limitations
- Counts are agency-level enforcement-order rows, not unique banking institutions.
- The public study artifact is aggregate-only and names no institution, consumer, or individual.
- The table combines OCC EASearch CSV rows with Federal Reserve enforcement JSON rows; source fields are not normalized into severity rankings.
- Re-run the SQL against a later source snapshot before citing the numbers as current live counts.
Sources
Two primary federal source families feed the aggregate: OCC EASearch enforcement action CSV and Federal Reserve enforcement action JSON.
Source: OCC EASearch CSV and Federal Reserve enforcement actions JSON, snapshot 2026-02-25. U.S. Government Works.
Frequently asked questions
What does this study count?
It counts 4,954 federal banking enforcement-order rows in public.federal_banking_enforcement_actions, grouped by source agency. The snapshot combines OCC EASearch CSV rows and Federal Reserve enforcement JSON rows as of 2026-02-25.
Which regulator accounts for the larger share?
The Federal Reserve accounts for 2,514 rows, or 50.7%. OCC accounts for 2,440 rows, or 49.3%. The split is almost even.
Does this page name banks, companies, consumers, or individuals?
No. The page and downloads are aggregate-only. They report agency, source-agency code, enforcement-order count, and share of total. They do not publish institution names, party names, document labels, or consumer-level facts.
Is this a severity ranking?
No. The two agencies publish different source feeds and fields. This page reports the public record's agency split; it does not score, rank, or infer severity from an order count.
How can I reproduce the numbers?
Use the SQL linked on this page against public.federal_banking_enforcement_actions, filtered to the 2026-02-25 snapshot and current rows, then group by agency. The JSON and CSV downloads are committed aggregate snapshots generated from those results.