Hedge Designation Documentation Template (IFRS 9, ASC 815)

Hedge Designation Documentation: [Hedge relationship ID]

Formal designation and documentation of one hedging relationship at its inception, as required for hedge accounting under IFRS 9 Financial Instruments (paragraph 6.4.1(b)) and, for US GAAP reporters, ASC 815 Derivatives and Hedging (paragraph 815-20-25-3). It records the risk management objective and strategy, the hedged item and risk, the hedging instrument, the hedge ratio, how effectiveness is assessed, the sources of ineffectiveness, excluded components, accounting entries, ongoing assessment, rebalancing and discontinuation. It notes ASU 2025-09 Hedge Accounting Improvements (effective for public business entities for fiscal years beginning after 2026-12-15) and treats the IASB Risk Mitigation Accounting exposure draft (December 2025) as a proposal only. Standards are cited by name and paragraph number only. Replace every [bracketed] value and every row marked Example. The worked example is a cash flow hedge of forecast USD platform-fee receipts of Corvid Commerce GmbH, the German operating subsidiary and treasury centre of the fictional Corvid Commerce Group (parent Corvid Commerce Group plc; EUR functional currency; IFRS reporter), which carry the group's net long USD position from US subscription sales. This is a document format, not accounting, financial, tax or legal advice. Obtain the standard for the normative text.

Document control

Approvals

Revision history

Contents

• 1. Relationship summary
• 2. Risk management objective and strategy
• 3. Hedge type and qualifying criteria
• 4. Hedged item and hedged risk
• 5. Hedging instrument
• 6. Hedge ratio
• 7. Effectiveness assessment
• 8. Sources of ineffectiveness
• 9. Excluded components and cost of hedging
• 10. Measurement and accounting entries
• 11. Rebalancing and discontinuation
• 12. US GAAP supplement
• 13. Disclosure links and requirement traceability
• 14. Glossary and references
• Appendix A. Fields for other hedge types
• Standard and licence note

1. Relationship summary

2. Risk management objective and strategy

Example:

3. Hedge type and qualifying criteria

3.1 Judgement on the intragroup hedged item (Example)

JDG-HDG-01. Corvid is net long USD because Corvid Commerce Inc (CC-US) sells subscriptions in USD (FY2027 budget USD 24,640k against USD 4,107k of USD costs, a net USD 20,533k, assumption ASM-014 in the Annual Budget, finance/annual-budget). CC-US has USD as its functional currency, so its own sales create no transaction exposure in its books, and in the consolidated statements their EUR value moves only through translation, which cannot be a cash flow hedged item. The exposure becomes a transaction exposure for a EUR entity when CC-US pays CC-DE the monthly USD platform fee under the intragroup licence agreement (forecast USD 16,000k for FY2027). The group financial controller concluded that the fee qualifies as a hedged item in the consolidated statements because it is denominated in a currency other than CC-DE's functional currency and it is directly linked to CC-US's external subscription sales, which are the related external transaction. The reserve is therefore reclassified to revenue in the month in which the related external subscription revenue is recognised (section 10.4).

Record this conclusion in a Technical Accounting Memo (finance/technical-accounting-memo) and agree it with the auditor before the first designation, because the qualifying conditions for forecast intragroup transactions are narrow: an intragroup fee that is not tied to an external transaction does not qualify in the consolidated statements, and the group would then either accept the FX result in profit or loss or consider a net investment hedge (Appendix A.2). Review the judgement whenever the intragroup agreement, the fee basis or the transfer pricing policy changes.

4. Hedged item and hedged risk

4.1 Description

4.2 Highly probable evidence

4.3 Writing a hedged item description that works

Write the description for the person who will match receipts to the hedge six months from now, not for the person who traded it. That person needs to know which entity receives, from whom, in which currency, in which window and in which order transactions are counted. A description such as "USD receipts in Q2" fails this test because it does not say whether a May fee paid early counts before an April fee paid late, whether receipts by another subsidiary count at all, or whether an intragroup flow is meant rather than an external one.

