29 posts tagged with "Screening"

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.

Supporting-document requirements are now configured per screening provider, from a new Supporting document tab in the screening provider configuration — replacing the previous per-task setup.

Previously, there was no way to reverse an entity's escalation once it had been raised during a Materiality Assessment — even after a corrected or superseding decision, the entity remained flagged as escalated indefinitely.

This release introduces automatic de-escalation. When you set a new materiality status on an assessment for an entity that is currently escalated, the escalation clears as part of that same action — there is no extra step, prompt, or new screen to interact with. Every de-escalation is recorded in the audit trail alongside the entity's other history.

Until now, every client's screening workflow required a materiality assessment, with no way to turn this off for a client whose process does not need it.

This release introduces a Materiality Assessment entitlement that can be switched off for a client. When it is, the materiality action, the Material/Immaterial/Escalated status chips and Materiality filter, the reassessment warning, and the requirement to complete materiality before finishing the task are no longer shown, along with the Materiality column on the Screening Assessment Outcomes tab. Escalate is unaffected and continues to work as before. This is managed by Fenergo Support or Product; there is no client-facing configuration screen.

The ODS: Screening Resolution & Materiality results table can now show a Classification data column, so reviewers can see a hit's captured Classification Data without opening the Match Resolution popup.