Product Updates September 2026

Smarter Risk Evaluation, Stronger Access Control, and Deeper Explainability

September’s FinCense update focuses on improving how risk teams evaluate customers, control access, and explain risk outcomes. Prospect Risk Scoring (PRS) can now evaluate multi-value customer attributes more accurately, Customer Risk Scoring (CRS) and Case Manager (CM) now support stronger Business Unit-level visibility controls, and CRS explainability now allows investigators to trace score drivers back to the exact transactions behind them.

Together, these updates help teams make risk decisions that are more accurate, better governed, and easier to explain.

PRS Native Multi-Value Attribute Evaluation in Risk Rules

Prospect Risk Scoring (PRS) can now evaluate multi-value customer attributes directly within risk rules. This is useful when a single business attribute can contain more than one value, such as a customer declaring multiple Sources of Funds. Instead of treating the attribute as one combined value, PRS can evaluate each constituent value independently and calculate the correct Risk Indicator result.

  • PRS can support attributes with zero, one, or multiple values.
  • Each value within a multi-value attribute can be evaluated independently against configured risk rules.
  • The current scope supports ANY-value matching, where a rule is matched if at least one value satisfies the configured rule.
  • Existing PRS scoring behaviour continues to apply: where multiple rules match within the same Risk Indicator, the highest matching rule score determines the Risk Indicator score.
  • Evaluation is order-independent, so the result does not change based on the sequence in which values are received.
  • The capability is generic and is not hard-coded to a specific client, field, or fixed number of values.
  • Existing single-value PRS configurations continue to work without migration or configuration changes.

{{product-cta-1}}

BU-Level Access Control for CRS and Case Manager

Customer Risk Scoring (CRS) and Case Manager now support Business Unit (BU)-level access control, so users only see the customers, alerts, and cases that belong to the BUs they are authorised to access. This improves data segregation and supports operating models where different teams must work within their own permitted business-unit scope.

  • User visibility can now be restricted based on Business Unit access.
  • CRS users only see customers and risk information within the BUs they are allowed to access.
  • Case Manager users only see cases and alerts that fall within their permitted BU scope.
  • BU-level filtering applies consistently across CRS and CM views.
  • Access control is aligned to the user’s assigned BU permissions, reducing unintended visibility across unrelated business units.

{{product-cta-2}}

Transaction Lineage Drill-Down from CRS Score Explainability

Customer Risk Scoring (CRS) score explainability now allows investigators to drill down from transaction-based score drivers to the exact transactions behind the computed value. Instead of only seeing that a transaction-derived rule contributed to the score, users can trace the supporting transactions directly from the explainability view.

  • Transaction-derived CRS rule values can be investigated from Score Explainability.
  • Users can drill down from a computed score driver to the underlying transactions used to calculate it.
  • Investigators can see the evidence behind transaction-based risk indicators without switching to separate manual searches.
  • The same explainability improvement is available where CRS details are viewed through Case Manager.
  • This gives users a clearer path from risk score → risk driver → supporting transaction evidence.

{{product-cta-3}}

Impact to Our Clients
‍

  • More accurate customer risk evaluation: each selected value is assessed on its own, so high-risk values are not hidden inside a combined attribute.
  • Better regulatory and compliance alignment: risk teams can model real-world customer attributes more naturally, especially where customers may provide multiple values.
  • Reduced configuration complexity: teams do not need to create artificial fields or configure every possible combination of selected values.
  • Improved explainability: users can understand which specific value matched which rule, and which match determined the final Risk Indicator score.
  • Future-ready rule evaluation: the capability can be reused for other multi-value PRS attributes beyond the initial use case.

Impact to Our Clients
‍

  • Stronger data governance: users are restricted to the customer and alert populations they are authorised to handle.
  • Improved compliance controls: BU-level segregation helps support internal access policies and audit expectations.
  • Reduced operational risk: teams are less likely to view or act on records outside their business-unit responsibility.
  • Cleaner investigation experience: users work with a more relevant queue, focused on the BUs assigned to them.
  • Better scalability for large organisations: multiple BUs can operate in the same platform with clearer visibility boundaries.

Impact to Our Clients
‍

  • Deeper explainability: investigators can understand not only which rule contributed to risk, but also the exact transaction evidence behind it.
  • Faster investigation review: users spend less time manually searching for supporting transactions.
  • Stronger audit narratives: teams can explain why a customer received a risk score with direct transaction-level evidence.
  • Improved confidence in CRS outputs: score drivers become easier to validate and challenge.
  • Better handoff between CRS and Case Manager: investigators can review the same supporting evidence from the embedded CRS view in CM.
Talk to an Expert