119-HR-8278 Corporate Impact Analysis

Summary

• Scope: Directs covered financial regulators to assess supervisory tech stacks, data collection/security, market‑risk monitoring tools, and procurement rules; then submit a joint report with workforce, data‑sharing, and upgrade plans, including estimated transition costs for supervised entities. Deadlines: 180 days for assessments; report 18 months after assessments; updates every 5 years. (docs.house.gov)
• Current status: Advanced by the House Financial Services Committee on May 13, 2026 by unanimous vote in markup. (bankingjournal.aba.com)
• Baseline context: Federal legacy IT remains costly to maintain (roughly 79% of FY2025 IT spend on operations/maintenance at CFO‑act agencies), and GAO highlights gaps in agencies’ performance measures and skills for fintech/AI oversight. (files.gao.gov)
• Policy posture (institutional, risk/return lens): Near‑term compliance burden is modest and government‑side; longer‑term costs/benefits for industry depend on whether the post‑report roadmap standardizes data interfaces or expands reporting. Opportunities exist for vendors (SupTech/RegTech, cybersecurity, cloud) and for financial institutions able to leverage interoperability; risks include procurement delays and energy/compute externalities from scaled analytics. (bis.org)

Economic Effects

Direct fiscal exposure appears limited at authorization, but downstream cost and competitive dynamics depend on eventual upgrade choices and data‑sharing requirements.

• Federal budget: A close predecessor (H.R. 7437, 118th) drew a CBO estimate of +$3M direct spending and −$1M revenue over 10 years, largely for added staff time; similar order‑of‑magnitude is plausible here unless Congress later funds major modernizations. (govinfo.gov)
• Agency execution capacity: GAO finds federal IT portfolios remain O&M‑heavy (≈79% in FY2025), implying modernization headwinds without new capital or reallocation; this may slow benefits realization. (files.gao.gov)
• Procurement pathways: Agencies can tap the Technology Modernization Fund (TMF) but GAO reports realized savings thus far have been minimal versus plans; TMF repayment policies have also tightened, affecting deal economics and repayment risk. (tmf.cio.gov)
• Industry compliance costs: The bill requires agencies to estimate what supervised entities would spend to modify systems for data‑sharing; effects will vary by data standardization choices. Regulators are simultaneously soliciting input to reduce Call Report burden—signaling potential for net‑neutral or even reduced recurring load if duplicative fields are rationalized, though transition costs could arise. (docs.house.gov)
• Competitive dynamics: Standardized APIs/ontologies can lower integration costs and favor firms with modern data pipelines (first‑mover advantage). FSB/BIS analyses suggest SupTech/RegTech can improve efficiency and risk detection but stress the need for data standards and governance to avoid duplicative tooling and vendor lock‑in. (fsb.org)

Social Effects

Primary channels are consumer protection, market integrity, inclusion risks, and safeguards for sensitive data.

• Consumer protection and market integrity: GAO documents regulators’ growing use of analytics/AI in supervision; effective deployment can speed anomaly detection and reduce errors in reported data. (gao.gov)
• Illicit finance and fraud: Treasury’s 2024 illicit‑finance strategy urges expanded use of AI/data analytics across government and enhanced public‑private information sharing; modernized supervisory tooling can support these aims if privacy and governance controls are robust. (home.treasury.gov)
• Data privacy and confidentiality: Financial regulators operate under strict confidential supervisory information (CSI) regimes (e.g., 12 CFR §261.2), constraining data‑sharing architectures and requiring auditable access controls; poor implementation could raise legal and reputational risks. (ecfr.io)
• Distributional effects: Smaller institutions may face proportionally higher one‑time transition costs when interfaces or reporting schemas change, even if recurring burden declines—consistent with past FFIEC burden‑reduction/modernization efforts that still required initial system updates. (occ.gov)

Environmental Effects

Impacts stem from data‑center energy demand versus federal optimization policies and cloud shifts.

