US GAAP vs IFRS Differences

Correct answer: .

IAS 2 explicitly prohibits the use of last-in, first-out as a cost formula for inventory, while ASC 330 in US GAAP continues to permit it, making this the correct choice and the clearest cost-flow difference between the two frameworks. The option describing first-in, first-out is wrong because IAS 2 and ASC 330 both permit it as an acceptable cost formula, so it is not a point of divergence. The option describing weighted-average cost is wrong for the same reason: both frameworks accept it as one of the standard cost formulas for interchangeable inventory. The option describing specific identification is wrong because both frameworks require or permit it for inventory items that are not ordinarily interchangeable, or that are produced and segregated for specific projects, so there is no restriction unique to either framework there. The LIFO prohibition under IFRS is a long-standing, deliberate divergence rather than an oversight, and it is one of the most frequently tested US GAAP vs IFRS inventory differences precisely because it can create materially different cost of goods sold and ending inventory figures during periods of changing prices.

Source: IFRS Foundation, IAS 2 Inventories (cost formulas, prohibiting LIFO); FASB Accounting Standards Codification ASC 330 Inventory (permitting LIFO)

Correct answer: .

IAS 2 requires a previously recognized inventory write-down to be reversed when the circumstances that caused it no longer exist or when net realizable value has clearly increased, but the reversal is capped at the amount of the original write-down so the new carrying amount never exceeds the item's original cost. US GAAP inventory guidance, once a write-down establishes a new, lower cost basis, does not permit that basis to be written back up even if the item's market value later recovers. The option claiming neither framework allows any adjustment is wrong because IAS 2 explicitly mandates a capped reversal in these circumstances. The option reversing the frameworks' positions is wrong because it attributes the mandatory-reversal treatment to US GAAP and the no-reversal treatment to IAS 2, which is the opposite of each standard's actual rule. The option allowing an uncapped reversal under both frameworks is wrong because IAS 2's reversal is explicitly limited to the original write-down amount, and US GAAP does not permit any reversal at all, capped or otherwise.

Source: IFRS Foundation, IAS 2 Inventories, paragraphs 33-34 (reversal of write-down); FASB Accounting Standards Codification ASC 330-10-35 (subsequent measurement of inventory, no write-up after write-down)

Correct answer: .

IAS 38 sets out six specific criteria an entity must demonstrate before development expenditure can be recognized as an intangible asset: technical feasibility of completing the asset, intention to complete it, ability to use or sell it, how it will generate probable future economic benefits, availability of adequate technical, financial and other resources, and the ability to measure the attributable expenditure reliably. Once all six are demonstrated, capitalization of further development costs is required, not merely permitted. ASC 730, by contrast, generally requires research and development costs to be charged to expense as incurred, reflecting a US GAAP view that the outcome of R&D activity is too uncertain to support asset recognition, aside from narrow exceptions such as certain capitalized software costs outside the scope of ASC 730 itself. The option describing the frameworks in reverse order is wrong because it attributes the expense-as-incurred rule to IAS 38 and the capitalization option to ASC 730, which inverts each standard's actual treatment. The option treating both frameworks as requiring expensing is wrong because it ignores IAS 38's mandatory capitalization once its criteria are met. The option treating both frameworks as requiring capitalization is wrong because ASC 730's default rule for research and development costs is expensing, not capitalization, regardless of technical feasibility.

Source: IFRS Foundation, IAS 38 Intangible Assets, paragraphs 57-58 (development cost recognition criteria); FASB Accounting Standards Codification ASC 730-10-25 Research and Development (costs charged to expense when incurred)

Correct answer: .

IAS 36 requires an entity to assess at each reporting date whether indicators suggest a previously recognized impairment loss on an asset (other than goodwill) may have decreased or no longer exists, and if so, to reverse the loss, but the increased carrying amount is capped at what the asset's depreciated carrying amount would have been had no impairment loss been recognized in prior years. ASC 360, governing US GAAP treatment of long-lived assets held and used, takes the opposite position: once an impairment loss is recognized, it establishes a new cost basis, and that basis cannot subsequently be written back up even if the asset's value recovers. The option attributing the reversal-permitted treatment to US GAAP and the no-reversal rule to IFRS is wrong because it swaps the two frameworks' actual positions. The option stating neither framework allows reversal is wrong because IAS 36 explicitly requires it, subject to its stated ceiling, once indicators of decreased impairment are present. The option describing an automatic reversal under both frameworks is wrong because US GAAP's ASC 360 prohibits reversal outright, and even under IAS 36 the reversal is capped rather than unlimited, so it is not simply automatic to the full extent of any recoverable-amount increase.

Source: IFRS Foundation, IAS 36 Impairment of Assets, paragraphs 114-117 (reversal of an impairment loss); FASB Accounting Standards Codification ASC 360-10-35-20 (no subsequent reversal for held-and-used long-lived assets)

Correct answer: .

ASC 360 uses a two-step impairment model for long-lived assets held and used: first, a recoverability test compares the asset's carrying amount to the sum of undiscounted future cash flows expected from its use and eventual disposal; only if the carrying amount exceeds that undiscounted total does the entity move to step two and measure a loss based on fair value. Because the undiscounted cash flows here exceed the carrying amount, the recoverability test passes and no impairment is recognized under US GAAP, regardless of what a discounted calculation would show. IAS 36 skips any undiscounted screening step entirely and compares the carrying amount directly to the recoverable amount, defined as the higher of fair value less costs of disposal and value in use, where value in use is calculated using discounted cash flows; since both of those figures are below the carrying amount here, an impairment loss is recognized under IFRS. The option reversing which framework reaches which conclusion is wrong because it swaps the actual outcomes. The option finding no impairment under both frameworks ignores that IFRS's test is based on discounted, not undiscounted, cash flows. The option finding an impairment under both frameworks ignores that the US GAAP recoverability screen is passed on an undiscounted basis, which blocks any loss measurement at this stage.

Source: FASB Accounting Standards Codification ASC 360-10-35-17 (recoverability test using undiscounted cash flows); IFRS Foundation, IAS 36 Impairment of Assets, paragraphs 18 and 6 (recoverable amount as the higher of fair value less costs of disposal and value in use)

Correct answer: .

IAS 16 allows an entity to choose, as an accounting policy applied to an entire class of property, plant and equipment, either the cost model or the revaluation model; under the revaluation model the asset is carried at its fair value at the revaluation date less subsequent depreciation and impairment, with increases generally recognized in other comprehensive income and accumulated as revaluation surplus, subject to reversing any previous decrease recognized in profit or loss for that same asset. US GAAP has no equivalent policy choice: property, plant and equipment is measured using the historical cost model, less accumulated depreciation and impairment, and upward revaluation to fair value is not permitted under any circumstances. The option reversing which framework allows revaluation is wrong because it attributes the optional revaluation model to US GAAP and a cost-only requirement to IAS 16, which is the opposite of each standard's actual position. The option claiming neither framework permits revaluation is wrong because IAS 16 explicitly offers it as an accounting policy choice. The option claiming both frameworks mandate revaluation at each reporting date is wrong because even under IAS 16 the revaluation model is elective, not mandatory, and revaluations only need to occur with sufficient regularity to keep carrying amounts from materially differing from fair value.

Source: IFRS Foundation, IAS 16 Property, Plant and Equipment, paragraphs 29-31 (cost model and revaluation model); FASB Accounting Standards Codification ASC 360 Property, Plant, and Equipment (historical cost model, no revaluation)

