Identity inconsistency
IBAN-name mismatch, structural ownership change, or missing rationale.
Operating flow
| Step | What happens |
|---|---|
| 1 | Client company scope, accounts, and threshold policy are configured. |
| 2 | Transactions are ingested and matched to known registry entities. |
| 3 | Unknown or changed entities open KYB, KYS, KYC, or KYA governance files. |
| 4 | Signals are evaluated against thresholds and escalation logic. |
| 5 | Varqus issues recommendations and maintains audit-ready records. |
What triggers escalation
Concentration pressure
Counterparty concentration above predefined yearly dependency limits.
Behavioural anomalies
High-value transfers, new coordinates, and pattern deviation events.
Execution model
Varqus operates as a managed governance layer. Monitoring produces signals, signals trigger review, and review produces decision gates for client leadership.
Annual refresh
Mandatory case renewal every 12 months.
Monthly monitoring
Periodic review of behaviour, concentration, and exceptions.
Real-time premium
API-driven alerts with reduced latency for high-exposure flows.