Personal Liability for AML Officers: Admissions, Alert Caps and Dismissed Charges

AML compliance officer personal liability cases at MoneyGram and U.S. Bank grew out of failed reporting and monitoring controls. Behind those failures were decisions to keep agents fraud staff wanted removed, cap alerts to match available staff, or leave staffing shortages unaddressed. If you know who made those decisions, your account can explain far more than an organization chart.

Can a Corporate Officer Be Held Personally Liable?

Yes. The Financial Crimes Enforcement Network pursued a former MoneyGram compliance executive over failures to maintain an effective program and report suspicious activity. A former U.S. Bank risk and compliance executive faced individual civil actions involving resources, alert limits and staffing deficiencies. The Office of the Comptroller of the Currency terminated its action against a former Rabobank chief compliance officer.

Who had the information? Who could change the control? Who received the warning, and what happened afterward? The MoneyGram and U.S. Bank cases turn on those operational questions.

The agencies also have different jobs. Their separate actions against the same executive can concern the same compliance failure while producing distinct orders.

What the AML Program Puts in the Officer’s Hands

Bank customer due diligence adds an understanding of customer relationships, risk profiles, ongoing monitoring and risk-based updates. These functions connect the policy on paper to the transactions the institution actually handles.

They also spread the relevant knowledge across the business. An investigator may know what happened to an alert. A monitoring engineer may understand the rule that generated it or kept it out of review. An auditor may have identified the gap, while a manager approved staffing or an exception. The person assigned to run compliance and the person controlling its resources may contribute different parts of the account.

The Wharton Initiative on Financial Policy and Regulation’s 2024 paper, Anti-Money Laundering: Opportunities for Improvement, examines that tension between expectations and capacity. It discusses research suggesting that compliance officials can see their work as aligned with law enforcement while others inside their firms treat it as an expense to minimize. Its proposed design principle is direct:

That tension is concrete in the cases below. Information can exist in the fraud department and fail to reach AML staff. A monitoring system can limit its output to the staff available to review it. An insider who understands either arrangement can explain the decision hidden behind the program description.

MoneyGram’s Former Compliance Executive and the Agents Who Stayed

MoneyGram’s individual compliance case concerned an allegedly ineffective AML program and failures to report suspicious activity. Under the company’s separate criminal agreement, MoneyGram admitted that its transfer agents facilitated fraud against consumers sending money through its network.

Under its deferred prosecution agreement announced in November 2012, MoneyGram admitted aiding and abetting wire fraud and failing to maintain an effective AML program. Managers rejected fraud staff’s recommendations to terminate agents. Fraud and AML information did not flow adequately, and the company failed to file suspicious activity reports on agents known to be involved in fraud.

The warning had already reached people inside the business. Fraud staff wanted agents removed. Managers kept them. The same institution that handled the transfers had information about the fraud, but its reporting process did not adequately use that information. For an employee who worked with agent complaints or termination recommendations, that is a recognizable failure between departments, decisions and reporting.

The individual action had its own outcome. The Financial Crimes Enforcement Network’s December 2014 assessment sought $1 million from the former compliance executive. The civil settlement announced in 2017 reduced the payable amount to $250,000 and imposed a three-year restriction on compliance work. The later settlement included admissions to specified conduct.

U.S. Bank: Staffing Set the Monitoring Limits

AML compliance officer personal liability over alert caps arose at U.S. Bank, where the former risk and compliance executive’s responsibilities included compliance resources and monitoring limits. The decision about how much activity reached review was part of the control failure itself.

In its separate criminal case, U.S. Bancorp accepted responsibility under a deferred prosecution agreement describing how the bank limited transaction-monitoring alerts to staffing capacity. The agreement also addressed the failure to report activity associated with a payday-lending scheme on time. Staffing capacity was setting the reach of the monitoring system.

An alert cap connects a technical setting to a management decision. The monitoring team can explain how the limit worked. The staffing record can explain the capacity it was built around. A resource request or escalation can show who knew the arrangement needed attention. Together, those records make it possible to understand a failure that a description of the software alone would miss.

The Financial Crimes Enforcement Network’s February 2020 assessment imposed a $450,000 individual civil penalty over compliance resources and alert limits, while the Comptroller’s separate consent order in March 2020 imposed $50,000 over the alleged failure to address or escalate known AML staffing deficiencies.

The distinction inside that last allegation matters. Addressing a shortage and escalating it describe different decisions. Someone may know the review team lacks capacity, someone else may control hiring, and another manager may receive the request for help. The useful account identifies those roles and what each did when the shortage became known.

Rabobank’s Former Compliance Officer and the Terminated Action

The Office of the Comptroller of the Currency terminated its enforcement action against Rabobank’s former chief compliance officer on April 5, 2023. It dismissed the charges without imposing the proposed employment prohibition or civil money penalty.

Rabobank’s corporate case concerned serious interference with supervision. In its guilty plea, the bank admitted conspiring with former executives to obstruct the Comptroller’s examination of its AML program. The conduct included concealing AML deficiencies from the regulator.

The bank pleaded guilty to hiding its AML deficiencies from the regulator. The regulator dismissed the charges against its former compliance chief.

AML Officer Employment Ban Versus Consent Order Penalty

An AML officer employment ban restricts work. A consent order penalty requires a payment. The MoneyGram executive’s settlement combined a payment with a restriction on compliance work. The U.S. Bank executive’s FinCEN assessment and the Comptroller’s order imposed separate civil penalties.

The U.S. Bank assessment also recorded that the executive had been out of a financial-institution compliance role since June 2014. The assessment described his earlier employment history rather than imposing a new employment ban.

What an AML Insider Can Bring to a Whistleblower Case

An AML insider can explain how the institution’s controls worked, who had the authority to change them and what happened after a warning. Compliance officers, investigators, auditors, monitoring engineers and managers may each know a different part of that sequence. The most useful account connects the failure to an actual decision inside the business.

At MoneyGram, that connection runs through agent information, rejected termination recommendations and reporting failures. At U.S. Bank, it runs through alert limits, staffing capacity and escalation. Those are concrete subjects for a conversation with us: the recommendation that went nowhere, the resource decision behind a monitoring limit, or the information that never reached the people responsible for reporting it.

Your role, your own involvement in the decisions and the applicable award program are matters we assess with you and AML whistleblower counsel. We use your understanding of the operation to identify the conduct a case needs to explain.

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. FinCEN’s AML whistleblower program is a separate route. We assess the program that fits the conduct you know about.

You Know What Happened After the Warning

We build a case strategy around your knowledge of the business and bring in AML whistleblower lawyers who understand institutional controls and individual responsibility. We stay beside you as partners throughout the case. If you saw an agent protected, an alert cap imposed or a staffing problem left unresolved, speak with our AML whistleblower experts about the decisions behind it.