Correct answer: .

IAS 16 requires that each part of an item of property, plant and equipment with a cost that is significant in relation to the total cost of the item be depreciated separately, which in practice means components with materially different useful lives or consumption patterns, such as aircraft engines versus the airframe, must be identified and depreciated on their own schedules. US GAAP does not impose this requirement: the component approach to depreciation is an available method, but entities are not obligated to disaggregate an asset into components, and in practice many US GAAP preparers depreciate the asset as a single unit using a composite or overall useful life. The option describing US GAAP as mandating componentization and IFRS as leaving it to discretion is wrong because it inverts the actual requirement, since IAS 16 imposes a mandatory requirement rather than leaving component depreciation purely to judgment once the significance threshold is met. The option claiming neither framework allows separate depreciation of a part is wrong because IAS 16 explicitly requires it under the stated conditions. The option limiting the requirement to regulated industries like aviation is wrong because IAS 16's componentization rule applies generally to any qualifying asset across any industry, not only to aircraft or similarly regulated equipment.

Source: IFRS Foundation, IAS 16 Property, Plant and Equipment, paragraph 43 (depreciation of significant parts separately); FASB Accounting Standards Codification ASC 360 Property, Plant, and Equipment (component approach permitted, not required)

Correct answer: .

IAS 40 defines investment property as land or a building held to earn rentals or for capital appreciation rather than for use in production or administration, and it permits an entity to choose the fair value model as its accounting policy for all such investment property, under which fair value changes are recognized directly in profit or loss each period, with no depreciation charged. US GAAP has no separate standard dedicated to investment property; a building leased out to third parties is generally accounted for like any other item of property, plant and equipment under cost-based guidance, measured at depreciated historical cost and tested for impairment, with fair value changes not recognized through profit or loss. The option describing US GAAP as having a dedicated fair-value-mandating standard and IFRS as requiring the cost model is wrong because it reverses which framework actually offers the fair value election, and IAS 40's fair value model is elective rather than restricted to IFRS-only cost treatment. The option claiming neither framework permits fair value accounting here is wrong because IAS 40 explicitly allows it as a policy choice. The option requiring inventory classification is wrong because a building generating rental income and held for the long term does not meet the definition of inventory under either framework.

Source: IFRS Foundation, IAS 40 Investment Property, paragraphs 5 and 33 (definition of investment property; fair value model policy choice); US GAAP has no separate investment property standard, so such property is generally accounted for under FASB Accounting Standards Codification ASC 360 Property, Plant, and Equipment

Correct answer: .

IAS 41 applies to biological assets such as living animals and plants used in agricultural activity, and it requires them to be measured, both on initial recognition and at each subsequent reporting date, at fair value less estimated costs to sell, with the resulting gain or loss recognized in profit or loss for the period in which it arises, except in the narrow case where fair value cannot be reliably measured on initial recognition. US GAAP has no equivalent comprehensive standard applying a fair value model to biological assets generally; livestock and similar agricultural assets held by most entities are typically carried at historical cost, consistent with the broader US GAAP preference for cost-based measurement, with only limited industry-specific guidance addressing certain agricultural producers. The option requiring fair value under both frameworks is wrong because it overstates US GAAP's treatment, which lacks IAS 41's general fair value mandate. The option swapping the frameworks is wrong because it attributes the dedicated fair-value agriculture standard to US GAAP and a cost-only rule to IFRS, which is the reverse of the actual standards. The option prohibiting recognition of living animals as assets under either framework is wrong because both frameworks recognize such animals as assets when the entity controls them and future economic benefits are expected to flow to the entity; the disagreement is only about how they are subsequently measured.

Source: IFRS Foundation, IAS 41 Agriculture, paragraphs 10-13 (recognition and fair value measurement of biological assets); US GAAP has no directly equivalent comprehensive standard, so agricultural assets are generally measured at historical cost

Correct answer: .

IAS 37 requires a provision to be recognized when an outflow of resources is probable, and the standard defines probable as more likely than not to occur, which is commonly applied as a threshold just above 50 percent; a 60 percent likelihood clearly clears that bar, so a provision is recognized together with a reasonable estimate of the amount. ASC 450 also uses the word probable as its recognition threshold, but in practice that threshold is applied at a materially higher likelihood, often described as roughly 75 to 80 percent or higher, so a 60 percent likelihood, while indicating a real possibility of loss, typically falls into the reasonably possible category that leads to disclosure in the notes rather than recognition of a liability. The option finding recognition under both frameworks is wrong because it assumes the two frameworks apply an identical numeric threshold, when the practical application of the probable threshold differs meaningfully between them. The option finding disclosure only under both frameworks is wrong because it understates IAS 37's lower more-likely-than-not threshold, which 60 percent satisfies. The option reversing the two frameworks' outcomes is wrong because it attributes the lower threshold to US GAAP and the higher threshold to IFRS, which is the opposite of how each standard is actually applied in practice.

Source: IFRS Foundation, IAS 37 Provisions, Contingent Liabilities and Contingent Assets, paragraphs 14 and 23 (probable defined as more likely than not); FASB Accounting Standards Codification ASC 450-20 Loss Contingencies (probable threshold applied at a materially higher likelihood in practice)

Correct answer: .

FASB's simplification of inventory guidance moved most US GAAP inventory measured under first-in, first-out or average cost to a lower-of-cost-and-net-realizable-value test, aligning that portion of US GAAP with the approach IAS 2 already applies to all inventory. That simplification explicitly carved out inventory measured using the last-in, first-out method or the retail inventory method, which continue to apply the older lower-of-cost-or-market test, under which market is defined as replacement cost, bounded by a ceiling equal to net realizable value and a floor equal to net realizable value less a normal profit margin. Because IAS 2 does not permit LIFO as a cost-flow assumption at all, an entity using LIFO under US GAAP would, if it reported the same inventory under IFRS, measure it using the ordinary lower-of-cost-and-net-realizable-value approach with no replacement-cost ceiling or floor concept involved. The option describing a fair-value-through-profit-or-loss approach is wrong because neither framework measures inventory at fair value in this way; both use a lower-of-cost-based test. The option claiming the FASB simplification applied without exception to all cost-flow assumptions is wrong because the simplification specifically excluded LIFO and retail-method inventory, leaving the older test in place for them. The option describing an absolute prohibition on writing inventory below cost, and no IAS 2 subsequent-measurement rule at all, is wrong because both frameworks require inventory to be written down when its recoverable value falls below cost.

Source: FASB Accounting Standards Update 2015-11, Simplifying the Measurement of Inventory (lower of cost and net realizable value, excluding LIFO and retail-method inventory); IFRS Foundation, IAS 2 Inventories, paragraphs 9 and 25-27 (lower of cost and net realizable value; LIFO prohibited)

Correct answer: .

