What is hedge documentation?

Hedge documentation is the formal, written record a company prepares at the start of a hedge relationship to qualify for hedge accounting. Under both IFRS 9 and US GAAP (ASC 815), it must set out the risk management objective and strategy for the hedge, identify the hedging instrument and the hedged item or transaction, state the nature of the risk being hedged, and describe how hedge effectiveness will be assessed. Without it, the relationship cannot use hedge accounting, however sound the hedge is economically.

What must be documented at hedge inception?

At inception you generally have to document five things: the risk management objective and strategy for undertaking the hedge; identification of the hedging instrument; identification of the hedged item or transaction; the nature of the risk being hedged; and the method you will use to assess whether the hedge is effective. The critical word is inception — the documentation has to be in place at the start of the relationship, before the fact, not written up afterwards once you know how the hedge performed.

What happens if hedge documentation is incomplete?

Incomplete or late documentation disqualifies the relationship from hedge accounting. The hedge still works economically — nothing changes about the protection — but the derivative goes back to being marked to market through profit and loss on its own timing, while the item it hedges sits on a different timing. The result is exactly the artificial P&L volatility hedge accounting exists to remove. Documentation failures are a process problem, not a hedging problem, and they are one of the most common ways companies lose hedge accounting.

Hedge Documentation for Hedge Accounting

Hedge documentation is the formal record you prepare at the start of a hedge relationship to qualify for hedge accounting — the written designation, made at inception, that says exactly what you are hedging, with what, against which risk, and how you will prove the offset. Under both IFRS 9 and US GAAP (ASC 815), this documentation is not paperwork you tidy up later. It is a condition of entry. No contemporaneous documentation, no hedge accounting — and I've watched genuinely good hedges lose the treatment on that point alone, in eighteen years of SAP FI and treasury work.

(This is a plain explanation of what hedge documentation involves, not accounting advice for a specific situation — the exact rules live in standards like IFRS 9 and ASC 815, and applying them to your book needs your accountants.)

Why it exists at all

Hedge accounting is optional and privileged. It lets you defer or relocate a derivative's gains and losses so they land in profit together with the item they hedge, instead of swinging around on their own timing. That's a valuable smoothing of reported profit — and because it's a privilege, the standards make you earn it. You earn it by formally designating and documenting the hedge before the fact, not by reconstructing a story after a good quarter.

That "before the fact" is the whole point. If you could designate hedges retrospectively, you could cherry-pick: call a position a hedge when it happened to move your way, and leave it undesignated when it didn't. Contemporaneous documentation closes that door. It fixes your intention in writing at the moment you enter the relationship, when you don't yet know how it will turn out.

What you actually have to document

The specifics vary by standard, but the substance is consistent across IFRS 9 and ASC 815. At inception you document, in essence, five things:

The risk management objective and strategy for undertaking the hedge — why you're doing it, and how it fits your broader approach to the risk.
Identification of the hedging instrument — the specific derivative or other instrument being used.
Identification of the hedged item or transaction — the recognised asset, liability, firm commitment or forecast transaction being protected.
The nature of the risk being hedged — FX, interest rate, a specific priced component, and so on.
How hedge effectiveness will be assessed — the method by which you'll show the instrument actually offsets the risk.

That last one is where the documentation hands off to a companion discipline. Naming your effectiveness method here is what you commit to in hedge effectiveness testing — designation is the promise, effectiveness testing is keeping it. Designation, documentation and effectiveness are the three legs of the same stool; pull any one and hedge accounting falls over.

The inception-timing rule

Say it plainly: the documentation must be in place at the start of the hedge relationship. Not the same week, not "we always intended to." At inception.

You cannot decide, after a good quarter, that a trade "was" a hedge all along. No contemporaneous documentation at inception, no hedge accounting — however clean the economics look in hindsight.

This is the rule people underestimate most, because it feels bureaucratic when the economics are obviously fine. But the timing requirement is the safeguard. It's what separates a designated hedge from a bet you're re-labelling with the benefit of knowing the answer.

What getting it wrong actually costs

The consequence is concrete and it's the exact thing you were trying to avoid. Incomplete or late documentation disqualifies the relationship. The hedge keeps working economically — the protection is unchanged — but the derivative reverts to being marked to market through P&L on its own timing, unmatched by the hedged item. You get the full, unhedged fair-value swing hitting reported profit: the artificial volatility hedge accounting exists to remove, delivered right back to you by a filing failure.

You did the right thing economically and got punished in the numbers, on process. That's a miserable conversation to have with a CFO, and I've had it.

Making it survive contact with reality

The fixes are unglamorous, which is why they get skipped:

A documentation template or library. Standardise the five elements so nothing gets forgotten under time pressure. A blank page at inception is how fields go missing.
Discipline to complete it before the trade settles. Tie the paperwork to the trade lifecycle, not to month-end. If the documentation isn't done, the designation isn't real.
Keeping it current. Relationships change — a rollover, a re-designation, a change in the hedged forecast. Documentation that describes last year's relationship doesn't support this year's.

Docs vs reality

Here's what I actually see. The hedge economics are almost always fine. Treasury sizes the exposure sensibly, picks a reasonable instrument, executes. Where hedge accounting gets lost is process — a trade done Friday afternoon and "documented" the following week, once someone in accounting has a moment. By then the designation isn't contemporaneous, and the treatment is gone for that relationship.

The discipline that keeps hedge accounting is contemporaneous paperwork, full stop. It's dull enough that people quietly defer it until an auditor asks to see the inception file — and that's the worst possible moment to discover the file was assembled after the fact. Build the documentation into the trade, not around the audit.

One honest caveat: not everything needs a financial hedge in the first place. Natural hedging — offsetting exposures inside the business — carries no instrument to designate and no inception file to get wrong, which sidesteps this entire problem for the exposures it can reach. Where you do use instruments, though, the documentation is the price of the accounting, and it's due at inception.

Part of the Treasury Risk Management guide. See also hedge accounting explained and what is treasury risk management. The newsletter sends one finance-systems pattern every two weeks.