StriseWiki
Features

Portfolio Health: What's New

Beta

Portfolio Health has moved from Alpha to Beta. It's bundled with the Monitoring module -- talk to your CSM if you'd like it enabled.

Portfolio Health gives your compliance team a single, portfolio-level view of where your risk sits: which entities drive each risk category, which ones show up in several categories at once, and how risk is distributed across your whole book of business.

It started life in Alpha as a focused summary of your riskiest companies. It's now in Beta, with numbers you can trust across the product, private persons included, and the ability to click any figure to see exactly which entities sit behind it.

If you tried Portfolio Health in Alpha, this page explains what has changed. If you're new to it, the Portfolio Health feature page covers the basics.

The Short Version

  • Numbers now match everywhere. The dashboard, the entity side panel, your portfolio list, and the exported file all draw from the same source, so the figures agree.
  • Private persons are included. A Companies / Private persons / All toggle lets you look at either population, or both together.
  • Every number is clickable. Click a risk factor or a slice of a chart to see the exact list of entities behind it, and review them one by one without losing your place.
  • A clearer risk overview. A new Risk distribution section shows how your portfolio spreads across risk levels -- both the risk your settings calculate and the risk your reviewers have decided.
  • Your custom risk fields are shown. Any custom risk fields your team has defined now appear as their own category.
  • You can see how fresh the data is. A timestamp shows when the portfolio numbers were last calculated.

What Was in Alpha

The first version of Portfolio Health answered one question well: which entities in my portfolio carry the most risk, and why?

It broke your portfolio down by risk factor and, for each one, listed the entities with the most hits or flags:

  • Sanctions -- entities with direct or relation-based sanctions hits.
  • PEPs and RCAs -- entities with politically exposed persons, or their close associates, in their ownership or leadership.
  • High-risk countries -- entities connected to countries your team has flagged.
  • High-risk industries -- entities in industries your team has scored as elevated risk.
  • High-risk legal forms -- entities registered under legal forms your team has scored as elevated risk.
  • Custom risk fields -- any risk fields your team defined itself.

It also highlighted cross-referenced entities -- the ones appearing in more than one category at once -- and ranked them by how many risk factors they combined, so the entities that most deserve a closer look rose to the top.

Alpha covered companies only, and each part of the product calculated its numbers independently, which meant totals didn't always line up between the dashboard and an export.

What's New in Beta

Numbers you can trust

In Beta, the dashboard, the entity side panel, your portfolio list, and the exported CSV all read from a single, shared source of portfolio data. The total you see on a card is the same total you get when you export it or open the underlying list. This consistency was the main reason Portfolio Health moved out of Alpha.

Private persons, alongside companies

Portfolio Health now covers your private-person portfolio, not just companies. A Companies / Private persons / All toggle sits at the top of the page and applies everywhere, so you can assess either population on its own or look at your whole portfolio together. (The private-person view appears for teams that have private-person monitoring enabled.)

Drill into any number

Every figure is now a starting point, not a dead end. Click a risk factor -- or a segment of a chart -- and Portfolio Health opens the full, paginated list of the entities behind that number. The side panel stays open as you work through them, so you can investigate entities one after another without losing your place on the dashboard.

A clearer risk overview

A new Risk distribution section shows how your portfolio is spread across risk levels, side by side in two views:

  • Calculated risk -- the risk level your team's settings calculate automatically.
  • Risk class -- the risk level your reviewers have actually decided in their reviews, including a bucket for entities not yet reviewed.

Seeing the two next to each other makes it easy to spot where your team's judgement differs from the automated picture, and how much of the portfolio still needs a first review.

Custom risk fields as their own view

If your team has defined its own custom risk fields, they now appear as a dedicated category on the dashboard, with the same drill-down behaviour as every other risk factor.

Review metrics and freshness

A review-metrics section surfaces how your team is progressing through reviews, and a freshness timestamp tells you exactly when the portfolio numbers were last calculated -- so you always know how current the picture is.

Alpha vs Beta at a Glance