IFRS 16 eliminates the finance-lease-versus-operating-lease classification decision for lessees entirely: with limited exceptions for short-term and low-value asset leases, a lessee recognizes a right-of-use asset and a lease liability for every qualifying lease and reports depreciation of the asset plus interest on the liability, producing a single accounting model regardless of the lease's economic character. ASC 842, by contrast, retains the classification step: a lessee must apply specific criteria to sort each lease into a finance lease, accounted for much like an IFRS 16 lease with separate interest and amortization, or an operating lease, which still appears on the balance sheet but produces a straight-line total lease expense rather than separate interest and depreciation lines. The option describing IFRS 16 as requiring the identical classification test is wrong because removing that step for lessees is precisely what distinguishes IFRS 16 from ASC 842. The option describing IFRS 16 as allowing leases to stay off the balance sheet is wrong because bringing nearly all leases onto the balance sheet was the standard's core objective. The option describing a mere reversal of which category gets straight-line treatment is wrong because IFRS 16 does not use finance-versus-operating categories for lessees at all.

Source: FASB Accounting Standards Codification ASC 842 Leases (lessee classification into finance and operating leases); IFRS Foundation, IFRS 16 Leases, paragraph 22 (single lessee accounting model, right-of-use asset and lease liability)

Correct answer: .

ASC 350, as simplified by ASU 2017-04, measures a goodwill impairment loss as the amount by which a reporting unit's carrying amount, including goodwill, exceeds its fair value, with the loss capped at the total goodwill assigned to that unit so it can never exceed the goodwill actually on the books. IAS 36 instead compares the cash-generating unit's carrying amount to its recoverable amount, defined as the higher of fair value less costs of disposal and value in use, where value in use is the present value of the unit's expected future cash flows; any resulting impairment loss is applied first to reduce the goodwill allocated to that unit before any other assets are written down. The option describing IAS 36 as ignoring value in use is wrong because value in use is one of the two amounts IAS 36 explicitly compares against fair value less costs of disposal when determining the recoverable amount. The option requiring an undiscounted-cash-flow screening step under both frameworks is wrong because neither ASC 350 nor IAS 36 uses an undiscounted-cash-flow recoverability test for goodwill; that screening step belongs to the impairment model for long-lived assets held and used, not goodwill. The option claiming no cap exists under either framework is wrong because ASC 350 explicitly limits the loss to the goodwill balance of the unit being tested.

Source: FASB Accounting Standards Codification ASC 350-20, as amended by Accounting Standards Update No. 2017-04 (goodwill impairment measured as excess of carrying amount over fair value, limited to goodwill balance); IFRS Foundation, IAS 36 Impairment of Assets, paragraphs 6, 18 and 104 (recoverable amount as the higher of fair value less costs of disposal and value in use; impairment allocated first to goodwill)

Correct answer: .

IAS 32 treats a convertible bond like this as a compound financial instrument and requires the issuer to split it at issuance into a liability component, representing the obligation to pay cash, and a residual equity component, representing the conversion option, each initially measured using a specified allocation approach. ASU 2020-06 moved current US GAAP in the opposite direction: it removed the separate accounting models that used to require pulling out a beneficial conversion feature or a cash conversion feature, so an instrument like this one is now generally accounted for as a single liability measured at amortized cost, with no separate equity component recognized, unless some other feature of the instrument independently meets the criteria in the derivatives guidance for bifurcation. The option claiming current US GAAP now mirrors IAS 32's split accounting is wrong because ASU 2020-06 moved US GAAP toward a single-instrument model, away from splitting. The option requiring fair-value-through-profit-or-loss bifurcation under both frameworks is wrong because IAS 32's equity component is not subsequently remeasured at fair value, and current US GAAP's single-liability model does not bifurcate a plain conversion option like this one at all. The option assigning the entire instrument to equity under US GAAP and entirely to a liability under IAS 32 is wrong because it misdescribes both frameworks: current US GAAP still recognizes the instrument as a liability, not equity, and IAS 32 splits the instrument rather than classifying all of it as a liability.

Source: IFRS Foundation, IAS 32 Financial Instruments: Presentation, paragraphs 28-32 (compound financial instruments, split accounting); FASB Accounting Standards Update No. 2020-06, Debt—Debt with Conversion and Other Options (Subtopic 470-20) and Derivatives and Hedging—Contracts in Entity's Own Equity (Subtopic 815-40)

Correct answer: .

Under ASC 740, a tax benefit is recognized only if it is more likely than not, meaning a likelihood of more than 50 percent, that the position will be sustained on its technical merits; because 55 percent clears that threshold here, the entity recognizes a benefit and then measures it as the largest amount of benefit that is greater than 50 percent likely of being realized upon ultimate settlement, a distinct second step from the recognition decision. IFRIC 23 does not use this two-step more-likely-than-not recognition gate at all: whenever there is uncertainty over how a tax treatment will be resolved, the entity reflects the effect of that uncertainty in its taxable profit, tax bases, unused losses, or tax rates by using whichever of the expected value method, a probability-weighted average of possible outcomes, or the most likely amount method better predicts the resolution of the uncertainty, without first asking whether a 50 percent-plus threshold has been cleared. The option asserting an identical two-step, most-likely-amount-only framework under both standards is wrong because IFRIC 23 has no recognition threshold step and allows either measurement method depending on which better predicts the outcome. The option describing IFRIC 23's threshold as matching ASC 740's more-likely-than-not test is wrong because IFRIC 23 does not impose a binary recognition threshold before reflecting the uncertainty at all. The option claiming technical merits are irrelevant under ASC 740 and that IFRIC 23 waits for the statute of limitations is wrong because ASC 740's entire recognition test turns on the position's technical merits, and IFRIC 23 requires reflecting uncertainty in the current period rather than deferring recognition until the statute of limitations expires.

Source: FASB Accounting Standards Codification ASC 740-10-25 and ASC 740-10-30 (more-likely-than-not recognition threshold; measurement at the largest amount more than 50 percent likely of being realized); IFRS Interpretations Committee, IFRIC 23 Uncertainty over Income Tax Treatments, paragraphs 9-11 (measurement using the expected value or most likely amount method)

Correct answer: .

ASC 480-10-S99 requires an SEC registrant to present preferred shares redeemable at a fixed or determinable price, at the holder's option, or upon an event outside the issuer's control, in a separate temporary equity or mezzanine equity section of the balance sheet, positioned between liabilities and permanent equity rather than within either category. IAS 32 has no such intermediate category: it classifies financial instruments using a substance-based test asking whether the issuer has an unconditional right to avoid delivering cash or another financial asset, and because this issuer cannot avoid redeeming the shares once the holder exercises its option, IAS 32 would classify the instrument as a financial liability in full rather than placing any part of it in a mezzanine section. The option describing ASC 480-10-S99 as simply classifying the shares as a liability is wrong because the SEC's mezzanine-equity presentation is a distinct third category, not a liability. The option claiming IAS 32 also has a temporary or mezzanine equity concept is wrong because IAS 32's classification is binary between liability and equity, with no intermediate presentation category available. The option treating the shares as ordinary permanent equity under both frameworks is wrong because the redemption feature is exactly what triggers special treatment, mezzanine presentation under US GAAP and liability classification under IAS 32, rather than leaving the shares in permanent equity under either standard.

Source: SEC guidance codified at FASB Accounting Standards Codification ASC 480-10-S99 (classification of redeemable securities as temporary equity); IFRS Foundation, IAS 32 Financial Instruments: Presentation, paragraphs 18-19 (substance-based liability classification; no unconditional right to avoid delivering cash)

Correct answer: .

