Chapter 46
Financial instruments: Derivatives and embedded derivatives

List of examples

Chapter 46
Financial instruments: Derivatives and embedded derivatives

1 INTRODUCTION

Under IFRS 9 – Financial Instruments, the question of whether an instrument is a derivative or not is an important one for accounting purposes. Derivatives are normally recorded in the statement of financial position at fair value with any changes in value reported in profit or loss (see Chapter 50 at 2), although there are some exceptions, e.g. derivatives that are designated in certain effective hedge relationships.

For many financial instruments, it will be reasonably clear whether or not they are derivatives, but there will be more marginal cases. Accordingly, the term derivative is formally defined within IFRS 9, and this definition, together with examples of derivatives, is considered further at 2 and 3 below.

IFRS 9 also contains the concept of an embedded derivative which is described as a component of a hybrid or combined instrument that also includes a non-derivative host contract. In certain circumstances embedded derivatives are required to be accounted for separately as if they were freestanding derivatives. The IASB introduced this concept because it believes that entities should not be able to circumvent the accounting requirements for derivatives merely by embedding a derivative in a non-derivative financial instrument or other non-financial contract, e.g. by placing a commodity forward in a debt instrument. In other words, it is chiefly an anti-abuse measure designed to enforce ‘derivative accounting’ on those derivatives that are ‘hidden’ in other contracts. [IFRS 9.BCZ4.92].

Embedded derivatives, and the situations in which they are required to be accounted for separately, are considered in more detail at 4 to 7 below. Under IFRS 9 the concept of embedded derivatives applies to financial liabilities and non-financial items only. Embedded derivatives are not separated from financial assets within the scope of IFRS 9 and the requirements of IFRS 9 are applied to the hybrid contract as a whole.

In addition to assessing when a financial instrument or other contract should be accounted for as if it were two contracts, we consider at 8 below situations when two financial instruments should be accounted for as if they were one, together with the question of linkage (for financial reporting purposes) of transactions more generally.

This chapter does not deal with valuation of derivative financial instruments. Chapter 14 outlines the requirements of IFRS 13 – Fair Value Measurement, a standard that defines fair value and provides principles-based guidance on how to measure fair value under IFRS. Additional guidance affecting the valuation of derivatives can be found in Chapter 53 at 3 and 6.

This chapter refers to a number of discussions by the IASB and the Interpretations Committee on topics relevant to derivatives and embedded derivatives. A number of these discussions were held in the context of IAS 39 – Financial Instruments: Recognition and Measurement, prior to the effective date of IFRS 9 on 1 January 2018. Those discussions which remain relevant to IFRS 9 have been retained in this chapter.

2 DEFINITION OF A DERIVATIVE

A derivative is a financial instrument or other contract within the scope of IFRS 9 (see Chapter 45 at 2 and 3) with all of the following characteristics:

  1. its value changes in response to the change in a specified interest rate, financial instrument price, commodity price, foreign exchange rate, index of prices or rates, credit rating or credit index, or other variable, provided in the case of a non-financial variable that the variable is not specific to a party to the contract (sometimes called the ‘underlying’);
  2. it requires no initial net investment, or an initial net investment that is smaller than would be required for other types of contracts that would be expected to have a similar response to changes in market factors; and
  3. it is settled at a future date. [IFRS 9 Appendix A].

These three defining characteristics are considered further below.

2.1 Changes in value in response to changes in underlying

2.1.1 Notional amounts

A derivative usually has a notional amount, such as an amount of currency, number of shares or units of weight or volume, but does not require the holder or writer to invest or receive the notional amount at inception.

However, while a derivative usually has a notional amount, this is not always the case: a derivative could require a fixed payment or payment of an amount that can change (but not proportionally with a change in the underlying) as a result of some future event that is unrelated to a notional amount. For example, a contract that requires a fixed payment of €1,000 if six-month LIBOR increases by 100 basis points is a derivative, even though a notional amount is not specified (at least not in the conventional sense). [IFRS 9.BA.1]. A further example is shown below.

2.1.2 Underlying variables

It follows from the definition (see 2 above) that a derivative will always have at least one underlying variable. The following underlying variables are referred to in the standard, but this is not an exhaustive list (we have provided an example for each of the underlyings):

  • specified interest rate (e.g. LIBOR);
  • financial instrument price (e.g. the share price of an entity);
  • commodity price (e.g. the price of a barrel of oil);
  • foreign exchange rate (e.g. the £/$ spot rate);
  • index of prices or rates (e.g. Consumer Price Index);
  • credit rating (e.g. Fitch);
  • credit index (e.g. AAA rated corporate bond index); and
  • non-financial variable (e.g. index of earthquake losses or of temperatures).

A contract to receive a royalty, often in exchange for the use of certain property that is not exchange-traded, where the payment is based on the volume of related sales or service revenues and accounted for under IFRS 15 – Revenue from Contracts with Customers (see Chapter 31 at 2.5) is not accounted for as a derivative.

Derivatives that are based on sales volume are not necessarily excluded from the scope of IFRS 9, especially where there is another (financial) underlying, as set out in the next example.

However, contracts that are linked to variables that might be considered non-financial, such as an entity's revenue, can sometimes cause particular interpretative problems as discussed below.

2.1.3 Non-financial variables specific to one party to the contract

The definition of a derivative (see 2 above) refers to underlyings that are non-financial variables not specific to one party to the contract. This reference was introduced by IFRS 4 – Insurance Contracts – to help determine whether or not a financial instrument is an insurance contract (see Chapter 45 at 3.3). An insurance contract is likely to contain such an underlying, for example the occurrence or non-occurrence of a fire that damages or destroys an asset of a party to the contract. For periods beginning on or after 1 January 2021, IFRS 4 will be replaced by IFRS 17 – Insurance Contracts. Non-financial variables that are not specific to one party to the contract might include an index of earthquake losses in a particular region or an index of temperatures in a particular city. [IFRS 9.BA.5]. Those based on climatic variables are sometimes referred to as ‘weather derivatives’. [IFRS 9.B2.1].

A change in the fair value of a non-financial asset is specific to the owner if the fair value reflects not only changes in market prices for such assets (a financial variable) but also the condition of the specific non-financial asset held (a non-financial variable). For example, if a guarantee of the residual value of a specific car exposes the guarantor to the risk of changes in the car's physical condition, the change in that residual value is specific to the owner of the car, and so would not be a derivative. [IFRS 9.BA.5].

Contracts with non-financial variables arise in the gaming industry where a gaming institution takes a position against a customer (rather than providing services to manage the organisation of games between two or more parties). For example, a customer will pay a stake to a bookmaker such that the bookmaker is contractually obliged to pay the customer a specified amount in the event that the bet is a winning one, e.g. if the specified horse wins a given race. The underlying variable (the outcome of the race) is clearly non-financial in nature, but it is unlikely to be specific to either party to the contract. Accordingly such contracts will typically be derivative financial instruments.2

It is not clear whether the reference to non-financial variables specific to one party to the contract means that all instruments with such an underlying would fail to meet the definition of a derivative or only those contracts that are insurance contracts, for which the reference was originally introduced. Until the standard is clarified, in our view, a legitimate case can be made for either view.

The Interpretations Committee considered this issue in the context of contracts indexed to an entity's revenue or EBITDA and initially came to a tentative conclusion that the exclusion was not restricted to insurance contracts.3 However, that conclusion was later withdrawn and the Interpretations Committee referred the issue to the IASB, recommending that the standard be amended to limit the exclusion to insurance contracts.4

The IASB confirmed that it had intended the exclusion to apply only to contracts that are within the scope of IFRS 45 however, the IASB eventually decided not to proceed on this issue and the existing definition of a derivative (see 2 above) was incorporated into IFRS 9 without alteration, leaving the issue unaddressed.

A further issue arises in that it is not always clear whether a variable is non-financial. This is illustrated in the following example (in this case the underlying is associated with an embedded feature which might or might not meet the definition of a derivative).

It is not only contracts with payments based on revenue that can cause such problems. Some contracts may require payments based on other measures taken or derived from an entity's financial statements such as EBITDA. The Interpretations Committee considered this matter in July 20066 and in January 2007 referred the matter to the IASB.7 However, the IASB eventually decided not to deal with this issue.

Whilst it is tempting to regard an entity's revenue and EBITDA as financial variables, they are driven by a number of different factors many of which are clearly non-financial in nature, for example the general business risks faced by the entity. In addition, many of the drivers of EBITDA and revenue will be specific to that business, for example the location of the business, the nature of its goods or services and managements actions.

One company that has faced this issue in practice is Groupe Renault. This company has issued liabilities on which coupons are linked to revenue and net profit. As can be seen in the following extract, Groupe Renault states that its revenue-linked and net profit-linked features are not considered embedded derivatives and the liabilities are therefore carried at amortised cost. The extract below is from Groupe Renault's 2018 accounts.

