← Back to blog

Treasury Controls for Hedging: A Practical Framework

October 26, 2026
Treasury Controls for Hedging: A Practical Framework

Treasury controls for hedging are the policies, limits, approvals, checks and records that make sure every hedge matches a real exposure, is executed by someone authorized, is confirmed independently and is reported honestly. Without them, a hedge meant to reduce risk can become a source of it. This guide walks through the controls a UK finance team needs, in the order a hedge moves through the business: exposure, policy, authorization, execution, confirmation, accounting and monitoring.

Corphedge
Bring Currency Risk Into View
CorpHedge gives finance teams tools to manage currency risk, view currency positions in real time and apply risk strategies.
Explore CorpHedge

TL;DR

  • A hedging control framework answers five questions: what are we hedging, who may decide, who may execute, who checks, and how do we prove it.
  • Write a short hedging policy with named owners and approval thresholds. Keep it specific enough to act as a guardrail, but not so detailed that it needs rewriting every quarter.
  • Separate the people who trade from the people who confirm and record. Add periodic checks from outside the FX function.
  • Document each hedge relationship at inception if you apply hedge accounting, and test effectiveness as the rules require.
  • Monitor hedge ratios, counterparty exposure, valuations and cash effects on a fixed cadence, and report breaches to the CFO.

Table of Contents

What treasury controls for hedging are meant to prevent

Most hedging losses that make the news are not market losses. They are control failures: a hedge nobody authorized, a position that was never reconciled, a valuation nobody challenged, or a forecast that turned out to be fiction while the derivative stayed live.

The AICPA's guide on financial instruments (2020) lists the typical failure points. It says inadequate confirmation and reconciliation, inappropriate documentation, or undue reliance on valuation techniques can lead to inaccurate recording, processing, valuation or risk measurement of financial instruments. The same guide defines market risk as the risk that fair values or future cash flows fluctuate because of changes in market prices, including currency, interest-rate and commodity prices. Hedging exists to manage that risk. Controls exist to manage the risk of the hedging itself.

In practice, a control framework protects against six things:

  1. Hedging something that does not exist. The exposure was forecast too optimistically, or already netted internally.
  2. Hedging the wrong amount. Over-hedging turns a hedge into a speculative position. Under-hedging leaves the budget rate unprotected.
  3. Unauthorized or off-policy trades. Someone executes an instrument, tenor or size the board never approved.
  4. Errors and fraud in processing. A wrong rate, wrong value date or wrong counterparty goes unnoticed because one person handled the whole chain.
  5. Counterparty and liquidity surprises. Mark-to-market swings create collateral calls or concentrate exposure on one bank.
  6. Misreporting. Hedge accounting fails its tests, or management accounts show a number nobody can reconcile.

Each control below maps to one or more of these.

Start with verified exposures

The first control sits before any trade. A hedge is only as good as the exposure underneath it, so treasury needs a repeatable way to verify what is being hedged.

A workable exposure control has four parts:

  • A single exposure register. One list of foreign-currency receivables, payables, forecast sales and costs, intercompany loans and net investments, owned by treasury and fed by finance and procurement.
  • Confidence tiers. Separate contracted or invoiced flows from budgeted or forecast ones. Hedge ratios should fall as certainty falls. Signed contracts can carry a high ratio; a budget line three quarters out cannot.
  • A refresh cycle. Exposures change when orders land, prices change or a customer pays late. Refresh the register on a fixed schedule, monthly for most mid-sized businesses and more often when volumes are volatile.
  • A reconciliation between hedges and exposures. Every live hedge should link to the exposure it covers. A hedge with no linked exposure is a flag. An exposure above the policy threshold with no hedge is also a flag.

The linked-hedge rule is the single most useful check for avoiding both over- and under-hedging. We cover the correction routine in more detail in our guide on how to stop overhedging and underhedging, and the different exposure types in our treasury guide to types of exposure hedging.

If your hedge program is meant to qualify for the UK EMIR exemption for non-financial counterparties, the exposure link matters even more, because the hedge has to be demonstrably tied to commercial activity. Our note on the UK EMIR hedging exemption explains how to turn risk targets into hedges that fit.

Write a hedging policy that works as a guardrail

A hedging policy is the control that every other control refers back to. It does not need to be long. Four to six pages is normal for an SME, and the useful ones fit on fewer.

A good policy covers:

  • Objective. Protect the budget rate, margin or cash flow; not make money from FX.
  • Permitted instruments. Forwards, plain-vanilla options, swaps, and so on. Anything else needs explicit approval.
  • Hedge ratios and tenors. Minimum and maximum percentages by time bucket and by certainty tier.
  • Counterparty rules. Who you may deal with, and the limit for each.
  • Authority and approval limits. Who can approve and execute, up to what size.
  • Reporting and review. What is reported, to whom, and how often the policy is reviewed.

