What is balance sheet FX hedging?

Balance sheet FX hedging protects profit and loss against the remeasurement of foreign-currency monetary items an entity already carries, such as receivables, payables, intercompany loans and foreign-currency cash. Under IAS 21 those items are retranslated at the closing rate each reporting date and the exchange difference goes to profit or loss. A treasury offsets that by holding FX forwards or swaps in the opposite direction, sized to the net booked balance per entity and currency, and rolled each period.

Why does balance sheet hedging usually not need hedge accounting?

Because the offset happens on its own. The hedged balance is remeasured through profit or loss under IAS 21, and an undesignated derivative is measured at fair value through profit or loss, so both movements land in the same line of the same period. Hedge accounting exists to fix a timing mismatch between the hedge and the hedged item, and here there is none to fix. US GAAP reaches the same place: fair value hedge accounting for a recognized foreign-currency item gives the same overall result as not applying it.

What is the difference between a balance sheet hedge and a cash flow hedge?

A balance sheet hedge covers an exposure that is already recognized, where the remeasurement of the item and the derivative both hit profit or loss, so no hedge accounting is needed. A cash flow hedge covers a forecast transaction that is not yet on the balance sheet, such as next quarter's expected sales. There the derivative would move profit or loss before the transaction exists, so hedge accounting defers the effective portion in other comprehensive income until the hedged cash flows affect profit or loss, which requires formal designation, documentation and effectiveness assessment.

Balance Sheet FX Hedging vs Cash Flow Hedging

Balance sheet FX hedging protects the P&L against the remeasurement of foreign-currency balances an entity already carries: receivables, payables, intercompany loans, foreign-currency cash. Because the balance is revalued through profit or loss and the hedging derivative is too, the two offset without any hedge accounting. Cash flow hedging protects transactions that are only forecast, and there hedge accounting is what stops the derivative from moving the P&L ahead of the transaction it hedges. Same forwards, same dealing desk, two different accounting problems. Treating them as one is how treasuries end up documenting hedges that didn't need it, or leaving hedges undocumented that did.

(This explains how the two approaches work. It isn't accounting or hedging advice for any particular entity, and your auditors decide the treatment.)

Two exposures, two problems

Both exposures are transaction exposure. They differ in whether the exposure is on the balance sheet yet, and that difference decides everything else.

Question	Balance sheet (remeasurement) hedge	Cash flow hedge
What is hedged	Booked FX monetary items: AR, AP, intercompany loans, FX cash	Forecast or committed flows not yet recognized
Accounting of the hedged item	Retranslated at closing rate; difference to P&L (IAS 21)	Nothing recognized until the transaction happens
Derivative without hedge accounting	Fair value through P&L	Fair value through P&L, ahead of the item: a genuine mismatch
Hedge accounting needed?	Usually not: the offset is natural	Yes, if the P&L volatility matters
Paperwork	Policy, exposure report, deal tickets	Designation, documentation, effectiveness at inception and ongoing
Typical cadence	Monthly (or more often), rolled around closing dates	Layered over the forecast horizon
Data source	The general ledger	The forecast

The last row causes more practical trouble than the rest put together. A balance-sheet programme is only as good as the ledger balances it reads. A cash flow programme is only as good as the forecast. They're different data problems owned by different people, and one hedging strategy document has to cover both.

Why the balance sheet hedge needs no hedge accounting

The mechanics come straight from IAS 21. Foreign-currency monetary items are translated at the closing rate at each reporting date (IAS 21.23), and exchange differences on them are recognized in profit or loss in the period they arise (IAS 21.28). A USD receivable in a EUR entity therefore generates a P&L gain or loss every month-end the rate moves.

An FX forward that isn't designated in a hedging relationship is a derivative at fair value through profit or loss. Sell USD forward against that receivable and its value moves the other way, in the same P&L, in the same period. Nothing needs deferring, because nothing is out of step. Hedge accounting under IFRS 9 is optional: it's a tool for fixing an accounting mismatch, and this relationship doesn't have one.

US GAAP gets to the same place by a different route. Foreign-currency balances are remeasured at spot under ASC 830 with the transaction gain or loss in earnings, and practitioner guidance on ASC 815 notes that applying fair value hedge accounting to such an item produces the same overall result as not applying it at all.

Hedge accounting fixes a timing mismatch. A balance sheet hedge doesn't have one. The receivable and the forward already move through the same P&L in the same month.

What doesn't offset, even without the paperwork

"Natural offset" doesn't mean a perfect one. Four residuals are worth predicting before someone asks about them in the month-end review:

Forward points. The balance is remeasured at spot. The forward is valued at fair value, which reflects the forward rate and discounting. The difference, broadly the interest differential between the two currencies, lands in P&L as carry. It's expected and it can be budgeted, but it isn't zero.
Timing of the exposure read. Balances move every day, while hedges are usually set from a snapshot of the ledger. Anything booked or settled between the snapshot and the closing date is unhedged or over-hedged by that amount.
Functional currency, not group currency. Remeasurement happens in each entity against its own functional currency. Two entities' balances in the same currency don't offset each other's P&L if their functional currencies differ, so the exposure has to be measured per entity and currency pair, not netted at group level by instinct.
Net investment balances. IAS 21.32 treats monetary items that form part of a net investment in a foreign operation differently in the consolidated statements, where exchange differences go to other comprehensive income instead. A long-term intercompany loan designated that way isn't a balance sheet exposure in the group P&L, and hedging it as one creates the very mismatch the programme exists to remove.

Each of these is an exposure-data question more than a dealing question, which is why exposure data quality decides whether a balance-sheet programme works.

Where cash flow hedges are different

A cash flow hedge covers something that isn't on the balance sheet yet: next quarter's forecast sales in USD, a committed purchase in JPY. Without hedge accounting, the forward's fair value moves the P&L now, while the sale it protects arrives later. That's the mismatch hedge accounting exists to remove.

Under IFRS 9 the effective portion of the hedging instrument's gain or loss goes to other comprehensive income (the cash flow hedge reserve) and is reclassified to profit or loss in the period the hedged cash flows affect it. If the hedged cash flows are no longer expected to occur, the amount is reclassified immediately. In exchange for that deferral, the standard asks for formal designation and documentation at inception and an ongoing effectiveness assessment. That's real, recurring work, and it's worth doing only where the alternative, P&L volatility on unrecognized flows, matters to someone.

The handover: when a forecast becomes a receivable

The two programmes meet at invoicing. The day a forecast sale is invoiced, the exposure stops being a forecast and becomes a booked receivable. It moves from the cash flow bucket to the balance sheet bucket.

There are two broad designs, and the system has to support whichever you pick:

One instrument, two phases. The same forward covers the forecast under a cash flow hedge and, once the item is recognized, offsets its remeasurement. How the relationship and the reserve are treated after recognition is an accounting-policy decision, and one to settle with your auditors before the first deal, not after the first quarter.
Two programmes. Cash flow hedges run to the point of recognition. A separate balance-sheet programme, rolled each month, covers booked balances from the ledger.

What fails is not choosing. The same receivable ends up covered by a forecast hedge that nobody de-designated and by a balance-sheet hedge sized from the ledger, and the exposure is hedged twice. That's natural and financial hedging losing track of each other inside one treasury.

How SAP supports balance sheet FX risk

SAP models the split in the product itself. Hedge Management in SAP has two FX processes, and only one of them involves hedge accounting.

Hedge Management of Balance Sheet FX Risk is the remeasurement process. SAP defines balance sheet FX risk as arising from the revaluation of monetary balance sheet items in foreign currency, and the process is built around that:

Step	What SAP provides
Exposure	The Review Balance Sheet FX Risk app reads open items and balances in foreign currency on G/L accounts in Financial Accounting, plus operational data from One Exposure, as FX exposures
Hedges	Financial transactions from the Transaction Manager appear as the hedges against those exposures
Freeze	A snapshot of exposures and hedges, taken from the app and stored, gives the reference point for decisions
Hedge requests	Balance sheet exposure hedge requests are generated from released snapshot data, or created manually
Release	In Process Hedge Requests - Balance Sheet FX Risk you edit, delete and release requests; on release the system creates a trade request automatically
Monitoring	The Balance Sheet FX Risk tile shows hedges, exposures and absolute net exposures by company code in a display currency

Notice what isn't in that list: designation, a hedge relationship, an effectiveness test. The process goes from ledger exposure to snapshot to hedge request to trade request to deal, and the accounting takes care of itself because the offset is natural.

The forecast side runs through the other process, Hedge Management and Accounting of Net Open Exposures (FX Risk), which SAP describes as managing the risks of planned and confirmed foreign-currency cash flows in future periods. There, hedging areas set the granularity, the Hedge Management Cockpit shows net open exposure, and hedge accounting has to be switched on deliberately: the hedging area is marked relevant for hedge accounting before automated designation of exposure items applies.

The practical upshot for a design: scope the balance-sheet process as a treasury and ledger-data project, and the net-open-exposure process as a treasury and accounting project. They share instruments and a trading desk. They don't share a data source, a control set or a workload.

What I would decide

Write down, per exposure type, whether it's hedged on the balance sheet or as a forecast, and where the handover at invoicing sits.
Run the balance-sheet programme without hedge accounting, and budget the forward points as carry.
Measure balance-sheet exposure per entity against its functional currency, and exclude net-investment balances explicitly.
Reserve hedge accounting for the forecast programme, where the mismatch is real, and staff it with someone who knows the standard.
In SAP, use the balance-sheet process for the ledger side and the net-open-exposure process for the forecast side, and don't force one to do the other's job.