CorphedgeVisit Website →
← Back to blog

Prospective Hedge Testing Under IFRS 9 and FRS 102

October 24, 2026
Prospective Hedge Testing Under IFRS 9 and FRS 102

Prospective hedge testing is the forward-looking check that a hedge will be effective, performed when you designate the hedging relationship and again at each reporting date. Under IFRS 9 it is no longer a numerical pass mark. You show that an economic relationship exists, that credit risk does not dominate, and that the hedge ratio matches what you actually use to manage risk. Under UK FRS 102 the rules are lighter still. This guide explains what each framework asks of you, what auditors look for, and where teams still go wrong.

Corphedge
Manage FX Risk With Greater Clarity
CorpHedge helps companies monitor currency positions and manage foreign exchange risk with real-time information and risk management tools.
Explore CorpHedge

TL;DR

  • Prospective testing asks whether the hedge is expected to work from now on. Under IFRS 9 it rests on three qualitative-led requirements, not the old 80-125% band.
  • Documentation at inception is mandatory, and it must describe how you will assess effectiveness and where ineffectiveness could come from.
  • IFRS 9 prohibits voluntary de-designation. If the relationship drifts, you rebalance rather than switch hedge accounting off.
  • UK entities on FRS 102 can often skip a quantitative effectiveness test at the start of a relationship, but must still document and measure ineffectiveness.
  • Most of the real work is judgment and data: proving forecast transactions stay highly probable and keeping treasury and accounting numbers aligned.

Table of Contents

What prospective hedge testing actually is

Hedge accounting lets you match the timing of gains and losses on a hedging instrument, such as an FX forward, with the exposure it covers. To qualify, you have to show the hedge is a sensible one. That demonstration has two time perspectives:

  • Prospective: will the hedge be effective going forward? This is done at inception and at each reporting date.
  • Retrospective: was it effective over the period just ended? This was a formal test under the old standard, IAS 39.

IAS 39 required both, with a rigid 80-125% bright-line threshold for the outcome. IFRS 9 dropped the quantitative retrospective test and the 80-125% threshold in favor of a principles-based model designed to align accounting with risk management. So today, when people search for prospective hedge testing, they usually mean the forward-looking assessment of the three IFRS 9 requirements, plus the ongoing monitoring that goes with it.

The three IFRS 9 requirements

According to the IASB's review of the hedge accounting requirements, prospective effectiveness testing means verifying three things.

Three prospective IFRS 9 hedge requirements

1. An economic relationship exists

The hedged item and the hedging instrument must be expected to move in opposite directions because of the same risk. For a sterling-based company with a forecast euro receipt and a forward to sell euros, the link is usually easy to argue: same currency pair, similar maturity. It gets harder when the hedge is a proxy, for example hedging a currency with a correlated one, or when timing and amounts differ.

The standard does not prescribe a method. Staff material on IFRS 9 notes that it does not specify how to assess the effectiveness requirements, so long as the method captures the relevant characteristics of the relationship. In practice treasuries choose from:

  • a critical terms match (notional, currency, maturity and settlement dates line up), which is a qualitative argument;
  • a regression or correlation analysis over historical data;
  • a scenario analysis that shocks the rate and compares the change in value of both sides.

The method must be written into the hedge documentation and applied consistently.

2. Credit risk does not dominate

Credit risk, whether the counterparty's or your own, should not be the main driver of value changes on either side. For plain vanilla forwards with a bank counterparty of good standing, this is typically a short paragraph of reasoning, refreshed when the counterparty's credit position changes materially. For long-dated or uncollateralized positions it deserves a closer look.

3. The hedge ratio reflects real risk management

The ratio between the quantity of the hedged item and the quantity of hedging instrument must be the same as the one you actually use for risk management. If treasury hedges 70% of forecast exposure, you designate 70%, not 100% because it looks tidier. This is the point of IFRS 9: accounting follows what the treasury does, not the other way round.

There is one more rule worth stating plainly. If you meet the first three requirements at inception but the ratio later drifts, you cannot just walk away from hedge accounting. That brings us to rebalancing.

Rebalancing instead of de-designation

The IASB's review points out that rebalancing is frequently misunderstood and underused. IAS 39 allowed voluntary de-designation. IFRS 9 prohibits it. If the relationship is still meeting the risk management objective but the hedge ratio no longer fits, you adjust the designated quantities of the hedging instrument or the hedged item.

