getregdata
Home / Blog / Article
Article · 2026-11-01

How to Screen a Company for Sanctions (OFAC, EU, UN, UK) and Adverse Media

kyc · aml · sanctions · adverse-media · compliance · 11 min read

To screen a company automatically, run two independent checks on every name. First, match it against the primary sanctions lists: OFAC SDN and Consolidated, the UN Security Council Consolidated List, the EU Consolidated Financial Sanctions List and the UK Sanctions List. Second, search news and the open web for negative coverage, keeping only stories in which the company is the wrongdoer. The Adverse Media & Sanctions Screener on Apify does both for a list of names and returns one JSON record per name, with a risk level, the list matches split into confirmed and possible, and a source trail for every news hit.

A result from any screening tool is input for a compliance decision, not the decision itself. The rest of this guide explains what each list covers, how to read the output, and where automated screening stops.

What you are screening against

Sanctions lists are official registers of people, companies, vessels and organisations subject to asset freezes and other restrictive measures. Each issuing authority publishes its own list:

ListPublished byNotes
OFAC SDN (Specially Designated Nationals)US Treasury, Office of Foreign Assets ControlThe main US blocking list.
OFAC Consolidated (non-SDN)US Treasury, OFACNarrower US programmes, such as sectoral sanctions.
UN Security Council Consolidated ListUnited Nations Security CouncilDesignations under Security Council sanctions regimes.
EU Consolidated Financial Sanctions ListEuropean CommissionPersons and entities subject to EU financial sanctions.
UK Sanctions ListForeign, Commonwealth & Development Office (FCDO)Since OFSI’s Consolidated List closed on 28 January 2026, the only source for UK designations.

Which lists you must check depends on where you operate and whose currency and banks you touch. An EU firm is bound by EU sanctions, a UK firm by UK sanctions, and anyone dealing in US dollars or with US persons usually has to take OFAC into account as well.

Adverse media (negative news) means public reporting that links a party to financial crime, fraud, corruption, sanctions evasion, money laundering, terrorism, organised crime, regulatory enforcement, serious litigation or environmental harm. There is no official list of it. Adverse media screening is part of risk-based customer due diligence, and especially of enhanced due diligence, and it catches what lists do not: a supplier under investigation, a director charged with fraud, a company that has settled a bribery case.

The manual way

For one name, the official tools are free:

  1. Search the OFAC Sanctions List Search. It covers the SDN list and OFAC’s other lists.
  2. Search the UK Sanctions List search tool.
  3. Search the EU list, either through the European Commission’s financial sanctions files or the EU Sanctions Map.
  4. Search the UN Security Council Consolidated List on the Security Council’s website.
  5. Run news and web searches on the name combined with terms such as fraud, investigation, bribery, money laundering and sanctions. Read each result and decide whether it is the same company and whether the company is the accused or just mentioned.
  6. Save screenshots or notes as evidence of what you checked and when.

That works for an occasional counterparty. It stops working when you onboard dozens of customers a week or need to re-screen a whole book. Each name then means five list searches with different matching rules, a news read that takes real time, and evidence filed by hand. Step 5 is also where manual screening is weakest. A keyword search for “Acme Corp lawsuit” returns every case where Acme is the plaintiff, and a common name returns every namesake.

The automated way: names in, a triaged record out

The Adverse Media & Sanctions Screener needs only an Apify account. You do not need your own list subscriptions or keys. The registry page at /registries/cross-border/adverse-media-screener/ lists every output field.

For each name, the actor runs two checks:

  • It matches the name against the five lists above, downloaded from the issuing authorities and refreshed daily. This check does not depend on anyone having written about the party.
  • It screens published news and web coverage. For each article it records the risk category, the screened entity’s role (perpetrator, plaintiff, victim, regulator, merely mentioned), the severity, and how confident it is that the article concerns the same entity. Only hits where the entity is the wrongdoer, the match is confident and your filters are met are kept.

The two halves are independent. A designated party with no press coverage is still a list match, and clean news never lowers a list match.

Input

{
  "entityNames": ["Wirecard AG", "JSC BIOGRAD"],
  "entityType": "company",
  "country": "de",
  "minSeverity": "medium",
  "maxHits": 25
}
ParameterMeaning
entityNamesRequired, at least one. Each name is screened, returned and billed separately.
entityTypeauto, person or company. Helps disambiguation.
aliasesOther spellings or transliterations. Only meaningful when you screen one entity per run.
countryISO code or country name. Biases the news search and helps with name matching.
categoriesReturn only these risk categories, for example ["sanctions", "money_laundering"].
minSeveritylow (default), medium or high.
maxHitsMaximum adverse hits returned per entity, 1-50 (default 25).

