22.12.2012 Views

ipsas 29—financial instruments: recognition and measurement - IFAC

ipsas 29—financial instruments: recognition and measurement - IFAC

ipsas 29—financial instruments: recognition and measurement - IFAC

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

FINANCIAL INSTRUMENTS: RECOGNITION AND MEASUREMENT<br />

No. It is inconsistent with the designation of a debt investment as being held to<br />

maturity to designate a swap as a cash flow hedge of the debt investment’s variable<br />

interest rate payments. IPSAS 29.88 states that a held-to-maturity investment cannot<br />

be a hedged item with respect to interest rate risk or prepayment risk “because<br />

designation of an investment as held to maturity requires an intention to hold the<br />

investment until maturity without regard to changes in the fair value or cash flows of<br />

such an investment attributable to changes in interest rates.”<br />

F.2.10 Hedged Items: Purchase of Held-to-Maturity Investment<br />

An entity forecasts the purchase of a financial asset that it intends to classify as<br />

held to maturity when the forecast transaction occurs. It enters into a derivative<br />

contract with the intent to lock in the current interest rate <strong>and</strong> designates the<br />

derivative as a hedge of the forecast purchase of the financial asset. Can the<br />

hedging relationship qualify for cash flow hedge accounting even though the<br />

asset will be classified as a held-to-maturity investment?<br />

Yes. With respect to interest rate risk, IPSAS 29 prohibits hedge accounting for<br />

financial assets that are classified as held-to-maturity (IPSAS 29.88). However, even<br />

though the entity intends to classify the asset as held to maturity, the instrument is<br />

not classified as such until the transaction occurs.<br />

F.2.11 Cash Flow Hedges: Reinvestment of Funds Obtained from Heldto-Maturity<br />

Investments<br />

An entity owns a variable rate asset that it has classified as held to maturity. It<br />

enters into a derivative contract with the intention to lock in the current interest<br />

rate on the reinvestment of variable rate cash flows, <strong>and</strong> designates the<br />

derivative as a cash flow hedge of the forecast future interest receipts on debt<br />

<strong>instruments</strong> resulting from the reinvestment of interest receipts on the held-tomaturity<br />

asset. Assuming that the other hedge accounting criteria are met, can<br />

the hedging relationship qualify for cash flow hedge accounting even though the<br />

interest payments that are being reinvested come from an asset that is classified<br />

as held to maturity?<br />

Yes. IPSAS 29.88 states that a held-to-maturity investment cannot be a hedged item<br />

with respect to interest rate risk. Question F.2.8 specifies that this applies not only to<br />

fair value hedges, i.e., hedges of the exposure to fair value interest rate risk<br />

associated with held-to-maturity investments that pay fixed interest, but also to cash<br />

flow hedges, i.e., hedges of the exposure to cash flow interest rate risk associated<br />

with held-to-maturity investments that pay variable interest at current market rates.<br />

However, in this instance, the derivative is designated as an offset of the exposure to<br />

cash flow risk associated with forecast future interest receipts on debt <strong>instruments</strong><br />

resulting from the forecast reinvestment of variable rate cash flows on the held-tomaturity<br />

investment. The source of the funds forecast to be reinvested is not relevant<br />

in determining whether the reinvestment risk can be hedged. Accordingly,<br />

designation of the derivative as a cash flow hedge is permitted. This answer applies<br />

1217<br />

IPSAS 29 IMPLEMENTATION GUIDANCE<br />

PUBLIC SECTOR

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!