Home/Product/Governance and audit

A record that answers the supervisor for you.

Approvals, access and third-party controls are built into the work, and every action by the engine, the agent or a person is written to one log that cannot be tidied afterwards.

0%

of actions logged with who, when and why

0

people on every change that policy says needs two

0

click to an examiner package

0

entries that can be edited after the fact

Controls that live in the work.

Governance is not a separate system to keep in sync. It is how the platform behaves.

01

Four eyes where policy asks

Choose which actions need a second person. The platform will not let them happen any other way, and both names go on the record.

  • Approval rules you define
  • Enforced, not reminded
  • Both people recorded
Rules
Any rule changeAuthor plus a second officer
2 people
Cases
Closing a High or Severe alertAnalyst plus a senior analyst
2 people
Filing
Submitting a reportMLRO sign-off
MLRO
Access
Granting an admin roleTwo administrators
2 people
02

Access by role, checked all the time

Roles come from your identity provider, and gaps like missing MFA or a conflict of duties surface as soon as they appear.

  • SSO and MFA
  • Separation of duties checks
  • Joiners and leavers synced
Access risks2 open
High
J. Kowalski signs in without MFAJunior Analyst · local password
Fix
Medium
K. Nordmann can author and approve rulesTeam Lead · separation of duties
Review
Clear
Leavers removed within a daySynced from Okta · 3 this month
OK
03

DORA, evidenced

Your providers, their criticality, exit plans and review dates live next to the integrations they describe, ready for the register.

  • ICT third-party register
  • Exit plans and reviews
  • Incidents with their timeline
ICT third-party registerDORA
Critical
Blockchain analyticsExit plan on file · reviewed Aug 2026
Current
Critical
Identity verificationSecond provider configured
Current
Important
Travel Rule networkReview due in 21 days
Due soon
04

An examiner package in one click

Registers, trails, case chains and rule history export together, limited to what the examiner is entitled to see.

  • Drawn from the live record
  • Scoped to need-to-know
  • Nothing rebuilt for the visit
Examiner packageNeed-to-know
STR register4 reports
Audit trail16 events
Signed case chains6 cases
Rule versions and approvals12 changes
Human and agent differences1
Export examiner package

Every entry says who did it.

Machine or person, the log keeps them apart so a reader always knows which is which.

Engine

The engine logs its reasons

Every score and rule hit is written with the version of the rule that produced it.

Agent

The agent is always labelled

Anything Case AI drafts or suggests is marked as such, and differences from the final decision are kept.

Person

People sign in their own name

Approvals, escalations and filings carry a name, a time and a reason.

Show us what your supervisor asks for.

We will produce it from a sample programme, live, in the meeting.