Scenario
Huntington Bank, now a $284 billion institution, is on the cusp of entering the Federal Reserve's Category III tier. The Cadence acquisition will push its average total assets above the $250 billion threshold by Q4 2026, triggering a cascade of new liquidity‑risk requirements. This mirrors the situation many regional banks will soon face as the industry consolidates and asset sizes climb. Banks must implement a unified data‑governance framework to meet Category III liquidity requirements.
Problem
Crossing the Category III line is not merely a checklist for Treasury or Finance. It forces banks to overhaul daily Liquidity Coverage Ratio (LCR) calculations, publish quarterly disclosures, meet Net Stable Funding Ratio (NSFR) mandates, and shift internal stress‑testing from quarterly to monthly cycles. Moreover, the Federal Reserve will expect annual supervisory stress tests instead of the biennial regime. The core dilemma is the same for every new requirement: Can the bank produce the number, trace it to its source, reconcile it across systems, identify approvers, and defend the evidence? Without a unified data‑governance framework, banks risk fragmented spreadsheets, duplicated data pipelines, and audit‑ready gaps that can stall regulatory filings.
The CoComply Approach
CoComply tackles Category III readiness as an enterprise‑wide transformation, not a siloed project. Our methodology consists of four pillars:
- Data Lineage Automation – We ingest all liquidity‑relevant feeds (cash balances, repo positions, off‑balance‑sheet exposures) into a centralized metadata catalog. Each data element is automatically tagged with its source system, transformation logic, and responsible owner. This enables instant traceability for the LCR and NSFR calculations. (See our internal guide on Data Lineage: /guides/data-lineage)
- Unified Stress‑Testing Engine – Our cloud‑native engine runs both internal and regulatory stress scenarios on a monthly cadence. Results are version‑controlled, and the impact on LCR, NSFR, and overall funding ratios is displayed in a single dashboard, satisfying both internal risk committees and external examiners. (Dashboard demo: https://demo.cocomply.com/liquidity-dashboard)
- Approval Workflow Integration – By embedding CoComply’s approval workflow into existing governance platforms (e.g., ServiceNow, Jira), every liquidity metric must pass through a documented sign‑off chain before publication. The system logs who approved, when, and why, creating an auditable trail for the Federal Reserve’s supervisory tests. (Read more about workflow integration: /integrations/workflow)
- Regulatory Reporting Automation – Daily LCR calculations and quarterly public disclosures are generated automatically, pulling directly from the validated data lake. The output format matches the Federal Reserve’s XML schema, and a one‑click submission portal streams the data to the Fed’s reporting portal. (Sample XML template: /templates/fed-lcr.xml)
For banks seeking a concrete example, review the OCC’s recent guidance on liquidity risk management: OCC Liquidity Guidance (2023). Additional internal references include our Liquidity Readiness Checklist (/resources/liquidity-checklist) and the Category III Transition Playbook (/playbooks/category-iii).
Closing
Category III readiness is a strategic, enterprise‑wide shift that demands integrated data governance, automated stress testing, and documented approvals. By adopting CoComply’s four‑pillar framework, banks can confidently answer the pivotal question: Can we produce, trace, reconcile, approve, and defend every liquidity number? The result is not just regulatory compliance—it’s a resilient operating model that positions the bank for sustainable growth beyond the $250 billion asset mark.
Tags: LiquidityRisk, CategoryIIIReadiness, RegulatoryReporting