IFRS Concepts & Framework

Why B? And why not the others?

Correct answer: B. Relevance and faithful representation

The Conceptual Framework identifies relevance and faithful representation as the fundamental qualitative characteristics: information cannot be useful to users unless it is both capable of making a difference to their decisions and faithfully represents the substance of what it purports to depict. Comparability, verifiability, timeliness and understandability are enhancing characteristics — they increase the usefulness of information that is already relevant and faithfully represented, but they cannot compensate for information that lacks one of the fundamental characteristics. The option pairing comparability with verifiability names two enhancing characteristics and omits both fundamental ones. The option pairing timeliness with understandability makes the same error. The option pairing relevance with comparability correctly names one fundamental characteristic but incorrectly substitutes an enhancing characteristic for faithful representation, so it does not identify the complete fundamental pair the Framework specifies.

Source: IASB Conceptual Framework for Financial Reporting (2018), Chapter 2, paragraphs 2.4–2.34 (qualitative characteristics of useful financial information)

Why C? And why not the others?

Correct answer: C. As current, because the company did not have an unconditional right to defer settlement for at least twelve months from the reporting date

IAS 1 requires a liability to be classified as non-current only if the entity has the right, at the end of the reporting period, to defer settlement for at least twelve months after that date; all other liabilities are classified as current. A covenant breach at the reporting date, with no waiver in place on or before that date, means the right to defer settlement did not exist at the reporting date — the lender is entitled to demand immediate repayment — so the loan must be classified as current regardless of what happens afterward. The option relying on the original 18-month contractual maturity ignores that the covenant breach overrides the original repayment schedule by giving the lender an immediate demand right at the reporting date itself. The option relying on management's belief that the lender probably will not call the loan is wrong because IAS 1's test is the existence of an unconditional contractual right at the reporting date, not management's expectations about counterparty behaviour. The option proposing a probability-weighted split invents a mechanism IAS 1 does not use for this scenario; classification of the loan is a binary current/non-current determination based on the contractual right that existed at the reporting date, not a proportional allocation.

Source: IAS 1 Presentation of Financial Statements, paragraphs 69, 72A–76 (classification of liabilities as current or non-current; effect of covenant breaches)

Why D? And why not the others?

Correct answer: D. As current, because it will be realised as part of the normal operating cycle even though that cycle exceeds twelve months

IAS 1 classifies assets such as inventories as current when they are expected to be realised, or are held for sale or consumption, in the entity's normal operating cycle — and this applies even when that cycle is not expected to complete within twelve months of the reporting date. The twelve-month period is only used as a default assumption when the entity's normal operating cycle is not clearly identifiable; here the 18-month cycle is clearly identifiable, so it governs instead. The option classifying the inventory as non-current purely because settlement exceeds twelve months applies the default assumption in a case where the standard says the actual operating cycle should be used instead. The option describing an election to use twelve months regardless of the actual cycle invents a free choice that the standard does not offer; the operating cycle is a factual characteristic of the business, not an accounting policy an entity can elect to override. The option proposing a proportional split between current and non-current based on months beyond twelve has no basis in IAS 1, which classifies an asset as current or non-current in full, not by prorating a single balance.

Source: IAS 1 Presentation of Financial Statements, paragraphs 66–68 (classification of assets as current, including the operating cycle exception)

Why A? And why not the others?

Correct answer: A. Refer to the requirements and guidance in IFRS Standards dealing with similar and related issues, and to the definitions and recognition and measurement concepts in the Conceptual Framework

IAS 8 sets out a hierarchy for developing an accounting policy in the absence of a specifically applicable IFRS Standard: management must first refer to, and consider the applicability of, the requirements in IFRS Standards dealing with similar and related issues, together with the definitions, recognition criteria and measurement concepts for assets, liabilities, income and expenses in the Conceptual Framework. Only after that step may management additionally consider the most recent pronouncements of other standard-setting bodies that use a similar conceptual framework, other accounting literature, and accepted industry practice, to the extent these do not conflict with the sources considered first. The option jumping straight to common industry practice skips the required analogy step entirely and lets practice override IFRS-based reasoning. The option invoking prudence as an overriding rule invents a general override that does not exist in IAS 8; prudence is one input to judgement, not a trump card that bypasses the hierarchy. The option placing other standard-setters' pronouncements above analogy to IFRS Standards reverses the actual order in the hierarchy, since those pronouncements are only a secondary source to be considered afterward.