ASC 326's current expected credit loss model requires an entity to recognize an allowance for the full lifetime expected credit losses on a financial asset like this loan at the moment of initial recognition, regardless of whether any deterioration has occurred, because the standard has no separate lower-loss stage for assets that have not yet shown increased risk. IFRS 9 instead places a newly originated loan with no credit deterioration into Stage 1 of its three-stage general approach, where the entity recognizes only a 12-month expected credit loss allowance, reflecting losses expected from default events possible within the next twelve months; the loan moves to Stage 2, and a lifetime expected credit loss allowance, only if its credit risk has increased significantly since origination, and to Stage 3 if it becomes credit-impaired. The option describing ASC 326 as waiting for a significant increase in credit risk is wrong because that staged trigger belongs to IFRS 9, not to the day-one lifetime model of ASC 326. The option requiring lifetime losses under both frameworks immediately is wrong because IFRS 9's Stage 1 allowance is deliberately limited to a 12-month horizon. The option requiring actual default or non-performing status under either framework is wrong because both standards require a forward-looking allowance well before any actual default occurs, based on expected, not incurred, losses.

Source: FASB Accounting Standards Codification ASC 326-20 (current expected credit losses, lifetime allowance recognized at initial recognition); IFRS Foundation, IFRS 9 Financial Instruments, paragraphs 5.5.1-5.5.5 (three-stage general approach to impairment: 12-month versus lifetime expected credit losses)

Correct answer: .

ASC 805 gives the acquirer no choice: the non-controlling interest must be measured at its acquisition-date fair value, which, combined with the fair value of the consideration transferred for the controlling interest, results in goodwill being recognized on the non-controlling interest's share of the business as well as the controlling interest's share, commonly called the full goodwill method. IFRS 3 instead gives the acquirer an accounting policy choice, made separately for each business combination, to measure the non-controlling interest either at fair value, which produces the same full goodwill outcome as ASC 805, or at the non-controlling interest's proportionate share of the acquiree's identifiable net assets, which produces a smaller amount of goodwill recognized only in respect of the controlling interest, commonly called the partial goodwill method. The option requiring proportionate-share measurement under both frameworks is wrong because ASC 805 does not offer that option at all. The option attributing the policy choice to ASC 805 and a fixed fair-value rule to IFRS 3 is wrong because it reverses which framework is mandatory and which is elective. The option denying that either framework permits fair value measurement of the non-controlling interest is wrong because fair value measurement is not only permitted but required under ASC 805, and is one of the two available elections under IFRS 3.

Source: FASB Accounting Standards Codification ASC 805-20-30 (non-controlling interest measured at fair value); IFRS Foundation, IFRS 3 Business Combinations, paragraph 19 (accounting policy choice, on a transaction-by-transaction basis, between fair value and proportionate share of identifiable net assets)

Correct answer: .

IAS 7 permits a bank overdraft to be included as a negative component of cash and cash equivalents when it is repayable on demand and forms an integral part of the entity's cash management, such as when the balance fluctuates regularly between positive and negative, reflecting the standard's view that such an overdraft functions economically like short-term, on-demand cash management rather than external financing. US GAAP takes a categorically different position: a bank overdraft is treated as a form of short-term financing and presented as a liability, with draws and repayments reported as separate financing activities in the statement of cash flows, and it is never combined with, or netted against, cash and cash equivalents, regardless of how integral it is to the entity's day-to-day cash management. The option requiring financing-liability treatment under both frameworks is wrong because IAS 7 explicitly allows overdrafts meeting its criteria to be included within cash and cash equivalents. The option claiming IAS 7 flatly prohibits including any overdraft in cash equivalents is wrong because IAS 7's own overdraft provision is precisely what allows this inclusion when the stated conditions are met. The option claiming US GAAP allows the same netting IAS 7 permits is wrong because US GAAP's treatment of overdrafts as financing liabilities excluded from cash and cash equivalents does not change based on how integral the facility is to cash management.

Source: IFRS Foundation, IAS 7 Statement of Cash Flows, paragraph 8 (bank overdrafts repayable on demand as a component of cash and cash equivalents); FASB Accounting Standards Codification ASC 305-10 and ASC 230 (bank overdrafts presented as financing liabilities, excluded from cash and cash equivalents)

Correct answer: .

ASC 420 requires each element of a restructuring cost to satisfy its own specific recognition criteria: a liability for one-time termination benefits is recognized once management with the appropriate level of authority has approved the plan and communicated it to employees in sufficient detail that they can determine the type and amount of benefits they will receive, while other exit costs, such as contract termination costs, are recognized separately as each is actually incurred, which often spreads recognition across several periods. IAS 37 instead asks whether a detailed formal restructuring plan has been announced in a way specific enough to create a valid expectation among those affected, employees, customers, and suppliers alike, that the entity will carry out the restructuring; once that constructive obligation arises, the qualifying restructuring costs, including comparable termination benefits, are generally recognized together as a single provision at that time rather than piecemeal as each cost is incurred. The option describing IAS 37 as waiting for actual cash payment and ASC 420 as recognizing everything the instant management merely starts considering the plan is wrong because it misstates both standards' actual triggers, which are the valid-expectation-creating announcement under IAS 37 and the specific communication-to-employees criteria under ASC 420, not cash payment or mere internal deliberation. The option requiring individual written employee acknowledgments under both frameworks is wrong because neither standard conditions recognition on employees personally signing anything. The option describing ASC 420 as triggered by any public announcement to any party is wrong because ASC 420's termination-benefit trigger is specifically communication to the affected employees in sufficient detail, not a general public announcement.

Source: FASB Accounting Standards Codification ASC 420-10-25 (recognition criteria for one-time termination benefits, communication date); IFRS Foundation, IAS 37 Provisions, Contingent Liabilities and Contingent Assets, paragraphs 72 and 78 (constructive obligation for restructuring arising from a detailed formal plan and valid expectation)

Correct answer: .

ASC 350-40 organizes internal-use software costs into three named stages: costs incurred during the preliminary project stage, while the entity is still evaluating alternatives and requirements, are expensed as incurred like research costs; costs incurred during the application development stage, which begins once management with the relevant authority has authorized and committed to funding the project, are capitalized; and costs incurred during the post-implementation stage, such as training and routine maintenance after the software is placed in service, are expensed again. IAS 38 does not use these three named stages at all; instead, it requires the entity to demonstrate all six of its general development-cost criteria, including technical feasibility, intention and ability to complete and use the asset, and the ability to measure the related expenditure reliably, before any development expenditure, software or otherwise, can be capitalized as an intangible asset. The option claiming IAS 38 uses the same three named stages and the same capitalization trigger point is wrong because IAS 38 has no equivalent preliminary-project or application-development stage terminology; it applies its own six-criteria test instead. The option describing IAS 38 as prohibiting capitalization entirely is wrong because IAS 38 does permit capitalization once its criteria are met, it simply frames the test differently from ASC 350-40's staged approach. The option describing ASC 350-40 as allowing capitalization from the earliest planning discussions with no approval required is wrong because ASC 350-40 specifically requires management authorization and commitment to funding before the application development stage, and therefore capitalization, begins.

Source: FASB Accounting Standards Codification ASC 350-40-25 (preliminary project stage, application development stage, and post-implementation stage for internal-use software); IFRS Foundation, IAS 38 Intangible Assets, paragraphs 57-58 (six criteria for capitalizing development expenditure)

Correct answer: .