On balance, aim for specific limits with room to operate. Policies that name every market scenario need constant revisions, and policies that are too vague give nobody anything to check against. If you want a starting structure with sample ratios, our compact FX hedging policy template is a reasonable base to adapt.

Assign owners and approval limits

Controls fail when nobody owns them. The usual split in a UK mid-sized company is a policy owner, normally the CFO or finance director, and an execution owner, such as a finance manager or treasurer. One adviser's 2026 guidance for UK SMEs illustrates tiered approval thresholds by deal size, with larger trades escalating to the CFO and then the board. Treat any figures like that as an example, not a standard: set your own thresholds against your balance sheet, the volatility of your cash flows and your board's risk appetite.

A simple way to calibrate is to ask what loss from one wrongly executed trade the business could absorb without a conversation with the board. Set the execution owner's limit below that, the CFO's limit above it, and require board approval for anything outside the policy's permitted instruments regardless of size.

Authorize, execute, confirm and record

Four stages of hedge trade control

This is the part of the process where most operational errors happen, and where segregation of duties does the most work.

Segregate duties

The person who agrees a hedge should not be the person who confirms it with the bank, books it in the ledger and signs off its valuation. In a small team, you cannot always have four people, but you can design the workflow so that at least two independent people touch every trade, and so that no one can both create and release a payment or booking on their own. For a phased route to get there, see our guide on fixing FX segregation of duties in 30 to 90 days.

Authorize and execute within limits

The professional guidance for corporate foreign-currency policies from the Association for Financial Professionals points to clear authorization of the individuals allowed to negotiate and execute transactions, periodic spot checks by treasury staff, and annual compliance testing by someone outside the foreign-currency function, such as internal audit. That is a sound minimum. In practice:

  • Keep a signed list of authorized traders and their limits, reviewed at least yearly and whenever staff change.
  • Require a recorded rationale for every hedge: which exposure, which policy bucket.
  • Where possible, obtain competing quotes, or record why you did not.
  • Execute only through counterparties on the approved list.

Confirm independently

Hedges are usually documented under an ISDA Master Agreement, and the confirmations produced by the bank's back office should be promptly reviewed for errors by the company's treasury or financial officers. The control is that someone who did not trade checks the confirmation against the trade ticket: currency pair, amounts, rate, value date and settlement instructions. Unmatched confirmations should be escalated within a day, not left to the month-end.

Record what happened

Good trade records are what let you reconstruct events during an audit or a dispute. The FCA's record-keeping rules in COBS 18 Annex 2 apply to regulated firms handling client orders rather than to a corporate treasury, but they are a useful model: they require firms in scope to record, immediately after executing an order, the client, instrument, unit and total price, quantity, counterparty and the person responsible for execution. Borrow that discipline. Your trade log should hold the same fields, plus the linked exposure and the approver, stamped at the time of the deal.

One more cost control is worth adding at the edge of the business. Currency conversion costs also hide in payment flows that never reach treasury, such as customer checkout. Our partners' piece on FX costs in multi-currency checkout shows the questions to ask there. Treasury should know where those flows sit, even when it does not run them.

Document hedges and satisfy the accounting rules

If you want the profit and loss account to reflect the economic purpose of a hedge, you need hedge accounting, and hedge accounting is a documentation discipline first.

HMRC's Corporate Finance Manual summarizes what applies to UK companies under the older rules. At inception, you should formally document the hedging relationship: the risk management objective and strategy, the hedging instrument, the hedged item or transaction and the risk being hedged. For cash flow hedges, the forecast transaction must be highly probable and effectiveness must be reliably measurable.

The same manual explains that companies applying IAS 39 or FRS 26 must also carry out a prospective assessment of hedge effectiveness to show the hedge is expected to be highly effective in achieving offset. Check which standard your group actually applies, because IFRS 9 and the FRS 102 options differ in their tests. Your auditors will tell you which applies.

The control checklist here is short:

  • A hedge designation memo, signed before or at inception, not reconstructed later.
  • A named person responsible for effectiveness testing, separate from the trader.
  • A calendar of test dates and a record of results.
  • A trigger for what happens when a forecast transaction is no longer highly probable: de-designate, document, and tell the CFO.

If you want to design hedges that stay consistent with accounting treatment, our article on accounting-aware dynamic hedging with hedge bands shows how bands can reduce the number of re-designations.

Monitor positions, counterparties and cash

Once hedges are live, the controls shift to monitoring. This is where many policies are weakest, because the work is routine and nobody's name is on it.

A practical cadence looks like this:

What to monitorTypical frequencyOwnerEscalate when
Hedge ratio by currency and bucketWeekly or monthlyTreasurerOutside policy range
Mark-to-market of each hedgeMonthly, more often if volatileTreasurer, checked by financeValuation differs from bank's by more than an agreed tolerance
Counterparty exposure vs limitWeeklyRisk or treasuryUtilization near limit
Exposure register vs hedge registerMonthlyTreasurer and FP&AUnlinked hedge or unhedged exposure
Cash and collateral needsWeeklyTreasuryForecast liquidity shortfall
Policy compliance reportQuarterlyCFOAny breach

