Customer FAQ: LexisNexis AML Screening
Last updated: October 28, 2026
LexisNexis is now live on AiPrise as an AML screening option and continuous monitoring provider. Nothing changes on your account until you opt in, and when you move, your past ComplyAdvantage decisions stay exactly as you left them.
What is changing?
We have integrated LexisNexis for AML screening (sanctions, PEP, adverse media, warnings and enforcement lists) and continuous monitoring. When you opt in to LexisNexis, we plan and migrate your existing sessions under continuous monitoring to LexisNexis.
Why LexisNexis?
In our proof-of-concept testing, LexisNexis showed stronger sanctions detection than our current setup. It screens against its WorldCompliance database plus official lists such as OFAC, UN, EU and UK sanctions, and the FinCEN money-laundering-concern list. It also gives you more transparency on each hit:
The name that matched, and whether it was an alias
A name match score on every hit
The exact lists and match settings each session was screened with
A complete history for every hit, with one entry per update date
What did the proof of concept show?
On a live customer book of about 12,600 profiles, LexisNexis returned sanctions-list matches on 709 profiles that ComplyAdvantage had screened as clear. 211 of those were exact or very high-confidence name matches (score 95 or above).
We re-screened the same profiles on both providers and compared the results profile by profile.
Individuals | Businesses | Total | |
|---|---|---|---|
Profiles screened | 1,021 | 11,634 | 12,655 |
Sanctions matches found by LexisNexis, missed by ComplyAdvantage | 109 | 600 | 709 |
of which exact name match (score 100) | 26 | 27 | 53 |
of which very high confidence (score 95–99) | 52 | 106 | 158 |
of which high confidence (score 90–94) | 30 | 241 | 271 |
A "miss" counts only profiles where ComplyAdvantage was actually run and returned no hit; the score rows also include 9 profiles where ComplyAdvantage was not run. Matches are name-based candidates; as with any screening result, your analysts confirm them using date of birth, country and other identifiers.
The difference comes largely from coverage. LexisNexis's published source catalogue reaches more of the world than ComplyAdvantage's:
Coverage | ComplyAdvantage | LexisNexis |
|---|---|---|
Countries and regions covered | ~126 | ~174 |
Jurisdictions the other provider does not cover | 3 | 51 |
Sanctions sources | ~163 | ~177 |
Warning and enforcement sources | ~1,044 | ~1,712 |
The extra jurisdictions are concentrated in Sub-Saharan Africa, the Caribbean, Southeast Asia and the Balkans, where emerging-market and correspondent-banking risk is highest. Coverage figures are directional, taken from each provider's own catalogue.
Is ComplyAdvantage going away?
No change is required today. ComplyAdvantage remains available for now, but based on the proof-of-concept results above, we recommend switching to LexisNexis.
Do I have to do anything?
No. If you are interested, comment on the announcement thread or tell your AiPrise contact, and we will schedule a setup or migration with you.
2. Getting access
How do I request LexisNexis?
Comment on the announcement thread or contact your AiPrise support team or FDE. We use the responses to plan the order of customer migrations, so registering early helps us schedule you sooner.
Can I try it before moving everything?
Yes. We can set up a new LexisNexis template next to your existing ones. New sessions on that template screen on LexisNexis, while sessions on your current templates stay on ComplyAdvantage. This lets you compare results on live traffic before migrating.
What can I configure?
On the template's AML Screening tab you can:
Choose which screening lists to search (by default, all lists are on)
Set a fuzziness level per list, from 0% to 30% (default 15%). Fuzziness sets how strict the name match is: the lower the fuzziness, the stricter the match and the fewer false positives.
Turn continuous monitoring on or off
Each session keeps a record of the lists and fuzziness it ran with. Later template edits apply to new sessions only, never to sessions already screened.
Can I test in sandbox?
Sandbox returns sample hits so you can build and test your integration. It does not run continuous monitoring, so monitoring behaviour can only be observed in production.
Does pricing change?
Monitoring billing does not change: you pay per monitored profile while monitoring is on, regardless of provider.
3. Migration and testing
How are you rolling this out?
In stages, one customer at a time. We ran LexisNexis in production on our own account first and checked that nothing else in the platform regressed. Monitoring has run in production since mid-October with no failures. Next come a small group of pilot customers, then a wider cohort. Each step only starts once the previous one is stable.
What happens on my migration date?
We call your migration date the baseline date. On that date:
We share a change note and confirm the date with you in advance.
We re-screen every profile you have under continuous monitoring on LexisNexis. Session IDs and profile IDs remain the same.
Every hit from that first LexisNexis screen is recorded as a resolved baseline. Your profile statuses stay the same, no callbacks are sent, and no reviews are created.
From then on, monitoring runs on LexisNexis and alerts you only on changes after the baseline date: new hits, or updates to existing ones.
We validate the data with you and confirm nothing else has changed.
Will my past ComplyAdvantage decisions be changed?
No. Every approval, rejection and whitelisted hit you made on ComplyAdvantage stands. We do not re-open or re-review them. Your ComplyAdvantage history stays on the profile and remains exportable for audit.
Why not just compare old and new hits?
The two providers describe the same person or business differently, so their hits cannot be matched one-to-one. A first LexisNexis screen returns everything it knows, including matters you already cleared on ComplyAdvantage. Treating that first screen as a baseline avoids a flood of duplicate reviews and keeps your earlier decisions intact.
Can I see what the baseline found?
Yes. Baseline hits are visible on each profile, marked as resolved during migration. You can open and review them at any time.
Will there be a gap in monitoring?
No. ComplyAdvantage keeps monitoring your profiles until your LexisNexis baseline is complete. On the profile, everything before the baseline date shows as ComplyAdvantage history and the LexisNexis timeline starts from that date.
What about cases that are in review on the migration date?
They either finish on ComplyAdvantage or are re-screened on LexisNexis. We agree which with you beforehand, so no case is split across both providers.
4. Impact on your workflows
How does continuous monitoring work on LexisNexis?
Every monitored profile is re-screened at least once a day, and again whenever a screening list it uses is updated. Only real changes are reported. A new, updated or removed hit moves the case to Review, creates a ticket if you have one configured, and sends the same AML monitoring update callback you receive today. A pass with no change does nothing.
Will I get more alerts?
Possibly a few more, because every LexisNexis update reflects a visible change to the listing. Two controls keep noise down: muting (whitelisting) a hit stops updates for that hit, and an approved case stays approved until the listing genuinely changes.
Do my risk rules need to change?
Possibly. LexisNexis groups hits into five types: Sanction, PEP, Warning, Fitness & Probity, and Adverse Media. It does not provide PEP classes 1 to 4, adverse media sub-types, or a separate criminal record type.
Your rule uses | What happens on LexisNexis | What to do |
|---|---|---|
Hit counts or the overall AML result | Works unchanged | Nothing |
PEP class 1, 2, 3 or 4 | Never fires | Replace with one PEP rule and choose its score |
Adverse media sub-types | Never fires | Replace with a single Adverse Media rule |
Criminal record or legal background | Never fires | Map to Fitness & Probity or Warning, as your policy requires |
We review your rules with you before go-live and help you update them.
Will my API integration or webhooks break?
The AML results in the API keep the same documented shape, and the monitoring callback payload is the same as for ComplyAdvantage. LexisNexis results add extra detail, such as the lists matched and match details. If your system reads provider-specific fields or the hit types listed above, check those before your migration date; we share the change note in advance for this.
What about API customers turning on monitoring later?
Turning on monitoring for a profile that was screened on ComplyAdvantage triggers a fresh LexisNexis screen. Through the API this runs asynchronously and reruns the existing session ID. Monitoring alerts cover changes from the date you turn it on.
Does anything change for business (KYB) checks?
Related persons and UBOs are screened in their own sub-sessions. Those templates are moved to LexisNexis as part of the same setup.
5. Data and compliance
How do I explain the baseline to an auditor or regulator?
Your ComplyAdvantage decisions are preserved and exportable, and ComplyAdvantage monitored your profiles right up to the baseline date. The first LexisNexis screen is recorded on each profile as a migration baseline, and every hit in it remains visible. From the baseline date, LexisNexis monitoring alerts you to any change. We will ask you to acknowledge this approach before your migration so it is documented on both sides.
What data is shared with LexisNexis?
Only the screening details already used for AML checks today, such as name, date of birth and country for individuals, and company name and country for businesses.
Is LexisNexis available for EU-hosted accounts?
The setup is the same for EU-region accounts.
Will my AML policy still be applied?
Yes. If you have uploaded an AML policy, the AML agent follows it when assessing new monitoring alerts after the baseline date.
6. Next steps and support
What happens after I register interest?
Your account FDE reaches out to agree a plan: a LexisNexis test template, a review of your risk rules and integration, and a migration date. You receive a change note before anything moves.
Who do I contact with questions?
Your AiPrise support team or FDE, or reply on the announcement thread.