ASC 270 adopts an integral view of interim reporting, treating each interim period as an integral part of the annual period, which permits certain costs and revenues that are expected to benefit the entity for the whole year, such as this planned maintenance-shutdown cost, to be allocated across the interim periods that benefit from them rather than reported entirely in the quarter in which they are incurred. IAS 34 instead adopts a discrete view, requiring an entity to recognize and measure income, expenses, assets, and liabilities for an interim period using the same principles it would apply in annual financial statements, as if that interim period were a stand-alone annual reporting period, so a cost like this one is generally recognized in full in the quarter it is incurred rather than smoothed across the year. The option claiming IAS 34 permits the same period-allocation smoothing as ASC 270 is wrong because IAS 34's discrete view is specifically defined by the absence of that kind of cross-period allocation. The option describing ASC 270 as requiring a wholly discrete view identical to IAS 34 is wrong because it is ASC 270's integral view, not a discrete view, that characterizes US GAAP's approach to interim reporting. The option claiming neither standard addresses this issue is wrong because the integral-versus-discrete distinction is the central, explicitly stated difference between how ASC 270 and IAS 34 approach interim financial reporting.

Source: FASB Accounting Standards Codification ASC 270-10-45 (interim period as an integral part of the annual period); IFRS Foundation, IAS 34 Interim Financial Reporting, paragraph 28 (interim period as a discrete accounting period, using the same recognition and measurement principles as annual statements)

Correct answer: .

IAS 20 requires a grant related to an asset, such as this equipment grant, to be recognized in profit or loss on a systematic basis over the periods in which the entity recognizes the depreciation expense on the related asset, presented either as deferred income released to income over the asset's life or as a deduction in arriving at the asset's carrying amount, so the grant income is matched against the depreciation it is meant to offset rather than recognized all at once. Current US GAAP has no single comprehensive standard addressing government grants received by for-profit business entities comparable to IAS 20, so practice varies: preparers commonly analogize to other available guidance, such as a gain-contingency framework, or to grant accounting used in other contexts, rather than following one unified recognition model, which can produce different timing and presentation outcomes from one company to the next. The option claiming a single US GAAP standard mirrors IAS 20 exactly is wrong because no such dedicated, comprehensive standard currently exists for for-profit entities receiving government grants. The option describing IAS 20 as deferring all recognition until the asset is fully depreciated, with immediate full recognition under US GAAP, is wrong because IAS 20 spreads recognition systematically over the asset's life rather than deferring it entirely, and US GAAP's lack of unified guidance does not translate into a rule of immediate full recognition. The option requiring recognition entirely within equity under both frameworks is wrong because IAS 20 explicitly recognizes grant income through profit or loss, not directly in equity.

Source: IFRS Foundation, IAS 20 Accounting for Government Grants and Disclosure of Government Assistance, paragraphs 12 and 24 (systematic recognition in profit or loss; deferred income or deduction from asset presentation); FASB Accounting Standards Codification has no dedicated Topic addressing government grants received by for-profit business entities as of this reporting period

Correct answer: .

Under US GAAP, ASC 230 leaves no room for choice on these items: interest paid and interest received are always operating cash flows because they enter into the determination of net income, and dividends received are likewise operating, while dividends paid to the reporting entity's own shareholders are always a financing outflow because they represent a distribution of profits to providers of equity capital, not a cost incurred to generate income. IAS 7 takes a different, more principles-based approach that gives preparers an accounting-policy choice: interest paid may be presented as an operating activity because it affects profit or loss, or alternatively as a financing activity because it is a cost of obtaining financial resources; interest received and dividends received may be presented as operating or investing; and dividends paid may be presented as financing, a cost of obtaining capital, or operating, to help users judge whether operating cash flows are sufficient to fund dividends — whichever classification is chosen must then be used consistently period to period. The claim that IFRS is the rigid framework and US GAAP the flexible one reverses the actual relationship. Forcing every item into financing ignores that both frameworks treat interest and some dividend flows as operating in at least one permitted presentation. Claiming the two frameworks always converge on investing and financing ignores that US GAAP routes interest and dividends received through operating, not investing.

Source: IFRS Foundation, IAS 7 Statement of Cash Flows, paragraphs 31, 33-34 (classification choice for interest and dividends, applied consistently); FASB ASC 230-10-45 (fixed classification: interest paid/received and dividends received as operating; dividends paid as financing)

Correct answer: .

IFRS 5 defines a discontinued operation as a component that has been disposed of, or is classified as held for sale, and represents a separate major line of business or geographical area of operations, or is part of a single coordinated plan to dispose of one, or is a subsidiary acquired exclusively with a view to resale; a single regional sales office that is a small slice of a broader distribution network does not meet that bar. ASC 205-20, following the 2014 FASB update narrowing the old discontinued-operations rules, asks a related but conceptually different question: whether the disposal represents a strategic shift that has, or will have, a major effect on the entity's operations and financial results, a test framed around the significance of the strategic change rather than around whether the disposed piece was itself a major line of business or geography. On facts this modest, both tests point the same direction, but they are not the same test, and in other fact patterns, such as disposing of an entire minor product line that happens to meet IFRS's major-line-of-business description without amounting to a US GAAP strategic shift, they can diverge, which is why more disposals have been found to qualify as discontinued under IFRS in practice. Claiming both frameworks apply the identical major-line-of-business test collapses two genuinely different legal tests into one. Claiming any disposal of a location automatically qualifies ignores both frameworks' explicit thresholds. Claiming IFRS 5 has no threshold at all, or that ASC 205-20 bans the presentation entirely, misstates both standards.

Source: IFRS Foundation, IFRS 5 Non-current Assets Held for Sale and Discontinued Operations, paragraph 32; FASB ASU 2014-08 / ASC 205-20-45-1B (strategic-shift-with-major-effect threshold)

Correct answer: .

The 2020 and 2022 amendments to IAS 1, effective for annual periods beginning on or after 1 January 2024, clarify that the classification of a liability as current or non-current depends solely on the rights that exist at the reporting date; if the lender had an unconditional right at that date to demand repayment within twelve months because of the breach, the loan is current, and a waiver the lender grants afterward, however promptly, does not retroactively change the rights that existed at the reporting date, because a waiver is treated as a modification of the loan's terms taking effect only when granted. US GAAP takes a materially different, more forgiving approach under ASC 470-10-45: a loan that is callable due to a covenant breach at the reporting date can still be classified as non-current if the lender has, before the financial statements are issued or available to be issued, waived the right to demand repayment for a period of more than twelve months from the reporting date, and it is not probable the entity will breach a provision again within that grace period. This is one of the more significant remaining points of divergence between the two frameworks on liability classification. Claiming both frameworks allow the waiver to cure classification ignores IAS 1's explicit reporting-date-only test. Claiming neither framework allows any post-reporting-date event to matter is wrong because ASC 470 explicitly does allow it. Claiming the 2024 IAS 1 amendments made no difference here ignores that clarifying this exact rights-at-the-reporting-date principle was the amendments' central purpose.

Source: IFRS Foundation, IAS 1 Presentation of Financial Statements (as amended by Classification of Liabilities as Current or Non-current, 2020 and 2022), paragraphs 72A-76; FASB ASC 470-10-45-2 through 45-3 (waiver/grace-period cure provision)

Correct answer: .

