Verkflo is in early access. Book a demo

Automate PEP and adverse media screening reviews

The agent takes each hit from ComplyAdvantage, compares it with what the customer file says, summarizes the articles against your categories and hands the evidence to a reviewer.

Book a demoSee how it runs

Works with

and any system with an API via Custom REST

What is PEP and adverse media screening?

  • The procedure

    PEP screening finds customers who hold or held a prominent public role. Adverse media screening finds news linking a customer to financial crime or other risks your policy lists. Both return many hits on common names, so each review asks two questions: is this the customer, and does it matter under your policy?

  • What the agent does

    • Pulls each hit and its sources from ComplyAdvantage

    • Compares name, date of birth and country with the customer file in Sumsub

    • Summarizes each article and matches it to your adverse media categories

    • Re-screens the customer list when the PEP list refreshes

  • What your team decides

    • Whether a PEP hit is the customer

    • Whether an article is relevant under your policy

    • Moving a customer to enhanced due diligence

    • Whether to keep the relationship, with your MLRO or compliance officer

Example runs for screening analysts, MLROs or compliance officers

Sample data

PEP Review Agent

Reviews screening hits against the customer file and your procedure.

  • ComplyAdvantage
  • Sumsub
  • +1

Trigger: Inbound webhook · screening hit

From a procedure PEP review · v1.1

Lena

Review the PEP hit on the director of Halden Trading.

PEP Review Agent

  1. Pulled the hit and its sources from ComplyAdvantage
  2. Pulled the director's date of birth and nationality from Sumsub
  3. Compared name, date of birth and country with the hit: identifiers agree
  4. Asked a reviewer, because a likely PEP match needs a person Waiting for a reviewerTom: confirmed PEP, enhanced due diligence per procedure
  5. Recorded the decision and set the customer to enhanced review

Confirmed after review. Tom confirmed the hit, and the customer moved to enhanced review under your procedure.

5 steps · 1 review

PEP Review Agent

Reviews screening hits against the customer file and your procedure.

  • ComplyAdvantage
  • Google Drive
  • +1

Trigger: Inbound webhook · screening hit

From a procedure PEP review · v1.1

Diego

Review the adverse media hits on Ostrava Metals.

PEP Review Agent

  1. Pulled 3 articles linked to the company from ComplyAdvantage
  2. Summarized each article and matched it to your adverse media categories
  3. One article concerns the company's former director, not the current one
  4. Flagged the relevant article for a reviewer Waiting for a reviewerPriya: relevant, request an explanation from the customer
  5. Saved the summaries and the reviewer's note to the case folder

Referred for follow-up. Priya found one article relevant and wants an explanation from the customer. The evidence pack is in the case folder.

5 steps · 1 review

PEP Review Agent

Reviews screening hits against the customer file and your procedure.

  • ComplyAdvantage
  • +1

Trigger: Daily at 06:00 · refreshed PEP list

From a procedure PEP review · v1.1

Marcus

Re-screen the refreshed PEP list and report changes.

PEP Review Agent

  1. Re-screened the customers on the list in ComplyAdvantage
  2. Compared each result with the previous review
  3. No new or changed hits since the last review screening.new_hits == 0
  4. Logged the re-screen against each customer file

No change. Nothing new to review. Each customer file shows the re-screen and the procedure version used.

4 steps · 0 reviews

Setting up the PEP Review Agent

Connect your systems

Pull hits and sources from ComplyAdvantage, compare them with the applicant record in Sumsub, keep evidence packs in Google Drive, and reach other systems through Custom REST.

  • ComplyAdvantage
  • Sumsub
  • Google Drive
  • Custom REST

Write the rules

Your hit-handling rules are CEL conditions. A PEP hit or a relevant article sends the case to a reviewer.

Sample data
pep.hits > 0 || media.relevant_articles > 0Ask a reviewer
screening.new_hits == 0Log and continue
review.decision == "confirmed_pep"Enhanced review

Add reviewers where the procedure says

The reviewer gets the hit, the file data and the comparison side by side, and makes the call your procedure leaves to a person.

Sample data

Review requested: Halden Trading

Reason
Possible PEP match on a director
Rule
pep.hits > 0
Procedure
PEP review · v1.1

Not a matchConfirm and escalate

Start it from the event

A screening hit from ComplyAdvantage starts a review through a webhook. A daily schedule re-screens the refreshed PEP list, and a reviewed Sumsub applicant can start one too.

  • Inbound webhook · screening hit
  • Daily at 06:00 · re-screen list
  • Sumsub · applicantReviewed

Version and evaluate

Test each version on a likely PEP, a false hit on a common name and an article about a former director. Publishing waits until each scenario passes.

Sample data

PEP review · v1.1Published

12/12 scenarios passed

PEP review · v1.2 Superseded

PEP review · v1.1 Superseded

Share with the team

Screening analysts review hits, an Author keeps your adverse media categories current, and the Auditor role gives read-only access to each comparison and decision.

  • Admin
  • Author
  • Reviewer
  • Auditor

Questions about PEP and adverse media screening

Does the agent decide whether someone is a PEP?

It compares the hit with the customer file and says whether the identifiers agree. A reviewer confirms or rejects the match, and that decision is logged with the comparison.

How are articles summarized?

The agent writes a short summary of each article and tags it with your adverse media categories. The reviewer reads each summary next to its source.

What about articles on former directors?

The summary notes who each article is about, as in the example where one concerned a former director. Whether older coverage still matters is the reviewer's call.

Can re-screening run on a schedule?

Yes. A daily schedule can re-screen your list and log a no-change result on each customer file, so the next reviewer can see when it last ran.

Controls your auditors will ask about

These controls apply to each agent you build. Sample data

Related use cases

See all use cases

Run this procedure as an agent

Book a demo with your own version of this procedure, and we'll show it running with each step logged.

Book a demo