Home/Product/Rules and policy

Policy in plain language, tested before it runs.

Write a rule the way you would say it. Avus reads each part, asks when something is ambiguous, tests it against your own history, and waits for a second officer before anything goes live.

Book a demoSee how it works

From a sentence to a live control.

The people who own the policy can write it, and every change leaves a record of who, when and why.

01

Understood, part by part

Avus reads the action, the customer, the threshold and the counterparty in your sentence, and asks rather than guesses when a part could mean two things.

  • No rule language to learn
  • Questions instead of assumptions
  • The engine runs exactly what you approved

Hold outgoing transfers above €100,000 for institutional clients to any VASP with incomplete Travel Rule data.

Avus asksShould €100,000 apply to each transfer, or to the total over 24 hours?
Each transferTotal over 24 hours
02

Tuned to each customer type

Retail customers, companies, private clients and institutions carry different risk. Each gets rules and thresholds that fit it.

  • Separate thresholds by segment
  • Early-tenure and dormancy checks
  • One policy, many profiles
Active rules by customer typePolicy v12
Retail · individuals38 rules · from €1,000
Business · companies44 rules · velocity
Private clients21 rules · source of funds
Institutions29 rules · Travel Rule
Unhosted wallets12 rules · ownership
03

Tested against your own history

Before a change goes live, it runs over months of your real transfers, so you see how many alerts it would raise and whether it would miss anything that mattered.

  • Backtests on your data
  • Alert volume before and after
  • Missed filings shown first
Version 3 against version 4180 days of your history
Alerts, v357
Alerts, v444
Filed cases missed0

Thirteen fewer alerts, and every case that led to a filing would still have been raised.

04

Four eyes before anything goes live

Every change is staged, versioned and approved by a second officer, and the full history stays readable for a supervisor.

  • Staged, then approved
  • Every version kept
  • Roll back in one step
R-114 historyFour-eyes
v4
Threshold tuned for new retailK. Nordmann · approved by P. Dupont
Awaiting
v3
Counterparty list widenedP. Dupont · approved by J. Jansen
Live 12 Aug
v2
Tenure window 30 daysJ. Jansen · approved by P. Dupont
Retired

You set the policy. The engine keeps to it.

Plain language on the way in, deterministic behaviour once it runs.

Person

Officers write and approve

The people accountable for policy write the rules, and a second officer signs off every change.

Agent

The agent reads and asks

It turns your sentence into parts and asks about anything ambiguous. It never changes a rule on its own.

Engine

The engine runs it exactly

Once approved, the rule runs the same way on every transfer until someone changes it on the record.

Where a rule shows up.

A rule raises alerts in monitoring, leaves its approvals in governance and is quoted in every case it touches.

Monitoring and alerts

Screening and scoring on every transfer, and a calm, reason-first queue.

Explore

Governance and audit

Approvals, access, DORA records and a log that cannot be tidied.

Explore

Investigation and cases

Case AI explores the chain and writes the reasoning. You decide.

Explore

Bring a rule you run today.

We will write it in plain language with you, backtest it on sample data and show the approval trail.

Book a demoSee how rules raise alerts