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.
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.
Screening v2 Classification Data fields could previously only be configured against the Client, and once configured they always rendered regardless of the case's policy attributes. This release adds trigger conditions, so a Classification Data field can be shown or hidden based on Policy field values on the main entity of the journey or the entity of the match, and a Target Entity setting so a field can be configured specifically for the Client or a Related Party.
The left-hand Legal entities list in the ODS: Screening Resolution & Materiality task now shows each entity's screening status at a glance and can be filtered and searched, so reviewers can quickly find and focus on the entities that need attention — without opening each one. This is particularly useful on large hierarchies and in Maker/Checker escalation reviews.
Screening V2 introduces two redesigned screening tasks across On Demand Screening (ODS) and Ongoing Screening (OGS). A new ODS: Screening Resolution & Materiality task combines hit resolution, hit classification, and materiality assessment — including, for the first time, materiality at Related Party (RP) level with one consistent outcome stored per RP. A new two-stage OGS: Screening Resolution & Client Selection task formalises the review of hits from periodic screening and drives the right downstream work per affected client.
This enhancement enables Ongoing Screening (OGS) to be configured per Configuration Set in LexisNexis, with two operational modes available via the new OGS Mode toggle:
Each Configuration Set can be mapped to its own Journey Schema with its own SLAs, team assignment, and routing.
Clients using Automatic Offboarding with policies scoped by Related Products conditions will now see more consistent outcomes for their client entities during Ongoing Screening journeys. Policy evaluation calls made during Ongoing Screening journeys now include the Related Products data source, bringing them into line with all other journey types.
This means that policies referencing Related Products data are evaluated with the correct data available throughout the Ongoing Screening lifecycle, and automatic offboarding decisions accurately reflect whether scoping conditions are genuinely met.
Previously, unsubscribing related parties (RPs) from Ongoing Screening (OGS) during an offboarding journey was entirely manual. Users had to individually review and unsubscribe each RP, which at volumes of thousands or tens of thousands of offboardings, represented a significant burden of repetitive analyst work.
This release introduces automation support for the OGS: Unsubscribe from Ongoing Screening task, allowing the system to intelligently handle unsubscription for eligible entities and RPs without user intervention.