DEV Community

Cover image for Building a Sanctions List Screening Workflow: From Name Matches to Auditable Review
EveryInfra for EveryInfra

Posted on Originally published at everyinfra.com

Building a Sanctions List Screening Workflow: From Name Matches to Auditable Review

The OFAC SDN list dated November 19, 2026 has 19,595 entries. We scored all 44,489 Latin-script names and aliases on it with a fuzzy matcher. At a score of 0.95, six common personal names recalled 6 candidates. At 0.85, the same six names recalled 240 candidates. We needed 0.85 to recall all six spelling variants of real listed parties (OFAC Sanctions List Service).

In the same 30 days, from October 21 to November 19, 2026, OFAC changed the SDN list on 9 days. It added 142 entries, removed 8 and changed 10. On November 4, 2026 it also added one note on secondary sanctions risk to 2,158 existing entries (OFAC Recent Actions). A screening product delivers a decision record that you can replay step by step. The record shows which list version was used, which candidates came back, and who decided on which fields.

This piece covers data methods and engineering limits only. It is not legal or compliance advice, and EveryInfra does not sell a sanctions screening service.

Key points

  • The OFAC SDN list has 19,595 entries: 10,122 entities, 7,561 individuals, 1,570 vessels and 342 aircraft; 99.1% of individuals have a date of birth, but only 57.9% have an ID document.
  • Our Jaro-Winkler test scored 44,489 names. At 0.95, six common names gave 6 candidates and 1 of 6 variants; at 0.85, they gave 240 candidates and 6 of 6 variants.
  • Three common names, Ali Hassan, Kim Chol and Sergei Ivanov, have an exact namesake on the SDN list with a score of 1.0. A name alone cannot separate them; a date of birth or an ID number can.
  • "Victor But" was recalled only through "BUTT", an alias that OFAC marks as low quality. The SDN list has 4,444 such names.
  • OFAC changed the SDN list on 9 of 30 days. A whole-record diff would re-screen 2,158 entries after the November 4, 2026 bulk note.
  • Eight live EveryInfra calls cost $0.006697: none of 36 news results linked to an official notice, but 8 of 10 web search results were official pages.
  • We got the list counts, the matching test and the 30-day changes from scripts on the raw list files. The enforcement details, the 50% rule and the weak alias rules come from OFAC releases and FAQs.

Isometric illustration: a screening machine on the left sifts a stack of grey name cards; most cards fall into a grey bin below, and a few slide onto a review desk on the right, where a magnifier rests on one teal-edged card next to a tabbed ledger and a padlock; a flipping wall calendar and a cabinet of numbered drawers stand in the background.

The shape of screening: many names go in, a few candidates stay for human review, and the result goes into a versioned record. EveryInfra generated illustration, no real data

Start with the list itself: 19,595 entries and four kinds of record

OFAC publishes the SDN list and the non-SDN consolidated list through the Sanctions List Service. The formats include CSV, fixed-width text, XML and an enhanced XML file with more structure. We downloaded SDN_ENHANCED.XML at 00:16 Singapore time on November 20, 2026. The file header gives a data date of November 19, 2026, US Eastern time.

Our parser counted 19,595 SDN entries. There are 10,122 entities, 7,561 individuals, 1,570 vessels and 342 aircraft. Each kind of record carries different identifiers. Of the individuals, 7,490 have a date of birth, which is 99.1%.

Another 5,726 have a nationality (75.7%), and 4,851 have a place of birth. Only 4,376 individuals have at least one ID document, such as a passport, national ID or tax number. That is 57.9%.

Vessels and aircraft are easier to pin down. Of 1,570 vessels, 1,569 have a vessel registration number such as an IMO number, and 840 also have an MMSI. All 342 aircraft have a model, and 292 have a manufacturer serial number. For entities, the most common strong identifiers are registration numbers (4,538) and tax numbers (4,412). In addition, 220 entities have a SWIFT/BIC code and 1,165 have a website.

Horizontal bar chart of the OFAC SDN list with 19,595 entries: 10,122 entities (45.2% with no alias), 7,561 individuals (43.0% with no alias), 1,570 vessels (88.9% with no alias) and 342 aircraft (99.4% with no alias). The individual bar is highlighted; 3,255 individuals have no alias.

Aliases are not spread evenly either. Of the individual entries, 3,255 have no alias at all. The median is 1 alias, the 90th percentile is 4, and the maximum is 46. There are 571 individuals with 5 or more aliases. One entity has 95 aliases.

Names also come in many scripts. The enhanced XML has 3,672 Cyrillic names, 1,504 Arabic names, 378 Simplified Chinese names and 183 Traditional Chinese names. In total, 4,885 entries have at least one name in a non-Latin script. A matcher that reads only Latin script cannot use the original spellings on these 4,885 entries.

Record type Entries Most common strong identifier Entries with it Share with no alias
Individual 7,561 Date of birth, ID document DOB 7,490; ID 4,376 43.0%
Entity 10,122 Registration number, tax number Any ID-type field 8,106 45.2%
Vessel 1,570 IMO number, MMSI 1,569 88.9%
Aircraft 342 Model, serial number, tail number Model 342; serial 292 99.4%

A single screening API can share one outer shape, and the match rules inside can split by record type. If you push a vessel into name + country, the IMO number stops working. If you push a company into the person model, the registration number has nowhere to go.

The list also holds relationships. The enhanced XML has 9,304 relationship records. Of these, 4,058 are "Owned or Controlled By", 1,882 are "Providing support to", 1,567 are "Acting for or on behalf of" and 1,094 are "Property in the interest of". These links only join records that are already on the list. A subsidiary that is not listed does not appear here. This limit matters again in the section on ownership.

You can also measure how old the list is. Each record carries a publication date for its list membership. We took the earliest date for each record and counted by year. The current list holds 2,393 entries first published in 2022, 2,602 from 2023, 3,264 from 2024 and 2,168 from 2025.

