Financial Instruments (IFRS 9)

Correct answer: .

IFRS 9 classifies a debt instrument based on two tests applied together: the business model test and the contractual cash flow characteristics (SPPI) test. A 'hold to collect and sell' business model, combined with cash flows that are solely payments of principal and interest, produces the FVOCI (fair value through other comprehensive income) category for debt instruments. Under this category, the asset is remeasured to fair value on the balance sheet, but interest revenue (using the effective interest method), expected credit loss impairment, and foreign exchange gains or losses are recognised in profit or loss exactly as they would be under amortised cost -- only the residual fair value movement goes to OCI, and that OCI balance is recycled to profit or loss on derecognition. The option describing amortised cost is wrong because that classification requires a 'hold to collect' business model only, without an integral selling objective; the mixed objective described here rules it out. The option treating any sale intention as an automatic trigger for FVTPL is wrong because FVTPL is the residual category for assets that fail the business model or SPPI tests entirely (or for equity instruments and instruments held for trading), not the outcome of a hold-to-collect-and-sell model with SPPI cash flows. The option describing FVOCI with all fair value movements kept outside profit or loss is wrong because that all-in-OCI, no-recycling treatment is the separate equity-instrument FVOCI election under IFRS 9.5.7.5, not the debt-instrument FVOCI category, which recognises interest, impairment and FX effects in profit or loss and recycles cumulative OCI on disposal.

Source: IFRS 9 Financial Instruments, paragraphs 4.1.2A and 5.7.10-5.7.11 (classification and measurement of debt instruments at FVOCI), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 requires trade receivables (and contract assets under IFRS 15) that do not contain a significant financing component to always be measured using the simplified approach, under which the loss allowance is lifetime expected credit losses from initial recognition, with no need to track or assess whether credit risk has increased significantly since origination. This is a deliberate practical expedient because most entities hold large volumes of short-dated trade receivables and tracking stage transitions for each one would be disproportionately costly. The option describing the general three-stage approach is wrong because that staged model (starting at 12-month losses and moving to lifetime losses only after a significant increase in credit risk) applies to instruments like loans and debt securities measured at amortised cost or FVOCI, not to trade receivables eligible for the simplified approach. The option describing no allowance until an actual default is wrong because it describes the incurred-loss model IFRS 9 replaced precisely because it recognised losses too late; IFRS 9 requires a forward-looking allowance from day one. The option limiting recognition to 12-month losses because the receivables mature within a year confuses the loss allowance's time horizon with the instrument's maturity; the simplified approach for short-dated trade receivables specifically substitutes lifetime losses for the 12-month measure, not the reverse.

Source: IFRS 9 Financial Instruments, paragraph 5.5.15 (simplified approach for trade receivables and contract assets without a significant financing component), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 carves out a specific exception for financial liabilities designated at fair value through profit or loss (the fair value option): the portion of the fair value change attributable to changes in the liability's own credit risk is presented in other comprehensive income, while the remaining amount is presented in profit or loss. This exists because the IASB judged it counterintuitive for an entity to recognise a profit-or-loss gain simply because its own creditworthiness worsened (making the liability cheaper to settle in fair value terms) -- the kind of result the incurred-loss thinking under the previous standard, IAS 39, allowed. Unlike most OCI items under IFRS 9, this own-credit-risk amount is never subsequently reclassified ('recycled') to profit or loss, even on derecognition of the liability; it may only be transferred within equity. The option putting the full amount in profit or loss describes the ordinary FVTPL treatment that would apply if this exception did not exist or if one of its exceptions (such as the treatment creating or enlarging an accounting mismatch) applied, but the question specifies no such exception applies. The option splitting the amount 50/50 between profit or loss and OCI has no basis in the standard, which allocates by the actual causal split between own-credit-risk and other fair value drivers, not a fixed ratio. The option of deducting directly from retained earnings describes neither IFRS 9's treatment nor any standard equity adjustment mechanism for this item.

Source: IFRS 9 Financial Instruments, paragraphs 5.7.7-5.7.9 (presentation of fair value changes on financial liabilities designated at FVTPL attributable to own credit risk), IFRS Foundation, ifrs.org

Correct answer: .

The equity FVOCI election under IFRS 9 is a distinct category from the debt-instrument FVOCI classification, and its defining feature is that fair value gains and losses accumulated in other comprehensive income are never reclassified ('recycled') to profit or loss, not even on sale or other derecognition of the shares. The cumulative amount may be transferred within equity, for example moved directly to retained earnings, but it can never pass through the profit or loss statement in any period. Dividends received on the shares, by contrast, are recognised in profit or loss (unless they clearly represent a recovery of part of the cost of the investment), and the shares are not subject to the impairment requirements that apply to amortised-cost or debt-FVOCI assets. The option describing reclassification to profit or loss on sale is wrong because that recycling behaviour applies to the debt-instrument FVOCI category (interest-bearing assets passing the business model and SPPI tests) but was deliberately excluded from the equity election specifically to prevent selective realisation of gains through profit or loss. The option describing retrospective restatement through profit or loss for prior periods is wrong; IFRS 9 has no such mechanism, and equity FVOCI gains are never restated into profit or loss at any point. The option describing a depreciated revaluation surplus wrong because equity shares are not depreciable assets and IFRS 9 has no comparable amortisation mechanism for this OCI balance.

Source: IFRS 9 Financial Instruments, paragraphs 5.7.5-5.7.6 and B5.7.1 (irrevocable FVOCI election for equity instruments; no subsequent reclassification to profit or loss), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 permits reclassification of financial assets only when, and only when, an entity changes the business model under which it manages those assets, and requires that reclassification to be applied prospectively from the reclassification date -- the first day of the first reporting period following the change. Previously recognised gains, losses and interest are not restated, which distinguishes this from a change in accounting policy or a correction of an error, both of which typically require retrospective treatment. A genuine business model change of the kind described (senior-management-approved, significant to operations, and evident to external parties) moves the bonds here from amortised cost toward the FVOCI category, with any resulting fair value adjustment recognised prospectively at the reclassification date. The option describing retrospective restatement is wrong because IFRS 9 explicitly bars restating prior interest, gains or losses on reclassification; that treatment would apply to certain error corrections or policy changes under IAS 8, not to a business model reclassification under IFRS 9. The option claiming reclassification is never permitted is wrong -- it is permitted, but only triggered by this specific type of infrequent, significant, top-down change, not by management's routine day-to-day decisions about individual assets. The option describing derecognition and reissuance as new instruments is wrong; reclassification changes measurement and presentation of the existing instruments going forward, it does not trigger derecognition of the original contractual rights.

