Enhanced due diligence. Funds frozen "pending review." An account application declined with no explanation. Three different phrases, and in most cases, one underlying cause: an automated name match in the World-Check database. For a bank, this is a routine screening step. For the person or company on the other end, it can mean weeks or months of uncertainty — even when there is no actual wrongdoing behind the match.

World-Check, now part of LSEG (London Stock Exchange Group) and previously a Refinitiv and Thomson Reuters product, isn't the only database of its kind, but it is the best known. Banks, payment providers, auditors, and law firms worldwide use it to screen counterparties against sanctions lists, PEP status, and adverse media. This article explains how that screening actually works, why people and companies end up flagged by mistake or unfairly, and what can realistically be done — legally and reputationally — to get a record corrected or removed.

World-Check is a commercial screening database built for KYC (know your customer) and AML (anti-money laundering) compliance. It aggregates three categories of records from open sources: politically exposed person (PEP) status, matches against sanctions and watchlists across multiple jurisdictions, and adverse media — everything from court filings to investigative journalism.

One distinction is worth understanding before taking any action: World-Check is a private database, not a government sanctions list. Being listed carries no legal force on its own — unlike, for example, the U.S. Treasury's OFAC Specially Designated Nationals (SDN) list, which is a binding government sanction. A World-Check entry is a flag for further internal review, not a verdict. In practice, though, many compliance teams treat a hit as grounds to decline or freeze first and ask questions later, simply because that's the cheaper, lower-risk path for them.

Alongside World-Check, banks and corporations rely on comparable products — Dow Jones Risk & Compliance, LexisNexis WorldCompliance, and others. The logic for disputing a record, and the grounds available for doing so, are similar across these databases, so this article applies to World-Check and its close equivalents alike.

PEP status. There is no single, universal definition of a politically exposed person — each jurisdiction interprets it differently, and that inconsistency is one of the main sources of misclassification. Typically the category covers current and former senior government officials, heads of state-owned enterprises, and senior judges, but individual regulators keep expanding the list of qualifying roles. A separate category — relatives and close associates (RCAs) — covers family members and business partners of a PEP who never held public office themselves but inherit the same status by association.

The duration of PEP status isn't universal either. In the UK, for instance, a former PEP must still be treated as one for at least 12 months after leaving office, and that period can be extended if elevated risk remains — meaning the calendar alone rarely guarantees an automatic removal anywhere.

Sanctions and watchlist matches. These are dominated by false positives — a name coincidentally matching someone on a sanctions list with no actual connection between the two people. The problem is worse for names transliterated from Cyrillic, Arabic, or Chinese scripts: the same person can appear in three or four different Latin spellings across databases and media, and one of those variants may happen to overlap with an actual listed individual.

Adverse media. This bucket covers court records, news coverage, and trade-press mentions, regardless of how the underlying matter was resolved. A case dismissed for lack of evidence five years ago continues to be indexed and aggregated exactly like an active investigation.

On paper, a World-Check entry is just a data point. In practice, it shapes three outcomes directly.

Opening or keeping a bank account. Any match triggers enhanced due diligence, a process that can run for months and end in a decline with no explanation — which is the bank's prerogative in most jurisdictions.

Visas, residency, and citizenship by investment. Consular and immigration authorities increasingly draw on the same commercial adverse-media databases as part of applicant screening; a World-Check hit is a common reason for a request for further documents or an outright refusal.

Deal due diligence. Buyer-side counsel and investment committees run this kind of screening as a standard checklist item; an unexplained match can lower a company's valuation or derail a transaction at the final stage.

In one AEGIS Reputation Lab project, a cluster of inaccurate public articles was what triggered banks in several countries to freeze a client's accounts under a standard adverse media screening procedure — clearing the record and the underlying sources took eight months, largely because part of the content was re-published by new outlets partway through the project. The full story is in the case study "Clean Search Results in 4 Countries Within 8 Months."

Because the company behind World-Check (LSEG) is incorporated in the UK, its data processing falls under UK GDPR, and EU residents' data is separately covered by the EU GDPR. Applicability turns on where the database operator processes the data, not on the data subject's nationality or country of residence — which means the framework applies formally even to applicants outside the UK and EU. That doesn't make the process automatic, but it does provide concrete levers:

• Right of access (Subject Access Request, SAR) — a request for exactly what data the database holds; the operator must respond within 30 days.

• Right to rectification (Art. 16) — where the data is factually inaccurate or outdated.

• Right to erasure, the "right to be forgotten" (Art. 17) — applicable in specific circumstances, where processing is no longer justified by its original purpose or is unlawful.

• Right to object (Art. 21) — to further processing, where the individual can show their particular situation makes it disproportionate.