So far in 2026, up to November 19, there are 1,561. Together, 11,988 entries date from 2022 or later. That is 61.2% of the 19,595 entries on today's list.

This has a direct effect on customer files. Suppose a customer base was screened once in 2021 and never again. Those customers were checked against less than 40% of the entries that are on the list today. So ongoing monitoring also records, for each stored customer, the list version of the last check.

New field types also appear over time. Among individuals, 46 entries carry a Bitcoin address, 31 an Ethereum address, 26 a Tron address and 11 a USDT address. Entities carry a similar set, with 19 Tron, 19 Bitcoin and 17 Ethereum addresses. These fields need exact matching, character by character.

Fuzzy matching on a wallet address recalls addresses that differ by one character. So one workflow holds two kinds of match. Names go through fuzzy recall and human review. Addresses, ID numbers and IMO numbers go through exact match. A product can put an exact hit at the top of the queue.

The official list is the source, not the decision

The collection layer keeps the source list, the record ID, the publication time, the download time, a file hash and the parser version. The enhanced XML makes this concrete. Each record has a stable entity id. Each list membership has a datePublished. The whole file has a dataAsOf value.

Other publishers use different version fields. The UN Security Council consolidated list XML has a dateGenerated attribute at the root. Each record has a DATAID, a VERSIONNUM and a LAST_DAY_UPDATED field. The UK Sanctions List page lists every change by date. For example, the entry for November 17, 2026 reports 9 new designations, 1 correction and 1 variation. With these fields, you can later answer one key question: which list version did a given screening run use?

Field coverage also differs by publisher. We ran the same counting script on the UN consolidated list, generated on November 19, 2026. It has 733 individuals and 274 entities. Of the UN individuals, 680 have a date of birth (92.8%) and 631 have a nationality (86.1%).

Only 296 have an ID document (40.4%), and 565 have at least one alias (77.1%). Compared with OFAC, the UN list has better nationality and alias coverage. It has weaker coverage for dates of birth and ID documents.

Grouped horizontal bar chart of the share of individual entries with each field. Date of birth: OFAC 99.1%, UN 92.8%. Nationality: OFAC 75.7%, UN 86.1%. ID document: OFAC 57.9%, UN 40.4%. At least one alias: OFAC 57.0%, UN 77.1%.

A missing field means different things on different lists. On the UN list, 40.4% of individuals have an ID document. For the other six in ten, an analyst can only compare name, date of birth and nationality. On the OFAC list, 43.0% of individuals have no alias.

If one of these persons uses a different spelling, only the fuzzy matcher can recall the record. The review screen can state when the list record itself has no ID number. Then the analyst does not think that the customer file is incomplete.

List How it is published Version fields Record key Our count
OFAC SDN Sanctions List Service exports (CSV, XML, enhanced XML) dataAsOf, datePublished per record entity id 19,595 entries
UN Security Council consolidated list XML and HTML in several official languages dateGenerated, VERSIONNUM, LAST_DAY_UPDATED DATAID, reference number 733 individuals, 274 entities
UK Sanctions List Web page, download files, dated change notes Date and text of each change Unique ID Changes on 8 days in 30
EU consolidated list EU Sanctions Map and financial sanctions files Legal act number and date EU reference 113 new listings on November 16, 2026

The UK data source changed in 2026: the OFSI Consolidated List of Asset Freeze Targets stopped updates on January 28, 2026.

Since then, the UK Sanctions List is the only source for all UK designations, and it logs each change by date on one page. We counted the entries after October 21, 2026. There are 12 change notes on 8 days. They add 35 designations and 9 new specifications, and they record 10 variations, 3 corrections, 5 amendments and 3 delistings. A job that still reads the closed OFSI list gets none of the updates after January 28, 2026.

A similarity score only recalls candidates: our own matching test

OFAC FAQ 246 says that its own Sanctions List Search tool applies fuzzy logic to the name field only. Other fields use character matching. FAQ 247 says the score combines a phonetic algorithm and a character similarity algorithm, and that the default of 100 means an exact match. So a name score is a recall signal. It is not a risk probability across fields.

We wanted to see what each step of the threshold does. At 00:18 Singapore time on November 20, 2026, we fixed a test list before we ran any scores. The list has three groups. Group one has six common personal names: Mohammad Ali, Ali Hassan, Kim Chol, Sergei Ivanov, Jose Garcia and Wang Wei. They stand for ordinary customers who have these names.

Group two has six spelling variants of real listed parties. For example, the list record "BOUT, Viktor Anatolijevitch" becomes "Viktor Anatolyevich Bout" and "Victor But". The record "HIZBALLAH" becomes "Hezbollah". Group three has two made-up company names.

We wrote our own Jaro-Winkler scorer. The formula comes from William Winkler's 1990 Census Bureau paper (ERIC record), with a method overview in Winkler 1993. We used a prefix cap of 4 and a prefix weight of 0.1. Each name goes through Unicode decomposition, accent removal, upper case and punctuation removal. The scorer then takes the higher of two scores: the names in their given order, and the names with tokens sorted. Each SDN record gets the best score over all its Latin-script names.

import re, unicodedata

def norm(x: str) -> str:
    x = unicodedata.normalize("NFKD", x)
    x = "".join(c for c in x if not unicodedata.combining(c))
    x = re.sub(r"[^A-Za-z0-9 ]", " ", x.upper())
    return " ".join(x.split())

def score(q: str, name: str) -> float:
    a, b = norm(q), norm(name)
    return max(jaro_winkler(a, b),
               jaro_winkler(" ".join(sorted(a.split())), " ".join(sorted(b.split()))))

# For each SDN record, keep the best score over all Latin-script names (primary + aliases)
Enter fullscreen mode Exit fullscreen mode

