How to Audit Hedge Accounting Under IFRS 9

Why hedge accounting under IFRS 9 creates audit risk

Your client tells you they “hedge the euro-dollar exposure” on a €15M USD-denominated purchase commitment. You ask for the hedge documentation. What comes back is a one-paragraph email from the CFO to the treasury manager, dated two months after the derivative was entered into. There is no formal designation, no effectiveness assessment, and no link between the hedging instrument and the hedged item that satisfies IFRS 9.6.4. The derivative is on the balance sheet at fair value. The question is whether the €620K gain sitting in other comprehensive income should be there, or whether it belongs in profit or loss.

IFRS 9 hedge accounting requires an entity to formally designate and document the hedging relationship at inception (IFRS 9.6.2.1), demonstrate that the relationship meets the qualifying criteria in IFRS 9.6.4 (economic relationship, credit risk does not dominate, hedge ratio reflects the actual quantity hedged), and assess effectiveness on an ongoing basis using a forward-looking method rather than the retrospective 80–125% bright-line test from IAS 39.

Hedge accounting is optional. An entity can hold derivatives and recognise all fair value changes in profit or loss without applying hedge accounting at all. When an entity elects hedge accounting, it is choosing to override the default measurement rules for derivatives in order to match the timing of gains and losses on the hedging instrument with the hedged item. That election comes with conditions, and your job is to verify those conditions are met.

For mid-market European entities, hedge accounting typically appears in two situations. The first is foreign currency hedging: a Dutch manufacturer with USD-denominated sales enters into forward contracts to lock in the EUR/USD rate on forecast revenue. The second is interest rate hedging: an entity with a variable-rate bank loan enters into an interest rate swap to convert the floating rate to a fixed rate. Both are legitimate economic hedges. Whether they qualify for hedge accounting under IFRS 9 depends entirely on whether the entity met the documentation and qualification requirements.

The shift from IAS 39 to IFRS 9 changed the effectiveness testing framework. IAS 39 required a retrospective 80–125% quantitative effectiveness test. IFRS 9 replaced this with a forward-looking, principles-based assessment (IFRS 9.6.4.1(c)). The 80–125% bright line is gone. Instead, the entity must demonstrate that an economic relationship exists between the hedging instrument and the hedged item, that credit risk does not dominate the value changes, and that the hedge ratio is consistent with the entity’s actual risk management strategy. This is more flexible than IAS 39, but it also means the entity needs to document its qualitative reasoning rather than just passing a numerical test.

Mid-market entities sometimes treat the removal of the 80–125% test as a relaxation that reduces their documentation burden. It doesn’t. IFRS 9.6.4.1 still requires formal designation and documentation at inception, and IFRS 9.B6.4.1–B6.4.6 specifies what that documentation must include. An undocumented hedge relationship does not qualify, regardless of how economically effective the hedge actually is.

The qualifying criteria you test at inception

IFRS 9.6.4.1 lists the conditions that must all be met at inception for a hedging relationship to qualify. You test each one independently.

The first condition is that the hedging relationship consists only of eligible hedging instruments and eligible hedged items (IFRS 9.6.4.1(a)). For hedging instruments, IFRS 9.6.2.1–6.2.6 specifies which instruments qualify. A derivative measured at fair value through profit or loss qualifies. A non-derivative financial asset or liability measured at fair value through profit or loss can qualify as a hedge of foreign currency risk only. The most common hedging instruments in mid-market files are forward foreign exchange contracts and interest rate swaps. Both qualify.

For hedged items, IFRS 9.6.3.1–6.3.7 casts a wide net: a recognised asset or liability, an unrecognised firm commitment, a highly probable forecast transaction, or a net investment in a foreign operation. The hedged item must be reliably measurable. Forecast transactions must be “highly probable” under IFRS 9.6.3.3. That probability assessment is where audit judgment concentrates. A forecast transaction that the entity has budgeted but has no historical pattern of executing is not automatically highly probable. Verify the probability assessment against historical data and current order books.

The second condition (IFRS 9.6.4.1(b)) requires formal designation and documentation at inception. This is covered in the next section.

The third condition (IFRS 9.6.4.1(c)) is the effectiveness requirement. The hedging relationship must meet all of these:

• There is an economic relationship between the hedging instrument and the hedged item (IFRS 9.B6.4.4–B6.4.6)
• The effect of credit risk does not dominate the value changes that result from that economic relationship (IFRS 9.B6.4.7–B6.4.8)
• The hedge ratio of the hedging relationship is the same as that resulting from the quantity of the hedged item that the entity actually hedges and the quantity of the hedging instrument the entity uses (IFRS 9.B6.4.9–B6.4.10)

The economic relationship test is usually straightforward for vanilla hedges. A USD/EUR forward contract has an obvious economic relationship with a USD-denominated forecast sale. Where the test gets harder is when there is a basis difference. If the entity hedges Brent crude oil purchases with WTI crude oil futures, the economic relationship depends on the statistical correlation between Brent and WTI prices. IFRS 9.B6.4.4 requires the entity to demonstrate that the hedging instrument and hedged item have values that “generally move in the opposite direction because of the same risk.” For proxy hedges with a basis difference, this requires quantitative support.

What the hedge documentation must contain

IFRS 9.6.4.1(b) and IFRS 9.B6.4.1 set out the mandatory documentation elements. Every hedge relationship file should contain all of the following:

The entity’s risk management objective and strategy for undertaking the hedge. This is not a generic statement about the entity’s risk management policy. It is a specific explanation of why this particular hedging relationship was designated. For a Dutch importer hedging USD purchases: “The entity designates this forward contract to hedge the foreign currency risk arising from the forecast purchase of raw materials denominated in USD, consistent with its policy of hedging committed foreign currency outflows exceeding €500K.”

Identification of the hedging instrument: the specific derivative contract, its notional amount, maturity date, and counterparty. Agree this to the derivative confirmation from the bank.

Identification of the hedged item: the specific risk being hedged, the nature of the hedged item, how the entity will assess whether the forecast transaction is highly probable, and the basis for that probability assessment. For a forecast transaction, the documentation should specify the expected timing and amount of the forecast cash flow, denominated in the relevant currency.

The nature of the risk being hedged. IFRS 9.6.3.7(a) permits the entity to designate only a component of the risk (for example, the benchmark interest rate component of a variable-rate loan, excluding the credit spread). If the entity designates a risk component, that designation must be in the documentation.

How the entity will assess whether the hedging relationship meets the effectiveness requirements in IFRS 9.6.4.1(c). This includes the method for assessing the economic relationship (qualitative or quantitative), the method for measuring hedge ineffectiveness (the hypothetical derivative method is common for cash flow hedges), and the expected sources of ineffectiveness. IFRS 9.B6.4.2 explicitly states that the documentation of the method need not detail the full analysis but must identify the approach.

Ongoing effectiveness and measuring ineffectiveness

Once a hedging relationship is designated, the entity must assess effectiveness on an ongoing forward-looking basis (IFRS 9.6.5.5). The assessment must take place at each reporting date or upon a significant change in circumstances, whichever is earlier. If the hedging relationship ceases to meet the effectiveness requirements, hedge accounting is discontinued prospectively from the date the qualifying criteria are no longer met (IFRS 9.6.5.6).

When to rebalance versus when to discontinue

IFRS 9 introduced a rebalancing mechanism that did not exist under IAS 39. If the hedge ratio of the hedging relationship no longer reflects the actual relationship between the hedged item and the hedging instrument (but the risk management objective remains unchanged), the entity rebalances by adjusting the quantities of the hedged item or the hedging instrument (IFRS 9.6.5.5(b) and IFRS 9.B6.5.7–B6.5.21). Rebalancing is not optional when the hedge ratio drifts. If the entity does not rebalance when required, it must discontinue hedge accounting.

Discontinuation is mandatory (not elective) when the risk management objective for the hedging relationship has changed, the hedging instrument expires or is sold or terminated, or the economic relationship between the hedged item and the hedging instrument no longer exists (IFRS 9.6.5.6). Under IFRS 9, voluntary discontinuation of a hedging relationship that still qualifies is not permitted. This is a key difference from IAS 39, which allowed voluntary de-designation.

When hedge accounting is discontinued for a cash flow hedge, the cumulative gain or loss in OCI remains there until the forecast transaction affects profit or loss (IFRS 9.6.5.12). But if the forecast transaction is no longer expected to occur, the cumulative OCI balance is reclassified immediately to profit or loss. The distinction matters: a hedge discontinued because the derivative expired (but the forecast purchase will still happen) keeps the OCI balance parked. A hedge discontinued because the forecast purchase was cancelled requires immediate P&L reclassification.

Measuring ineffectiveness: the mechanics

IFRS 9.6.5.5 distinguishes between two concepts your audit needs to address separately. The first is whether the effectiveness requirements continue to be met (the qualitative question: does the economic relationship still exist, does credit risk still not dominate, is the hedge ratio still appropriate). The second is the measurement of hedge ineffectiveness (the quantitative question: how much of the fair value change in the hedging instrument is ineffective, and does that amount go to profit or loss).

For cash flow hedges (the most common type in mid-market files), IFRS 9.6.5.11 specifies the measurement. The gain or loss on the hedging instrument is split into an effective portion (recognised in OCI, in the cash flow hedge reserve) and an ineffective portion (recognised immediately in profit or loss). The effective portion is the lower of the cumulative gain or loss on the hedging instrument from inception and the cumulative change in fair value of the hedged item (the “hypothetical derivative”) from inception. Everything beyond that is ineffectiveness.

The hypothetical derivative method works like this. You construct a hypothetical derivative that perfectly matches the hedged item’s critical terms (notional, maturity, underlying). Measure its fair value change. Then compare that to the actual hedging instrument’s fair value change. The difference is ineffectiveness. Sources of ineffectiveness in practice include maturity mismatches (the forward contract settles on 30 June but the forecast purchase occurs on 15 July), notional mismatches (the forward covers $5M but the forecast purchase is $4.8M), and credit value adjustments on the hedging instrument.

For fair value hedges, the mechanics differ. Under IFRS 9.6.5.8, the gain or loss on the hedging instrument is recognised in profit or loss, and the hedged item’s carrying amount is adjusted for the gain or loss attributable to the hedged risk (also in profit or loss). Ineffectiveness is the net of these two amounts. Fair value hedges are less common in mid-market files but appear when entities hedge the fair value of fixed-rate debt or inventories.

Worked example: auditing a cash flow hedge on a forecast purchase

Client: De Groot Importhandel B.V., a Rotterdam-based food ingredients importer. €52M revenue, December 2025 year-end. The entity entered into a USD/EUR forward contract on 15 March 2025 to hedge a forecast USD purchase of raw materials. Notional: $2,000,000. Forward rate: 1.0850 EUR/USD. Settlement date: 15 September 2025. The forecast purchase occurred on 12 September 2025 at $1,950,000.

1. Verify the hedge documentation was in place at inception

Obtain the hedge documentation file. Check that it is dated on or before 15 March 2025 (the designation date). Verify it identifies the specific forward contract (counterparty: ING Bank, notional $2,000,000, forward rate 1.0850, maturity 15 September 2025), the specific hedged item (forecast purchase of soybean lecithin from US supplier Cargill, expected Q3 2025, approximately $2,000,000), the risk being hedged (foreign currency risk on the USD cash outflow), and the method for assessing effectiveness (qualitative assessment based on matched critical terms, with the hypothetical derivative method for measuring ineffectiveness).

2. Assess whether the forecast transaction was highly probable

De Groot has purchased soybean lecithin from Cargill annually for the past four years. Volumes ranged from $1.7M to $2.4M per year. The 2025 purchase budget is $2.1M. A $2,000,000 forecast purchase is consistent with historical patterns and the current budget.

3. Test the qualifying criteria at inception

Economic relationship: a USD/EUR forward contract has a direct and obvious economic relationship with a USD-denominated forecast purchase. Both are exposed to the same risk (EUR/USD exchange rate). The critical terms are closely matched (notional $2M vs. forecast purchase ~$2M, settlement September vs. forecast purchase Q3). No basis difference exists. Qualitative assessment is sufficient.

Credit risk: ING Bank has an A+ credit rating. The credit risk on the forward contract does not dominate the value changes. No further analysis needed.

Hedge ratio: the entity hedges $2,000,000 of a forecast purchase of approximately $2,000,000. The hedge ratio is 1:1, consistent with the entity’s risk management strategy of hedging forecast foreign currency outflows at their expected amount.

4. Test the measurement of hedge ineffectiveness

The forecast purchase occurred on 12 September 2025 at $1,950,000 (not the hedged $2,000,000). The forward contract settled on 15 September 2025 at $2,000,000. Two sources of ineffectiveness exist: a notional mismatch ($2,000,000 forward vs. $1,950,000 actual purchase) and a timing mismatch (settlement three days after the purchase date).

At 31 December 2025, the hedge has been settled. The entity should have reclassified the cash flow hedge reserve from OCI to the cost of the inventory (IFRS 9.6.5.11(d)(i)) when the hedged item (the purchase) affected the balance sheet. Verify the reclassification entry. The ineffective portion (attributable to the $50,000 over-hedge and the three-day timing mismatch) should have been recognised in profit or loss. De Groot calculated the ineffectiveness at €1,840. Recalculate using the hypothetical derivative method: the hypothetical derivative has a notional of $1,950,000 and settles on 12 September, matching the actual purchase. The difference between the actual forward contract’s gain and the hypothetical derivative’s gain produces the ineffectiveness figure.

Conclusion: The completed file demonstrates that each qualifying criterion was tested at inception, the forecast transaction’s probability was supported by historical data, and the ineffectiveness measurement was recalculated independently.

Practical checklist for your engagement file

1. Obtain the hedge designation document and verify it was dated at or before inception of the hedging relationship per IFRS 9.6.2.1, not prepared retrospectively
2. Verify the documentation contains all mandatory elements from IFRS 9.6.4.1(b): risk management objective, hedging instrument identification, hedged item identification, nature of hedged risk, and the method for assessing the effectiveness requirements
3. For forecast transactions, obtain evidence supporting the “highly probable” assessment under IFRS 9.6.3.3: historical transaction data, current order books or purchase orders, approved budgets, and management representations
4. Test each IFRS 9.6.4.1(c) criterion independently: economic relationship (qualitative or quantitative depending on complexity), credit risk dominance, and hedge ratio consistency with the entity’s actual risk management
5. Recalculate hedge ineffectiveness using the hypothetical derivative method (or the entity’s documented method) and verify the ineffective portion was recognised in profit or loss per IFRS 9.6.5.11
6. For settled hedges, verify the OCI reclassification timing and amount: cash flow hedge reserves reclassify when the hedged item affects profit or loss (IFRS 9.6.5.11(d)), or when the forecast transaction is no longer expected to occur (IFRS 9.6.5.12)

Common mistakes

• Retrospective hedge documentation: the most common deficiency in mid-market files is documentation prepared after the derivative was traded. IFRS 9.6.2.1 requires designation at inception. The AFM and the FRC have both flagged late designation as a basis for denying hedge accounting treatment in inspected files.
• Failing to recognise ineffectiveness: some entities recognise the entire fair value change on the hedging instrument in OCI without splitting out the ineffective portion. IFRS 9.6.5.11 requires the ineffective portion to go to profit or loss. Even when ineffectiveness is small, it must be measured and recognised separately.
• Continuing hedge accounting after the forecast transaction is no longer highly probable: if the entity designated a cash flow hedge on a forecast transaction that subsequently becomes unlikely to occur, IFRS 9.6.5.12 requires immediate reclassification of the cumulative OCI balance to profit or loss. Entities sometimes keep the OCI balance “parked” indefinitely rather than recognising the loss.

Related Ciferi content

Related guides:

Put audit concepts into practice with these free tools:

Frequently asked questions

Further reading and source references

• IFRS 9, Financial Instruments – Chapter 6 covers hedge accounting requirements including designation, documentation, effectiveness assessment, and discontinuation.
• IAS 39, Financial Instruments: Recognition and Measurement – the predecessor standard; understanding its 80–125% test helps contextualise the IFRS 9 changes.
• IFRS 13, Fair Value Measurement – the framework for measuring derivative fair values used in hedge accounting relationships.