This causes friction for groups that report under both IFRS and US GAAP, because US GAAP still permits voluntary de-designation. If your parent reports under US GAAP and your UK subsidiary under IFRS, agree on the process early, so the same hedge is not treated differently in the two sets of books.

A practical consequence: your prospective assessment should include a rule for when to rebalance. For example, a monthly review of the hedge ratio against the current forecast, with a documented trigger when actual exposure moves outside an agreed range.

Documentation: where audits are won or lost

It is easy to focus on the test and forget that formal documentation is a condition of hedge accounting. Under paragraph 6.4.1(b) of IFRS 9, as summarized in an IASB staff paper, at inception you must document:

  1. the hedging relationship;
  2. the risk management objective and strategy;
  3. the hedging instrument and the hedged item;
  4. the nature of the risk being hedged;
  5. how you will assess whether the effectiveness requirements are met, including the sources of ineffectiveness.

A hedge that passes every test but lacks this file at inception does not qualify. The documentation also has to be consistent with the treasury policy that is actually approved and followed.

For a worked layout, see our IFRS 9 hedge documentation example, which walks through a €2,000,000 exposure.

A step-by-step prospective test for an FX forward hedge

Here is a workable sequence for a UK company hedging a forecast foreign currency sale with a forward.

  1. Define the risk and the objective. State which currency risk you hedge and why, in line with the board-approved policy.
  2. Identify the hedged item. Describe the forecast transaction precisely: currency, amount range, expected timing, counterparty or customer group.
  3. Support "highly probable". Cash flow hedges of forecast transactions require the transaction to be highly probable. Keep evidence: contracts, order books, budgets, historical patterns.
  4. Identify the hedging instrument. Forward contract reference, notional, maturity, counterparty.
  5. Set the hedge ratio. Use the ratio treasury actually applies, and record it.
  6. Assess the economic relationship. Critical terms match, or a quantitative method where terms differ. Record the result.
  7. Assess credit risk. Note the counterparty rating or other evidence and whether it dominates.
  8. List sources of ineffectiveness. Timing differences, counterparty credit, forward points, differences in discount curves.
  9. Set review triggers. Reporting dates and events such as a change in forecast, counterparty downgrade or a new contract.
  10. Re-run at every reporting date, and rebalance if required.

Where judgment gets difficult

Removing the bright-line test did not make the exercise trivial. The IASB's 2026 post-implementation review reports that many preparers and auditors welcomed the change, but that the model still demands significant judgment, particularly in showing that forecast transactions remain highly probable amid geopolitical challenges, uncertain long-term contracts or deal-contingent transactions.

Two other pain points come from the same review:

  • Cost of hedging. Separating the time value of options, or forward points, can reduce volatility in profit or loss, but it requires hypothetical derivatives, and limited application guidance leads to inconsistent practice across firms.
  • Transition costs. Aligning accounting with risk management takes staff education, integration between treasury and accounting systems and updated documentation. The IASB expects those costs to be offset by a lower ongoing burden compared with IAS 39.

A common mistake is to keep running old retrospective 80-125% calculations out of habit. IFRS 9 does not require them. They create parallel work and can create disputes with auditors when a number falls outside a band that no longer has any standing. Keep a retrospective comparison as a management tool if it helps, but do not label it a compliance test.

Prospective testing under FRS 102

Many UK companies do not report under full IFRS. For them, hedge accounting sits in Section 12 of FRS 102, and the ICAEW publishes a helpsheet on hedge accounting under FRS 102 that gives short overviews of the three types of hedge accounting.

The FRC amended FRS 102 to bring it closer to international principles while keeping it accessible to less complex businesses. When it proposed the changes, it explained that entities would not have to assess quantitatively whether a hedge is effective at the start of the relationship, and that there would be no restrictions on discontinuing a hedge. The amendments issued in 2014 aimed to make hedge accounting more readily available where it fits the entity's risk management processes. Check the current edition of FRS 102 and your auditor's view for the precise requirements that apply to your accounting period, because the standard has been revised since those announcements.

In practice, FRS 102 reporters should still:

  • document the relationship, objective and strategy at inception;
  • be able to explain why the hedge is expected to offset the exposure;
  • measure and recognize any ineffectiveness.