Here are the results. At 0.95, the six common names recalled 6 records in total, and we recalled only 1 of 6 variants ("Sberbank Russia", score 0.967). At 0.90, the common names recalled 49 records, and we recalled 4 variants. At 0.85, they recalled 240 records, and we recalled all 6 variants. At 0.80, they recalled 716 records. On this list and with this algorithm, a zero-miss result on the six variants costs 240 review candidates from six common names.

The common names gave one more result. "Ali Hassan" scored 1.0 against SDN entries 6924 and 12113. "Kim Chol" scored 1.0 against entry 23483. "Sergei Ivanov" scored 1.0 against entry 16688, listed as "IVANOV, Sergei". "Mohammad Ali" scored 0.967 against two "MOHAMMED ALI" names (entries 19930 and 21387). So an ordinary customer named Ali Hassan has the same name as two listed persons.

A threshold of 1.0 cannot remove these candidates. Only the date of birth, nationality and ID number can separate them.

The four 1.0 scores come from different name types. "KIM, Chol" is the primary name of entry 23483. Entry 16688 has the primary name "IVANOV, Sergei Borisovich", and "IVANOV, Sergei" is a normal alias in ALT.CSV. Entry 6924 has the primary name "FADHIL, Mustafa Mohamed", and "ALI, Hassan" is one of its 9 aliases. Entry 12113 has the primary name "MORTEZAVI, Hasan", and "ALI, Hassan" is a weak alias in the remarks field of SDN.CSV.

All four entries have a date of birth: 1976-06-23, 1964-08-23, 1964-09-27 and 1953-01-31. Entries 6924 and 12113 also have an ID number. Entries 23483 and 16688 have no ID number, so the date of birth in the customer file is the only field that can dismiss them.

Column chart of SDN records recalled by six common names at each threshold: 6 at 0.95, 49 at 0.90, 240 at 0.85 and 716 at 0.80. Labels under the columns show spelling variants recalled: 1 of 6, 4 of 6, 6 of 6 and 6 of 6. The 0.85 column is highlighted.

"Yevgeny Prigozhin" scored only 0.896 against "PRIGOZHIN, Yevgeniy Viktorovich", because the list version adds a patronymic.

The best score for "Victor But" was 0.86, and it came from "BUTT". OFAC marks that alias as low quality in the enhanced XML. The full form "Viktor Anatolyevich Bout" scored 0.903 against the primary name. "Hezbollah" scored exactly 0.900 against "LEBANESE HEZBOLLAH". A rule of "0.90 or more" recalls it, but a rule of "more than 0.90" misses it. A threshold of 0.90 misses Prigozhin and "Victor But".

Query name Group 0.95 0.90 0.85 0.80 Note
Mohammad Ali Common 2 23 95 271 0.967 against two MOHAMMED ALI names; 94 are individuals at 0.85
Ali Hassan Common 2 7 74 245 Exact namesake on the list (6924, 12113; 1.0)
Kim Chol Common 1 16 41 96 Exact namesake on the list (23483; 1.0)
Sergei Ivanov Common 1 3 14 54 Exact namesake on the list (16688; 1.0)
Jose Garcia Common 0 0 5 22 Best 0.896
Wang Wei Common 0 0 11 28 Best 0.892
Viktor Anatolyevich Bout Variant Miss Hit Hit Hit 0.903 against the primary name
Victor But Variant Miss Miss Hit Hit Through weak alias "BUTT", 0.86
Yevgeny Prigozhin Variant Miss Miss Hit Hit 0.896
Joaquin Guzman Variant Miss Hit Hit Hit 0.94
Hezbollah Variant Miss Hit Hit Hit Exactly 0.900; a "> 0.90" rule misses it
Sberbank Russia Variant Hit Hit Hit Hit 0.967; the only variant hit at 0.95
Northwind Trading LLC Made-up company 0 0 4 58
Blue Harbor Shipping Co Made-up company 0 0 2 13

Horizontal bar chart of SDN records recalled per query at threshold 0.85: Mohammad Ali 95, Ali Hassan 74, Kim Chol 41, Sergei Ivanov 14, Jose Garcia 5, Wang Wei 11, Northwind Trading LLC 4 and Blue Harbor Shipping Co 2. The queries stand for ordinary customers. The bars for Ali Hassan, Kim Chol and Sergei Ivanov are highlighted and starred: each has an SDN entry with the same name at a score of 1.0, so a name alone cannot separate them.

Another number shows how little a type filter does. At 0.85, the six common personal names recalled 240 records, and 232 of them were already individual records. A type filter removes only 8 records, which is 3%.

Date of birth, nationality and ID numbers are what cut the 240 down. For a query with an exact namesake on the list, such as Ali Hassan, these fields are the only way to separate the candidates. A thread in r/fintech from October 28, 2026 gives the same advice. One reply says to require a date of birth or nationality before the check, so the system can drop clear mismatches.

The test has limits. It has 14 queries only. The scorer is our own Jaro-Winkler, with no phonetic step and no matching on non-Latin scripts. Commercial screening tools and the OFAC search tool give different scores, so our numbers are not a production rule.

The test shows a direction. Each 0.05 drop in the threshold multiplied candidates by about 3 to 8 in our sample. The factors were 8.2 from 0.95 to 0.90, 4.9 from 0.90 to 0.85 and 3.0 from 0.85 to 0.80. Variant recall moved at the same time. Read the two curves together.

Weak aliases: where recall comes from, and where noise comes from

OFAC explains weak aliases in FAQ 122. A weak alias is a broad or generic alias that can cause many false hits in automated screening. OFAC flags candidates by length, digits, nicknames, place references and very common prefixes. Its experts then review each flag. In the enhanced XML, these names carry isLowQuality=true. The SDN list has 4,444 of them: 2,282 on individuals, 2,091 on entities and 71 on vessels.

The "Victor But" case shows that weak aliases do real recall work. The Bout record has 5 aliases, and 4 of them are weak: BONT, BOUTOV, BUTT and BUTTE. If you drop all weak aliases, "Victor But" is no longer recalled at 0.85. Weak aliases also pull in unrelated names.