Source: IFRS 9 Financial Instruments, paragraphs 4.4.1-4.4.3 and 5.6.1-5.6.2 (reclassification of financial assets following a change in business model; prospective application), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 kept the IAS 39 separation logic for hybrid contracts whose host is not itself a financial asset within the standard's classification scope -- financial liabilities and non-financial contracts are the main examples. When the host is a financial liability (as here) and is not measured at FVTPL, an embedded feature must be separated and accounted for as a standalone derivative if its economic characteristics and risks are not closely related to the host's, a separate instrument with the same terms would itself meet the definition of a derivative, and the hybrid contract as a whole is not already measured at fair value through profit or loss. Once separated, the host debt instrument is measured at amortised cost using the normal effective interest method, while the embedded derivative is measured at fair value through profit or loss. The option describing automatic amortised-cost measurement of the whole hybrid contract with no separation is wrong because it ignores the very separation trigger the question describes being met. The option describing the whole contract as a single financial asset at FVTPL is wrong on two counts: this is a liability, not an asset, and IFRS 9's 'no separation, classify the whole hybrid instrument' rule applies specifically to hybrid contracts with a financial asset host, not a liability host. The option claiming IFRS 9 has no separation concept is factually wrong; IFRS 9 explicitly retained this requirement for non-asset hosts precisely because removing it entirely would have created a gap for liability-side hybrid instruments.

Source: IFRS 9 Financial Instruments, paragraph 4.3.3 (separation of embedded derivatives from hosts that are not financial assets), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9's derecognition model for financial assets is a multi-step analysis, and after confirming the contractual rights to the cash flows have been transferred (or qualify for pass-through treatment), the first substantive test is whether the entity has transferred or retained substantially all the risks and rewards of ownership of the asset. If substantially all risks and rewards are transferred, the asset is derecognised. If substantially all are retained, derecognition is not appropriate and the asset continues to be recognised, typically with a corresponding liability for any proceeds received. Only when the outcome of that test is inconclusive -- neither substantially transferred nor substantially retained -- does the analysis move on to a separate control test to decide between full derecognition and continuing-involvement accounting. The option about legal form as a sale versus secured borrowing is wrong because IFRS 9 derecognition turns on the substance of risks-and-rewards transfer, not on the legal label attached to the transaction; a transaction labelled a sale can still fail derecognition if substantially all risks and rewards are retained. The option about consolidating a special purpose entity is wrong because consolidation is governed by IFRS 10's control model for group reporting, a separate question from whether an individual asset is derecognised from the transferor's own financial statements. The option about prior FVTPL measurement is wrong; how the asset was previously classified does not determine whether derecognition criteria are met on transfer.

Source: IFRS 9 Financial Instruments, paragraph 3.2.6 (derecognition: risks and rewards test as the primary step, before any control assessment), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 replaced IAS 39's rigid quantitative bright-line effectiveness test with a more principles-based set of conditions. To qualify for hedge accounting, an entity must demonstrate an economic relationship between the hedged item and the hedging instrument, such that their values would be expected to move in opposite directions because of a common underlying or hedged risk; that the effect of credit risk does not dominate the value changes that result from that economic relationship (for example, severe counterparty credit deterioration on an uncollateralised derivative could otherwise swamp the hedge's intended offset); and that the hedge ratio designated for accounting purposes is the same ratio actually used for risk management purposes, so the entity cannot artificially rebalance the ratio purely to obtain a particular accounting outcome. The option describing an 80-125% quantitative threshold is wrong because that bright-line test was a defining feature of IAS 39 that IFRS 9 deliberately removed, replacing it with the qualitative conditions above. The option claiming effectiveness can simply be assumed with no assessment is wrong; IFRS 9 still requires an effectiveness assessment at inception and on an ongoing basis, it has just changed the assessment's nature from a rigid numerical test to a qualitative and, where needed, quantitative economic-relationship analysis. The option requiring the hedge ratio to exactly match total risk exposure regardless of actual risk management practice is wrong; IFRS 9 ties the accounting hedge ratio to how the entity actually manages the risk, not to some abstract notion of total exposure divorced from real risk management decisions.

Source: IFRS 9 Financial Instruments, paragraph 6.4.1 (qualifying criteria for hedge accounting: economic relationship, credit risk not dominating, and hedge ratio consistent with risk management), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9's classification model for financial liabilities is much simpler than the model for financial assets: the default and by far most common outcome is subsequent measurement at amortised cost using the effective interest method. Fair value through profit or loss is the exception, reserved for liabilities held for trading, derivative liabilities, contingent consideration in a business combination, and liabilities an entity voluntarily designates at FVTPL under the fair value option (typically to eliminate an accounting mismatch). An ordinary trade payable with no embedded derivative and no FVTPL designation falls into the default amortised cost category. The option requiring FVTPL for all financial liabilities is wrong; IFRS 9 does not impose blanket fair value measurement on liabilities the way some early proposals considered -- amortised cost remains the norm. The option describing FVOCI is wrong because IFRS 9 has no FVOCI category for financial liabilities at all; the FVOCI category (for debt instruments) and the FVOCI election (for equity instruments) are asset-side concepts only, with the narrow exception of the own-credit-risk OCI presentation that applies only to liabilities already designated at FVTPL, not to liabilities generally. The option describing lower-of-cost-and-net-realisable-value measurement is wrong; that principle governs inventory under IAS 2, an entirely different standard covering non-financial assets, not financial liabilities under IFRS 9.

Source: IFRS 9 Financial Instruments, paragraph 4.2.1 (financial liabilities measured at amortised cost unless required or elected to be measured at FVTPL), IFRS Foundation, ifrs.org

Correct answer: .

Classification under IFRS 9 requires both the business model test and the SPPI (solely payments of principal and interest) test to be satisfied; a favourable business model cannot rescue an instrument that fails the cash flow characteristics test. IFRS 9 defines interest, for SPPI purposes, as consideration for the time value of money, credit risk, and other basic lending risks and costs plus a reasonable profit margin. Interest contingent on the debtor's revenue is not consideration for those factors -- it introduces equity-like or business-performance risk into what is meant to be a basic lending arrangement -- so the contractual cash flows are not solely principal and interest. Because the instrument fails SPPI regardless of the business model, IFRS 9 requires it to be measured at fair value through profit or loss, even though it is held in a hold-to-collect model. The option claiming the business model alone determines classification is wrong because both tests must be passed; a hold-to-collect model does not exempt an instrument from the SPPI test. The option claiming the hold-to-collect model overrides the cash flow terms is wrong for the same reason -- there is no override mechanism in IFRS 9 that lets business model results substitute for a failed SPPI assessment. The option describing a required host/derivative split into amortised-cost components is wrong; IFRS 9 does not separate embedded features from a financial asset host at all -- when an asset fails SPPI, the entire hybrid instrument is classified as a single unit at FVTPL, not split and both parts measured at amortised cost.

