PRODUCT

Features / Decision Engine

Decision engine for KYB routing and outcomes

Route cases by risk, standardize approvals and escalations, and capture reviewer-ready rationale for every decision.

Request a demo See routing logic

Risk-based routing • Approve / restrict / escalate • 100% logged rationale

Routing outcomes the Decision engine produces

Standardize how cases move through approval, restriction, or escalation, with rationale attached to each outcome

Auto-approve when required evidence is complete and risk signals stay within policy thresholds.

Apply restrictions when risk is acceptable but requires limits, extra verification, or monitored conditions.

Escalate edge cases that need EDD or manual resolution, with clear “why” and what’s missing.

Bilding blocks

DECISION ENGINE

Risk-based routing

Building blocks of KYB decisions

Risk signals: Evidence, screening, jurisdiction, and ownership inputs that drive routing.

Policy thresholds: Approve, restrict, or escalate based on your KYB rules.

Queues and escalation: Send edge cases to the right team with clear context.

Rationale and sources: Capture reason codes and sources so outcomes are audit-ready.

See routing examples →

Or view audit trail →

Rule examples

Example KYB routing rules

Real-world rule patterns teams configure. These examples show the “if this, then that” logic behind consistent outcomes.

If required evidence is complete and screening returns no matches, then Approve with rationale attached.

If evidence is complete but risk exposure requires limits, then Restrict and add a reviewer checklist for next steps.

If there is a potential screening match or insufficient identifiers, then Escalate to EDD with the missing details listed.

If ownership is complex or control is unclear, then Escalate with a required follow-up list (UBO proof, structure clarification).

Decision engine FAQ

Quick answers on routing rules, escalation, and rationale.

How are routing thresholds defined?

Thresholds are configured using your risk factors and policy rules, so outcomes stay consistent across reviewers and workflows.

What’s the difference between Restrict and Escalate?

Restrict applies limits or required steps while keeping the case within policy. Escalate routes the case to EDD or manual resolution when risk is unclear or exceeds thresholds.

How is decision rationale captured?

The decision engine records structured reason codes and supporting sources so outcomes can be reproduced and audited.

Can different workflows use different rules?

Yes. Teams can define routing logic per workflow so decisions match product, jurisdiction, and risk appetite differences.

What happens when risk changes after approval?

Changes can trigger a re-review workflow, typically handled with Monitoring, while keeping the original decision context attached.