The Legal Stack
Independent LegalTech Analysis
← Research Briefings
Research BriefingNo. 110 · November 02, 2026 · 10 min read
Compliance & Regulation · Research Report

What FINRA Guidance, SEC Staff Releases, and Enforcement Actions Through October 2026 Actually Say About AI-Assisted Compliance Monitoring Tools — and What Financial Firm Legal Departments Need to Do Now

The Legal Stack | Regulatory Research / Financial Services | November 2, 2026

The Legal Stack | Regulatory Research / Financial Services | November 2, 2026


The Threshold Problem: Specific Citations Are Scarce, and That Matters

Before surveying what the published regulatory record says, legal departments need to understand a foundational difficulty: as of October 2026, neither FINRA nor the SEC has issued a comprehensive, standalone rulebook governing AI-assisted compliance monitoring tools in the way that, say, the EU AI Act governs high-risk automated systems. What exists instead is a layered mosaic of technology-neutral supervisory obligations, targeted regulatory notices, SEC staff publications, and a small but growing body of enforcement actions. The absence of a dedicated AI compliance-tool framework does not mean firms operate in a vacuum — it means the existing framework applies, and regulators have been explicit about that.


FINRA Regulatory Notice 24-09: What It Actually Says

FINRA Regulatory Notice 24-09, published in June 2024, is the primary published FINRA guidance addressing member firm use of generative artificial intelligence and large language models. It does not establish new rules. Instead, RN 24-09 maps generative AI use cases — including compliance monitoring support, surveillance, and customer interaction tools — onto FINRA's existing rulebook and articulates how existing obligations apply when AI is in the loop.

Several principles in RN 24-09 carry direct operational weight for legal and compliance teams.

Technology-neutral supervisory obligations apply regardless of the tool. FINRA Rule 3110 (Supervision) requires member firms to establish and maintain a supervisory system reasonably designed to achieve compliance with applicable securities laws and FINRA rules. RN 24-09 is explicit that this obligation does not change because a firm has automated a component of that system. If a firm deploys an AI model to flag potentially unsuitable transactions, the firm must still be able to demonstrate that the system — including the AI component — is reasonably designed and that supervisory principals are exercising genuine oversight of its outputs. The notice emphasizes that human reviewers must exercise genuine, independent oversight of AI outputs rather than deferring to them uncritically — a concern that FINRA's 2026 Annual Regulatory Oversight Report later characterized using the term "automation bias."

Vendor relationships require due diligence and ongoing oversight. RN 24-09 addresses the common structure in which broker-dealers license AI-powered compliance tools from third-party vendors. The notice makes clear that outsourcing a function does not outsource the regulatory obligation. Firms remain responsible for the performance of vendor systems, must conduct adequate due diligence before deployment, and must implement ongoing monitoring to detect model drift, data quality failures, or changes in vendor model versions that could affect the tool's performance.

Explainability is a supervisory requirement, not merely a best practice. Where an AI tool generates alerts — for example, flagging a transaction as potentially outside a customer's stated investment profile — supervisory principals must be able to understand, evaluate, and document the basis for action taken or not taken on each alert. A "black box" workflow in which compliance staff clear AI-generated alerts without being able to articulate the reasoning behind the flag, or the reasoning behind their decision to override it, is inconsistent with Rule 3110's reasonable design standard under the framework RN 24-09 describes.


SEC Division of Examinations: Examination Priorities and AI Surveillance

The SEC's Division of Examinations has included algorithmic compliance tools and AI-assisted surveillance in its published examination priorities in recent cycles. The Division's examination priorities documents — publicly available on the SEC website — have flagged the following areas for review in the broker-dealer and investment adviser contexts:

Algorithmic trading and surveillance. The Division has indicated that examiners will review whether firms using automated surveillance tools have implemented adequate testing, calibration, and human review processes. This includes reviewing whether firms can produce records demonstrating that surveillance alerts were reviewed in a timely manner, by appropriately qualified personnel, and that supervisory sign-off is documented with specificity.

Suitability and best-interest obligations with AI-assisted recommendation tools. Where AI is used to generate or screen investment recommendations — whether in robo-advisory platforms or hybrid models — the Division has examined whether the underlying logic reflects the firm's stated suitability or best-interest methodology, whether the tool has been tested for algorithmic bias, and whether the firm's Form ADV disclosures accurately describe how technology is used in the investment process. Regulation Best Interest (Reg BI) obligations apply to broker-dealers regardless of whether the recommendation process is automated, partially automated, or human-driven.

Books-and-records integrity when AI processes communications. The Division has flagged the use of AI tools for complaint monitoring, communications surveillance, and electronic message review as an area of examination focus. The core question is whether the firm's recordkeeping system — governed by Exchange Act Rules 17a-3 and 17a-4 for broker-dealers, and Rule 204-2 under the Investment Advisers Act for RIAs — captures all material communications and whether AI-assisted filtering does not result in the inadvertent destruction or non-retention of communications that should be preserved.