Source: IFRS 9 Financial Instruments, paragraphs 4.1.2, 4.1.4 and B4.1.7A (SPPI test; contingent or business-performance-linked interest fails the test; classification of the entire instrument at FVTPL on SPPI failure), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9's general impairment model uses three stages measured by the change in credit risk since initial recognition, not by whether a payment has actually been missed. Stage 1 applies from initial recognition and carries a 12-month expected credit loss allowance. Once there has been a significant increase in credit risk (SICR) since initial recognition -- evidenced here by the sharp rating downgrade and the market's reassessment of default probability -- the instrument moves to Stage 2, where the loss allowance is measured at an amount equal to lifetime expected credit losses, even though the instrument is not yet credit-impaired and payments remain current. The option keeping the bond in Stage 1 is wrong because SICR, not actual missed payments, is the trigger for moving to lifetime losses; waiting for a default event would recognise losses too late, which is the exact criticism of the incurred-loss model IFRS 9 replaced. The option moving straight to Stage 3 is wrong because Stage 3 requires the instrument to be credit-impaired, meaning an event with a detrimental impact on estimated future cash flows has actually occurred (for example a default or a concession to a borrower in financial difficulty); a downgrade alone, however sharp, is a SICR trigger for Stage 2, not evidence of credit-impairment justifying net-carrying-amount interest recognition. The option describing derecognition and recognition of a new instrument is wrong because a third-party credit downgrade is not a modification of the bond's own contractual terms at all -- derecognition and modification accounting apply only when the issuer and holder actually renegotiate the contractual cash flows, which has not happened here.

Source: IFRS 9 Financial Instruments, paragraphs 5.5.3, 5.5.5 and 5.5.9 (recognition of expected credit losses and the significant-increase-in-credit-risk trigger), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 has a dedicated category for purchased or originated credit-impaired (POCI) financial assets, precisely because ordinary Stage 1/2/3 tracking assumes credit quality was unimpaired when the instrument was first recognised by the reporting entity -- which is untrue here, since the purchaser knowingly buys an already credit-impaired loan and prices in the expected losses from day one. For POCI assets, no separate loss allowance is grossed up at initial recognition; instead, the expected credit losses are folded directly into the initial fair value the purchaser pays, and interest revenue afterward is recognised using a credit-adjusted effective interest rate -- a rate derived by discounting the estimated future cash flows (already reflecting expected credit losses) to the instrument's amortised cost -- applied to the amortised cost (net) carrying amount rather than to a gross carrying amount. The option assigning a fresh Stage 1 allowance is wrong because Stage 1 assumes no significant credit deterioration has occurred since initial recognition, which cannot be true for an instrument that is impaired at the very moment of purchase; POCI assets are carved out of the three-stage model entirely and never begin in Stage 1. The option describing an immediate day-one expense followed by the stated coupon rate is wrong because POCI accounting does not front-load a loss expense at all -- the discount is already embedded in the low purchase price, and only favourable or unfavourable changes in lifetime expected credit loss estimates after acquisition are recognised as impairment gains or losses; using the stated coupon rather than the credit-adjusted rate would also ignore the pricing discount entirely. The option requiring FVTPL classification is wrong because being credit-impaired does not itself fail the SPPI test -- SPPI is about the nature of the contractual cash flows (principal and interest), not the borrower's current credit standing -- so a POCI loan can still be, and typically is, held at amortised cost if the business model supports it.

Source: IFRS 9 Financial Instruments, Appendix A (definition of 'credit-adjusted effective interest rate' and 'purchased or originated credit-impaired financial assets') and paragraph 5.4.1(b), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 uses a quantitative '10% test' to decide whether a renegotiation of a financial liability's terms is substantial enough to be treated as an extinguishment: the discounted present value of the cash flows under the new terms, including any fees paid net of fees received between the borrower and lender and discounted at the original effective interest rate, is compared with the discounted present value of the remaining cash flows under the original terms. If that difference is at least 10%, the terms are deemed substantially different. Here the difference is 12%, which clears the 10% threshold, so the exchange is accounted for as an extinguishment: the original liability is derecognised, a new liability is recognised at its fair value (net of the fee, which is treated as part of the exchange rather than deferred and amortised), and any difference between the derecognised carrying amount and the new liability's fair value is recognised immediately in profit or loss. The option describing modification accounting is wrong because that treatment -- recalculating the gross carrying amount at the original rate and recognising the adjustment as a modification gain or loss -- applies specifically when the 10% threshold is NOT met, i.e. for non-substantial modifications, which is not the case on these facts. The option describing a prospective change in accounting estimate is wrong because IFRS 9 does not permit spreading a substantial change in a liability's terms over future periods with no immediate income statement effect; both the substantial-modification (extinguishment) and non-substantial-modification outcomes require an immediate profit or loss recognition, just calculated differently. The option describing an equity transaction is wrong because paying a fee to a lender to renegotiate loan terms is a transaction between the company and a creditor, not a transaction with an owner in its capacity as owner, so equity accounting has no application here regardless of the fee.

Source: IFRS 9 Financial Instruments, paragraph 3.3.2 and paragraph B3.3.6 (the '10 per cent' test for substantially different terms and treatment of fees), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 contains specific application guidance for contractually linked instruments -- tranched structures, such as this securitisation, where multiple tranches create concentrations of credit risk and a subordination waterfall determines the order of payment. Rather than assessing the junior tranche's legal wording alone, the holder must 'look through' to the underlying pool of instruments and perform two linked assessments: first, whether the underlying pool itself, if held directly, contains cash flow characteristics that are (or could be) solely payments of principal and interest, and second, whether the tranche being assessed has credit risk exposure equal to or less than the credit risk of that underlying pool (because a tranche that is leveraged relative to the pool, in a way that creates exposure exceeding the pool's own risk, fails the test even if the pool itself qualifies). The option finding automatic failure because of subordination alone is wrong because subordination is exactly the fact pattern the look-through guidance was written to address in detail -- the standard does not simply disqualify every subordinated tranche outright; it requires the two-part look-through analysis before reaching a conclusion. The option looking only at the tranche's own legal terms in isolation is wrong because ordinary SPPI assessment of a single, non-tranched instrument would indeed stop at that instrument's own terms, but the whole point of the contractually-linked-instruments guidance is that this ordinary approach is insufficient once payments are contractually linked to, and prioritised against, an underlying pool -- the pool's composition must be examined. The option asserting automatic FVTPL classification is wrong because contractually linked instruments are not excluded from amortised cost or FVOCI outright; if the tranche passes both parts of the look-through test and the holder's business model supports it, the tranche can still qualify for amortised cost or FVOCI, exactly like any other debt instrument.

