The $1.2 Billion AML Wake-Up Call
Lessons from FinCEN’s Bank of America Enforcement Action
📅 October 28, 2026
📅 October 28, 2026
On October 13, 2026, the U.S. Department of the Treasury announced an enforcement package exceeding $1.21 billion involving Bank of America. The Financial Crimes Enforcement Network (FinCEN) assessed a $1.2 billion civil money penalty for willful violations of the Bank Secrecy Act (BSA), citing deficiencies in the bank’s anti-money laundering (AML) program, customer due diligence (CDD), foreign correspondent banking controls, and suspicious activity reporting.
The action offers a clear lesson for financial institutions: having AML controls in place is not enough. Those controls must identify suspicious activity, support timely investigations, and adapt as risks evolve.
According to FinCEN’s consent order, deficiencies between January 1, 2018 and July 1, 2025 undermined the bank’s ability to identify and report suspicious transactions.
The bank’s transaction monitoring system, known as Event Processor, generated alerts that were grouped and scored. Generally, an Event Group had to reach a score of 20 before being investigated. FinCEN found that the scoring methodology and thresholds were not sufficiently effective, allowing potentially suspicious activity to remain below the investigation threshold.
In December 2023, the bank lowered the threshold and conducted a one-time review. That review identified more than 8,000 suspicious activity reports (SARs) involving approximately $3.96 billion in previously unreported suspicious activity.
The order also identified weaknesses in how monitoring rules and risk factors were maintained, how alerts were rescored or suppressed, and how investigations were prioritized. In some cases, investigations were delayed for months or longer.
These findings underscore a fundamental point: a monitoring system’s effectiveness cannot be measured simply by whether it generates alerts. Institutions must also assess whether their rules, thresholds, and investigative processes identify the risks they are designed to detect.
FinCEN determined that the bank failed to report more than $5 billion in suspicious transactions in a timely manner. Approximately $1 billion involved national security-related and priority illicit finance risks, including Chinese Money Laundering Networks (CMLNs), fraud, and potential trade-based money laundering (TBML) connected to the U.S. southwest border.
The consent order describes suspicious patterns that included repeated high-value credit card purchases at major retailers and shipping companies, payments from third parties to settle credit card balances, and large wires to China with generic descriptions such as “for goods” but no clear business rationale.
Other warning signs included repeated transfers to counterparties with limited online presence and businesses operating from residential addresses.
The order also highlighted gaps in monitoring negotiable instruments. Two corporate customers operating in the online auto auction sector deposited large volumes of money orders that were not effectively monitored. More than $600 million in suspicious money order deposits was not reported in a timely manner.
These examples show how suspicious activity can become harder to detect when monitoring controls do not adequately account for a customer’s products, transaction channels, counterparties, and expected activity.
FinCEN also identified weaknesses in the bank’s CDD processes. Some customers received payments from unknown third parties or conducted transactions inconsistent with their expected activity. Internal concerns involving potential fraud, TBML, and possible narcotics trafficking did not always lead to timely action or reassessment of related customer relationships.
Effective CDD must do more than establish a customer’s identity at onboarding. It should provide an ongoing understanding of how the customer operates, who sends and receives funds, and whether actual activity aligns with the institution’s risk assessment.
When transaction monitoring identifies unusual activity, that information should inform customer risk ratings and decisions about whether enhanced due diligence, further investigation, or SAR filing is warranted. If these processes operate in silos, warning signs may be missed even when relevant information exists within the institution.
The consent order points to shortcomings in internal testing, audit, and remediation. Identifying a control weakness is only the first step. Institutions must determine its root cause, assess the impact on previously reviewed transactions, and verify that corrective actions work.
The bank estimated that lowering its monitoring threshold would double monthly investigation volumes and require approximately 750 additional staff. While resource constraints are a practical consideration, they cannot substitute for an effective risk-based approach. Thresholds should reflect the institution’s risk exposure, not simply the number of alerts investigators can manage.
Testing should therefore examine whether monitoring rules capture relevant suspicious patterns, whether alert suppression and scoring changes are appropriately governed, and whether investigations and SAR filings occur within a reasonable timeframe.
The order requires significant independent review and remediation, including a lookback of suspicious activity reporting covering activity from January 2022 through completion of remediation. The review will consider areas such as credit card activity, negotiable instruments, cross-border transactions, and Event Groups that fell below previous investigation thresholds.
The bank must also undergo independent reviews of its interim and final transaction monitoring controls, CDD, foreign correspondent account due diligence, and relevant AML data governance. The order contemplates the use of advanced analytics and network analysis to help identify patterns of suspicious activity.
These requirements reflect the scale of the identified deficiencies and the need to assess not only whether controls have been updated, but whether they are effective in practice.
The Bank of America enforcement action highlights several priorities for AML compliance teams:
The Bank of America enforcement action illustrates how weaknesses across transaction monitoring, customer due diligence, and suspicious activity reporting can compound over time. Controls that appear functional on paper may still fail if their thresholds are poorly calibrated, investigations are delayed, or warning signs do not lead to appropriate escalation.
For financial institutions, the priority is not simply to generate more alerts. It is to build AML programs that identify meaningful risks, support timely decisions, and adapt as suspicious activity patterns change.
At the Institute for Financial Integrity, we work with financial institutions to assess where their teams’ knowledge and skills fall short of their risk profile, then build customized training that addresses those gaps, from transaction monitoring governance and TBML typologies to the convergence of AML and sanctions obligations, and many more. Our DOLFIN® platform extends that work with on-demand learning for compliance teams at every level.
Talk to IFI about a training needs assessment for your organization.










This site uses cookies. By continuing to browse the site, you are agreeing to our use of cookies.
Accept settingsHide notification onlySettingsWe may request cookies to be set on your device. We use cookies to let us know when you visit our websites, how you interact with us, to enrich your user experience, and to customize your relationship with our website.
Click on the different category headings to find out more. You can also change some of your preferences. Note that blocking some types of cookies may impact your experience on our websites and the services we are able to offer.
These cookies are strictly necessary to provide you with services available through our website and to use some of its features.
Because these cookies are strictly necessary to deliver the website, refusing them will have impact how our site functions. You always can block or delete cookies by changing your browser settings and force blocking all cookies on this website. But this will always prompt you to accept/refuse cookies when revisiting our site.
We fully respect if you want to refuse cookies but to avoid asking you again and again kindly allow us to store a cookie for that. You are free to opt out any time or opt in for other cookies to get a better experience. If you refuse cookies we will remove all set cookies in our domain.
We provide you with a list of stored cookies on your computer in our domain so you can check what we stored. Due to security reasons we are not able to show or modify cookies from other domains. You can check these in your browser security settings.
These cookies collect information that is used either in aggregate form to help us understand how our website is being used or how effective our marketing campaigns are, or to help us customize our website and application for you in order to enhance your experience.
If you do not want that we track your visit to our site you can disable tracking in your browser here:
We also use different external services like Google Webfonts, Google Maps, and external Video providers. Since these providers may collect personal data like your IP address we allow you to block them here. Please be aware that this might heavily reduce the functionality and appearance of our site. Changes will take effect once you reload the page.
Google Webfont Settings:
Google Map Settings:
Google reCaptcha Settings:
Vimeo and Youtube video embeds:
You can read about our cookies and privacy settings in detail on our Privacy Policy Page.
Privacy Policy