IFRS 9 gives an entity a genuine, instrument-by-instrument choice for an equity investment that is not held for trading: measure it at fair value through profit or loss by default, or make an irrevocable election at initial recognition to present fair value changes in other comprehensive income instead; under that OCI election, gains and losses accumulate in equity and are never reclassified, or recycled, to profit or loss, even when the investment is eventually sold, and dividends received are still recognized in profit or loss. US GAAP moved in the opposite direction: ASU 2016-01 eliminated the old available-for-sale category for most equity securities and now generally requires equity investments to be measured at fair value with all changes, realized and unrealized, running through net income, subject only to a narrow measurement-alternative exception for equity securities without a readily determinable fair value. Claiming both frameworks force everything through profit or loss or net income ignores IFRS 9's OCI election entirely. The option that reverses which framework offers the election misstates which standard changed in 2016. Claiming both frameworks permit the OCI election is wrong because current US GAAP eliminated that option for equity securities generally.

Source: IFRS Foundation, IFRS 9 Financial Instruments, paragraphs 5.7.5-5.7.6 (irrevocable FVOCI election for equity instruments, no recycling); FASB ASU 2016-01 / ASC 321-10-35 (fair value through net income for equity securities)

Correct answer: .

IFRS 2 treats a graded-vesting award with only a service condition as, in substance, several separate awards layered on top of each other, one third vesting after one year, another third after two years, and the last third after three years, and requires the fair value of each tranche to be recognized over its own vesting period, which produces a front-loaded, accelerated expense pattern because the first tranche is fully expensed over just one year. ASC 718 instead gives US preparers a genuine accounting-policy choice for awards subject only to a service condition: they may use that same graded-vesting, tranche-by-tranche method, or they may instead recognize the total grant-date fair value on a straight-line basis over the entire three-year requisite service period, producing a smoother, less front-loaded expense pattern; that straight-line election is not available, however, once an award also carries a performance or market condition, where graded attribution becomes mandatory even under ASC 718. The option reversing which framework mandates which method misstates both standards. Claiming both frameworks mandate straight-line ignores IFRS 2's mandatory graded approach entirely. Claiming neither framework permits graded attribution ignores that IFRS 2 requires it and ASC 718 allows it.

Source: IFRS Foundation, IFRS 2 Share-based Payment, Appendix B / IG Example 11 (graded vesting treated as multiple awards); FASB ASC 718-10-35-8 (accounting policy choice between graded and straight-line attribution for service-condition-only awards)

Correct answer: .

IAS 1 has, for as long as it has governed the presentation of financial statements, prohibited entities from presenting any items of income or expense as extraordinary items, either on the face of the statement of comprehensive income or in the notes; unusual or infrequent items are instead presented and described within the ordinary structure of the income statement, with separate disclosure of their nature and amount where material. US GAAP historically allowed a narrow extraordinary item classification for events that were both unusual in nature and infrequent in occurrence, requiring separate presentation net of tax below income from continuing operations, but the FASB found that qualifying events had become extremely rare while the analysis of whether an item qualified consumed disproportionate preparer and auditor effort, so ASU 2015-01 eliminated the concept for fiscal years, and interim periods within those years, beginning after December 15, 2015, a change the FASB explicitly framed as aligning US GAAP more closely with IAS 1's long-standing prohibition. The option reversing which framework historically permitted the classification misstates the history. Claiming neither framework ever recognized the concept ignores US GAAP's pre-2015 practice. Claiming US GAAP still requires the classification today is incorrect since ASU 2015-01 eliminated it outright.

Source: IFRS Foundation, IAS 1 Presentation of Financial Statements, paragraph 87; FASB ASU 2015-01, Income Statement—Extraordinary and Unusual Items (Subtopic 225-20), effective for fiscal years beginning after December 15, 2015

Correct answer: .

IAS 19, since its 2011 amendment eliminated the corridor approach entirely, requires an entity to recognize the full amount of a period's remeasurements, actuarial gains and losses on the obligation together with the difference between actual and expected return on plan assets, immediately and in full in other comprehensive income, and explicitly bars ever reclassifying that amount to profit or loss in a subsequent period, so it permanently remains in equity. ASC 715 takes a substantially more flexible approach: an employer may recognize actuarial gains and losses immediately in net income as they arise, or, as most preparers do, defer them in accumulated other comprehensive income and amortize the cumulative unrecognized amount into net periodic benefit cost over the average remaining service period of active employees, using at minimum the corridor method, amortizing only the excess over 10 percent of the greater of the beginning obligation or the market-related value of plan assets, effectively smoothing volatility into future income statements rather than absorbing it all in OCI permanently. Claiming both frameworks require immediate profit-or-loss recognition ignores both IAS 19's mandatory OCI routing and ASC 715's deferral option. The option reversing which framework prohibits deferral misstates both standards. Claiming a shared 10 percent corridor is wrong because IAS 19 no longer uses a corridor at all.

Source: IFRS Foundation, IAS 19 Employee Benefits (as amended 2011), paragraphs 57(d), 120-123 (remeasurements in OCI, no recycling); FASB ASC 715-30-35 (corridor amortization method and immediate-recognition alternative)

Correct answer: .

US GAAP under ASC 810 maintains two separate, parallel consolidation frameworks: the voting interest model, which looks at majority voting rights for most operating entities, and a distinct variable interest entity model that applies instead whenever an entity exhibits VIE characteristics, most commonly insufficient equity investment at risk for the entity to finance its activities without additional subordinated support, or where the equity holders as a group lack the typical characteristics of a controlling financial interest; under the VIE model, the reporting entity that has both the power to direct the VIE's most significant economic activities and the obligation to absorb losses or right to receive benefits that could be significant to the VIE is deemed the primary beneficiary and must consolidate it. IFRS 10 dispenses with this two-tier structure altogether and applies one single control model to every investee, structured or not: an investor consolidates when it has power over the investee, exposure or rights to variable returns from its involvement, and the ability to use its power to affect the amount of those returns, a broader concept that also incorporates de facto control and potential voting rights, such as options, in ways the US voting-interest model generally does not. The option describing a single shared test for both frameworks ignores US GAAP's distinct VIE model. The option that swaps which framework has the two-tier structure misstates the actual arrangement. The option denying either framework has a special model for structured entities ignores the VIE model's entire purpose.

Source: FASB ASC 810-10-15 (voting interest model and variable interest entity model); IFRS Foundation, IFRS 10 Consolidated Financial Statements, paragraphs 5-9 (single control model: power, variable returns, linkage)

Correct answer: .

ASC 410 requires an asset retirement obligation to be discounted using a credit-adjusted risk-free rate: preparers start from a risk-free rate, typically derived from the yield curve for government securities with a maturity matched to the expected settlement timing, and then adjust it for the effect of the entity's own credit standing, so a company with weaker credit uses a higher discount rate, and therefore recognizes a smaller initial liability, than an otherwise identical company with stronger credit. IAS 37 takes a deliberately different approach: the discount rate must be a pre-tax rate reflecting current market assessments of the time value of money and the risks specific to the liability, but the standard is explicit that this rate must not reflect the risk that the entity itself will fail to settle the obligation, meaning the company's own credit standing, or non-performance risk, is excluded from the rate entirely, leaving IAS 37's rate closer to a pure risk-free rate adjusted only for liability-specific, not entity-specific, risk. Claiming both frameworks use an identical credit-adjusted rate ignores IAS 37's explicit exclusion of non-performance risk. The option reversing which framework includes credit risk misstates both standards. Denying any credit adjustment under either framework ignores ASC 410's explicit credit adjustment.