Source: IFRS 9 Financial Instruments, paragraphs B4.1.20-B4.1.26 (contractually linked instruments and the look-through approach), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 requires an issuer of a financial guarantee contract (that is not designated at fair value through profit or loss and does not arise from an insurance-scoped arrangement) to subsequently measure the guarantee at the HIGHER of two amounts: the loss allowance determined under IFRS 9's expected credit loss model, and the amount initially recognised (the guarantee's initial fair value) less the cumulative amount of income recognised in line with the company's revenue recognition policy. This 'higher of' test exists precisely to catch situations like the one described, where the credit risk on the underlying obligor has deteriorated enough that the expected loss now exceeds the remaining unamortised fee -- if the company simply carried the unamortised fee balance, it would understate its exposure to a real, growing risk of having to pay out under the guarantee. The option measuring at only the unamortised fee balance is wrong because it ignores the expected-credit-loss side of the comparison entirely, which is exactly the amount that has become larger and more relevant here. The option treating financial guarantee contracts as outside IFRS 9's subsequent measurement requirements is wrong because IFRS 9 explicitly brings issued financial guarantee contracts (not accounted for under IFRS 17) within its scope for both classification and impairment purposes; they are not simply frozen at initial fair value. The option using the LOWER of the two amounts is wrong because it inverts the test -- using the lower amount would systematically understate the liability whenever expected credit losses rise above the fee balance, defeating the purpose of requiring a credit-loss-based floor on the guarantee's carrying amount.

Source: IFRS 9 Financial Instruments, paragraph 4.2.1(c) and paragraph 9.3.3.2 (subsequent measurement of financial guarantee contracts at the higher of the ECL allowance and the amortised initial recognition amount), IFRS Foundation, ifrs.org

Correct answer: .

In a qualifying cash flow hedge under IFRS 9, the gain or loss on the hedging instrument is split between an effective and an ineffective portion, not recognised wholesale in one place. The effective portion -- the lower, in absolute amount, of the cumulative change in the hedging instrument's fair value and the cumulative change in the present value of the hedged item's expected future cash flows attributable to the hedged risk -- is recognised in other comprehensive income within the cash flow hedge reserve, where it stays until the hedged forecast transaction itself affects profit or loss (at which point it is reclassified, or 'recycled'). Any excess of the swap's fair value change over the hedged item's present value change is, by definition, hedge ineffectiveness, and IFRS 9 requires that excess to be recognised immediately in profit or loss rather than deferred in OCI. The option sending the entire fair value change to OCI is wrong because it would defer genuine ineffectiveness -- a real economic mismatch between the hedge and the hedged risk -- alongside the effective portion, which IFRS 9 does not permit; only the effective portion qualifies for OCI treatment. The option sending the entire change to profit or loss is wrong because a hedging relationship having some ineffectiveness does not, by itself, disqualify it from hedge accounting altogether under IFRS 9's more principles-based effectiveness requirements (unlike IAS 39's stricter 80-125% bright line); the relationship continues to qualify, and only the ineffective slice is expensed, not the whole change. The option deferring the entire change as a balance sheet item with no OCI or profit-or-loss effect is wrong because cash flow hedge accounting always requires splitting recognition between OCI (effective portion) and profit or loss (ineffective portion) each period; nothing is held off both statements simultaneously.

Source: IFRS 9 Financial Instruments, paragraph 6.5.11 (recognition of gains and losses on cash flow hedges, effective and ineffective portions), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 allows an entity to recognise and derecognise a regular way purchase or sale of financial assets using either trade date accounting or settlement date accounting, applied consistently within each category of financial asset. Under settlement date accounting, the asset itself is recognised only on the settlement date (2 April here), but IFRS 9 still requires the entity to account for any change in the fair value of the asset to be received during the period between trade date and settlement date in the same way it would account for the acquired asset once recognised. Because these shares are classified at fair value through profit or loss, the price rise between 28 March and 2 April is recognised in profit or loss during that window, even though the share asset itself has not yet been formally recognised on the balance sheet. The option ignoring the price movement entirely and recording the shares at the original 28 March cost is wrong because that treatment would only be appropriate for an asset measured at amortised cost, where fair value changes in the interim period are not recognised; it is not correct for an FVTPL asset, where interim fair value movements must flow through profit or loss even under settlement date accounting. The option recognising both an asset and a liability on the trade date and remeasuring them is a description of trade date accounting, not the settlement date policy the company has adopted for this category -- the company cannot apply trade date recognition here since it has chosen, and must consistently apply, settlement date accounting for this asset category. The option requiring retroactive restatement to trade date accounting is wrong because IFRS 9 does not require or permit switching accounting policy transaction-by-transaction based on whether the price happens to move; the chosen policy is applied consistently regardless of price movement.

Source: IFRS 9 Financial Instruments, paragraphs 3.1.2 and B3.1.3-B3.1.6 (regular way purchases and sales, trade date and settlement date accounting), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 measures every financial asset at initial recognition at fair value, but then treats transaction costs differently depending on the asset's measurement category. For a financial asset measured at fair value through profit or loss, transaction costs are expensed immediately in profit or loss rather than added to the initial carrying amount, because capitalising them would be inconsistent with a category that is remeasured to fair value every period with changes going straight to profit or loss anyway. For a financial asset measured at amortised cost (or at fair value through other comprehensive income), IFRS 9 requires the initial fair value to be adjusted for transaction costs that are incremental and directly attributable to the acquisition, and those capitalised costs are then factored into the calculation of the effective interest rate used to recognise interest income over the asset's life. The option capitalising the fees for both assets is wrong because it ignores the specific carve-out for FVTPL instruments, where capitalisation is explicitly not permitted. The option expensing the fees for both assets is wrong because it ignores the requirement, for amortised cost and FVOCI instruments, to include directly attributable transaction costs in the initial measurement -- transaction costs are very much part of initial measurement for those categories, just not for FVTPL. The option reversing the treatment -- capitalising for the fair value asset and expensing for the amortised cost asset -- is wrong because it is the exact opposite of IFRS 9's rule: fair value through profit or loss is the category that expenses transaction costs immediately, while amortised cost is the category that capitalises them.

Source: IFRS 9 Financial Instruments, paragraph 5.1.1 (initial measurement of financial assets and treatment of transaction costs by measurement category), IFRS Foundation, ifrs.org

Correct answer: .

