Decision IntelDeutsche Bank
Deutsche Bank Mirror Trading Scandal
Estimated impact: $630M
Deutsche Bank's Moscow branch facilitated $10 billion in mirror trades that moved money out of Russia between 2011 and 2015. Compliance failures and a culture of status quo acceptance allowed suspicious transactions to continue despite red flags, resulting in $630 million in regulatory fines.
Decision context
Whether to investigate and halt suspicious mirror trading patterns between the Moscow and London offices that compliance teams had flagged multiple times.
What the record already said
The document below predates the decision. Everything after it is read from that document alone, so a reader can check each line against the words above it rather than take the reading on trust.
Deutsche Bank Moscow equity desk from 2011 onward executed a pattern of same-day matched trades: the Moscow office bought Russian equities from clients for rubles while the London office sold the same securities for dollars or euros to related counterparties. Internal compliance teams flagged the pattern as 'economically meaningless from a trading perspective' multiple times between 2012 and 2014. Trade volume reached approximately $10B. Moscow head of equities Tim Wiswell's personal relationships with client counterparties were documented in internal communications that went unaddressed.
Source: FCA Final Notice to Deutsche Bank AG (2017); NY DFS Consent Order (2017) ¶¶ 21-45
What a reader could have found without knowing the ending
- Compliance team described the mirror-trade pattern as 'economically meaningless' in writing — yet trades continued
- Revenue from the trades was material to Moscow equity desk P&L — creating escalation disincentive
- Sanctioned clients appeared in trade counterparty chains
- Head of equities Moscow (Wiswell) had personal relationships with counterparty firms, flagged but not reviewed
- No jurisdictional KYC review correlated Moscow-client identities with London-counterparty identities
DI would flag Deutsche Bank's mirror-trading case as the canonical 'revenue-generating activity evades compliance scrutiny' failure. When a compliance team calls transactions 'economically meaningless' and they continue, a decision process with working circuit-breakers would have required either a documented business-purpose explanation or a halt. The organizational status quo — 'this desk makes money, other desks don't, let the experts manage it' — is the bias. A bias-adjusted AML review would have required cross-jurisdiction identity matching as a mandatory bright-line check that would have surfaced the pattern in months, not years.
Written after the outcome was known. Nothing here can be falsified, which is why it sits below the document rather than above it.
Decision anatomy
Red = risk factor present · Green = protective factor present
Biases present in the decision
★ Primary driver · Severity estimated from bias type and decision outcome
Toxic combinations
The curated library this case sits in
Across all 155 curated case studies in our library, by documented outcome:
The library is curated toward documented failures, so this split describes the library, not the base rate of deals. The case above is one row in it.
Lessons learned
- Status quo bias in compliance means that revenue-generating activities receive less scrutiny than they warrant.
- Cognitive misering in AML processes leads teams to check boxes rather than critically analyze transaction patterns.
- Decentralized operations across jurisdictions create oversight gaps that enable illicit activity to persist.
Source: FCA Final Notice to Deutsche Bank AG (2017); NY DFS Consent Order (2017) (FCA Enforcement)
These patterns were flaggable in Deutsche Bank's own record — before the outcome.
See the full hindsight-stripped audit we ran — no login, no card. Then run the same audit on a deal you have already closed.
Or leave your email, we'll run the audit on a deal of your choosing and send the readout within a business day.
Workflows that fire on decisions like Deutsche Bank’s
The same Recognition-Rigor Framework that documents this case audits memos in the same shape — before the outcome forces the lesson.