FAQ 125 describes how OFAC views a transaction where a weak alias is the only sanctions reference. One of its conditions is a rigorous, risk-based compliance program. How that text applies to a given firm is a legal question. Check the text yourself or ask a qualified adviser.

Bout record name Type Low quality Best score for "Victor But"
BOUT, Viktor Anatolijevitch Primary name No 0.582
BUTT Alias Yes 0.86 (the recall path)
BUTTE Alias Yes 0.813
BOUTOV Alias Yes 0.740
BONT Alias Yes 0.610
SERGITOV, Vitali Alias No 0.556

The product can do one clear thing. It can flag any candidate that came only from a weak alias, and it can say so on the review screen. A person with the right authority then handles the case under the firm's own policy. The UN list carries a similar flag.

Each alias has a QUALITY field with the value "Good" or "Low". We counted 1,530 good aliases and 620 low aliases on UN individuals. A screening system can use the OFAC isLowQuality field and the UN QUALITY field to tag each candidate.

Four result states, and how long "we cleared this before" lasts

Screening results need at least four states: needs review, can dismiss, escalate, and no usable result. An enforcement release from October 2026 shows the opposite case. On October 13, 2026, OFAC announced an $11,662,930 settlement with Bank of America. The enforcement release lists four problems, and two of them sit inside state design.

The first problem was an alert suppression rule. If a new alert used the same criteria as an alert that an analyst had closed as a false positive, the system suppressed it. The release says that some payments involving blocked banks were released automatically for this reason. The second problem was a flaw in alert priority. Alerts for customers whose name and date of birth both matched a blocked person exactly were ranked low or medium. Three designated individuals then made 31 transactions, worth $56,258 in total, between September 2021 and February 2024.

Put these two points back into the workflow. A past dismissal only shows that the case was clear under that list version and those fields. If the list record gains an alias or an ID number, or the customer moves, the old reason may no longer hold. A product can bind a good match exception to the record ID, the fields used, the list version and an expiry condition.

When an identity field changes on the list record, the exception ends and the case goes back to "needs review". A product can give top priority to a candidate with an exact name and date of birth match. That candidate then stays out of the total score sort and the batch rules.

State When it applies Fields stored When it expires
Needs review A name or alias passes the recall threshold, and other fields cannot separate it Name that recalled it, weak alias flag, score When someone decides
Can dismiss An analyst dismisses it on clear field differences Fields used, list version, analyst, time When an identity field changes on the list or the customer file
Escalate Key fields match, or ownership or location needs a judgment Matching fields, escalation owner When the compliance lead decides
No usable result The query failed, the list is stale, or input is missing Reason, list age When the re-screen finishes

The same release describes a re-screen backlog. In May 2023, an analyst closed an alert in error. The alert was on the beneficial owner of a business, and that person had just been designated. In September 2023, the bank moved to a new screening platform and re-screened all existing customers.

The bank was not ready for the alert volume. It only reached this alert around July 2024, about 14 months after the designation. A full re-screen is a normal part of monitoring. A product can give its alerts their own queue, staffing estimate and deadline. Then they do not bury new alerts.

In the product, "no usable result" is a separate state. A stale list, a timeout and missing input all go there. The screen does not show it as "clear", and the item goes into the re-screen queue.

A thread in r/AMLCompliance shows the opposite case. One reply comes from a person who says that he builds a screening tool. He writes that a source can be unreachable, a batch can fail or a lookup can time out. Many systems then show those rows as "clear", not as "not screened". His test is to force a source outage or a timeout in the middle of a batch. Then you read what the export says for those rows.

Input quality limits screening quality

Suppose an intake form sends only a truncated payee name. No back-end logic can restore the missing identity. The screening API can return input quality flags. Examples are a missing country or an unknown record type.

Other examples are a name cut off by a field limit, a removed company suffix, or an ID number in an unknown format. The business can then collect the missing data. Lowering the threshold again and again does not fix bad input.

Transliteration is also part of input quality. ICAO Doc 9303 Part 3 covers machine-readable travel documents. If the national script is not Latin, the document must also give a Latin transcription or transliteration. The same person can have different Latin spellings on a passport, a bank file and a sanctions list.

The Cyrillic, Arabic and Chinese names on the list help to close that gap. In our test, "Yevgeny" and "Yevgeniy" differ by one letter, and so do "Victor" and "Viktor". That small gap was enough to put a variant on either side of the threshold.

Keep the privacy scope tight as well. A screening check needs some identity fields, but that is no reason to keep customer documents forever. A product can store document images, extracted fields, screening requests and analyst decisions in separate layers. Each layer then gets its own access rights and its own retention period. Our unified data API guide can help you separate source evidence from business actions. It does not replace a legal review for each country and each use case.

A direct list hit and an ownership check are two different jobs

OFAC's FAQs on the 50 Percent Rule cover entities that blocked persons own. If one or more blocked persons own 50% or more of an entity, directly or indirectly and in total, that entity is also blocked. This holds even if the entity is not on the list. FAQ 401 gives five worked examples. In one, person X owns 50% of company A, and A owns 50% of company B, so B is blocked.

In another, X owns 50% of A and 25% of B, and A and B each own 25% of C, so C is not blocked. These examples need ownership data. A name search cannot answer them.

A recent case shows the gap. On October 27, 2026, OFAC announced a $1,529,685 settlement with Extreme Networks. The Russian defense manufacturer in the case was "blocked by operation of law" and majority owned by a designated group. A name search on the manufacturer alone gives no direct hit. Only ownership data links it to the listed parent.

We counted 4,058 "Owned or Controlled By" links in the enhanced XML. They are useful leads, but they only cover links between records that are already listed. A product can split direct list hits and ownership checks into two task types. Ownership checks need company registry data, shareholder records and entity IDs such as the Legal Entity Identifier. A name search has no ownership data, so it cannot give a result for an ownership case.

