Contents
The Standard Chartered sanctions money laundering case includes a $340 million New York civil settlement over concealed Iranian payment information, followed by separate actions over failed monitoring and further sanctions violations. The bank knew Iranian connections that it kept out of the payment record. For someone inside a payments or compliance team, that gap between what the bank knew and what its systems showed is the heart of the story.
Standard Chartered is a global bank headquartered in London. Its New York branch and other U.S. financial institutions processed dollar payments for customers abroad. The cases reach from the information removed before a payment arrived in the United States to the monitoring rules that failed after the bank had already faced enforcement.
Correspondent banking lets one bank process payments for another bank and its customers. The bank handling the dollars may not hold the customer’s account or have the same information about the business behind it.
In Standard Chartered’s case, that separation mattered. Its Dubai branch could hold the account while its New York branch or another U.S. bank processed the dollars. The Treasury’s Office of Foreign Assets Control, in its account of the Iran-related payments, describes customers sending instructions to Dubai while physically located or ordinarily resident in Iran. A Dubai account did not tell the whole story about where the customer was operating.
Removing Iranian identifiers from payment messages is one example of sanctions evasion in the Standard Chartered cases. The bank’s September 21, 2012 New York consent order describes the removal or omission of identifying information through cover payments and a practice called repair. The later New York order records the bank’s admission of intentional stripping.
The resolved account covered approximately 59,000 transactions from January 2001 through 2007. The U.S. processing bank was being asked to screen a payment without the Iranian connection Standard Chartered already knew.
Calling the practice repair made it sound like routine processing. The information being removed was precisely what a sanctions review needed. Comparing the original payment instruction with the message sent onward can reveal that change, while the direction to alter it can show who wanted the connection hidden.
A related access problem appears in Danske Bank‘s guilty plea. Danske admitted misleading U.S. banks that supplied dollar clearing. After one correspondent ended the relationship, it sought another and misrepresented why the earlier bank had left. The common thread is control over what the bank providing access gets told.
Anti-money laundering transaction monitoring red flags include gaps between the written rulebook and the system that actually runs. Those were the problems described in Standard Chartered’s August 19, 2014 New York consent order, after an independent monitor found deficiencies in transaction surveillance.
The consent order describes the monitor’s findings: implemented monitoring scenarios did not match the rulebook, contained errors or were incomplete. Testing failed too. New York imposed a separate $300 million civil penalty for this later control failure.
The distinction matters to the employee who knows the system. A rulebook describes what the bank intends to detect. The deployed scenario determines what it actually tests. When those diverge, a policy can look complete while the transactions pass through a different set of rules.
That makes scenario versions, test results and internal findings useful evidence. They connect the promised control to the one that ran, and management’s response to the defect. The system meant to improve the bank’s controls had become another control failure.
Under its amended deferred prosecution agreement, announced on April 9, 2019, Standard Chartered admitted that two former Dubai employees helped Iran-connected customers conduct dollar transactions through the U.S. financial system from 2007 through 2011. The Justice Department’s account of those admissions explains what the employees knew and what they concealed.
One customer operated business accounts at the Dubai branch while living in Iran. The employees helped manage those accounts and disguised the Iranian connections. They knew the customer’s businesses operated from Iran and conducted dollar transactions for Iranian interests.
The bank admitted processing approximately 9,500 U.S. dollar transactions totaling approximately $240 million for the customer’s companies. More than half resulted from compliance deficiencies that allowed customers to request dollar transactions from within sanctioned countries, including Iran.
A separate indictment of the customer alleged that supposed general trading companies registered in the United Arab Emirates served as fronts for a money exchange business in Iran.
The sequence runs from the New York stripping settlement in 2012, through the separate monitoring case in 2014, to the coordinated sanctions resolutions in 2019.
The Federal Reserve’s December 2012 civil order imposed $100 million for sanctions-related practices and information supplied to examiners.
In April 2019, the Federal Reserve’s separate civil order imposed $163,687,500, while New York’s consent order imposed $180 million.
The Office of Foreign Assets Control’s coordinated civil settlement was $639,023,750. Payments to other U.S. federal agencies for the same conduct and periods could satisfy that obligation up to an equal amount.
That civil settlement covered 9,335 transactions totaling $437,553,380 from June 2009 until June 2014, involving Burma, Cuba, Iran, Sudan and Syria. The agency found that the transactions gave companies subject to U.S. sanctions access to the U.S. financial system.
The Office of Foreign Assets Control separately required $18,016,283 for apparent Zimbabwe sanctions violations. The accounts belonged to designated or blocked parties at the bank’s Zimbabwe affiliate. Funds transfers and debit or credit card transactions produced settlement transfers processed in New York or through other U.S. financial institutions.
The agency found that efforts to isolate those customers were insufficient. Some personnel at the Zimbabwe affiliate appeared unaware that customers, including those on the sanctions list, could use their bank-issued credit cards outside Zimbabwe, including in the United States.
The local account was only the starting point. The card and settlement network carried the transaction farther, into the U.S. financial system. That is a different control problem from deleting an Iranian identifier from a wire.
The Office of Foreign Assets Control’s April 2019 notice describes new measures to block payment instructions from sanctioned countries, stronger customer due diligence, upgraded screening tools and training for the bank’s correspondent clients. It also records a special board committee overseeing financial crime compliance. By then, Standard Chartered had spent $2.8 billion on financial crime compliance since 2012.
The New York oversight arrangements changed as well. The regulator’s monitor ended on December 31, 2018, followed by a consultant, as described in the New York transition order.
Spending and oversight matter, but the operational question remains what a control detects. The 2024 Wharton Initiative on Financial Policy and Regulation paper Anti-Money Laundering: Opportunities for Improvement argues that anti-money laundering and sanctions systems need several complementary measures, combining numerical and qualitative evidence.
The paper also describes the conflicting incentives inside financial institutions: compliance staff may see their work as aligned with law enforcement while others in the firm see an expense to minimize.
A whistleblower brought a separate False Claims Act case alleging that concealed Iranian transactions extended beyond the earlier resolutions and that their disclosures produced the later recovery. The court dismissed that case at the government’s request.
The Treasury’s FinCEN whistleblower program covers anti-money laundering and sanctions violations. Matching evidence of bank misconduct to the right whistleblower program is part of the work we do with you.
A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.
For a payments employee, the important comparison may be between the original instruction and the message sent to the next bank. For someone responsible for customer accounts, it may be between what the bank knew about the business and the explanation given to its U.S. correspondent. For a monitoring specialist, it may be the rulebook beside the scenario that actually ran.
Those are different views of the same institutional decisions. Original and altered messages can expose removed information. Ownership and customer records can explain who was behind an account. Test results, audit findings, risk overrides and management escalations can connect a control defect to the people who knew about it.
We work with insiders to connect those views: what the payment showed, what the bank knew, and what happened when the discrepancy reached someone who could act. That is where knowledge of an ordinary banking workflow becomes the substance of a whistleblower case.
If you saw payment details removed, customer connections concealed or monitoring rules fail in practice, speak to one of our whistleblower experts about what the payment left out. We work with you to build your strongest sanctions whistleblower case, bring in sanctions and money laundering whistleblower lawyers who understand correspondent banking, and stay beside you through the process.