The Risk Settings Migration (2026)

This migration is complete. During the first half of 2026, all teams moved from the legacy Review Settings risk model to Calculated Risk. This page remains as a reference for what changed and where to adjust your configuration.

What changed

The legacy system assessed risk through manually configured review parameters. Calculated Risk replaces it with a transparent, points-based model: each risk category — PEP, RCA, sanctions, countries, industries, legal forms, and custom fields — contributes configurable points, and the total maps to a risk class your team defines. The full model and every setting is documented in Calculated Risk Settings.

Teams that had not migrated themselves by the deadline were transitioned automatically in 2026. If that was your team, your risk points and thresholds are the standard starting configuration — review them against your internal risk policy under Settings → Calculated Risk.

Risk visibility across the platform

With Calculated Risk, risk indicators appear consistently across the product:

• Portfolio — the risk class next to each entity in the portfolio overview
• Monitoring — data changes that affect risk inputs generate alerts; see The Monitoring System
• Reviews — the class and the per-category points breakdown are documented in each review
• Entity pages — the class with a hover breakdown of exactly how it was calculated

What stayed the same

Your day-to-day review and monitoring workflows are unchanged — only the underlying risk methodology moved from opaque review parameters to explicit points you control.

Checking your configuration

1. Open Settings → Calculated Risk.
2. Verify the risk points per category against your internal policy — remember that within each category only the highest matching level counts, while custom fields sum.
3. Verify the risk class thresholds and validity periods.
4. Use the hover breakdown on a few known entities to sanity-check that classifications land where your policy says they should.

Questions about what your team was migrated with? Contact your customer success manager.