Question Data it needs Can the list answer it? Task in the product
Direct list hit Name, alias, DOB, ID number, IMO Yes, after recall and field checks Candidate review
Blocked under the 50% rule Direct and indirect ownership shares Only links between listed records Ownership check
Export control affiliate Entity List, ownership shares No Separate export control process
Vessel renamed or reflagged IMO number, past names Yes, by IMO number Re-screen by number

Export controls have a matching rule. In September 2025, the US Bureau of Industry and Security published an affiliates rule. It extends Entity List limits to affiliates that listed parties own by 50% or more. The rule applied for just over a month and was then suspended for one year, to November 9, 2026.

A Federal Register notice of November 9, 2026 extends the suspension to January 10, 2027. Clyde & Co gives a summary. For a data product, the demand for ownership data does not come from OFAC alone. Treat the effective date of each rule as a setting that you track.

Ongoing monitoring: 9 change days in 30, and one bulk note on 2,158 entries

After a list update, the system finds new, changed and removed records. Then it re-screens only the customers that the change can affect. We downloaded all 12 OFAC Recent Actions pages from October 21 to November 19, 2026. On each page, we counted the entries under "added", "deletions" and "changes". Nine of the 12 pages changed the SDN list. The other three were FAQ amendments (October 26, 2026), a settlement (October 27, 2026) and a general license (October 29, 2026).

Timeline bar chart of each day OFAC changed the SDN list between October 21 and November 19, 2026: Oct 21 added 18, removed 8; Oct 28 added 13; Nov 4 added 15, changed 2, plus a bulk note on 2,158 entries (highlighted); Nov 5 added 56, changed 5; Nov 6 added 8; Nov 9 changed 1; Nov 13 added 2, changed 1; Nov 18 added 6; Nov 19 added 24, changed 1.

The added entries total 142. The enhanced XML gives the same count: 142 records have a datePublished inside these 30 days. The two sources check each other. The largest day was November 5, 2026, with 56 new entries, mostly scam networks and linked companies. Removals happened on one day only, October 21, 2026, with 8 entries.

The day that needs the most design is November 4, 2026. OFAC added 15 entries and changed 2. It also added one sentence to 2,158 existing SDN entries: "Secondary sanctions risk: See Section 2 of E.O. 13902". The names, aliases and ID numbers of these entries did not change.

Only a note changed. A monitor that hashes whole records would flag 2,158 changed records that day and re-screen all of them. A monitor that compares fields, and separates identity fields from notes, would re-screen 17 records. For the other 2,158, it only needs to refresh the display.

{
  "entity_id": "example: list record key",
  "list_version": "2026-11-04",
  "changed_fields": ["features.secondary_sanctions_risk"],
  "identity_fields_changed": false,
  "action": "refresh_display_only",
  "rescreen": false
}
Enter fullscreen mode Exit fullscreen mode

The opposite case also happened: the whole name changed, but the number stayed. In the changes on November 5, 2026, a products tanker named CARLOTA C under the Panama flag became MARIA CRISTINA under the Cuba flag. Its IMO number, 9502453, did not change. OFAC also added an MMSI and a build year.

Screenshot of the OFAC action page of November 5, 2026, with a teal box around one change: CARLOTA C, chemical and products tanker, Panama flag, IMO 9502453, changed to MARIA CRISTINA, Cuba flag, built 2010, IMO 9502453, MMSI 323147000, still linked to the same shipping company.

The same ship gets a new name and flag, and the IMO number stays the same. Screenshot of the OFAC action page. OFAC Recent Actions, November 5, 2026 screenshot

The IMO page on ship identification numbers says that the number stays the same when a ship changes flag. IMO also never gives the number to another ship. A name-based monitor sees MARIA CRISTINA as a new name it has never seen. A number-based monitor knows that the same record changed its name.

A Corporate Compliance Insights article of November 16, 2026 cites one count. By April 2026, the EU, the UK and OFAC had designated 1,674 vessels under Russia programs, and only 170 appeared on all three lists. The same ship can carry three different names on three lists. Only the number links them.

The page for November 9, 2026 has one change. An alias of VOLTA SHIPPING SERVICES LLC changed from "VOLTA SHIPPING SERVICES FZCO" to "VOLTA CONTAINER LINE FZCO". The primary name and address did not change, but the alias used for recall did. The new alias can recall customers that the old one missed, so a product can set this kind of change to start a re-screen.

Change type Example in the 30 days Affects identity? Monitor action
New record 142 records on 8 of the 9 change days Yes Re-screen all customers against the new records
Removed record 8 records on October 21, 2026 Yes Open review tasks for a person with authority
Alias change VOLTA, November 9, 2026 Yes Re-screen with the new alias
Rename and reflag, same number IMO 9502453, November 5, 2026 Yes, but the number links it Link by number, then re-screen the new name
Note added 2,158 records on November 4, 2026 No Refresh display only

In the product, a removal only opens a review task. Compliance staff check earlier freezes, rejections or escalations against the rules that apply. A data change only opens a task, and the system gives no legal conclusion.

The UN and UK lists move at a different pace. The UN consolidated list added no records in these 30 days. It updated 10 records: 3 on October 26, 5 on October 29, 1 on November 11 and 1 on November 13, 2026. The last two match a press release on a 1533 Committee alias change and one on a 1718 Committee entry update.

On November 16, 2026, the EU added 12 individuals and 101 entities in one act (Council press release). A product can run monitoring per list, on each list's own version field, and not as one global "once a day" job.

What public data adds: notes from eight live calls

Outside the list, teams usually want two more things. They want to know what just changed on the lists. They also want to know if public reporting holds negative news on a candidate. Public data endpoints can fetch both, but this data is different in kind from a sanctions list. We ran 8 live calls on EveryInfra data endpoints at three times on November 20, 2026: 00:19, 00:23 and 00:30 Singapore time (16:19, 16:23 and 16:30 UTC on November 19). The goal was to see where public data fits in a screening flow.

Singapore time Capability Query Results Official or regulator domains charged_usd
00:19 google_news/search OFAC sanctions designations, past week 7 0 0.000792
00:19 web/search OFAC recent actions sanctions list update November 2026 10 8 0.001389
00:19 reddit/search sanctions screening false positives 3 0 0.000792
00:23 google_news/search UK sanctions list new designations, UK, past week 11 0 0.000792
00:23 duckduckgo/search UN Security Council sanctions committee amends list entry November 2026, past month 10 3 + 2 regulator reposts 0.000556
00:24 reddit/search OFAC screening, newest first 1 0 0.000792
00:30 google_news/search Spanish query on the OFAC list, Mexico, past week 14 0 0.000792
00:30 google_news/search Chinese query on Treasury sanctions, Taiwan, past week 4 0 0.000792

The 8 calls cost $0.006697 in total. Only 2 of the 10 web/search results had a publication date. The 8 official pages came back with no date field.

Stacked bar chart of official-source results per live call. The four google_news/search calls had 0 of 7, 0 of 11, 0 of 14 and 0 of 4; web/search had 8 of 10; duckduckgo/search had 3 of 10 plus 2 regulator reposts; the two reddit/search calls had 0 of 3 and 0 of 1.

First note: news results are good for "what happened", and they are not a list. The four google_news/search calls returned 36 results. None of them linked to ofac.treasury.gov, gov.uk or un.org. The events still match the official action pages.

OFAC's counter narcotics and counter terrorism designations of November 13, 2026 appeared the same day in Just Security and in several Spanish-language outlets. The counter terrorism designations of November 18, 2026 appeared in The Tribune that evening, US Eastern time. But the reports carry no list record numbers, no dates of birth and no ID numbers. They also do not tell you which records got a new alias.

The earliest Spanish result on Guatemala has a time of 18:08 UTC on November 13, 2026, and the Just Security piece came at 21:08 UTC. The OFAC action page gives a date but no time. So the news and the action only share the same day. News can bring a "the list may have changed" alert to your team early. The new version number of the list file is what starts a re-screen.

Screenshot of a real EveryInfra google_news/search response: the request and response at 00:19:05 Singapore time on November 20, 2026, showing 3 of 7 results. Teal boxes mark Just Security at 2026-11-13T21:08:14Z and The Tribune at 2026-11-18T20:52:06Z, with the matching OFAC action dates noted, and the charge of 0.000792 US dollars at the bottom.

News results line up with official action dates, but they carry no list record IDs or identity fields. EveryInfra google_news/search real response screenshot, November 20, 2026

Second note: web search leads to official text more often. Of 10 web/search results for "OFAC recent actions", 8 were pages on ofac.treasury.gov, home.treasury.gov or the OFAC search tool. Of 10 duckduckgo/search results on UN sanctions committee changes, 3 were on press.un.org and main.un.org. Two more were reposts by regulators: the British Virgin Islands Financial Services Commission and the Central Bank of The Bahamas. These results work well as a "the list changed" alert. After the alert, your job still pulls structured data from the official file.

Third note: a different language shows different events. The Spanish query returned 14 results. Seven covered the three Guatemalan trafficking groups designated on November 13, 2026. Five covered a listed Latin American politician who spoke in public about his own legal status. One covered a November 19, 2026 designation of an Italian organized crime group.

The Chinese query returned only 4 results. Their topic was chip transshipment and export controls, and one reported the delay of the affiliates rule. For adverse media checks in several markets, design query terms per language. A straight translation of English terms misses events.

Source type What it answers What it cannot answer Role in the flow
Official list file Who is listed, with which identifiers, in which version Unlisted owned entities Basis of every match
Official action page What changed on which day Field-level detail in a machine format Change alert and cross-check
News search Which events drew coverage, in which language Record IDs, birth dates, ID numbers Early alert and adverse media
Web search Where the official notice sits Freshness, since most official pages carry no date field Route to the official text
Forum search Which problems practitioners raise Any count you can generalize Frame questions and test cases

Fourth note: forums show real pain points, but in small numbers. The reddit/search window is fixed to the last month. "sanctions screening false positives" returned 3 posts. "OFAC screening", sorted by newest, returned 1 post, and that post was about exports of airport security scanners.

It had nothing to do with financial screening. Use forum results to frame questions. Do not use them for statistics.

The cost of this layer is small at catalog prices. Say you run 5 google_news/search calls per day (one or two term sets each in English, Spanish and Chinese) and 2 web/search calls for list change alerts. One day costs 5 × $0.000792 + 2 × $0.001389 = $0.006738. Thirty days cost about $0.20. Failed calls and empty results are not charged. Our failure refund reconciliation guide checks this call by call.

curl -s https://api.everyinfra.com/api/v1/social \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"platform":"google_news","action":"search",
       "params":{"keyword":"OFAC sanctions designations","time_window":"week","language":"en","country":"us"}}'
Enter fullscreen mode Exit fullscreen mode

For details, see the Google News scraper API and its keyword search page. Web search is on the web search API and its search page. Forum search is on the Reddit scraper API and its post search page. DuckDuckGo is on the DuckDuckGo search API and its search page.

The same endpoints also connect to AI tools through our MCP server. The quickstart shows the first call. These endpoints fetch public web pages and news. They do not match names against sanctions lists, and they do not replace the official list files.

Plan for outages before the outage

A failed list download, a parser error, a screening timeout and a case system outage are four different failures. The product shows the current list version and its age. It does not present a stale cache as a fresh check. Keep an idempotency key on each request that can be retried, so a recovery does not open duplicate cases.

Two parts of the Bank of America enforcement release describe failed list updates. From May 24 to June 28, 2023, a human error at a third-party vendor stopped the bank's screening list file from tracking SDN changes. In that window, the bank processed 6 transactions worth $100,828 that involved newly designated entities. It found the problem about a month after another US bank blocked one of the payments.

