Treasurii
    • Exposure
    • Hedging
    • Execution
    • Settlement
    • Reporting
    • Compliance
  • How it works
  • ii² Intelligence
  • Pricing
  • Standards
Log in Sign up
    • Exposure
    • Hedging
    • Execution
    • Settlement
    • Reporting
    • Compliance
  • How it works
  • ii² Intelligence
  • Pricing
  • Standards
  • Log in

Platform · 02 Hedging

See the impact before you trade.

Live hedge ratios, what-if scenarios on every rate move, recommended cover calibrated to your policy. Decide with evidence, not instinct.

The problem with instinct-based hedging

Most treasury teams hedge on a schedule — monthly, quarterly, whatever the policy says — without a live view of what they're actually hedged against. The hedge ratio gets calculated in a spreadsheet on the day of the decision. The what-if analysis, if it exists at all, is a manual calculation someone does in a separate tab.

The result: hedge decisions that feel defensible but aren't fully evidenced. Board questions about "why did we hedge 70% this month" that get answered with "that's our policy" rather than "here's the rate move scenario that justified that ratio at that moment."

Treasurii makes the hedge decision the easiest part of treasury — because all the work happens before you click execute.

Live hedge ratios

Your hedge ratio in Treasurii is calculated continuously — not on the day you run the report, but right now. As new exposures land from your ERP and existing hedges are settled, the ratio updates automatically.

Ratios are shown per currency pair and per entity, against your written policy band. If you're at 64% and your policy target is 70%, the platform shows you that gap in real time — not at month-end.

What-if scenarios

Before executing any hedge, you can run a what-if scenario against your live exposure. Move the rate slider to any level and the platform instantly shows you:

  • The MTM impact on your total unhedged exposure at that rate
  • What your hedge ratio would be after adding a proposed new hedge
  • How the proposed hedge compares to your policy band
  • The rate at which your hedge would break even versus remaining unhedged

The what-if snaps to the current mid-market rate as its starting point, so scenarios are always grounded in live market data — not a rate someone typed in last week.

Policy as a guardrail, not a gate

Your treasury policy is configured in Treasurii as a set of rules — hedge ratio bands, tenor limits, counterparty concentration limits, instrument constraints. These rules surface as guardrails during the hedge decision, not as hard blocks.

If a proposed hedge would take you outside your policy band, the platform flags it clearly and requires an approval step. But it doesn't prevent you from acting. Treasury requires human judgment — the platform's job is to make sure that judgment is informed and documented, not to replace it.

Every policy override is logged with a reason and the authorising user. The audit trail is intact whether you followed the policy or not.

IFRS 9 alignment

Hedges booked through Treasurii are structured to support IFRS 9 hedge accounting from the moment of execution. The platform records the required documentation — hedge designation, economic relationship, hedged item reference, hedging instrument reference — automatically at the point of booking.

This doesn't eliminate the need for your finance team's IFRS 9 assessment, but it means the data they need for that assessment is already captured, correctly, in the audit trail.

See it in action

The hedging workspace is best understood by using it with your own exposure data and your own policy. A 30-minute demo will show you exactly how it works with your currencies and your counterparties.

Book a demo →
treasurii

AI-driven treasury risk management for international FX and crypto exposure.

Platform

  • Exposure
  • Hedging
  • Execution
  • Settlement
  • Reporting
  • Compliance
  • AI

Company

  • Book a demo
  • Partner with us

Legal

  • Terms
  • Privacy
  • Cookies
  • Security
© 2026 Treasurii Ltd LDN · —