In 2009 the Interpretations Committee was asked to consider the accounting treatment for an instrument that contains participation rights by which the instrument holder shares in the net income and losses of the issuer. However, the Interpretations Committee considered the issue without reconsidering the assumptions described in the request, including one that the financial liability did not contain any embedded derivatives.8 In other words, the Interpretations Committee implicitly accepted that such a feature need not be separated but did not indicate that separation was necessarily prohibited.

In practice, we believe that an entity may make an accounting policy choice as to whether the entity's revenue, EBITDA or other measures taken or derived from the entity's financial statements, are financial or non-financial variables. Once an entity elects a particular policy, it must consistently apply that approach to all similar transactions.

2.2 Initial net investment

The second key characteristic of a derivative is that it has no initial net investment, or one that is smaller than would be required for other types of contracts that would be expected to have a similar response to changes in market factors (see 2 above). [IFRS 9 Appendix A].

An option contract meets the definition because the premium is less than the investment that would be required to obtain the underlying financial instrument to which the option is linked. [IFRS 9.BA.3].

The implementation guidance to IAS 39 suggested that the purchase of a deeply in the money call option would fail to satisfy the original ‘little net investment’ test if the premium paid was equal or close to the amount required to invest in the underlying instrument. However, the implementation guidance on which Example 46.8 below is based explains that a contract is not a derivative if the initial net investment approximates the amount that an entity otherwise would be required to invest. [IAS 39.IG B.9, IFRS 9.IG B.9].

Currency swaps sometimes require an exchange of different currencies of equal value at inception. This does not mean that they would not meet the definition a derivative, i.e. no initial net investment or an initial investment that is smaller than would be required for other types of contracts that would be expected to have a similar response to changes in market factors, as the following example demonstrates.

The following examples illustrate how to assess the initial net investment characteristic in various prepaid derivatives – these can provide guidance when assessing whether what appears to be a non-derivative instrument is actually a derivative.

The conclusions in Examples 46.6 and 46.7 above are fundamentally different for what, on the face of it, appear to be very similar transactions. The key difference is that in Example 46.7 all possible cash flow variances are eliminated and, consequently, the resulting cash flows exhibit the characteristics of a simple non-derivative instrument, i.e. an amortising loan.

Many derivative instruments, such as futures contracts and exchange traded written options, require margin payments. The implementation guidance explains that a margin payment is not part of the initial net investment in a derivative, but is a form of collateral for the counterparty or clearing-house and may take the form of cash, securities, or other specified assets, typically liquid assets. Consequently, they are separate assets that are accounted for separately. [IFRS 9.IG B.10].

However, while accounted for separately, the margin call and the derivative would be presented net in the statement of financial position if the offsetting requirements of IAS 32 – Financial Instruments: Presentation – are met (see Chapter 54 at 7.4.1). In some jurisdictions, depending on the precise terms of the related contracts, margin payments may actually represent a partial settlement of a derivative.

2.3 Future settlement

The third characteristic is that settlement takes place at a future date. Sometimes, a contract will require gross cash settlement. However, as illustrated in the next example, it makes no difference whether the future settlements are gross or net.

The definition of a derivative also includes contracts that are settled gross by delivery of the underlying item, e.g. a forward contract to purchase a fixed rate debt instrument. An entity may have a contract to buy or sell a non-financial item that can be settled net, e.g. a contract to buy or sell a commodity at a fixed price at a future date; if that contract is within the scope of IFRS 9 (see Chapter 45 at 4), then the question of whether or not it meets the definition of a derivative will be assessed in the same way as for a financial instrument that may be settled gross. [IFRS 9.BA.2].

Expiry of an option at its maturity is a form of settlement even though there is no additional exchange of consideration. Therefore, even if an option is not expected to be exercised, e.g. because it is significantly ‘out of the money’, it can still be a derivative. [IFRS 9.IG B.7]. Such an option will have some value, albeit small, because it still offers the opportunity for gain if it becomes ‘in the money’ before expiry even if such a possibility is remote – the more remote the possibility, the lower its value.

3 EXAMPLES OF DERIVATIVES

3.1 Common derivatives

The following table provides examples of contracts that normally qualify as derivatives. The list is not exhaustive – any contract that has an underlying may be a derivative. Moreover, as set out in Chapter 45 at 3, even if an instrument meets the definition of a derivative, it may not fall within the scope of IFRS 9.

Type of contract Main underlying variable
Interest rate swap Interest rates
Currency swap (foreign exchange swap) Currency rates
Commodity swap Commodity prices
Equity swap Equity prices (equity of another entity)
Credit swap Credit rating, credit index, or credit price
Total return swap Total fair value of the reference asset and interest rates
Purchased or written bond option (call or put) Interest rates
Purchased or written currency option (call or put) Currency rates
Purchased or written commodity option (call or put) Commodity prices
Purchased or written stock option (call or put) Equity prices (equity of another entity)
Interest rate futures linked to government debt (treasury futures) Interest rates
Currency futures Currency rates
Commodity futures Commodity prices
Interest rate forward linked to government debt (treasury forward) Interest rates
Currency forward Currency rates
Commodity forward Commodity prices
Equity forward Equity prices (equity of another entity) [IFRS 9.B2]

3.2 In-substance derivatives

The implementation guidance explains that the accounting should follow the substance of arrangements. In particular, non-derivative transactions should be aggregated and treated as a derivative when, in substance, the transactions result in a derivative. Indicators of this would include:

  • they are entered into at the same time and in contemplation of one another;
  • they have the same counterparty;
  • they relate to the same risk; and
  • there is no apparent economic need or substantive business purpose for structuring the transactions separately that could not also have been accomplished in a single transaction. [IFRS 9.IG B.6].

The application of this guidance is illustrated in the following example.

The analysis above would be equally applicable if the loans were in different currencies – such an arrangement could synthesise a cross-currency interest rate swap and should be accounted for as a derivative if that is its substance.

3.3 Regular way contracts

A regular way purchase or sale is a purchase or sale of a financial asset under a contract whose terms require delivery of the asset within the time frame established generally by regulation or convention in the marketplace concerned. [IFRS 9 Appendix A].

Such contracts give rise to a fixed price commitment between trade date and settlement date that meets the definition of a derivative. However, because of the short duration of the commitments, they are not accounted for as derivatives but in accordance with special accounting rules. These requirements are discussed in Chapter 49 at 2.2. [IFRS 9.BA.4].

4 EMBEDDED DERIVATIVES

An embedded derivative is a component of a hybrid or combined instrument that also includes a non-derivative host contract; it has the effect that some of the cash flows of the combined instrument vary in a similar way to a stand-alone derivative. In other words, it causes some or all of the cash flows, that otherwise would be required by the contract, to be modified according to a specified interest rate, financial instrument price, commodity price, foreign exchange rate, index of prices or rates, credit rating or credit index, or other underlying variable (provided in the case of a non-financial variable that the variable is not specific to a party to the contract). [IFRS 9.4.3.1].

Common examples of contracts that can contain embedded derivatives include non-derivative financial instruments (especially debt instruments), leases, insurance contracts as well as contracts for the supply of goods or services. In fact, they may occur in all sorts of unsuspected locations.

Under IFRS 9 the concept of embedded derivatives applies to only financial liabilities and non-financial items. Embedded derivatives are not separated from financial assets within the scope of IFRS 9 and the requirements of IFRS 9 are applied to the hybrid contract as a whole. [IFRS 9.4.3.2].

Normal sale or purchase contracts (see Chapter 45 at 4) can also contain embedded derivatives. This is an important difference from US GAAP, under which a contract for the sale or purchase of a non-financial item, that can be settled net, cannot be treated as a normal sale or purchase at all if it contains an embedded pricing feature, that is not clearly and closely related to the host contract – instead the whole contract would be accounted for as a derivative.

In the basis for conclusions to IFRS 9, the IASB asserts that, in principle, all embedded derivatives that are not measured at fair value with gains and losses recognised in profit or loss ought to be accounted for separately, but explains that, as a practical expedient, they should not be where they are regarded as ‘closely related’ to their host contracts. In those cases, it is believed less likely that the derivative was embedded to achieve a desired accounting result. [IFRS 9.BCZ4.92].

Accordingly, only where all of the following conditions are met should an embedded derivative be separated from the host contract and accounted for separately:

  1. the economic characteristics and risks of the embedded derivative are not closely related to the economic characteristics and risks of the host contract;
  2. a separate instrument with the same terms as the embedded derivative would meet the definition of a derivative; and
  3. the hybrid (combined) instrument is not measured at fair value with changes in fair value recognised in profit or loss. [IFRS 9.4.3.3].

If any of these conditions are not met, the embedded derivative should not be accounted for separately, [IFRS 9.4.3.3, IFRS 9.B4.3.8], i.e. an entity is prohibited from separating an embedded derivative that is closely related to its host contract. The process is similar, although not identical, to that applied when separating the equity element of a compound instrument by the issuer under IAS 32 (see Chapter 47 at 6). The assessment of the closely related criterion should be made when the entity first becomes a party to a contract or in other words, on initial recognition of the contract (see 7 below). [IFRS 9.B4.3.11].

