A Hedgebook exposure report is not a hedge instruction

Separate exposure measurement from hedge authorization

Hedgebook's official record documents FX exposure and risk-management tools. The direct answer is that an exposure report can organize treasury information, but it is not a hedge instruction. A decision still requires the underlying business exposure, legal entity, currency or rate basis, amount, timing, certainty, accounting treatment, existing offsets, policy objective, limits, eligible instruments, counterparty capacity, market conditions, and named approval authority.

Treasury should retain a decision record that distinguishes forecast, committed, recognized, and contingent exposures. It should identify source transactions, entity, currency, value dates, confidence, natural offsets, current hedges, policy coverage range, proposed action, instrument and tenor, rationale, limit use, approvers, execution channel, and residual risk. A dashboard percentage or suggested position should never become an executable instruction by implication.

Reconcile the exposure population before acting

Exposure data can arrive from ERP ledgers, orders, invoices, procurement, payroll, debt systems, forecasts, bank records, and manually maintained assumptions. Duplicates, canceled transactions, changed dates, intercompany items, netting, unrecorded commitments, late actuals, and currency conversions can materially change the result. The report needs a visible population, observation time, exchange-rate source, transformation, and reconciliation state.

A controlled test should trace one displayed exposure back to every contributing record and forward to the approved decision. It should cover partial settlement, forecast replacement by an invoice, changed payment timing, intercompany elimination, currency triangulation, corrected master data, missing feeds, manual overrides, and a hedge that no longer matches the exposure. Exceptions should remain visible instead of being forced into an aggregate number.

Keep policy, execution, accounting, and settlement distinct

Risk appetite and treasury policy determine which exposures may be hedged, within which limits, using which instruments and counterparties. Execution creates a trade that then requires confirmation, settlement, valuation, accounting assessment, collateral or cash handling where relevant, monitoring, and closeout. A report may support several of those steps without owning all of them.

A buyer demonstration should ask Hedgebook to show source ingestion, exposure versions, netting and aggregation, market-data timestamps, overrides, policy limits, approvals, segregation, audit history, exports, and links to trades and valuations. The organization should separately verify bank or platform execution, counterparty confirmation, settlement, hedge designation, effectiveness assessment, journals, disclosure, and residual exposure under qualified treasury and accounting ownership.

Keep Hedgebook claims inside the official record

The registered Hedgebook page establishes current provider positioning for FX, interest-rate and commodity risk-management software, reporting, analytics, exposure tools, and financial-instrument valuations. It does not establish complete exposure data, a suitable hedge, an authorized instruction, correct execution, effective risk reduction, accounting sufficiency, fair value for a particular purpose, or a financial outcome.

Treasury Operations Review reviewed the official source on August 19, 2026 and did not operate a customer environment. Buyers should verify the current product, source systems, exposure definitions, market data, models, currencies and instruments, policy controls, approvals, user roles, audit history, valuation scope, accounting support, integrations, exports, implementation, and service boundaries before using a report in a consequential decision.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Treasury Operations Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.