Source: FASB ASC 410-20-25 and 410-20-30 (credit-adjusted risk-free rate); IFRS Foundation, IAS 37 Provisions, Contingent Liabilities and Contingent Assets, paragraph 47 (rate excludes risks for which cash flows have been adjusted and non-performance risk)

Correct answer: .

IAS 37 treats a contingent asset as recognizable once the realization of the related economic benefit becomes virtually certain; at that point, the standard reasons, the item is no longer appropriately regarded as contingent at all, and it is recognized as an asset in the financial statements, with disclosure required at the lower probable threshold. ASC 450-30 applies a markedly more conservative rule to gain contingencies: a gain is not recognized in the financial statements until it is realized, meaning cash or a claim to cash has actually been received or become legally enforceable, or realizable, meaning an asset is readily convertible to a known amount of cash such as having an active market with a quoted price, so even a gain lawyers regard as virtually certain, but that has not yet resulted in cash or an enforceable right, remains unrecognized, disclosed only carefully to avoid implying more certainty than the standard permits. This makes the reporting outcome on these identical facts genuinely different between the two frameworks: an asset under IAS 37, but no recognized asset under ASC 450-30. Claiming both frameworks share the same recognition threshold ignores this documented divergence. Claiming neither framework allows recognition or disclosure ignores IAS 37's explicit virtually-certain recognition and probable-level disclosure. The option reversing which framework is stricter misstates both standards.

Source: IFRS Foundation, IAS 37 Provisions, Contingent Liabilities and Contingent Assets, paragraphs 33, 35 (contingent asset recognized once virtually certain); FASB ASC 450-30-25 (gain contingencies recognized only when realized or realizable)

Correct answer: .

IFRS 16 retains only two lessor classifications, finance and operating, carried over largely unchanged from the superseded IAS 17 lease standard; it does not reproduce ASC 842's three-way split. Under ASC 842, a lease is classified as sales-type when the lessor is substantively selling the underlying asset and recognizes any dealer's profit at commencement, and as direct financing when the lessor is purely financing a transfer of control without a dealer's margin. IFRS 16 folds both of those economic situations into its single finance-lease category, applying essentially the same recognition pattern, derecognizing the underlying asset, recognizing a net investment in the lease, and splitting receipts between interest income and principal, whether or not the lessor is a dealer; it identifies a lessor as a manufacturer or dealer only to require separate disclosure of selling profit, not to create a different classification bucket. The option describing a mere renaming is wrong because direct financing and operating leases are governed by different recognition models, not interchangeable labels. The option inventing a fourth, related-party category is wrong because IFRS 16's lessor classification turns on risk-and-reward transfer, not counterparty relationship. The option claiming a single undifferentiated category is wrong because IFRS 16 still requires lessors to distinguish finance leases from operating leases; it only eliminates the further split within the finance category.

Source: FASB Accounting Standards Codification ASC 842 Leases (lessor classification: sales-type, direct financing, operating); IFRS Foundation, IFRS 16 Leases, paragraphs 61-71 (lessor classification: finance and operating leases only)

Correct answer: .

IFRS 11 draws a binary distinction between a joint operation, where the parties have rights to the arrangement's individual assets and obligations for its individual liabilities, and a joint venture, where the parties instead have rights only to the arrangement's net assets. A party to a joint operation recognizes its own share of each asset, liability, revenue, and expense line directly in its own financial statements, essentially a scaled, line-by-line recognition rather than a single net investment figure. US GAAP has no corresponding joint-operation category or definition; arrangements that are jointly controlled and organized through a separate legal or unincorporated entity are generally accounted for by each investor using the equity method under ASC 323, regardless of whether the underlying contractual rights resemble an IFRS joint operation or joint venture. The option claiming both frameworks reach the equity method by converged reasoning is wrong because it ignores IFRS 11's explicit joint-operation line-item recognition model, which is not an equity-method outcome. The option describing automatic joint-venture treatment under IFRS 11 is wrong because the scenario's rights-to-assets-and-liabilities structure is the defining feature of a joint operation, not a joint venture. The option describing full consolidation under IFRS 11 and mere disclosure under US GAAP is wrong because IFRS 11's joint-operation treatment recognizes only the party's own proportionate share, not the arrangement's assets and liabilities in full, and US GAAP requires on-balance-sheet equity-method recognition, not disclosure alone.

Source: IFRS Foundation, IFRS 11 Joint Arrangements, paragraphs 14-23 (classification as joint operation or joint venture, and resulting accounting); FASB Accounting Standards Codification ASC 323 Investments—Equity Method and Joint Ventures

Correct answer: .

ASU 2018-15 amended ASC 350-40 so that a customer in a hosting arrangement that is a service contract applies the same stage-based capitalization model used for internal-use software: costs in the preliminary-project and post-implementation stages are expensed, but qualifying costs incurred during the application-development stage, such as configuration and customization, are capitalized and then expensed over the term of the hosting arrangement. IFRS has no equivalent standard addressing cloud-hosting implementation costs directly; the IFRS Interpretations Committee's 2021 agenda decision concluded that, because the customer typically only receives a service rather than control of software, these configuration and customization costs should generally be expensed as incurred unless they create a separate asset the customer controls that meets IAS 38's recognition criteria, which is uncommon for standard SaaS implementations. The option claiming full convergence is wrong because the 2018 US GAAP update created broader capitalization, not alignment with IFRS's generally more restrictive expensing outcome. The option describing a right-of-use asset election under IFRS 16 is wrong because a hosting arrangement that is a service contract, by definition, does not convey a lease of an identified software asset, so IFRS 16 does not apply to it. The option claiming both frameworks prohibit all capitalization is wrong because ASC 350-40 explicitly permits and requires capitalization of qualifying application-development-stage costs.