The accounting treatment for a separated embedded derivative is the same as for a standalone derivative. Such an instrument (actually, in this case, a component of an instrument) will normally be recorded in the statement of financial position at fair value with all changes in value being recognised in profit or loss (see 1 above, Chapter 50 at 2), although there are some exceptions, e.g. embedded derivatives may be designated as a hedging instrument in an effective hedge relationship in the same way as standalone derivatives (see Chapter 53 at 3.2.3).

A derivative that is attached to a financial instrument but is contractually transferable independently of that instrument, or has a different counterparty from that instrument, is not an embedded derivative, but a separate financial instrument. [IFRS 9.4.3.1].

Where the embedded derivative's fair value cannot be determined reliably on the basis of its terms and conditions, it may be determined indirectly as the difference between the hybrid (combined) instrument and the host instrument, if their fair values can be determined. [IFRS 9.4.3.7]. If an entity is unable to measure an embedded derivative that is required to be separated from its host, either on acquisition or subsequently, the entire contract is designated at fair value through profit or loss. [IFRS 9.4.3.6].

5 EMBEDDED DERIVATIVES: THE MEANING OF ‘CLOSELY RELATED’

The standard does not define what is meant by ‘closely related’. Instead, it illustrates what was intended by providing a series of situations where the embedded derivative is, or is not, regarded as closely related to the host. Making this determination can prove very challenging, not least because the illustrations do not always seem to be consistent with each other. This guidance is considered in the remainder of this subsection.

5.1 Financial instrument hosts

Where a host contract has no stated or predetermined maturity and represents a residual interest in the net assets of an entity, its economic characteristics and risks are those of an equity instrument. From the issuer's perspective a hybrid instrument which meets the conditions for classification as equity under IAS 32 (see Chapter 47) is excluded from the scope of IFRS 9.

More commonly, if the host is not an equity instrument and meets the definition of a financial instrument, then its economic characteristics and risks are those of a debt instrument. [IFRS 9.B4.3.2]. From the issuer's perspective the application of these principles to debt hosts is considered at 5.1.1 to 5.1.8 below and to instruments that may be debt or equity hosts are considered at 5.1.9 below.

The application of these principles are not relevant to the holder of debt or equity instruments as embedded derivatives are not separated from financial assets within the scope of IFRS 9 and the requirements of IFRS 9 are applied to the hybrid contract as a whole. [IFRS 9.4.3.2].

5.1.1 Foreign currency monetary items

A monetary item denominated in a currency other than an entity's functional currency is accounted for under IAS 21 – The Effects of Changes in Foreign Exchange Rates – with foreign currency gains and losses recognised in profit or loss. The embedded foreign currency derivative is considered closely related to the debt host and is not separated. In other words it would not be considered a functional currency monetary item and a foreign currency forward contract. This also applies where the embedded derivative in a host debt instrument provides a stream of either principal or interest payments denominated in a foreign currency (e.g. a dual currency bond). [IFRS 9.B4.3.8(c)].

5.1.2 Interest rate indices

Many debt instruments contain embedded interest rate indices that can change the amount of interest that would otherwise be paid or received. One of the simplest examples would be a floating rate loan whereby interest is paid quarterly based on three month LIBOR. More complex examples might include the following:

  • inverse floater – coupons are paid at a fixed rate minus LIBOR;
  • levered inverse floater – as above but a multiplier greater than 1.0 is applied to the resulting coupon;
  • delevered floater – coupons lag overall movements in a specified rate, e.g. coupons equal a proportion of the ten year constant maturity treasuries rate plus a fixed premium; or
  • range floater – interest is paid at a fixed rate but only for each day in a given period that LIBOR is within a stated range.

In such cases the embedded derivative is closely related to the host debt instrument unless:

  1. the combined instrument can be settled in such a way that the holder would not recover substantially all of its recognised investment; or
  2. the embedded derivative could at least double the holder's initial rate of return on the host contract and could result in a rate of return that is at least twice what the market return would be for a contract with the same terms as the host contract (often referred to as the ‘double-double test’). [IFRS 9.B4.3.8(a)].

If a holder is permitted, but not required, to settle the combined instrument in a manner such that it does not recover substantially all of its recognised investment, e.g. puttable debt, condition (a) is not satisfied and the embedded derivative is not separated. [IFRS 9.IG C.10]. The standard does not define ‘substantially all’ and therefore judgement will need to be applied, considering all relevant facts and circumstances.

To meet condition (b), the embedded derivative must be able to double the initial return and result in a rate of return that is at least twice what would be expected for a similar contract at the time it takes effect. If it meets only one part of this condition, but not the other, the derivative is regarded as closely related to the host. Due to the requirement ‘could result in a rate of return that is at least twice what the market return would be for a contract with the same terms as the host contract’, the derivative embedded in a simple variable rate loan would be considered closely related to the host because the variable rate at any specific time would be a market rate.

As with all embedded derivatives, the assessment of condition (a) and (b) above is made when the entity becomes party to the contract on the basis of market conditions existing at that time (see 4 above). It is important to note that the assessment is based on the possibility of the holder not recovering its recognised investment or doubling its initial return and obtaining twice the then-market return. The likelihood of this happening is ignored in making the assessment. Therefore, even if the likelihood of this happening is low, the embedded derivative has to be separated from the host contract. The valuation of the embedded derivative would however consider the low probability of this happening, possibly resulting in a relatively low fair value at inception.

An example where the holder would not recover substantially all of its recognised investment would be a bond which becomes immediately repayable if LIBOR increases above a certain threshold, at an amount significantly lower than its issue price. A further example is set out below.

An example of condition (b) above, the ‘double-double test’, is set out below.

5.1.3 Term extension and similar call, put and prepayment options in debt instruments

The application guidance explains that a call, put or prepayment option embedded in a host debt instrument is closely related to the host instrument if, on each exercise date, either i) the option's exercise price is approximately equal to the debt instrument's amortised cost or ii) the exercise price reimburses the lender for an amount up to the approximate present value of lost interest for the remaining term of the host contract; otherwise it is not regarded as closely related. [IFRS 9.B4.3.5(e)]. For embedded derivatives with more than one exercise date, there is no requirement to apply only assessment i) or ii) above to all dates, i.e. provided that either of the assessments is met for each exercise date, the embedded option will be considered to be closely related.

There is no elaboration on what is meant by the term ‘approximately equal’ and so judgement will need to be applied. In assessing whether the exercise price is approximately equal to the amortised cost at each exercise date, should one consider the amortised cost of the hybrid that would reflect the entity's original expectations regarding the future exercise of the prepayment option, or potential revised estimates applying the catch up method to the amortised cost? This question is illustrated in the following simple example (which also provides further illustrations of the application of the effective interest method to instruments containing prepayment options).

Unfortunately, the standard is silent on this issue and preparers of accounts will be required to exercise judgement as to the most appropriate method to use in their individual circumstances.

The standard also says that an option or automatic provision to extend the remaining term to maturity of a debt instrument is not closely related to the host unless, at the time of the extension, there is a concurrent adjustment to the approximate current market rate of interest. [IFRS 9.B4.3.5(b)]. The current market rate of interest would take into consideration the credit risk of the issuer. Taken in isolation, this paragraph and the first paragraph in this section on call, put or prepayment options appear reasonably straightforward to apply. However, in some situations, they are contradictory as set out in the following example.

As set out at 6.2 below, an embedded option-based derivative should be separated from its host contract on the basis of the stated terms of the option feature. However, in situations similar to the one described above, there is significant diversity in practice and we are aware of at least two ways in which entities have dealt with this contradiction in practice. Some entities have looked to the wording in the contract so that what is described as an extension option (or a prepayment option) is evaluated in accordance with the guidance for extension options (or prepayment options). Other entities have determined the most likely outcome of the hybrid instrument based on conditions at initial recognition and the alternative outcome is regarded as the ‘option’. Under this latter approach, if Company Z in the example above considered it was likely to repay its loans from Bank A and Bank B after three years, both loans would be regarded as having a two-year extension option. The first approach is based on the contractual terms, while the second approach is substance-based.

Another complication is that, viewed as a separate instrument, a term extension option is effectively a loan commitment. As loan commitments are generally outside the scope of IFRS 9, with the exception of derecognition and impairment provisions, (see Chapter 45 at 3), some would argue they do not meet the definition of a derivative (see 2 above). Accordingly, when embedded in a host debt instrument, a loan commitment would not be separated as an embedded derivative or, alternatively, would be separated and accounted for as a loan commitment.9

The Interpretations Committee discussed both of the above contradictions in March 2012, noting significant diversity in practice and recommended that the IASB consider this issue when it redeliberated the classification and measurement requirements of financial liabilities under IFRS 9. The Committee decided that if the Board did not address this issue as part of its redeliberations, then the Committee would revisit this issue and consider whether guidance should be provided to clarify the accounting for the issuer of a fixed-rate-debt instrument that includes a term-extending option.10 This issue remains unaddressed in IFRS 9 with no indication from the Interpretations Committee about bringing it back onto its agenda. Preparers of financial statements are therefore left to apply their own judgement considering all the facts and circumstances.