When a modification of a financial asset's contractual cash flows does not result in derecognition, IFRS 9 requires the gross carrying amount of the asset to be recalculated as the present value of the renegotiated (modified) cash flows, discounted at the asset's ORIGINAL effective interest rate -- not a newly recalculated rate. Any difference between this recalculated gross carrying amount and the previous gross carrying amount is a modification gain or loss, and IFRS 9 requires that gain or loss to be recognised in profit or loss immediately, at the date of modification, rather than spread over future periods. The option adjusting only future interest income prospectively with a new rate is wrong because it describes a catch-up-free, rate-reset approach that IFRS 9 does not use for non-derecognition modifications; the standard instead requires an immediate recalculation of the carrying amount using the ORIGINAL rate and an immediate profit-or-loss adjustment, not a purely prospective spreading of the effect. The option treating the modification as a new loan at fair value with the difference in OCI is wrong on two counts: modification accounting for a non-derecognition event does not involve derecognising and re-recognising a brand new instrument at fair value at all, and even where fair value differences do arise elsewhere in IFRS 9, a modification gain or loss on an amortised cost asset is a profit-or-loss item, not an OCI item. The option deferring the gain or loss until final repayment is wrong because IFRS 9 explicitly requires immediate profit-or-loss recognition of the modification gain or loss at the modification date; deferral to a future settlement date would misstate the current period's results and is not permitted.

Source: IFRS 9 Financial Instruments, paragraph 5.4.3 (accounting for a modification of a financial asset that does not result in derecognition), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 permits an entity to make an irrevocable election, at initial recognition, to designate a financial asset (that would otherwise be measured at amortised cost or FVOCI) as measured at fair value through profit or loss, if doing so eliminates or significantly reduces a measurement or recognition inconsistency -- an 'accounting mismatch' -- that would otherwise arise from measuring related assets or liabilities, or recognising gains and losses on them, on different bases. The designation must be made at initial recognition of the instrument and, once made, cannot be revoked even if the mismatch later narrows or disappears; the same fair value option, on the same irrevocable-at-initial-recognition basis, is also available for financial liabilities under IFRS 9. The option allowing reclassification to FVTPL at any later date, with the ability to reclassify back once the mismatch disappears, is wrong because the fair value option is a one-time, irrevocable choice made only at initial recognition; IFRS 9 does not allow entities to opt in and out of FVTPL for the same instrument as circumstances change, which would open the door to earnings management. The option saying the company must simply continue at amortised cost regardless of the mismatch is wrong because it ignores the fair value option that IFRS 9 specifically provides for exactly this scenario. The option restricting the company to hedge accounting only is wrong because the fair value option and hedge accounting are separate, independently available tools under IFRS 9 for addressing measurement or timing mismatches; the fair value option is available for a qualifying instrument regardless of whether a formal hedging relationship is also designated.

Source: IFRS 9 Financial Instruments, paragraphs 4.1.5 and 4.2.2 (the fair value option to eliminate or significantly reduce an accounting mismatch, for financial assets and financial liabilities respectively), IFRS Foundation, ifrs.org

Correct answer: .

IAS 32 requires both of two conditions before a financial asset and a financial liability may be presented net in the statement of financial position: the entity must currently have a legally enforceable right to set off the recognised amounts, and it must intend either to settle the asset and liability on a net basis or to realise the asset and settle the liability simultaneously. Both conditions are mandatory; satisfying only the legal right without also having the settlement intention does not permit offsetting, so the company must continue to present the asset and liability separately, gross, in this scenario. The suggestion that a currently enforceable legal right alone is sufficient is wrong because it ignores the second, equally mandatory condition about settlement intention -- IAS 32 explicitly treats the two conditions as cumulative, not alternative. The claim that offsetting is never permitted under any circumstances is wrong because IAS 32 does permit net presentation, but only when both conditions above are met together; the standard does not prohibit offsetting outright. The suggestion that written consent from the counterparty at the reporting date is what unlocks offsetting is wrong because IAS 32's test turns on the entity's own currently enforceable legal right and settlement intention, not on obtaining a fresh, separate written agreement at each reporting date; the legal right itself must already be enforceable, not merely available if the counterparty agrees.

Source: IAS 32 Financial Instruments: Presentation, paragraphs 42-48 (offsetting a financial asset and a financial liability), IFRS Foundation, ifrs.org

Correct answer: .

IAS 32 treats a puttable instrument as meeting the definition of a financial liability by default, because the holder's right to put it back to the issuer for cash or another financial asset gives the issuer a contractual obligation to deliver cash. As a narrow exception, such an instrument may instead be classified as equity, but only if it meets every one of a specific set of conditions together: it must entitle the holder to a pro rata share of the entity's net assets on liquidation, it must be in the class of instruments that is subordinate to all other classes, all instruments in that subordinate class must have identical features, the instrument must carry no contractual obligation to deliver cash or another financial asset other than the holder's right to put it back, and the total expected cash flows attributable to it over its life must be based substantially on the profit or loss, the change in recognised net assets, or the change in fair value of the entity. Missing any one of these conditions means the instrument stays a financial liability. The suggestion that the exception applies automatically to any private-company puttable instrument is wrong because the exception's conditions turn on the instrument's contractual features, not on the issuer's ownership structure or public/private status. The claim that a five-year exercise deferral alone triggers the exception is wrong because IAS 32 sets out no such time-based test; deferring when a put can first be exercised does not, by itself, satisfy any of the listed conditions. The idea that the exception is limited to related-party holders is wrong because the exception's conditions are about the instrument's own contractual terms and subordination, not about who holds it.

Source: IAS 32 Financial Instruments: Presentation, paragraphs 16A-16D (puttable instruments classified as equity instruments), IFRS Foundation, ifrs.org

Correct answer: .

IAS 32 treats an entity's own equity instruments -- including shares it has repurchased and holds as treasury shares -- as not giving rise to a gain or loss for the entity, no matter what price they are later resold, reissued, or cancelled at. Consideration paid to reacquire the shares reduces equity directly, and consideration received on a later resale is likewise recognised directly within equity, with no amount ever passing through profit or loss. The entire favourable difference between the original repurchase cost and the higher resale price is recorded as a direct adjustment within equity (commonly added to share premium or a similar reserve), not as income of any kind. The option treating the difference as a profit-or-loss gain is wrong because IAS 32 specifically prohibits recognising any gain or loss in profit or loss on transactions in an entity's own equity instruments, regardless of whether the counterparty is a third party. The option routing the difference through other comprehensive income, with later recycling on cancellation, is wrong because IAS 32 does not use an OCI mechanism for treasury share transactions at all; the difference goes directly to equity, with no profit-or-loss effect ever, whether the shares are resold or subsequently cancelled. The option calling the difference revenue is wrong because a transaction in an entity's own equity instruments is a transaction with the entity's owners in their capacity as owners, not a revenue-generating transaction with a customer, and IAS 32 excludes it entirely from profit or loss.

