All Courses are free for limited time.
NISM Professor

Embedded derivative

Also written Embedded derivatives

A derivative component hidden inside a non-derivative contract, which Ind AS 109 requires to be pulled out and accounted for separately unless it is "closely related" to the host contract.

In plain language

Not every derivative shows up as its own trade. Sometimes a derivative is buried inside another contract — a bond whose redemption amount moves with a commodity price, or a lease with an option to buy the equipment at a fixed rate. The host contract might not look like a derivative at all, but a piece of it behaves like one.

Accounting has to see through that. Ind AS 109 requires that derivative components embedded in non-derivative contracts be separated and accounted for as standalone derivatives — but only if that embedded piece is not "closely related" to the host contract. If it is closely related, the whole contract is accounted for as one thing; if it is not, the derivative inside it has to be pulled out and measured on its own.

How it works

The workbook's rule, in the context of the accounting for exchange-traded currency derivatives, has two branches:

  1. Separate it, if not closely related. Where the embedded derivative is not "closely related" to its host contract, it must be separated from the host and accounted for as a standalone derivative in its own right — which, under the general rule for derivatives, means measured at Fair Value Through Profit or Loss (FVTPL) unless it qualifies for hedge accounting.
  2. Fall back to FVTPL for the whole hybrid, if it cannot be measured reliably. If the embedded derivative cannot be measured reliably once separated, Ind AS 109 does not leave it half-done — instead the entire hybrid contract is designated as FVTPL, host and embedded component together.

This sits alongside the workbook's general default measurement rule for derivatives: unless a derivative is in a hedging relationship, it is measured at FVTPL, with gains or losses recognised immediately in the profit and loss. An embedded derivative that has been separated out is treated no differently from a standalone one at that point — it just started life folded into another contract's paperwork.

A worked example

A company issues a Rs 50 crore rupee-denominated bond to an investor, but the bond's maturity redemption amount is contractually linked to the USD-INR exchange rate — if the rupee weakens beyond a stated level, the redemption payout rises.

Step 1 — spot the embedded derivative. The bond itself (the host contract) is a plain debt instrument. But the currency-linked redemption feature behaves like a currency derivative sitting inside it.

Step 2 — test "closely related". A foreign-currency-linked payoff on a rupee bond, for an issuer whose functional currency is the rupee, is not considered closely related to a plain-vanilla debt host — so separation is required.

Step 3 — separate and measure.

ComponentAccounting treatment
Host bond (plain debt)Amortised cost, as an ordinary borrowing
Embedded currency derivativeSeparated out, measured at FVTPL — gains and losses go straight to profit and loss, unless it is designated and qualifies as a hedge

Step 4 — the fallback. If, in a more complex instrument, the company's accountants find they cannot reliably measure the fair value of the embedded currency feature on its own — say the payoff formula is too bespoke to value separately — Ind AS 109 does not permit an estimate. Instead, the entire hybrid contract, bond and embedded feature together, is designated at FVTPL.

Why NISM asks about it

Chapter 9 (Accounting and Taxation of ETCD), section 9.1, lists embedded derivatives as one of the topics under Ind AS 109 hedge accounting, immediately after the three types of hedge accounting (fair value hedge, cash flow hedge, net investment hedge) and the default FVTPL measurement rule. Expect a question on the separation test — separate if not "closely related" — and the fallback rule when the separated derivative cannot be reliably measured.

Common exam traps

  • "Closely related" is the test, and it runs the opposite way to what intuition suggests: an embedded derivative is separated out precisely when it is not closely related to its host — a closely related one stays bundled in.
  • The fallback is for the whole hybrid contract, not just the embedded piece. If the separated derivative cannot be measured reliably, Ind AS 109 designates the entire contract at FVTPL — it does not leave the derivative unmeasured while the host is measured separately.
  • Default measurement for any derivative — embedded or standalone — is FVTPL, unless it is in a qualifying hedging relationship.
  • Do not confuse this with the three types of hedge accounting discussed in the same section (fair value, cash flow, net investment hedge) — those govern how a designated hedging instrument's gains and losses are recognised; the embedded derivative rule is about whether a derivative has to be pulled out of a contract in the first place.

Where this is taught

Free preparation for NISM Series IV

Related terms

← All terms
Something look wrong? Report it