Source: IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors, paragraphs 10–12 (selection and application of accounting policies)

Why B? And why not the others?

Correct answer: B. Not recognised as a liability at 31 December; instead disclosed in the notes as a non-adjusting event

IAS 10 treats dividends declared after the end of the reporting period, but before the financial statements are authorised for issue, as a non-adjusting event: because no present obligation to pay existed at the reporting date, no liability is recognised at that date, and the dividend is instead disclosed in the notes. The option recognising a liability because the dividend relates to that year's profit confuses the period the dividend is drawn from with the period in which the obligation to pay actually arises; a liability can only be recognised once a present obligation exists, which here is after the reporting date. The option conditioning recognition on later shareholder approval at the annual general meeting does not change the analysis for this scenario, since the fact pattern already establishes that no obligation existed at the reporting date regardless of subsequent approval steps, and even a later approval would still be an event after that date. The option recognising a reduction of retained earnings with a restatement of comparatives misapplies the treatment for correcting prior period errors under IAS 8 to a routine subsequent dividend declaration, which is not an error and does not call for restating any prior period.

Source: IAS 10 Events after the Reporting Period, paragraphs 12–13 (dividends declared after the reporting period)

Why C? And why not the others?

Correct answer: C. A provision, measured at the best estimate of the expenditure required to settle the present obligation

IAS 37 requires a provision to be recognised when all three conditions are met: a present obligation exists as a result of a past event, an outflow of economic benefits to settle it is probable, and a reliable estimate can be made of the amount. The scenario satisfies all three — the incident during the year is the past event giving rise to the obligation, counsel assesses the outflow as probable, and a reliable estimate is available — so a provision must be recognised at the best estimate of the settlement amount. The option limiting this to note disclosure describes the treatment for a contingent liability, which applies when an outflow is not probable or a reliable estimate cannot be made; neither limitation applies here since both conditions are satisfied. The option requiring a final, non-appealable judgment before recognising anything ignores that the obligating event is the underlying incident, not the court's eventual ruling, and that IAS 37 recognises obligations based on probability and estimability rather than waiting for legal finality. The option recognising the maximum amount claimed rather than the best estimate misapplies measurement: IAS 37 calls for the best estimate of the expenditure required to settle the obligation, not the highest figure asserted by the counterparty, and deliberately inflating the amount is not what the standard means by exercising caution.

Source: IAS 37 Provisions, Contingent Liabilities and Contingent Assets, paragraphs 14 and 36 (recognition and measurement of provisions)

Why D? And why not the others?

Correct answer: D. Only the finance director's compensation, disclosed by category, because the director is key management personnel; the unrelated supplier is not a related party

The finance director meets IAS 24's definition of key management personnel, since that definition covers persons with authority and responsibility for planning, directing and controlling the entity's activities, so their compensation must be disclosed in total and by category — including short-term benefits, post-employment benefits, and share-based payments. The supplier, by contrast, has no control, joint control, significant influence, or family or key-management link to the entity, and transacts at standard list prices available to any customer, so it does not meet IAS 24's definition of a related party at all, regardless of the fact that ordinary trading occurs. The option treating both as related-party matters wrongly extends the definition to an arm's-length commercial counterparty with no ownership, control or influence connection to the entity. The option flagging only the supplier purchases as always requiring disclosure invents a blanket rule that all purchases are related-party transactions, which is not how IAS 24 defines its scope. The option exempting both wrongly drops key management personnel compensation, which IAS 24 specifically requires to be disclosed precisely because employment and remuneration arrangements with those individuals are within its scope.

Source: IAS 24 Related Party Disclosures, paragraphs 9 and 17 (definition of related party and key management personnel compensation disclosure)

Why A? And why not the others?

Correct answer: A. Twelve months

IAS 1 requires management's going concern assessment to look forward at least twelve months from the end of the reporting period, and this is a floor rather than a ceiling — the standard expects management to extend the assessment further when facts and circumstances, such as heightened economic uncertainty, indicate that a longer horizon is needed to properly evaluate the entity's ability to continue as a going concern. Six months falls short of the minimum period the standard actually specifies. Eighteen months confuses this requirement with a different disclosure obligation — the liquidity risk maturity analysis under IFRS 7 — which serves a different purpose and is not the going concern assessment period set out in IAS 1. The option claiming there is no minimum period ignores the explicit twelve-month floor; management has discretion to look further ahead when warranted, but not to use a shorter period or treat the requirement as entirely open-ended.

