Compliance, automated.

The problem with manual compliance monitoring

Most treasury compliance is retrospective. The hedge ratio gets checked at month-end. The counterparty limit breach gets discovered when someone runs the utilisation report. The concentration risk gets flagged in the board pack, three weeks after the trade that caused it.

By the time a manual compliance process surfaces a breach, the decision that caused it has already been made, the trade has already been executed, and the conversation with the board is already awkward.

Treasurii evaluates compliance rules continuously against your live positions. Breaches surface in real time — before the trade, not after.

Automated rule types

Treasurii's compliance engine evaluates seven categories of rule, configured per organisation and assessed automatically against live data:

Policy hedge ratio

Monitors your hedge ratio per currency pair against your written policy band. If your policy requires 60–80% coverage on EUR/GBP and your current ratio is 54%, the rule fires a warning automatically — not when someone remembers to check.

Concentration risk

Flags when a single currency pair represents more than your configured maximum share of total gross exposure. Prevents inadvertent over-reliance on a single pair without a board-level conversation.

Counterparty limits

Monitors credit utilisation per counterparty continuously. Warning at 75% utilised, breach at 100%. The Execute Trade modal shows live utilisation with a pending-trade preview before you confirm — so the limit check happens at decision time, not settlement time.

Exposure limits

Monitors total gross FX exposure against your board-approved limit. Warning at 80% utilised. If a new receivable would push you over the threshold, it surfaces immediately on capture.

Tenor limits

Checks that all open forward contracts fall within your maximum approved tenor. Forwards booked beyond your policy tenor are flagged — relevant for audit and for FCA best-execution documentation.

Regulatory obligations

Tracks regulatory filing deadlines and attestation requirements. Status displayed in the compliance dashboard with filing date and responsible party. Regulatory filings can be marked as submitted directly from the platform with an immutable timestamp.

Manual checks

User-defined compliance items that require human verification — board resolutions, internal sign-offs, annual policy reviews. Surfaced in the compliance dashboard alongside automated rules so everything is in one place.

Pre-trade enforcement

Compliance rules aren't just a monitoring dashboard. They're wired into the execution flow. Before any trade is submitted, Treasurii automatically checks:

• Would this trade push counterparty utilisation above the limit?
• Is the tenor within the approved policy range?
• Does this trade require a second approver based on size or instrument type?
• Does the currency pair have an active policy, and does this trade fall within it?

Trades that would breach a hard limit are blocked at submission. Trades that approach a soft threshold surface a warning and require acknowledgement. No trade can be executed that violates a configured hard limit — enforcement happens at the point of decision, not in the next compliance report.

Compliance dashboard

The compliance dashboard gives a single view of your organisation's policy standing at any moment:

• Compliance summary: overall pass rate across all automated rules, updated continuously
• Rule status table: per-rule pass / warning / fail with the specific threshold and current value
• Regulatory filings tracker: upcoming deadlines, filing status, submission history
• Audit trail: the last 10 significant events with user attribution and timestamp

Rules are configurable per organisation. You can add, edit, or deactivate rules without raising a support ticket — the rule engine is part of your platform, not a fixed template.

Audit trail

Every compliance event — a rule firing, a limit being approached, a filing being submitted, a policy override being approved — generates an immutable audit log entry. The trail includes who saw the warning, who acknowledged it, and what decision was made.

This is what turns "we have a compliance policy" into "we can prove we followed our compliance policy." The difference matters in a board review and it matters in a regulatory examination.

See it in action

The compliance engine is most useful to see against your own policy — your currency pairs, your counterparties, your regulatory obligations. A 30-minute demo will walk through how rules are configured and how they surface in the execution workflow.