For put, call and prepayment options, there is a further complication that the determination as to whether or not the option is closely related depends on the amortised cost of the instrument. It is not clear whether this reference is to the amortised cost of the host instrument, on the assumption that the option is separated, or to the amortised cost of the entire instrument on the assumption that the option is not separated. As can be seen in Chapter 50 at 3.4, the existence of such options can affect the amortised cost, especially for a portfolio of instruments. Although one trade body has published guidance explaining that where early repayment fees are included in the calculation of effective interest, the prepayment option is likely to be closely related to the loan,11 entities are largely left to apply their own judgement to assess which appears the most appropriate in the specific circumstances.

Prepayment options are also considered closely related to the host debt instrument if the exercise price reimburses the lender for an amount up to the approximate present value of lost interest for the remaining term of the host contract. For these purposes, lost interest is the product of the principal amount prepaid multiplied by the interest rate differential, i.e. the excess of the effective interest rate of the host contract over the effective interest rate that the entity would receive at the prepayment date if it reinvested the principal amount prepaid in a similar contract for the remaining term of the host contract. [IFRS 9.B4.3.5(e)(ii)]. In other words, in order for the prepayment option to be considered closely related to the host, the exercise price of the prepayment option would need to compensate the lender for loss of interest by reducing the economic loss from that which would be incurred on reinvestment. [IFRS 9.BCZ4.97]. In making this assessment, the question may arise what interest rate should be used to discount the interest payments that would be lost if the prepayment option was exercised. If the discount rate used reflects an equivalent credit risk of the issuer, this would seem reasonable. However, the guidance does not prescribe the discount rate to be used and since the assessment is whether the lender would be reimbursed for an amount that is ‘approximately equal’ to the present value of lost interest, there is scope to exercise judgment in determining the appropriate discount rate.

Another question that may arise, is whether the lost interest test requires the lender to be reimbursed for lost interest over the full remaining contractual term at the date of exercise. The assessment states that the interest may be ‘an amount up to’ the present value of the remaining interest. This suggests that the amount may be less than the remaining contractual interest over the full remaining contractual term. Where this is the case, the prepayment option would be deemed to be closely related.

From the perspective of the issuer of a convertible debt instrument with an embedded call or put option, the assessment of whether the option is closely related to the host debt instrument is made before separating the equity element in accordance with IAS 32. [IFRS 9.B4.3.5(e)]. This provides a specific relaxation from the general guidance on prepayment options above because, for accounting purposes, separate accounting for the equity component results in a discount on recognition of the liability component (see Chapter 47 at 6.2), which means that the amortised cost and exercise price are unlikely to approximate to each other for much of the term of the instrument.

An embedded prepayment option in an interest-only or principal-only strip is regarded as closely related to the host contract provided the host contract (i) initially resulted from separating the right to receive contractual cash flows of a financial instrument that, in and of itself, did not contain an embedded derivative, and (ii) does not contain any terms not present in the original host debt contract. [IFRS 9.B4.3.8(e)]. Again this is a specific relaxation from the general guidance on prepayment options above.

If an entity issues a debt instrument and the holder writes a call option on the debt instrument to a third party, the issuer regards the call option as extending the term to maturity of the debt instrument, provided the issuer can be required to participate in or facilitate the remarketing of the debt instrument as a result of the call option being exercised. [IFRS 9.B4.3.5(b)]. Such a component is presumably considered to represent part of a hybrid financial instrument contract rather than a separate instrument in its own right (see 4 above).

5.1.4 Interest rate floors and caps

An embedded floor or cap on the interest rate on a debt instrument is closely related to the host debt instrument, provided the cap is at or above the market rate of interest, and the floor is at or below the market rate of interest, when the instrument is issued (in other words it needs to be at- or out-of-the-money), and the cap or floor is not leveraged in relation to the host instrument. [IFRS 9.B4.3.8(b)].

The standard does not clarify what is meant by ‘market rate of interest’, or whether the cap (floor) should be considered as a single derivative or a series of caplets (floorlets) to be evaluated separately. Where the cap (floor) is at a constant amount throughout the term of the debt, historically entities have often compared the cap (floor) rate with the current spot floating rate at inception of the contract to determine whether the embedded derivative is closely related. However, in the current extremely low, or negative, interest rate environment of many economies, floors are more commonly being set at higher rates than current spot rates. As a result, entities are starting to evaluate whether more sophisticated approaches to evaluate these features are more appropriate, e.g. by comparing the average forward rate over the life of the bond with the floor rate or by comparing the forward rate at each interest reset date with each floorlet rate. We do not believe it is necessary for both a cap and a floor to be present to be considered closely related. For example, a cap (or floor) on the coupon paid on a debt instrument without a corresponding floor (or cap) could be regarded as closely related to the host, provided it was above (or below) the market rate of interest on origination.

The Interpretations Committee was asked, in January 2016, to clarify the application of the embedded derivatives requirements in a negative interest rate environment. The Interpretations Committee observed that:

  • paragraph B4.3.8(b) of IFRS 9 does not distinguish between positive and negative interest rate environments. As such an interest rate floor in a negative interest rate environment should be treated in the same way as in a positive interest rate environment;
  • when applying paragraph B4.3.8(b) of IFRS 9 in a positive or negative interest rate environment, an entity should compare the overall interest rate floor (i.e. benchmark interest rate referenced in the contract plus contractual spreads and if applicable any premiums, discounts or other elements that would be relevant to the calculation of the effective interest rate) for the hybrid contract to the market rate of interest for a similar contract without the interest rate floor (i.e. the host contract); and
  • the appropriate market rate of interest for the host contract should be determined by considering the specific forms of the host contract and the relevant spreads (including credit spreads) appropriate for the transaction. They also noted that the term market rate of interest is linked to the concept of fair value as defined in IFRS 13 and is described in IFRS 9 as the rate of interest ‘for a similar instrument (similar as to currency, term, type of interest and other factors) with a similar credit rating’. [IFRS 9.B5.1.1].

The Interpretations Committee determined that neither an Interpretation nor an amendment to a Standard was necessary and did not add this issue to its agenda.12

In practice entities perform the assessment of whether a cap or floor is ‘at or below market interest’ by either considering the cap or floor as a single instrument and applying the current swap rate, or by considering the component caplets and floorlets making up the overall cap or floor using the forward rate for the payment date of each particular caplet or floorlet.

Where, in making the assessment on the cap or floor as a single instrument, an entity determines that the cap or floor is not closely related, then the whole embedded cap or floor is accounted for as a single non-closely related embedded derivative at fair value through profit or loss.

5.1.5 Inflation-linked debt instruments

It is quite common for some entities (and governments) to issue inflation-linked debt instruments, i.e. where interest and/or principal payments are linked to, say, a consumer price index. The only embedded derivative guidance in IFRS 9 relating to embedded inflation-linked features is provided in the context of leases (see 5.3.2 below). If that guidance is accepted as applying to finance leases, it should also apply to debt instruments because finance leases result in assets and liabilities that are, in substance, no different to debt instruments (see Chapter 45 at 2.2.4). Further, in much finance theory, either real (applied to current prices) or nominal (applied to inflation adjusted prices) interest rates are used, suggesting a strong link between inflation and interest rates. Finally, a government or central bank will generally raise short-term interest rates as inflation rises and reduce rates as inflation recedes, which also suggests a close relationship between the two.

Therefore, we believe it would often be appropriate to treat the embedded derivative in inflation-linked debt as similar to an interest rate index and refer to the guidance at 5.1.2 above to determine whether the index is regarded as closely related to the debt. Typically, the index will be closely related to the debt where it is based on inflation in an economic environment in which the bond is issued/denominated, it is not significantly leveraged in relation to the debt and there is a sufficiently low risk of the investor not recovering its initial investment (only sometimes do such instruments provide an absolute guarantee that the principal will not be lost, although this situation will normally only arise if, over the life of the instrument, cumulative inflation is negative). However, some may argue that even if there is a very small risk of the initial investment not being recovered, the embedded derivative should be separated.

The staff of the Interpretations Committee has expressed a view that it would be appropriate to treat the embedded derivative in inflation-linked debt as closely related in economic environments where interest rates are mainly set so as to meet inflation targets, as evidenced by strong long-run correlation between nominal interest rates and inflation. In such jurisdictions they considered the characteristics and risks of the inflation embedded derivative to be closely related to the host debt contract.13 Further, in debating the application of the effective interest method to such instruments (see Chapter 50 at 3.6) they have implicitly acknowledged that these instruments do not necessarily contain embedded derivatives requiring separation.

5.1.6 Commodity- and equity-linked interest and principal payments

Equity-indexed or commodity-indexed interest or principal payments embedded in a host debt instrument, i.e. where the amount of interest or principal is indexed to the value of an equity instrument or commodity (e.g. gold), are not closely related to the host debt instrument because the risks inherent in the embedded derivative are dissimilar to those of the host. [IFRS 9.B4.3.5(c)-(d)]. This is illustrated in the following example.