Source: FASB ASU 2018-15, codified at ASC 350-40 (customer's accounting for implementation costs of a hosting arrangement that is a service contract); IFRS Interpretations Committee agenda decision, March 2019 and April 2021 (configuration and customisation costs in a cloud computing arrangement, IAS 38)

Correct answer: .

IAS 29 takes a restatement-based approach: once an economy is judged hyperinflationary, using a practical threshold of cumulative three-year inflation approaching or exceeding 100 percent, the entity restates its own financial statements into the measuring unit current at the reporting date using a general price index, restating non-monetary items for the change in the index while monetary items, already expressed in current purchasing power, are left unrestated. US GAAP has no directly equivalent price-level restatement standard. Instead, ASC 830 addresses a highly inflationary economy, using a similar three-year cumulative threshold, by requiring the subsidiary's functional currency to be treated as that of its parent, so the subsidiary's books are effectively remeasured into the parent's reporting currency using the temporal method, rather than restated for general price-level changes and then translated at the closing rate. The option claiming both frameworks use the same general-price-index restatement is wrong because US GAAP has no such restatement mechanism; it solves the problem through a functional-currency change instead. The option describing automatic deconsolidation under IAS 29 is wrong because operating in a hyperinflationary economy affects measurement, not whether the subsidiary is consolidated at all. The option describing a general-price-index restatement limited to non-monetary liabilities under US GAAP is wrong because US GAAP does not perform price-level restatement in this situation at all.

Source: IFRS Foundation, IAS 29 Financial Reporting in Hyperinflationary Economies, paragraphs 1-3, 8-9, 11-14; FASB Accounting Standards Codification ASC 830 Foreign Currency Matters (highly inflationary economies, functional currency determination)

Correct answer: .

Under ASC 470-20, when bonds are issued with detachable, equity-classified stock warrants for a lump-sum price and both components have determinable fair values, the proceeds are allocated between the two based on their relative fair values, so each component absorbs a proportional share of any discount to the combined fair values. IAS 32 takes a different, residual approach to a compound instrument: the liability component is measured first, at the fair value of a similar liability that carries no conversion or warrant feature, and whatever is left of the proceeds after that liability amount is assigned to equity, without ever separately fair-valuing the equity component itself. The option asserting both frameworks use the same relative-fair-value method is wrong because IAS 32 deliberately avoids a proportional split, measuring the liability first and treating equity as a residual plug. The option claiming ASC 470-20 assigns all proceeds to debt is wrong because that framework explicitly requires a split between debt and warrants whenever both components have determinable fair values. The option reversing which framework measures which component first is wrong because it is IAS 32, not ASC 470-20, that measures a single component, the liability, first and treats the other as a residual; ASC 470-20 values both components independently before allocating proportionally.

Source: FASB Accounting Standards Codification ASC 470-20 Debt—Debt with Conversion and Other Options (allocation of proceeds between debt and detachable warrants); IFRS Foundation, IAS 32 Financial Instruments: Presentation, paragraphs 28-32 (compound financial instruments, residual method)

Correct answer: .

IAS 12 measures deferred tax assets and liabilities at the tax rates expected to apply when the asset is realized or the liability is settled, based on rates and tax laws that have been enacted or substantively enacted by the end of the reporting period, so a rate that has passed all substantive legislative steps but is awaiting a final formality can already be used. ASC 740, by contrast, requires that only a rate that has been enacted, meaning it has completed the full formal legislative process required to become law in that jurisdiction, be reflected in the measurement of deferred tax balances; a change that is merely substantively certain but not yet formally enacted is not used. The option claiming both frameworks accept the substantively-enacted rate is wrong because ASC 740 does not recognize a substantively-enacted threshold at all. The option claiming neither framework permits use of the new rate is wrong because IAS 12 explicitly permits it once substantive enactment is reached. The option swapping which framework applies which standard is wrong because it is IAS 12 that accepts substantive enactment and ASC 740 that insists on full formal enactment, not the reverse.

Source: IFRS Foundation, IAS 12 Income Taxes, paragraph 47 (measurement using enacted or substantively enacted tax rates); FASB Accounting Standards Codification ASC 740 Income Taxes (measurement using enacted tax rates)

Correct answer: .

IAS 20 treats the benefit of a below-market-rate government loan as a government grant: the loan is initially recognized and measured in accordance with the applicable financial instruments standard, meaning at the fair value a market-rate loan would have, and the difference between that fair value and the actual proceeds received is accounted for as a government grant. US GAAP reaches a different outcome because the general requirement to impute interest at a market rate when a loan's stated rate is not a market rate, found in the interest-imputation guidance, contains a scope exception for interest rates that are affected by legal restrictions prescribed by a governmental agency; as a result, a company receiving a below-market government loan does not impute a market rate or separately recognize a grant benefit for the interest-rate concession. The option claiming identical treatment under both frameworks is wrong because US GAAP's scope exception specifically avoids the fair-value-versus-proceeds grant calculation that IAS 20 requires. The option reversing which framework ignores the benefit is wrong because it is US GAAP, not IAS 20, that excludes this situation from imputation. The option claiming neither framework recognizes any benefit is wrong because IAS 20 explicitly requires recognizing one.

Source: IFRS Foundation, IAS 20 Accounting for Government Grants and Disclosure of Government Assistance, paragraph 10A; FASB Accounting Standards Codification ASC 835-30-15-3(e) (scope exception for government-mandated below-market interest rates)

Correct answer: .

IAS 1 establishes a default rule with a built-in exception: an entity presents a classified statement of financial position separating current and non-current assets and liabilities, unless a presentation based on liquidity provides information that is reliable and more relevant, in which case all assets and liabilities are presented broadly in order of liquidity instead; IAS 1 itself expresses no preference for which assets are listed first within either approach. US practice does not offer the same live choice in most cases: SEC Regulation S-X requires a classified balance sheet for most registrants, so the liquidity-order alternative that IAS 1 permits is rarely available or used in practice under US GAAP. The option claiming IAS 1 bars a liquidity-order presentation entirely is wrong because that presentation is explicitly permitted as an exception when more relevant and reliable. The option claiming both frameworks require strict liquidity order is wrong because a classified presentation remains the default, and generally the required, approach under both. The option claiming SEC regulations require liquidity order is wrong because the opposite is true: the classified presentation is the SEC's requirement, not the exception.

Source: IFRS Foundation, IAS 1 Presentation of Financial Statements, paragraphs 60-63; SEC Regulation S-X, Rule 5-02 (classified balance sheet requirement for most registrants)

Correct answer: .

ASC 805-50 gives an acquired company the option, exercisable separately each time a change-in-control event occurs, to elect push-down accounting, under which the acquired company applies the new parent's purchase-price allocation, including any goodwill and fair-value step-ups, directly within its own separate financial statements, and once elected, the election is irrevocable for that event. IFRS has no standard that directly addresses push-down accounting; the IASB considered, and ultimately did not pursue, a comprehensive project on the topic, so whether and how an acquired entity reflects its new parent's acquisition accounting in separate financial statements is left to local regulators and existing general principles, and in practice most subsidiaries reporting under IFRS continue to carry their pre-acquisition historical amounts in their own separate statements. The option claiming neither framework ever permits push-down accounting is wrong because ASC 805-50 explicitly provides this option. The option claiming both frameworks require it automatically is wrong because US GAAP treats it as an election, not a mandate, and IFRS has no such requirement at all. The option reversing which framework mandates and which prohibits push-down accounting is wrong because US GAAP permits, rather than prohibits, the election, and IFRS has no mandate requiring it.

Source: FASB Accounting Standards Codification ASC 805-50-25 (pushdown accounting election); FASB ASU 2014-17, Business Combinations (Topic 805): Pushdown Accounting

Correct answer: .

IFRS 9 requires an issuer to subsequently measure a financial guarantee contract at the higher of two figures combined into a single carrying amount: the loss allowance determined under the expected-credit-loss impairment model, and the amount initially recognized for the guarantee less any cumulative income recognized since inception, so the credit-loss consideration and the original fair-value liability are blended into one number. US GAAP takes a two-track approach instead: the noncontingent, fair-value-based liability recognized at inception under ASC 460 continues to be accounted for, typically amortized into income, on its own track, while the contingent, credit-loss-related component is separately measured and recognized under ASC 326's current expected credit loss model, with the two amounts reported in addition to each other rather than netted into a single higher-of figure. The option claiming both frameworks use a single netted higher-of approach is wrong because that combined approach is specific to IFRS 9; US GAAP keeps the two components apart. The option claiming IFRS 9 keeps the components separate while US GAAP nets them states the rule backwards. The option claiming neither framework requires a credit-loss allowance is wrong because both explicitly require one; they differ only on whether it is combined with the fair-value liability or reported alongside it.

Source: IFRS Foundation, IFRS 9 Financial Instruments, paragraph 4.2.1(c) and 5.5.1 (financial guarantee contract subsequent measurement); FASB Accounting Standards Codification ASC 460 Guarantees and ASC 326-20 (current expected credit losses)