Risk categories: financial_crime, fraud, corruption_bribery, sanctions, money_laundering, terrorism, organized_crime, regulatory_enforcement, litigation, environmental, other.

Output: a company with adverse media and no list match

Trimmed: the real record lists all five lists in listsChecked.

{
  "entityName": "Wirecard AG",
  "overallRisk": "high",
  "adverseHitCount": 6,
  "categoriesFound": ["fraud", "financial_crime", "money_laundering"],
  "hits": [
    {
      "title": "Wirecard Investors Drop Fraud Case ...",
      "url": "https://...",
      "source": "bloomberglaw.com",
      "publishedDate": "Nov 10, 2025",
      "snippet": "Wirecard invented fictional escrow accounts worth about $2 billion ...",
      "riskCategory": "fraud",
      "severity": "high",
      "entityRole": "perpetrator",
      "entityMatchConfidence": "high",
      "reason": "Wirecard AG is accused of inventing fictional escrow accounts."
    }
  ],
  "sanctionsListStatus": "no-match",
  "listMatches": [],
  "possibleListMatches": [],
  "listsChecked": [
    { "list": "OFAC-SDN", "status": "ok", "retrievedAt": "2026-07-28T...", "entryCount": 19157 },
    { "list": "OFAC-CONS", "status": "ok", "retrievedAt": "2026-07-28T...", "entryCount": 481 }
  ],
  "screenedAt": "2026-07-28T...",
  "disclaimer": "..."
}

Output: a designated entity

{
  "entityName": "JSC BIOGRAD",
  "overallRisk": "high",
  "sanctionsListStatus": "confirmed",
  "listMatches": [
    {
      "list": "OFAC-SDN",
      "listName": "OFAC Specially Designated Nationals (SDN)",
      "entryId": "48544",
      "listedName": "JSC BIOGRAD",
      "matchedName": "JSC BIOGRAD",
      "matchedOn": "primary",
      "entryType": "entity",
      "programs": ["RUSSIA-EO14024"],
      "countries": ["Russia"],
      "datesOfBirth": [],
      "why": "Exact match on the listed name."
    }
  ]
}

The listMatches entry stands on its own: no news coverage was needed to produce it.

How to read the result

Confirmed vs possible list matches

A name is not an identity, so list matches come in two tiers.

  • listMatches (confirmed) - the name matches a listed name or one of its strong aliases exactly, after case, accents and punctuation are normalised. This is a fact about the register: this name appears on this list as this entry. It is still not proof that your counterparty is that party. Check the countries, datesOfBirth and entryId against what you know: registration number, address, incorporation country, directors.
  • possibleListMatches (possible) - surfaced for a person to judge, not asserted. Three cases land here: matches on weak aliases, short personal names, and the same name parts in a different order. Weak aliases are the abbreviations and fragments the lists grade as low quality. BNC, for example, is a weak alias of Banco Nacional de Cuba, and treating it as a hit would flag every firm with those initials. Short personal names collide often, so they stay here unless the country you supplied matches the entry.

A confirmed match always sets overallRisk to high. A possible match sets it to at least medium. Clean media cannot lower either.

sanctionsListStatus

ValueMeaning
confirmedAt least one confirmed match.
possibleNo confirmed match, at least one possible match to review.
no-matchEvery list was checked, fresh, and nothing matched.
incompleteNothing matched, but at least one list was unavailable or more than seven days old, so the miss does not prove anything.
unavailableThe lists could not be loaded for this run. No sanctions screen happened.

listsChecked shows, per list, whether it was ok, stale or unavailable, when it was retrieved and how many entries it had. Keep it with the record as your evidence of what was screened.

screeningStatus and overallRisk

screeningStatus describes the media half:

  • complete - the whole news and web sweep ran. Only here can overallRisk be clear.
  • partial - some searches failed. The hits are real, but missing hits mean nothing. searchesRun / searchesTotal show how much ran.
  • unavailable - the media sweep did not run. The row carries the full sanctions result and a disclaimer saying no media screen was performed. Re-run the name to get the media half.

overallRisk is clear, low, medium, high or unknown. It is the worst media severity found, raised to the floor set by any list match. unknown is not a pass. It means part of the screen could not be run, and the right action is to re-run, not to onboard. A clear result is only produced when the full media sweep completed and every list was fresh. Even then it means “nothing found by this screen”, not “approved”.

Code

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });

const run = await client.actor('regdata/adverse-media-screener').call({
  entityNames: ['Wirecard AG', 'JSC BIOGRAD'],
  entityType: 'company',
  minSeverity: 'medium',
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
for (const r of items) {
  const review = r.overallRisk !== 'clear' || r.sanctionsListStatus !== 'no-match';
  console.log(r.entityName, r.overallRisk, r.sanctionsListStatus, review ? 'REVIEW' : 'no findings');
}

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])

