How to screen vendors for sanctions
Paying a sanctioned entity by accident is a compliance failure, not a bookkeeping error. Here is how to screen every payee before money moves.
Why manual sanctions screening fails
The U.S. Treasury’s Specially Designated Nationals (SDN) list changes regularly, and manually checking every new vendor against it - let alone re-checking existing vendors when the list updates - is not something a busy AP team does consistently. It only takes one missed check to create a real regulatory problem.
Where teams get it wrong
- Screening only at vendor onboarding, never again as the SDN list is updated.
- Checking the exact legal name only, missing common aliases or spelling variants.
- No record kept of the screening result, so there is nothing to show an auditor or regulator.
- Screening happens after payment is already scheduled instead of before the bill is approved.
- Treating a hit as a hard stop with no defined escalation path for a false positive.
The Vendor Screening Framework
- 1Screen at onboarding - check every new vendor and payee against the SDN list before the first payment.
- 2Re-screen on a schedule - run existing payees against list updates, not just once.
- 3Screen before every payment - not just once at setup, since names and lists both change.
- 4Escalate hits, don’t auto-reject - a name match needs human review before you refuse to pay a legitimate vendor.
- 5Log every screening result - keep a timestamped record whether the outcome was clear or flagged.
How Fintra automates sanctions screening
| Step | What Fintra does |
|---|---|
| Screen at onboarding | Every new vendor is checked against the real U.S. Treasury SDN list before their first bill is approved. |
| Re-screen on a schedule | Existing payees are re-checked as the SDN list updates, not just once at setup. |
| Screen before payment | Bill pay screens the payee again at the point of payment over the ACH payment rail, not only at onboarding. |
| Escalate hits | A potential match is flagged and routed to a human for review rather than silently blocking or silently paying. |
| Log results | SentriAI-powered compliance records every screening outcome with a timestamp in the audit trail. |
Screening is a real-time trust verdict, not a rubber stamp: AI flags potential matches, a human reviews and decides, and the decision is logged either way.
Your vendor screening checklist
Put these in place before your next vendor payment run
- Screen every new vendor against the SDN list before onboarding is complete.
- Re-screen your full vendor list whenever the SDN list updates.
- Screen at the point of payment, not only at vendor setup.
- Define an escalation owner for any potential match.
- Keep a timestamped log of every screening result, clear or flagged.
- Include aliases and known variant spellings in the check, not just the legal name.
- Review your screening process annually against current OFAC guidance.
Frequently asked questions
What is OFAC vendor screening?
It is the process of checking a vendor or payee against the U.S. Treasury Office of Foreign Assets Control’s Specially Designated Nationals (SDN) list before you do business with or pay them. Paying a sanctioned party, even unknowingly, can create real regulatory exposure - screening is the control that catches it beforehand.
Do small businesses need to do sanctions screening?
Any business making payments, including SMBs, benefits from screening - sanctions obligations are not limited to large enterprises or financial institutions. It is inexpensive to automate and expensive to skip: a single missed match can trigger a real regulatory inquiry regardless of company size.
What happens if a vendor screening returns a potential match?
A match should be escalated for human review, not treated as an automatic rejection - many hits are false positives from common names. The right process pauses the payment, routes the case to a named reviewer, and logs the outcome whether the match is cleared or confirmed.
How often does the SDN list change?
The Treasury updates the SDN list on an ongoing basis, sometimes multiple times a month. That is why screening only at vendor onboarding is not sufficient - a payee cleared last year could be added to the list later, so re-screening on a schedule and at the point of payment matters.
Stay in the loop
One practical finance briefing a week - new guides, checklists, and benchmarks.
Screen every payee before you pay
Fintra checks vendors against the real Treasury SDN list at onboarding and at payment time. Free to start, no card required.
Talk to us