Granvemhoacvibimdeol
Hedge Management

Rolling Commodity Hedge Programmes Without Creating Gap Exposure Along the Way

Lead Risk Analyst October 2026
Calendar showing futures expiry and roll dates
Roll date alignment prevents unplanned gaps in hedge coverage

The standard approach to rolling a commodity hedge is to close the expiring position and open the next-period contract in a single transaction — a calendar spread executed simultaneously to eliminate the price risk of the interval. This works cleanly when the expiry date of the futures contract aligns with the pricing date of the physical procurement contract. When those two dates diverge, the spread transaction does not eliminate the gap — it shifts it. A futures contract that expires on the last business day of the month, rolled against a physical contract that prices on the fifteenth, leaves a two-week window where the hedge ratio is either over- or under-stated depending on which side of the roll the business sits. The diagnostic step is to map every procurement pricing date against the corresponding futures expiry schedule at the start of the programme, not at each individual roll event. That forward calendar reveals the structural gaps before they become live exposure, and it gives the treasury team the option to address them through contract negotiation with the supplier rather than through last-minute derivative adjustments.

Analyst calculating hedge ratio for rolling programme
Hedge ratio must be recalculated at each roll event

A rolling programme does not maintain a fixed hedge ratio automatically. The notional volume of each successive position must be recalculated at each roll event to reflect the current procurement forecast for the upcoming period. This is straightforward in principle and frequently neglected in practice. A programme that was sized against a procurement volume forecast prepared at the start of the financial year will drift away from its intended hedge ratio as actual volumes diverge from that forecast. By the third or fourth roll event, the mismatch between the hedged notional and the actual exposure can be material — particularly in industries where production schedules respond to demand signals on a quarterly basis. The recalculation is not technically demanding. It requires the treasury team to obtain an updated procurement volume estimate from the operations or supply chain function at each roll event, compare it to the current hedged notional, and adjust the new position size accordingly. The operational challenge is institutional: the conversation between treasury and operations needs to be scheduled into the roll process, not treated as an optional input. Programmes that omit this step tend to discover the volume mismatch through a hedge accounting effectiveness test failure rather than through a proactive review.

Futures price curve showing contango and backwardation
Contango markets add cumulative roll costs over time

Rolling a hedge in a market that is in contango — where forward prices are higher than spot — introduces a structural cost that is sometimes described as roll yield, and more accurately described as the cost of extending protection into a more expensive part of the futures curve. Each time a position is rolled, the closing price of the expiring contract is lower than the opening price of the next-period contract. That difference is a real cash flow, and in a persistently contangoed market it accumulates across multiple roll events into a meaningful programme cost. This is not a reason to avoid rolling hedges in contango markets. It is a reason to include the expected roll cost in the business case for the programme before it is approved. A treasury team that presents a rolling hedge programme to a board without modelling the cumulative roll cost in a contango scenario is presenting an incomplete picture. The same analysis applies in reverse for backwardated markets, where rolling generates a positive roll yield. Treating that positive yield as a return rather than as a structural feature of the current market shape creates a different category of planning error when the curve structure changes.

Treasury team reviewing AASB 9 hedge documentation
Each roll event requires its own hedge designation document

Under AASB 9, each new position in a rolling programme requires its own hedge designation and documentation. The original hedge relationship cannot simply be carried forward to the next period without a formal re-designation. This is a documentation workflow, not a complex accounting judgement, but it is one that treasury teams under operational pressure frequently defer. The consequence of deferral is that positions which were economically intended as hedge instruments are treated as speculative derivatives in the financial statements, with mark-to-market movements flowing directly through profit and loss rather than through the cash flow hedge reserve. For a business with a material rolling programme, the income statement volatility generated by a lapse in hedge documentation can be significant — and explaining it to an audit committee after the reporting date is considerably more difficult than maintaining the documentation workflow in real time. We recommend that the roll event checklist include a documentation step as a formal gate: the new position is not considered open for reporting purposes until the hedge designation document is completed, reviewed, and filed. This is a process control, not an accounting innovation, and it is one that any treasury function can implement without specialist external support.

Legal documents for OTC derivative counterparty agreement
Counterparty exposure accumulates as rolling programmes extend

Rolling programmes that use over-the-counter instruments rather than exchange-traded futures accumulate counterparty credit exposure over time in a way that a single-period hedge does not. Each new swap or forward added to the programme increases the gross notional outstanding with the counterparty, and in a market that moves significantly in the hedger's favour, the mark-to-market receivable from that counterparty grows accordingly. A programme that was sized within the organisation's counterparty credit limits at inception may breach those limits after several roll events if prices have moved materially. The mitigation tools available are well documented: credit support annexes that require collateral posting when mark-to-market exposure exceeds a threshold, netting agreements that reduce gross exposure to net exposure across all outstanding positions with a single counterparty, and counterparty diversification across multiple dealers. The diagnostic question for any rolling OTC programme is whether the counterparty credit limits were set against the expected maximum mark-to-market exposure at programme maturity, not just against the initial notional. Limits set at inception without modelling the potential future exposure across the full rolling horizon are limits that will be tested at the worst possible time — when the hedge is most in-the-money and the counterparty's credit quality may be under pressure from the same market move that created the receivable.

A rolling hedge programme is not a set-and-forget structure. It is a recurring operational workflow that requires calendar discipline, volume recalculation, documentation hygiene, and counterparty credit monitoring at every roll event without exception.

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.