How does FX hedging work for a commodity trader with mismatched currencies?

By Saurabh Goyal, Founder & CEO of Phlo Systems. Published 3 August 2026.

Ask a commodity trading CFO whether their firm trades FX and most will say no — FX is what banks and hedge funds do, not a physical commodity house buying cocoa or steel. Ask the same CFO what currency the last purchase contract was priced in, what currency the matching sale was priced in, and what currency the working capital facility draws in, and you will usually get three different answers. That gap between "we don't trade FX" and "we have three currency legs on every deal" is where unhedged currency risk quietly erodes margin that the trading desk worked hard to lock in.

The 30-second answer: currency exposure in physical commodity trading is structural, not optional — it is created automatically the moment a purchase leg, a sale leg, and a financing leg are priced in different currencies, which is the normal case, not the exception. The standard hedge is a forward FX contract (or a matching FX swap against the facility) sized to the exposed leg and dated to the expected cash-flow date, locking in today's rate for a future settlement. The hedge only works if it is booked against the actual exposure — the real invoice amount and real expected date — which means treasury needs to see every mismatched-currency deal the moment it is captured, not in a week-end FX exposure report that is already stale by the time someone reads it.

Where the currency exposure actually comes from

A single physical trade can carry FX exposure at up to three separate points, each created independently:

• The purchase leg. Buying cocoa from a West African cooperative, priced and invoiced in USD.
• The sale leg. Selling the processed output to a European buyer, priced and invoiced in EUR.
• The financing leg. Drawing a working capital facility in GBP (the currency the lender operates in, or the currency the trading entity reports in) to fund the purchase before the sale settles.

None of these three legs is itself "an FX trade." Each is a normal commercial decision — buy where the supplier prices, sell where the buyer prices, borrow where the facility is domiciled. The FX exposure is the byproduct of those three independent, entirely reasonable decisions landing in three different currencies on the same deal. A trader who has never placed an FX order can still be running a materially open currency position without realising it, because nobody labelled it as one.

The two hedges that cover almost every case

Physical commodity traders overwhelmingly use two instruments, not the exotic structures FX desks sometimes pitch:

1. FX forward contract. A contract to exchange a fixed amount of one currency for another at a fixed rate, on a fixed future date. If a USD purchase invoice is due in 45 days, the trader books a forward to sell GBP (or whatever the functional currency is) and buy USD in 45 days at today's rate — locking in the cost of that invoice regardless of where spot moves between now and settlement.
2. FX swap against the facility. Where the financing leg itself is in a different currency from the purchase or sale leg, an FX swap converts the drawn facility currency into the currency actually needed to pay the supplier, then reverses the conversion when the sale proceeds land — matching the timing of the loan to the timing of the underlying trade rather than leaving a currency mismatch sitting on the balance sheet between drawdown and repayment.

Both instruments do the same underlying job: they convert an uncertain future exchange rate into a certain one, for the specific amount and the specific date the underlying commercial exposure actually has. Options and more structured hedges exist, and desks with a house view on currency direction sometimes use them, but for a trading firm whose job is margin on physical goods, not a view on EUR/USD, a plain forward matched to the real exposure covers the overwhelming majority of cases.

Why the hedge only works if it matches the real exposure

A forward hedge is only as good as the number and date it is booked against. Three ways this goes wrong in practice, all more common than a trader expects:

• Wrong amount. The forward is sized against the contract quantity at the price agreed weeks ago, but the final invoice comes in different — a quality adjustment, a quantity tolerance clause, a demurrage deduction — and the hedge no longer matches the actual cash flow it was meant to cover.
• Wrong date. The forward is dated against the contractual payment term, but the actual payment happens early (a supplier discount taken) or late (a documentary discrepancy delays release), leaving the hedge settling on a day when the underlying cash flow hasn't happened yet, or already has.
• Wrong exposure entirely. Treasury hedges the gross purchase leg without netting it against a matching sale leg in the same currency that was already going to offset most of the exposure naturally — paying for a hedge, and the bid/offer spread that comes with it, on a position that barely needed one.

Every one of these failure modes has the same root cause: the hedge was booked against what the contract said at signing, not against what the trading book actually shows the exposure to be right now. That is a data-currency problem before it is a hedging-skill problem.

