Courses / Commodity & FX Hedging

Portfolio-based hedging

From hedging trades to hedging a book: netting, portfolio structure, tolerance bands — and what netting genuinely saves.

Module 8 of 143 lessonsAbout 40 minQuiz: 6 questions
Hedge

Lesson 1 · free to read

From hedging trades to hedging the book

Two pure philosophies bracket every hedging programme:

Item-by-item (back-to-back) hedging. Every physical tranche gets its own hedge the moment it prices: buy 2,000 MT of corn at 10:04, sell 16 December contracts at 10:05 (2,000 / 127 = 15.7, rounded), allocate them to that contract. Attribution is perfect — each deal carries its own hedge, its own hedge P&L, its own story (and modules 2–6 built exactly this machinery). The costs: maximum trade count (commissions, spread crossings), maximum gross lots (margin funding, module 5), and constant small-lot execution including at illiquid moments.

Net-exposure (portfolio) hedging. Let the book's internal offsets cancel first — today's purchases against today's sales, this desk's longs against that desk's shorts — then hedge only the residual on a cycle (continuously within a tolerance, or at defined times). Fewer trades, fewer gross lots, better execution moments. The costs: attribution weakens (a hedge covers "the book", so per-deal hedge P&L needs an allocation convention), the interval between physical event and hedge is open risk, and the netting is only as good as the exposure calculation feeding it — a portfolio hedge on a wrong exposure number is a precise hedge of the wrong thing.

Real desks sit between the poles, deliberately. Common shape: automatic item hedges for large or unusual deals and for auto-hedge programmes (an accepted producer offer triggers its own lots); portfolio treatment for the high-frequency small flow, netted within the day and trued up at the close within a tolerance band. The choice per flow is a policy the system should encode — "deals over X MT hedge individually; the rest sweep into the book" — not tribal knowledge.

Tolerance bands make the programme governable. A band per commodity/book ("residual within ±200 MT, or ±2 lots, at all times; zero by month-end") converts hedging from continuous judgement calls into an exception process: inside the band, nothing to do; outside it, the system raises the residual and someone acts the same day. Bands should be set from the desk's risk appetite in currency terms (what does a 5% move on the band cost?) and reviewed when volatility regimes change — a band set in a quiet year is twice the risk in a wild one.

What changes operationally when a desk goes portfolio: exposure calculation moves from per-deal arithmetic to the book-level pipeline of module 2 (and must be trusted, hence reconciliation discipline); hedge allocation gains a convention layer (pro-rata across covered deals, FIFO, or explicit book-level P&L, module 8); and the exception reports — priced-but-not-hedged, residual-outside-band, over-hedged bucket — stop being nice-to-haves and become the control system itself.

The rest of this module

  1. Netting — what it saves, and what it cannot
    Offsets across trades, the same-period test, and the honest arithmetic of netting benefits.
  2. Portfolio structure and running the programme
    Books along commodity, segment, region and strategy lines; internal transfers; the operating rhythm.

Carry on with the course

The other lessons and the quiz are in the course itself, where your progress is saved and counts towards the certificate: Commodity & FX Hedging Operations.

Next module: MTM, P&L and reporting