A common type of transaction is where refiners of commodities enter into purchase contracts for mineral ores, whereby the price is adjusted subsequent to delivery, based on the quoted market price of the refined commodity extracted from the ore. These arrangements, often called provisionally-priced contracts, can provide the refiner with a hedge of the fair value of its inventories and/or related sales proceeds which vary depending on subsequent changes in quoted commodity prices. Like the debt instruments noted above, any payable (or receivable) recognised at the time of delivery will contain an embedded commodity derivative. In these circumstances, provided the payable is held at fair value through profit or loss, it is unlikely to make much difference to the amount recognised whether the embedded derivative is separated or not. Since the receivable is an asset within the scope of IFRS 9 the embedded derivative could not be separated.

However, it would not normally be regarded as necessary to account separately for such an embedded derivative prior to delivery of the non-financial item. This is because, until delivery occurs, the contract is considered executory and the pricing feature would be considered closely related to the commodity being delivered (see 5.2.2 below).

5.1.7 Credit-linked notes

Credit derivatives are sometimes embedded in a host debt instrument whereby one party (the ‘beneficiary’) transfers the credit risk of a particular reference asset, which it may not own, to another party (the ‘guarantor’). Such credit derivatives allow the guarantor to assume the credit risk associated with the reference asset without directly owning it. [IFRS 9.B4.3.5(f)].

Whilst the economic characteristics of a debt instrument will include credit risk, should the embedded derivative be a credit derivative linked to the credit standing of an entity other than the issuer, it would not normally be regarded as closely related to the host debt instrument if the issuer were not required, through the terms of the financial instrument, to own the reference asset.

For example, an entity (commonly a structured entity) may issue various tranches of debt instruments that are referenced to a group of assets, such as a portfolio of bonds, mortgages or trade receivables, and the credit exposure from those assets is allocated to the debt instruments using a so called ‘waterfall’ feature. The waterfall feature itself does not normally result in the separation of an embedded credit derivative; it is the location or ownership of the reference assets that is most important to the assessment.14 If the structured entity is required to hold the reference assets, the credit risk embedded in the debt instruments is considered closely related. However, if the issuer of the debt instruments held a credit derivative over the reference assets rather than the assets themselves, the embedded credit derivative would not be regarded as closely related.

5.1.8 Instruments with an equity kicker

In some instances, venture capital entities provide subordinated loans on terms that entitle them to receive shares if and when the borrowing entity lists its shares on a stock exchange, as illustrated in the following example.

Similarly, the derivative embedded in a bond that is convertible (or exchangeable) into equity shares of a third party will not be closely related to the host debt instrument.

5.1.9 Puttable instruments

Another example of a hybrid contract is a financial instrument that gives the holder a right to put it back to the issuer in exchange for an amount that varies on the basis of the change in an equity or commodity price or index (a ‘puttable instrument’). Where the host is a debt instrument, the embedded derivative, the indexed principal payment, cannot be regarded as closely related to that debt instrument. Because the principal payment can increase and decrease, the embedded derivative is a non-option derivative whose value is indexed to the underlying variable (see 6.1 below). [IFRS 9.B4.3.5(a), B4.3.6].

From the perspective of the issuer of a puttable instrument, that can be put back at any time for cash equal to a proportionate share of the net asset value of an entity (such as units of an open-ended mutual fund or some unit-linked investment products), the effect of the issuer separating an embedded derivative and accounting for each component is to measure the combined instrument at the redemption amount, that would be payable at the end of the reporting period, if the holder were to exercise its right to put the instrument back to the issuer. [IFRS 9.B4.3.7].

For the holder of such an instrument, the requirements of the standard are applied to the instrument as a whole, resulting in such investments in puttable instruments being recognised at fair value through profit or loss in their entirety. [IFRS 9.4.3.2].

This treatment was clarified by the Interpretations Committee in May 2017 when the Committee confirmed that the election to present subsequent changes in fair value in other comprehensive income was not available to these instruments, as they did not meet the definition of an equity instrument.15

Whilst it was not explicitly stated, the ineligibility of such instruments to make this election means they must be recognised at fair value through profit or loss.

5.2 Contracts for the sale of goods or services

5.2.1 Foreign currency derivatives

An embedded foreign currency derivative in a contract that is not a financial instrument is closely related to the host contract provided it is not leveraged, does not contain an option feature and requires payments denominated in one of the following currencies:

  1. the functional currency of any substantial party to the contract – see 5.2.1.A below;
  2. the currency in which the price of the related good or service that is acquired or delivered is routinely denominated in commercial transactions around the world (such as the US dollar for crude oil transactions) – see 5.2.1.B below; or
  3. a currency that is commonly used in contracts to purchase or sell non-financial items in the economic environment in which the transaction takes place (e.g. a relatively stable and liquid currency that is commonly used in local business transactions or external trade) – see 5.2.1.C below.

Therefore, in such cases the embedded foreign currency derivative is not accounted for separately from the host contract. [IFRS 9.B4.3.8(d)]. An example would be a contract for the purchase or sale of a non-financial item, where the price is denominated in a foreign currency that meets one of the three criteria outlined above.

5.2.1.A Functional currency of counterparty

In principle, the assessment of exception (i) above is straightforward. In practice, however, the functional currency of the counterparty to a contract will not always be known with certainty and, in some cases, can be a somewhat subjective assessment even for the counterparty's management (assuming the counterparty is a corporate entity) – see Chapter 15 at 4. Consequently, entities will need to demonstrate they have taken appropriate steps to make a reasonable judgement as to their counterparties' functional currencies. Where available, a counterparty's financial statements will provide evidence of its functional currency. Otherwise, it would often be appropriate to assume that an entity operating in a single country has that country's currency as its functional currency, although if there were indicators to the contrary these would have to be taken into account.

Another practical problem that arises in applying this exception is identifying which parties to a contract are ‘substantial’. IFRS 9 does not provide any further guidance, but it is generally considered that such a party should be one that is acting as principal to the contract. Therefore if, as part of a contract, a parent provides a performance guarantee in respect of services to be provided by its operating subsidiary, the parent may be seen to be the substantial party to the contract and not the subsidiary, where the subsidiary is acting as an agent. However, if the guarantee is not expected to be called upon, the parent would not normally be considered a substantial party to the contract. Particular care is necessary when assessing a contract under which one party subcontracts an element of the work to another entity under common control, say a fellow subsidiary with a different functional currency, although in most cases it will only be the primary contractor that is considered a substantial party.

5.2.1.B Routinely denominated in commercial transactions

For the purposes of exception (ii) above, the currency must be used for similar transactions all around the world, not just in one local area. For example, if cross-border transactions in natural gas in North America are routinely denominated in US dollars and such transactions are routinely denominated in euros in Europe, neither the US dollar nor the euro is a currency in which the good or service is routinely denominated in international commerce. [IFRS 9.IG C.9]. Accordingly, the number of items to which this will apply will be limited – in practice it will be mainly commodities that are traded in, say, US dollars throughout much of the world. Examples include crude oil, jet fuel, certain base metals (including aluminium, copper and nickel) and some precious metals (including gold, silver and platinum). One other notable item might be wide-bodied aircraft where it appears that Boeing and Airbus, the two major manufacturers, routinely denominate sales in US dollars.

In September 2014 the Interpretations Committee received a request relating to the routinely denominated criterion. They were asked to consider whether a licensing agreement denominated in a currency, in which commercial transactions of that type were routinely denominated around the world, held an embedded foreign currency derivative that was closely related to the economic characteristics of the host contract.16

The Interpretations Committee noted that the issue related to a contract for a specific type of item and observed that an assessment of routinely denominated criterion is based on evidence of whether or not such commercial transactions are denominated in that currency all around the world and not merely in one local area. They further observed that the assessment of the routinely denominated criterion is a question of fact and is based on an assessment of available evidence.

5.2.1.C Commonly used currencies

The IASB noted that the requirement to separate embedded foreign currency derivatives may be burdensome for entities that operate in economies in which business contracts denominated in a foreign currency are common. For example, entities domiciled in small countries may find it convenient to denominate business contracts with entities from other small countries in an internationally liquid currency (such as the US dollar, euro or yen) rather than the local currency of any party to the transaction. Also, an entity operating in a hyperinflationary economy may use a price list in a hard currency to protect against inflation, for example an entity that has a foreign operation in a hyperinflationary economy that denominates local contracts in the functional currency of the parent. [IFRS 9.BCZ4.94].

Unfortunately, however, the assessment of whether or not a particular currency meets this requirement in a particular situation has not been straightforward in practice and this question reached the attention of the Interpretations Committee in May 2007.

