Compliance
OFAC and visitor screening: what facilities are actually required to do.
The Office of Foreign Assets Control (OFAC) publishes the Specially Designated Nationals and Blocked Persons List, the SDN List. Most companies screen against it in finance, sales and payroll, where money and services change hands. No OFAC regulation requires you to screen people as they come through the front door. Some facilities choose to anyway, as part of a risk-based sanctions or security program. This post covers what the law does and doesn't ask, how the list works, and how to screen at check-in without slowing arrivals.
Who OFAC rules apply to
OFAC sanctions bind US persons. In most programs that means US citizens and permanent residents wherever they are, entities organized under US law (including their foreign branches), and anyone physically in the United States. The Cuba and Iran programs go further and also cover foreign entities owned or controlled by US persons.
A company outside the US isn't generally subject to OFAC just because it has US customers. It can still be exposed if it causes a US person to violate sanctions, for example by routing a prohibited payment through a US bank, and some programs carry secondary sanctions aimed at non-US persons.
The core prohibition is about dealings. US persons may not do business with an SDN, directly or indirectly, and must block any of their property that comes into their possession. Under OFAC's 50 Percent Rule, the same applies to entities owned 50% or more by blocked persons.
What the law doesn't say
There is no OFAC rule that says a facility must check visitors against the SDN List at entry. Admitting someone isn't automatically a sanctions issue, but what happens during the visit can be: a sales meeting, a paid training course or a technical service given to a blocked person can be a prohibited dealing. That is the real reason some organizations screen at the door.
How far to go is a risk decision. OFAC's 2019 Framework for OFAC Compliance Commitments expects a risk-based compliance program sized to your exposure, built on a risk assessment, internal controls, testing and training. Screening the people who come on site is one control an organization can choose to include.
Export controls are a separate question. Under the Export Administration Regulations (administered by Commerce's Bureau of Industry and Security) and ITAR (administered by the State Department's Directorate of Defense Trade Controls), releasing controlled technology or technical data to a foreign person in the United States can be a "deemed export" that needs a license (15 CFR 734.13(b); 22 CFR 120.50). That turns on the visitor's nationality and what they will see, not on the SDN List. The restricted-party lists those agencies keep, such as the BIS Entity List and Denied Persons List and DDTC's debarred parties, are published in the US Consolidated Screening List.
Organizations that do screen at entry are usually:
- Defense and export-controlled manufacturers, where visitor screening sits alongside their deemed-export controls.
- Banks, money services businesses and other financial firms that already run sanctions programs for customers and extend them to the building.
- Energy, utility and other infrastructure operators that treat it as a security measure.
- Companies that regularly host foreign delegations, trade visits or training.
What the SDN list actually is
The SDN List is maintained by OFAC. It names individuals, entities, vessels and aircraft whose property is blocked under one or more sanctions programs, and it runs to thousands of entries.
SDN entries include:
- Primary name in Latin script.
- Aliases, alternative spellings, and transliterations.
- Date of birth if known.
- Nationality and country of residence if known.
- Passport or ID numbers if known.
- The specific sanctions program they are on (for example SDGT for global terrorism, IRAN for Iran-related, RUSSIA-EO14024 for Russia-related).
OFAC changes the list whenever it adds, removes or amends designations. There is no fixed schedule; in practice updates often land several times a month, sometimes on consecutive days. A screening tool should refresh its copy at least daily, so a designation published this morning is in the next day's checks at the latest.
Fuzzy matching: what holds and what blocks
A visitor types their name at the kiosk and the screening engine compares it with every list entry. Exact matching misses spelling variants; loose matching floods reception with false hits. Most programs settle on two thresholds:
- A high score that stops entry. An exact or near-exact match on a listed name or alias. The visitor is refused until someone with authority reviews it.
- A review band below it. Close enough to need a person's judgment. The visitor waits while a named reviewer decides.
- Everything else clears. Below the review band the visitor signs in normally.
The reviewer's job is to rule a namesake in or out using what the list entry says beyond the name: date of birth, nationality, addresses, the company the visitor came from. Set the thresholds so the review band stays small. If everything is held, front-desk staff learn to wave people through and nothing gets caught.
What the screening record should show
No regulation sets a format for visitor screening records. If anyone reviews your screening later (an internal auditor, an insurer, a due-diligence team, or OFAC after an apparent violation), the record should show:
- Timestamp of the screening event.
- The name that was screened, as typed.
- Which copy of each list was used, for example when it was last refreshed.
- The result: clear, held for review, or refused, with the match score.
- If held or refused: the reviewer's decision, their name, the time and their reason.
How BeckonDesk screens at check-in
- Five public lists plus your watchlist. Each visitor's name and company are checked against the OFAC SDN List, the US Consolidated Screening List, the UN Security Council Consolidated List, the EU Consolidated Financial Sanctions List and the UK Sanctions List. Contractors are screened too, when they are added and at every kiosk check-in.
- Refreshed daily. The lists are downloaded from their publishers once a day. Aliases and alternate names published on all five lists are screened as names in their own right.
- Name-only matching. Names are uppercased and stripped of accents and punctuation, then scored from 0 to 100 on edit distance and word overlap. Common transliteration variants, such as Alexei, Alexey and Aleksei or Sergei and Sergey, are matched as well, and a name made up entirely of variant spellings is held for review rather than refused. There is no phonetic or nickname table, and date of birth, nationality and country are not used. Your reviewer checks those against the list entry.
- Refuse at 88, hold from 80. Every sign-in path refuses a score of 88 or more. At the kiosk, a score of 80 to 87 holds the visit for review rather than letting it through. The visitor sees "We're unable to clear your visit. Please see the front desk." The host, receptionists and admins are emailed, without the match details.
- Admins decide. Only an admin can clear a hold, and overriding a refusal needs a written reason. For kiosk holds, an AI-written note suggests whether the match looks like a namesake; it never clears anyone.
- A screening log. Every check, clear or not, is logged with its outcome, score and the time each list was last refreshed, and the log exports as CSV.
BeckonDesk doesn't record nationality, so it can't tell you whether a visit is a deemed export. Keep that check in your export compliance process.
Related reading
- OFAC visitor screening: how it works
- Visitor sanctions screening checklist: 36 items
- Visitor screening for defense, manufacturing and ITAR-adjacent sites
- Sanctions screening feature deep-dive
- Visitor management for regulated facilities
- Contractor insurance verification at the gate
- Evacuation roll call vs the paper visitor book
Screen a real SDN name in a live demo.
Bring a name off the SDN List. In 30 minutes we'll show the hold at the kiosk, the admin review and the screening log export.