On February 7, 2025, a technical problem in the bank's own systems stopped the file from loading the prior day's designations. That day, the bank processed 26 transactions for a designated ship management company. The update was only active on February 12, 2025.

In both cases that the release describes, transactions went through while the list was stale, and the bank found out later. A product can make list age a switch that can stop automatic release. The institution sets the age limit per list under its own policy. Past that limit, the product shows "no usable result" until a fresh version loads.

A product can hold the fallback rules as one versioned setting that the institution approves in advance. The setting gives the list age limit, the flows that stop past that limit and the team that works the hold queue. During an outage, the system follows that setting. Engineers then do not decide in the middle of an outage whether real money or real customers go through.

Failure What users see Action you can set in the product After recovery
List download fails Version stays at an old date The institution sets the age limit; the product makes it a switch that stops automatic release Re-screen all records from the gap once the new version loads
Parser error Entry count jumps or drops Roll back to the last good version and alert; partial data is not used Compare entry counts and keys of both versions
Screening timeout No result for a request Return "no usable result" and hold the item Replay with the same idempotency key
Case system down Candidates have nowhere to go Write candidates to a local queue with no loss and no duplicates De-duplicate, then open cases

The OFAC Framework for Compliance Commitments names five parts of a compliance program: management commitment, risk assessment, internal controls, testing and auditing, and training. A screening product can leave evidence for these controls. For each release, it can record the list version and the list age. It can also record who approved the fallback rule and which records got a re-screen after recovery. After an outage, build a re-screen list.

It holds the records and transactions in the gap and the list version used at the time. It also holds any change in the new result and the person who reviewed each change. Our API error and self-healing guide helps with retries and exception queues. People with the right authority still set the real release rules.

Flow chart: list version, normalize, recall candidates, field-by-field check, four states (needs review, can dismiss, escalate, no usable result), review or escalate; every step writes to the audit record. A dashed line shows that a list update re-screens only affected records.

Make the review flow work first; zero false positives is not the goal of version one

The first version can cover one record type, one business entry point and a clear set of official lists. Build a test set from approved historical samples. Track true-hit recall, irrelevant candidates, review time per case, missing input and list update delay as separate numbers. One overall "accuracy" figure hides the different costs of a miss and a false alert.

Our matching test can become a release test. Keep a fixed sample of known variants, common names and made-up names. Re-run it each time you change the threshold or the algorithm, and watch variant recall and candidate count together. In a thread in r/AMLCompliance from October 20, 2026, one reply splits alerts into five groups.

They are false positives, unproductive alerts, good alerts, true positives and false negatives. The same reply notes that a review of past alerts never finds the misses that raised no alert. The "below-threshold testing" in that reply is the job of a fixed sample like ours.

Metric How to measure it Value in our test
Variant recall Known spelling variants of true hits that the matcher recalls 0.95: 1 of 6; 0.90: 4 of 6; 0.85: 6 of 6
Irrelevant candidates Records recalled by a fixed set of common names 0.85: 240
Weak-alias-only recall Candidates recalled only through a weak alias 1 case ("Victor But")
List age Gap between your version date and the publisher's date Our test used the November 19, 2026 version
Review time per case Time from case open to decision Not measured; needs real business data

To validate, pick closed cases at random. Check that a second analyst can rebuild each decision from the same input, list version and stated reason. Also run one list update drill and one outage drill. Confirm that old results are not reused without notice, that no backlog item is lost and that the re-screen runs after recovery. Our articles on SEC filing monitoring, creator due diligence and public tender subscriptions describe data products of the same kind. Each one has a versioned source and decisions that you can replay.

Changes in the last 60 days that affect list data

  • October 13, 2026: OFAC announced the Bank of America settlement of $11,662,930. The release names late list updates, a low priority for exact name and date of birth matches, and automatic alert suppression. The release names list age, priority rules and automatic handling of past dismissals as design problems.
  • October 26, 2026: OFAC amended a set of FAQs on blocking and rejecting transactions and on filing reports. You can check your decision states and report fields against the new text. For how it applies to you, check the text yourself or ask a qualified adviser.
  • October 30, 2026: the FATF October plenary ended. It made scam compound finance a global priority and launched a targeted review on virtual assets. The SDN list already has 46 individuals with a Bitcoin address, and these fields use exact match.
  • November 9, 2026: a Federal Register notice extended the suspension of the affiliates rule to January 10, 2027. If the rule comes back into effect after that date, the need for ownership data extends to export control lists.
  • November 16, 2026: the EU listed 113 more persons and entities, close to 50 of them banks and financial firms (EEAS summary). With 113 new listings on one day, the re-screen of existing customers falls on a single date.
  • November 19, 2026: the European Commission set up an EU Sanctions Office, with effect from January 16, 2027. Its tasks include faster compliance guidance and data sharing. EU publication formats and guidance may change. A product can keep the source address and parser rules in settings that are easy to change.

What this approach does not cover

This approach covers how to turn sanctions list data into a product, and the engineering controls around it. It does not decide if any party is sanctioned. It does not explain legal duties in any country, and it does not say if any transaction is allowed. Qualified legal and compliance staff answer those questions.

Our matching test had 14 queries and used our own Jaro-Winkler scorer. It had no phonetic step and no non-Latin matching, so its numbers only show a direction. The 8 live calls fetched public news, web pages and forum posts. They can tell you that a list changed, and they can add adverse media. They cannot replace the official list files or identity checks.

FAQ

What does sanctions list screening mean?

Screening compares the identity data of customers, counterparties or vessels with official sanctions lists. It recalls possible candidates. A person then checks each field and records the decision.

In FAQ 5, OFAC gives steps to check a possible match. First confirm which list the hit is on. Then check if it is a name on that list, and compare the other identity details. A list hit alone is not a conclusion.

Which lists does a screening check run against?

