Calculated Risk SettingsCopy Anchor Link

Calculated Risk is Strise's automated risk classification. It assigns a Calculated Risk Class to each entity by scoring the entity across your configured risk categories and mapping the total points to your team's risk class thresholds. These settings encode your risk rating model into Strise, so every assessment in the portfolio scores the same way and records why.

Find them under Settings → Calculated Risk. Everyone on the team can view the page; editing requires manager permissions.

The screenshots show fictional demonstration data.

How the Score Is CalculatedCopy Anchor Link

1. Data collection — Strise evaluates the entity's current data: screening results (PEP, RCA, sanctions), countries, industry codes, legal form, and any custom risk fields. For companies this includes connected entities — beneficial owners, roles, and owners across the ownership structure — so a PEP two layers up still counts.
2. Category scoring — each category contributes points according to your configuration (details per category below).
3. Summation — points from the categories are added into a total risk score.
4. Class assignment — the total is mapped to a risk class using your thresholds.

The result is shown on the entity page, in Portfolio, and in Reviews. The Calculated risk card on the entity page lays the whole calculation out — every category's contribution, the matched values, the categories that were checked without a hit, and any missing data:

Two scoring rules worth understanding before you configure anything:

• Within a category, the highest-scoring match wins — no summation. A company linked to two high-risk countries gets the points of the highest-scoring country level once, not twice. The same applies to industries and legal forms. This means the risk is never underestimated by averaging, and never inflated by double-counting within a category.
• Custom risk fields are the exception: each configured field scores independently, and the fields sum with each other. Adding many custom fields raises the maximum possible score.

⚠️ Plan your maximum before setting thresholds. Strise does not display a "maximum possible score" — it depends on your configuration. Work out your worst case (one highest level per category + every custom field) before deciding where Low/Medium/High should start. Points per level go up to 100.

Risk CategoriesCopy Anchor Link

Screening the Entire NetworkCopy Anchor Link

Which connected entities are screened for PEP, RCA and sanctions is configured per category in PEP Settings and Sanctions Settings: the entity itself, its active roles, beneficial owners, shareholders, and the subsidiaries above the ownership thresholds you set there. A subsidiary's share is its highest reported figure — when a source states a range, Strise compares your threshold against the top of that range — and a subsidiary with no reported share is treated as fully owned, so it is always included. Teams with the network-risk toggle enabled — ask support@strise.ai — also get a Screen entire network switch on the Calculated risk card. Turning it on extends the same screening one hop further out: the companies in the entity's network are screened for their own roles and owners as well, so a PEP or sanctions hit sitting behind a subsidiary shows up in the risk factors too. The line beside the switch always names the scope currently in effect.

Custom screening lists have their own screening scope on the Settings → Custom screening lists page; see Custom Screening Lists.

Country, industry and legal-form risk each have their own screening scope under Settings → Geographic & Structural. In each of them, Include companies on the ownership path (under Shareholders) is off by default, so a holding company that owns less than your shareholder threshold does not add its country, industry or legal form to the score just because a larger owner sits behind it. Turn it on in a category's scope to count those companies too. This is a saved team setting, unlike the Screen entire network switch above.

The switch changes what you are looking at, not what your team screens. It is not saved, it applies to the entity page only, it changes nothing for anyone else, and it returns to your configured scope when the page reloads. Everything automated — monitoring alerts, Portfolio, Reviews, and the Connect API — keeps using the scope from your screening settings.

Configuring Risk PointsCopy Anchor Link

For each category you create score levels: a number of points (0–100) and the values that trigger it. Up to five levels per category. An entity matching a level gets that level's points; if it matches several levels in the same category, the highest one counts. Each level can also carry a highlight colour (moderate / medium / high) used to flag the factor across the app.

ℹ️ When you click Add risk level, the new level starts at the lowest unused point value — often 1 point. That's a placeholder, not a recommendation: set the points you actually mean. (Two levels in the same category can't share the same point value.)

PEP and RCACopy Anchor Link

A single hit-level score each: if the entity's network contains at least one PEP (or RCA), the configured points are added. PEP and RCA are scored separately so you can weight direct political exposure differently from associates.

SanctionsCopy Anchor Link

Points added when the entity or its network has at least one suggested-true sanctions match. Because a sanctions match is a critical finding, teams typically set this high enough that it alone puts the entity in your highest class.

Custom Screening ListsCopy Anchor Link

Points added when a company in scope has a hit on one of your team's custom screening lists. This category applies to companies only, and it adds nothing until you put lists in a score level: a new team starts with one level at 0 points and no lists.

Each score level holds points, a highlight colour, and the lists that trigger it. Select Add lists on a level to pick lists. Lists in different levels can score differently, for example one list in a high level and another in a lower one. If your team has no lists yet, Upload a list opens the same upload as the Custom screening lists settings page.