Source: IAS 32 Financial Instruments: Presentation, paragraph 33 (treasury shares -- no gain or loss recognised in profit or loss on purchase, sale, issue or cancellation of own equity instruments), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9's reclassification requirement -- under which an entity reclassifies affected financial assets when, and only when, it changes the business model for managing them -- applies solely to debt instruments classified as amortised cost, FVOCI, or FVTPL under IFRS 9's classification model. The equity FVOCI election available for equity investments not held for trading is a separate, one-time, irrevocable choice made at initial recognition; because it does not depend on a business model assessment or a contractual cash flow characteristics test in the way debt classification does, no later event -- including a change in the business model used for an entirely different portfolio of debt instruments -- can reclassify it. The company's equity investment therefore remains in the FVOCI category, with its fair value changes continuing to be presented in other comprehensive income and never recycled to profit or loss, even on sale. The option claiming the reclassification requirement applies equally to equity instruments is wrong because IFRS 9 expressly limits mandatory reclassification to debt instruments; equity investments are not eligible for reclassification at all once the FVOCI election is made. The option suggesting reclassification is permitted specifically when the fair value has fallen is wrong because IFRS 9 ties reclassification only to a change in business model for debt instruments, not to the direction or magnitude of an equity investment's fair value movement. The option asserting that business models can never change for any asset category is also wrong -- IFRS 9 does contemplate business model changes and requires reclassification of the affected debt instruments when they are expected to be infrequent -- but that reclassification mechanism simply has no application to equity investments in the first place.

Source: IFRS 9 Financial Instruments, paragraphs 4.1.4, 4.1.2A, 5.7.5 and 4.4.1-4.4.3 (equity investments at fair value through other comprehensive income; reclassification applies only to debt instruments), IFRS Foundation, ifrs.org

Correct answer: .

Under IFRS 9's fair value hedge accounting model, the hedging instrument -- here, the interest rate swap -- is remeasured at fair value each period, with the resulting gain or loss recognised in profit or loss. At the same time, the carrying amount of the hedged item -- the fixed-rate bond -- is adjusted for the gain or loss attributable to the specific hedged risk (interest rate risk) only, and that basis adjustment is also recognised in profit or loss. Because both the instrument's fair value change and the hedged item's basis adjustment flow through profit or loss in the same period, an effective fair value hedge produces largely offsetting entries there, which is the mechanism's defining feature and what distinguishes it from cash flow hedge accounting, where the effective portion instead goes to other comprehensive income. The option describing the swap's changes as deferred in OCI until the bond is derecognised or matures is wrong because that OCI-deferral treatment describes cash flow hedge accounting, not the fair value hedge model used here. The option claiming neither instrument is remeasured until the hedge relationship ends is wrong because fair value hedge accounting requires remeasurement of the hedging instrument, and a basis adjustment to the hedged item, throughout the life of the relationship, not only at its conclusion. The option asserting that only the swap is remeasured and the bond's carrying amount is never adjusted is wrong because adjusting the hedged item's carrying amount for the hedged risk is the second, equally essential half of fair value hedge accounting; without it, the hedge would not achieve the offsetting effect the model is designed to produce.

Source: IFRS 9 Financial Instruments, paragraph 6.5.8 (fair value hedges -- gain or loss on the hedging instrument recognised in profit or loss; carrying amount of the hedged item adjusted for the gain or loss attributable to the hedged risk, also recognised in profit or loss), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 7's fair value hierarchy disclosures, which draw on the three-level hierarchy in IFRS 13, classify a fair value measurement based on the lowest level of input that is significant to the measurement as a whole. Level 1 inputs are unadjusted quoted prices in active markets for identical items; Level 2 inputs are observable, directly or indirectly, other than quoted prices included within Level 1 (for example, quoted prices for similar items, or inputs derived from observable market data); Level 3 inputs are unobservable inputs, typically the entity's own assumptions, used when little or no relevant market activity exists for the item or a similar one. Because the discounted cash flow model here relies on the company's own unobservable assumptions about future volumes and margins, with no comparable market data available, the measurement is classified as Level 3. The option asserting that discounted cash flow models are automatically Level 1 is wrong because Level 1 is reserved specifically for unadjusted quoted prices in active markets for identical items, not for outputs of any valuation model. The option claiming any model-based measurement is automatically Level 2 is wrong because Level 2 requires the model's significant inputs to be observable; a model built on the entity's own unobservable assumptions falls to Level 3 instead, regardless of how sophisticated the model itself is. The option suggesting the hierarchy does not apply outside actively traded instruments is wrong because the hierarchy exists precisely to classify fair value measurements across the full spectrum from actively quoted prices down to wholly unobservable, entity-specific assumptions; it is not limited to actively traded items.

Source: IFRS 7 Financial Instruments: Disclosures, paragraph 27A, and IFRS 13 Fair Value Measurement, paragraphs 72-90 (the three-level fair value hierarchy and its levels of inputs), IFRS Foundation, ifrs.org

Correct answer: .

Under IFRS 9, when an entity has no reasonable expectation of recovering a financial asset in its entirety or a portion of it, it must directly reduce the asset's gross carrying amount by that amount -- this is a write-off. A write-off may relate to a financial asset in its entirety or only to a portion of it, and it constitutes a derecognition event for the amount written off, distinct from simply carrying a fully provided-for loss allowance against an asset that remains on the balance sheet at its full gross amount. Writing off does not necessarily mean the entity is abandoning all further enforcement or recovery efforts against the borrower; it reflects the accounting conclusion that recovery is no longer reasonably expected, based on the information available. The option describing an indefinitely carried gross amount fully offset by a 100 percent loss allowance is wrong because IFRS 9 specifically requires the gross carrying amount itself to be reduced once there is no reasonable expectation of recovery, rather than leaving it unchanged and relying solely on an ever-larger allowance. The option describing a shift to an off-balance-sheet memorandum record is wrong because IFRS 9's write-off mechanism operates through directly reducing the gross carrying amount and derecognising the written-off amount within the financial statements themselves, not through an informal memorandum tracking system outside them. The option calling for reversing all previously recognised expected credit losses is wrong because a write-off does not reverse prior loss recognition; instead, the loss allowance previously built up is used against, and reduced along with, the gross carrying amount being written off, consistent with the loss having already been substantially recognised.

Source: IFRS 9 Financial Instruments, paragraph 5.4.4 and Appendix A (write-off -- direct reduction of the gross carrying amount of a financial asset when there is no reasonable expectation of recovery), IFRS Foundation, ifrs.org

Correct answer: .