Prefer a layer ("the first USD 1,000,000") over a percentage of a total ("75% of the April fee"). A layer stays fully designated if the total falls but remains above the layer, while a percentage shrinks with every change in the forecast and forces a partial discontinuation. Keep a buffer between the layer and the forecast that reflects the forecast's track record; the evidence in 4.2 should justify the size of the buffer, not only the existence of the forecast.

State the timing window and what happens outside it. If settlement can slip, say how many days of slippage still count as the same transaction, and record in section 8 that a slip changes the forward points and is a source of ineffectiveness. Finally, link the description to the exposure register entry used by treasury (here EXP-USD-2027Q2), so that the hedge file, the register and the monthly hedge report all describe the same thing.

5. Hedging instrument

Contract rate check (Hedging Policy section 7.2): spot 1.0950, USD rate 4.00%, EUR rate 2.00%, 179 days from 2026-11-02 to 2027-04-30.

EUR leg: 1,000,000 / 1.1058 = EUR 904,322.66.

6. Hedge ratio

7. Effectiveness assessment

7.1 Requirements and evidence

7.2 Methods available

Dollar offset ratio (cumulative, from inception):

where $\Delta V_{\text{hedged item}}$ is measured with a hypothetical derivative whose terms match the hedged item and whose fair value at inception is nil.

Regression (practice): estimate $\Delta V_{\text{item}} = \alpha + \beta \, \Delta V_{\text{instrument}} + \varepsilon$ and record the slope, coefficient of determination and the number and frequency of observations. Many US GAAP reporters apply ranges for "highly effective" such as a slope magnitude between 0.80 and 1.25 and a coefficient of determination of at least 0.80; record the thresholds the group uses and their source in its accounting policy.

7.3 Assessment schedule

8. Sources of ineffectiveness

9. Excluded components and cost of hedging

10. Measurement and accounting entries

10.1 Conventions

All amounts in EUR to two decimals. EUR/USD quoted as USD per EUR. Discounting at the EUR rate on an ACT/360 basis. Fair values exclude settlement-date bid-offer.

10.2 Cash flow hedge reserve (IFRS)

Under IFRS 9 para 6.5.11(a), the reserve is adjusted to the lower, in absolute terms, of the cumulative gain or loss on the instrument and the cumulative change in fair value of the hedged item (both from inception). Any remaining gain or loss on the instrument is ineffectiveness in profit or loss.

with the sign of the instrument's gain or loss.

10.3 Worked example at 2026-12-31 (Example)

Market forward rate for 2027-04-30: 1.0800; 120 days to settlement; EUR discount rate 2.00%; discount factor 1 / (1 + 0.02 x 120/360) = 0.99337748 (used unrounded below). The USD has strengthened since the trade (fewer USD per EUR), so the forecast receipt is worth more in EUR and the forward, which sells USD at 1.1058, has lost value.

The instrument lost less than the hedged item gained (an under-hedge), so the whole loss goes to the reserve and no ineffectiveness is recognised.

10.4 Settlement and reclassification at 2027-04-30 (Example)

Spot EUR/USD 1.0750 on 2027-04-30; debit valuation adjustment nil at settlement. The April 2027 platform fee received on 2027-04-30 is USD 1,330,000, so the first USD 1,000,000 (the designated layer) occurs on that date and the remaining USD 330,000 is converted at spot outside the hedge. For simplicity the example assumes that the April average rate used to translate CC-US's April subscription revenue equals the 2027-04-30 spot rate; any difference is a translation difference outside the hedge.

The fee itself is eliminated on consolidation, so the reclassification is presented in the revenue line that carries the related external subscription revenue, as the group's accounting policy states. Unlike a hedge of a purchase of inventory, no non-financial asset is recognised, so no basis adjustment arises and the amount passes through OCI as a reclassification adjustment. Under US GAAP the amount is also reclassified from accumulated OCI to the same earnings line when the hedged transaction affects earnings (section 12).

10.5 Reporting-date routine

At each reporting date, work through the same steps in the same order and file the results with this document. First, confirm the hedged item is still highly probable: refresh the evidence in 4.2 from the latest rolling forecast and note any change in the fee basis, currency or timing. Second, repeat the effectiveness assessment in section 7 and record it in 7.3, even when the critical terms still match. Third, obtain the instrument's fair value from the valuation source named in the hedging policy, including the credit adjustment, and rebuild the hypothetical derivative with the same curves. Fourth, compute the cumulative amounts, apply the lower-of test, and post the reserve and any ineffectiveness. Fifth, agree the reserve balance for this relationship to the hedge reserve reconciliation used for the disclosures.

