All modules
    New in ComplianceSuite — Rules Engine

    Your policy. Live in production. No release needed.

    Rules Engine turns your written compliance policy into executable logic — visually. Compliance officers build, simulate and ship rules across KYC, AML screening, transaction monitoring and case management without touching code.

    0
    Lines of code required
    90d
    Back-test simulation window
    4-eyes
    On every rule change
    EDD onboarding rule
    Active
    1. 1
      Customer is onboarded
    2. 2
      Country is on enhanced-DD list
    3. 3
      PEP score ≥ 70
    4. 4
      Then: trigger EDD workflow + create ticket
    142
    Customers matched (90d)
    3.1%
    False-positive rate

    What rules can react to

    A trigger for every signal in your stack.

    Rules Engine is wired into every ComplianceSuite module — so the same logic that scores an onboarding can also pause a payment, request a document, or open a case.

    Customer events

    Onboarding, profile change, new beneficial owner, periodic review due.

    Risk signals

    Score deltas, watchlist hits, adverse media, sanctions refresh.

    Transactional patterns

    Velocity, structuring, geography, counterparty risk, channel switch.

    Time-based

    Periodic reviews, document expiries, SLA breaches, regulator deadlines.

    From draft to production in three steps

    Build it. Simulate it. Ship it.

    1. 1. Compose visually

      Drag conditions, group with AND/OR, attach actions. Every change shows you affected customers in real time.

    2. 2. Simulate against history

      Run the rule across the last 90 days of production data. See match counts, FP estimates and overlap with existing rules — before anyone is impacted.

    3. 3. Approve & activate

      Submit for four-eyes approval. Once signed off, the rule goes live with a versioned audit record showing exactly who approved what and when.

    Simulation result

    "EDD if PEP ≥ 70 AND high-risk country" — replayed against 90 days of onboardings.

    8,412
    Customers evaluated
    142
    Would have triggered
    3.1%
    Estimated false-positives
    12% overlap with existing rule "PEP-EDD-default" — consider deprecating before activation.

    Why teams adopt Rules Engine

    A safer way to change what your platform does.

    Visual no-code builder

    Drag conditions, group with AND/OR, branch by risk band — no engineering tickets.

    Simulation mode

    Replay any rule against the last 90 days of data before activation. See exactly who it would have flagged.

    Four-eyes approval

    Every rule change is reviewed and signed off by a second compliance officer before going live.

    Full version history

    Every edit, activation, deactivation and approver is captured for regulator inspection.

    Real-time evaluation

    Rules execute synchronously at decision points, asynchronously across the portfolio overnight.

    Library of starter rules

    Pre-built templates aligned to FATF, AMLD6, FCA, FinCEN and SAMA expectations — adapt, don't start blank.

    ↓ 5×
    Time from policy change to production
    0
    Engineering tickets per rule update
    100%
    Of changes audit-trailed & approver-signed

    What you get

    Native to ComplianceSuite. Aware of every module.

    Rules Engine sees the same data as KYC, AML Screening, Transaction Monitoring and Case Management — so a single rule can read a screening hit, score a customer and fire a ticket without crossing system boundaries.

    • Visual no-code rule builder with AND/OR grouping
    • Library of starter rules aligned to FATF, AMLD6, FCA, FinCEN, SAMA
    • 90-day simulation against production data
    • Conflict and overlap detection between rules
    • Real-time and batch evaluation modes
    • Four-eyes approval & versioned activation
    • Granular role-based authoring permissions
    • Immutable change log with diff per version

    Stop waiting for engineering to change your policy.

    See Rules Engine simulate one of your real policies against an anonymised dataset. 30 minutes, your typologies, your thresholds.