Screening & Materiality Assessment v2 — Overview
Fenergo SaaS supports two versions of the screening match resolution and materiality assessment workflow. Screening v1 (the original implementation) and Screening & Materiality Assessment v2 (the new combined task experience) are both available and can coexist in the same environment. Adopting v2 is optional — existing v1 journeys are unaffected and do not require any changes.
This page explains what is different in v2, when to adopt it, and links to the relevant user and configuration guides for each version.
What is new in v2
Screening & Materiality Assessment v2 introduces a new optional task type — ODS: Screening Resolution & Materiality — that combines match resolution and materiality assessment into a single analyst workflow. It also introduces a redesigned ongoing screening task — OGS: Screening Resolution & Client Selection — that separates the hit resolution and client impact assessment into two distinct stages.
| Capability | Screening v1 | Screening & Materiality Assessment v2 |
|---|---|---|
| On demand screening task | Two separate tasks: Screening Match Resolution, then Materiality Assessment | One combined task: ODS: Screening Resolution & Materiality |
| Materiality assessment scope | Main client entity only | Main client entity and related parties (RP-level materiality) |
| Provider status visibility | Single combined banner | Real-time per-provider banners — Completed, In Progress, and Error states shown simultaneously |
| Classification Data | Not supported | Policy-driven fields captured at match resolution, scoped to screening category (PEP, Sanctions, Adverse Media, Enforcements, Other) |
| Sanctions proceed decision | Not supported | Configurable toggle on the ODS task. When enabled, analysts must record an OK to Proceed or Not OK to Proceed decision and enter a rationale when a Sanctions hit is confirmed as a match |
| Document upload — match level | Not supported | Configurable Hit document enabled toggle on the ODS task. When enabled, an optional document upload section appears in the Match Resolution popup. Upload is not mandatory — analysts can save a decision without uploading. Documents cannot be uploaded after the batch is closed |
| Document upload — entity level | Not supported | Configurable toggle on the ODS task. When enabled, analysts must upload a supporting document at the entity level |
| Escalation process | Not supported | A two-task journey pattern supports four-eyes escalation. Task 1 (Initial Review) is the first-line ODS task; when the Escalation toggle is enabled, users can escalate via an Escalate button in the Materiality Assessment page, selecting a team or user to notify and leaving a comment. Task 2 (Final Review) is an optional second-line task that displays Task 1 outcomes, highlights the escalation comment, and allows the second-line reviewer to override match decisions and complete outstanding materiality assessments. Task 2 is scoped using Materiality Outcome conditions configured in Journey Builder |
| Risk Calculation integration | Not supported | On ODS task completion, six OOTB policy fields are written to the main entity's policy record: FinalMaterialityPEP, FinalMaterialitySanctions, FinalMaterialityAdverseMedia, FinalMaterialityEnforcements, FinalMaterialityOther, and OverallMateriality. Values use worst-case aggregation across the main entity and related parties and can drive risk calculations and conditional task routing |
| Reuse | Match resolution decisions reused in subsequent screenings | Match resolution reuse plus prior completed materiality decisions reusable from within the task |
| Ongoing screening task | Screening Match Resolution + Materiality Assessment (same task types as ODS) | New dedicated two-stage task: OGS: Screening Resolution & Client Selection |
| OGS — hit resolution | At client level | At entity level (one hit list covering all providers, across all clients sharing that entity) |
| OGS — client impact | Implicit — all clients are impacted | Explicit — analyst selects which clients should receive a downstream ODS journey |
How the tasks relate
In v2, the ODS and OGS tasks serve distinct and complementary purposes.
The ODS: Screening Resolution & Materiality task handles on demand screening. It is used during onboarding and any journey where screening is triggered directly. The analyst resolves hits, captures classification data for confirmed matches, and completes a materiality assessment — all in one task.
The OGS: Screening Resolution & Client Selection task handles ongoing screening alerts. In Stage 1, the analyst resolves hits at the entity level. In Stage 2, the analyst selects which client relationships are affected and should receive a downstream ODS journey. That downstream journey uses the ODS task type, so the analyst workflow in ODS is the same regardless of whether the task was triggered by onboarding screening or by OGS.
Separation of concerns: OGS determines whether a hit is real at the entity level. The downstream ODS task determines what it means for each affected client, including classification, materiality, and any required escalation. These are intentionally separate stages.
How v1 and v2 coexist
Both versions of the screening tasks are available in Journey Builder simultaneously. Administrators can add the v2 task type to new journeys without modifying or removing the v1 task types from existing journeys. The two versions operate independently and do not share task state.
The v2 task type requires activation by your Fenergo implementation team before it appears in Journey Builder. Contact your implementation team to confirm whether it has been activated for your environment.
Which guide do I need?
User guides (for analysts and screening reviewers)
| I want to... | Guide |
|---|---|
| Understand how to use the on demand screening workflow in v1 | Using Screening Functionality |
| Understand how to use the ongoing screening workflow in v1 | Using Ongoing Screening |
| Understand how to use the new combined ODS task in v2 | Using ODS: Screening Resolution & Materiality |
| Understand how to use the new OGS task in v2 | Using OGS: Screening Resolution & Client Selection |
Configuration guides (for Journey Builder administrators)
| I want to... | Guide |
|---|---|
| Configure on demand screening in v1 | Configuring Screening Functionality |
| Configure ongoing screening in v1 | Configuring Ongoing Screening |
| Configure the new combined ODS task in v2 | Configuring ODS: Screening Resolution & Materiality |
| Configure the new OGS task in v2 | Configuring OGS: Screening Resolution & Client Selection |