Use cases

Sanctions screening workflows for business teams

Choose a sanctions screening workflow for customers, suppliers or procurement. Plan the checks, review steps and evidence your team needs.

Customer onboarding sanctions screening workflow

Add sanctions checks to your customer screening process. Review matches, keep evidence and resolve failed checks before making the account-opening decision.

Explore the workflow

Supplier screening: batch checks and review workflow

Add sanctions checks to your vendor screening process. Run a supplier file in bulk, review each result and keep ownership and export checks with their own evidence.

Explore the workflow

Debarment screening for procurement review

Use debarment screening to review a bidder’s name and listing details. Save the evidence and assess contract eligibility under the right procurement rules.

Explore the workflow

Try the screening workflow your team needs

Check customers, review suppliers or assess bidders. Run a check, compare a possible match and save your team’s reasons in one place. Choose the sources that fit the task from current coverage.

Start free with 250 live screenings. Your first workspace gets them once, shared by the API and dashboard. There is no monthly reset and no card is needed. When you need more, Starter is $59/month for 5,000 checks each month. The API and review dashboard are included.

Start with the decision your team needs to make

A new customer, a supplier, and a bidder may need different checks. First name the relationship and the decision. Then choose the sources and who will review a possible match. Decide what to do if a check fails before you start.

SanctionsKit gives you list results, case review, and saved evidence. Your team decides whether to open an account, work with a supplier, or award a contract. Link that decision to the checks and the reviewer’s reasons.

Choose a single check, a batch, or monitoring

Use a single check to get a result for one person or business. Use a batch to check a file, then look at each row’s result. Use monitoring when you need to keep a subject’s details and check them again over time.

All three modes use the same completed-subject allowance. Each completed check or batch row counts once. So does each completed rescreen. To plan usage, count the subjects you will check and how often. Define why you need to keep the input for a monitor.

Plan for matches, no matches, and errors

Send a possible match to review. A completed no-match result can finish the list-check step under your policy. An error leaves that step incomplete. A required source that is unknown or unavailable cannot count as a successful check.

Keep the original list category visible. A procurement list has its own contract rules. An export-control record has its own list, and a financial-sanctions record has program details. These labels help you send the case to the right reviewer.

Test the workflow with examples that fit your work

Use examples whose answers have been checked outside the screening system. Include the names, scripts, IDs, and difficult cases your team will see. Look for missed matches and avoidable alerts before deciding how to route results.

The demo uses invented records to show the steps. It cannot prove that the matching works for your customers or that a live source is available. Use current coverage to check source status. The linked use cases explain each review process.

Common questions

Which screening workflow should our team start with?

Start with the relationship you need to review: a customer, supplier, or bidder. Name the required sources and reviewer. Then choose how to submit checks and what happens when a result needs attention.

Can several teams use the same dashboard?

Yes. The API and dashboard share saved screening history. Use clear references for each customer, supplier, or bidder so results stay easy to find. Your policy defines which checks and approvals each team needs.

Does a bulk file use one screening from our plan?

No. The plan counts completed subjects. Each completed batch row counts, as does each single check or monitoring rescreen. Count the subjects in your files and repeat checks when you estimate usage.

What should we do when a check cannot finish?

Keep it incomplete and follow your approved retry or review process. An unavailable required source is an error, even if other sources work. Do not approve the list-check step from an error response.