What Sanctions Screening Really Costs: A Worked Example for a 2-Million-Customer Bank
In our five-year model for a hypothetical 2-million-customer bank, the screening license is under 17% of total cost. Analysts clearing false positives cost far more, and the gap between a tuned and an untuned setup tops $6 million.
Why the license fee is the smallest number you'll negotiate
Most sanctions screening procurements start with the vendor's quote and stop there. That's the wrong order. Over a full contract term, the license is usually a minor line in sanctions screening software pricing. The big costs are the analysts who clear alerts and the tuning work that decides how many alerts there are.
This piece builds a five-year cost model for a hypothetical bank. Every figure is an assumption, built on typical 2026 market ranges that vary widely by contract, region and vendor. Keep the structure, then replace the numbers with your own quotes and salary data before anything goes to a budget committee.
The hypothetical bank and the assumptions behind it
Hypothetical example. Say a retail and commercial bank has 2 million customers and screens 40,000 payments a day, including cross-border wires and some instant payments that run 24/7. That's roughly 14.6 million screened payments a year. The bank screens customers at onboarding and whenever a list changes, against consolidated sanctions lists, PEP lists and a limited set of adverse-media categories.
The core assumptions:
- A Level 1 analyst clears about 70 payment alerts or 60 customer alerts per working day, across roughly 220 working days a year.
- Level 2 review, QA and supervision add 20% on top of Level 1 headcount.
- A blended fully loaded cost of $75,000 per analyst, mixing an onshore Level 2 team with a nearshore or offshore Level 1 team. Fully loaded costs might run from roughly $25,000–$45,000 in hubs like Manila, Bengaluru or Cairo to $90,000–$140,000 in London, New York, Singapore or Dubai.
- Two scenarios. Scenario A runs close to out-of-the-box settings: 2% of payments alert, plus 300 customer alerts per business day. Scenario B pays for tuning: 0.7% of payments alert, plus 120 customer alerts per business day.
What a $250,000-a-year screening license and implementation cover
For a bank this size, an annual SaaS subscription covering customer and payment screening typically falls between $150,000 and $400,000. Pricing is usually tiered by customer records, transaction volume, or both. The model assumes $250,000 in year one with a 5% annual uplift, about $1.38 million over five years. Implementation is a one-time $350,000, toward the middle of a typical $200,000–$600,000 range. That covers integration with core banking and payment hubs, ISO 20022 message mapping and initial list configuration.
Established vendors in this space include LexisNexis Risk Solutions (Firco), NICE Actimize, Oracle and SAS. Cloud-native options such as ComplyAdvantage and Napier use different pricing structures that can suit mid-sized institutions, so compare them on total cost, not license alone. Whatever you shortlist, confirm it can screen in real time for instant schemes like SEPA Inst, UPI, PIX or FedNow.
Regulation shapes this too. In the EU, the Instant Payments Regulation moves SEPA instant transfers toward regular (at least daily) screening of customers against sanctions lists rather than screening every transaction. That shifts load from payment screening to customer screening. Other regions differ, so confirm how your local rules apply with counsel.
Sanctions list data cost and PEP screening subscriptions
Official lists are free. OFAC, the UN, the EU, the UK's OFSI and many national authorities publish their own. Banks pay for consolidated, de-duplicated data enriched with aliases, identifiers and ownership links, plus PEP and adverse-media coverage. Providers include LSEG World-Check, Dow Jones Risk & Compliance, LexisNexis and Moody's.
For a 2-million-customer book, a commercial sanctions list data cost of $60,000 to $250,000 a year is a plausible range. Most of the variation comes from how broad your PEP screening is (including relatives and close associates) and how much adverse media you take. The model assumes $120,000 a year with 6% annual increases, about $680,000 over five years.
Data choice also changes your labor costs. A broad PEP file with weak identifiers, like missing dates of birth or nationalities, produces more watchlist screening false positives than a narrower file with richer identifiers. Ask every data vendor for identifier fill rates by list category.
Where alert volume turns into headcount
In Scenario A, 2% of 40,000 payments is 800 alerts a day, every day of the year. That needs about 19 Level 1 analysts, or 22.8 once Level 2 and QA are added. The 300 customer alerts per business day add about 7 more. The total is close to 30 people, about $2.24 million a year.
In Scenario B, tuning brings payment alerts down to 280 a day and customer alerts to 120. Headcount falls to about 11, roughly $820,000 a year. Tuning isn't free: the model includes a $200,000 initial project and $75,000 a year for retuning and model validation in years two to five. Year one is costed at $1.5 million in analyst spend, because savings arrive gradually as rules change and the changes are validated. Scenario A carries only $40,000 a year of baseline validation.
The levers that usually matter most are fuzzy-match thresholds and secondary identifiers like date of birth, country and entity type. Good-guy lists for repeat counterparties and cleaner structured address data in ISO 20022 messages help too. Each change needs documented testing so true matches aren't suppressed. Regulators in most jurisdictions will ask to see it.
Five-year totals for the untuned and tuned scenarios
| Cost line (5 years, USD) | Scenario A: untuned | Scenario B: tuned |
|---|---|---|
| Software license | $1.38M | $1.38M |
| Implementation | $0.35M | $0.35M |
| List and PEP data | $0.68M | $0.68M |
| Tuning and model validation | $0.20M | $0.50M |
| Internal IT and operations support | $0.50M | $0.50M |
| Analyst headcount | $11.25M | $4.80M |
| Total | $14.36M | $8.21M |
| License as share of total | 10% | 17% |
License, data and implementation cost the same in both scenarios. The $6.15 million gap comes almost entirely from alert volume: an extra $300,000 on tuning saves about $6.45 million in analyst time. All figures are hypothetical. Your ratio will depend on local salaries and your starting alert rate.
A point of false positives versus a pricier license
Here's the trade-off most buying committees miss. Holding everything else constant, this is what payment alert rates alone cost in analyst time at a blended $75,000 per FTE:
| Payment alert rate | Alerts per day | FTE (incl. Level 2 and QA) | Five-year analyst cost |
|---|---|---|---|
| 0.5% | 200 | 5.7 | $2.1M |
| 1% | 400 | 11.4 | $4.3M |
| 2% | 800 | 22.8 | $8.5M |
| 3% | 1,200 | 34.1 | $12.8M |
Each percentage point of payment alerts costs about $4.3 million over five years. Doubling the license from $250,000 to $500,000 a year costs about $1.4 million more. So a vendor twice as expensive pays for itself if, on your own data, it cuts the payment alert rate by about a third of a point without missing true matches. Put that comparison in front of the committee.
Red flags in sanctions screening quotes
- Uncapped volume pricing. Per-transaction fees with no ceiling penalize growth, and instant payments can multiply volumes quickly.
- Tuning only through vendor professional services. If your team can't change thresholds or good-guy rules in a controlled, auditable way, every adjustment becomes a change order.
- Black-box match scoring. You must be able to explain to an examiner why an alert fired or didn't. Opaque scoring makes model validation slower and costlier.
- Per-seat data licensing. If list data is priced per analyst seat, a high alert rate inflates your data bill as well as your headcount.
- No proof of value on your data. Demo results on vendor-curated test files say nothing about your false-positive rate.
- Vague list-update latency. Ask how many minutes pass between an official list publication and its deployment in screening, and get the answer into the SLA.
Run a proof of value before you sign
Before you shortlist on price, run a four-to-six-week proof of value with two or three vendors. Use the same anonymized sample: about three months of payment messages and a customer extract of at least 100,000 records. Seed it with known true matches so you can measure misses as well as noise. Score each vendor on alerts per thousand screened items, true matches caught and analyst minutes per alert. Then feed those figures into the model above with your own salary costs.
Decision rule: choose the option with the lowest five-year total at a miss rate your compliance officer and external advisers will sign off on. Where alert results are close, take the cheaper license. Where they aren't, the license fee shouldn't decide it.
Questions buyers ask
What does sanctions screening software typically cost for a mid-sized bank?
For a bank with around 2 million customers, annual subscriptions covering customer and payment screening commonly fall between $150,000 and $400,000, plus one-time implementation of roughly $200,000–$600,000. These are typical 2026 market ranges that vary by contract, region and volume, so confirm with vendors. Analyst costs over the contract term can exceed the license several times over.
Why pay for sanctions list data when official lists are free?
Official lists from bodies like OFAC, the UN, the EU and OFSI are free, but they aren't consolidated and are often light on identifiers. Commercial providers merge and de-duplicate many sources and add aliases, ownership links, PEP coverage and adverse media. Richer identifiers also reduce false positives, which cuts labor costs.
What is a realistic false-positive rate for payment screening?
It varies widely with payment corridors, data quality and configuration. Untuned systems can alert on low single-digit percentages of payments, while well-tuned systems with good secondary identifiers can run well under 1%. Measure it on your own data in a proof of value rather than relying on vendor claims.
Can we cut alert volume just by raising match thresholds?
Raising thresholds reduces alerts but increases the risk of missing true matches, which carries regulatory and legal exposure. Most supervisors expect documented testing, validation and governance for any threshold change. Work with your compliance function and qualified advisers, and test changes against seeded true matches before going live.
Do instant payment schemes change screening costs?
Yes. Real-time schemes need very fast screening responses and 24/7 alert coverage, which raises headcount needs for payment alerts. In the EU, the Instant Payments Regulation moves SEPA instant transfers toward regular customer screening rather than per-transaction checks, which shifts load to customer screening. Rules differ by jurisdiction, so confirm local requirements with counsel.
Written by the Vaultgridplus editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.