Audit Ready IFRS 9 Hedge Documentation with €2,000,000 Worked Example

IFRS 9 requires formal, inception-date documentation naming the hedging instrument and hedged item, stating the risk-management objective and strategy, defining the risk being hedged, setting out the effectiveness assessment method, listing expected sources of ineffectiveness, and recording the hedge ratio. Miss any element and the hedge relationship does not qualify for hedge accounting from that date forward. The immediate action: draft the inception record before the trade settles, and build a calendar for reassessment at every reporting date.

TL;DR:

• Accurate hedge documentation must record a clear risk management objective linked to governance policies, specifying the decision-makers and business outcomes protected.
• Every hedge file needs a unique reference, a precise identification of both the hedge instrument and the hedged item, and explicit details of the risk being hedged.
• Effectiveness assessments must be performed at inception, each reporting date, and upon material changes, with detailed records of methods, data sources, and reviewer sign-offs.
• Rebalancing involves documenting any ineffectiveness before adjusting the hedge ratio, ensuring the risk management approach remains aligned without gaps or inaccuracies.
• Most audit failures stem from missing or stale documentation of sources of ineffectiveness, outdated ratios, lack of sign-offs, or incomplete records, which can be prevented through disciplined governance.

Table of Contents

• What Does IFRS 9 Hedge Documentation Need to Include?
• How Do You Test and Document Hedge Effectiveness?
• Setting the Hedge Ratio and Handling Rebalancing
• What Does a Hedge Documentation Template Look Like in Practice?
• How Do Disclosures and Transition Rules Connect to the Documentation File?
• Where Do Most Companies Fail Their Hedge Documentation Audit?
• How CorpHedge Turns Documentation Fields Into Platform Data
• The Documentation Problem Nobody Talks About Enough
• How CorpHedge Supports IFRS 9 Documentation Workflows
• Sources
• FAQ

What Does IFRS 9 Hedge Documentation Need to Include?

Auditors reviewing a hedge file are checking for seven specific things, and if even one is missing or vague, the whole relationship can lose hedge accounting treatment retroactively to inception. IFRS Foundation's Chapter 6 guidance spells these out explicitly, and PwC's practical commentary fills in what "good enough" looks like in practice. Here is what each element actually demands.

Risk management objective and strategy. This is not a boilerplate sentence copied from last year's file. The objective has to tie back to an actual corporate treasury policy, name the decision-makers who approved the hedge, and explain what business outcome the hedge protects. A treasurer hedging a forecast EUR receivable might write: "To protect budgeted gross margin on the Q3 European sales forecast from EUR/USD depreciation, per the Board-approved FX Risk Policy dated January 2026." That sentence does real work. It links the hedge to a governance document, states the currency pair, and gives a timeframe. A vague version like "to manage FX risk" gives an auditor nothing to test against.

Identification of the hedging instrument and hedged item. Every instrument needs a unique trade or deal reference, ideally pulled straight from the treasury management system or ERP. The hedged item needs equal precision: is it a specific invoice, a layer of a forecast transaction population, or a risk component of a larger item? IFRS 9 permits hedging a risk component (say, just the commodity-price element of a purchase contract) as long as that component is separately identifiable and reliably measurable. Document which approach applies, and if you are hedging a layer of a larger forecast population (the first $2 million of expected Q4 purchases, for example), state the layer boundaries explicitly.

Nature of the risk being hedged. "FX risk" is not a risk category anyone can test effectiveness against. The documentation needs the specific risk variable: EUR/USD cash flow risk on a forecast purchase, USD/PLN translation risk on a subsidiary loan, or the benchmark interest-rate component of a floating-rate liability. If the entity is only hedging one risk component out of several embedded in an instrument (interest rate but not credit spread, for instance), say so and explain how that component is isolated.

The hedge ratio. Record the formula used, the source data behind it, and the reasoning that ties the ratio back to how the business actually manages the risk.

