Continually watch the portfolio so only genuine change opens a case, and prove the monitoring never stopped. Say yes faster, without risk quietly moving between review dates.
“The moment a watchlist changed, the case was already open and half the context was sitting there. We stopped re-verifying customers we had verified weeks earlier.”MLRO · UK challenger bank · named reference on request
Event-driven perpetual KYC. Only a genuinely risk-changing event opens a case, orchestrated re-screening and your own configurable rules clear the rest, and the refresh runs on your risk model, not a vendor default.
Shipped, non-AI, and running on your own risk model. Watch the whole book, absorb the noise, and keep every re-screen on the trail.
Daily batch re-screening runs every customer against your feeds, and event-driven re-screening fires the moment a profile, watchlist, or registry record changes, opening a case only when the change actually matters, across 53 pre-integrated vendors from one integration. FATF R.10 and UK MLR 2017 Reg 28 make current CDD a standing duty, not an annual event.
See monitoringYour own configurable rules auto-clear the immaterial changes so they never reach an analyst, and only a genuine event lands in one risk-ranked inbox with entity and UBO context already beside it. This absorbs the industry problem where roughly 95% of alerts are false positives (Accenture, McKinsey, ACAMS), so always-on does not become a second full-time job.
See case managementConfigure the Customer Risk Assessment in Studio on the FATF four dimensions with your own weightings, thresholds, and tiers, watch high-risk customers more tightly, and backtest a change against your historical cases before it goes live. Live country-risk feeds draw on 209 countries at 16 indicators each.
See StudioWhen a new case opens for an already-verified customer, still-valid checks are referenced, not re-requested, so the customer is not asked twice and you only pay for the checks you truly need. Every re-screen, auto-clear, reuse, and decision writes to a write-once trail of 32 immutable event types with one-click regulator export.
See the audit trailWatchlist, registry, and screening feeds run from one integration, and you swap one by configuration when a better provider arrives. No lock-in, ever.
See all integrations ›With design partners, we are testing a Perpetual Monitor agent that explains what changed on a file and why it might matter, plus a Risk Model Copilot that suggests model changes for a human to review. Human-in-the-loop and opt-in, never an automatic decline. Early results in testing show investigation moving from an industry benchmark of about 22 hours toward roughly 12 minutes.
AI investigates, humans decide.
“The change lands, the case opens, and the trail shows the monitoring never stopped. That is the difference at examination.”MLRO · UK challenger bank · named reference on request
Refresh fires on genuine change, not a review date, so risk cannot quietly move between calendar cycles.
Watchlist change, case already open, no re-verifying customers cleared weeks earlier.
Ask for a referenceImmaterial changes auto-cleared, only genuine events reach an analyst.
Ask for a referenceRefresh on its own risk model, tuned in Studio without an engineering ticket.
Ask for a referenceWe publish no customer names. Discretion is the point.
FATF Recommendation 10 requires firms to keep customer due diligence "up to date", and UK MLR 2017 Regulation 28 makes current CDD a standing obligation, not a one-off event. How frequently a customer is reviewed is risk-based, but calendar-only refresh is increasingly scrutinised. An event-driven approach, triggered by genuine change, satisfies the obligation while removing the false-positive flood of blanket batch schedules.
You define the rules in Studio. Daily batch re-screening runs all customers against your feeds; event-driven re-screening fires the moment a profile, watchlist, or registry record changes. Your own configurable rules then determine whether that change is material enough to open a case or be auto-cleared. Nothing is auto-cleared by Zenoo's defaults without your approval.
No. When a new case opens for an already-verified customer, still-valid checks are referenced from the prior case, not re-requested. The customer is not interrupted and you are not charged twice. Only genuinely expired or changed checks trigger a new data pull.
Annual cycles review every customer on a fixed date regardless of whether anything has changed. Event-driven perpetual KYC triggers a review only when a genuinely risk-relevant event occurs: a watchlist match, a registry change, a beneficial ownership update. High-risk customers are watched more tightly; low-risk customers are not over-reviewed. The result is a continuous, auditable monitoring programme that does not require a team twice the size.
Every re-screen, auto-clear, check reuse, case open, analyst decision, and supervisor override writes to a write-once trail of 32 immutable event types with millisecond timestamps. The trail is exportable in one click for a regulator visit, designed to turn a two-week manual reconstruction into a 40-minute export (platform benchmark).
Bring your Monday inbox and we run perpetual monitoring live in 30 minutes.