Sanctions and AML Screening, Natively in Salesforce

Screen any Lead, Contact or Account in one click without leaving the record. Automate checks on record creation or stage changes, run bulk or scheduled scans, and log every decision with a full audit trail inside Salesforce.

Book a Discovery Call Start a Free Trial
Or design your screening workflow in 60 seconds
~350 ms
Avg API response
Hourly
Data updates
400+
Customers
SOC 2
Type II compliant
Lead
 
 
Company
 
Country
 
Screened by sanctions.io
 

Screening With and Without the Salesforce Integration

The same check, done two ways. One of them survives an audit, a quarter-end, and a sales team in a hurry.

Legacy tools and spreadsheets beside the CRM

Export, then screen. Leads leave Salesforce as a CSV. A second copy of personal data now exists somewhere ungoverned.
Someone has to remember. The check runs when compliance gets to it. Sales has usually moved the deal on by then.
Names re-keyed by hand. Typos and missing middle names mean two people screen the same record and get two answers.
Screened once, never again. The record was clean the day it was exported. Lists have changed every hour since.
Every common name is an alert. String matching floods the queue, and the one real match hides in the noise.
Decisions live in email. When the auditor asks who cleared it and why, the answer is a search through three inboxes.

Screening natively in your CRM

Nothing leaves the org as a file. The record is screened where it sits. Input is hashed after processing and nothing is stored.
Triggered, not remembered. Screening runs on create, on a stage change or on a schedule, whether or not anyone is watching.
Fields as stored. Name, company and country come straight from the record. Same input, same answer, every time.
Rescreened as lists move. Scheduled batch runs re-check the whole object against lists refreshed every 60 minutes.
Matching that reads like a human. AI and NLP handle transliteration, nicknames, spelling and name order before an alert exists.
Every decision on the record. Reviewer, timestamp, note and outcome live on a Screening Alert object. Export the trail as CSV.

What the Integration Does

Pick an area, then a capability, to see it inside Salesforce.

Interactive

Design your screening workflow

Choose what triggers a screening, which objects it runs on, and what happens when a match comes back. The designer assembles the workflow, estimates the screening load, and lists what still needs a human decision.

Screening Across the Salesforce Record Lifecycle

Six moments in a record's life where screening runs inside Salesforce. Select one to see what gets screened, and what it costs to miss it.

AI and NLP Powered Name Matching

Matching built on natural language processing and machine learning, so the variants that defeat a string comparison still match, and the names that only look alike stop generating false positives.

Transliteration, nicknames, spelling errors and honorifics Fewer false positives No real match slipping through

Custom Confidence Scores for Your Risk Appetite

Set a separate minimum confidence score for sanctions, PEP and adverse media matches. Each data set carries a different level of risk, so each one can have its own threshold.

Stricter where it matters
Keep sanctions broad so nothing slips through, and tighten PEP or adverse media to cut the noise.
Fewer false positives
A higher score returns fewer, more precise matches, so your team reviews less noise.
A threshold you can defend
Record the thresholds you chose and why, so the decision holds up in an audit or examination.
Book a Call to See How It Works
app.sanctions.io · Confidence score settings
Screening: Alexander Petrov  
Illustrative example only. Each slider shows the minimum confidence score being adjusted, and which matches it lets through.
Next step

Talk Through Your Salesforce Setup With Us

Bring your Salesforce org and your current screening process. We'll map which objects to screen, which triggers to automate, and what changes for sales and compliance. No deck.

Book a Discovery Call Read the Implementation Guide Explore Our API
What happens next
A short call
Your org, your objects, your volume. No discovery deck.
A sandbox key the same day
Screen real names against live lists before any contract.
Live same-day
Most teams are screening real records on the day they start.

The practical guide to sanctions screening

How screening programs are built, tuned and defended: list selection across OFAC, EU, UN and HMT/OFSI, thresholds you can defend in an examination, false-positive management, and the evidence examiners ask for.

Implementation guide

Step-by-step help implementing sanctions.io into your compliance process and systems, including field catalogs, Postman collections and code snippets in several languages.

sanctions.io product data sheet

The one-pager procurement and IT ask for: full list inventory, refresh cadence, endpoint reference, latency and uptime figures, security posture, data residency and deployment options.

Sanctions and AML Screening in Salesforce, Answered

The questions Salesforce admins, RevOps and compliance teams ask before installing.

Resources

Implementation Guide
Our Implementation Guide helps you with implementing sanctions.io into your compliance process and systems.
Sanctions Screening Guide
Our Sanctions Screening Guide offers step-by-step instructions to kickstart your sanctions compliance process.
Resource Center
Our Resource Center is your ultimate palce for AML and sanctions white papers, guides,  updates, and more.
Sanctions Screening vs Sanctions Monitoring: When to Choose Which
Sanctions screening and monitoring are two distinct yet complementary approaches that form the backbone of an effective sanctions compliance program. Screening involves checking names or transactions against watchlists at key moments (such as onboarding or payment processing) to prevent prohibited activity from occurring. Monitoring, on the other hand, is an ongoing process that tracks customer behavior, ownership changes, and geopolitical developments to identify emerging or indirect sanctions risks. While screening provides immediate frontline protection, monitoring captures threats that evolve over time. The most resilient compliance frameworks combine both practices, supported by clean data, calibrated tools, strong governance, and continuous training. Organizations should align their use of screening and monitoring with their specific risk profile, regulatory obligations, and operational complexity.
Understanding OFAC Sanctions Lists: A Comprehensive Guide
The OFAC (Office of Foreign Assets Control) sanctions lists are essential tools used by the U.S. government to enforce foreign policy and national security objectives by targeting individuals, organisations, and countries involved in activities like terrorism, corruption, or arms proliferation. These lists—such as the Specially Designated Nationals (SDN) List and various non-SDN lists—restrict access to the U.S. financial system and prohibit transactions with listed entities. While centred in the United States, the global impact of OFAC sanctions means businesses worldwide must remain compliant to avoid severe penalties or reputational damage. With tools like the Sanctions List Search and downloadable datasets, OFAC facilitates screening and compliance efforts, making it crucial for companies to implement regular monitoring, staff training, and legal oversight to mitigate risks.
How Long Is Someone a PEP? Declassification, Family Members, and Where to Draw the Line
A minister leaves office. How long do you keep treating them as a PEP? Their spouse, their business partner, their adult child? FATF, the EU, the UK, and the US all answer this differently, and most firms have never actually compared the four side by side. This post lays out the real positions, the scope question around relatives and close associates, and the governance point that ties it together.
Setting Sanctions and PEP Match Thresholds: Why They Shouldn't Be the Same Number
Most firms set one fuzzy-matching threshold at implementation and apply it to every list they screen, including sanctions and PEP data, without ever revisiting the decision. This post argues that's a configuration accident, not a risk decision, and walks through why sanctions and PEP screening deserve different settings, with worked examples across payments, B2B onboarding, and insurance.
View Resources