The Interpretations Committee debated this matter in four consecutive meetings before referring the matter to the IASB. During its debates, the Interpretations Committee noted that entities should:17

  • Identify where the transaction takes place.

    This is not as straightforward as it might seem. For example, consider a Polish company that manufactures components in Poland and exports them to a third party in the Czech Republic. Should the sale of components be regarded as a transaction occurring in Poland or in the Czech Republic?18 It is likely that the Polish company would regard it as occurring in Poland and the Czech entity in the Czech Republic, but this is not entirely beyond debate; and

  • Identify currencies that are commonly used in the economic environment in which the transaction takes place.

    Entities need to address what the population of transactions in the economic environment is. Some might suggest that transactions to which (i) or (ii) above apply should be excluded, although this is not a view shared by the staff of the Interpretations Committee which considered that all transactions should be included.19

    Entities should also consider what an economic environment is. The guidance, on which Example 46.17 below is based, implies that a country could be an economic environment. The references to local business transactions and to external trade in (iii) above suggest that other examples of economic environment are the external trade or internal trade environment of the country in which the transaction takes place. The question remains as to whether there could be other economic environments, for example the luxury goods market in a country. Depending on the view taken, a different treatment could arise.20 In considering the issue subsequently, the IASB staff noted their understanding that all of these views (and possibly more, such as the internal or external trade of a specific company) were being applied in practice.21

The Interpretations Committee had also been asked to provide guidance on how to interpret the term ‘common’, but understandably was reluctant to do so.22 The IASB staff noted that there is no guidance as to the quantum of transactions or value that would need to be denominated in a foreign currency to conclude that the currency was commonly used and that a related matter is whether ‘common’ should be considered in the context of a particular entity, of an industry, or of a country.23

The IASB staff noted other related interpretive questions raised by constituents including the following:24

  • What evidence does an entity require to support the notion that the use of a currency is common?
  • Does the reporting entity need to investigate published statistics?
  • If the reporting entity has to look for statistics, what percentage of business needs to be conducted in that currency to assert that use of the currency is common?
  • Whether the consideration that a currency is commonly used should exclude from the population set those transactions falling under (i) or (ii) above.

They concluded that there are a variety of views on the appropriate interpretation of this guidance and, consequently, that there is significant diversity in practice.25

Ultimately, however, no additional guidance has been included within IFRS 9.

5.2.1.D Examples and other practical issues

The application of the guidance above is illustrated in the examples below.

The implementation guidance on which this example is based does not state in which currency the host contract should be denominated (this will also be the currency of the second leg of the embedded forward contract). The currency should be chosen so that the host does not contain an embedded derivative requiring separation. In theory, therefore, it could be Norwegian krone or euro (the functional currencies of the parties to the contract) or US dollars (the currency in which oil contracts are routinely denominated in international commerce). Typically, however, an entity will use its own functional currency to define the terms of the host contract and embedded derivative.

A second issue arises where the terms of the contract require delivery and payment on different dates. For example, assume the contract was entered into on 1 January, with delivery scheduled for 30 June and payment required by 30 September. Should the embedded derivative be considered a six-month forward contract maturing on 30 June, or a nine-month forward contract maturing on 30 September? Conceptually at least, the latter approach seems more satisfactory, for example because it does not introduce into the notional terms cash flows at a point in time (i.e. on delivery) when none exist in the combined contract. In practice, however, the former approach is used far more often and is not without technical merit. For example, it avoids the recognition of an embedded foreign currency derivative between the delivery and payment dates on what would be a foreign currency denominated monetary item, something that is prohibited by IFRS 9 (see 5.1.1 above).

In practice, all but the simplest contracts will contain other terms and features that can often make it much more difficult to isolate the precise terms of the embedded foreign currency derivative (and the host). For example, a clause may allow a purchaser to terminate the contract in return for making a specified compensation payment to the supplier – the standard offers little guidance as to whether such a feature should be included within the terms of the host, of the embedded foreign currency derivative or, possibly, of both. Other problematic terms can include options to defer the specified delivery date and options to order additional goods or services.

5.2.2 Inputs, ingredients, substitutes and other proxy pricing mechanisms

It is common for the pricing of contracts for the supply of goods, services or other non-financial items to be determined by reference to the price of inputs to, ingredients used to generate, or substitutes for the non-financial item, especially where the non-financial item is not itself quoted in an active market. For example, a provider of call centre services may determine that a large proportion of the costs of providing the service will be employee costs in a particular country. Accordingly, it may seek to link the price in a long-term contract to supply its services to the relevant wage index, effectively to provide an economic hedge of its exposure to changes in employee costs. Similarly, the producer of goods may index the price of its product to the market value of commodities that are used in the production process.

The standard contains little or no detailed guidance for determining whether or not such pricing features should be considered closely related to the host contract. However, the general requirement of the standard to assess the economic characteristics and risks would suggest that where a good link to the inputs can be established, such features will normally be considered closely related to the host, unless they were significantly leveraged.

Other proxy pricing mechanisms may arise in long-term supply agreements for commodities where there is no active market in the commodity. For example, in the 1980s, when natural gas first started to be extracted from the North Sea in significant volumes, there was no active market for that gas and thus no market price on which to base the price of long-term contracts. Because of this, suppliers and customers were willing to enter into such contracts where the price was indexed to the market price of other commodities such as crude oil that could potentially be used as a substitute for gas. For contracts entered into before the development of an active gas market, such features would normally be considered closely related, especially if similar pricing mechanisms were commonly used by other participants in the market.

Where there is an active market price for the non-financial items being supplied under the contract, different considerations apply. The use of the proxy pricing mechanism is a strong indication that the entity has entered into a speculative position and we would not normally consider such features to be closely related to the host. The separation of these types of embedded derivatives can be seen in the following extract from BP's financial statements. Although this was disclosed under IAS 39 there is no reason to believe that the outcome would be different under IFRS 9.

5.2.3 Inflation-linked features

Apart from that related to leases (see 5.3.2 below), there is no reference in the guidance to contracts containing payments that are linked to inflation. Many types of contracts contain inflation-linked payments and it would appear sensible to apply the guidance in respect of leases to these contracts. Consider, for example, a long-term agreement to supply services under which payments increase by reference to a general price index and are not leveraged in any way. In cases such as this, the embedded inflation-linked derivative would normally be considered closely related to the host, provided the index related to a measure of inflation in an appropriate economic environment, such as the one in which the services were being supplied.

5.2.4 Floors and caps

Similar to debt instruments (see 5.1.4 above), provisions within a contract to purchase or sell an asset (e.g. a commodity) that establishes a cap and a floor on the price to be paid or received for the asset are closely related to the host contract if both the cap and floor were out-of-the-money at inception and are not leveraged. [IFRS 9.B4.3.8(b)].

5.2.5 Fund performance fees

In the investment management industry, it is common for a fund manager to receive a fee based on the performance of the assets managed in addition to a base fee. For example, if a fund's net asset value increases over its accounting year, the manager may be entitled to a percentage of that increase. The contract for providing investment management services to the fund clearly contains an embedded derivative (the underlying is the value of the fund's assets). However, whilst not addressed explicitly in the standard, we would normally consider it appropriate to regard such features as closely related to the host contract. Performance-based fees are discussed in more detail in Chapter 29 at 2.2.3 and Example 29.5.

5.3 Leases

5.3.1 Foreign currency derivatives

A lessor's finance lease receivable or a lessee's lease payable, which is recognised in accordance with IFRS 16 – Leases, is accounted for as a financial instrument, albeit one that is not subject to all of the measurement requirements of IFRS 9 (see Chapter 45 at 2.2.4). Therefore, a lease denominated in a foreign currency will not generally be considered to contain an embedded foreign currency derivative requiring separation, because the payable or receivable is a monetary item within the scope of IAS 21.

However, under IFRS 16, an operating lease for a lessor and a short-term lease for a lessee, is accounted for as an executory contract. Accordingly, where the lease payments are denominated in a foreign currency, the analysis at 5.2.1 above is applicable and it may be necessary to separate an embedded derivative. See Example 46.19 at 6.1 below for an example of a foreign exchange currency derivative requiring separation from a (hybrid) lease contract.

5.3.2 Inflation-linked features

An embedded derivative in a lease is considered closely related to the host if it is an inflation-related index such as an index of lease payments to a consumer price index, provided that the lease is not leveraged and the index relates to inflation in the entity's own economic environment. [IFRS 9.B4.3.8(f)(i)].

5.3.3 Contingent rentals based on related sales

Where a lease requires contingent rentals based on related sales, that embedded derivative is considered to be closely related to the host lease. [IFRS 9.B4.3.8(f)(ii)].

5.3.4 Contingent rentals based on variable interest rates

If a derivative embedded within a lease arises from contingent rentals based on variable interest rates, it is considered closely related. [IFRS 9.B4.3.8(f)(iii)].

5.4 Insurance contracts

The guidance at 5.1.2 to 5.1.4, 5.1.6 and 5.2.1 above also applies to insurance contracts. IFRS 4 added two further illustrations to IFRS 9 that deal primarily with insurance contracts.

A unit-linking feature embedded in a host financial instrument, or host insurance contract, is closely related to the host if the unit-denominated payments are measured at current unit values that reflect the fair values of the assets of the fund. A unit-linking feature is a contractual term that requires payments denominated in units of an internal or external investment fund. [IFRS 9.B4.3.8(g)].

