Screen before they're a customer. Keep watching after.

Yes. Retail and corporate banking run on one workflow and one customer record, each segment with its own thresholds and checks. A customer who holds both a personal and a business relationship appears as one person, not two. The setup works the same way for traditional banks and neobanks.

Yes. Sanctions, PEP and ownership checks run as one step inside your own onboarding flow, with a screening response under 200 ms. The result arrives before the account exists, not in a queue someone clears after the customer is already live.

Applicants, directors, beneficial owners and counterparties, against sanctions, PEP and adverse media in one query. For corporate accounts, the people behind the company are screened together with the company, because exposure usually sits one or two layers below the applicant.

With one file or one API sync. Duplicates across your core banking system, card system and CRM are merged on the way in, so each customer is screened once and raises one alert. This matters most at migration, when the same customer often exists under three spellings in three systems.

Existing customers are rescreened as lists change, and a new designation reaches your queue within fifteen minutes of publication. A name published at midnight is in your morning check, not in next month's batch. For sanctions this matters because freezing obligations apply from the moment of designation.

Spellings such as "Mohammad Al-Hussain" and "Muhammad Alhusayn" resolve to one profile and raise one alert, not two. Entity resolution runs before matching is scored, so analysts review people rather than spelling variants. In bank screening, spelling variants are one of the largest sources of false positive volume.

Yes. Spouses, children and business partners are linked to each PEP, across four tiers from heads of state down to municipal officials. PEP data is built from official gazettes and parliamentary records, country by country. The link is what exposes a relative who opens an account under a different surname.

Yes. The compliance team writes rules in plain English and tests them on last month's data before they go live, so the alert volume a rule creates is known in advance. Each alert links to the customer and their current risk profile, and the analyst sees the transaction next to the onboarding and screening history.

Only what you configure. The agent closes routine cases with a written reason and a full log, and anything outside its remit or below your confidence threshold goes to an analyst. Each closure keeps the sources used, the reasoning and the steps taken, in the format your auditor requires.

Yes. complead runs alongside your existing system on the same customer file until you switch the traffic over, so screening never stops and both systems' alerts can be compared on real names before cutover. The parallel period also gives your model risk and audit teams the evidence they need to approve the change.