run = client.actor("regdata/adverse-media-screener").call(
    run_input={"entityNames": ["Wirecard AG", "JSC BIOGRAD"], "entityType": "company"}
)

for r in client.dataset(run["defaultDatasetId"]).iterate_items():
    for m in r.get("listMatches", []):
        print(r["entityName"], "CONFIRMED", m["list"], m["entryId"], m["programs"])
    for m in r.get("possibleListMatches", []):
        print(r["entityName"], "possible", m["list"], m["entryId"], m["why"])
    for h in r.get("hits", []):
        print(r["entityName"], h["severity"], h["riskCategory"], h["url"])

A worked workflow: onboarding plus monthly re-screening

  1. At onboarding, screen the company name and the names of its directors and beneficial owners in one run. For Polish companies, get the owners from the CRBR beneficial owners register first. The Poland KYB Risk Check runs registry identity, owners and insolvency in one call.
  2. Route by result. high or any listMatches goes to a compliance analyst. possibleListMatches goes to a reviewer who compares dates of birth, countries and registration details. unknown or screeningStatus: partial is queued for an automatic re-run. clear with no-match is filed with the record.
  3. Keep the evidence. Store the full JSON, including listsChecked, screenedAt, every hit’s url and reason, and the disclaimer. That shows what was checked, against which list versions, and when.
  4. Re-screen the book. Save the customer list as an Apify task and schedule it monthly, or more often for high-risk customers. Lists change daily, so a customer who was clean at onboarding can be designated later. Compare each run with the last and alert only on changes: a new list match, a new high-severity hit, or a risk level that went up.
  5. Wire it in. Apify integrations send results to a webhook, n8n, Make or Zapier. In n8n, use the official Apify community node to run the task and a Switch node on overallRisk and sanctionsListStatus.

Limits and gotchas

  • Coverage is five lists. OFAC SDN, OFAC Consolidated, UN, EU and UK. Other national regimes (Switzerland, Canada, Australia and others) and PEP (politically exposed persons) data are not checked. If your obligations include them, add a dedicated provider.
  • Ownership is not in the name. Under OFAC’s 50 Percent Rule, an entity owned 50% or more, in aggregate, by blocked persons is itself blocked even if it is not on the list. The EU and UK apply similar ownership and control tests. A name screen of the company alone will not catch this. Screen the beneficial owners and parent companies too.
  • A name match is not an identification. Confirm identity on a date of birth, a registration number or a country before you act on any match. The reverse also holds: transliteration and spelling differences can hide a listed party, so pass known aliases when you screen a single entity.
  • Adverse media is reporting, not findings. Hits are mentions attributed to their sources for analyst review. They are not verified allegations or legal determinations. Coverage is public open-web news and search, so paywalled databases, court dockets and local-language press that is not indexed are not guaranteed to appear.
  • Severity filters cut both ways. minSeverity: "high" reduces review load and can hide a medium-severity enforcement story you would want to see. Start with the default and tighten only once you know your false-positive rate.
  • Not a consumer report. Do not use the output for decisions covered by the US FCRA, such as employment or consumer credit.
  • Personal data. Screening named individuals is processing personal data. Under GDPR you are the controller and need a lawful basis. For AML-regulated firms that is usually the legal obligation to perform due diligence.

Pricing

Pay per entity screened: from $0.095 per entity plus $0.01 per run start. Search and classification are included. A row is charged when at least one half of the screen ran. If neither the list check nor the media sweep ran for a name, no row is written and nothing is charged. Current prices are on the Store page.

FAQ

Which sanctions lists does it check?

OFAC SDN, OFAC Consolidated (non-SDN), the UN Security Council Consolidated List, the EU Consolidated Financial Sanctions List and the UK Sanctions List published by the FCDO. It does not check PEP data or other national lists.

Does “clear” mean the company passed compliance?

No. It means the full media sweep ran, every list was fresh, and nothing met your filters. The compliance decision, including ownership and identity checks, remains yours.

What is the difference between a confirmed and a possible match?

A confirmed match is an exact match on a listed name or a strong alias. A possible match rests on a weak alias, a short personal name or reordered name parts, and it needs a person to adjudicate it.

Why did I get “unknown”?

Part of the screen could not be completed: a list was unavailable or older than seven days, or the media sweep did not finish. Re-run the name. Do not read unknown as clean.

Can it screen people as well as companies?

Yes. Set entityType to person and add country where you know it. A matching country can promote a short-name list match from possible to confirmed.

How often should I re-screen?

As often as your risk assessment requires. Lists change without notice, so a customer who was clean at onboarding can be designated later. A scheduled Apify task makes weekly or monthly re-screening of the whole book routine.


Turn this into working data. Browse the registries and use cases, or start free on Apify.