• Only the highest level counts. If the company has hits on lists in several levels, the factor adds the points of the highest matching level once.
• Only lists in a level are screened for calculated risk. A list you have uploaded but not put in a level adds no points and shows no hits on the entity page. Monitoring still screens it.
• A hit counts until someone marks it as a false positive. Hits with no decision and confirmed matches both add points.

Which companies are screened is set under Screening scope on the Settings → Custom screening lists page, not in PEP or Sanctions settings. By default only the company itself is screened. See Screening Scope.

Deleting a list removes it from its score level, saved as a new settings version.

High-Risk CountriesCopy Anchor Link

Create up to five score levels and fill them with individual countries and/or predefined collections: FATF High-Risk Jurisdictions (Call for Action), FATF Jurisdictions under Increased Monitoring, EU High-Risk Third Countries, and Tax Havens (Tax Justice Network).

ℹ️ Collections and manual selections don't double-count. If a country appears both in one of your levels and in a selected collection, the entity simply gets the points of the highest matching level. Collections are curated lists that update with Strise releases — adding FATF High-Risk Jurisdictions (Call for Action) means future list changes flow into your scoring automatically.

High-Risk IndustriesCopy Anchor Link

Assign industry codes (NACE-style, per country standard) to score levels. Parent categories cover their sub-codes.

Companies outside the national registries (Global Entities) are scored against the Global tab, which uses ISIC Rev 4 codes. A Global Entity counts with the ISIC Rev 4 codes from its source data plus any industry you add by editing the entity. Industry codes in another standard from the source data are not scored; an industry you add by editing is scored in whichever standard you choose.

High-Risk Legal FormsCopy Anchor Link

Assign legal forms (per country) to score levels — for example structures with anonymous ownership.

Custom Risk FieldsCopy Anchor Link

Define your own fields — single-select or multi-select — and give each option a score level. Field definitions are shared across the team (and across Companies and Private persons); the scoring is configured per entity type. Remember: custom fields sum with each other, unlike the built-in categories.

Missing DataCopy Anchor Link

For countries, industries, and legal forms you can set a missing data score — points to add when Strise has no data for that category. If data is missing and no missing-data score is configured, the entity's result becomes Inconclusive instead of a risk class, so absent data is never silently treated as low risk. An Inconclusive result lists the factors that had no data and marks them as missing data, so you can see what caused it. Setting a missing-data score for a factor avoids Inconclusive.

Risk Classes and ThresholdsCopy Anchor Link

The total score maps to a risk class through thresholds you define:

• Up to five classes, each with an editable name. The default set is None (0), Low (20), Medium (40), High (60) enabled, plus Severe (80) available to enable — thresholds fully editable.
• A threshold is the class's starting point (inclusive). Each class covers from its threshold up to the next enabled class's threshold; the top class is open-ended. Ranges are contiguous by construction — every score lands in exactly one class.
• At least two classes must be enabled, the lowest enabled class must start at 0, and thresholds must be strictly ascending.
• Validity period (months) is set per class in the same table — how long a completed review stays valid before the entity is due for re-review. Validity is unset until you configure it; a common risk-based pattern is 24 / 12 / 6 months for Low / Medium / High. A validity period must be between 1 and 240 months. It applies to any entity carrying its class — even a class that has since been disabled, so entities assessed at that class still come due.
• Validity is per entity kind: the Companies and Private persons tabs each hold their own validity periods, so a team can, for example, re-review private persons every 12 months and companies every 24.

Manual Risk LevelCopy Anchor Link

The calculated class can be supplemented or overridden with a Manual Risk Level, set when performing a Review. Both values stay visible — it's always transparent that an override exists and what the system calculated.

The Risk assessment card at the top of the entity's Overview tab is where you read the two side by side: it shows the risk class recorded in the latest review alongside Calculated risk at review, together with who reviewed it, the next scheduled review, and the review report. Earlier reviews sit collapsed below it.

• The calculated class keeps recalculating as data changes; the manual level persists until a reviewer changes it.
• The manual level (when set) is what drives the next-review date via the class validity periods.
• Typical uses: documentation justifies a lower class despite a high-risk industry; a company naturally has many PEPs (say, a political party) without warranting your top class; or a self-declaration adds context the automated score can't see.
• A company that has never been reviewed shows an empty Risk assessment card with an Add to Review button — see Adding a Company to Review.
• Links to an entity's reviews, including saved URLs ending in ?tab=reviews, open the Overview tab, where the card is.

Private PersonsCopy Anchor Link

Teams with private persons enabled get a separate tab with its own risk classes, thresholds, validity periods, and scoring — limited to PEP, RCA, sanctions, and custom risk fields (no geographic or structural categories).

Copy buttons let you copy a section's configuration between the Companies and Private persons tabs.