The right set depends on where you operate and on your own policy. We do not advise on it; check the rules that apply to you. From a data view, the OFAC, UN, UK and EU lists differ in fields and in update pace. The table above lists their version fields. OFAC FAQ 5 also notes that screening tools often check lists from other agencies, such as the Commerce Department Entity List.

How do we cut false positives on common names?

In our test, six common names recalled 240 records at 0.85. Three of the names have an exact namesake on the list, so a threshold change cannot remove them. Date of birth, nationality and ID numbers cut the candidates down (see the matching test above).

What do we do when the screening service goes down?

A product can make list age a switch that stops automatic release. On a timeout, it returns "no usable result". After recovery, it replays with idempotency keys and builds a re-screen list. The fallback setting that the institution approves in advance decides which flows stop (see the outage table above).

How often is the OFAC list updated?

OFAC has no fixed update day. From October 21 to November 19, 2026, OFAC changed the SDN list on 9 days. The peak was 56 new entries in one day. In the same window, the UK list changed on 8 days, and the UN list updated 10 records. A daily poll per list works, with the version field of each list to show if there is new content.

How can I check if a company is on a sanctions list?

You can search the OFAC Sanctions List Search, the UN consolidated list, the UK Sanctions List and the EU Sanctions Map. Two limits apply. If a name search finds nothing, the company can still be blocked. An entity blocked under the 50% rule may not be on any list. If a search finds the same name, it may still be a different company. Compare registration numbers, addresses and other fields.

References

  1. Sanctions List Service, US Treasury OFAC, read 2026-11-20.
  2. SDN_ENHANCED.XML, OFAC, data as of 2026-11-19, downloaded 2026-11-20.
  3. FAQ 246: fuzzy logic in Sanctions List Search, OFAC, read 2026-11-20.
  4. FAQ 247: the score field, OFAC, read 2026-11-20.
  5. FAQ 5: how to check a potential match, OFAC, read 2026-11-20.
  6. FAQ 122: weak aliases, OFAC, read 2026-11-20.
  7. FAQ 125: transactions with a weak alias only, OFAC, read 2026-11-20.
  8. 50 Percent Rule FAQs, OFAC, read 2026-11-20.
  9. A Framework for OFAC Compliance Commitments, OFAC, May 2019.
  10. Recent Actions, OFAC, read 2026-11-20.
  11. Action page, 2026-10-21, OFAC, 2026-10-21.
  12. FAQ amendments, 2026-10-26, OFAC, 2026-10-26.
  13. Extreme Networks settlement, OFAC, 2026-10-27.
  14. Action page, 2026-10-28, OFAC, 2026-10-28.
  15. General license, 2026-10-29, OFAC, 2026-10-29.
  16. Action page, 2026-11-04, OFAC, 2026-11-04.
  17. Action page, 2026-11-05, OFAC, 2026-11-05.
  18. Action page, 2026-11-06, OFAC, 2026-11-06.
  19. SDN list update, 2026-11-09, OFAC, 2026-11-09.
  20. Action page, 2026-11-13, OFAC, 2026-11-13.
  21. Action page, 2026-11-18, OFAC, 2026-11-18.
  22. Action page, 2026-11-19, OFAC, 2026-11-19.
  23. Bank of America settlement, OFAC, 2026-10-13.
  24. Bank of America enforcement release (PDF), OFAC, 2026-10-13.
  25. Blocking and rejecting transactions FAQs, OFAC, read 2026-11-20.
  26. Filing reports with OFAC FAQs, OFAC, read 2026-11-20.
  27. Sanctions List Search, OFAC, read 2026-11-20.
  28. UN Security Council consolidated list XML, United Nations, generated 2026-11-19.
  29. UN Security Council consolidated list page, United Nations, read 2026-11-20.
  30. SC/16506: 1533 Committee amends one entity, United Nations, 2026-11-13.
  31. SC/16512: 1718 Committee updates one entry, United Nations, 2026-11-13.
  32. The UK Sanctions List, UK Government, updated 2026-11-17.
  33. EU lists 113 individuals and entities, Council of the EU, 2026-11-16.
  34. EU extends sanctions to nearly all major Russian banks, EEAS, 2026-11-17.
  35. Commission sets up new EU Sanctions Office, European Commission, 2026-11-19.
  36. EU Sanctions Map, European Union, read 2026-11-20.
  37. Outcomes FATF Plenary, October 2026, FATF, 2026-10-30.
  38. Extension of the suspension of the affiliates rule, Federal Register, 2026-11-09.
  39. Expansion of End-User Controls to Cover Affiliates, Federal Register, 2025-09-30.
  40. BIS extends suspension of affiliates rule, Clyde & Co, November 2026.
  41. String Comparator Metrics and Enhanced Decision Rules, William Winkler, US Census Bureau, 1990.
  42. Matching and Record Linkage, William Winkler, US Census Bureau, 1993.
  43. Doc 9303 Part 3, ICAO, eighth edition.
  44. IMO identification number schemes, IMO, read 2026-11-20.
  45. Introducing the Legal Entity Identifier, GLEIF, read 2026-11-20.
  46. A Ship by Any Other Name, Corporate Compliance Insights, 2026-11-16.
  47. Treasury and State Department designate three Guatemalan drug trafficking groups, Just Security, 2026-11-13.
  48. US sanctions three Lebanese individuals, entities, The Tribune, 2026-11-18.
  49. How are fintech startups handling sanctions screening, Reddit r/fintech, 2026-10-28.
  50. How are you dealing with false positives in AML screening, Reddit r/AMLCompliance, 2026-10-20.
  51. EveryInfra data API catalog, EveryInfra, read 2026-11-20.

Originally published on the EveryInfra blog: Building a Sanctions List Screening Workflow: From Name Matches to Auditable Review. This article was written with AI assistance; the numbers come from the API calls and sources linked above, and were checked before publishing.

EveryInfra is a pay-per-call data API for AI agents and developers: everyinfra.com.

Top comments (0)