Exceptions and service levels
Clear the exception queue without clearing the control.
Operations holds the exception queues with live SLA countdowns and ageing, opens each record to show the checks that were actually run, names the residual risk, and assembles a release pack that stops at an authorised approver. Versidon does not release payments.
How it works
The queue, the checks and the handover in one place.
An exception is only resolved when someone can see what was verified and what was not. Versidon works the queue, records each check against the record it was run on, states what risk remains, and hands the pack to an authorised approver rather than acting on it.
- 01
Work the queue
Exceptions are presented with a live SLA countdown and ageing, so the item closest to breach is the item in front of you.
- 02
Run and record the checks
Each record opens to the checks that were actually run and their results — not a status badge asserting that checks happened.
- 03
Hand over, do not release
A release pack is assembled with the residual risk named, and stops at an authorised approver. The approval is a human act with an entitlement behind it.
What it produces
A resolution someone can stand behind.
Operational risk is where automation is most tempting and most dangerous. The output is a prepared handover: complete enough to approve quickly, honest enough to reject.
Live SLA countdowns
Each exception carries the time remaining against its service level, so prioritisation follows the commitment rather than the queue order.
Ageing visibility
Ageing across the queue, so an item that has been quietly deferred cannot stay quiet.
Per-record check detail
The checks actually run on a record, with results, visible to anyone reviewing the resolution afterwards.
Named residual risk
What remains unverified is stated in the pack. An approver is told what they are accepting, not only what was completed.
Release pack for an authoriser
A complete pack assembled and held at the authoriser step, with initiator, reviewer and authoriser kept distinct.
Maker-checker preserved
The agent holds its own least-privilege identity and never inherits a person's approval rights. Every action is logged with actor, entity and timestamp.
Where it stops
Versidon does not release payments.
This is a design constraint, not a configuration default. Versidon prepares the release pack, states the residual risk and stops. The release itself requires an authorised approver acting under their own entitlement, and the log records who that was.
The pack stops at the authoriser rather than past them. Nothing irreversible happens on its own.
Works with the rest of the platform
One record, one permission model, one audit trail.
Compliance
Alert triage, adverse media and a case narrative drafted for the MLRO — never filed without one.
Build your own agentsStudio
Compose agents against your policy sets and knowledge, evaluate them on labelled cases, and gate publish on the result.
Governance and auditControl
Model registry, agent registry, entitlements and an immutable event log covering every human and agent action.