If you may move to IFRS later, for example because of a new parent or a listing, building the IFRS 9 style file now saves rework.

Interest rate benchmark reform reliefs

If you hedge floating-rate debt, benchmark transition added special rules. Amendments to IFRS 9 introduced reliefs so that uncertainty during the move away from IBOR benchmarks did not force the end of hedging relationships; entities may assume, in prospective assessments, that the hedged risk or cash flows are not altered solely by that uncertainty. The EFRAG background is available at EFRAG. In the UK, the FRC likewise amended FRS 102 for interest rate benchmark reform to avoid unnecessary discontinuation of hedge accounting. For most FX-only hedgers, this is background rather than daily work.

Our perspective

We build tools for corporate FX risk, and the pattern we see is consistent: teams treat prospective testing as an accounting chore, when it is really a record of a risk decision.

If the policy says you hedge 70% of the next twelve months of forecast euro receipts, then the test file should read as the same sentence, with the same number, in the same currency. When treasury runs one set of numbers and accounting another, every reporting date turns into a reconciliation project. IFRS 9 was designed to remove that gap, and the teams that benefit most are the ones that actually close it.

Three habits make the difference:

  • Keep exposures, hedges, ratios and documentation in one place, so the file is a by-product of the process and not a separate exercise.
  • Write the review triggers down, so rebalancing is a routine action and not an argument at year end.
  • Treat ineffectiveness as information. If the hedge is not performing as expected, you want to know before the auditors do.

Our hedge performance analysis article covers how to show that risk actually fell after hedging, which is the natural companion to the prospective file.

— Bartas

Building the process with the right tooling

Spreadsheets can carry a handful of forwards. They get fragile as the number of currencies, entities and hedge relationships grows, particularly when the ERP, the treasury records and the accounting file each hold a different version of the exposure. Our write-up on ERP integration for hedging lists seven fields worth mapping so the data flows cleanly.

The Corphedge platform is built for corporate FX risk management. It brings currency position tracking, hedging strategy simulation, Value at Risk analysis and portfolio reporting into one place. If your team needs a second pair of eyes on a hedge program, our operational expert advice is available. For people new to hedging who want to understand the mechanics first, the FX hedging course is a one-off purchase at €220.

If you are weighing how hedge accounting connects to your wider program, these pages may help:

A checklist before your next reporting date

  • Is the hedge documentation dated at or before inception, and does it name the assessment method?
  • Does the designated hedge ratio equal the ratio treasury actually uses?
  • Is there current evidence that each forecast transaction is highly probable?
  • Has the counterparty's credit standing been reviewed since the last assessment?
  • Are sources of ineffectiveness listed and measured?
  • Does the file say when you would rebalance, and has anyone checked it against current exposures?
  • If you report under both IFRS and US GAAP, have you agreed how de-designation and rebalancing are treated in each?
  • Are you running old 80-125% retrospective calculations out of habit?

If you have more than a few ticks missing, start with documentation and the hedge ratio. Those two items cause the most trouble in audits and are the cheapest to fix.

FAQ

Is prospective hedge testing still required under IFRS 9?

Yes, in the form of a forward-looking assessment. At inception and at each reporting date you confirm the economic relationship, that credit risk does not dominate, and that the hedge ratio is the one used for risk management. What disappeared is the 80-125% numerical threshold and the quantitative retrospective test.

What is the difference between prospective and retrospective testing?

Prospective testing looks forward and asks whether the hedge is expected to be effective. Retrospective testing looked back over the period just ended. IAS 39 required both, while IFRS 9 keeps the forward-looking assessment and drops the quantitative retrospective test.

Do I need regression analysis to pass the test?

Not necessarily. IFRS 9 does not prescribe a method, so a critical terms match can be enough for simple hedges where notional, currency and dates align. Use regression or scenario analysis when terms differ or a proxy hedge is involved, and document your choice.

Does FRS 102 require the same testing as IFRS 9?

No. FRS 102 takes a more pragmatic approach and, as the FRC explained, does not require a quantitative effectiveness assessment at the start of a relationship in many cases. You still need documentation and you must recognize ineffectiveness. Confirm the current requirements with your auditor.

Sources