What's New at spektr

Features

A new Active Scenarios widget

The flat text list of active scenarios on the customer record is replaced by a proper widget, styled after the Risk Score Breakdown. Each active scenario is a row with its name and activation time; expand it to see its rule groups and per-rule results. The widget reflects the latest process run, shows active scenarios by default, and an Active/All switch reveals the scenarios that didn't trigger. Rolling out behind a feature flag.

What this changes for you: Scenarios no longer appear as a plain text field and can't be added as a field inside other widgets; they live in their own widget instead. Nothing changes until the flag is enabled for your workspace, then analysts will see the new layout on the customer record and case pages.

List screening in transaction monitoring rules

You can now use your Lists as a rule source on the transaction monitoring rule node. A new "is in list" predicate checks any transaction field against a list, the same way lists already work in Scenario and Router nodes, which covers use cases like keyword and high-risk jurisdiction screening. Lists are still created and maintained in the Risk Matrix section, including CSV import, and all existing ways of adding rules are unchanged. Only Lists are included here, not scored matrices.

What this changes for you: Your team can now build transaction monitoring rules that screen against your own lists. Existing rules are untouched, and note that editing a list doesn't update rules that already use it: re-apply the list in the rule to pick up changes.

Reported badge on filed transactions

When a report is filed from a case, the transactions attached to it are now durably marked as reported. A "Reported" badge sits on the transaction, with the report reference(s) shown on hover, and a transaction can appear in more than one report or amendment. Each report also gets its own view in the case's transactions tab, where you pick its transactions with checkboxes or select-all; select-all covers the entire filtered set across every page, not just the one on screen. Rolling out behind a feature flag.

What this changes for you: Reporting is only available upon request, this only applies for users of the SAR reporting in cases.

Filters and saved views for case transactions

The transactions tab on cases now has a filter bar with the same fields as the global transactions view. Filters work across every view in the tab: the default linked transactions, the 6-month history pull, and each report's own view. You can save a filter setup as a named view and come back to it later, and filtering runs server-side so it stays fast on cases with hundreds of transactions. Rolling out behind a feature flag.

What this changes for you: Analysts working large cases can narrow long transaction lists instead of scrolling, and keep go-to filters as reusable views.

SAR report lifecycle notifications

Every transition in a report's lifecycle now notifies the person who needs to act next: submitted for review, sent back, approved, disregarded, or filed. Recipients come from the case workflow's Draft, Approve and File roles, falling back to permission holders and the case assignee when no workflow applies. Each user can choose platform-only or platform plus email notifications, and every transition is also written to the case timeline. Rolling out behind a feature flag.

What this changes for you: Reporting is only available upon request, this only applies for users of the SAR reporting in cases.

Alerts and cases inside the case view

The Client details dropdown in a case now includes an "Alerts and Cases" option. It shows the selected customer's full list of alerts and cases, including closed ones, directly in the case canvas, with the same layout, search and Alerts/Cases switch as the customer profile. Changing the customer in the picker updates the view to match. Rolling out behind a feature flag.

What this changes for you: Investigators no longer need to leave the case and open the customer profile to check whether a customer has other open alerts or a case history.

Tags as conditions in Scenario nodes

Scenario nodes now accept your existing customer tags as condition inputs. You can check whether a specific tag exists on the customer, or that it doesn't, pick from your workspace's configured tags, and combine tag conditions with any other scenario conditions. Evaluation uses the latest tag state at that point in the process, and if tags aren't available in a given process context, the UI explains why instead of hiding them.

What this changes for you: No change to existing processes. You no longer need extra nodes or workarounds to route on tags.

Version history for case summary AI

The case summary AI now saves every generated summary instead of overwriting the previous one. A date dropdown on the summary block lists all versions, with the newest marked "Current"; pick an older date to read that version in place, and use "See latest version" to jump back. The dropdown only appears once a case has more than one version, and the history persists across sessions.

What this changes for you: You can now see how the AI's read of a case evolved, which helps when reviewing why a triage decision looked the way it did at a given date.

Customer mapping for external risk signals

Incoming signals that carry transaction IDs are now matched to every relevant client record type in your setup, for example both the consumer and the merchant side. When a case is created from such a signal, it automatically includes all linked transactions and all related client records. Signals with no transactions are guarded so they don't produce empty cases.

What this changes for you: Cases created from external signals arrive complete, instead of needing an analyst to link the related customer records by hand.

More complete UBO data for Norwegian and Finnish companies

For companies in Norway and Finland, spektr now calls DnB's Risk Guardian Suite AML real-time screening API in addition to the existing DnB Ownership Insights lookup, which can miss UBOs on its own, especially cross-border ones. Results from both sources are merged and deduplicated, and if both return nothing we fall back to DnB's Principals and Contacts data. Rolling out behind a feature flag.

What this changes for you: No change to your current workflows. Once enabled for you, ownership results for Norwegian and Finnish companies will be more complete.

Filter the timeline by event type

The timeline now has a multi-select filter at the top. You can narrow it by category: process events, tag changes, status changes, alerts, record updates, and AI events. All categories are on by default, and your selection sticks as you move between customer profiles.

What this changes for you: Long timelines are easier to scan, and you don't need to redo your filter when switching profiles.

Waiting processes in the Ongoing processes tab

Processes that are waiting, for example for an alert to be resolved or for another process to finish, now show up in the Ongoing processes tab. A new "Paused at" column shows when each process entered the waiting state. These runs aren't client-facing and never expire, so they show "-" in the Expires column and skip the Open, copy link and delete actions.

What this changes for you: Runs that used to be invisible while waiting are now visible in Ongoing processes. Nothing changes about how your processes run.

Improvements

All DnB industry codes, not just the first

DnB Company Information now exposes every industry code on a company instead of only the first one, so you may see additional industry codes where DnB returns more than one.

Real links in the customer, cases and alerts lists

Rows in the customer list, cases list and alerts list are now real links, so you can right-click or middle-click any row to open it in a new tab.

Real links on the customer profile lists

The cases and alerts lists on the customer profile got the same treatment: rows are real links you can open in a new tab.

Full timestamps in the events list

Hovering the Created column in the events list now shows the full timestamp, not just the date.

We also fixed the Website Checker's Terms & Conditions check showing "No match" even when the document was retrieved and its content matched the company, so the Technical Checks panel now agrees with the AI's reasoning.

This release also includes general performance improvements and bug fixes.