How it works

From bank behaviour to governance action.

Varqus converts transaction data into counterparty governance. Unknown entities become cases. Known entities are continuously reconciled: name and IBAN match, expiry status, yearly concentration, and escalation triggers.

Ingestion: bank API connectivity for real-time monitoring, or statement upload when API is not available.
Cadence: weekly or monthly operating cycles, with real-time alerts in the premium tier.

Operating flow

The flow is designed to be practical for SMEs: minimal manual work, strict logic, clear exceptions.

Select the client company

The platform user selects the client profile: known bank accounts, risk appetite thresholds, and active registries (KYB, KYS, KYC, KYA).

Ingest bank activity

Premium: bank API connectivity pulls transactions in real time.
Fallback: statement upload (PDF or export) is processed on demand. IBAN is mandatory and is always extracted.

Classify direction and counterparty type

For each transaction, Varqus identifies in or out, counterparty name, counterparty IBAN, amount, currency, and booking date. Incoming from private individuals is not treated as KYB. Outgoing to individuals is classified into KYA (HR context) or KYC (non-HR).

Match against the registry

Counterparty is matched against existing cases by IBAN and name. If the entity exists, the system verifies the name and IBAN match rule. Any mismatch is flagged.

Open cases for unknown entities

Incoming from unknown company: open KYB.
Outgoing to unknown company: open KYS.
The case is prefilled with counterparty name and IBAN. After completion, it is added to the KYB or KYS registry for future matching.

Accrue relationship totals

Every transaction between the client company and a verified counterparty is added to the yearly totals: total inflow, total outflow, and per-counterparty relationship totals.

Apply escalation triggers

The system flags exceptions and recommends actions based on rules: transactions above 2000 EUR, IBAN and name mismatches, check expiry approaching, and concentration thresholds.

Report and act

Depending on package: real-time alerts, weekly exception list, monthly governance review, registry updates, and EDD recommendations. Varqus then supports decision-making as an external line of defence.

Rules and triggers used in monitoring

Rule	Condition	Action
IBAN and name match	If counterparty exists in registry, transaction IBAN and name must match the stored record.	Flag mismatch. Recommend verification refresh or case review; treat as integrity concern.
Unknown entity	Counterparty not found in KYB or KYS registry.	Open KYB for unknown incoming company. Open KYS for unknown outgoing company. Prefill name and IBAN.
High-value transfer	Any single transaction above 2000 EUR.	Flag for review regardless of counterparty status.
Yearly concentration	From 01 January to 31 December: a single counterparty accounts for more than 20 percent of total inflow or total outflow.	Recommend EDD for that relationship. Include dependency reasoning in the report.
Expiry horizon	Any completed case is older than 12 months, or is approaching the 12-month deadline.	Flag as refresh due. Recommend refresh scheduling; mark status as verification not current.

The year is evaluated as a calendar year. Relationship totals and dependency ratios reset on 01 January, while case expiry remains a rolling 12 months from completion date.

Boundaries

Varqus is strictly B2B. We do not conduct private investigations and do not provide services that can be used to target individuals or companies. We process client-provided financial data to protect lawful business relationships and support governance decisions.

B2B only

Incoming from private individuals is not treated as KYB.

Individuals

HR-related flows map to KYA, other person-to-person flows trigger KYC rationale.

Auditability

Flags, case links, and event logs are retained for defensibility.

Contact

Tell us whether bank API connectivity is available, your transaction volume, and your cross-border exposure. We will recommend the correct cadence and package.

Request engagement

Share scope, regions, and bank connectivity. We respond with an operating proposal.

Book a call

Use a governance call to define risk appetite thresholds and registry ownership.

Start with Foundation

If uncertain, start monthly and upgrade to weekly or real-time once volume and exposure justify it.