Exposures, captured.

The problem with manual exposure tracking

Most treasury teams track FX exposure in a spreadsheet that someone built two years ago and nobody fully understands. It's updated monthly, sometimes weekly, almost never daily. It doesn't know about invoices that landed this morning. It definitely doesn't know about the forecast receivable your sales team logged yesterday.

The result: hedge decisions made on stale data. Ratios that look right on the 1st of the month and are wrong by the 15th. Board reports that require a manual reconciliation exercise nobody has time to do properly.

Treasurii replaces this with a live exposure ledger — updated continuously from your ERP, reconciled automatically, with every entry source-tagged and auditable.

ERP connectivity

Treasurii connects directly to your ERP to pull exposure data in real time. Supported systems include:

• SAP — S/4HANA and ECC via RFC or OData
• Oracle — Fusion and EBS via REST API
• NetSuite — via SuiteQL and REST API
• Xero — via Xero API (accounts payable and receivable)
• Sage — Sage 200 and Intacct via API
• Microsoft Dynamics — 365 Finance via Dataverse API

Each connection is read-only. Treasurii does not write back to your ERP. If your ERP is not listed above, contact us — we support custom integrations via CSV upload, SFTP, or webhook for systems we don't yet have a native connector for.

What gets captured

For each exposure, Treasurii records:

• Currency pair and direction (receivable vs payable)
• Amount in transaction currency and base currency equivalent at current mid rate
• Counterparty and entity
• Due date and invoice date
• Source system and sync timestamp
• Whether the exposure is hedged, partially hedged, or unhedged — and against which forward contract

Forecast cash flows can be entered manually or imported via CSV. They are flagged separately from confirmed payables and receivables so your hedge ratios are always calculated against a transparent denominator.

Row-level isolation

Each exposure is tagged to a legal entity within your organisation. If you run multiple entities — different subsidiaries, different jurisdictions — each entity's exposure data is isolated at the database layer. Users with access to Entity A cannot read Entity B's exposure data, even within the same organisation account. This is enforced by row-level security at the Postgres layer, not by application-level filtering.

Multi-entity support

Most mid-market corporates operate through more than one legal entity — subsidiaries, branches, overseas holdings, SPVs. FX exposure doesn't respect entity boundaries: a receivable in your German subsidiary and a payable in your UK holdco may net against each other, or may require separate hedging depending on your treasury policy and functional currencies.

Treasurii supports full multi-entity treasury management. Your organisation's entity hierarchy — parent, subsidiary, branch, SPV — is configured once in platform settings and then available across every module:

• Exposures are tagged to the entity that owns them
• Hedge ratios are calculated per entity, per currency pair, and in aggregate
• Reports can be run at entity level or consolidated across the group
• Users can be granted access to specific entities within the organisation — a subsidiary treasurer sees their entity, a group CFO sees everything

Isolation is enforced at the database layer. A user with access to Entity A cannot read Entity B's exposure or trade data, even if they are within the same parent organisation. This is structural, not application-level filtering.

Live MTM on exposure

Every exposure in Treasurii carries a live mark-to-market value — what that exposure is worth right now at the current mid-market rate, versus what it was worth when it was booked. Rates are sourced from live institutional feeds and updated continuously during market hours.

This means you know at any moment: your total FX exposure by currency, your total unhedged exposure by currency, and the unrealised P&L movement since your last hedge decision. Not on a monthly report — live, in the platform.

Audit trail

Every exposure record carries a complete audit trail — who created it, when, from which source system, and every change made to it thereafter. The audit trail is immutable. It cannot be modified or deleted by any user.

This is the foundation of board-ready reporting: when the auditor asks where a number came from, the answer is a timestamped, source-tagged entry that traces back to a specific invoice in a specific ERP, pulled at a specific time.

See it in action

The exposure module is the starting point for the full Treasurii lifecycle — from captured exposure through hedge decision, execution, settlement, and board reporting. The best way to see how it works with your currencies and your ERP is a 30-minute demo.