IFRS 9 designation traps that quietly cost balance sheets at year-end

A well-built economic hedge can still cause a P&L problem if the accounting around it wasn't designed correctly at the outset. This is one of the more common — and more avoidable — surprises finance teams run into at year-end, and it almost always traces back to decisions made (or skipped) months earlier, at the point the hedge was put on.

The trap: designation after the fact

IFRS 9 requires formal hedge documentation at inception — the risk management objective, the hedged item, and the hedging instrument all need to be documented before or at the point the hedge is executed, not reconstructed afterwards to justify the accounting treatment you'd like to achieve. Retrospective documentation is one of the most common findings auditors raise, and it can force a business to unwind hedge accounting treatment it was otherwise economically entitled to.

Where effectiveness testing quietly breaks down

A second common trap sits in effectiveness testing. A hedge that was highly effective at inception can drift as the underlying exposure changes — a forecast transaction gets rescheduled, a loan gets refinanced, a hedge ratio no longer matches the revised exposure. IFRS 9's more principles-based approach to effectiveness testing (relative to the old IAS 39 bright-line tests) gives more flexibility, but it also puts more responsibility on the business to keep testing methodology current and genuinely reflective of the hedge relationship, not just a rolled-forward spreadsheet from the prior period.

Documentation that survives an audit, not just a transaction

The standard a hedge documentation file needs to meet isn't "did the treasury team understand what we were doing" — it's "can an external auditor, reading this file cold, follow the risk management objective, the hedge relationship, and the effectiveness conclusion without needing it explained to them." That's a materially higher bar, and it's the one that actually gets tested every year-end.

The practical takeaway

The fix is procedural, not complicated: build hedge designation and documentation into the same workflow as the hedge execution itself, not as a follow-up task for the accounting team once the trade is already booked. A hedge programme and its accounting treatment should be designed together, from the first conversation about the exposure.