Under IFRS 9's general three-stage expected credit loss model, interest revenue is calculated differently depending on the asset's stage. While an asset remains in Stage 1 (or Stage 2, where credit risk has increased significantly but the asset is not yet credit-impaired), interest revenue is calculated by applying the effective interest rate to the asset's gross carrying amount, before deducting the loss allowance. Once the asset becomes credit-impaired and moves to Stage 3, interest revenue is instead calculated by applying the effective interest rate to the asset's net carrying amount -- the gross carrying amount less the loss allowance -- reflecting that a credit-impaired asset is no longer expected to generate a return on its full gross balance. This produces a difference between the interest that would result from applying the effective interest rate to the gross carrying amount and the interest revenue actually recognised for a credit-impaired asset. The option claiming the calculation is identical in every stage is wrong because IFRS 9 specifically changes the base amount, from gross to net carrying amount, once an asset becomes credit-impaired in Stage 3. The option asserting that interest recognition stops entirely in Stage 3 is wrong because IFRS 9 does not eliminate interest recognition for credit-impaired assets; it continues to recognise interest, just calculated on the reduced net carrying amount rather than the gross amount. The option suggesting the interest rate itself is reduced to zero is wrong because IFRS 9 does not adjust the effective interest rate when an asset becomes credit-impaired; the rate stays the same, and it is the base to which that rate is applied -- gross versus net carrying amount -- that changes.

Source: IFRS 9 Financial Instruments, paragraph 5.4.1(b) (calculation of interest revenue on credit-impaired financial assets using the net carrying amount), IFRS Foundation, ifrs.org

Correct answer: .

Contracts to buy or sell a non-financial item, such as a commodity, are generally outside the scope of IFRS 9. However, a contract that can be settled net in cash or another financial instrument -- including because its terms permit net settlement -- can still be treated as if it were a financial instrument and brought within IFRS 9's scope as a derivative. The 'own use' exemption provides a carve-out from that outcome: even if a contract could otherwise be net-settled, it remains outside IFRS 9 if it was entered into, and continues to be held, for the purpose of receiving or delivering the non-financial item in accordance with the entity's expected purchase, sale, or usage requirements, rather than for trading or speculative purposes. Because the company here holds the contract solely to receive the physical raw material for its own production, and has no history of net-settling similar contracts or of reselling the commodity shortly after delivery, the own use exemption applies and the contract stays outside IFRS 9's scope despite its net-settlement clause. The option asserting that the mere presence of a net-settlement clause automatically forces the contract into IFRS 9's scope regardless of intent or practice is wrong because that is precisely the outcome the own use exemption is designed to prevent for contracts genuinely entered into for the entity's own purchase or usage requirements. The option describing a split into a derivative component and a separate executory contract is wrong because IFRS 9 does not require bifurcating an own-use commodity contract in this manner; the own use exemption keeps the whole contract outside the standard's scope, not just part of it. The option claiming any contract involving a physical commodity is automatically outside IFRS 9's scope, regardless of settlement terms or practices, is wrong because a commodity contract that meets the net-settlement criteria and does not meet the own use exemption's conditions -- for example, one entered into for trading purposes -- is brought within IFRS 9's scope and accounted for as a derivative.

Source: IFRS 9 Financial Instruments, paragraphs 2.4-2.7 (contracts to buy or sell a non-financial item; net settlement criteria and the 'own use' exemption), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 requires bifurcation -- separating an embedded derivative from its host and accounting for it separately at fair value through profit or loss -- only for hybrid contracts whose host is not itself a financial asset within the scope of IFRS 9, such as a hybrid contract with a financial liability host or a host that is a non-financial contract. Where the host contract is a financial asset within the scope of IFRS 9, no such separation applies at all; instead, the entity applies IFRS 9's classification requirements -- the business model assessment and the contractual cash flow characteristics (SPPI) test -- to the entire hybrid contract as a single unit. If the embedded feature causes the hybrid contract's contractual cash flows to fail the SPPI test, the whole instrument is simply classified and measured at fair value through profit or loss in its entirety, rather than being split into a separately measured derivative component and a separately classified host. The option describing separation of the embedded derivative with the host measured under its own category is wrong because that bifurcation approach applies to financial liability hosts (and non-financial hosts), not to financial asset hosts, which IFRS 9 always classifies as a whole. The option applying a closely-related test to decide whether to separate is wrong for the same reason: that closely-related-style test is part of the bifurcation analysis used for liability and non-financial hosts, and IFRS 9 does not perform any such bifurcation analysis for a financial asset host in the first place. The option describing only a disclosure-only independent valuation, with no separate recognition, is wrong because it mischaracterises the actual mechanism: the whole hybrid contract, embedded feature included, is recognised and measured as a single financial asset under IFRS 9's classification model, not left unmeasured in the primary statements with disclosure standing in for accounting.

Source: IFRS 9 Financial Instruments, paragraph 4.3.2 and paragraphs 4.1.1-4.1.5 (hybrid contracts with a host that is a financial asset within the scope of IFRS 9 are classified in their entirety; no separate bifurcation of an embedded derivative applies), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 draws a firm line between financial assets and financial liabilities when it comes to reclassification: a financial asset is reclassified between measurement categories only when, and exactly when, the entity changes the business model it uses to manage the group of financial assets affected by that change, and even then only prospectively from the start of the next reporting period. Financial liabilities receive no equivalent provision at all -- IFRS 9 simply does not include a reclassification mechanism for liabilities, so a bond payable measured at amortised cost remains at amortised cost (or, if originally designated at fair value through profit or loss under the irrevocable fair value option, remains there) for as long as it is outstanding, no matter how the entity's objectives for managing its liabilities evolve. The option mirroring the asset test for liabilities is wrong because it assumes a reclassification trigger for liabilities that the standard never created; demonstrating a significant, external-facing change in objective is the asset test, and it has no liability counterpart. The option describing a periodic, audit-committee-approved reclassification right is wrong because no such mechanism exists anywhere in IFRS 9 for either assets or liabilities; reclassification of assets is triggered solely by a genuine business model change, not by elapsed time or governance approval. The option claiming amortised-cost measurement forever forecloses reclassification for any instrument is wrong because it misstates the asset side of the rule: a financial asset measured at amortised cost is reclassified to fair value through profit or loss (or vice versa) precisely when the entity's business model for managing it changes, so amortised cost is not a permanent bar for assets -- only for liabilities is reclassification unavailable altogether.

Source: IFRS 9 Financial Instruments, paragraph 4.4.1 (reclassification of financial assets only, upon a change in business model) and paragraph 4.4.2 (an entity shall not reclassify any financial liability), IFRS Foundation, ifrs.org

Correct answer: .