⚠️ Copying replaces the target tab's current configuration immediately and without a confirmation step — and copying Risk Classes also carries over the validity periods. Nothing is saved until you press Save, so if you copy by mistake, leave the page without saving.

Staging Changes in Draft ModeCopy Anchor Link

With draft mode you can stage Calculated Risk changes instead of saving them straight away. Open draft mode from the page header. One draft spans this page and the PEP, Sanctions, Geographic & Structural and Monitoring alerts settings pages, so a scoring change and a screening change can be applied together.

• What a draft can change: risk points per category, the points given to existing custom risk field options, risk classes with their thresholds and validity periods, and the same settings on the Private persons tab.
• What it can't: custom risk field definitions. Adding, renaming or deleting a field or one of its options only works outside draft mode.
• No impact preview yet: a draft doesn't show how many entities would move to another risk class. The apply summary lists every staged change.

Applying the draft needs a reason for change, which is recorded in the Settings Change Log, and has the same effect as saving the settings directly: the Calculated Risk shown on entity pages uses the new settings right away, and the stored risk classes that monitoring alerts on are recalculated in the next monitoring run.

Where Calculated Risk Shows UpCopy Anchor Link

• Entity pages — the class with its full breakdown on the Calculated risk card.
• Portfolio — class per entity for at-a-glance risk distribution; also the basis of Portfolio Health.
• Reviews — the class and its breakdown at review time are part of the documented assessment. Settings changes are not retroactive: a completed review keeps the class it documented; the updated settings apply from the next review.
• Monitoring — monitored data changes (new PEP hit, ownership change, sanctions match) change the inputs to the calculation; see The Monitoring System.

PermissionsCopy Anchor Link

Risk context, under Settings → Risk context, is shared team guidance for the Assessment summary: business rationale, conditional exceptions and what evidence to obtain. It can inform explanations, follow-up and suggested disposition. In recommended actions, it takes priority over general advice. It never changes Calculated Risk or establishes facts about an entity. Rules that belong in Calculated Risk settings are listed separately in an AI suggestion.

Write the guidance in the editor on Settings → Risk context. Format it with headings, bold, italics, links and bulleted or numbered lists; there is no Markdown to learn. The guidance has a maximum of 1,000 words, and the counter below the editor shows how many you have used. Its language defaults to your own display language. To use another, choose an Output language when you first create it with Import from file; the editor has no language picker. Viewing and editing use your normal settings permissions. Save your changes from the bar at the bottom of the page, as on other settings pages. While you have unsaved changes, Show changes highlights what you added and removed compared with the saved version.

The How to write risk context guide above the editor describes three optional sections, in this order: Business context (what your business does and which customers, products or channels need extra care), Risk guidance (judgement that Calculated Risk cannot capture, such as conditional exceptions) and Investigation expectations (which evidence to ask for, and when). Write rules as a condition and an action, such as "When a customer is cash-intensive, ask for one month of receipts." Leave out anything Calculated Risk already handles, such as risk classes, thresholds and country or industry lists, as well as facts about specific customers. An empty editor starts with the three headings; they are not saved until you write under them, and empty sections are left out when you save. The headings follow the language you choose. AI suggestions use the same sections.

Select Import from file to have Strise draft or update the guidance from one file, your instructions, or both. An updated file proposes changes to the current text and preserves unrelated guidance, including manual notes. To replace everything, say so in your instructions. Where assisted risk settings import is also enabled, you can use its uploaded file for a separate risk-context suggestion.

Imports open in a panel beside the editor. The AI works in the background, so you can close the panel or leave the page and come back to it. A suggestion belongs to the person who requested it until it is saved. When it is ready, the panel shows what it adds and removes, notes to check, and any rules that belong in Calculated Risk settings instead. Select Use suggestion to load it into the editor, adjust it if you need to, and save it to update the team's context. Dismissing a suggestion leaves saved context unchanged. If someone saves settings before you do, Strise shows the differences against their version before you can save over it.

Upload PDF, XLS/XLSX, CSV, TXT or Markdown, up to 10 MiB and 600,000 extracted characters. Spreadsheets support up to 2,000 nonempty rows across the workbook and 50 columns; content beyond these limits is rejected. Unreadable or scanned PDFs need a readable, text-based replacement. Uploads are temporary processing inputs. A retry uses the latest saved context and may require you to upload the file again.

The Assessment summary uses saved context when someone generates an AI summary in an assessment. Suggestions that are not saved do not apply, and changing context does not rewrite an existing summary. If Strise disables risk context, saved context and suggestions are retained, but editing, saving suggestions and use in new Assessment generations are unavailable until it is re-enabled.

Related PagesCopy Anchor Link

• Calculated Risk — the feature overview
• PEP Settings and Sanctions Settings — screening configuration that produces the hits this page scores
• Custom Screening Lists — uploading the lists this page scores
• Risk Flag Settings
• Monitoring Alerts Settings