A derivative embedded in an insurance contract is closely related to the host if the embedded derivative and host are so interdependent that the embedded derivative cannot be measured separately, i.e. without considering the host contract. [IFRS 9.B4.3.8(h)].

Derivatives embedded within insurance contracts are covered in more detail in Chapter 55 at 4 for IFRS 4 and Chapter 56 at 4.1 for IFRS 17.

6 IDENTIFYING THE TERMS OF EMBEDDED DERIVATIVES AND HOST CONTRACTS

The IASB has provided only limited guidance on determining the terms of a separated embedded derivative and host contract. Accordingly, entities may find this aspect of the embedded derivative requirements particularly difficult to implement. In addition to the guidance set out below, Examples 46.17 and 46.18 above also identify the terms of an embedded derivative requiring separation.

6.1 Embedded non-option derivatives

IFRS 9 does not define the term ‘non-option derivative’ but suggests that it includes forwards, swaps and similar contracts. An embedded derivative of this type should be separated from its host contract on the basis of its stated or implied substantive terms, so as to result in it having a fair value of zero at initial recognition. [IFRS 9.B4.3.3].

The IASB has provided implementation guidance on separating non-option derivatives in the situation where the host is a debt instrument. It is explained that, in the absence of implied or stated terms, judgement will be necessary to identify the terms of the host (e.g. whether it should be a fixed rate, variable rate or zero coupon instrument) and the embedded derivative. However, an embedded derivative that is not already clearly present in the hybrid should not be separated, i.e. a cash flow that does not exist cannot be created. [IFRS 9.IG C.1].

For example, if a five year debt instrument has fixed annual interest payments of £40 and a principal payment at maturity of £1,000 multiplied by the change in an equity price index, it would be inappropriate to identify a floating rate host and an embedded equity swap that has an offsetting floating rate leg. The host should be a fixed rate debt instrument that pays £40 annually because there are no floating interest rate cash flows in the hybrid instrument. [IFRS 9.IG C.1].

Further, as noted above, the terms of the embedded derivative should be determined so that it has a fair value of zero on inception of the hybrid instrument. It is explained that if an embedded non-option derivative could be separated on other terms, a single hybrid instrument could be decomposed into an infinite variety of combinations of host debt instruments and embedded derivatives. This might be achieved, for example, by separating embedded derivatives with terms that create leverage, asymmetry or some other risk exposure not already present in the hybrid instrument. [IFRS 9.IG C.1].

Finally, it is explained that the terms of the embedded derivative should be identified based on the conditions existing when the financial instrument was issued, [IFRS 9.IG C.1], or when a contract is required to be reassessed (see 7 below).

The following example illustrates how a foreign currency derivative embedded in a (hybrid) lease contract, that is not closely related, could be separated.

6.2 Embedded option-based derivative

As for non-option derivatives, IFRS 9 does not define the term ‘option-based derivative’ but suggests that it includes puts, calls, caps, floors and swaptions. An embedded derivative of this type should be separated from its host contract on the basis of the stated terms of the option feature. [IFRS 9.B4.3.3].

The implementation guidance explains that the economic nature of an option-based derivative is fundamentally different from a non-option derivative and depends critically on the strike price (or strike rate) specified for the option feature in the hybrid instrument. Therefore, the separation of such a derivative should be based on the stated terms of the option feature documented in the hybrid instrument. Consequently, in contrast to the position for non-option derivatives (see 6.1 above), an embedded option-based derivative would not normally have a fair value of zero. [IFRS 9.IG C.2].

In fact, if the terms of an embedded option-based derivative were identified so as to result in it having a fair value of zero, the implied strike price would generally result in the option being infinitely out-of-the-money, i.e. it would have a zero probability of the option feature being exercised. However, since the probability of exercising the option feature is generally not zero, this would be inconsistent with the likely economic behaviour of the hybrid. [IFRS 9.IG C.2].

Similarly, if the terms were identified so as to achieve an intrinsic value of zero, the strike price would equal the price of the underlying at initial recognition. In this case, the fair value of the option would consist only of time value. However, this may also be inconsistent with the likely economic behaviour of the hybrid, including the probability of the option feature being exercised, unless the agreed strike price was indeed equal to the price of the underlying at initial recognition. [IFRS 9.IG C.2].

6.3 Multiple embedded derivatives

Generally, multiple embedded derivatives in a single instrument should be treated as a single compound embedded derivative. However, embedded derivatives that are classified as equity are accounted for separately from those classified as assets or liabilities (see Chapter 47 at 6). In addition, derivatives embedded in a single instrument that relate to different risk exposures and are readily separable and independent of each other, should be accounted for separately from each other. [IFRS 9.B4.3.4].

For example, if a debt instrument has a principal amount related to an equity index and that amount doubles if the equity index exceeds a certain level, it is not appropriate to separate both a forward and an option on the equity index because those derivative features relate to the same risk exposure. Instead, the forward and option elements are treated as a single compound embedded derivative. Similarly, for an embedded call, put or prepayment option, if the risk associated with the option varies distinctly in different periods over the debt instrument's life, it would still be considered as a single embedded derivative. For the same reason, an embedded floor or cap on interest rates should not be separated into a series of ‘floorlets’ or ‘caplets’ (i.e. single interest rate options).26

On the other hand, if a hybrid debt instrument contains, for example, two options that give the holder a right to choose both the interest rate index on which interest payments are determined and the currency in which the principal is repaid, those two options may qualify for separation as two separate embedded derivatives since they relate to different risk exposures and are readily separable and independent of each other.27

7 REASSESSMENT OF EMBEDDED DERIVATIVES

It is clear that, on initial recognition, a contract should be reviewed to assess whether it contains one or more embedded derivatives requiring separation. However, the issue arises whether an entity is required to continue to carry out this assessment after it first becomes a party to a contract, and if so, with what frequency. [IFRS 9.BCZ4.99].

The question is relevant, for example, when the terms of the embedded derivative do not change but market conditions change and the market was the principal factor in determining whether the host contract and embedded derivative are closely related. Instances when this might arise are embedded foreign currency derivatives in host contracts that are insurance contracts or contracts for the purchase or sale of a non-financial item denominated in a foreign currency. [IFRS 9.BCZ4.100, IFRS 9.B4.3.8(d)].

Consider, for example, an entity that enters into a purchase contract denominated in US dollars. If, at the time the contract is entered into, US dollars are commonly used in the economic environment in which the transaction takes place, the contract will not contain an embedded foreign currency derivative requiring separation. Subsequently however, the economic environment may change such that transactions are now commonly denominated in euros, rather than US dollars. Countries joining the European Union may encounter just such a scenario.

Clearly, in this situation, an embedded foreign currency derivative would be separated from any new US dollar denominated purchase contracts, assuming they would not otherwise be considered closely related. However, should the entity separately account for derivatives embedded within its existing US dollar denominated contracts that were outstanding prior to the change in the market?

Conversely, the entity may have identified, and separately accounted for, embedded foreign currency derivatives in contracts denominated in euros that were entered into before the economic environment changed. Does the change in economic circumstances mean that the embedded derivative should now be considered closely related and not separately accounted for as a derivative? [IFRS 9.BCZ4.100‑101].

IFRS 9 confirms that entities should assess whether an embedded derivative is required to be separated from the host contract and accounted for as a derivative when the entity first becomes a party to the contract. Subsequent reassessment is prohibited unless there is a change in the terms of a contract that significantly modifies the cash flows that otherwise would be required under the contract, in which case an assessment is required. An entity determines whether a modification to cash flows is significant by considering the extent to which the expected future cash flows associated with the embedded derivative, the host contract or both have changed and whether the change is significant relative to the previously expected cash flows on the contract. [IFRS 9.B4.3.11].

For a financial liability, a change to the terms of the contract which significantly modifies the cash flows may also require derecognition of the original instrument and recognition of a new instrument. This is discussed in more detail in Chapter 52 at 6.

7.1 Acquisition of contracts

IFRS 9 requires an entity to assess whether an embedded derivative needs to be separated from the host contract and accounted for as a derivative when it first becomes a party to that contract. Therefore, if an entity purchases a contract that contains an embedded derivative, it assesses whether the embedded derivative needs to be separated and accounted for as a derivative on the basis of conditions at the date it acquires it, not the date the original contract was established. [IFRS 9.BCZ4.106].

7.2 Business combinations

From the point of view of a consolidated entity, the acquisition of a contract within a business combination accounted for using the acquisition method under IFRS 3 – Business Combinations – is hardly different from the acquisition of a contract in general. Consequently, an assessment of the acquiree's contracts should be made on the date of acquisition as if the contracts themselves had been acquired. [IFRS 3.15, 16(c)].

Neither IFRS 9 nor IFRS 3 applies to a combination of entities or businesses under common control or the formation of a joint venture. [IFRS 3.2, IFRS 9.B4.3.12].

