Compliance must become independent, capable of running itself. Staying current without prompting. Getting sharper as it learns. Freeing your team to decide rather than maintain. That's what Marble is building toward, and it starts with customer risk scoring. Set your framework around your risks and obligations, and let the platform carry it forward.
Scoring belongs where screening and monitoring already happen
Customer risk is never static. So the score can't be either. Screening results shift. Transactions pile up. Profiles change. Any of it can move a customer's risk, at any time, without warning.
A score computed off in a separate tool is out of date the moment the data moves. (Or was supposed to move.) So it shouldn't live in a separate tool.
Customer risk scoring belongs on the same platform as your AML screening and transaction monitoring, not “bolted on” beside them.
Score where the data lives, and everything gets stronger.
The score tracks real behavior. Sitting right next to transaction monitoring, the customer's actual activity (e.g. volumes, counterparties, patterns) feeds the risk level directly. Behavior is the truest risk signal you have, and it's wasted the moment you cut it off from the score.
It's simply easier. No piping data between systems, no reconciliation, no gap between the tool that sees the behavior and the tool that rates it. Screening flags feed the score on the spot. Any new hit re-scores the customer on its own.
And it closes the regulatory loop. A risk-based approach – what regulators require – means your monitoring has to be calibrated to each customer's risk. That only works when the risk level and the monitoring rules share a platform: high-risk customers get stricter thresholds, low-risk customers get lighter ones, automatically, and flowing straight into case review.
Less noise, sharper focus, and controls you can actually defend.
Scoring that sharpens with every case
You set the methodology, not a vendor.
Build rules around the risk factors that matter to you (e.g. customer, geography, channel, activity) aligned to your own framework, with your own thresholds and risk appetite.
Every ruleset is versioned and backtestable. You can prove a change before it goes live.
Because scoring factors in confirmed-risk outcomes from past cases, it keeps getting sharper as your book teaches it what risk really looks like. And when an auditor asks how a customer reached a given level, the answer is already in the system.
Score every customer automatically, and keep every score up to date
Define your framework, adjust it anytime, and Marble handles the rest.
Every customer gets a structured risk level, recomputed automatically – when they're onboarded, when their profile changes, when screening moves, or on the review cadence you set. So even quiet accounts don't drift out of date: Marble automatically refreshes any score that ages past the interval you set. No spreadsheets. No batch jobs. No periodic scramble to find out what changed months ago.
Compliance that runs itself isn't a someday promise. It's how customer risk scoring works in Marble today.
Define your risk framework, refine it whenever your risks or obligations change, and let Marble keep every customer current and sharpen with every case. Free your team for the decisions that actually need judgment.
See in our one-pager how Customer Risk Assessment fits your framework in the Marble documentation, or book a call to see it on your data.
