What's New at spektr

Features

Scenarios that compare a field's previous and new value

You can now build scenario conditions that compare what a field was with what it is now, inside the rule groups and and/or logic you already use. A scenario can alert when a beneficial owner's percentage falls from above a threshold to below it, and stays quiet when ownership moves but remains above it. Fields that carry a previous value are marked before you save, and the alert shows both the old and the new value, so the analyst can act without opening the source record. Scope for now: DnB monitoring changes on the main entity and its related entities.

What this changes for you: You can express before/after rules yourself, for example alerting when a UBO drops below 25%. Existing scenarios keep alerting exactly as configured.

Lists in transaction monitoring aggregation conditions

You can now use a list as the right-hand side of a transaction monitoring aggregation filter, with "is in" and "is not in". Pick a list and one of its columns, and the condition fills itself with that column's values instead of you typing each one. List conditions give identical aggregation results in real-time, periodic and backtest runs, and "is in" / "is not in" are now available on string fields as well as country fields.

What this changes for you: No more hand-maintained value lists inside aggregation conditions. If your TM scenarios filter what gets counted or summed, you can point the condition at a managed list instead.

Bolagsverket roles and signatory rules in Swedish

Swedish forms and their generated PDFs now show Bolagsverket roles and signatory rules in Swedish instead of English. "Board member" renders as "Styrelseledamot", "Chairman" as "Styrelseordförande", and "CEO" as "Verkställande direktör (VD)", with a Swedish translation for every other label in the set. English forms are unchanged, and a value with no Swedish text falls back to English rather than showing blank.

What this changes for you: Swedish-language forms and PDFs no longer mix in English role labels. Nothing to configure on your side.

Clearer old and new values in change alerts

Event orchestration alerts are easier to read. Each changed field now appears with its own old and new value side by side, and each scenario block shows only the fields that scenario matched on. Fields that did not change no longer appear, each change shows once however many scenarios matched it, and a record change covering many fields stays readable.

What this changes for you: Analysts can see exactly what changed on a customer record directly in the alert, without opening the record to compare by hand.

Improvements

Alert activity tracking

The platform now records an event every time an analyst opens an alert and every time an individual hit is resolved, capturing who acted and, for hit resolutions, the reason and outcome. Nothing is surfaced in the product yet: this builds the activity record behind alert-handling efficiency analysis.

What this changes for you: No change to existing workflows.

Website Sentinel word list moves to Platform Settings

Rolling out behind a feature flag: the Website Sentinel word list moves from account settings to platform settings, alongside other workspace-level configuration, and appears in the platform settings navigation as "Website Sentinel". The word list itself is unchanged, with the same view, add, edit and delete.

What this changes for you: Once enabled on your workspace, the word list leaves account settings, and old links redirect or show an empty state. Anyone maintaining the word list should look in platform settings.

This release also includes bug fixes, platform and performance work.

‍