FINRA Enforcement: What the Public Record Reveals About AI-Adjacent Compliance Failures

FINRA's published enforcement actions through October 2026 do not yet contain a large body of cases in which AI-specific tool failures are the named violation. However, the enforcement record is instructive for what it reveals about supervisory system failures in automated contexts.

FINRA has imposed sanctions in cases where firms failed to review surveillance alerts generated by automated systems in a timely manner — treating the failure to act on an alert as equivalent in regulatory weight to the failure to have a system at all. The regulatory logic is consistent with RN 24-09: the obligation is to act on information the system surfaces, not merely to have the system running. Firms that can demonstrate only that an automated tool generated alerts, without records showing supervisory review and disposition of those alerts, have fared poorly in FINRA examination and enforcement contexts.

Separately, FINRA enforcement actions involving inadequate supervisory systems have increasingly referenced the firm's failure to test whether automated components were functioning as designed. Where a firm's written supervisory procedures (WSPs) describe a surveillance process that relies on automated logic, but the firm cannot produce evidence that the automated component was regularly tested, audited for accuracy, or reviewed for model degradation, examiners have treated the gap between the described system and the operational system as a Rule 3110 violation.


What Legal and Compliance Departments Must Do Now

Synthesising RN 24-09, the Division of Examinations' published priorities, and the enforcement record, legal and compliance teams at broker-dealers and RIAs should prioritize the following:

Map every AI-assisted compliance function to an existing rule. For each tool — trade surveillance, suitability screening, complaint monitoring, communications review — identify the specific FINRA rule, Exchange Act obligation, or Reg BI provision that governs the underlying activity. The AI component does not create a new regulatory hook; it sits inside an existing one.

Update written supervisory procedures to describe the AI component explicitly. WSPs that describe a compliance process without acknowledging its automated components create a documentation gap that examiners will identify. WSPs should describe what the tool does, what it does not do, who reviews outputs, at what frequency, and how escalation decisions are documented.

Build and retain records of alert review. Every alert generated by an automated surveillance or compliance tool should have a documented disposition — reviewed by a named supervisory principal, on a specific date, with a recorded outcome. Undocumented alert clearing is the most common enforcement vulnerability in this space.

Conduct and document pre-deployment vendor due diligence. Before deploying a third-party AI compliance tool, document the due diligence process: what the vendor disclosed about model design and training data, what testing the firm conducted, and what contractual obligations govern notification of material model changes.

Implement ongoing model monitoring with a defined escalation path. Post-deployment, firms should establish a schedule for reviewing whether the tool continues to perform as intended, who is responsible for reviewing performance metrics, and what triggers a compliance review or suspension of the tool pending remediation. This is not discretionary under the RN 24-09 framework — it is the operational expression of the Rule 3110 reasonable-design obligation applied to a dynamic, potentially changing AI system.

Review Form ADV and other public disclosures for accuracy. Where AI tools influence investment recommendations or portfolio management, the firm's disclosures to clients and regulators must accurately describe the role of technology. The Division of Examinations has flagged disclosure accuracy as an examination priority, and material misstatements about automated process in Form ADV Part 2A carry their own liability exposure.


The Bottom Line

FINRA RN 24-09 and the SEC's examination priorities confirm that no gap exists between the regulatory framework and AI-assisted compliance tools — the existing supervisory, recordkeeping, and disclosure obligations apply in full. What changes with AI is the operational complexity of satisfying those obligations: documentation must be more granular, vendor oversight must be continuous, and human review must be genuine rather than a nominal sign-off on algorithmic output. Firms that treat AI compliance tools as a way to reduce supervisory workload, rather than as a component of a supervised system, have consistently found themselves on the wrong side of FINRA's enforcement posture.

Filed under Compliance & Regulation → · The Legal Stack accepts no vendor funding for its research.

More Research

View all →
No. 109
10 min
What Published Federal Trade Commission Enforcement Actions, Policy Statements, and Staff Reports Through October 2026 Actually Say About AI-Generated Legal Documents, Automated Contract Formation, and the Deception Risk That Consumer-Facing Legal AI Creates
10 min
No. 108
10 min
What Federal Agency AI Use Policies Actually Say About AI-Assisted Legal Work Product: A Reading of Published OMB Guidance, DOJ AI Strategy Documents, and GSA Procurement Standards Through October 2026
10 min
No. 107
10 min
What U.S. State Consumer Protection Statutes and Their Enforcement Histories Actually Say About AI-Generated Legal Documents Sold Directly to Consumers — and Which State Attorneys General Have Moved First
10 min
© 2026 The Legal Stack — Independent LegalTech Analysis