All modules
    Objective, repeatable risk ratings

    Customer Risk Scoring

    Eliminate subjective assessments with a configurable risk-scoring engine.

    ComplianceSuite · Risk Scoring
    cust #96273547
    Profiles › Customer › J. Cameron
    John Cameron
    Retail · Activated 23/02/2025
    High · 78
    Composite score
    78/100
    Geography · UAE corridor+22
    Product · High-value crypto+18
    Behaviour · velocity spike+14
    PEP relationship · 2nd degree+12
    Tenure · 3+ yrs clean history−8
    Model · cs-risk-v3.4 · explainable · last refresh 12 min ago
    30+
    Risk factors per model
    Geography, product, channel, behaviour
    Real-time
    Recalculation
    On every customer event
    100%
    Models version-controlled
    With full diff history
    1:1
    Maps to your written policy
    No black-box scoring

    What it does

    Objective, repeatable risk ratings

    Map your internal risk policy into ComplianceSuite's scoring matrix. Apply weights to geography, product, channel, and behavioural signals — recalculated continuously.

    • Drag-and-drop risk-factor configuration
    • Geography, product, channel, and behaviour weighting
    • Continuous recalculation on customer events
    • Risk band thresholds with automatic re-review triggers
    • Full versioning of risk model changes

    Use cases

    How teams put it to work.

    Three concrete scenarios from regulated institutions running ComplianceSuite in production today.

    1

    Onboarding-time risk band assignment

    A neobank wants to assign a risk band (low / medium / high / prohibited) at the moment of onboarding so it can route customers into the right product, due-diligence depth and monitoring intensity.

    The Risk Scoring engine returns a score and band in <100ms based on geography, product mix, source-of-funds and behavioural signals — fully transparent to the reviewer with the contributing factors visible.

    2

    Continuous re-rating on new evidence

    A bank's high-risk customers must be re-rated when a new screening hit, transaction pattern or jurisdiction change occurs — currently a quarterly manual review.

    Continuous recalculation re-rates customers in real time as events arrive, automatically triggering re-reviews when a customer crosses a band threshold — closing the gap between event and action from 90 days to seconds.

    3

    Regulator model defence

    A regulator demands evidence that the bank's customer risk-rating methodology aligns with its written EWRA, has been independently reviewed and is consistently applied.

    Every risk model is versioned with a full change diff, four-eyes approval log and back-test report. The MLRO exports a model-defence pack on demand, mapping each factor to the written policy.

    How teams use it

    Built into a single end-to-end workflow.

    STEP 1

    Configure

    Map your policies, risk factors, and regulator requirements into the engine — no code.

    STEP 2

    Operate

    Your reviewers work from one inbox with full context, history, and supporting evidence.

    STEP 3

    Prove

    Generate audit-ready reports in minutes, on demand, with full versioned trail.

    FAQ

    Buyer questions, answered.

    The five things compliance, product and security teams ask before activating Customer Risk Scoring. Need more detail? Talk to a specialist.

    Reviewed by our compliance product team — Q1 2026

    Up next

    Case Management

    Continue