OFAC sanctions enforcement, 2016 to 2026: what 156 releases say about screening, IP data and penalty size
We counted every OFAC civil penalty, settlement and finding of violation for a decade and coded the technology causes each release itself names.
The question
The Office of Foreign Assets Control (OFAC) publishes every civil penalty, settlement and finding of violation it concludes as a short enforcement release, and lists them by year with the amount each one states [1]. Read together, those releases are the most detailed public record of how sanctions compliance fails in practice: which firms, how much, and what went wrong in their systems. This report counts the releases dated from January 1, 2016 to November 16, 2026, sizes them, and codes the technology causes each release itself names [1].
Data and method
Dataset: OFAC's Civil Penalties and Enforcement Information page, which carries the 2026 Civil Penalties Information Chart, the yearly enforcement pages for 2016 to 2025 that it links to, and the enforcement release each chart row links to, all read on November 16, 2026 [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]. A short script read the charts; every release was downloaded and its text searched, and each passage used for coding was read in full.
- One case is one enforcement release, the document a chart row links to. OFAC's chart sometimes gives one release two rows (the 2017 Toronto-Dominion Bank and 2018 JPMorgan Chase releases each carry a settlement and a finding of violation) and its "Aggregate Number" column sometimes counts one release as two or three, so the chart's own count for the period is 165 against our 156 releases [1].
- Year: the date OFAC gives the release in its chart, which is the release date printed on the document [1].
- Amount: the figure in OFAC's chart, summed across a release's rows. Our yearly sums match the "Year to date totals" OFAC prints for every year [1]. Where a release says part or all of the amount is deemed satisfied by a payment to another agency, or suspended, we still record the amount OFAC states and note the credit separately.
- Type: a settlement where the release says the party agreed to settle; a penalty where OFAC says it issued a Penalty Notice or assessed a penalty; a finding of violation where OFAC issued one without money [1].
- Financial firm: a release whose own description of the party is a bank, card issuer, finance company, insurer, broker-dealer, exchange operator, money services or payments business, virtual currency business, or investment firm [1].
- Technology cause: coded only from what the release says caused the apparent violations or what OFAC lists as aggravating factors. Remedial steps alone do not count (a release that says a firm later added IP blocking is not an IP case unless it says the missing control contributed). Conduct the release describes as deliberate, such as stripping payment messages or staff evading screening, is not coded as a technology cause, though a release can carry both [1].
OFAC's own appendix of root causes, drawn from earlier enforcement actions, includes "Sanctions Screening Software or Filter Faults": failing to update software for list changes, leaving out identifiers such as SWIFT Business Identifier Codes, and not accounting for alternative spellings [12]. Our categories follow the releases' own words and sit close to that list.
A steady count and a lumpy total
| Year | Releases (our count) | OFAC's aggregate count | Total OFAC states (USD) | Largest single amount (USD) | Releases about financial firms | Releases naming a technology cause |
|---|---|---|---|---|---|---|
| 2016 | 9 [2] | 9 [2] | 21,609,315 [2] | 7,617,150 [2] | 1 [2] | 2 [2] |
| 2017 | 16 [3] | 17 [3] | 119,527,845 [3] | 100,871,266 [3] | 4 [3] | 3 [3] |
| 2018 | 7 [4] | 8 [4] | 71,510,561 [4] | 53,966,916 [4] | 2 [4] | 2 [4] |
| 2019 | 22 [5] | 26 [5] | 1,289,027,059 [5] | 657,040,033 [5] | 7 [5] | 4 [5] |
| 2020 | 15 [6] | 16 [6] | 23,565,657 [6] | 7,829,640 [6] | 3 [6] | 5 [6] |
| 2021 | 19 [7] | 20 [7] | 20,896,739.22 [7] | 8,572,500 [7] | 8 [7] | 7 [7] |
| 2022 | 16 [8] | 16 [8] | 42,664,006.65 [8] | 24,280,829.20 [8] | 9 [8] | 10 [8] |
| 2023 | 16 [9] | 17 [9] | 1,541,380,594.08 [9] | 968,618,825 [9] | 10 [9] | 11 [9] |
| 2024 | 12 [10] | 12 [10] | 48,790,404 [10] | 20,000,000 [10] | 3 [10] | 5 [10] |
| 2025 | 14 [11] | 14 [11] | 265,746,819 [11] | 215,988,868 [11] | 5 [11] | 6 [11] |
| 2026 (to November 16) | 10 [1] | 10 [1] | 297,513,285 [1] | 275,000,000 [1] | 2 [1] | 5 [1] |
Releases ran between 7 and 22 a year, and 10 had been published in 2026 by November 16 [1]. The money does not track the count. Across the 156 releases OFAC states $3,742,232,284.95 in amounts, but four releases account for $2,745,294,771 of it, or 73%: Binance ($968,618,825, 2023), Standard Chartered Bank ($657,040,033, 2019), UniCredit Bank ($611,023,421, 2019) and British American Tobacco p.l.c. ($508,612,492, 2023) [1]. Each of those four releases says part or all of its amount was deemed satisfied by payments to other US authorities for the same conduct [1] [24].
The typical case is far smaller. Of the 153 releases with an amount, 84 (55%) are under $1 million, and the median is $750,000 [1]. The median moved up, from $515,400 in 2016 to 2020 to about $1.06 million in 2021 to 2026, and releases of $10 million or more went from 5 to 11 between those halves [1]. Single cases still decide the yearly totals: GVA Capital Ltd.'s $215,988,868 penalty is 81% of 2025's total and Adani Enterprises Limited's $275,000,000 settlement is 92% of 2026's so far [1] [11] [28].
Moraph's view
Moraph's view: the yearly total is the wrong measure of enforcement pressure. It swings more than seventyfold across the decade on the strength of one or two global settlements. The count and the median are steadier, and both point the same way: a few more releases with mid-sized amounts, not a collapse or a surge.
Financial firms: a third of the releases, most of the money
54 of the 156 releases concern financial firms by our definition, and they account for $2,660,375,406, or 71% of the dollars [1]. Their share of releases rose from 17 of 69 (25%) in 2016 to 2020 to 37 of 87 (43%) from 2021 [1]. The rise came with new kinds of firm: the first release about a digital asset business is BitGo, Inc. on December 30, 2020 [16], and by November 2026 releases had named virtual currency exchanges, wallet providers, a digital currency payment processor, brokers and investment firms alongside banks and insurers [1]. 2026 so far has 2, Bank of America, N.A. and TradeStation Securities, Inc. [1].
What the releases say went wrong in the systems
| Cause, as the release describes it | 2016 to 2020 | 2021 to November 16, 2026 | All releases | Of which about financial firms |
|---|---|---|---|---|
| Screening gap: screening absent for the party, location or data at issue, set up so it missed the match, out of date, or an alert closed or not acted on | 14 [1] | 33 [1] | 47 [1] | 30 [1] |
| IP address or geolocation: IP or other location data pointed to a sanctioned place and was not collected, not used, or applied with gaps | 1 [1] | 13 [1] | 14 [1] | 12 [1] |
| Customer or payment data: fields missing, inaccurate, in free text or a script the screening did not read, or not loaded into the system that screened | 2 [1] | 7 [1] | 9 [1] | 7 [1] |
| Other system defect: a platform, integration or technical defect the release names as a cause | 1 [1] | 3 [1] | 4 [1] | 2 [1] |
| Any of the four | 16 [1] | 44 [1] | 60 [1] | 39 [1] |
60 of the 156 releases (38%) name at least one technology cause, and the share rose from 16 of 69 (23%) in 2016 to 2020 to 44 of 87 (51%) since 2021 [1]. For financial firms it is 39 of 54 (72%), and 32 of the 37 financial-firm releases since 2021 (86%) [1]. Of the 96 releases that name none, 81 concern firms or people outside financial services [1].
Screening gaps come in a few repeated forms. Deutsche Bank Trust Company Americas let 61 payments through because the designated bank's SWIFT code was not in its screening tool and the tool was set to escalate only exact matches [18]. Amazon.com, Inc.'s automated screening did not flag orders addressed to "Yalta, Krimea" [17]. Payoneer Inc.'s release lists weak matching algorithms, no screening of SWIFT codes and automatic release of held payments during backlogs [19]. Bank of America, N.A.'s 2026 release cites payments routed through blocked banks by an automated process that drew on a vendor's routing directory, slow watchlist updates and alerts on exact name and date-of-birth matches that were not prioritized [27].
Data causes are fewer but specific. Uphold HQ Inc. did not screen the free-text address field where some customers wrote a sanctioned country [22], and other releases describe ownership data never loaded into the screening system, country fields that disagreed with addresses, and names held in Cyrillic or Chinese script that screening did not read [1].
IP addresses: from no cases to a recurring finding
No release before December 2020 names IP address or geolocation data as a cause; 14 have since, 12 of them about financial firms, in every year from 2020 to 2026 except 2024 [1]. The first, BitGo, said the firm had reason to know users were in sanctioned places from the IP addresses of the devices they logged in from, but had no controls to act on it [16]. OFAC's sanctions guidance for the virtual currency industry describes the same pattern as a case study: a company that tracked users' IP addresses for security but did not use them to screen [13].
The later releases describe the same gap in different systems. SAP SE's release says internal audits in 2006, 2007, 2010 and 2014 found the company did not screen customers' IP addresses [20]. Bittrex, Inc. collected IP and physical address data at onboarding but had no controls to screen customers or transactions for a sanctioned-country link until October 2017 [21]. Swedbank Latvia collected and stored customer IP data but did not feed it into screening; OFAC says the data would have shown the client was in Crimea [23]. Interactive Brokers LLC's geo-blocking had a technical bug, left Crimea off its IP blocking list before May 2019 and left out Sevastopol addresses until June 2021 [25]. TradeStation Securities, Inc.'s first-tier geo-blocking stayed off after an employee failed to switch it back on, on June 21, 2021, after disabling it to install a software update, and a lapsed alert subscription went unnoticed for over eight months [26].
Moraph's view
Moraph's view: the IP cases are mostly operations failures, not missing technology. In most of them the firm already held the location data for fraud, security or login purposes and did not route it to sanctions controls, or the control existed and stopped working without anyone noticing. The testable questions for any platform are whether location signals reach the sanctions engine, whether the blocking list covers regions as well as countries, and who notices when a control or feed goes silent.
Settlements, penalties and credits
147 of the 156 releases announce settlements, two of them alongside a finding of violation; 6 announce penalties OFAC imposed, and 3 are findings of violation with no money [1]. Three of the six imposed penalties came in 2025, including GVA Capital Ltd.'s, which also covers failure to comply with an OFAC subpoena [1] [28]. 11 releases say part or all of the amount was deemed satisfied by payment to another authority, and 3 more say it is satisfied or credited in part by payments to the Commerce Department's Bureau of Industry and Security; in Binance's case $898,618,825 of $968,618,825 was deemed satisfied by its payment to the Department of Justice, and its release also refers to settlements with FinCEN and the Commodity Futures Trading Commission [1] [24]. Bittrex's release likewise points to FinCEN's parallel settlement [21]. FinCEN's own Bank Secrecy Act actions, including its orders against Bittrex and Binance, are outside this count; our FinCEN enforcement trend report covers them.
Rules that change the next count
Two changes affect what the record will show. On April 24, 2024 the statute of limitations for civil violations of IEEPA and the Trading with the Enemy Act went from five years to 10, and OFAC's guidance says it can now act on violations whose latest date was after April 24, 2019 [14]. On September 25, 2026 OFAC's new Sanctions Penalties Regulations, 31 CFR part 505, took effect, consolidating penalty provisions from individual program rules with no substantive change [15].
Moraph's view
Moraph's view: the longer limitations period matters most for the technology causes above. A gap in IP handling or alert disposition from 2020 can still surface in a release in 2028, so the evidence that a control worked, such as logs, list versions and alert decisions, needs to outlive the old five-year habit.
Limits of this count
The coding reads what OFAC chose to write; a release that is silent on causes is coded as having none, so the technology counts are a floor. The financial-firm label rests on how each release describes the party. Amounts are as OFAC states them, before credits and suspensions, and this report did not trace later litigation, payment or collection. Percentages are rounded to the nearest whole number.
What this means for you
- Banks: Test the failure modes OFAC keeps naming: SWIFT codes and other identifiers in the screening list, matching that catches near spellings, same-day list updates, and how alerts on strong matches are prioritized and closed [18] [19] [27]. OFAC's root-cause appendix lists the same faults [12].
- Brokers, payment firms and virtual currency platforms: Check that IP and other location data already collected for security or fraud reaches sanctions controls, that blocking lists cover regions such as Crimea and its cities, and that someone is alerted when a geo-blocking control or list feed stops [16] [23] [25] [26].
- Compliance technology and data owners: Screen free-text address fields, identity documents and non-Latin scripts, and load ownership data into the system that screens; releases since 2021 cite each of these gaps [1] [22]. Keep evidence of control operation for the 10-year limitations period [14].
- Insurers and investment firms: Read the releases about insurers, private equity and venture capital firms alongside bank cases; the largest imposed penalty in the decade, $215,988,868, was on a venture capital firm [1] [28].
Moraph predictions
Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.
P1 By Confidence 75% Open
OFAC's chart for calendar 2027 shows an aggregate count of at least 10 penalties, settlements or findings of violation.
How we will check: On or after January 31, 2028, read the 'Year to date totals' row of OFAC's 2027 Civil Penalties Information Chart (on the Civil Penalties and Enforcement Information page, or the 2027 Enforcement Information page once archived). Right if the aggregate number is 10 or more.
Basis: OFAC's aggregate count reached 10 or more in 9 of the 11 years from 2016 to 2026, ranging from 8 to 26, and stood at 10 on November 16, 2026 [1] [2] [4] [5].
P2 By Confidence 75% Open
The total OFAC states for calendar 2027 is below $500 million.
How we will check: On or after January 31, 2028, read the 'Year to date totals' dollar figure on OFAC's 2027 chart. Right if it is below $500,000,000.
Basis: Yearly totals exceeded $500 million only in 2019 ($1,289,027,059) and 2023 ($1,541,380,594.08), both driven by global settlements [5] [9]; 2026 stood at $297,513,285 on November 16 [1].
P3 By Confidence 65% Open
At least one OFAC enforcement release dated in 2027 names IP address or geolocation data as a cause of the apparent violations.
How we will check: An OFAC enforcement release dated January 1 to December 31, 2027 says that IP address or other geolocation data was not collected, not used, or applied with gaps (for example a missing region in an IP blocking list) and that this contributed to the apparent violations. Remedial-step mentions alone do not count.
Basis: Releases naming IP or geolocation causes appear in every year from 2020 to 2026 except 2024, 14 in all [1], most recently TradeStation in March 2026 [26]; OFAC's virtual currency guidance treats unused IP data as a case study [13].
P4 By Confidence 60% Open
At least 3 OFAC enforcement releases dated in 2027 concern financial firms.
How we will check: Apply this report's definition: count 2027 releases whose own description of the party is a bank, card issuer, finance company, insurer, broker-dealer, exchange operator, money services or payments business, virtual currency business or investment firm. Right if 3 or more.
Basis: Financial-firm releases numbered 3 or more in 8 of the 11 years from 2016 to 2026 and 8 to 10 a year from 2021 to 2023, but 2 in 2026 up to November 16 [1].
Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.
Spotted an error? Tell us and we will check it and correct the piece where needed.