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 />

designated hedged portion of the interest rate risk could be documented as being based on<br />

the same yield curve as the derivative hedging instrument.<br />

The hedging instrument – Each derivative hedging instrument is documented as a hedge<br />

of specified amounts in specified future time periods corresponding with the forecast<br />

transactions occurring in the specified future time periods designated as being hedged.<br />

The method of assessing effectiveness – The effectiveness test is documented as being<br />

measured by comparing the changes in the cash flows of the derivatives allocated to<br />

the applicable periods in which they are designated as a hedge to the changes in the<br />

cash flows of the forecast transactions being hedged. Measurement of the cash flow<br />

changes is based on the applicable yield curves of the derivatives <strong>and</strong> hedged items.<br />

Issue (d) – If the hedging relationship is designated as a cash flow hedge, how<br />

does an entity satisfy the requirement for an expectation of high effectiveness in<br />

achieving offsetting changes in IPSAS 29.98(b)?<br />

An entity may demonstrate an expectation of high effectiveness by preparing an<br />

analysis demonstrating high historical <strong>and</strong> expected future correlation between the<br />

interest rate risk designated as being hedged <strong>and</strong> the interest rate risk of the hedging<br />

instrument. Existing documentation of the hedge ratio used in establishing the<br />

derivative contracts may also serve to demonstrate an expectation of effectiveness.<br />

Issue (e) – If the hedging relationship is designated as a cash flow hedge, how<br />

does an entity demonstrate a high probability of the forecast transactions<br />

occurring as required by IPSAS 29.98(c)?<br />

An entity may do this by preparing a cash flow maturity schedule showing that there<br />

exist sufficient aggregate gross levels of expected cash flows, including the effects of<br />

the resetting of interest rates for assets or liabilities, to establish that the forecast<br />

transactions that are designated as being hedged are highly probable to occur. Such a<br />

schedule should be supported by management’s stated intentions <strong>and</strong> past practice of<br />

reinvesting cash inflows <strong>and</strong> refinancing cash outflows.<br />

For example, an entity may forecast aggregate gross cash inflows of CU100 <strong>and</strong><br />

aggregate gross cash outflows of CU90 in a particular time period in the near future.<br />

In this case, it may wish to designate the forecast reinvestment of gross cash inflows<br />

of CU10 as the hedged item in the future time period. If more than CU10 of the<br />

forecast cash inflows are contractually specified <strong>and</strong> have low credit risk, the entity<br />

has strong evidence to support an assertion that gross cash inflows of CU10 are<br />

highly probable to occur <strong>and</strong> to support the designation of the forecast reinvestment<br />

of those cash flows as being hedged for a particular portion of the reinvestment<br />

period. A high probability of the forecast transactions occurring may also be<br />

demonstrated under other circumstances.<br />

Issue (f) – If the hedging relationship is designated as a cash flow hedge, how<br />

does an entity assess <strong>and</strong> measure effectiveness under IPSAS 29.98(d) <strong>and</strong><br />

IPSAS 29.98(e)?<br />

IPSAS 29 IMPLEMENTATION GUIDANCE 1250

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

Saved successfully!

Ooh no, something went wrong!