implement OFAC/sanctions screening against the SDN list with fuzzy matching and false-positive handling

domain: banking-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Obtain the OFAC SDN (Specially Designated Nationals) list in XML format from the US Treasury's public URL; also consider downloading the Consolidated Sanctions List which includes additional programs beyond OFAC.
  2. Parse and index the SDN list, normalising names by removing diacritics, standardising whitespace, and storing name variants (alt names, aliases) separately; rebuild the index on each updated list download (OFAC publishes updates irregularly).
  3. At screening time, run the input name through phonetic normalisation (e.g., Soundex or Metaphone) or edit-distance matching (Levenshtein) against the index; most compliance vendors use a configurable match score threshold (commonly 85–90%) to flag hits.
  4. For any hit above your threshold, present the match for human review with the matched SDN entry details, the input data, and the match score; do not auto-block on fuzzy matches without human review unless your compliance policy explicitly requires it.
  5. Implement a false-positive management workflow: allow compliance officers to document cleared false positives and store the cleared name/ID pair to reduce repeat alerts on the same individual.
  6. Log all screening events with timestamps, input data, match results, reviewer actions, and disposition; retain these records for the period required by your compliance program (typically 5 years for BSA purposes).

Known gotchas

Related routes

Run OFAC SDN list screening with fuzzy matching using the OFAC OFAC API and manage false positives with a review queue
banking-general · 6 steps · unrated
Integrate sanctions and watchlist screening (OFAC and other lists) into onboarding
ofac.treas.gov/faqs/SDN-list-access · 6 steps · unrated
Screen a customer against OFAC SDN, PEP lists, and adverse media sources during onboarding
identity-general · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans