Balance sheet hedging is the practice of using short-dated forwards or swaps to offset FX remeasurement risk on monetary items already booked, like receivables, payables, intercompany loans, and cash. Its purpose is a cleaner income statement, not speculation. Most treasuries run it under IFRS 9 without full hedge accounting, and platforms like CorpHedge now automate the exposure netting and trade sizing behind it.
TL;DR:
- Short-dated forwards or swaps are used to hedge actual, recorded FX exposures, prioritizing simplicity and automatic netting over full hedge accounting compliance.
- Managing timing mismatches and liquidity constraints is essential, with shorter tenors and cash buffers helping prevent hedge ineffectiveness.
- Automation based on regular, VaR-triggered netting cycles improves efficiency while maintaining human oversight for governance and approval.
- Accurate, reconciled exposure data from ERP systems is fundamental to implementing effective and credible hedging programs.
- Formal hedge accounting under IFRS 9 often becomes unnecessary because the hedge and the hedged item typically remeasure simultaneously on the P&L.
Table of Contents
- What Is Balance Sheet Hedging and When Should Treasury Use It?
- How Are Balance Sheet Hedges Built and Executed?
- What Do IFRS 9 and IAS 39 Mean for Reporting?
- What Governance and Controls Should Treasury Have in Place?
- How Does Automation and VaR-Based Policy Design Work in Practice?
- What Challenges Come Up and How Do You Mitigate Them?
- What Should Treasury Ask Before Starting a Program?
- Pragmatic Choices for Mid-Market Treasury Teams
- Get Started With CorpHedge's Hedging Platform
- Primary Sources and Recommended Reading
- Sources
- FAQ
What Is Balance Sheet Hedging and When Should Treasury Use It?
Balance sheet hedging targets monetary items denominated in a currency other than an entity's functional currency: accounts receivable, accounts payable, intercompany loans, and cash balances sitting on a subsidiary's books. Every time the exchange rate moves before those items settle, the company has to remeasure them, and that remeasurement runs straight through the income statement. Balance sheet hedging exists to blunt that volatility, not to eliminate currency risk altogether.
It differs from two other common programs in a specific way:
- Cash-flow hedging protects forecasted future transactions that have not yet hit the balance sheet.
- Net investment hedging protects the translated value of a foreign subsidiary's equity, not its transactional exposures.
- Balance sheet hedging deals only with exposures already recorded, which makes it the most mechanical of the three to design.
That mechanical simplicity is exactly why most mid-market treasuries start here. Short-dated, already-booked exposures are easier to size and hedge than a forecast that might not materialize, and the types of exposure hedging a company chooses usually depend on how much of its risk is transactional versus translational.
How Are Balance Sheet Hedges Built and Executed?
The workflow starts with data, not trades. Treasury pulls an ERP extract of monetary items by currency, then nets AR against AP, folds in intercompany balances, and adds cash positions to arrive at one net exposure figure per currency pair. That net number, not the gross AR or AP balance, is what gets hedged.
A simple operational sequence looks like this:
- Extract AR, AP, intercompany, and cash balances by currency from the ERP.
- Calculate net exposure per currency pair.
- Select the instrument: short-dated forwards for most exposures, swaps when rolling a position, options only for longer or asymmetric risk.
- Execute the hedge and log the trade against the exposure it offsets.
- Reconcile actuals against the hedge at period end or on the next cycle.
Execution cadence varies by company size and volatility appetite. Some treasuries hedge only at period end to match reporting dates; others run a rolling weekly cycle that recalculates net exposure and adjusts the hedge automatically. An automated hedging solution typically recalculates on a weekly basis, extracting net AR/AP and bank liquidity data before surfacing a trade recommendation for approval.
Pro Tip: *Set a rolling trigger, not just a calendar date.
What Do IFRS 9 and IAS 39 Mean for Reporting?
Remeasurement of a foreign currency monetary item flows through the P&L in the period it occurs. A properly sized balance sheet hedge generates an offsetting gain or loss in the same period, so the two largely cancel out and the net P&L impact shrinks.
IFRS 9 changed several things that matter to treasury compared with its predecessor, IAS 39:
- More exposures become eligible for hedge accounting, including aggregated or net positions in some cases.
- Time value of money must be considered explicitly in the accounting for certain hedge instruments.
- Documentation and effectiveness testing rules shifted, changing what auditors expect to see.
Here is the part many teams overlook: balance sheet hedging often avoids the need for formal hedge accounting entirely, because the hedge and the hedged item typically hit the P&L in the same period anyway. That is one reason some treasuries continue applying IAS 39 rules where permitted rather than rushing a full IFRS 9 hedge accounting transition before their systems and valuation processes are ready. Common pitfalls include mismatched settlement dates between the hedge and hedged item, forgetting to net intercompany balances before sizing the trade, and failing to document the rationale for instrument choice, which auditors will ask for regardless of whether formal hedge accounting applies.
What Governance and Controls Should Treasury Have in Place?
A credible program rests on three pillars: clean data, a documented policy, and separation of duties. None of these are optional once trade volume grows past a handful of currency pairs.
Data and systems requirements include:
- Reliable ERP exposure extracts by currency and entity.
- Bank cash feeds that reconcile against the ERP without manual adjustment.
- A reconciliation routine that catches breaks before they compound.
Policy elements should define the mandate, set Value at Risk thresholds for when a hedge is triggered, and set authorization limits by trade size. The FX Global Code framework stresses separating trade execution from risk oversight, so the person who books the forward is not the same person who signed off on the exposure calculation.
| Control area | What it covers | Why it matters |
|---|---|---|
| Data integrity | ERP extracts, bank feeds, reconciliation | Prevents hedging the wrong exposure size |
| Policy mandate | VaR thresholds, authorization limits | Defines when and how much to hedge |
| Segregation of duties | Execution vs. risk sign-off | Reduces conflict-of-interest risk |
| Audit trail | Trade logs, approval records | Supports year-end review and auditor requests |
Metrics worth tracking week to week are covered in more detail in this rundown of signs of effective FX hedging.
How Does Automation and VaR-Based Policy Design Work in Practice?
Automation earns its keep on repeatability. Instead of a treasury analyst manually pulling exposure data every Friday, an automated system extracts net AR/AP and bank liquidity, calculates the hedge adjustment on a set cycle, and presents a trade for approval. Repeatable, auditable cycles are what make back-testing possible and what give an audit committee confidence the program runs the same way every period.
VaR plays a specific role here: it sizes and triggers hedges based on the potential loss a currency position could generate over a given horizon, rather than hedging every exposure at 100% regardless of materiality. CorpHedge builds its recommendations around this VaR-based approach, pairing exposure tracking with ERP integration so the netting and the trade recommendation happen in the same workflow, with governance review sitting on top before anything executes.
- Weekly (or period-end) netting cycle pulls AR, AP, intercompany, and cash automatically.
- VaR thresholds flag when an exposure crosses a materiality limit worth hedging.
- Governance review remains a human step before trade execution, preserving the separation of duties auditors expect.
Pro Tip: Do not automate the approval step, only the calculation. Keep a human sign-off between the system's recommendation and the executed trade, at least for the first two or three cycles.
What Challenges Come Up and How Do You Mitigate Them?
Timing mismatches are the most common failure point: a receivable settles a week later than the forward matures, and now the hedge and the hedged item are misaligned. Liquidity shortfalls come next, particularly when a forward requires cash settlement at a moment the entity's local account is tight.
To detect ineffectiveness, compare the actual FX gain or loss on the hedged item against the gain or loss on the hedge itself each period, and document the variance. Auditors want to see that variance tracked, not just the net P&L number.
Practical mitigations include:
- Favor shorter tenors that match settlement dates more precisely.
- Keep a cash buffer in the settlement currency to avoid liquidity crunches.
- Set tolerance bands so small mismatches do not trigger unnecessary rebalancing.
- Reconcile hedge and exposure positions on a fixed schedule, not ad hoc.
What Should Treasury Ask Before Starting a Program?
Before committing budget or headcount to a balance sheet hedging program, run through this sequence:
- Is your exposure data clean enough to trust, with ERP extracts and bank feeds that reconcile?
- Have you defined governance and VaR triggers, including who approves a hedge above a given threshold?
- Can your team execute and reconcile short-dated forwards within your normal operating cycle?
- Who has trade approval authority, and where does the audit trail live?
- What is the contingency plan if a currency moves sharply between review cycles or liquidity tightens unexpectedly?
If any of those questions produce a shrug rather than an answer, that is the gap to close first, before adding more currency pairs or automation layers.
Pragmatic Choices for Mid-Market Treasury Teams
Most mid-market treasuries overbuild before they need to. Start with a manual, weekly netting cycle on your two or three largest currency pairs before automating anything. The trade-off between control and scale is real: automation buys speed, but only after your data and governance are trustworthy enough to act on without daily manual checks. Clean exposure data and a documented mandate get a program credible faster than any software purchase does.
— Bartas
Get Started With CorpHedge's Hedging Platform
CorpHedge is the practical next step once you have decided balance sheet hedging fits your exposure profile. Instead of building netting spreadsheets by hand, the platform tracks currency positions in real time, applies VaR-based triggers to size and time hedges, and integrates with ERP systems so the exposure data feeding your hedge calculations stays current without manual re-entry.
Beyond the platform, CorpHedge offers operational expert advice and Risk Safari Tours for teams that want hands-on implementation support, and a standalone FX hedging course for finance professionals who want structured training before automating a program. CorpHedge offers exposure tracking and VaR tools for treasury teams managing FX risk. If you want to see how the netting and trade recommendation workflow looks in practice, walk through the CorpHedge use cases or take the product tour to evaluate whether automation fits your current setup.
Primary Sources and Recommended Reading
For deeper reading on hedging program design, see the ACT's guidance on choosing an FX hedging path, IAS Plus on IFRS 9 for treasurers, and the ECB's 2025 annual accounts on balance sheet revaluation. Financial systems governance is covered in this guide to securing financial systems.
Sources
- FX hedging: how to choose the right path | The Association of Corporate Treasurers
- Key points that treasurers need to know about IFRS 9 | IAS Plus
- ECB annual accounts 2025 (annual-accounts2025)
FAQ
What Is the Difference Between a Cash-Flow Hedge and a Balance Sheet Hedge?
A cash-flow hedge protects a forecasted future transaction that has not yet been booked, while a balance sheet hedge offsets remeasurement risk on monetary items already recorded, like receivables or intercompany loans. Balance sheet hedges typically settle faster and rarely need formal hedge accounting, since the hedge and hedged item often hit the P&L in the same period.
What Does Hedging Mean in Accounting?
In accounting, hedging means entering into an instrument, usually a forward or swap, whose gain or loss is expected to offset the gain or loss on an existing or forecasted exposure. Under IFRS 9, certain hedges qualify for formal hedge accounting treatment, which changes how gains and losses are recognized between the P&L and other comprehensive income.
How Do You Account for Hedging Transactions?
Most balance sheet hedge transactions are recorded at fair value through profit or loss, with the gain or loss on the hedge offsetting the remeasurement loss or gain on the underlying monetary item in the same period. Formal hedge accounting under IFRS 9 is only required for certain hedge types, such as cash-flow or net investment hedges, where the timing of recognition needs to be matched more precisely.
What Is an Example of Hedging?
A subsidiary with $2 million in euro-denominated receivables can enter a short-dated forward contract to sell euros at a locked rate, offsetting the risk that the euro weakens before settlement. Platforms like CorpHedge automate this by netting exposures and sizing the forward based on VaR thresholds rather than hedging the full gross amount.