Working with supporting documents in Screening V2 now also requires the Document Management permissions, in addition to Screening Edit. Check that the teams who work on screening tasks have the permissions they need before this change applies to them.
The supporting documents table in Screening V2 now shows a Type column, so analysts can see each document's type, and tell virtual documents from uploaded ones, at a glance.
The ODS: Screening Resolution & Materiality task can now auto-complete once every hit has been resolved and no required action remains — not just when a screening returns no hits at all. This removes the need for a separate "complete task" call for clients who disposition hits on an external system and push results to Fenergo via API.
Screening V2 now supports virtual documents as supporting evidence, at entity level and at hit level.
Journeys can now be configured to require re-screening when screening results have aged past a set validity period. The new Verify Screening Period task checks every screening process it governs against the validity period configured on the relevant Configuration Set(s), and blocks the journey with a checkpoint if any result has expired.
At the checkpoint, users can go back and refresh any governed screening stage — not only the one that expired — or continue without rescreening. Going back is recorded to the audit trail like any other reopen; continuing without rescreening is reflected in the task's completion record instead. Verify Screening Period is available for both Screening V1 tasks and the ODS: Screening Resolution & Materiality (v2) task.
KYC and compliance analysts can now select all screening hits visible on the current page and bulk-resolve them in a single action — applying a status, reason, and comment to every selected hit at once.
Ongoing Screening alerts from World-Check One can now be routed by Configuration Set. Each Configuration Set can be individually enabled for Ongoing Screening and mapped to its own Journey Schema for Individual, Company, and Other entities, so alerts from different screening groups launch the correct review journey.
Where an entity is screened On Demand under more than one Configuration Set, Ongoing Screening results are now processed and routed separately for each set, rather than a single Journey Schema handling every alert.
The Fenergo SaaS LexisNexis integration has been upgraded from version 11 to version 12.1 of the LexisNexis Bridger APIs. This keeps the integration aligned with the current supported LexisNexis API version and ensures continued access to LexisNexis service updates.
Fenergo SaaS now supports the LexisNexis WorldCompliance Data Plus watchlist alongside the existing WorldCompliance – Full (Legacy) dataset. WorldCompliance Data Plus provides richer, structured screening data and more frequent sanctions updates, helping firms meet intraday sanctions-screening obligations such as the EU Instant Payments Regulation.
Analysts can now have Screening Classification Data captured directly at the point an Ongoing Screening hit is confirmed as a match, rather than waiting until the downstream On-Demand Screening task. Once captured, that classification is reused automatically across every related On-Demand Screening task the confirmed match triggers.