Platform · Compliance
Compliance, monitored.
Seven rule types evaluated continuously against your live positions. i² surfaces the policy breach early, before it becomes a board problem.
The problem
Manual compliance is always retrospective.
By the time a manual process surfaces a breach, the decision that caused it is already made, the trade is already executed, and the conversation with the board is already awkward.
The rule engine
Seven rule types, evaluated against live data.
Policy hedge ratio
Your hedge ratio per currency pair against your written policy band. Policy says 60–80% on EUR/GBP and you're sitting at 54%, so the rule fires a warning automatically rather than when someone remembers to check.
Concentration risk
Flags when a single currency pair exceeds your configured maximum share of total gross exposure, so there's no inadvertent over-reliance on one pair without a board-level conversation.
Counterparty limits
Credit utilisation per counterparty, monitored continuously, with a warning at 75% and a breach at 100%. As you enter a trade, the workspace shows live utilisation with a preview before you confirm it.
Exposure limits
Total gross FX exposure against your board-approved limit, with a warning at 80% utilised. A new receivable that would push you over the threshold surfaces immediately on capture.
Tenor limits
Checks that every open forward falls within your maximum approved tenor. Forwards booked beyond your policy tenor are flagged for audit review.
Regulatory obligations
Tracks filing deadlines and attestation requirements, with the filing date and responsible party on the dashboard. Filings can be marked submitted from the platform with an immutable timestamp.
Manual checks
User-defined items that need human verification, such as board resolutions, internal sign-offs and annual policy reviews, surfaced alongside the automated rules so everything lives in one place.
Every rule is configured per organisation: add, edit, or deactivate it yourself, no support ticket. The rule engine is part of your platform, not a fixed template.
See it in action
Your policy standing, live.
Every rule scored pass, warning, or fail against live positions, with i² surfacing the breach in the workflow before it ever reaches a report.
See it on your policyPre-trade checks
Caught at the point of decision, not the next report.
Your policy runs as you work, not as a monthly review. As you enter a trade, i² checks it against your rules: a soft threshold surfaces a warning to acknowledge, and a hard breach is flagged before you book it, so a limit-breaking trade is caught at the point of decision, not found in the next report.
Flagged before you book: a hard breach surfaces the moment you enter the trade.
Warning surfaced; requires acknowledgement to proceed.
Every trade is checked against policy:
- 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?
The dashboard
One view of your policy standing, with the trail to prove it.
Compliance summary
Overall pass rate across every automated rule, updated continuously: one number for your policy standing at any moment.
Rule status table
Per-rule pass, warning, or fail, with each row carrying the specific threshold and the current value that triggered it.
Regulatory filings tracker
Upcoming deadlines, filing status, and full submission history. Nothing tracked in a side spreadsheet nobody owns.
Immutable audit trail
Every compliance event logged: who saw the warning, who acknowledged it, what decision was made. It turns “we have a compliance policy” into “we can prove we followed it,” for a board review or a regulatory examination.
See the compliance engine on your own policy.
A 30-minute demo: your currency pairs, your counterparties, your regulatory obligations. How rules are configured, and how they surface in your day-to-day workflow.