Do You Need to Screen Employees Against the OFAC List? Hiring, HR, and Staffing Agency Obligations

The Short Answer

No statute or regulation says the words "screen your employees against the OFAC list." There is no employment-specific OFAC rule the way there is a Bank Secrecy Act rule for banks. But that is not the same as "you're in the clear." OFAC's sanctions regulations prohibit U.S. persons from dealing in the property of a blocked person and from providing that person services, and a paycheck, health insurance, or a 401(k) match all count. If you employ someone who is on the Specially Designated Nationals (SDN) list, every payroll run is a prohibited transaction, whether or not you ever ran a check. Is it legal to hire someone on the sanctions list? The act of hiring is not itself the violation, but paying them wages or benefits is, and because you cannot employ a person without transacting with them, you cannot lawfully keep someone on the SDN list on payroll without a specific license from OFAC. The obligation is not really "screen employees." It is "don't transact with sanctioned people," and payroll is a transaction like any other.

There's no box on a compliance checklist labeled "OFAC hire screening" that a regulator hands you. The exposure sits underneath your existing hiring process, and it surfaces the first time a name you never checked turns out to be on a list.

Does a Background Check Include an OFAC Check? Usually Not

This is the question that trips up more HR departments than any other, and the honest answer is: probably not, unless you specifically asked for it. Standard pre-employment background check packages, criminal history, employment verification, education verification, credit checks where permitted, are built around consumer reporting data sources. OFAC's SDN list and the other sanctions lists are a separate government dataset that most background check vendors do not automatically pull unless it's a named add-on or you're using a package explicitly marketed as including "OFAC" or "watchlist" screening.

Do not assume. Pull up your vendor's product description or ask your account rep directly whether sanctions list screening is bundled into the package you're paying for, or whether it's an optional line item you have to enable. Some vendors call it "OFAC screening," others bury it under "global watchlist" or "government list search." If it's not explicitly named, assume it's not there and run the check separately.

Three Different Systems, Three Different Questions

HR teams often mentally lump E-Verify, criminal background checks, and OFAC screening into one undifferentiated "background check" bucket. They answer completely different questions:

• E-Verify confirms someone is authorized to work in the United States, by matching their I-9 information against Department of Homeland Security and Social Security Administration records. It has nothing to do with sanctions.
• Criminal background checks look at arrest and conviction history through court and criminal record databases. Also unrelated to sanctions.
• OFAC screening checks a name against sanctions and denied-party lists maintained by Treasury, Commerce, and equivalent foreign bodies. It has nothing to do with someone's work authorization or criminal record. A person can be a U.S. citizen with a clean criminal record and full work authorization and still appear on the SDN list.

Passing E-Verify and a criminal check tells you nothing about sanctions status. If you need all three, you need to run all three, and most employers only run the first two.

Staffing and Temp Agencies Carry Double Exposure

If you run a staffing or temp agency, the obligation isn't singular, it's doubled. You have exposure on two fronts:

• The workers you place. You're the one issuing the paycheck (or the client is, but you sourced and vetted the person), so an unscreened worker who turns out to be sanctioned puts you in the same position as any other employer paying an SDN.
• The client companies you invoice. If you're billing a business entity for placed labor and that entity turns out to be owned or controlled by a sanctioned party, or is itself on a denied-party list like the BIS Denied Persons List, you have a second, independent screening obligation on the client side.

Agencies that only screen candidates and never screen the businesses they're contracting with are covering half the risk. Both sides of a staffing relationship, the worker and the company paying for the worker, need a check.

The Cortez Lesson: Sloppy Matching Creates FCRA Liability

If OFAC data shows up inside a consumer background report, the Fair Credit Reporting Act (FCRA) attaches to it, and a sloppy name-only match can turn a screening error into a lawsuit. The leading case is Cortez v. Trans Union, a 2010 Third Circuit decision. A consumer named Sandra Cortez was denied a car loan because a background product mistakenly matched her to a narcotics trafficker on the OFAC list who shared a similar name, and the reporting agency did not correct the error despite repeated disputes. A jury found the company violated the FCRA and awarded substantial damages. The court's broader holding was that once OFAC data becomes part of a consumer report, the credit reporting agency has to follow the same accuracy and dispute-handling duties it follows for any other credit data.

The lesson isn't "don't use OFAC data," it's "don't let name-only matching make the decision for you." A careless match on a common name can become a legal problem, not because you screened, but because you screened badly and acted on it without verification.

Getting a Hit on a Candidate: Almost Always a False Positive

If a candidate's name comes back as a potential match, do not panic and do not make an adverse decision on the name alone. The overwhelming majority of hits on common names are false positives. Before you act:

• Check the date of birth on the list entry against the candidate's actual DOB.
• Check any identification numbers, passport, national ID, or similar, against the entry.
• Check country and address information for any real overlap.
• Review aliases, not just the primary name, in case the match is on an alias rather than the legal name.

Only escalate to your compliance officer or legal counsel if identifying details actually line up, not on name similarity alone. For the full walkthrough of clearing a hit, including what documentation to keep, see how to handle an OFAC match.

A Lightweight HR Workflow That Actually Gets Used

You don't need a compliance department to do this reasonably well. A workable process for most employers looks like:

1. At offer stage, run the candidate's full legal name through a free sanctions search at ofacscreen.com/screen/, which checks all 8 major lists (OFAC SDN, OFAC Non-SDN Consolidated, BIS Denied Persons, UN Consolidated, EU FSF, UK OFSI, Canada SEMA, Swiss SECO) in one search with full results and no signup.
2. Document it. A one-time $9.99 audit-ready PDF report gives you a dated, list-versioned record for the personnel file, which is the kind of documentation an auditor or plaintiff's attorney will ask for later and which a screenshot of a search result does not reliably provide.
3. Rescreen the workforce when major list updates land, rather than treating the hire-date check as a one-time event that covers you forever. Sanctions lists change frequently, and a clean result at hire says nothing about six months later. For screening more than a handful of names at once, see batch screening best practices.

Contractors and Vendors Count Too

The prohibited-transaction logic doesn't care whether the money is a W-2 wage or a 1099 payment. If you pay a contractor, freelancer, or vendor who turns out to be on the SDN list, that payment is just as prohibited as a payroll deposit to a sanctioned employee. Businesses that carefully screen full-time hires but wave 1099 contractors and vendors straight through accounts payable are leaving the same exposure open under a different label. If your accounts payable process doesn't run new vendors and contractors through the same check as new employees, it should.

Bottom Line

There's no OFAC rule that says "screen new hires," but there doesn't need to be: paying a sanctioned person is prohibited regardless of the label on the payment, wages, benefits, contractor invoices, all of it. Don't assume your background check vendor covers sanctions screening unless it's explicitly named. Treat E-Verify, criminal checks, and OFAC screening as three separate questions. If you run a staffing agency, screen both the worker and the client. And when a hit comes back, verify identifying details before you act on it, a name alone is rarely enough to justify an adverse decision. A free check at ofacscreen.com/screen/ at offer stage, backed by a documented report, closes most of this gap in a few minutes per hire.