Choosing sanctions screening software
Most tools sold as "sanctions screening" screen names. If your exposure is in what you ship rather than who you ship to, that is the wrong category of product — and the distinction is not always obvious from the marketing.
First, work out which problem you have
The market divides into two categories that share a name:
- Party screening tools match counterparty names against consolidated designation lists. They are built around fuzzy matching, transliteration, alias handling and false-positive reduction. Banks and payment firms live here.
- Goods screening tools check product classification codes against the annexes of trade regulations. They are built around nomenclature, annex structure, derogations and change tracking. Exporters, manufacturers and freight operators live here.
Many compliance suites do the first well and the second barely at all — offering, at most, a static list of restricted codes with no annex mapping and no derogation logic. If you manufacture or move physical goods, you need both, and you should evaluate them as two separate purchases even if one vendor sells both.
What a goods screening tool must actually do
Screen at eight digits
If the tool works at six-digit HS level, it cannot be accurate, because EU annexes discriminate at eight. Ask to see a case where two codes under the same six-digit subheading are treated differently.
Cover every regime, not just Russia
Russia coverage is table stakes. Ask what happens with Belarus, Iran, Syria, Crimea, the non-government-controlled areas of Ukraine, anti-torture goods and the military list — and whether a code caught by several regimes returns several results or just the first one.
Return the legal basis, not a verdict
A red light is not usable output. You need the annex, the operative article, and the text — because the compliance decision, and the file that evidences it, are built on the provision rather than on the tool's conclusion. A tool that cannot show you why it flagged something cannot be audited.
Handle derogations, thresholds and wind-downs
This is where thin tools fail. Sanctions are full of conditional measures: authorisation requirements, value thresholds, pre-existing contract carve-outs, humanitarian exemptions, time-limited transitions. A tool that reduces all of this to "restricted / not restricted" will cause you to stop lawful shipments, which is a commercial cost that rarely gets attributed back to the tool.
Handle "ex" codes honestly
Where an annex covers only part of a code, the tool should say so and show the qualifying description, rather than reporting a clean match. Silently treating "ex" entries as full matches is a common shortcut.
Track changes and tell you
Annexes change package by package. A tool that gives a correct answer today and no notification when the answer changes has solved the easy half. Ask how quickly the dataset is updated after a package is published, and whether you can subscribe to alerts on the specific codes in your catalogue.
Take a catalogue, not one code at a time
Screening becomes real work at the point where you have thousands of codes. Bulk upload, structured export and a result format that can be attached to a compliance file are what make the difference between a demo and a control.
Give you a defensible record
The output should be exportable and should carry the dataset version and the date. That is what makes it evidence later.
Questions worth asking any vendor
- Do you screen goods, parties, or both — and if both, which one is the product you actually built?
- At what digit level is your matching performed?
- Which regulations are covered, and how are multi-regime hits presented?
- Do you return the annex and article, and can I see the source text?
- How do you represent derogations, thresholds and wind-down periods?
- How are "ex" entries handled?
- How long after a new package is published is the dataset updated, and how is that communicated?
- Can I screen a full catalogue, and export the results with a version stamp?
- Where is my data processed and stored, and is it retained?
- What exactly does the tool not decide — and does the vendor say so plainly?
That last question is a reasonable test of a vendor. Sanctions screening tools are decision-support aids: they narrow the question, surface the law and evidence the check. Any vendor implying their output is a legal determination is either misunderstanding the product or misrepresenting it.
Where data residency comes in
Your screening inputs are commercially sensitive — a catalogue of codes and destinations describes your business and your pipeline. Ask whether inputs are transmitted, logged or retained, and for how long. Architectures differ: TRADESANCTIONS.EU performs screening in the browser, so codes and catalogues are processed locally and are not stored against the account. Whatever tool you choose, get the answer in writing.
Build versus buy
A spreadsheet of restricted codes is cheap to build and expensive to own. The build cost is not the problem; the maintenance is — tracking every package, re-reading amended annexes, and keeping derogation logic current is continuous specialist work, and the failure mode is silent. Home-built lists tend to be accurate on the day they are made and progressively wrong afterwards, with no signal that this is happening. If you build, budget for the monitoring, and assign it to a named person.
If you are still defining the control itself rather than choosing a tool, start with the sanctions screening overview and the compliance checklist.
Frequently asked questions
- What is sanctions screening software?
- Sanctions screening software checks transactions against restrictive measures before they are executed. The market divides into party screening tools, which match counterparty names against designation lists, and goods screening tools, which check product classification codes against the annexes of trade regulations. Companies that move physical goods generally need both.
- What is the difference between goods screening and party screening software?
- Party screening tools are built around name matching — fuzzy logic, aliases, transliteration and false-positive reduction. Goods screening tools are built around classification nomenclature, annex structure, derogations and change tracking. They solve different problems and are usually best evaluated as separate purchases even when one vendor offers both.
- What should I look for in a goods sanctions screening tool?
- Screening at eight-digit CN level, coverage of every applicable regime rather than Russia alone, output that gives the annex and article rather than only a verdict, explicit handling of derogations, thresholds, wind-down periods and "ex" entries, prompt dataset updates with change alerts, bulk catalogue screening, and an exportable result carrying the dataset version and date.
- Can screening software replace legal advice?
- No. Screening tools are decision-support aids: they narrow the question, surface the applicable provision and evidence that a check was performed. Binding determinations come from the National Competent Authority or from qualified counsel, and the authentic legal text is the Official Journal as published and amended.