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 Salesforce

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
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 20-minute 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 in just days
Most teams ship in under a week.

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 catalogues, 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.
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.
You've Got a Real Match. Now What?
Almost everything written about sanctions screening covers finding the match. Almost nothing covers the twenty minutes after, which is when firms actually get into trouble. This post walks through what a confirmed hit obliges you to do: blocking versus rejecting, the reporting clocks, what you can and cannot tell the customer, and what happens to the relationship afterward.
Screening Contractor and Payroll Payouts: A Compliance Guide for Global Payment Platforms
A compliance guide for global payment platforms on screening contractor and payroll payouts against sanctions lists, covering why every payout requires screening, the speed-versus-compliance tension in instant payment rails, and how to implement real-time API screening that keeps false positives low.
Screening Audit Trails: What Evidence to Retain, in What Format, and for How Long
Compliance teams routinely discover during an audit that they can prove a screen happened but not what it was screened against, at what threshold, or why an alert was cleared. Using NYDFS's 2017 findings against Habib Bank as a real example of what happens when disposition rationale goes undocumented, this post specifies the evidence set a defensible screening trail requires, the format considerations that make it usable years later, and retention periods across the US, UK, and EU.
View Resources