ipsas 29—financial instruments: recognition and measurement - IFAC
ipsas 29—financial instruments: recognition and measurement - IFAC
ipsas 29—financial instruments: recognition and measurement - IFAC
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 />
B.31 Recognition <strong>and</strong> De<strong>recognition</strong> of Financial Liabilities Using Trade Date or<br />
Settlement Date Accounting<br />
IPSAS 29 has special rules about <strong>recognition</strong> <strong>and</strong> de<strong>recognition</strong> of financial<br />
assets using trade date or settlement date accounting. Do these rules apply to<br />
transactions in financial <strong>instruments</strong> that are classified as financial liabilities,<br />
such as transactions in deposit liabilities <strong>and</strong> trading liabilities?<br />
No. IPSAS 29 does not contain any specific requirements about trade date accounting<br />
<strong>and</strong> settlement date accounting in the case of transactions in financial <strong>instruments</strong> that<br />
are classified as financial liabilities. Therefore, the general <strong>recognition</strong> <strong>and</strong><br />
de<strong>recognition</strong> requirements in IPSAS 29.18 <strong>and</strong> IPSAS 29.41 apply. IPSAS 29.16<br />
states that financial liabilities are recognized on the date the entity “becomes a party to<br />
the contractual provisions of the instrument.” Such contracts generally are not<br />
recognized unless one of the parties has performed or the contract is a derivative<br />
contract not exempted from the scope of IPSAS 29. IPSAS 29.41 specifies that<br />
financial liabilities are derecognized only when they are extinguished, i.e., when the<br />
obligation specified in the contract is discharged or cancelled or expires.<br />
Section C: Embedded Derivatives<br />
C.1 Embedded Derivatives: Separation of Host Debt Instrument<br />
If an embedded non-option derivative is required to be separated from a host<br />
debt instrument, how are the terms of the host debt instrument <strong>and</strong> the embedded<br />
derivative identified? For example, would the host debt instrument be a fixed rate<br />
instrument, a variable rate instrument or a zero coupon instrument?<br />
The terms of the host debt instrument reflect the stated or implied substantive terms of<br />
the hybrid instrument. In the absence of implied or stated terms, the entity makes its<br />
own judgment of the terms. However, an entity may not identify a component that is<br />
not specified or may not establish terms of the host debt instrument in a manner that<br />
would result in the separation of an embedded derivative that is not already clearly<br />
present in the hybrid instrument, that is to say, it cannot create a cash flow that does not<br />
exist. For example, if a five-year debt instrument has fixed interest payments of<br />
CU40,000 annually <strong>and</strong> a principal payment at maturity of CU1,000,000 multiplied by<br />
the change in an equity price index, it would be inappropriate to identify a floating rate<br />
host contract <strong>and</strong> an embedded equity swap that has an offsetting floating rate leg in<br />
lieu of identifying a fixed rate host. In that example, the host contract is a fixed rate<br />
debt instrument that pays CU40,000 annually because there are no floating interest rate<br />
cash flows in the hybrid instrument.<br />
In addition, the terms of an embedded non-option derivative, such as a forward or swap,<br />
must be determined so as to result in the embedded derivative having a fair value of zero<br />
at the inception of the hybrid instrument. If it were permitted to separate embedded nonoption<br />
derivatives on other terms, a single hybrid instrument could be decomposed into<br />
an infinite variety of combinations of host debt <strong>instruments</strong> <strong>and</strong> embedded derivatives,<br />
for example, by separating embedded derivatives with terms that create leverage,<br />
1173<br />
IPSAS 29 IMPLEMENTATION GUIDANCE<br />
PUBLIC SECTOR