Table of Contents
Sanctions screening in customer onboarding is the checkpoint that stops a risky party before they become a live account. It sits inside the process you already run to sign up a new customer. The goal is simple. No account goes active until it has passed a screen. This article is about the workflow, not the mechanics of a single search.
Think of it as a gate, not a task. Onboarding moves a person or company from lead to approved customer. You want the screen built into that flow so it happens every time, on its own, with a clear record. If you want the step-by-step of one check, read our guide on how to do denied party screening. Here we focus on process design.
Why the onboarding stage matters
Onboarding is your first and best chance to catch a problem. Once an account is live, money moves and goods ship. Unwinding a bad relationship later is slow and costly. A denied party that slips through can expose you to real penalties. Our page on penalties for dealing with a denied party shows what is at stake.
Screening at onboarding also sets a clean baseline. You know the customer was clear on day one. From there you only need to watch for changes. That makes your whole program easier to run. Screening is one piece of a wider denied party screening program that covers your customers, suppliers, and partners.
Where screening fits with KYC
KYC collects who the customer is. Screening checks that identity against sanctions and denied party lists. The two work together. You cannot screen well without good KYC data. And KYC without screening leaves the risk question unanswered.
Run the screen after you have collected core identity fields. You need the legal name, any trading names, the country, and the key people. For companies, you also need the owners. Sanctions can reach an entity through ownership. The 50 percent rule means a firm can be blocked because a listed party owns enough of it. So collect ownership data before you screen.
The onboarding screening workflow
Here is a clean order of steps. Each account passes through the same path. That is what makes the gate reliable.
- Capture identity data during signup. Legal name, aliases, address, country, and beneficial owners.
- Trigger the screen automatically once required fields are complete.
- Match the data against sanctions and denied party lists.
- Route any hit to a reviewer. A clean pass moves straight to approval.
- Resolve each hit as a true match or a false positive, with a note.
- Approve and activate the account only after the screen is cleared.
- Store the result, the lists used, and the date in your records.
The key design choice is the block at step six. The system should not let an account go live with an open hit. Make that a hard rule in your tooling. A soft warning gets ignored under pressure.
Which lists to screen against
Match against the lists that fit your markets and goods. For US exposure, that includes the main sanctions and export lists.
| List | What it covers |
|---|---|
| OFAC SDN List | Sanctioned people, firms, and vessels blocked from US dealings. |
| BIS Entity List | Parties with export restrictions on US-origin items. |
| Consolidated Screening List | A single US government feed that combines many lists. |
Pick your lists based on where you sell and where your customers sit. Many teams start with the consolidated feed for wide US coverage. Add regional lists for your own jurisdictions. Keep the list set the same for every account so results stay consistent.
Automate the trigger, not just the search
Many teams automate the search but still start it by hand. That gap is where accounts slip through. The stronger design fires the screen from the onboarding system itself. When the required fields are filled, the screen runs. No one has to remember.
Automation also cuts noise. Good tools handle name spelling, aliases, and partial matches better than a manual lookup. That means fewer false hits and faster clean passes. For a fuller comparison, see automated versus manual denied party screening. Automation does not remove human review. It routes real hits to a person and lets clean cases flow.
Handling hits and false positives
Most hits are not real matches. A common name can flag the wrong person. Your process needs a clear way to resolve each one. A reviewer compares the extra data, such as date of birth, address, or country. If it does not match the listed party, mark it a false positive and note why.
Write down the reason every time. That note is your defense if the decision is ever questioned. Our guide on false positives in denied party screening covers how to work through them. If the match looks real, stop the onboarding and escalate.
Keep the records
A screen you cannot prove is a screen you did not do. For each account, keep a record of what you checked and when. That record is your audit trail.
- The name and data screened.
- The lists used and their date.
- The result, including any hits.
- How each hit was resolved, and by whom.
- The date the account was approved.
Store these so you can pull one up fast. Regulators and auditors want to see the decision behind an account. A clean file makes that easy. Learn more about what makes a good audit trail.
Screening does not end at onboarding
Passing at signup is the start. Lists change and so do customers. A party clear today can be listed next month. So plan to re-screen your customer base on a schedule. Our page on how often to run denied party screening can help you set the cadence. Build the same gate logic into that ongoing check.
Frequently Asked Questions
When in onboarding should the screen run?
Run it after you collect core identity and ownership data, and before you activate the account. That way the screen has good data to work with, and no account goes live unchecked.
Is sanctions screening the same as KYC?
No. KYC gathers and verifies who the customer is. Screening checks that identity against sanctions and denied party lists. They work as a pair inside the same onboarding flow.
Can small teams automate onboarding screening?
Yes. Many affordable tools connect to signup forms and run the screen on their own. Small firms benefit most, since it saves time and cuts errors. See our notes on denied party screening for small business.
Key Takeaways
Build the screen into your onboarding flow as a hard gate. Collect identity and ownership data, run the check automatically, route hits to a person, and block activation until the account is clear. Keep a clean record of every decision. Then re-screen on a schedule so a clear customer stays clear. Do this well and no account goes live unchecked. If you want help designing this into your denied party screening process, contact our team.