AlphaBeta
Risk-factor breakdownYesYes
Cross-referenced entitiesYesYes
Consistent numbers across dashboard, side panel, list and exportNoYes
Private personsNoYes (Companies / Private persons / All)
Click a number to see the entities behind itNoYes
Risk distribution (calculated risk vs reviewer risk class)NoYes
Custom risk fields as their own categoryLimitedYes
Review metricsNoYes
"Last calculated" freshness timestampNoYes

Where to Find It

Portfolio Health is the home view for teams that have it enabled -- you'll land on it when you open Strise. The Companies / Private persons / All toggle and the Export button sit at the top of the page.

What You Need

  • Calculated Risk (the Automated Risk Engine) must be enabled for your team -- Portfolio Health is built on top of it.
  • At least one entity in your portfolio.
  • The feature is enabled per team. If you don't see it, contact your CSM.

For Technical and API Users

Everything above is available in the Strise app. This section covers the underlying data model, the export, and what's reachable programmatically.

Data model

Risk factors. The Beta dashboard reports six standard risk factors, each with a separate count for companies and for private persons:

  • PEPs
  • Sanctions
  • RCAs (relatives and close associates)
  • High-risk countries
  • High-risk industries
  • High-risk legal forms

Custom risk fields your team defines are reported as additional categories alongside these.

Risk levels / risk classes. Entities are placed on a configurable risk scale: None, Low, Medium, High, Severe, Critical, plus Inconclusive for entities that can't be classified. The labels are team-configurable in your risk settings.

Two risk distributions. The Risk distribution section reports the same portfolio against two independent measures:

  • Calculated risk -- derived from your team's risk settings (the Automated Risk Engine).
  • Risk class -- the level set by a reviewer during a review, with a separate "not set" bucket for entities that haven't been reviewed yet.

Entity kinds. The Companies / Private persons / All filter maps to company, privatePerson, and all. The private-person and combined views require private-person monitoring to be enabled for the team; otherwise Portfolio Health is companies-only.

How often the numbers refresh

Portfolio numbers are recalculated on a schedule, not in real time. Standard portfolios are recalculated each night; very large portfolios are recalculated less frequently (at least weekly). The page shows a "Portfolio numbers last calculated …" timestamp per entity type, so you always know how current the figures are. Actions you take in-app (reviews, risk changes) are reflected at the next recalculation, not instantly.

Exporting portfolio data

The Export button (available to team managers) generates a portfolio data file:

  • Format: CSV. Values are double-quoted and comma-separated.
  • Scope: companies in your portfolio. (The export is companies-only; private persons are available in the dashboard but not in this export.)
  • Generation: the file is generated asynchronously -- it's queued, then appears in the "History of generated reports" list for download when ready.

You choose which fields to include, grouped into three sections:

  • General information -- Company ID (registration number), company name, countries, industries, legal form, auditor, roles and individuals, UBOs (name and date of birth).
  • Risk factors -- current status, previous status, status-changed date, AMS count, PEP count, RCA count, sanction count, and flag categories.
  • Review details -- assignees, review-added date, review-completed date, tags, review risk class, calculated risk class, next upcoming review, and comments.

Programmatic access (Connect API)

Portfolio-level Portfolio Health aggregates -- the risk-factor totals, the risk distribution, and the review metrics -- are produced inside the Strise app and are not currently exposed as a Connect API endpoint.

What the Connect API does expose is the per-entity data you'd aggregate yourself:

  • portfolioCompanies -- a paginated listing of your portfolio companies, filterable by status and country (up to 100 per page). Iterate this to walk your whole portfolio.
  • On each company: calculatedRiskLevel (based on your team settings), userAssessedRiskLevel (the reviewer-set level), and riskSignals (the individual risk factors contributing to risk).
  • Custom risk fields are available through the Connect custom-risk-field queries.

So if you want to reproduce a portfolio-level risk view in your own systems, page through portfolioCompanies and aggregate calculatedRiskLevel / userAssessedRiskLevel / riskSignals per entity. See the Strise Connect API and What Data is Available for full schema and authentication details.

Note: The internal GraphQL API that the Strise app itself uses is not a customer integration surface and isn't covered by our API compatibility guarantees. Build integrations on the Connect API.

Last updated on

On this page