Why exposure visibility has to be continuous, not a weekly report

The standard treasury process at most mid-market trading firms is a periodic FX exposure report — often weekly, sometimes only at month end — built by pulling open positions from the trading system, matching them against known settlement dates, and handing the summary to whoever executes the hedges. Two things make this structurally late:

• New exposure is created every time a mismatched-currency deal is booked, not on the reporting cycle. A USD purchase booked on a Tuesday sits unhedged until the next Friday report, unhedged for however many days the currency moves against the firm in the meantime.
• Existing exposure changes shape continuously — an invoice amount is confirmed, a payment date shifts, a sale leg that was going to net against the purchase falls through — and a report built once a week is describing a position that has already moved by the time treasury reads it.

Treasury systems built as a bolt-on to the trading book inherit this lag by design: FX exposure is derived, periodically, from data that lives natively somewhere else. A treasury function that sees every currency-mismatched deal the moment it is captured in the trading book — not on a reporting cycle — can hedge the actual, current exposure instead of last week's snapshot of it.

	Periodic exposure reporting	Continuous exposure visibility
When is new exposure seen?	Next scheduled report	The moment the deal is booked
What does the hedge get sized against?	Contract terms at signing	Current invoice amount and expected date
How does a changed payment date get reflected?	Next report cycle	Same day
Where does netting happen?	Manual, if anyone remembers to check	Automatic, against the live book

What a CFO should ask their treasury or trading system to do

1. Show today's open FX exposure by currency pair, live, not as of the last report — the same discipline as asking for a real-time trial balance rather than a month-end close.
2. Net exposures automatically across purchase, sale, and financing legs in the same currency pair before flagging what actually needs hedging, so treasury isn't paying spread on exposure that already offsets itself.
3. Re-flag hedged positions when the underlying changes — a quantity adjustment, a shifted payment date — rather than leaving a stale forward matched against a contract term that no longer reflects reality.
4. Tie every FX forward to the specific invoice or cash flow it hedges, not a round-number estimate, so a finance team can prove hedge effectiveness to an auditor without reconstructing the logic after the fact.

Frequently Asked Questions

Why does a physical commodity trader have FX exposure if they never trade currencies directly?

Because purchase, sale, and financing legs are routinely priced in different currencies as a normal consequence of where suppliers, buyers, and lenders operate — not because the trader chose to take a currency position. Buying in USD, selling in EUR, and borrowing in GBP on the same deal creates exposure automatically, whether or not anyone labels it "FX trading."

What is the standard hedge for commodity trade FX exposure?

An FX forward contract sized to the specific exposed amount and dated to the expected cash-flow date, or an FX swap where the mismatch is between the financing currency and the trade currency. Both lock in today's exchange rate for a known future settlement, which is what the underlying commercial exposure actually needs.

Why do FX hedges sometimes fail to fully protect margin even when the trader hedged?

Usually because the hedge was sized or dated against the contract terms at signing rather than the actual invoice amount and actual payment date, which can shift due to quantity tolerances, quality adjustments, or payment timing changes — leaving a mismatch between what was hedged and what actually happened.

How often should FX exposure be reviewed?

Continuously, in principle — new exposure is created the moment a mismatched-currency deal is booked, not on a reporting schedule. A weekly or monthly exposure report means every deal booked since the last report sits unhedged, by construction, for however long the gap is.

How Phlo Systems helps

finPhlo surfaces FX exposure from the trading book in real time — every purchase, sale, and financing leg priced in a different currency is visible to treasury the moment it is booked, netted automatically against offsetting legs in the same pair, and re-flagged if the underlying amount or date changes before settlement. Hedges can be tied directly to the invoice or cash flow they cover, so hedge effectiveness is provable, not reconstructed after the fact. See how finPhlo tracks FX exposure.

---

Related reading:

• Cash Flow at Risk (CFAR) for commodity trading firms: a practical guide
• The cash flow implications of hedging commodity positions with futures
• Best Trade Finance Software for Commodity Trader CFOs in 2026

Saurabh Goyal is the Founder & CEO of Phlo Systems. He spent 12 years building CTRM and ERP systems for global commodity trading houses before founding Phlo in 2016.