OFAC Background Check: A Guide for Nonprofits
What is an OFAC background check and does your nonprofit need one? Our guide explains the SDN list, compliance, and how to screen volunteers responsibly.
On this page
Do you need an OFAC background check for every volunteer, or are you adding friction because bank-style compliance advice got copied into the nonprofit world without context?
That's the gap most nonprofit leaders run into. They hear that OFAC screening is important, then they get vague guidance that treats a church volunteer, a youth coach, an international aid contractor, and a wire transfer beneficiary as if they create the same risk. They don't.
For nonprofits, an OFAC background check is useful when your program touches sanctions risk in a real way. That usually means cross-border activity, international donors, overseas travel, foreign beneficiaries, payments, or roles with financial authority or sensitive access. If your volunteer program is entirely local and low-risk, OFAC may matter far less than your criminal screening process, reference checks, and safeguarding controls.
Table of Contents
- What Is an OFAC Background Check
- OFAC Checks vs Other Volunteer Screening
- When Nonprofits Actually Need an OFAC Check
- A Step-by-Step Workflow for OFAC Screening
- Handling Hits and Documenting Your Process
- Integrating OFAC Checks Into Your Workflow
- OFAC Check Frequently Asked Questions
- Do we need consent to run an OFAC check on a volunteer
- How often should we re-screen volunteers
- Is the SDN list the only thing that matters
- Does a possible match mean we should reject the volunteer
- Do all nonprofits have a legal duty to run OFAC checks on every volunteer
- What about entity screening for vendors or partner organizations
- Does insurance require OFAC screening
What Is an OFAC Background Check
Could one volunteer application create sanctions risk for your nonprofit, even if nothing looks unusual in a standard screening report?
An OFAC background check screens a person or organization against U.S. sanctions and restricted-party lists maintained by the Office of Foreign Assets Control, part of the U.S. Department of the Treasury. For nonprofits, the point is narrow and practical. The check helps prevent the organization from doing business with, sending funds to, or providing certain forms of support to a blocked or restricted party.
In plain terms, this is a sanctions screen. It is not a character assessment, and it is not a general safety screen.
How it differs from a criminal background check
A criminal background check looks for reportable court records. An OFAC check looks for possible matches to sanctioned individuals, entities, vessels, or other blocked parties.
That distinction matters for nonprofit leaders because these checks answer different questions. A criminal screen helps evaluate role-related safety and suitability. An OFAC screen helps address sanctions exposure. One does not replace the other, and a clean result on one says little about the other.
A possible OFAC hit also does not mean the person committed a crime. It means the name needs review before your team moves ahead.
If your staff needs a quick refresher on screening categories, this guide to what shows on background checks explains what criminal screening reports usually contain and what they do not.
Why name matches require review
OFAC screening tools are built to catch possible matches, including close variations in spelling and formatting. The U.S. Treasury's OFAC Sanctions List Search tool guidance reflects that reality. Searches may return similar names, aliases, and partial matches because the goal is to identify names that deserve a closer look.
For nonprofits, process holds significant importance. Many volunteer programs work with incomplete applications, nickname usage, and names transliterated from other languages. That increases the chance of false positives. A match on name alone is not enough to make a final call. You need to compare other identifiers, such as date of birth, address, country, passport data, or organizational details if you have them.
Practical rule: Treat an OFAC result as a screening flag that requires review, not as proof that the applicant is sanctioned.
What this means in a nonprofit setting
Nonprofits tend to overuse or misunderstand OFAC checks in one of two ways. Some skip them even when they handle international payments, cross-border aid, or finance-related volunteer roles. Others run them on every volunteer in every program, even when the legal risk is remote and the process only slows onboarding.
The better approach is to use OFAC screening for the risk it addresses. Sanctions compliance. Nothing more.
Used well, an OFAC check gives your organization a defensible way to identify restricted-party concerns and document that you reviewed them. Used poorly, it creates avoidable noise and makes volunteers feel like they are being screened for criminal conduct when your team is only checking sanctions risk.
OFAC Checks vs Other Volunteer Screening
Why do nonprofit teams get tripped up here? Because "background check" gets used as if it means one thing, when it really covers different tools built for different risks.
An OFAC check does not measure safety. It measures sanctions exposure. Criminal history screening and sex offender registry searches answer different questions, and a nonprofit that treats them as interchangeable will either miss a real risk or add screening that creates delay without much value.
What each screening type is built to catch
For volunteer programs, the better approach is to match the screen to the role. A youth-serving program, a warehouse volunteer role, and a volunteer who can approve overseas expenses do not raise the same issues.
| Check Type | What It Is | Primary Purpose |
|---|---|---|
| Criminal background check | A search for reportable criminal court records | Assess safety, suitability, and role-related risk |
| Sex offender registry search | A registry search tied to sex offender registration records | Protect vulnerable populations and support safeguarding |
| OFAC check | A sanctions screening against restricted-party lists | Help prevent prohibited dealings with sanctioned individuals or entities |
That distinction matters in day-to-day operations.
A clean criminal result does not resolve sanctions risk. A clean OFAC result does not tell you whether someone is appropriate for a youth program, elder care role, or any position involving vulnerable people.
Why nonprofits should keep these checks separate
OFAC rules are enforced by the U.S. Treasury's Office of Foreign Assets Control. Civil and criminal penalties for sanctions violations can be severe under OFAC's enforcement framework and the underlying statutory authorities described by the U.S. Department of the Treasury and the U.S. Department of Justice summary of IEEPA penalties. For a nonprofit director, the practical point is simple. If your organization engages with cross-border funds, foreign partners, overseas travel, or restricted regions, sanctions screening is a legal risk control, not a substitute for safeguarding review.
For many domestic volunteer roles, sanctions risk is low. The heavier lift usually belongs in criminal screening, reference checks, training, supervision, and role design. That is where many nonprofits should spend their limited time and budget.
For internationally exposed roles, OFAC earns its place. Even then, it should be scoped to the risk. A volunteer helping with local event setup is different from a volunteer who can move money, coordinate foreign shipments, vet overseas partners, or handle donor activity tied to another country.
What works in practice
Use criminal and registry screening to address person-based safety concerns. Use OFAC to address prohibited-party and sanctions concerns. Keep the decision logic separate in your policy and in your staff training.
That separation also makes onboarding easier to explain. Volunteers are less likely to feel over-screened when your team can say, in plain language, why a given check is being run and what decision it supports.
If your organization is tightening intake and approval steps at the same time, tools like solutions for managing nonprofit volunteers can help centralize forms, role assignments, and review records. The compliance value comes from consistency, not from adding every possible screen to every volunteer.
The mistake I see most often is using OFAC as a symbolic add-on. If you run it, define which roles require it, who reviews possible matches, and what records you keep. Otherwise, the check adds noise, slows onboarding, and does little to protect the organization.
When Nonprofits Actually Need an OFAC Check
Here, nonprofit screening should get more selective.
Not every organization needs to run an OFAC background check on every volunteer. The stronger approach is risk-based. Guidance cited by BackgroundChecks.com on when an OFAC check is needed says OFAC checks are especially relevant when applicants have non-U.S. origins, recently emigrated, or lived abroad, and for nonprofits the primary exposure often comes from international donors, cross-border payments, or volunteer roles with sensitive access.
Situations where OFAC screening usually makes sense
If I were advising a nonprofit director, I'd start with the program model, not the volunteer title.
- International programs: Volunteers who support overseas projects, travel abroad, coordinate shipments, or work with foreign partner organizations create clearer sanctions exposure.
- Cross-border money movement: If your organization receives foreign donations, sends grants abroad, reimburses international expenses, or pays foreign vendors, OFAC deserves attention.
- Sensitive financial authority: Treasurers, finance volunteers, procurement support, and staff-like volunteers with payment access can create outsized risk even in a domestic nonprofit.
- Foreign ties in the role itself: Some roles naturally involve people, entities, or destinations outside the United States. Those are stronger candidates for OFAC screening.
Situations where OFAC may be more noise than value
A local youth sports league, neighborhood pantry, or library volunteer program with no international activity may decide OFAC isn't a front-line control for every role. That can be a sound decision if it's documented and paired with stronger controls where the actual risk sits.
That's the part generic compliance content misses. A volunteer handing out water bottles at a local event does not create the same sanctions profile as a volunteer managing overseas partner payments.
Director's test: Ask where your organization could accidentally interact with a sanctioned person or entity. If you can't describe a realistic path, universal OFAC screening may be hard to justify.
Build the decision into volunteer operations
This decision shouldn't live only in legal memos. It should live inside your intake process, role design, and volunteer management workflow. If your team is tightening operational consistency anyway, these solutions for managing nonprofit volunteers can help you map screening requirements to role types, approval paths, and recurring reviews.
A practical approach is to classify roles into simple categories such as local low-risk, financially sensitive, and internationally exposed. Then assign OFAC screening only where it meaningfully reduces risk. That keeps the process defensible without turning onboarding into a compliance obstacle course.
A Step-by-Step Workflow for OFAC Screening
The hardest part of OFAC screening isn't running the search. It's building a repeatable process around it.
OFAC's own search tools use approximate string matching, which means similar names can trigger false positives, and OFAC's sanctions search guidance makes the larger point clear: good screening depends on a repeatable method to minimize false positives, document decisions, and keep records current as lists change.
A simple visual helps teams standardize the process.
A workable nonprofit workflow
Decide which roles need it
Don't start with universal screening. Start with role categories and sanctions exposure.Collect enough identifying information
A name alone often isn't enough to resolve a possible match. Use the details your process lawfully collects, such as legal name and other identifying information relevant to screening.Run the search during onboarding
Put the OFAC check where it belongs in the intake flow. It should be part of the decision path for designated roles, not an afterthought after placement.Review potential matches calmly
Expect possible flags. Similar names are common. The first question is not “How do we reject this person?” It's “What else do we need to compare?”Document the outcome
Record what was reviewed, what did or didn't align, and why the record was cleared or escalated.Set a re-screen trigger
Screening shouldn't freeze in time. If the role remains active and risk remains present, define when to re-screen.
A short explainer can also help train non-legal staff on the basic flow:
What to do with a flag
The wrong reaction is instant disqualification. The right reaction is controlled review.
Look at whether multiple details line up, not just the name. If your process is light and local, the review may be simple. If the role involves overseas payments or partner entities, your review should be more careful.
A nonprofit doesn't need a giant sanctions department to do this well. It needs a checklist, a designated reviewer, and a rule that nobody makes snap decisions from a fuzzy match result.
Handling Hits and Documenting Your Process
What happens when a volunteer's name appears to match a sanctions list entry?
This is the point where nonprofit screening either stays disciplined or becomes arbitrary. A possible OFAC hit does not mean you have found a blocked person. In volunteer programs, the usual issue is a common name, limited identifying data, and a staff member who is unsure whether to clear the record or stop the onboarding process.
The practical goal is simple: make a consistent decision, document why you made it, and escalate only when the facts justify it.
The FFIEC BSA/AML Manual on OFAC controls explains the control concepts that matter here, including timely list updates, defined name-matching criteria, and OFAC's 50 Percent Rule for entities owned in the aggregate by blocked persons. For nonprofits, that matters most when a volunteer role touches international partners, overseas programs, or vendor and grant payments. For a local volunteer role with no money movement and no international exposure, ownership look-through is often not the issue. Careful review and clear records are.
How to review a possible match
Start with the record in front of you. Do not treat a name hit as a final result, and do not let front-line staff make ad hoc calls.
- Compare more than the name: Check date of birth, country, address, middle name, passport or ID details, and any other data you lawfully collected.
- Record what matched and what did not: A short note saying “cleared” is not enough. Note which identifiers were reviewed and why the record was cleared or escalated.
- Pause placement for higher-risk roles: If the role involves international travel, access to funds, or contact with foreign counterparties, hold the placement until review is complete.
- Escalate on multiple points of alignment: If several identifiers line up, send the case to the person responsible for compliance, outside counsel, or a screening provider with sanctions review capability.
- Keep decisions centralized: One reviewer or a small trained group should handle these cases so similar facts get similar outcomes.
For most nonprofits, that level of process is enough. You do not need a bank-style sanctions team. You need a defined path, a trained reviewer, and notes that another staff member could understand six months later.
Sample policy language you can adapt
Use language that reflects how nonprofit programs operate:
The organization may conduct sanctions screening for volunteer roles that present elevated compliance risk, including roles involving international activity, access to funds, partner onboarding, or other identified risk factors. If a potential OFAC match appears, the organization will review available identifying information, document the basis for its determination, and escalate the matter when the available facts suggest a credible match. The organization will not make a final decision based on name similarity alone.
That wording helps because it ties screening to role-based risk, not blanket screening for every volunteer in every program.
Documentation protects the organization and the volunteer
Good documentation does two jobs. It shows that staff followed a defined process, and it reduces the chance that a volunteer with a common name gets treated unfairly.
Keep the file practical. Save the search result, the identifiers reviewed, the reviewer's name, the date, and the final disposition. If your team is still building that discipline, it helps to understand what are compliance systems for before you add tools or automate decisions.
If a screening outcome later feeds into a broader background check denial process, this adverse action notice template for screening workflows can help your team structure notice steps correctly.
Integrating OFAC Checks Into Your Workflow
Manual screening works for very small programs. It starts to break when your team manages recurring cohorts, multiple approval points, or a mix of domestic and international roles.
That's where workflow design matters more than legal theory. If screening sits outside your volunteer system, people forget it, duplicate it, or apply it inconsistently. If it sits inside the process, the check becomes one controlled decision point among several.
What efficient integration looks like
A solid setup usually includes role-based triggers, a queue for possible matches, and an audit trail showing who reviewed what. That can be done with a volunteer management platform, a background screening provider, or internal workflow software if your process is mature enough.
If your team is still building that foundation, it helps to understand what compliance systems are for before you buy tools or automate steps. The point of a compliance system isn't bureaucracy. It's consistent execution, documentation, and follow-through.
Tools should reduce judgment errors, not remove judgment
Automation is useful for routing and recordkeeping. It is not a substitute for review when a name is close but unclear.
Some nonprofits use provider APIs to kick off screening from their volunteer application flow, push results into a case review queue, and trigger re-screening reminders for active high-risk roles. That makes sense. So does connecting alerts to staff notifications and approval tasks.
VolunteerBadge is one example of a screening provider that includes OFAC sanctions screening in its volunteer background check workflow, and teams that want less manual handling may also look at options for automated background check processes that connect screening to intake systems and internal approval paths.
The best nonprofit workflow is usually not the most complex one. It's the one your staff will actually follow every time.
Keep the nonprofit version of “integration” modest
You don't need enterprise software architecture to do this well. A practical build often looks like this:
- Role tagging in intake: Mark internationally exposed or financially sensitive positions.
- Automatic routing: Send those applications into an OFAC review step.
- Decision logging: Store the result and reviewer notes in the same record.
- Re-screen prompts: Trigger review when a role changes, an assignment becomes international, or a periodic review date arrives.
That's enough structure for most nonprofits. The primary win is consistency.
OFAC Check Frequently Asked Questions
Do we need consent to run an OFAC check on a volunteer
Your organization should align this with its overall screening and disclosure process, especially when OFAC screening is bundled with a broader background check. As a practical matter, nonprofits should be transparent about what checks they run, when they run them, and how results are reviewed.
How often should we re-screen volunteers
Use a risk-based schedule. For low-risk local roles, many nonprofits won't need frequent OFAC re-screening. For internationally exposed or financially sensitive roles, re-screen at onboarding and again on a defined recurring basis, and also when role details, geography, or payment activity change.
Is the SDN list the only thing that matters
No. The SDN list is central, but sanctions screening isn't just an exact name lookup against one static list. In practice, your process should focus on whether a flagged result needs review and whether your provider or tool keeps underlying lists current.
Does a possible match mean we should reject the volunteer
No. A possible match means you need review. Similar names can trigger results, so the decision should be based on documented comparison of available identifiers, not on the flag alone.
Do all nonprofits have a legal duty to run OFAC checks on every volunteer
No universal rule fits every nonprofit volunteer role. The stronger question is whether your organization has sanctions exposure through international relationships, payments, donors, travel, or sensitive access. If the answer is yes, OFAC screening becomes more relevant.
What about entity screening for vendors or partner organizations
That's where many nonprofits underestimate risk. If you work with foreign counterparties, grants, fiscal partners, or overseas intermediaries, sanctions review may need to cover entities as well as individuals. Ownership issues can matter, so treat organization screening as more than a simple name search.
Does insurance require OFAC screening
Sometimes people assume insurance automatically requires it. That isn't a safe assumption. Check your policy requirements, funding agreements, and legal advice if your nonprofit has international exposure. Don't build a universal screening rule based on guesswork.
A sound nonprofit policy is usually simple: run OFAC checks where sanctions risk is real, review flags carefully, document decisions, and avoid turning a narrow compliance tool into a blanket obstacle for volunteers.
If your nonprofit wants to include OFAC sanctions screening inside a broader volunteer screening process, VolunteerBadge offers volunteer background checks built for nonprofits, with OFAC included as part of the screening workflow.