Expected sources of ineffectiveness. This is the field auditors flag most often, according to PwC's practical guidance on hedge accounting, because most companies write a single generic line instead of a real analysis. Common sources worth naming individually include timing mismatches between when the hedge settles and when the hedged cash flow actually occurs, changes in the notional quantity of the forecast transaction, and counterparty credit risk becoming a material driver of the instrument's fair value. A cash flow hedge of a forecast inventory purchase, for example, should flag quantity risk (the order might come in smaller than forecast) as a distinct, named source rather than folding it into a generic "market risk" catch-all.

Here is the shortlist auditors expect to see addressed, item by item, rather than glossed over:

• Timing differences between hedge settlement and hedged item cash flow
• Quantity or volume changes in the forecast transaction
• Basis differences (different reference rates, indices, or delivery points)
• Counterparty or own credit risk affecting instrument fair value
• Currency basis spread on cross-currency instruments

Each of these needs a sentence explaining why it might apply to this specific hedge, not a copied list from a template with no analysis attached.

How Do You Test and Document Hedge Effectiveness?

IFRS 9 replaced the old 80 to 125 percent bright-line test with a principles-based approach centered on whether an economic relationship exists between the hedging instrument and the hedged item, and whether credit risk dominates the value changes in that relationship. Both checks need to happen, and both need paper evidence behind them.

The economic relationship test asks a simple question with a not-always-simple answer: do the instrument and the hedged item move in offsetting directions because of the same underlying risk? For a forward contract hedging a forecast EUR purchase, the answer is usually straightforward. For a hedge involving basis differences, such as hedging a jet fuel purchase with a Brent crude derivative, the relationship needs more careful documentation of the correlation and the reasons the two prices move together.

The credit-risk dominance check confirms that changes in counterparty or own credit risk are not swamping the value changes driven by the hedged risk itself. This matters more for longer-dated hedges and for instruments with weaker counterparties, where credit spread movements can start to overwhelm the FX or rate movement the hedge is meant to capture.

Which method you use, and how often, depends on the complexity of the hedge:

1. Qualitative assessment (critical terms match). Appropriate when the critical terms of the instrument and the hedged item align closely, meaning matching notional, currency, maturity, and underlying. This is common for straightforward forward-contract hedges of forecast FX purchases and requires only a written comparison of the terms, not a statistical model.
2. Quantitative regression analysis. Used when critical terms do not fully match, or when the relationship needs statistical support, such as hedging with an instrument that references a related but distinct underlying. Document the regression period, the R-squared or slope coefficient, and the data source.
3. Ratio analysis (dollar-offset method). Compares cumulative changes in the value of the hedging instrument against the hedged item over the assessment period, useful as a supplementary check alongside qualitative assessment.

Run these tests at inception, at every reporting date, and immediately whenever there is a material change in circumstances, such as a counterparty credit downgrade, a change in the forecast transaction's timing, or a shift in the underlying business exposure. PwC's guidance on achieving hedge accounting in practice recommends aligning the reassessment calendar to the entity's actual reporting dates rather than running tests on an arbitrary schedule, since that is what auditors will ask to see evidence of first.

Every test needs a saved record: the calculation itself, the model parameters and data source used, the date it was run, and a named sign-off from whoever in treasury or finance reviewed the result. A spreadsheet with no date stamp and no reviewer name is not documentation, it is a file that happens to contain numbers.

Pro Tip: Build the reassessment dates into your treasury calendar the same week you designate the hedge, not the week before the next reporting deadline. Auditors notice when every effectiveness test in a file was run in the three days before quarter-end.

Setting the Hedge Ratio and Handling Rebalancing

The hedge ratio used for accounting has to match the ratio actually used for risk management. IFRS 9 is explicit on this point: a company cannot designate a ratio purely to smooth accounting outcomes if that ratio creates an imbalance capable of generating ineffectiveness the actual risk management approach would never accept.

Designation also comes in two flavors, and the choice has consequences. A specific designation names one instrument against one hedged item, which is simple to document but breaks the moment either side is refinanced or replaced. A generic designation can allow the hedge relationship to continue through a refinancing event, provided the underlying risk characteristics stay the same, a nuance worth building into treasury policy from the start rather than discovering after a loan rollover forces an unplanned de-designation.

