Testing embedded derivatives under Ind AS 109 means first finding contracts that combine a non-derivative host with a feature whose value moves with an underlying variable — an interest rate, a foreign exchange rate, a commodity price, an index — and then testing three things in order: whether the host itself is a financial asset within the scope of Ind AS 109, whether the embedded feature itself meets the definition of a derivative, and, only where the host is not a financial asset in the standard's scope, whether the feature's economic characteristics are closely related to the host's. Separation and fair valuation follow only when that third test fails.
Why identification, not valuation, is where this goes wrong
A valuation specialist can fair value a derivative once it is flagged. The failure almost always happens earlier: a supply contract with a price indexed to a foreign benchmark, a loan with an equity conversion feature, a lease with an inflation-linked escalation beyond ordinary indexation, or a purchase contract denominated in a currency that is not the functional currency of either party and not routine for that contract type — none of these were ever treated as containing a derivative because nobody read the contract looking for one.
The testing sequence
- 01Build a population of contracts likely to contain an embedded featureDebt and preference instruments with conversion, prepayment or extension options; supply and purchase contracts with price indexation to something other than the functional currency inflation; leases with unusual escalation clauses; insurance-type contracts with investment features.
- 02Determine the scope test first: is the host itself a financial asset under Ind AS 109Where the host is a financial asset within the scope of Ind AS 109, the whole hybrid contract is classified and measured as a single unit — the separation question does not arise, and the entity's own classification of the host under the business model and cash flow tests governs.
- 03Where the host is not an Ind AS 109 financial asset, test whether the embedded feature meets the definition of a derivativeA value that changes in response to a specified underlying, little or no initial net investment, and settlement at a future date. An option, a forward price, an indexation clause, and a leverage factor are the usual signals.
- 04Test whether the feature's economic characteristics and risks are closely related to the host'sA foreign-currency price clause in a contract where that currency is routine for the economic environment of either substantial party, or is the currency the product is routinely denominated in internationally, is typically closely related and does not require separation. An unrelated currency, an equity conversion option in a debt host, or a leveraged indexation formula typically is not closely related.
- 05Conclude on separation and document the reasoning, not just the conclusionClosely related: no separation, account for the combined contract as one instrument. Not closely related, and the combined instrument is not already measured at fair value through profit or loss: separate the derivative and fair value it, with the host accounted for under the standard otherwise applicable to it.
- 06Recompute the fair value of any separated derivative independentlyUsing observable inputs where they exist; otherwise test the valuation model and its inputs against market data as of the measurement date, not as of the contract's inception.
- 07Test the disclosure of the separated derivative and the residual host separatelyThey are two different instruments after separation and should be disclosed, classified and measured as such, not netted or disclosed as one combined balance.
| Question | Evidence |
|---|---|
| Is the host within the scope of Ind AS 109 | Contract terms, nature of the host obligation |
| Does the embedded feature meet the derivative definition | Underlying variable, initial investment, settlement terms |
| Are the economic characteristics closely related | Comparison of the feature's risk profile to the host's, by instrument type |
| If separated, what is the fair value | Independent valuation model, market inputs as at measurement date |
Routine clauses are the ones most often missed, not the exotic ones. A commodity purchase contract priced in US dollars where neither counterparty's functional currency is the dollar, and the product is not conventionally priced internationally in dollars, contains a foreign-currency derivative that is frequently never identified because the contract looks entirely ordinary.
How we think about this
Once a feature is correctly identified as a derivative requiring separation, its fair valuation is a mechanical exercise that a model can reperform against market inputs. Finding the feature in the first place, and judging whether its characteristics are closely related to the host's, is a reading-and-reasoning exercise that depends on understanding the contract's commercial substance, and that is the auditor's work.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Revenue, receivables & cut-offInd AS 109: financial instruments and the expected credit loss modelThe old model waited for a loss to be incurred before providing for it. ECL is built the opposite way — provide for the loss you expect, before it happens.
- Audit documentationInd AS 109 ECL model in practice — testing expected credit lossThe ECL number on the balance sheet is a model output. The audit work is entirely about whether the stage allocation and the inputs feeding that model actually hold up.
- Audit documentationAuditing Ind AS 32 — testing the liability vs equity classificationInd AS 32 cares about substance over legal form for one specific question — does the issuer have an unconditional right to avoid delivering cash — and that single test decides liability vs equity.
- Audit documentationInd AS 113: fair value measurement, and the three-level hierarchy that ranks the inputsFair value isn't one method — it's a framework that ranks how reliable the inputs behind a number actually are, from an observable market price down to a pure internal estimate.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.