Screening searches a name against published sanctions and export-control lists. It takes seconds, it is repeatable, and it produces a hit or no hit against the lists as they stood on that day. Due diligence is a document about one company: its registration, who controls it, what it is registered to do, and what else is publicly recorded. One answers whether a name is on a list. The other answers who is on the other side of the deal.
A screening tool compares a string against a name list. It is fast and cheap enough to run on every counterparty, and it should be run again before significant payments, because the lists change continuously. What it cannot do is tell you whether a name that produced no hit is the company you think you are dealing with. Screening is blind to the difference between a real supplier and a shell that happens to use a clean name.
Due diligence starts from the entity, not from a list. It reads the registry for the legal name, the code, the status, the scope, the registered representatives and the ownership structure, and it records where each fact came from. Because it is tied to one company and one date, it does not transfer to a different company with a similar name, and it does not stay current by itself.
The most expensive confusion is treating a clean screening result as a due diligence result. A no-hit says nothing about whether the supplier is registered for your goods, whether the account you are paying belongs to the entity on the invoice, or whether the ownership has changed since you last looked.
| Sanctions screening | Due diligence | |
|---|---|---|
| Question it answers | Is this name on a published list | Who is this company, and what is publicly recorded about it |
| Input | A name, and any aliases you know | One named legal entity |
| Output | Matching list entries, or none | A short document with sources |
| How long it takes | Seconds | Hours to days, depending on the registry |
| Shelf life | The day it was run, and the lists change | The date it was made; ownership and status can change after it |
| What it cannot tell you | Whether this name belongs to the company you are dealing with | Whether a name appears on a list with no other public record |
| Run it when | Before onboarding and before payment runs | Before a first significant order, or when the counterparty changes |
In practice you run both, in this order: screen first, because it is free and instant, then assemble the entity facts for the counterparties that survive. If screening returns a hit, the entity work is what lets you clear it against identifiers rather than against a feeling.
If the only risk you care about is list exposure, yes. If you are about to pay money to a company you have never dealt with, a clean screening result does not tell you that the bank account belongs to the entity on the invoice.
That depends on your jurisdiction, your sector and your bank. Banks impose their own requirements on cross-border payments, and those are usually stricter than any general rule. We are not in a position to give you a legal answer.
Screen before onboarding and before payment runs in higher-risk corridors, because the lists move. Refresh a due-diligence document when the counterparty's details change, when ownership changes, or when the relationship changes size.