OFAC screening for employers (2026): when sanctions list checks apply to hiring and how to run one
On this page
- What does OFAC prohibit, and how does it reach hiring?
- Does every employer have to screen candidates?
- Which lists should the screen cover?
- How do you run a search and clear a hit?
- When does the FCRA apply?
- How do you screen without discriminating?
- What should staffing agencies do?
- Summary: OFAC screening in hiring
- Questions people ask
OFAC screening checks a candidate's name against the Treasury Department's sanctions lists, chiefly the Specially Designated Nationals and Blocked Persons (SDN) List. It matters in hiring because U.S. persons generally may not deal with blocked persons, and OFAC's blocking regulations treat both paying a blocked person and receiving services from one as prohibited; OFAC says it may impose civil penalties on a strict liability basis. We found no OFAC rule that requires every employer to screen every applicant, so as of November 2026 screening follows the employer's risk: remote workers and contractors abroad, cross-border pay, and regulated industries. A hit is only a potential match until you have checked it the way OFAC describes, and if a screening company runs the check, the FCRA applies.
Sanctions screening is one row in most international packages; the other checks are on international background checks, and the North Korean remote worker scheme, the main reason U.S. employers now meet sanctions risk in hiring, is on North Korean IT worker red flags.
Not legal advice. This summarizes OFAC's regulations, FAQs and guidance, two court decisions and other governments' official list pages as we read them in November 2026. Sanctions programs change often; involve counsel before acting on a match or hiring anyone connected to a sanctioned jurisdiction.
What does OFAC prohibit, and how does it reach hiring?
- Who must comply. "All U.S. persons," including U.S. citizens and permanent residents wherever they are, everyone within the United States, and U.S. companies and their foreign branches (OFAC FAQ 11).
- Dealing with listed people. For people on the SDN List, "generally U.S. persons are prohibited from engaging in transactions involving blocked persons wherever such blocked persons are located" (FAQ 10). The Global Terrorism Sanctions Regulations, for example, prohibit "the making of any contribution or provision of funds, goods, or services" to a blocked person and "the receipt of any contribution or provision of funds, goods, or services" from one (31 CFR 594.204). Wages are funds; work is a service.
- Employment itself. In a Russia-related FAQ, OFAC told U.S. persons employed by a blocked entity that "absent authorization from OFAC, your continued employment or board membership with such an entity is prohibited" (FAQ 568).
- Whole jurisdictions. As of FAQ 10's update of October 26, 2026, broad sanctions that generally prohibit importing or exporting goods, services or technology cover Cuba, Iran, North Korea, the Crimea region of Ukraine, and the so-called Donetsk and Luhansk People's Republic regions; the governments of Cuba, Iran, North Korea and Venezuela are blocked. Work performed for you from one of those places can raise the same issue.
- Penalties. Civil penalties vary by program and are adjusted each year for inflation, with criminal penalties in some cases (FAQ 12). OFAC "may impose civil penalties for sanctions violations on a strict liability basis" (Treasury, March 12, 2026).
The hiring risk is concrete. The State Department, Treasury and FBI warned in 2022 that North Korean IT workers seek jobs "while posing as non-North Korean nationals," and that companies that hire them face legal consequences including sanctions (joint advisory, May 16, 2022).
Does every employer have to screen candidates?
OFAC prohibits dealings; it does not set a hiring procedure. Its Framework for OFAC Compliance Commitments (May 2019) "strongly encourages" a risk-based sanctions compliance program built on a risk assessment, and OFAC does not issue certificates of non-inclusion or a "safe list" (FAQ 469). Situations where a sanctions check usually earns its place:
| Situation | Why it raises sanctions risk | Source |
|---|---|---|
| Remote employees or contractors you have not met, especially in software work | The DPRK IT worker scheme relies on false identities and remote work | 2022 advisory |
| Workers located outside the United States, or paid to foreign accounts | Listed persons can be anywhere; some jurisdictions are under broad sanctions | FAQ 10 |
| Hiring through an overseas vendor or subcontractor | Entities owned 50 percent or more, directly or indirectly, by blocked persons are blocked too | FAQ 401 |
| Employers that already run a sanctions program for customers, suppliers or exports | The program's risk assessment should decide whether workers and contractors are in scope | OFAC Framework, 2019 |
Which lists should the screen cover?
| List | Who keeps it | Note |
|---|---|---|
| SDN List and non-SDN Consolidated Sanctions List | Treasury, OFAC | Both searchable in OFAC's free Sanctions List Search |
| Consolidated Screening List | Commerce (trade.gov) | Combines "multiple export screening lists of the Departments of Commerce, State, and the Treasury" (trade.gov) |
| UN Security Council Consolidated List | United Nations | "All individuals and entities subject to measures imposed by the Security Council" (UN) |
| UK Sanctions List | UK government | "The only source for all UK sanctions designations" since the OFSI list closed on January 28, 2026 (gov.uk) |
| EU consolidated financial sanctions list | European Commission | Binding on EU nationals and people located or doing business in the EU (European Commission) |
OFAC answers questions only about its own lists. If a hit comes from another agency's list, such as the Commerce Department's Entity List, contact that agency (FAQ 5).
How do you run a search and clear a hit?
OFAC's tool "employs fuzzy logic on its name search field," using character, string and phonetic matching. A score of 100 is an exact match, lower scores widen the results, and OFAC will not recommend a threshold: users "must make their own match threshold determinations." The tool is for individual searches and should not be run by automated systems (FAQs 246 to 250 and 287). OFAC's FAQ 5 then sets four steps, which translate to hiring like this:
- Identify the list. Confirm the alert is against an OFAC list, not another agency's list or a vendor's own list.
- Identify the kind of hit. A listed name is one thing; a link to a sanctioned jurisdiction, such as a work location in Iran, is another, and OFAC says to escalate that before acting.
- Compare every detail. Review the full entry (aliases, date and place of birth, nationality, passport and ID numbers, addresses). OFAC says "many potential matches identified through screening are false positives" and suggests gathering documents such as a birth certificate or driver's license. In hiring, use the identity documents already collected for the role, not extra ones from some candidates only.
- Act on a valid match. If several details match and nothing disqualifies the match, pause the offer and any payment, and escalate to counsel. If you already hold property of a blocked person, such as unpaid wages, blocked-property rules and OFAC's 10-business-day reporting deadline may apply (FAQ 9).
A copy-ready escalation note for the file (an example to adapt with counsel):
SANCTIONS SCREENING NOTE
Candidate: [name] Role: [title] Work location: [city, country]
Date screened: [date] Lists: [SDN + non-SDN / CSL / UN / UK / EU]
Tool and settings: [tool, minimum name score]
Result: [no hit / potential match to entry ID ___]
Details compared: [DOB, nationality, ID numbers, address] - [match / differ]
Decision: [cleared as false positive / escalated to counsel on ___]
Reviewer: [name] Second reviewer (if escalated): [name]
When does the FCRA apply?
If you run the search yourself on OFAC's tool, no consumer reporting agency is involved. If a screening company reports a sanctions result about a candidate, it is part of a consumer report:
- In Cortez v. Trans Union (3d Cir., August 13, 2010), the court held "information relating to the OFAC alert is part of the consumer's 'file'" under the FCRA.
- In TransUnion LLC v. Ramirez (June 25, 2021), the Supreme Court described an OFAC add-on that flagged a "potential match" when only first and last names matched; 1,853 class members' flagged reports went to third parties.
So use the FCRA steps: the stand-alone disclosure and authorization before the check, the screening company's duty of "maximum possible accuracy" (15 U.S.C. § 1681e(b)), and the pre-adverse action notice before rejecting anyone over a reported hit. Ask the vendor which identifiers it matches on; name-only matching is what went wrong in Ramirez.
How do you screen without discriminating?
- Screen by role, not by person. Every candidate for a covered role, at the same stage, against the same lists.
- Never use nationality or a foreign-sounding name as the trigger. OFAC itself notes "sanctioned persons can be located anywhere in the world" (FAQ 10). Title VII bars national origin discrimination (42 U.S.C. § 2000e-2), and the Immigration and Nationality Act bars citizenship status and national origin discrimination (8 U.S.C. § 1324b); see citizenship status discrimination in hiring.
- Keep sanctions apart from work authorization. Form I-9 and E-Verify answer a different question and have their own anti-discrimination rules.
What should staffing agencies do?
- The agency that pays the worker carries the payment risk. Screen workers and any overseas subcontractor or vendor before the first payment.
- Put the scope in the client agreement: which lists, when, re-screening frequency, and who decides on a potential match.
- Re-screen. Lists change often; OFAC posts each change on its Recent Actions page, and the UK list page logs its own updates.
Summary: OFAC screening in hiring
| Item | The rule | Source |
|---|---|---|
| Who must comply | All U.S. persons and everyone in the United States | OFAC FAQ 11 |
| Blocked persons | No funds, goods or services to or from them | 31 CFR 594.204 (example) |
| Liability | Civil penalties possible on a strict liability basis | Treasury, March 12, 2026 |
| Duty to screen applicants | None we found; OFAC encourages a risk-based program | OFAC Framework, 2019 |
| Clearing a hit | Four steps; compare all identifiers | OFAC FAQ 5 |
| Blocked property | Report within 10 business days | OFAC FAQ 9 |
| Screening company reports it | FCRA consent, accuracy and adverse action steps | Cortez (2010); 15 U.S.C. § 1681e(b) |
| Fairness | Same check for every candidate in the role; no national origin or citizenship triggers | 42 U.S.C. § 2000e-2; 8 U.S.C. § 1324b |
Questions people ask
Do employers have to run OFAC checks on job candidates?
We found no OFAC rule that requires every employer to screen every applicant. But U.S. persons may not deal with blocked persons, which includes paying them or receiving their services, and OFAC says it may impose civil penalties on a strict liability basis. OFAC encourages a risk-based sanctions compliance program, so whether to screen, and which roles, follows the employer's own risk, such as workers or contractors abroad and cross-border payments.
What should I do if a candidate's name matches the SDN list?
Treat it as a potential match, not a finding. OFAC's FAQ 5 says to confirm the hit is on an OFAC list, review the full list entry, and compare every detail, such as date of birth, nationality, identification numbers and addresses; most alerts are false positives. If several details match and nothing disqualifies the match, stop the hiring and payment steps and escalate to counsel, who can contact OFAC.
Is an OFAC check part of a background check under the FCRA?
When a consumer reporting agency reports it, yes. The Third Circuit held in Cortez v. Trans Union (2010) that an OFAC alert was part of the consumer's file under the FCRA, and the Supreme Court's 2021 TransUnion v. Ramirez decision described a product that flagged people as potential matches on first and last name alone. The FCRA's consent, accuracy and adverse action rules then apply.
Which sanctions lists should an employer that hires internationally screen?
U.S. employers screen OFAC's SDN List and its non-SDN lists, and may use the U.S. Consolidated Screening List, which combines Commerce, State and Treasury lists. Employers with operations or workers elsewhere may also need the UN Security Council Consolidated List, the UK Sanctions List, which became the only source of UK designations on January 28, 2026, and the EU's consolidated financial sanctions list.