IAS 32 classifies a derivative on an entity's own equity instruments -- which is what a conversion option is -- as equity only if it will be settled by the entity exchanging a fixed amount of cash (or another financial asset) for a fixed number of its own equity instruments: the 'fixed-for-fixed' condition. Here the number of shares delivered on conversion is not fixed; it varies inversely with the share price so that its value always equals the same $1,000 cash amount, which means the holder is economically entitled to a fixed cash value rather than a fixed equity stake, exposing the entity to a cash-like, index-linked obligation rather than a true residual-interest exposure. That fails the fixed-for-fixed condition, so the conversion option cannot be classified as equity; it is instead accounted for as a liability, specifically a derivative on the entity's own equity measured at fair value through profit or loss, even though matching the entity's functional currency removes one potential source of failure (a currency mismatch) that the condition also screens for. The option treating settlement in own shares as sufficient on its own is wrong because IAS 32 looks past the form of settlement -- shares rather than cash -- to whether the number of shares is fixed; many instruments settled in shares still fail the fixed-for-fixed condition precisely because the share count itself varies. The option treating the currency match as the only requirement is wrong because currency denomination is only one element of the fixed-for-fixed test; the test equally requires the number of shares delivered to be fixed, which is not the case on these facts. The option describing this as an ordinary compound instrument needing a liability/equity split is wrong because that split accounting applies to a conversion option that itself qualifies as equity under the fixed-for-fixed condition; here the conversion option fails that condition entirely and is instead a wholly separate derivative liability, not a residual equity component sitting alongside a debt host.

Source: IAS 32 Financial Instruments: Presentation, paragraph 11 (definitions of a financial liability and an equity instrument) and paragraph 16 / AG27 (the 'fixed-for-fixed' condition for a derivative on own equity), IFRS Foundation, ifrs.org

Correct answer: .

IAS 32 treats a convertible bond like this as a compound financial instrument and requires a residual, not a relative-fair-value, split between its liability and equity components. The liability component is measured first, at the present value of the instrument's contractual cash flows -- the coupons and principal -- discounted at the market rate of interest for an otherwise-identical bond carrying no conversion feature, which here is $9,200,000. The equity component, representing the value of the conversion option, is then recognized simply as whatever is left of the total proceeds after that liability amount is deducted: $10,000,000 minus $9,200,000, or $800,000. Critically, the equity component is never independently fair-valued under this approach, and once measured, it is not remeasured at subsequent reporting dates. The option assigning the entire $10,000,000 to the liability with no equity component is wrong because it describes the post-ASU 2020-06 US GAAP treatment for most convertible instruments, not IAS 32's residual approach, which has always required splitting out an equity component for an instrument like this one. The option independently fair-valuing both components and forcing any excess over the proceeds into an immediate loss is wrong because that describes a relative-fair-value allocation method, which IAS 32 does not use for compound instruments; IAS 32's method never independently fair-values the equity component or recognizes a day-one loss from this split. The option reversing the amounts, assigning the larger figure to equity, is wrong simply because it has the mechanics backwards for these facts: the liability component is computed first and directly, as the $9,200,000 present value of the cash flows at the market rate, and whatever remains of the $10,000,000 proceeds -- $800,000 -- is assigned to equity as the residual, not the other way around.

Source: IAS 32 Financial Instruments: Presentation, paragraphs 28-32 and AG31 (compound financial instruments, residual method for separating liability and equity components), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9's derecognition model provides a specific middle path for exactly this situation -- control transferred, but risks and rewards neither substantially transferred nor substantially retained: continuing-involvement accounting. Under this approach the entity derecognizes the transferred asset only to the extent it is no longer exposed to its risks and rewards, and continues to recognize the asset only to the extent of its continuing involvement -- here, the bank's maximum exposure to loss under the guarantee, capped at 5% of the pool's principal -- together with an associated liability measured so that the net carrying amount of the retained asset and liability reflects the rights and obligations the bank has kept. This correctly confines both the bank's remaining asset recognition and its related liability to the capped exposure it actually still bears, rather than either the whole pool or nothing. The option derecognizing the entire pool and treating the guarantee as a mere off-balance-sheet note disclosure is wrong because a retained guarantee exposure of this kind is a form of continuing involvement that IFRS 9 requires to be recognized on the balance sheet, not relegated to disclosure alone. The option continuing to recognize the entire pool at its original carrying amount is wrong because it describes the outcome for substantially retaining risks and rewards, a different, more extreme fact pattern than this one, where the bank has already concluded it retained only some, not substantially all, of the risks and rewards; continuing-involvement accounting is specifically the narrower, partial-recognition outcome for the facts given, not full retention. The option derecognizing the whole pool while recognizing a guarantee liability at its full notional amount is wrong because continuing-involvement accounting requires the retained asset, not just a separate guarantee liability, to also remain partly on the balance sheet to the extent of the continuing exposure, with the liability measured to net consistently against that retained asset rather than set at the guarantee's full notional cap in isolation from the asset side of the entry.

Source: IFRS 9 Financial Instruments, paragraphs 3.2.5-3.2.6 and 3.2.16 (continuing involvement when an entity neither transfers nor retains substantially all risks and rewards but does not retain control) and paragraph B3.2.9 (measurement of the retained asset and associated liability, including the guarantee case), IFRS Foundation, ifrs.org

Correct answer: .

IFRS 9 distinguishes between a forecast transaction that is still expected to occur, even if hedge accounting is discontinued for some other reason, and a forecast transaction that is no longer expected to occur at all. When the hedged future cash flow is still expected, the cumulative gain or loss already accumulated in the cash flow hedge reserve stays there, deferred in other comprehensive income, until the forecast transaction itself affects profit or loss. But once the forecast transaction is no longer expected to occur at all -- as here, where the purchase has been cancelled outright -- there is no future transaction left for that deferred amount to attach to, so IFRS 9 requires the entire cumulative gain or loss to be reclassified out of the cash flow hedge reserve and recognized in profit or loss immediately, as a reclassification adjustment. The option claiming the amount is never reclassified is wrong because it confuses this item with the separate own-credit-risk OCI amount for fair-value-option liabilities, which genuinely is never recycled to profit or loss; a cash flow hedge reserve balance is always eventually recognized in profit or loss, either when the transaction occurs or, as here, immediately when it stops being expected. The option transferring the amount directly to retained earnings is wrong for the same reason: that bypass-profit-or-loss treatment is specific to the own-credit-risk OCI item, not to cash flow hedge reserve balances, which route through profit or loss. The option continuing to defer the amount until the original four-month window would have passed is wrong because IFRS 9 ties reclassification to whether the transaction is still expected to occur, not to a calendar deadline; once the transaction is no longer expected at all, the amount is reclassified at once, well before any original timing window would have elapsed.

Source: IFRS 9 Financial Instruments, paragraph 6.5.12(b) (reclassification of the cash flow hedge reserve to profit or loss when a hedged future cash flow is no longer expected to occur), IFRS Foundation, ifrs.org