However, in our view, if the acquisition method is applied to such arrangements, the requirements set out in IFRS 3 should be followed.

7.3 Remeasurement issues arising from reassessment

IFRS 9 does not address remeasurement issues arising from a reassessment of embedded derivatives. One of the reasons for prohibiting reassessment in general was the difficulty in determining the accounting treatment following a reassessment, which is explained in the following terms.

Assume that an entity, when it first became party to a contract, separately recognised a host asset not within the scope of IFRS 9, and an embedded derivative liability. If the entity were required to reassess whether the embedded derivative was to be accounted for separately and if the entity concluded some time after becoming a party to the contract that the derivative was no longer required to be separated, then questions of recognition and measurement would arise. In the above circumstances, the entity could: [IFRS 9.BCZ4.105]

  1. remove the derivative from its statement of financial position and recognise in profit or loss a corresponding gain or loss. This would lead to recognition of a gain or loss even though there had been no transaction and no change in the value of the total contract or its components;
  2. leave the derivative as a separate item in the statement of financial position. The issue would then arise as to when the item is to be removed from the statement of financial position. Should it be amortised (and, if so, how would the amortisation affect the effective interest rate of the asset), or should it be derecognised only when the asset is derecognised?
  3. combine the derivative (which is recognised at fair value) with the asset (which may not be recognised at fair value). This would alter the carrying amount of the asset even though there had been no change in the economics of the whole contract.

IFRS 9 states that subsequent reassessment is appropriate only when there has been a change in the terms of the contract that ‘significantly’ modifies the cash flows, accordingly the above issues are not expected to arise. [IFRS 9.BCZ4.105].

8 LINKED AND SEPARATE TRANSACTIONS AND ‘SYNTHETIC’ INSTRUMENTS

A derivative that is attached to a financial instrument, but is contractually transferable independently of that instrument, or has a different counterparty from that instrument, is not an embedded derivative, but a separate financial instrument. [IFRS 9.4.3.1].

This is also the case where a synthetic instrument is created by using derivatives to ‘alter’ the nature of a non-derivative instrument, as illustrated in the following example:

It is asserted that these transactions differ from those discussed at 3.2 above because those had no substance apart from the resulting interest rate swap. [IFRS 9.IG C.6].

Although some might argue that the substance of the two transactions above is the resulting synthetic fixed rate debt instrument, this interpretation is clearly not allowed under the standard.

Interestingly, the guidance does not address a much more common situation whereby a company both borrows from, and transacts a related derivative with, the same counterparty – typically the borrowing will be floating rate and the derivative a perfectly matched pay-fixed, receive-floating interest rate swap.

In fact, the subject of linking transactions for accounting purposes is a difficult one, especially in the context of financial instruments. The IASB's Conceptual Framework specifies that transactions should be reported in accordance with their substance and economic reality and not merely their legal form, [CF 2.12], and linking transactions can be seen as dealing with the question of how to interpret this principle.

IAS 32, and IFRS 9 deal with the subject in a piecemeal way. For example, in addition to the synthetic instrument illustration above:

  • two or more non-derivative contracts that are, ‘in substance’, no more than a single derivative are treated as a single derivative (see 3.2 above);
  • derivatives that are ‘attached’ to a non-derivative financial instrument may sometimes be regarded as part of a single combined instrument (see 3.2 above);
  • in classifying an instrument in consolidated financial statements as equity or a financial liability, all terms and conditions agreed between members of the group and holders of the instrument are considered (see Chapter 47 at 4.8);
  • if a loan is guaranteed by a third party, the expected credit loss determined in accordance with IFRS 9 should be calculated based on the combined credit risk of the guarantor and the guaranteed party if the guarantee is ‘integral’ to the contractual terms of the loan (see Chapter 51 at 5.8.1); and
  • determining the appropriate accounting treatment for a transaction that involves the transfer of some or all rights associated with financial assets, without the sale of the assets themselves, inevitably involves linking separate contracts to assess whether the transaction results in derecognition of the assets. For example, there might be one contract defining the continued ownership of the asset and another obliging the owner to transfer the rights associated with the asset to a third party (see Chapter 49 at 2, Chapter 50 at 2 and Chapter 52 at 3 and 4).

The Interpretations Committee first considered the subject of linkage in 2002 and has, in the past, made certain recommendations to the IASB. In fact, the requirement to take account of linked terms when classifying instruments as debt or equity in consolidated financial statements was introduced into IAS 32 in December 2003 following the Interpretations Committee's deliberations. In spite of agreeing proposed indicators for when transactions should be linked, and proposed guidance on accounting for linked transactions, these have never been published as an interpretation or standard.28

In August 2013 the Interpretations Committee received a request to clarify whether three different transactions should be accounted for separately or be aggregated and treated as a single derivative. The Committee decided not to add this issue to its agenda but noted that in order to determine whether to aggregate and account for the three transactions as a single derivative, reference should be made to B.6 (see 3.2 above) and C.6 (see Example 46.20 above) of the Implementation Guidance to IFRS 9 and paragraph AG39 of IAS 32. The Interpretations Committee noted that the application of the guidance in paragraph B.6 of IFRS 9 requires judgement and that the indicators in that paragraph may help an entity to determine the substance of the transaction, but that the presence or absence of any single specific indicator alone may not be conclusive.29

Consequently, in considering the borrowing and swap situation above, we are left principally with the guidance in IFRS 9. It is likely that the swap and the loan have their own terms and conditions and may be transferred or settled independently of each other. Therefore, the principles in Example 46.20 above would suggest separate accounting for the two instruments. Applying the guidance at 3.2 above (aggregating non-derivative transactions and treating them as a derivative) would also suggest separate accounting in most cases. Even though the instruments are transacted with the same counterparty, there will normally be a substantive business purpose for transacting the instruments separately.

It seems clear that in situations involving two separate legal contracts, in most cases, the two instruments will be regarded as separate for accounting purposes. However, in certain situations the linkage between those contracts (normally itself contractual) may be such that for accounting purposes those contracts cannot be regarded as existing independently of each other.

References

  1.   1 IGC Q&A 10‑6. Whilst the Implementation Guidance Committee (IGC) discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  2.   2 IFRIC Update, July 2007. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  3.   3 IFRIC Update, July 2006. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  4.   4 IFRIC Update, January 2007. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  5.   5 IASB Update, February 2007. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  6.   6 IFRIC Update, July 2006. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  7.   7 IFRIC Update, January 2007. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  8.   8 IFRIC Update, May 2009. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  9.   9 Staff paper, Term-extending options in fixed rate debt instruments, IFRS Interpretations Committee, March 2012. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  10. 10 IFRIC Update, March 2012. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  11. 11 Implementation of International Accounting Standards, British Bankers' Association, July 2004, para. 10. Whilst the guidance was provided in the context of IAS 39, it holds true under IFRS 9.
  12. 12 IFRIC Update, January 2016.
  13. 13 Information for Observers of March 2006 IFRIC meeting, Hedging Inflation Risk (Agenda Paper 12), IASB, March 2006, para. 32. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  14. 14 Information for Observers (December 2008 IASB meeting), Clarification of accounting for investments in collateralised debt obligations (Agenda Paper 6E), IASB, December 2008 and Q&As on accounting for some collateralised debts obligations (CDOs) – prepared by staff of the IASB, IASB, February 2009. Whilst the IASB discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  15. 15 IFRIC Update, May 2017.
  16. 16 IFRIC Update, September 2014. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  17. 17 IFRIC Update, May 2007. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  18. 18 Information for Observers (May 2007 IFRIC meeting), IAS 39: Financial Instruments: Recognition and Measurement AG33(d)(iii) of IAS 39 (Agenda Paper 11(v)), IASB, May 2007, paras. 12-14. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  19. 19 Information for Observers, paras. 18 to 19. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  20. 20 Information for Observers, paras. 20 to 28. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  21. 21 Information for Observers (December 2007 IASB meeting), Application of paragraph AG33(d)(iii) – Bifurcation of embedded foreign currency derivative (Agenda Paper 3C), IASB, December 2007, para. 11. Whilst the IASB discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  22. 22 Information for Observers (May 2007 IFRIC meeting), IAS 39: Financial Instruments: Recognition and Measurement AG33(d)(iii) of IAS 39 (Agenda Paper 11(v)), IASB, May 2007, para. 44. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  23. 23 Information for Observers (December 2007 IASB meeting), Application of paragraph AG33(d)(iii) – Bifurcation of embedded foreign currency derivative (Agenda Paper 3C), IASB, December 2007, paras. 12 and 13. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  24. 24 Information for Observers, para. 14. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  25. 25 Information for Observers, para. 15. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  26. 26 IGC Q&A 23‑8. Whilst the IGC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  27. 27 IGC Q&A 23‑8. Whilst the IGC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
  28. 28 IFRIC Update, April 2002, July 2002 and February 2003 and IASB Update, October 2002.
  29. 29 IFRIC Update, March 2014. Whilst the IFRIC discussion was held in the context of IAS 39, the discussion also holds true under IFRS 9.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset