Granvemhoacvibimdeol

Commodity Price Scenario Analysis: How to Stress-Test a Hedging Programme Before the Board Approves It

Scenario Analysis October 2026 by Senior Risk Analyst

The workflow for a rigorous commodity price scenario analysis follows a defined sequence of steps, each building on the output of the previous. Skipping any step produces a stress-test that looks complete but leaves material tail risks unexamined. We walk through the process in the order it should be executed, before the hedge programme is presented to the board for approval.

Finance analyst building commodity price stress test model
Step 1

Establish the Base Case Price Forecast and Its Explicit Assumptions

Most base-case price forecasts are assembled from a combination of dealer consensus, publicly available commodity outlook reports, and internal procurement team experience. None of these sources is neutral. Dealer consensus reflects the views of market participants with commercial positions. Published outlooks reflect the analytical frameworks of the institutions that produce them, which vary in methodology and track record. Internal procurement experience captures historical patterns but may not account for structural supply chain changes. The base case should be documented with its source assumptions stated explicitly, so that the scenario analysis can systematically challenge each assumption rather than treating the forecast as a fixed backdrop. If the base case assumes stable freight costs, one scenario should model a freight disruption. If it assumes a specific currency trajectory, one scenario should model a significant AUD depreciation. The base case is the starting point, not the analysis.

Step 2

Define the Tail Scenarios That the Hedge Programme Is Designed to Survive

A tail scenario is not a pessimistic version of the base case. It is a structurally different market outcome — one where the relationships assumed in the base case break down. For a commodity hedging programme, the relevant tail scenarios are those in which the commodity price moves far enough, fast enough, or in a sufficiently correlated way with other cost inputs to overwhelm the hedge's protective effect. Standard practice in risk management literature, including guidance from the Bank for International Settlements on stress-testing frameworks, recommends defining scenarios based on historical precedent — price dislocations that have actually occurred in the target commodity — and on hypothetical scenarios that reflect plausible but not-yet-observed combinations of risk factors. For Australian industrial commodity users, relevant historical precedents include the 2008 commodity price collapse, the 2021 supply chain disruption cycle, and the extended energy price volatility of 2022. Each of these events produced commodity price movements that fell well outside the range of contemporary base-case forecasts. The programme should be tested against a price move of at least two standard deviations from the mean over the hedge horizon, using the historical volatility of the commodity, not the implied volatility from the current options market, which may understate tail risk in low-volatility regimes.

Step 3

Apply Each Scenario to the Hedge Structure and Calculate the Net Outcome

For each scenario, the analysis should calculate three numbers: the physical procurement cost under that scenario without any hedge, the net cost after accounting for the hedge payoff or loss, and the residual unhedged exposure that remains after the hedge settles. The first number establishes what the business was trying to protect against. The second number measures whether the hedge achieved that objective. The third number identifies what the programme does not cover and why. The residual exposure calculation is the most frequently omitted step. Treasury teams present the hedged outcome as the final result, without identifying the portion of the exposure that the hedge did not address — either because the hedge ratio was less than one, because basis reduced the hedge effectiveness, or because the programme covered only a subset of the total procurement volume. In a severe scenario, the residual unhedged exposure can be the dominant number. Presenting the hedged outcome without the residual leaves the board with an incomplete picture of the programme's actual protective scope.

Step 4

Quantify the Basis Risk Contribution Separately Within Each Scenario

Basis risk does not behave uniformly across price scenarios. In moderate market conditions, basis may be relatively stable and its contribution to programme outcomes modest. In tail scenarios — precisely those conditions the hedge is designed to address — basis tends to widen. Supply chain disruptions that drive commodity prices to extremes typically do so through regional or grade-specific dynamics that diverge from the broad exchange-traded price on which most derivative hedges are based. The 2021 supply chain disruption cycle is a documented example: physical commodity prices for specific industrial grades and delivery locations diverged significantly from exchange-traded benchmarks, reducing the effectiveness of derivative hedges that had been sized and structured against those benchmarks. The scenario analysis should therefore model basis explicitly in each tail scenario, using a range of basis outcomes rather than the historical mean. The range should extend to the widest basis observed in the historical sample for that commodity, applied to the tail price scenario. This produces a worst-case combined outcome — adverse price movement and wide basis simultaneously — which is the scenario a well-designed programme should still survive at an acceptable cost.

Step 5

Test the Programme's Hedge Accounting Stability Under Each Scenario

A scenario analysis that covers only the economic outcomes of the hedge — procurement cost, hedge payoff, net position — without addressing the accounting outcomes is incomplete for a board presentation. Under AASB 9, hedge accounting designation can be disrupted by price movements that push the hedge ratio outside the range that reflects the economic hedge, by basis movements that impair the economic relationship between the hedged item and the hedging instrument, or by volume changes that alter the notional size of the hedged exposure. In a severe price scenario, all three disruption mechanisms may operate simultaneously. The scenario analysis should test whether the hedge accounting designation remains intact — whether the programme continues to qualify for hedge accounting — under each tail scenario. If a tail scenario produces conditions under which the programme would fail the AASB 9 effectiveness assessment, that outcome should be disclosed to the board, along with the accounting consequence: mark-to-market movements on the derivative flowing through profit and loss rather than through the cash flow hedge reserve. This is not a reason to avoid the hedge. It is information the board needs to set appropriate expectations for reported earnings volatility under stress conditions.

Step 6

Present the Scenario Results With Explicit Risk Appetite Linkage

A scenario analysis that produces a table of numbers without connecting those numbers to the organisation's documented risk appetite has not completed its analytical task. The final step is to map each scenario outcome — net procurement cost, residual exposure, basis contribution, accounting impact — against the risk tolerance thresholds that the board or risk committee has approved. Where a scenario outcome falls within the approved tolerance, the programme is confirmed as adequate for that scenario. Where a scenario outcome exceeds the tolerance, the gap must be addressed: either by modifying the hedge programme to extend its coverage, by revising the risk appetite to reflect the cost of additional coverage, or by formally accepting the residual tail risk with board acknowledgement. The gap between the stress-test outcome and the risk appetite is the most important number in the scenario analysis, and it is the one most frequently absent from the board paper. A hedging programme presented as adequate without a documented risk appetite comparison is a programme that has been approved against an undefined standard. When a tail scenario eventually materialises — and the historical record suggests it will — the absence of that documented comparison makes it considerably more difficult to assess whether the programme performed as intended or fell short of what was required.

We use cookies on this site

This website uses cookies to support core functionality and to collect anonymised analytics data about how visitors use the site. We do not use cookies for targeted advertising or cross-site tracking. You may accept all cookies, reject non-essential cookies, or manage your preferences at any time. For full details refer to our Cookie Policy.

Strictly necessary site cookies Required

These cookies enable core website navigation and page access functions. They cannot be disabled without impairing the basic operation of the site.

Analytics and performance cookies

These cookies collect anonymised data on pages visited and time spent, used only to improve the technical performance of the site.