World-Check and PEP Status: How to Remove an Inaccurate Record and Rebuild Banks' Trust

Enhanced due diligence. A transaction freeze "pending further review." An account application declined without explanation. Three different phrasings, but in most cases, one and the same cause behind them: an automatic name match in the World-Check database. For the bank, it's a routine screening step. For the person or company on the other side, it's weeks or months of uncertainty — even when there may be no actual wrongdoing at all.

World-Check — now part of LSEG (London Stock Exchange Group), formerly a Refinitiv and Thomson Reuters product — isn't the only database of its kind, but it's the best known. Banks, payment providers, and audit and law firms around the world use it to screen counterparties for sanctions exposure, PEP status, and negative media coverage. This article explains how that screening works, why people end up in the database by mistake or unfairly, and what can actually be done — legally and reputationally — to get a record corrected or removed.

What World-Check Is, and Why It's Not a "Blacklist"

World-Check is a commercial screening database used in compliance checks (KYC — know your customer, AML — anti-money laundering). It aggregates three types of records from public sources: politically exposed person (PEP) status, matches against sanctions and watch lists from various jurisdictions, and adverse media coverage — everything from court proceedings to investigative journalism.

There's an important distinction worth understanding before doing anything: World-Check is a private database, not a government sanctions list. Being included in it carries no legal force, unlike, say, the U.S. Treasury's Office of Foreign Assets Control (OFAC) SDN list — an actual government sanctions decision. A World-Check entry is a flag for further review inside the bank, not a verdict. In practice, though, many compliance departments treat it as a straight-up signal to decline or freeze, without digging into the details, because that's cheaper than investigating it themselves.

Besides World-Check, banks and corporations use similar products — Dow Jones Risk & Compliance, LexisNexis WorldCompliance, and others. The logic for working with them and the grounds for disputing a record are similar, so the rest of this article covers World-Check and comparable databases together.

Who Ends Up in the Database, and Why

PEP status (Politically Exposed Person). There's no single international definition of a PEP — every jurisdiction interprets it differently, which is one of the main reasons for erroneous inclusions. The category typically covers current and former government officials, executives of state-owned enterprises, and senior judges, but regulators in different countries keep expanding the list of qualifying positions. A separate category is "relatives or close associates" (RCA): family members or business partners of a PEP who never held a public position themselves but get the same status purely on the formal basis of the relationship.

How long the status remains in effect isn't universal either. In the UK, for example, the requirement to keep applying enhanced scrutiny to a former PEP lasts at least 12 months after they leave office, and that period can be extended if elevated risk persists — meaning the mere passage of a calendar deadline doesn't guarantee automatic removal of the status anywhere.

Sanctions and watch lists. This is where false positives are most common — a name matching someone on a sanctions list with no actual connection to that person. The problem gets worse when a name is transliterated from Cyrillic or another alphabet: the same person can appear in 3-4 different Latin-alphabet spellings across various databases and media outlets, and some of those spellings happen to coincide with the names of people in actual cases.

Adverse media. This category picks up mentions in court records, news articles, and trade-press posts, regardless of how a case ended. A case dismissed for lack of evidence five years ago keeps getting indexed and aggregated exactly the same way as an active investigation.

Why This Costs More Than It Looks Like

Formally, a World-Check entry is just data. In practice, it directly affects three situations.

Opening and maintaining a bank account. At the slightest match, a bank's compliance department launches enhanced due diligence, which can drag on for months and still end in a refusal with no explanation given — that's the bank's right in most jurisdictions.

Visas, residency permits, citizenship by investment. Consular and immigration authorities increasingly use commercial adverse-media databases as part of applicant vetting; a World-Check entry is a common reason for requests for additional documents or outright refusal.

Deal due diligence. Buyer-side lawyers and investment committees include checks against these databases as a standard checklist item; an unexplained match can lower a company's valuation or derail a deal at the final stage.

In one AEGIS Reputation Lab project, it was precisely a cluster of inaccurate public-domain publications that led foreign banks to freeze a client's accounts under standard adverse media screening — clearing the search results and working with sources took eight months, partly because some publications got re-syndicated again in the middle of the project.

Case Study · Anonymized under NDA A Clean Search Presence in 4 Countries in 8 Months This is the very project referenced above — clearing search results after accounts were frozen due to adverse media screening. Read the case study →

Legal Grounds for Correcting a Record

Because the company that operates World-Check is registered in the UK (LSEG), data processing falls under UK GDPR, and for EU residents, the EU's General Data Protection Regulation applies as well. Formally, this holds regardless of the data subject's citizenship or country of residence: what matters is that the database operator processes personal data under UK or EU jurisdiction. In practice, that doesn't turn the process into a rubber stamp, but it does provide concrete levers:

• Right of access (SAR, Subject Access Request) — a request for what data the database holds about a person; the operator must respond within 30 days.
• Right to rectification (Art. 16) — if the data is factually inaccurate or out of date.
• Right to erasure, the "right to be forgotten" (Art. 17) — applicable not in every case, but where processing is no longer justified by its original purpose or the data is being processed unlawfully.
• Right to object (Art. 21) — to further processing, if the person can show that their specific situation makes the processing disproportionate.

