The Governing Framework: SR 11-7 and the Interagency Statement
Financial institutions deploying AI and machine learning for transaction monitoring, KYC screening, or fraud detection must still satisfy model risk management expectations set by SR 11-7 and the 2021 Interagency Statement on Model Risk Management for BSA/AML Compliance. Neither document was written with AI specifically in mind, so examiners and validators apply the same three-part framework that has governed model risk since 2011: model development, implementation, and use; independent model validation; and governance.
SR 11-7 identifies three core elements of effective validation: evaluation of conceptual soundness, ongoing monitoring, and outcomes analysis, including backtesting. It also requires that validation be performed by staff independent of the teams that develop, own, or use the model, and that documentation be sufficient for someone unfamiliar with the model to understand how it operates, including its limitations and key assumptions.
The 2021 Interagency Statement adds BSA/AML-specific context. It clarifies that not every BSA/AML compliance system meets the formal definition of a model, that risk management practices should be tailored to a system's complexity and risk, and that banks do not need prior supervisory approval before implementing AI-based BSA/AML solutions. The statement explicitly encourages responsible innovation, including the use of artificial intelligence and machine learning, in compliance programs.
AI-Specific Complications for Validation
Traditional SR 11-7 validation assumes a model specification that stays largely fixed between review cycles. AI and machine learning models used for transaction monitoring or customer risk scoring often retrain or adapt on new data, which complicates a fixed-point review of conceptual soundness. Ensemble methods and deep learning approaches can also limit interpretability, constraining a validator's ability to assess model logic through direct inspection.
Data drift in underlying transaction or customer behavior patterns can degrade model performance between scheduled revalidation cycles, which is one reason more frequent or continuous outcomes analysis is often necessary for AI-driven AML systems. Third-party or vendor-supplied models add another layer of complexity: institutions depend on documentation and testing artifacts they did not produce themselves, which raises questions for independent validation functions that must still exercise effective challenge.
A related gap involves runtime behavior. Adaptive or self-tuning models can behave differently in production than the logic described in original validation documentation. Static, point-in-time validation captures intended model design, but it does not by itself confirm that runtime behavior remains consistent with that design over time.
Runtime governance capabilities, such as runtime monitoring, policy enforcement, and audit logging provided by platforms like Trussed AI, can supply a continuous record of actual model and agent behavior in production. This complements periodic validation rather than replacing it, and it helps close the gap between documented model logic and observed system behavior.
Validation Checklist
Use the following checklist to assess whether an AI-based AML system addresses both core SR 11-7 expectations and AI-specific gaps in documentation, testing, monitoring, and oversight.
- Documentation covers data lineage, feature engineering, and training data provenance sufficient for an independent reviewer to reconstruct model logic.
- Explainability tooling or surrogate-model techniques are available where the underlying AI model cannot be directly inspected.
- A defined process exists for evaluating whether retraining or parameter updates constitute a model change requiring incremental revalidation.
- Independent validation staff have the technical capability and access needed to review AI/ML methodologies, not only traditional statistical models.
- Vendor documentation for third-party AI AML tools covers model methodology, training data characteristics, and update or retraining cadence.
- Outcomes analysis and backtesting are performed on a schedule consistent with SR 11-7 expectations for ongoing monitoring.
- Monitoring mechanisms can detect data drift, performance degradation, or alert-volume anomalies between formal validation cycles.
- Independent testing required under the FFIEC BSA/AML Examination Manual evaluates transaction monitoring rules, thresholds, and overall system effectiveness.
- Change management processes define thresholds for when an AI model update triggers formal revalidation versus routine monitoring.
- Board- or senior-management-level oversight extends to AI-specific risks, including retraining frequency and explainability limitations.