• Specific designation: cleaner audit trail, but any instrument replacement (a refinanced loan, a rolled forward contract) typically requires full re-designation and fresh documentation.
• Generic designation: more resilient through refinancing and rollover events, but requires more detailed upfront documentation explaining why the risk profile survives the change.
• Rebalancing (not re-designation): adjusts the existing hedge ratio without ending the relationship, provided the risk-management objective is unchanged.

Rebalancing itself follows a strict sequence. When the actual ratio drifts from the designated ratio, whether because the notional of the hedged item changed or the instrument's terms shifted, the entity must first recognize and document any hedge ineffectiveness that exists immediately before adjusting the ratio. Only after that ineffectiveness is captured does the documentation get updated with the new ratio and a written rationale for the change. Skipping the "recognize ineffectiveness first" step is one of the more common technical errors treasury teams make when they rebalance in a hurry.

A practical rollover example: a company hedging a 12-month forecast USD payable with a series of three-month forward contracts needs to document, at each rollover, whether the new forward is a continuation of the same hedge relationship (if the underlying forecast is unchanged) or a fresh designation. CorpHedge's guide to hedge accounting for currency risk management walks through how to keep that designation trail consistent across rollovers so the file does not fragment into a dozen disconnected records for what is really one ongoing hedge program.

What Does a Hedge Documentation Template Look Like in Practice?

A usable template needs a fixed set of fields, populated with enough specificity that a reviewer three years from now, who was not in the room when the hedge was designated, can reconstruct exactly why the relationship qualifies for hedge accounting. PwC's worked template and illustrative example is the industry reference point for the level of detail expected.

The core fields any template needs:

• Unique hedge reference number and designation date
• Risk management objective and strategy statement
• Hedging instrument identifier (trade reference, counterparty, notional, maturity)
• Hedged item identifier (transaction, layer, or risk component, with forecast date if applicable)
• Risk category being hedged (specific currency pair, rate, or commodity)
• Hedge ratio, with formula and supporting data
• Effectiveness assessment method and assessment frequency
• Expected sources of ineffectiveness, listed individually
• Scheduled review and reassessment dates
• Sign-off name and date

A worked example makes this concrete. Say a company enters a forward contract on January 15, 2026, to buy €2,000,000 in six months, hedging a forecast inventory purchase from a European supplier. The spot rate at inception is 1.0850 USD/EUR and the six-month forward rate is 1.0910. The documentation would record the hedged amount (€2,000,000), the forward rate locked in (1.0910), the spot rate at inception (1.0850) for calculating the forward element, and the expected settlement date (July 15, 2026). The hedge ratio here is 1:1, since the forward notional matches the forecast purchase exactly, and the effectiveness method is critical terms match, since currency, notional, and maturity all align between instrument and hedged item.

The table below shows how those fields map into a populated record.

Storing this in a spreadsheet works for a handful of hedges. Once a treasury desk is running dozens of forward contracts across multiple currency pairs, the audit trail gets fragile fast, since each rollover, rebalancing, or de-designation needs its own dated record linked back to the original. A treasury or ERP system that timestamps every trade against its hedge designation reference removes most of the manual reconciliation work at quarter-end.

Pro Tip: Assign the hedge reference number in your treasury system before you execute the trade, not after. That single sequencing habit is the difference between an audit trail and a reconstruction project.

For the actual ratio math behind more complex designations, CorpHedge's breakdown of hedge ratio calculation walks through the formula and a worked calculation you can adapt directly into the template above.

How Do Disclosures and Transition Rules Connect to the Documentation File?

The hedge documentation file is not just an internal audit artifact. It is the direct source for several IFRS 7 disclosure requirements, which means gaps in the file show up as gaps in the financial statements themselves.

IFRS 7 disclosures draw on the documentation in three main areas:

• Risk management strategy disclosures, which summarize the objective and strategy statements from each hedge file into a coherent narrative about how the entity manages FX, interest rate, or commodity risk overall.
• Effects on the timing and amount of future cash flows, which pulls directly from the hedged item identification and expected settlement dates recorded at designation.
• Impact on the primary financial statements, including the cash flow hedge reserve movement and reclassification adjustments, which requires the ineffectiveness figures captured during ongoing effectiveness testing.