An important caveat: a private database isn't obligated to grant a request on first demand — the decision rests with the operator, and if it's refused, the next step is a complaint to the regulator (in the UK, that's the ICO). A realistic strategy is therefore built not on a single letter, but on an evidence package and, if needed, escalation.

What to Do When PEP Status Was Formally Assigned Correctly

Not every case is a mistake. If a person genuinely holds, or recently held, a government position that meets PEP criteria in a given jurisdiction, disputing the status itself is pointless and counterproductive: an aggressive attempt to "remove" a legitimately assigned status will likely be rejected and add a record of the attempt itself. In that situation, the task shifts from removal to managing the risks the status creates in practice.

A different toolkit applies here: proactively disclosing the status to the bank instead of letting it surface during an automated check; preparing documentation that explains the source of wealth and the nature of the position (source of wealth / source of funds); and systematic work on the digital profile, so that alongside the PEP status, public sources show current, verifiable information about ongoing activity, not just a position held years ago.

The Step-by-Step Process: Five Stages of Working a Record

1. Audit the record and the digital profile. Before disputing anything, you need to know exactly what the compliance system sees. That's done through a SAR request to the database itself and a parallel audit of public sources — search results across every language version of the name, court records, media mentions.

2. Legal analysis of the grounds. Each entry is classified individually: factual error (wrong person), outdated data (PEP status expired, case closed), disproportionality (the mention exists but doesn't reflect current status or scale), or a GDPR violation in processing. This classification determines which tool applies — rectification, erasure, or objection.

3. Work on the digital profile. Alongside the legal track, it's worth updating public sources: publishing current information about ongoing activity, pushing outdated material out of the top results. Compliance officers and database-enrichment algorithms regularly pull data from the open internet, so a clean picture in search improves the odds of a favorable decision on the formal request.

4. Preparing and filing the official request. A document package — including supporting materials, a legal opinion where needed, and direct references to the inaccuracies — is submitted to World-Check or a comparable database, clearly stating what needs correcting and on what grounds.

5. Review, escalation, monitoring. The operator reviews the request on its own timeline; if refused, the next step is a complaint to the regulator. The work doesn't end once a correction succeeds: databases are regularly refreshed from the same sources, so ongoing monitoring is needed to keep the corrected record from reappearing.

How Long This Actually Takes

No agency and no lawyer specializing in these disputes can give exact timing guarantees — too much depends on the specific database, jurisdiction, and nature of the record. But for typical scenarios, these ranges are a reasonable guide:

• Technical error or name match — usually the fastest case, 3–6 weeks: confirming it's a different person is generally enough.
• Outdated record or expired PEP status — 6–12 weeks, when the grounds are backed by documentation (the date of leaving office, a case-closure decision).
• Disputed classification or a disproportionate media mention — 2–4 months: requires legal analysis of proportionality and often parallel work with sources.
• A complex case spanning multiple jurisdictions — 6 months to a year, especially when the information is duplicated across countries and languages, as in the AEGIS case above.

The operator typically registers the first technical changes within a few weeks of filing, but a durable result on a multilingual record spanning several countries is a matter of months, not days.

Why a Single Legal Request Is Often Not Enough

A formal request to World-Check solves the problem inside that database. But as we covered in our article on the digital profile and international compliance, a compliance officer, a consul, or a deal partner in practice checks more than just specialized databases — they also check ordinary search results and AI overviews. If, after a successful correction to the World-Check record, an outdated or inaccurate publication that originally triggered the entry still sits at the top of Google or Yandex, the risk still looks unresolved to the bank or partner, even though the database itself has technically been updated.

That's why systematic work almost always combines the legal track described above with SEO reputation suppression of outdated content in search results — we break down the methodology for that process in our article on how to push negative content out of Google and Yandex.

Common Mistakes

• Waiting until the bank says no. By the time an account is already frozen, some tools work more slowly — a preventive audit ahead of a deal or banking procedure is almost always more effective than a reactive one.
• Confusing World-Check with a government sanctions list. Demanding that World-Check "lift sanctions" is formally meaningless — the database doesn't impose sanctions, it aggregates information; the correct framing for a request is about factual inaccuracy, outdated status, or disproportionality in the record.
• Relying on a legal request alone, without digital-profile work. If the public sources that triggered the entry stay at the top of search results, the database can pull the same information back in during its next automatic update.
• Working with only one language version of the name. It's common in international business for the problematic record to exist under one transliteration while the audit only covers another — leaving the risk unnoticed until the next check abroad.

Frequently Asked Questions

What to Do Next

If a bank has requested additional documents with no clear reason, frozen transactions, or declined to open an account — or if a deal, visa, or residency application is coming up and there's reason to believe a compliance database may hold an inaccurate record — the right place to start is an audit. It will show exactly what banks and partners see, which entries can be corrected legally, and which require digital-profile work.

AEGIS Reputation Lab conducts these audits confidentially, works with records in World-Check, Dow Jones, and comparable databases across Tier 1-3 jurisdictions, and builds a strategy around the specific goal. Get in touch to discuss your situation.

Service World-Check Removal & PEP Status Correction Discuss →

See Also

Counterparty Screening

Your Company in Business Data Brokers: What Partners See in Your D&B Report

Read the article → Anonymized under NDA

Case Study: A Clean Search Presence in 4 Countries in 8 Months — an SEO Reputation Project for a C-Suite Executive

Read the case study → Compliance

Digital Profile and International Compliance: How Online Reputation Affects Bank Accounts, Visas, and Deals Abroad

Read the article → SEO Reputation

SEO Reputation Management: How to Push Negative Content Out of Google and Yandex

Read the article → Anonymized under NDA

The Investor Who Googled and Walked Away: Synchronizing Search Results Across 3 Countries in 7 Months

Read the case study → Deindexing

Right to Be Forgotten: How to Legally Remove Links From Google and Yandex

Read the article →

Show more