How a Tier-2 European bank paired LexisNexis® Bridger Insight® XG with ComplianceSuite's sub-200ms API and AI-assisted risk scoring to cut sanctions false positives by 62%, halve analyst review time, and screen 4.1M payments a day without adding headcount.
The customer: a Tier-2 European retail and commercial bank (anonymised at the customer's request), regulated by a Eurozone NCA, screening roughly 4.1 million SWIFT, SEPA and card payments per day across six subsidiaries. Sanctions and PEP screening ran on LexisNexis® Bridger Insight® XG — a best-in-class dataset, but wired into three separate case-management tools and a homegrown scoring layer that had accumulated years of ad-hoc rules.
The problem: good data, expensive workflow
Bridger's underlying data quality was never in question. The pain was operational:
- False-positive rate of ~7.4% on payment screening — translating into ~300,000 analyst-touched alerts per month.
- Average alert-to-decision time of 11 minutes, with a long tail of complex names (CJK, Cyrillic transliterations, corporate look-alikes) taking 25+ minutes.
- Three disconnected review queues across retail, corporate and correspondent-banking desks, each with its own disposition codes.
- Audit fatigue: every disposition had to be reconstructed from screenshots and CSV exports at inspection time.
The integration: Bridger, wrapped by ComplianceSuite
Instead of ripping out Bridger, the bank connected it to ComplianceSuite's native Bridger Insight XG integration. Bridger continues to serve as the sanctions, PEP and adverse-media data source; ComplianceSuite becomes the orchestration, scoring and case-management layer around it.
Technically, the integration does three things:
- Sub-200ms screening API. Payment messages hit ComplianceSuite's screening endpoint, which fans out to Bridger's XML API, normalises the response and returns a scored decision in a p95 of 178 ms end-to-end — inside the bank's SWIFT straight-through-processing budget.
- AI-assisted match scoring. ComplianceSuite's risk-scoring engine layers name-similarity models, transliteration awareness, secondary identifiers (DOB, country, corporate registry ID) and historical disposition memory on top of every Bridger hit. Low-risk matches auto-close with a full evidence trail; only genuinely ambiguous alerts reach analysts.
- One unified case queue. Retail, corporate and correspondent-banking alerts route into ComplianceSuite's case management with a single disposition taxonomy, four-eyes approvals, and a regulator-ready audit log stitched to the underlying Bridger payload.
The results (90 days after go-live)
The 62% false-positive reduction came almost entirely from AI-assisted scoring — the underlying Bridger data was already high quality; what was missing was context (secondary identifiers, prior dispositions, geographic plausibility) baked into the decision. The 54% cut in review time came from the unified queue and evidence pre-attachment; analysts stopped hunting for the Bridger payload and started deciding.
What the compliance team said
"We kept Bridger — we never wanted to lose that data quality. What changed is that our analysts stopped drowning in benign hits. ComplianceSuite gave the Bridger output a brain, and it gave our auditors a single place to look."
— Head of Financial Crime, EU Tier-2 bank
Why the integration works
The pattern here is deliberate: Bridger stays the source of truth for sanctions, PEP, adverse media and State-Owned Company data. ComplianceSuite adds the three things a screening engine alone can't deliver — low-latency orchestration, contextual AI scoring, and unified case management with audit-ready evidence. For institutions already invested in Bridger Insight XG, that combination is usually the fastest path to lower false positives and faster reviews without a rip-and- replace project.
See the integration
Explore the technical detail on the LexisNexis Bridger Insight XG integration page, or book a demo and we'll walk you through a live screening flow using your own name and payment samples.