There is also a standing accounting-policy choice worth flagging for any entity still running portfolio fair-value hedges of interest-rate risk. IFRS 9 permits continued application of the IAS 39 portfolio hedge requirements for that specific case, pending the completion of the macro-hedging project, rather than forcing immediate transition to IFRS 9's general model. That choice needs to be documented as a policy decision, and it affects which set of documentation rules apply to those specific hedges.

For companies that transitioned from IAS 39 to IFRS 9 and carried forward existing hedge relationships, the transition documentation needs updating to include two things IAS 39 never required: an explicit hedge ratio statement and a written analysis of expected sources of ineffectiveness. Entities that migrated hedge files without adding these two elements are sitting on documentation gaps that will surface the moment an auditor pulls a legacy file for testing. If your organization has not revisited pre-transition hedge files against the current checklist, that is worth doing before the next audit cycle rather than during it.

CorpHedge's guide to cash flow hedging programs covers how the cash flow hedge reserve and reclassification mechanics tie back to the disclosure requirements in more depth.

Where Do Most Companies Fail Their Hedge Documentation Audit?

The same handful of mistakes show up across most audit findings, and nearly all of them are fixable with a governance process rather than a bigger accounting team.

1. Vague or generic sources of ineffectiveness. A single line reading "market volatility" is not an analysis. PwC's commentary on hedge documentation notes this is the single most common audit criticism: auditors expect a specific explanation of why ineffectiveness might occur for this hedge, not confirmation that the hedge is currently effective.
2. Hedge ratios that drift from stated risk management practice. If treasury policy says hedge 75% of forecast exposure but the documented ratio says 100%, that mismatch invites scrutiny even if both numbers are internally consistent with something.
3. Stale templates copied forward without updates. A hedge file dated three reporting periods ago, with no evidence of a reassessment in between, tells an auditor nobody has looked at whether the relationship still qualifies.
4. Missing sign-offs and dates. A calculation with no reviewer name and no date attached is not evidence, whatever the numbers say.
5. No retrospective note on rebalancing events. When a ratio changes, the file needs to show the ineffectiveness that was recognized before the ratio adjustment, not just the new ratio after the fact.

The remediation checklist is short: pull every active hedge file and confirm each one has a dated effectiveness test from the most recent reporting period, a named sign-off, and a specific (not generic) ineffectiveness analysis. Where a file is missing any of these, add a retrospective note explaining the gap and the corrective action taken, since auditors respond far better to documented remediation than to silence.

Build an audit evidence folder per hedge relationship that holds the designation memo, every effectiveness test with its underlying data, the sign-off record, and any rebalancing notes, all timestamped and version controlled. CorpHedge's overview of signs of effective FX hedging lists the operational metrics worth tracking alongside this file so the evidence folder doubles as a performance record, not just a compliance one.

Pro Tip: Run a mock audit on three random hedge files every quarter, picked by someone outside the treasury team. Finding the gaps yourself in March beats an external auditor finding them in your year-end review.

How CorpHedge Turns Documentation Fields Into Platform Data

Most of the fields IFRS 9 demands already exist somewhere in a treasury operation, scattered across trade confirmations, spreadsheets, and email chains. The documentation burden usually comes from stitching those pieces together consistently, not from the substance itself.

A platform built around live position tracking naturally captures several required fields as a byproduct of normal operations rather than as a separate compliance exercise:

• Trade-level references and counterparty data feed directly into the hedging instrument identification field.
• Value at Risk workflows generate the data behind hedge ratio justification, since the same exposure calculations that drive VaR-based strategy also support the ratio's link to actual risk management practice.
• Scheduled reporting cycles map onto the reassessment calendar IFRS 9 requires at each reporting date, rather than leaving reassessment dates to manual tracking.
• Governance workflows with sign-off steps produce the reviewer name and date trail auditors look for on every effectiveness test.

CorpHedge's approach to VaR-based hedging is built around this overlap: the same position and exposure data that supports a hedging decision is the data an auditor eventually asks to see justifying the hedge ratio. That does not replace the judgment behind writing a risk management objective or analyzing sources of ineffectiveness, but it does mean the numeric backbone of the documentation file is already assembled before anyone starts drafting.

