Bank Regulatory Enforcement Screening
Anweshna reads examination correspondence and legal disclosures for the regulatory-action history that signals how a bank actually operates under supervision.
What it screens for
- Consent orders — active or historical consent orders and their remediation status.
- Matters Requiring Attention (MRAs) — open MRAs and how long they've remained unresolved.
- Enforcement history — prior regulatory actions and whether remediation was actually completed.
- State AG investigations — active investigations by state attorneys general.
- Data breach disclosure obligations — whether a breach was disclosed on the timeline regulators require.
Why it's a blocking category
Regulatory Enforcement carries a 20% weight and is one of five blocking categories in the Banking ruleset — a score of 70 or above halts the deal for mandatory review. An open consent order or unresolved MRA is a direct signal of supervisory concern, and it typically has to be resolved (or explicitly addressed in deal terms) before regulators will approve the transaction at all.
Regulatory Enforcement FAQ
What does Anweshna screen for in Regulatory Enforcement?
Anweshna screens deal documents for consent orders, matters Requiring Attention (MRAs), and enforcement history, among other signals. See the full list of signals above.
Is Regulatory Enforcement a blocking risk category?
Yes — Regulatory Enforcement carries a 20% weight in Anweshna's composite score and is one of the categories that can independently flag a deal for mandatory review: any document scoring 70 or above here halts the deal until a human reviews it.