One caveat matters here: a private database is not obliged to comply with the first request it receives — the decision sits with the operator, and if it declines, the next step is a complaint to the relevant regulator (the ICO in the UK). A realistic strategy is built on an evidence package, not a single letter, with escalation built in from the start.

Not every case is a mistake. If someone genuinely holds, or recently held, a government role that meets the criteria for PEP status in a given jurisdiction, disputing the status itself is pointless and can backfire — an aggressive attempt to have a legitimately assigned status removed is likely to be declined and simply adds a record of the attempt itself. In that situation, the goal shifts from removal to managing the practical risk the status creates.

That calls for a different toolkit: proactively disclosing the status to a bank rather than letting it surface during an automated check; preparing documentation on source of wealth and source of funds that explains the income and the nature of the role; and systematically maintaining a digital profile so that, alongside the PEP status, open sources show current, verifiable information about present-day activity rather than only a years-old title. Compliance teams don't react to PEP status itself — thousands of legitimate clients worldwide carry it — they react to opacity, and to a mismatch between the official status and what a quick search actually shows.

Before disputing anything, you need to know exactly what the compliance system sees. That means filing a SAR with the database itself, in parallel with an audit of open sources — search results across every language version of the name, court databases, and media mentions.

Each flagged item is classified separately: a factual error (wrong person), outdated information (an expired PEP term, a closed case), disproportionality (a mention exists but no longer reflects current status or significance), or a GDPR processing violation. This classification determines which tool applies — correction, deletion, or an objection.

In parallel with the legal track, it's worth updating the open sources that fed the original listing — publishing current, verifiable information and displacing outdated material from top search results. Compliance officers and the automated enrichment processes behind these databases regularly pull fresh data from the open internet, so a clean search profile improves the odds of a favorable decision on the formal request.

A documentation package — supporting evidence, a legal opinion where relevant, and precise references to the inaccuracies — goes to World-Check or the equivalent database, with a clear statement of what needs correcting and on what grounds.

The operator reviews the request on its own timeline; a decline is followed by a regulatory complaint. The work doesn't end at a successful correction — these databases are refreshed continuously from the same open sources, so ongoing monitoring is what keeps a corrected record from reappearing.

No agency and no lawyer specializing in these disputes can guarantee a timeline — too much depends on the specific database, jurisdiction, and nature of the record. But by scenario type, realistic ranges look like this:

• Factual error or name clash — usually the fastest case, 3–6 weeks: confirming it's a different person is often enough.

• Outdated record or expired PEP term — 6–12 weeks, when the grounds are documented (a departure date, a case-closure ruling).

• Disputed classification or disproportionate media coverage — 2–4 months: this requires a proportionality analysis and often parallel work on the underlying sources.

• Complex multi-jurisdiction cases — six months to a year, especially when the same information has been duplicated across several countries and languages, as in the AEGIS case above.

Operators typically log the first technical changes within a few weeks of submission, but a durable result on a multilingual or multi-country record is a matter of months, not days.

A formal request to World-Check resolves the problem inside that specific database. But a compliance officer, a consular officer, or a deal counterparty — as covered in "Digital Profile and International Compliance" — checks more than specialized databases in practice; they also check plain search results and AI-generated summaries. If the outdated or inaccurate publication that originally triggered the listing still ranks at the top of Google after the database record is corrected, the risk still looks unresolved to whoever is checking, even though the underlying database has technically been updated.

That's why systematic work almost always combines the legal track described above with SERM — displacing outdated content from search results — a process covered in detail in "SERM: How to Push Negative Information Out of Google and Yandex Rankings."

By the time an account is frozen, some tools work less effectively — a preventive audit ahead of a transaction or banking procedure is consistently more effective than a reactive one.

Asking World-Check to "lift sanctions" is a category error — the database doesn't impose sanctions, it aggregates information. The correct framing for a request is factual inaccuracy, obsolescence, or disproportionality.

If the public sources that triggered the listing remain at the top of search results, the database can pull the same information back in during its next automated refresh.

International businesses commonly discover that a problematic record exists under one transliteration while the audit only covered another — leaving the risk unaddressed until the next check abroad surfaces it.

If a bank has requested extra documents with no clear reason, frozen a transaction, or declined to open an account — or if a deal, visa, or residency application is coming up and there's reason to think a compliance database may hold an inaccurate record — the starting point is an audit. It shows exactly what banks and counterparties see, which entries can be corrected through legal channels, and which need parallel digital-profile work.

AEGIS Reputation Lab runs these audits confidentially, works directly with World-Check, Dow Jones, and comparable databases across Tier 1–3 jurisdictions, and builds a strategy around the specific goal at hand. Contact us to discuss your situation.