The cadences are a starting point, not a standard. Adjust them to volumes and to how fast your exposures move.

Counterparty exposure

Counterparty limits should reflect more than the notional amount of your trades. Potential future exposure matters, but so do concentration across banks and the quality of each counterparty. Our piece on FX counterparty limits explains why risk teams need more than a single PFE number.

Valuations

Treat bank valuations as a starting point. Have someone independent of the trader compare them with a separately sourced market rate, and record any difference. The AICPA guide quoted earlier names undue reliance on valuation techniques as a risk in itself, and a simple second view is the cheapest control against it.

Cash-flow effects

A forward that is deep out of the money is a liability on paper and a possible margin or credit-line issue in practice. Monitor the cash needs of your hedges as part of your liquidity forecast, and agree in advance who may draw on facilities if cash is needed.

Using value at risk as a control

Some teams set hedging limits on a value-at-risk basis: the policy states how much potential loss from currency moves the company will tolerate, and hedges are sized to stay inside it. This turns a board's risk appetite into a number that can be monitored. It still needs the controls above, because the model is only as reliable as the exposure data feeding it.

Perspective: controls should be simple enough to run every week

We talk to finance teams that have excellent policies and poor routines. The document is approved, the thresholds are sensible, and yet the exposure list lives in one spreadsheet, the trades in another and the bank confirmations in an inbox. When something goes wrong, nobody can say which hedge covered which exposure.

Our view is that a control you cannot run every week is a control you do not have. That is why we build around a few principles: one view of exposure, one record per hedge linked to the exposure it covers, limits that are checked automatically rather than remembered, and reports that a CFO can read in minutes. Smaller companies do not need an institutional treasury department to get this right. They need fewer tools, clearer ownership and alerts that arrive before a breach, not after.

Start with the controls that are cheapest and prevent the most damage: the linked-hedge rule, the second pair of eyes on every confirmation, and a monthly policy-compliance report to the CFO. Add the rest as the program grows.

— Bartas

Where a platform helps

Spreadsheets can hold every control above, until volume, staff changes or audit requests expose their limits. The Corphedge platform brings together currency position tracking, hedging strategy simulation, value at risk analysis, portfolio reporting, live market data and automated notifications, so exposure, hedges and limits sit in one place. You can see how it works on our product tour, or read how hedging based on value at risk fits a policy. Operational expert advice is also available through our features page.

If your team is building controls from scratch, our FX hedging course is a one-off €220 purchase. We are also expanding to Poland and Sweden, so groups with subsidiaries there can talk to us about covering those exposures.

A 30-day plan to put the controls in place

You do not need a project to start. A sensible order for a UK finance team:

  1. Week 1: Inventory. List exposures, live hedges, counterparties and who currently does what. Mark every step performed by one person alone.
  2. Week 2: Policy. Draft or refresh the policy: instruments, ratios, limits, owners and approval thresholds. Take it to the CFO.
  3. Week 3: Workflow. Separate trading from confirmation and booking. Set up the trade log with the fields listed above and the linked exposure.
  4. Week 4: Monitoring. Agree the reporting calendar, the escalation triggers and the first compliance report. Schedule the annual independent test.

After that, review the policy at least yearly. Public bodies subject to HM Treasury's guidance on managing foreign exchange exposure are expected to review their FX policy document annually and to seek Treasury consent for novel or contentious transactions. Private companies are not bound by that rule, but an annual review is a sound habit for any board.

For a wider picture of how currency risk relates to your other exposures, see currency risk vs market risk and our overview of advanced strategies to reduce corporate forex risk.

FAQ

What are the main treasury controls for hedging?

The core set is a written hedging policy, verified exposures, approval and trading limits, segregation of duties, independent confirmation of every trade, hedge documentation, and regular monitoring of ratios, counterparties and valuations. Each one answers a specific risk, from unauthorized trades to misreporting.

Who should approve a hedge?

The policy should name this, typically with a finance manager or treasurer executing within a set limit, the CFO approving above it, and the board approving anything outside the policy. The thresholds depend on your size and risk appetite, so set them against what a single error would cost you.

Do UK companies have to use hedge accounting?

No, it is an election. If you choose it, you must document the hedge at inception and test effectiveness as the applicable standard requires. Without it, derivative gains and losses can hit profit and loss before the hedged transaction does, so confirm the treatment with your auditors.

How often should hedging controls be reviewed?

Review the policy at least once a year and after any major change in the business, such as a new market or a new banking relationship. Monitoring runs on a faster cadence: hedge ratios and counterparty limits weekly or monthly, and a compliance report to the CFO each quarter.

Sources