Source: IAS 1 Presentation of Financial Statements, paragraph 26 (going concern assessment period)

Why B? And why not the others?

Correct answer: B. Yes, provided the relevant regulatory framework does not prohibit such a departure, and the entity discloses the departure, the reasons for it, and its financial effect

IAS 1's fair presentation override permits departure from a specific IFRS requirement in the extremely rare circumstances where management concludes that compliance would be so misleading that it would conflict with the objective of financial statements in the Conceptual Framework, provided the relevant regulatory framework — normally national law or securities regulation — allows the departure or does not prohibit it. A jurisdiction that neither explicitly permits nor explicitly prohibits departure counts as not prohibiting it, so the override remains available here, but only together with disclosure of the fact of departure, the reasons for it, and its financial effect on each item affected. The option asserting IAS 1 never permits departure under any circumstances is wrong because the standard explicitly provides this override, even though it correctly implies the override is meant to be exceptional rather than routine. The option requiring a formal IFRS Interpretations Committee exemption invents a precondition that does not exist; the override operates through the regulatory-framework test and required disclosures, not through seeking prior approval from the Committee. The option treating management's own conclusion as sufficient with no further disclosure omits the mandatory disclosures IAS 1 requires whenever the override is invoked, which are not optional once the departure is made.

Source: IAS 1 Presentation of Financial Statements, paragraphs 19–23 (departure from a requirement of an IFRS in extremely rare circumstances)

Why C? And why not the others?

Correct answer: C. Prudence is defined as the exercise of caution when making judgements under conditions of uncertainty, and supports neutrality rather than permitting deliberate misstatement

The 2018 Conceptual Framework reinstates prudence as 'the exercise of caution when making judgements under conditions of uncertainty,' and positions it as an element supporting neutrality — itself part of faithful representation — rather than as licence to introduce deliberate bias into financial statements. The IASB was explicit that this reinstated 'cautious prudence' does not permit the deliberate overstatement or understatement of assets, liabilities, income or expenses, since that kind of asymmetric bias would itself undermine neutrality and faithful representation. The option describing prudence as deliberately understating assets or income, or overstating liabilities or expenses, is describing exactly the biased, asymmetric conservatism that the 2018 Framework says prudence does not sanction. The option calling prudence a standalone fundamental qualitative characteristic misstates its place in the Framework's structure: the two fundamental qualitative characteristics remain relevance and faithful representation, and prudence operates underneath neutrality as a supporting concept, not as a separate, higher-ranked characteristic. The option requiring the systematically lowest-profit measurement basis whenever a choice exists would itself be the kind of deliberate asymmetric bias the Framework says cautious prudence does not require or endorse.

Source: IASB Conceptual Framework for Financial Reporting (2018), Chapter 2, paragraphs 2.16 and 2.18 (prudence and neutrality)

Why D? And why not the others?

Correct answer: D. Disclose the contingent asset and a brief description of its nature in the notes, without recognising any asset or income, because realisation is probable but not yet virtually certain

IAS 37 sets a higher recognition threshold for contingent assets than for provisions: a contingent asset is only recognised once realisation of the inflow is virtually certain, at which point it is no longer treated as contingent at all. Where an inflow is merely probable — as here, where counsel assesses recovery as probable but not virtually certain — the standard requires disclosure of the contingent asset and a brief description of its nature, without recognising any asset or income. Both options that recognise an asset or income at year end — whether as separate income or as an offset against the loss — apply the virtually-certain threshold too loosely, treating 'probable' as if it were sufficient, when IAS 37 deliberately sets a stricter bar for assets than the 'probable' threshold used for recognising provisions. The option ignoring the recovery entirely overcorrects in the other direction: a probable inflow that falls short of virtually certain still triggers a disclosure obligation under IAS 37, so complete silence about the claim is not the correct treatment either.

Source: IAS 37 Provisions, Contingent Liabilities and Contingent Assets, paragraphs 31–35 (contingent assets: recognition and disclosure)