• AI and data‑center load: IEA projects electricity use from data centres/AI/crypto could double by 2026; data centres account for roughly 2.6% of global electricity demand in the base case. Scaling supervisory analytics without efficiency gains could raise agencies’ compute footprint. (iea.org)
• Mitigating factors: Federal Data Center Optimization Initiative (DCOI) encourages consolidation and efficiency (e.g., virtualization, metering, PUE targets) and cloud adoption, partially offsetting compute growth if agencies retire legacy on‑prem systems. Net effect depends on workload placement and procurement specs. (cio.gov)

Temporal Analysis

Short‑run actions are procedural; long‑run outcomes hinge on follow‑on implementation choices.

• 0–12 months post‑enactment: Complete 180‑day assessments; inventory supervisory tooling, data pipelines, procurement rules, and workforce gaps; identify quick wins aligned with OMB’s zero‑trust requirements (e.g., identity/logging baselines). (docs.house.gov)
• ~18–36 months after assessments: Deliver joint interagency report; agencies begin prioritized upgrades and pilot evaluations; early procurements may leverage TMF or existing vehicles, with measurable KPIs for data quality, timeliness, and auditability. (docs.house.gov)
• 3–7 years: If Congress and agencies pursue shared data standards/APIs and cross‑agency analytics, expect efficiency gains in exams and potential changes to reporting for supervised entities—producing one‑time transition costs with longer‑term interoperability benefits if standards mature. (fsb.org)

Unintended Consequences

Risks to monitor and mitigate through governance, procurement design, and privacy/security controls.

• Procurement slippage/vendor lock‑in: Complex analytics stacks can entrench incumbent vendors absent open standards; BIS/FSB emphasize governance and data standards to avoid stranded investments. (bis.org)
• Cost pass‑through via fees: Prior CBO analysis noted regulators might raise fees to offset report costs (private‑sector mandate well below UMRA thresholds); scale could grow if future implementations expand. (govinfo.gov)
• Small‑bank burden asymmetry: Transition costs may weigh more heavily on community institutions lacking internal data engineering capacity, even where net burden later declines. (occ.gov)
• Compute externalities: If agencies ramp AI without strict efficiency targets, energy use and scope‑2 emissions could rise despite DCOI; procurement should include energy/PUE/SLA criteria. (iea.org)

Assessment

Analytical summary (not advocacy).

Neutral. The bill is primarily a diagnostic/reporting mandate with modest direct fiscal effects at passage; upside depends on whether agencies translate findings into interoperable standards, measurable KPIs, and security‑by‑design upgrades aligned to zero‑trust. Execution risks include procurement delays, privacy/CSI controls, and uneven transition costs for smaller institutions; energy externalities rise if AI‑heavy analytics scale without efficiency requirements. (govinfo.gov)

Key Metrics

Figures that frame likely exposure and operating context.

Sourcing

Selected high‑salience sources underpinning this assessment.

• Bill text and deadlines: H.R. 8278 (IH), docs.house.gov. (docs.house.gov)
• Committee action: HFSC markup listing and ABA coverage of unanimous support on May 13, 2026. (docs.house.gov)
• Legacy IT/O&M baseline and AI oversight gaps: GAO IT modernization (GAO‑25‑107795); GAO AI in financial services (GAO‑25‑107197). (files.gao.gov)
• CBO fiscal benchmark (prior bill): House Report 118‑728 (includes CBO estimate). (govinfo.gov)
• SupTech/RegTech benefits and governance needs: FSB 2020; BIS FSI Insights 2024. (fsb.org)
• Zero‑trust policy anchor for cybersecurity upgrades: OMB M‑22‑09 (White House). (whitehouse.gov)
• Energy context: IEA Electricity 2024 (doubling by 2026) and IEA Energy & AI (share of demand). (iea.org)
• Data‑center optimization policy: CIO.gov DCOI overview. (cio.gov)
• Call Report burden signals (transition vs recurring load): OCC/FDIC notices. (occ.gov)
• TMF as a modernization vehicle and repayment/savings track record: TMF site; GAO review. (tmf.cio.gov)
• Confidential Supervisory Information constraints: 12 CFR §261.2 (eCFR). (ecfr.io)