The reviewer should recompute at least one line of the table independently, check that the dates and day counts match the trade confirmation, and confirm that no event in section 11 has occurred without being logged. A reporting-date file that only contains the valuation statement from the bank is not enough: it shows what the derivative is worth, not whether the relationship still qualifies.

11. Rebalancing and discontinuation

11.1 Triggers and responses

11.2 Event log

11.3 Review points and common errors

Review the document twice: once before the trade, for design, and once after the first reporting date, for operation. The design review asks whether a reader with no other information could identify the hedged transactions, the instrument and the method from this document alone, and whether every field in the summary table agrees with the detailed sections. The operation review asks whether the numbers in section 10 can be rebuilt from the confirmation, the valuation and the forecast.

The errors auditors find most often are predictable. The first is late documentation: a designation signed after the trade, or a draft approved by email with no time stamp, which cannot support hedge accounting from the trade date. The second is an over-hedge that nobody noticed because the forecast was updated in the planning system but not in the hedge file; when the forecast falls below the designated layer, part of the relationship must be discontinued and the reserve for that part treated under section 11. The third is a mismatch between the policy and the designation, for example a forward that exceeds the band maximum or a dealer who traded above their authority; the relationship may still qualify for hedge accounting, but the breach must be reported under the hedging policy. The fourth is a hypothetical derivative built with different curves, dates or notional from the hedged item, which creates ineffectiveness that does not exist in the economics.

Two further points deserve attention in groups. When the instrument is held by one entity and the hedged item belongs to another, record clearly in which financial statements the relationship is designated (consolidated, individual or both) and whether an internal back-to-back contract exists. When a relationship is discontinued, keep this document and add the event to the log rather than deleting it; the reserve can remain in equity for months after the instrument has gone, and the trail must explain why.

12. US GAAP supplement

13. Disclosure links and requirement traceability

13.1 Disclosure feed

Use the Financial Statement Disclosure Checklist (finance/financial-statement-disclosure-checklist) to confirm completeness.

13.2 Traceability matrix

14. Glossary and references

14.1 Glossary

14.2 References

• IFRS 9 Financial Instruments, Chapter 6 and Appendix B (paras B6.x); IFRS 7 Financial Instruments: Disclosures; IFRS 13 Fair Value Measurement (IFRS Foundation; names and paragraph numbers only).
• IASB Exposure Draft, Risk Mitigation Accounting, proposed amendments to IFRS 9 and IFRS 7 (December 2025; comment deadline extended to 2026-11-30). Proposal only; not applicable until issued as a standard.
• FASB ASC 815 Derivatives and Hedging (subtopics 815-20, 815-25, 815-30, 815-35); ASU 2025-09, Derivatives and Hedging (Topic 815): Hedge Accounting Improvements, issued November 2025 (topic and paragraph numbers only).
• FX and Interest Rate Hedging Policy (finance/fx-interest-rate-hedging-policy) and Treasury Policy (finance/treasury-policy).

Appendix A. Fields for other hedge types

A.1 Fair value hedge (for example fixed-rate debt with a receive-fixed swap)

A.2 Net investment hedge (for example GBP borrowing hedging a UK subsidiary)

Standard and licence note

Structure aligned with the hedge documentation requirements of IFRS 9 (paragraph 6.4.1(b)) and FASB ASC 815 (paragraph 815-20-25-3). IFRS 9, IFRS 7, IFRS 13, the IASB Risk Mitigation Accounting exposure draft, FASB ASC 815 and ASU 2025-09 are cited by name and paragraph or topic number only; no text from IFRS Foundation or FASB material is reproduced or paraphrased, and neither body endorses this template. IFRS is a trade mark of the IFRS Foundation. The fields, methods, worked example and wording are original; regression thresholds are described as common practice, not as requirements. Check the current official version of each standard, any amendments and the group's adoption status before use. Corvid Commerce Group and every figure are fictional. Template licence: MIT.