The Documentation Problem Nobody Talks About Enough

Most guidance on IFRS 9 hedge documentation treats it as a one-time drafting exercise: fill in the template at inception, file it, move on. That framing is wrong, and it is why so many companies fail audits on hedges that were perfectly well designed. The real difficulty is not writing the initial file. It is keeping seven distinct fields current across dozens of live hedge relationships as forecasts shift, ratios rebalance, and counterparties change, quarter after quarter.

The conventional advice to "document at inception and reassess as required" undersells how often "as required" actually triggers. A shipment delay, a credit downgrade, a revised sales forecast: any one of these can force a reassessment, and most treasury teams do not have a system that flags these triggers automatically. They find out during the next audit cycle instead.

If you take one thing from this, prioritize the sources of ineffectiveness analysis over everything else. It is the field auditors flag most, the one companies write most generically, and the one that actually forces you to think through whether your hedge will hold up under real market conditions rather than an ideal one.

— Bartas

How CorpHedge Supports IFRS 9 Documentation Workflows

Corphedge is the alternative to rebuilding your hedge documentation process from scratch in spreadsheets every quarter. Instead of chasing trade confirmations, VaR calculations, and reassessment dates across separate systems, the platform keeps transaction identifiers, scheduled effectiveness reports, and VaR-based strategy records in one place, which is exactly the data an auditor asks for when reviewing a hedge file.

As Corphedge expands into the Poland and Sweden markets, the same governance workflows apply for finance teams managing EUR, PLN, SEK, and USD exposures across borders. If you want to see how position tracking and scheduled reporting map onto the IFRS 9 fields covered here, start with the product tour to see how trade-level references and audit trail data get captured automatically. If your team is still building internal expertise on hedge accounting mechanics, the FX Hedging course in the CorpHedge Academy covers the practical side of designation and effectiveness testing your documentation team will need. For companies specifically evaluating a VaR-based approach to hedge ratio justification, the VaR hedging page explains how that maps to the ratio field auditors review.

Sources

Keep three references close when drafting or reviewing hedge documentation. The IFRS Foundation's Chapter 6 text is the formal standard language every documentation field ultimately traces back to. PwC's practical guidance and worked template shows the level of numeric and narrative detail auditors expect, including the illustrative cash flow hedge example referenced earlier. CorpHedge's own advanced FX risk accounting strategies guide covers designation choices for multinational hedge programs in more depth than fits in a single article.

• IFRS Foundation — IFRS 9 (Chapter 6) hedge accounting
• PwC — Achieving hedge accounting in practice under IFRS 9 (practical guidance)

FAQ

What Are the Requirements for Hedge Accounting Under IFRS 9?

Hedge accounting under IFRS 9 requires formal documentation at inception naming the hedging instrument, the hedged item, the risk category, the risk management objective, the effectiveness assessment method, expected sources of ineffectiveness, and the hedge ratio, plus ongoing effectiveness testing at each reporting date.

How Do You Account for a Fair Value Hedge?

A fair value hedge recognizes changes in the fair value of both the hedging instrument and the hedged item's designated risk in profit or loss for the period, with any difference between the two representing hedge ineffectiveness, which must also be separately identified in the documentation.

How Often Must Hedge Effectiveness Be Reassessed?

Effectiveness must be assessed at hedge inception, at every subsequent reporting date, and immediately whenever circumstances change materially, such as a counterparty credit event or a shift in the forecast transaction.

What Happens if Hedge Documentation Is Incomplete or Missing a Required Field?

If the documentation is incomplete at inception or missing a required element, the hedge relationship generally does not qualify for hedge accounting from that date, which means gains and losses on the instrument flow through profit or loss without the offset a properly designated hedge would provide.

Can Existing Hedge Documentation From IAS 39 Still Be Used Under IFRS 9?

Legacy IAS 39 documentation can be carried forward, but it typically needs updating to add an explicit hedge ratio statement and a written analysis of expected sources of ineffectiveness, since IAS 39 did not require either field.

Recommended

• Advanced accounting for FX risk: Strategies for global companies
• CorpHedge accounting service: 45% less earnings volatility
• The Foreign Currency Audit Checklist for Central Europe