FX overhedging and underhedging: keep hedge size aligned with the commercial exposure

Underhedging leaves part of an FX exposure open, while overhedging creates a hedge larger than the underlying commercial exposure and can introduce a new speculative position. This guide explains the mechanics, evidence, failure points and controls a UK business should understand before relying on the process.

What this means in practice

Underhedging leaves part of an FX exposure open, while overhedging creates a hedge larger than the underlying commercial exposure and can introduce a new speculative position. The practical question is whether the company can evidence the condition at the moment a payment, drawdown or hedge decision is made.

The right hedge ratio depends on exposure certainty, policy, timing and instrument flexibility, so forecast exposures are often hedged in layers rather than automatically at 100%. Translating these mechanics into a short checklist helps only if the checklist still points users back to the authoritative wording and current transaction data.

How the process works

The operating sequence should move from identification to validation, approval, external submission or notice, and then confirmation. For this topic, the critical mechanics are: The right hedge ratio depends on exposure certainty, policy, timing and instrument flexibility, so forecast exposures are often hedged in layers rather than automatically at 100%.

Timing should be planned backwards from the required result. Notice periods, value dates, bank cut-offs and internal approval windows can make a technically correct action late, so the process needs enough recovery time to repair data or obtain another consent. For this subject, the file should specifically reconcile underlying currency exposure, confidence level, expected date, existing hedges, hedge notional, policy range, cancellations, forecast revisions and rollover requirements. Those fields are not interchangeable with a generic approval record because they are the facts that determine whether this particular transaction remains inside the agreed rule.

The data and evidence that matter

At minimum, retain underlying currency exposure, confidence level, expected date, existing hedges, hedge notional, policy range, cancellations, forecast revisions and rollover requirements. If one of these items is uncertain, the case should remain open rather than being presented as fully resolved.

The record should distinguish internal intention from external outcome. An approved instruction proves what the company wanted to do; a bank acknowledgement, lender consent, statement entry or counterparty confirmation proves what happened outside the company.

Where the process can fail

A forecast sale can be reduced or cancelled after treasury has hedged the full amount, leaving the company with more currency sold forward than the eventual foreign-currency receipt. The financial cost of the problem usually increases as the payment, settlement, test date or financing event gets closer.

Fragmented ownership can hide exceptions. Legal, treasury, accounts payable and the bank may each see part of the issue, so one person should own the case until the final external status is known.

Worked example: test the mechanics

A business expects €10 million of sales and hedges 100%. Orders later fall to €7 million, leaving €3 million of forward sales without matching revenue. Treasury must decide whether to close, roll or offset that excess instead of continuing to label the entire hedge as risk reduction.

The example is intentionally simplified. In a live case the business should replace every illustrative amount, date and threshold with current source evidence, then repeat the test before treating cash, consent or hedging capacity as available.

Governance and control design

Reconcile hedges to refreshed exposures regularly and require escalation when hedge ratios move outside approved ranges. Where technology supports it, the rule should be enforced in workflow and exceptions should require explicit approval rather than a warning that can be ignored.

Routine review should include hedge notional as a percentage of confirmed and forecast exposure by currency and maturity bucket. Stable top-line activity can otherwise hide growing concentration, stale exceptions or shrinking liquidity headroom.

Change control matters as much as daily operation. When a bank changes a service, a facility is amended, an entity joins the group or a system is migrated, the company should retest the process from source data through final reconciliation. The management signal for this topic is hedge notional as a percentage of confirmed and forecast exposure by currency and maturity bucket. That indicator should have an owner and escalation threshold so treasury can intervene while the exposure is still manageable rather than discovering the problem only after the external deadline.

Contingency planning should be proportionate to value and urgency. The team should know the alternate approver, funding route, bank contact or manual fallback before a live fx overhedging and underhedging issue becomes time-critical.

Documentation should be short enough to use under pressure. A one-page operating checklist can point staff to underlying currency exposure, confidence level, expected date, existing hedges, hedge notional, policy range, cancellations, forecast revisions and rollover requirements while the fuller policy keeps the legal, technical or scheme background.

Periodic review should compare the documented procedure with what staff actually do. Where practice has drifted, management should either update the policy deliberately or restore the intended control rather than accept an undocumented compromise.

A tested fallback is part of the control. The team should know which pieces of underlying currency exposure, confidence level, expected date, existing hedges, hedge notional, policy range, cancellations, forecast revisions and rollover requirements are essential to act safely if the preferred system, approver or communication channel is unavailable.