A financial controller is preparing a note disclosure under the IASB Conceptual Framework for Financial Reporting. Information about a matter would be highly relevant to users' decisions, but presenting it in a fully comparable, easily verified format across all prior periods would take several weeks longer than the reporting deadline allows. Which pair of qualitative characteristics does the Conceptual Framework identify as fundamental — meaning information must possess both before enhancing characteristics come into play?
AComparability and verifiability
BRelevance and faithful representation
CTimeliness and understandability
DRelevance and comparability
Correct answer: .
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)
At the reporting date, a company has an outstanding bank loan repayable in 18 months. The loan agreement contains a covenant that entitles the lender to demand immediate repayment if breached, and the company was in breach of that covenant at the reporting date. No waiver had been obtained from the lender on or before the reporting date. Under IAS 1, how should the loan be classified in the statement of financial position?
AAs non-current, because the loan's original contractual maturity is 18 months from the reporting date
BAs non-current, provided management believes it is probable the lender will not demand repayment
CAs current, because the company did not have an unconditional right to defer settlement for at least twelve months from the reporting date
DSplit between current and non-current based on the likelihood-weighted probability of the lender calling the loan
Correct answer: .
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)
A manufacturer's normal operating cycle, from raw-material purchase through to cash collection on the resulting sale, is clearly identifiable as 18 months, longer than a standard 12-month period. At the reporting date, the manufacturer holds work-in-progress inventory that will not be sold and converted to cash until 16 months after the reporting date. Under IAS 1, how should this inventory be classified?
AAs non-current, because settlement will not occur within twelve months of the reporting date
BAs non-current, unless the entity elects to use a twelve-month period regardless of its actual operating cycle
CSplit between current and non-current in proportion to the number of months beyond twelve
DAs current, because it will be realised as part of the normal operating cycle even though that cycle exceeds twelve months
Correct answer: .
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)
A company enters into a transaction for which no IFRS Standard specifically prescribes an accounting treatment. Under IAS 8, before considering the most recent pronouncements of other standard-setting bodies that use a similar conceptual framework, what must management do first when developing an accounting policy for this transaction?
ARefer 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
BAdopt whatever policy is most commonly used by other entities in the same industry, regardless of whether an IFRS Standard addresses an analogous issue
CApply the most conservative policy available, since IAS 8 requires prudence to override all other considerations when no specific standard applies
DConsult recent pronouncements of other standard-setting bodies immediately, since IAS 8 places these above analogy to existing IFRS Standards
Correct answer: .
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)
A company's board of directors declares a final dividend on 10 March, several weeks after its 31 December reporting date, and before the financial statements for the year ended 31 December are authorised for issue. No obligation to pay the dividend existed at 31 December. Under IAS 10, how should the dividend be reflected in the financial statements for the year ended 31 December?
ARecognised as a liability at 31 December, because the dividend relates to that year's profit
BNot recognised as a liability at 31 December; instead disclosed in the notes as a non-adjusting event
CRecognised as a liability at 31 December only if the dividend is later approved by shareholders at the annual general meeting
DRecognised as a reduction of retained earnings at 31 December with a corresponding restatement of the prior year's comparative figures
Correct answer: .
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)
At year end, a company is a defendant in a lawsuit arising from an incident that occurred during the year. Legal counsel advises that it is probable the company will lose and be required to pay damages, and is also able to provide a reliable range from which management determines a best estimate of the amount. Under IAS 37, what should the company recognise?
AA contingent liability disclosed only in the notes, because litigation outcomes are inherently uncertain until a court rules
BNothing, because a legal obligation only arises once a final, non-appealable judgment is issued
CA provision, measured at the best estimate of the expenditure required to settle the present obligation
DA provision equal to the maximum amount claimed by the plaintiff, in order to be prudent
Correct answer: .
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)
An entity's finance director, who has authority and responsibility for planning, directing, and controlling the entity's activities, receives a salary, a pension contribution, and a share-based payment award during the year. A separate, unrelated supplier — in which no director or their close family holds any interest, and which has no control, joint control, or significant influence over the entity — sells raw materials to the entity at the same standard market list prices available to all customers. Under IAS 24, which of these must be disclosed as related party information?
ABoth the finance director's compensation and the purchases from the unrelated supplier, since both involve transactions with the entity
BOnly the purchases from the supplier, because purchases of raw materials are always considered related party transactions requiring disclosure
CNeither, because compensation paid under normal employment terms and arm's-length market transactions both fall outside the scope of IAS 24
DOnly the finance director's compensation, disclosed by category, because the director is key management personnel; the unrelated supplier is not a related party
Correct answer: .
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)
When assessing whether the going concern basis of preparation is appropriate, IAS 1 requires management to take into account all available information about the future, covering a period of at least how long from the end of the reporting period, with a longer period considered if circumstances warrant?
ATwelve months
BSix months
CEighteen months, matching the period commonly used for liquidity risk maturity analysis under IFRS 7
DThere is no minimum period specified; management may use whatever period it judges appropriate
Correct answer: .
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.
Management believes that complying with a specific presentation requirement in an IFRS Standard would, in an unusual and extremely rare scenario, be so misleading that it would conflict with the objective of financial statements set out in the Conceptual Framework. The entity's jurisdiction neither explicitly permits nor explicitly prohibits departing from an IFRS requirement in such circumstances. Under IAS 1, may the entity depart from the requirement?
ANo — IAS 1 never permits departure from an IFRS requirement under any circumstances, however misleading compliance would be
BYes, 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
CYes, but only after first obtaining a formal exemption granted by the IFRS Interpretations Committee
DYes, automatically, since management's own conclusion that compliance would be misleading is sufficient on its own, with no further disclosure required once the departure is made
Correct answer: .
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)
The IASB's 2018 Conceptual Framework reintroduced explicit reference to 'prudence' after the concept had been removed from the 2010 framework. Which statement correctly describes how the 2018 Conceptual Framework defines and positions this concept?
APrudence means deliberately understating assets or income, or overstating liabilities or expenses, to protect users from overly optimistic reporting
BPrudence is a standalone fundamental qualitative characteristic, ranked above relevance and faithful representation
CPrudence is defined as the exercise of caution when making judgements under conditions of uncertainty, and supports neutrality rather than permitting deliberate misstatement
DPrudence requires that, whenever a transaction could be measured on more than one acceptable basis, the entity must always select the basis that produces the lowest reported profit
Correct answer: .
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)
A company has filed an insurance claim following a warehouse fire. At year end, in-house legal counsel assesses that recovery from the insurer is probable but not virtually certain. Under IAS 37, how should the company account for the potential insurance recovery at year end?
ARecognise the expected recovery as an asset and as income in profit or loss, since a probable inflow is enough to recognise a contingent asset
BRecognise the expected recovery as an asset, but only as a reduction of the related loss rather than as separate income
CIgnore the potential recovery entirely, since contingent assets are never referred to anywhere in the financial statements until cash is actually received
DDisclose 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
Correct answer: .
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)
Under the IASB's 2018 Conceptual Framework for Financial Reporting, which of the following correctly states the definition of an asset?
AA present economic resource controlled by the entity as a result of past events
BA resource controlled by the entity as a result of past events from which future economic benefits are expected to flow to the entity
CA resource for which it is probable that future economic benefits will flow to the entity and whose cost or value can be measured with reliability
DAny right or other resource acquired by the entity in exchange for consideration, regardless of whether the entity currently controls that resource
Correct answer: .
The 2018 Conceptual Framework defines an asset as a present economic resource controlled by the entity as a result of past events, with an economic resource itself defined as a right that has the potential to produce economic benefits. This wording deliberately replaced the earlier approach because describing an asset by reference to 'expected' future flows blurred the definition with the separate question of how probable those flows are. The option referring to a resource from which benefits 'are expected to flow' states the superseded 2010-framework wording, which the IASB specifically dropped because expectation language belongs to recognition and measurement, not to whether something meets the definition of an asset at all. The option requiring that a flow be 'probable' and reliably measurable describes the old recognition criteria that used to sit alongside the asset definition, not the definition itself, and both of those thresholds were removed from the recognition test in 2018 as well. The option requiring acquisition 'in exchange for consideration' invents a cost-based precondition the definition does not contain, and its allowance for the entity to lack control directly contradicts the requirement that the resource be controlled by the entity.
Source: IASB Conceptual Framework for Financial Reporting (2018), Chapter 4, paragraphs 4.3-4.4 (definition of an asset and economic resource)
The IASB's 2018 Conceptual Framework revised the definition of a liability. Which option correctly states both that definition and how the Framework describes the 'obligation' embedded within it?
AA present obligation of the entity, arising from past events, the settlement of which is expected to result in an outflow of resources embodying economic benefits
BA present duty to make a payment of cash or another financial asset to another party, evidenced by a binding contract signed by both parties
CA present obligation of the entity to transfer an economic resource as a result of past events, where an obligation is a duty or responsibility that the entity has no practical ability to avoid
DA possible obligation whose existence will be confirmed only by the occurrence of one or more uncertain future events not wholly within the entity's control
Correct answer: .
The 2018 Conceptual Framework defines a liability as a present obligation of the entity to transfer an economic resource as a result of past events, and it characterises the obligation itself as a duty or responsibility that the entity has no practical ability to avoid. That second phrase was added to give a workable test for identifying when an obligation truly exists, including constructive obligations, rather than relying on expectation language. The option describing settlement as 'expected to result in an outflow of resources embodying economic benefits' is the superseded 2010-framework wording, dropped for the same reason the equivalent asset language was dropped: expectation of a flow is a separate question from whether the definition is met. The option limiting liabilities to duties evidenced by a signed, binding contract is far too narrow, since it would exclude constructive obligations arising from an entity's own established practices or published policies, which the Framework and IAS 37 both recognise as capable of creating an obligation despite the absence of any contract. The option describing a possible obligation confirmed only by uncertain future events describes a contingent liability, which is explicitly distinguished from a liability precisely because no present obligation yet exists.
Source: IASB Conceptual Framework for Financial Reporting (2018), Chapter 4, paragraphs 4.26, 4.29-4.31 (definition of a liability and of an obligation)
The 2010 Conceptual Framework included a probability threshold and a reliable-measurement threshold as separate recognition criteria for assets and liabilities. Under the 2018 Conceptual Framework, how are recognition decisions made instead?
ABy retaining the probability threshold but removing the reliable-measurement threshold, since measurement uncertainty is now addressed solely through disclosure
BBy recognising an asset or liability only if doing so provides users with relevant information about it and a faithful representation of it, treating factors such as existence uncertainty and a low probability of an economic-benefit flow as circumstances that may make recognition less useful rather than as separate pass/fail thresholds
CBy requiring that any item meeting the definition of an asset or liability be recognised automatically, regardless of measurement uncertainty or the probability of an economic-benefit flow
DBy replacing the probability and reliable-measurement thresholds with a single 'virtually certain' threshold applied uniformly across all IFRS Standards
Correct answer: .
The 2018 Conceptual Framework dropped the separate probability and reliable-measurement gates and instead recognises an asset, liability, or related income or expense only when doing so gives users relevant information about it and a faithful representation of it. Existence uncertainty and a low probability that economic benefits will flow are no longer framed as thresholds an item must clear before recognition is even considered; instead they are treated as circumstances that can mean recognition would not be the most relevant information, in which case disclosure may serve users better. The option retaining probability while dropping only the measurement threshold misstates the change, since both discrete thresholds were removed together as a pair, not traded off against each other. The option requiring automatic recognition of anything meeting the definitions ignores that the Framework explicitly contemplates cases, such as high existence uncertainty or low probability, where recognition would not provide useful information and disclosure is preferred instead. The option describing a single uniform 'virtually certain' threshold invents a framework-wide replacement rule; individual Standards retain their own specific thresholds for particular items, but the Conceptual Framework itself did not impose one uniform figure across all of them.
Source: IASB Conceptual Framework for Financial Reporting (2018), Chapter 5, paragraphs 5.9, 5.12-5.25 (recognition criteria and factors affecting relevance)
The Conceptual Framework identifies two broad categories of measurement basis available for assets and liabilities. Which option correctly describes them and how they relate to entry and exit values?
ANominal cost and real cost, where nominal cost is unadjusted for inflation and real cost is adjusted for inflation
BFair value and value in use only, since the Framework treats these as the sole permissible bases for measuring any asset
CBook value and market value, where book value is always an entry value and market value is always an exit value
DHistorical cost and current value, where current value further divides into fair value (a market-participant, exit-value measure) and value in use or fulfilment value (an entity-specific, exit-value measure), while current cost is an entry-value measure
Correct answer: .
The Conceptual Framework groups measurement bases into historical cost and current value, and it further splits current value into measures based on market-participant assumptions (fair value, an exit value) and measures based on entity-specific assumptions (value in use for assets or fulfilment value for liabilities, also exit values), while treating current cost as an entry-value measure. The Framework is explicit that IFRS Standards adopt this mixed set of bases rather than a single one, because no single basis provides the most relevant information in every circumstance. The option describing 'nominal cost' and 'real cost' invents terminology the Framework does not use; inflation adjustment is not the organising distinction it draws between measurement bases. The option limiting measurement to fair value and value in use alone wrongly excludes historical cost and current cost, and wrongly asserts these two are the only bases permitted, when the Framework describes a broader mixed-measurement approach. The option using 'book value' and 'market value' substitutes informal terms not found in the Framework and incorrectly assumes book value is always an entry value, when historical cost — the actual entry-value example the Framework gives — is not equivalent to whatever amount happens to be carried in the books under any measurement basis.
Source: IASB Conceptual Framework for Financial Reporting (2018), Chapter 6, paragraphs 6.4-6.14 (measurement bases: historical cost and current value)
A company nets a financial asset owed to it by one counterparty against a financial liability it owes to a different counterparty, presenting only the net amount in its statement of financial position, on the basis that it expects to settle both amounts around the same time. No IFRS Standard specifically requires or permits offsetting in this situation. Under IAS 1, is this presentation permitted?
ANo — IAS 1 prohibits offsetting assets and liabilities, or income and expenses, unless another IFRS Standard specifically requires or permits it
BYes, because presenting the net amount always provides more relevant information about the entity's exposure than presenting the gross amounts separately
CYes, provided the entity discloses both the gross amounts and the net amount together in the notes
DNo, but only because the two amounts are owed to and by different counterparties; offsetting would otherwise be permitted between amounts owed to and by the same counterparty without any further condition
Correct answer: .
IAS 1 establishes offsetting as prohibited by default: an entity shall not offset assets and liabilities, or income and expenses, unless offsetting is specifically required or permitted by an IFRS Standard. Because no Standard authorises offsetting on these facts, presenting only the net amount is not permitted regardless of any expectation about settlement timing. The option claiming net presentation is 'always' more relevant gets the default backwards — the starting position under IAS 1 is that gross presentation is required unless a Standard says otherwise, precisely because netting can obscure the separate asset and liability exposures. The option suggesting that disclosing both gross and net figures in the notes cures the problem misunderstands that offsetting is a presentation issue: showing a net figure on the face of the statement while relegating the gross figures to a footnote does not comply with a rule about how the primary statements themselves must be presented. The option focused on the counterparties being different implies that offsetting would automatically be fine between amounts owed to and by the same counterparty, but the financial-instrument offsetting criteria in IFRS require both an enforceable legal right of set-off and an intention to settle net or simultaneously — same-counterparty status alone does not satisfy those conditions either.
Source: IAS 1 Presentation of Financial Statements, paragraph 32 (offsetting)
A company determines that several minor expense items are, in aggregate, immaterial, but that two of them are of a clearly different nature from the rest: a small litigation settlement cost and a small foreign-exchange loss. To save space, the company folds both of these into a single catch-all 'miscellaneous expense' line together with numerous minor supply-purchase items of a similar nature to each other. Under IAS 1, is this presentation appropriate?
AYes — IAS 1 permits any items assessed as immaterial to be freely aggregated together in any combination, regardless of their nature or function
BYes — materiality is assessed only at the level of the combined total, so once that total is confirmed immaterial no further presentation requirement applies
CNo — combining items of a clearly dissimilar nature or function together risks obscuring material information and does not reflect the presentation IAS 1 intends, which calls for separate presentation of dissimilar items and warns against obscuring information through inappropriate aggregation
DNo — but only because the litigation settlement, as a legal matter, must always be presented as its own separate line item on the face of the statement of profit or loss regardless of materiality
Correct answer: .
IAS 1 requires an entity to present separately each material class of similar items and to present items of a dissimilar nature or function separately unless they are immaterial, and it further states that an entity shall not reduce the understandability of its financial statements by obscuring material information with immaterial information or by aggregating items that have different natures or functions. Folding a litigation cost and a foreign-exchange loss — items with clearly different natures — into the same line as unrelated minor supply purchases is exactly the kind of aggregation the standard warns can obscure information, so this presentation is not appropriate. The option treating immaterial items as freely combinable in any grouping ignores that IAS 1 organises presentation around the nature and function of items, not merely around a materiality cut-off applied without regard to what is being combined. The option assessing materiality only at the combined-total level skips the separate requirement about the nature and function of the items being aggregated, which applies independently of whether the resulting total happens to be immaterial. The option insisting the litigation cost must always appear as its own line item on the face of the statement overstates the rule; IAS 1's concern here is about not obscuring dissimilar items through inappropriate aggregation, not a blanket mandate that every legal cost be a standalone face line regardless of materiality.
Source: IAS 1 Presentation of Financial Statements, paragraphs 29-30A (aggregation of similar items and dissimilar items; obscuring material information)
A company depreciates a machine over an estimated 10-year useful life. After 4 years, new information indicates the machine will in fact only remain usable for a further 4 years (8 years in total), so the company revises the depreciation charge for the remaining years accordingly, without restating the depreciation already charged in the first 4 years. Under IAS 8, how is this change classified and applied?
AAs a correction of a prior period error, requiring retrospective restatement of the financial statements for the first 4 years
BAs a change in accounting estimate, applied prospectively so that only the current and future periods' depreciation charges are affected
CAs a change in accounting policy, requiring retrospective application as if the 8-year useful life had been used from the start
DAs a change in accounting policy, but applied prospectively, because retrospective application of a policy change is never permitted under IAS 8
Correct answer: .
Revising an asset's estimated useful life in light of new information is a change in accounting estimate under IAS 8, and changes in accounting estimate are applied prospectively — only the current and future periods' depreciation charges change, while amounts already recognised in earlier periods are left untouched. The option treating this as a prior period error is wrong because nothing about the original 10-year estimate was mistaken given the information available at the time; a later change in circumstances or better information does not turn a reasonable earlier estimate into an error requiring restatement. The option treating this as a change in accounting policy requiring full retrospective restatement misclassifies the type of change altogether — a revised useful-life estimate is not a change in the method or basis used to account for a class of transactions, which is what a policy change involves, so the retrospective-application requirement that attaches to policy changes does not apply here. The option that reaches the correct prospective treatment but justifies it by claiming retrospective application of a policy change is 'never permitted' is wrong on that reasoning, since IAS 8 does require retrospective application for a genuine change in accounting policy unless it is impracticable to determine the effects.
Source: IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors, paragraphs 32, 36-38 (accounting for changes in accounting estimates; prospective application)
A company currently measures a class of property using the cost model permitted by IAS 16, and management wants to switch to the revaluation model purely as a matter of preference, with no new IFRS requirement compelling the change and no change in the entity's circumstances. Under IAS 8, is this voluntary change in accounting policy permitted, and if so, on what condition?
AIt is never permitted, because voluntary changes in accounting policy are prohibited outright once a policy has first been applied
BIt is permitted automatically, because management is always free to choose between any of the accounting policies allowed by an IFRS Standard at any time, without further justification
CIt is permitted only if a majority of the entity's shareholders formally approve the change at a general meeting
DIt is permitted only if the change results in the financial statements providing reliable and more relevant information about the effects of transactions, other events or conditions on the entity's financial position, financial performance or cash flows
Correct answer: .
IAS 8 permits an entity to change an accounting policy voluntarily only if the change results in the financial statements providing reliable and more relevant information about the effects of transactions, other events or conditions on the entity's financial position, financial performance or cash flows; management must be able to justify the switch on that basis, and the reasons must be disclosed. The option treating voluntary policy changes as prohibited outright is wrong because IAS 8 explicitly permits them under that condition; a policy is not frozen forever simply because it has been applied once. The option treating the change as automatically permitted with no further justification ignores that IAS 8 conditions voluntary changes on demonstrating improved reliability and relevance, not on management's unconstrained preference alone. The option requiring formal shareholder approval at a general meeting invents a governance mechanism that IAS 8 does not impose; the standard's test is about the quality of the resulting information and the required disclosures, not a shareholder vote.
Source: IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors, paragraphs 14-16 (selection and application of accounting policies; voluntary changes)
At the reporting date, a company holds a trade receivable from a customer, assessed at that date as fully collectible based on the information then available. Three weeks after the reporting date, but before the financial statements are authorised for issue, the customer files for bankruptcy because of financial difficulties that had already existed at the reporting date. Under IAS 10, how should the company treat this development?
AAs a non-adjusting event, disclosed in the notes only, because the bankruptcy filing itself occurred after the reporting date
BAs a non-adjusting event, with no disclosure required, because the receivable was assessed as fully collectible at the reporting date based on the best information available at that time
CAs an adjusting event, because the bankruptcy provides evidence of conditions that already existed at the reporting date, requiring the carrying amount of the receivable to be adjusted
DAs an adjusting event, but only if the company's auditors had already flagged the customer as a credit risk before the reporting date
Correct answer: .
IAS 10 treats a customer's bankruptcy occurring after the reporting period as an adjusting event when it confirms that the customer's financial difficulties, and therefore the impairment of the receivable, already existed at the reporting date; the carrying amount of the receivable must be adjusted to reflect that evidence. The option classifying this as non-adjusting because the filing itself happened after the reporting date focuses on the wrong moment in time — what matters under IAS 10 is when the underlying conditions (the customer's financial difficulty) existed, not when the formal bankruptcy filing or announcement occurred. The option treating the earlier favourable assessment as the end of the matter, with no disclosure or adjustment needed, misses the entire purpose of adjusting events: later-arriving evidence is used to correct the reporting-date estimate to reflect what was actually true then, even though it was not yet known. The option conditioning the classification on whether auditors had previously flagged the customer as a credit risk introduces a factor IAS 10 does not use at all; the adjusting/non-adjusting distinction turns solely on whether the event provides evidence of conditions existing at the reporting date, not on what any particular party had previously flagged.
Source: IAS 10 Events after the Reporting Period, paragraph 9(a) (example of an adjusting event: bankruptcy of a customer confirming a loss existed at the reporting date)
A company holds a contract that has become onerous. Under IAS 37, as clarified by the IASB's amendment on the costs of fulfilling a contract, what amount should the unavoidable cost of the contract be measured at?
AThe total remaining contractual revenue the company would have received had it continued to perform the contract in full
BThe lower of the cost of fulfilling the contract and any compensation or penalties arising from failure to fulfil it, representing the least net cost of exiting the contract
CThe higher of the cost of fulfilling the contract and any compensation or penalties arising from failure to fulfil it, so as to be prudent
DThe historical cost of any assets dedicated to the contract, without regard to any compensation or penalties for non-performance
Correct answer: .
IAS 37 measures the unavoidable costs under an onerous contract as the lower of the cost of fulfilling the contract and any compensation or penalties arising from failing to fulfil it, which together represent the least net cost of exiting the contract; a provision is recognised for that amount after any related assets have first been tested for impairment under IAS 36. The option pointing to the total remaining contractual revenue is wrong because revenue forgone is not what the standard measures at all — the test compares costs of performance against the cost of walking away, not what income would have been received. The option using the higher of the two figures inverts the actual rule: picking the larger amount would systematically overstate the provision, and deliberately inflating a provision beyond the standard's specified measure is not what IAS 37 means by a faithful or prudent estimate. The option relying on historical cost of dedicated assets, ignoring compensation or penalties, addresses a different question — impairment of the contract's related assets under IAS 36 — rather than the onerous-contract provision itself, which specifically requires comparing fulfilment cost against exit compensation or penalties.
Source: IAS 37 Provisions, Contingent Liabilities and Contingent Assets, paragraph 68 and Onerous Contracts—Cost of Fulfilling a Contract (Amendments to IAS 37, 2020)
A company's board approves a detailed restructuring plan at a meeting on a given date, identifying the business units affected, the approximate number of employees to be terminated, and the expected implementation timeline and costs. The board's decision is recorded in board minutes, but it is not announced to employees or anyone else affected, and no steps to implement the plan have been taken by the reporting date. Under IAS 37, has a constructive obligation to restructure arisen at the reporting date?
ANo — a detailed formal plan alone does not create a constructive obligation; the entity must also have raised a valid expectation in those affected, by starting to implement the plan or announcing its main features to them, before the reporting date
BYes — board approval of a detailed formal plan is, by itself, sufficient to create a constructive obligation, regardless of whether anyone affected by the plan has been informed
CNo — a constructive obligation to restructure can never arise under IAS 37, since restructuring costs are only recognised once they are actually incurred
DYes — because the plan, once documented in board minutes, becomes legally binding on the company under company law
Correct answer: .
IAS 37 requires two elements before a constructive obligation to restructure arises: a detailed formal plan identifying matters such as the business affected, the locations and approximate numbers of employees involved, the expenditures to be undertaken, and the timing, and — separately — that the entity has raised a valid expectation in those affected that it will carry out the restructuring, either by starting to implement the plan or by announcing its main features to them. A board decision recorded only in internal minutes, with no announcement and no implementation, satisfies the first element but not the second, so no constructive obligation exists yet at the reporting date. The option treating board approval alone as sufficient skips the valid-expectation requirement entirely, but IAS 37 is explicit that an internal decision, without more, does not bind the entity in the eyes of those who would be affected by it. The option claiming a restructuring obligation can never arise under IAS 37 overcorrects: the standard specifically sets out recognition criteria for constructive restructuring obligations precisely because they can arise before cash is paid, so this option misstates the standard's basic purpose. The option claiming board minutes make the plan legally binding under company law confuses an internal governance record with the constructive-obligation test IAS 37 actually applies, which turns on expectations raised in affected parties, not on the mere existence of a documented board decision.
Source: IAS 37 Provisions, Contingent Liabilities and Contingent Assets, paragraph 72 (constructive obligation to restructure)
A parent entity has a wholly owned subsidiary. During the year, the subsidiary had no transactions of any kind with the parent or with any other related party. Under IAS 24, must the parent-subsidiary relationship still be disclosed in the subsidiary's financial statements?
ANo — IAS 24 only requires disclosure once at least one transaction has occurred between the related parties during the reporting period
BNo — related party disclosures apply only to transactions with key management personnel, not to relationships between a parent and its subsidiaries
CYes, but only if the subsidiary is not wholly owned, since IAS 24 exempts wholly owned subsidiaries from disclosing the parent relationship
DYes — IAS 24 requires disclosure of the relationship between a parent and its subsidiaries irrespective of whether there have been transactions between them
Correct answer: .
IAS 24 requires disclosure of the relationship between a parent and its subsidiaries irrespective of whether there have been transactions between them, because the existence of that close relationship can itself affect how users assess the entity's financial position and performance, separately from whatever transactions may or may not have occurred. The option requiring at least one transaction before disclosure is triggered misreads the standard's disclosure-only approach to relationships, which is explicitly not conditioned on any transaction having taken place. The option limiting related party disclosures to key management personnel is far too narrow: IAS 24's definition of a related party also expressly covers parents, subsidiaries, fellow subsidiaries, associates and joint ventures, so restricting the scope to key management personnel compensation ignores the parent-subsidiary category this scenario is actually about. The option claiming a blanket exemption for wholly owned subsidiaries invents a carve-out that IAS 24 does not contain; the standard's requirement to disclose the parent-subsidiary relationship itself applies regardless of the percentage of ownership held.
Source: IAS 24 Related Party Disclosures, paragraph 13 (disclosure of parent-subsidiary relationships irrespective of transactions)
Under the IASB's 2018 Conceptual Framework for Financial Reporting, which option correctly states how income and expenses are defined?
AIncome is increases in assets, or decreases in liabilities, that result in increases in equity, other than those relating to contributions from holders of equity claims; expenses are decreases in assets, or increases in liabilities, that result in decreases in equity, other than those relating to distributions to holders of equity claims
BIncome is any increase in cash or cash equivalents during the period; expenses are any decrease in cash or cash equivalents during the period, regardless of the source of the change
CIncome and expenses are the two components of comprehensive income that appear only in the statement of profit or loss, never in other comprehensive income
DIncome is recognised when a right to consideration becomes unconditional under a contract, and expenses are recognised when the corresponding performance obligation is satisfied
Correct answer: .
The Conceptual Framework defines income and expense purely in terms of changes in the other elements: income is increases in assets or decreases in liabilities that increase equity, other than increases relating to contributions from holders of equity claims, and expense is the mirror-image decrease in equity from asset decreases or liability increases, other than decreases relating to distributions to those holders. This asset/liability-driven approach applies across the whole statement of comprehensive income, not merely one line of it. The option limiting income and expense to changes in cash misstates the Framework's element-based approach as a cash-basis test, which would exclude accruals entirely. The option confining income and expense to profit or loss alone is wrong because the Framework's definitions cover items recognised in other comprehensive income just as much as items in profit or loss; the split between the two is a presentation question, not part of the definition. The option describing contract-based recognition timing is describing a specific requirement of IFRS 15 for revenue, not the Framework's general definition of income, which applies far more broadly than to revenue contracts alone.
Source: IASB Conceptual Framework for Financial Reporting (2018), Chapter 4, paragraphs 4.68-4.78 (definitions of income and expense)
Under the IASB's 2018 Conceptual Framework, faithful representation is one of the two fundamental qualitative characteristics of useful financial information. Which option correctly identifies the three characteristics a perfectly faithful representation would possess?
AComplete, comparable, and understandable
BComplete, neutral, and free from error
CComplete, verifiable, and timely
DNeutral, prudent, and consistent
Correct answer: .
A perfectly faithful representation would be complete (containing everything a user needs to understand the depicted phenomenon, including necessary descriptions and explanations), neutral (selected and presented without bias, supported by the exercise of prudence so that assets and income are not overstated nor liabilities and expenses understated), and free from error (no errors or omissions in the description, with the process used to produce the information selected and applied without error). Comparability, verifiability, timeliness and understandability are the Framework's four enhancing qualitative characteristics, which make already-useful information even more useful, but they are separate from what makes a depiction itself faithful, so the option pairing completeness with comparability and understandability, and the option pairing completeness with verifiability and timeliness, both wrongly substitute enhancing characteristics for faithful representation's own components. The option pairing neutrality with prudence and consistency is also wrong, since consistency is not one of faithful representation's three components either, even though prudence is correctly linked to supporting neutrality.
Under the IASB's Conceptual Framework, a reporting entity is not necessarily a legal entity. Three finance managers each describe a different set of financial statements: Manager 1's statements cover a parent and all of its subsidiaries as a single economic unit. Manager 2's statements cover only the parent, with the subsidiaries excluded. Manager 3's statements cover two sister entities under common control that are not linked to each other by any parent-subsidiary relationship. What does the Conceptual Framework call each manager's financial statements, respectively?
The Conceptual Framework's reporting-entity chapter labels financial statements by what the reporting entity itself comprises: when the reporting entity is a parent together with all of its subsidiaries, the resulting statements are consolidated financial statements; when the reporting entity is the parent alone, excluding its subsidiaries, the resulting statements are unconsolidated financial statements; and when the reporting entity comprises two or more entities that are not all linked by a parent-subsidiary relationship, such as sister entities under common control, the resulting statements are combined financial statements. Any option that swaps consolidated and unconsolidated, describing the parent-plus-subsidiaries case as unconsolidated or the parent-alone case as consolidated, has the two terms backwards relative to what each label specifically means. The option that assigns the sister-entity case to unconsolidated rather than combined statements misses that the combined label exists precisely because those entities have no parent-subsidiary link to consolidate in the first place, so unconsolidated is not the correct term for that scenario either.
Source: IASB Conceptual Framework for Financial Reporting (2018), Chapter 3, paragraphs 3.10-3.15 (the reporting entity)
A retailer starts the year with net assets financed entirely by equity, and ends the year with higher net assets purely because the specific inventory it holds increased in price faster than general inflation, with no new capital contributed or withdrawn during the year. Under the IASB's Conceptual Framework's concepts of capital maintenance, which statement correctly distinguishes how a financial capital maintenance concept (measured in nominal monetary units) and a physical capital maintenance concept would each treat this increase?
AUnder both concepts, none of the increase is profit; all of it is a capital maintenance adjustment recognised directly in equity
BUnder both concepts, all of the increase is profit, because capital maintenance concepts apply only when an entity's shares are actively traded
CUnder the physical capital concept, all of the increase is profit, because operating capacity is unaffected by asset-specific price changes
DUnder the financial capital concept measured in nominal monetary units, all of the increase in net assets is profit; under the physical capital concept, only the increase in current prices that exceeds the increase needed to maintain physical operating capacity is profit, with the rest treated as a capital maintenance adjustment in equity
Correct answer: .
Under the financial capital maintenance concept measured in nominal monetary units, profit is any increase in the nominal money amount of net assets over the period, after excluding contributions and distributions, so an asset-specific price rise that pushes up nominal net assets is recognised entirely as profit, with no separate capital maintenance adjustment. Under the physical capital maintenance concept, profit is measured only after the entity's physical productive capacity (or the resources needed to achieve it) at the start of the period has been maintained; only the portion of the price increase that exceeds what is needed to keep replacing that operating capacity counts as profit, while the remainder is treated as a capital maintenance adjustment recognised directly in equity rather than in profit. Saying neither concept recognises any profit from the increase ignores how the nominal financial capital concept actually works. Saying both concepts treat the whole increase as profit ignores the physical concept's operating-capacity adjustment, and misstates capital maintenance concepts as depending on whether shares are publicly traded, which they do not. Saying the physical concept treats the whole increase as profit gets that concept's own mechanism backwards.
Source: IASB Conceptual Framework for Financial Reporting (2018), Chapter 8, paragraphs 8.1-8.10 (concepts of capital and capital maintenance)
A company changes an accounting policy retrospectively during the current year, and the change has a material effect on the amounts reported in the statement of financial position at the start of the immediately preceding comparative period. Under IAS 1, in addition to the statements as at the end of the current period and the end of the comparative period, what additional primary statement, if any, must the complete set of financial statements include?
AA third statement of financial position, as at the beginning of the earliest comparative period presented, together with related notes
BA pro-forma statement of financial position prepared under the previous accounting policy for comparison purposes only, presented as supplementary information outside the financial statements
CNo additional statement is required; a note disclosure describing the change in accounting policy and its quantified effect is sufficient on its own
DA fourth statement of financial position covering two years before the comparative period, in addition to the third statement, to show the full multi-year trend
Correct answer: .
IAS 1 requires a third statement of financial position, as at the beginning of the earliest comparative period presented, together with related notes, whenever a retrospective change in accounting policy, a retrospective restatement, or a reclassification has a material effect on the information in that opening statement of financial position. This gives users a complete before-and-after picture across all periods affected, not just the two periods normally presented. A supplementary pro-forma statement prepared under the old policy is not what IAS 1 asks for; the standard requires an actual third statement of financial position prepared on the same, updated basis as the rest of the accounts, not a comparison exhibit sitting outside the financial statements. A note disclosure alone is insufficient because IAS 1 specifically elevates this to a primary statement requirement, not merely a narrative disclosure. Requiring a fourth statement covering an additional year goes beyond what IAS 1 asks for, which stops at the one extra statement at the start of the earliest comparative period, not additional years further back.
Source: IAS 1 Presentation of Financial Statements, paragraphs 10 and 40A-40D (third statement of financial position)
A company's financial statements comply with every requirement of IFRS Accounting Standards except one specific disclosure requirement in IFRS 7, which the company omits because it considers the information immaterial to users, even though IFRS 7 provides no materiality-based exemption for that particular disclosure. Under IAS 1, may the company still describe its financial statements as complying with IFRS in its notes?
AYes, provided the company discloses the specific requirement it did not comply with and its reasons in the notes
BNo, an entity must not describe its financial statements as complying with IFRS unless they comply with all the requirements of all applicable Standards and Interpretations
CYes, because IAS 1 permits an unreserved statement of compliance as long as at least substantially all disclosure requirements, excluding minor ones, are met
DYes, but only if the company's audit committee and external auditor jointly approve the specific omission in writing before the financial statements are authorised for issue
Correct answer: .
IAS 1 states that an entity must not describe its financial statements as complying with IFRS unless they comply with all the requirements of all applicable Standards and Interpretations; there is no partial-compliance version of the statement of compliance. Disclosing the specific requirement not met, together with reasons, does not cure the problem, because IAS 1's compliance statement is binary rather than something that can be qualified or reserved by an accompanying explanation. Treating immateriality as an automatic excuse is wrong here because the scenario specifies that IFRS 7 provides no materiality-based exemption for that particular disclosure, so materiality cannot be invoked to justify skipping a requirement the Standard itself does not make conditional on materiality. Framing this as a matter of substantial, rather than complete, compliance misstates the requirement, and no amount of internal or external sign-off by an audit committee or auditor can substitute for actually meeting the requirement, since IAS 1 grants no such governance-based exception.
Source: IAS 1 Presentation of Financial Statements, paragraph 16 (statement of compliance)
During the current year, a company discovers that revenue was overstated by a material amount in the prior year's financial statements due to a calculation mistake, not a change in estimate or accounting policy. Under IAS 8, assuming retrospective restatement is practicable, how should the company correct this error in the current year's financial statements?
ARecognise the entire cumulative effect of the error as an adjustment to profit or loss in the current period, since IAS 8 requires all corrections to be reflected prospectively from the date of discovery
BDisclose the error in the notes only, without adjusting any reported figures, since retrospective correction is reserved exclusively for changes in accounting policy, not for errors
CRestate the comparative amounts for the prior period presented and adjust the opening balance of retained earnings (or other equity component affected) for the earliest prior period presented, as if the error had never occurred
DRestate only the current period's opening statement of financial position, leaving the comparative income statement for the prior period exactly as originally reported, to preserve consistency with previously issued reports
Correct answer: .
IAS 8 requires a material prior period error to be corrected retrospectively in the first financial statements authorised for issue after its discovery: the entity restates the comparative amounts for the prior period(s) presented in which the error occurred, and adjusts the opening balance of retained earnings (or another affected equity component) for the earliest prior period presented, as if the error had never occurred. Treating the whole cumulative effect as a current-period profit-or-loss adjustment describes prospective treatment, which is how IAS 8 treats a change in accounting estimate, not how it treats an error; a calculation mistake in reported revenue is an error, not an estimate revision. Disclosing the error without adjusting any figures ignores that retrospective correction under IAS 8 applies specifically to material errors, not only to voluntary changes in accounting policy. Leaving the prior period's income statement exactly as originally reported while touching only the opening statement of financial position would understate the correction, since the comparative income statement itself must also be restated to reflect what the results would have been without the error.
Source: IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors, paragraphs 42-49 (correction of prior period errors)
A company's board of directors formally declares a dividend on 20 December, creating a present obligation to pay at that date. The company's reporting date is 31 December, and the dividend remains unpaid at that date. Under IAS 10, how should the dividend be reflected in the financial statements for the year ended 31 December?
AAs a non-adjusting event, disclosed in the notes only, because dividend-related items are always treated as occurring after the reporting period regardless of when the board acts
BAs a deduction from other comprehensive income for the period, rather than a liability, because dividends never affect the statement of financial position
CAs a contingent liability, disclosed but not recognised, because the obligation to pay a declared dividend is not confirmed until the dividend is actually paid in cash
DAs a liability at the reporting date, because the obligation to pay arose when the dividend was declared, before the end of the reporting period
Correct answer: .
A dividend becomes a present obligation the moment the board (or whichever body holds the authority) formally declares it, not when it is eventually paid, so a dividend declared on 20 December, before the 31 December reporting date, gives rise to a liability that must be recognised in the financial statements for the year ended on that date. This is the mirror image of a dividend declared after the reporting date, which IAS 10 treats as a non-adjusting event because no obligation yet existed at the reporting date. Treating this dividend as a non-adjusting note disclosure only would be applying the after-year-end rule to a before-year-end fact pattern, which gets the timing backwards. Deducting it from other comprehensive income misdescribes dividends entirely, since a declared but unpaid dividend is a liability on the statement of financial position, not an item running through other comprehensive income. Calling it a contingent liability confuses the confirmation of a present obligation, which already exists once declared, with the separate, later event of actually settling that obligation in cash.
Source: IAS 10 Events after the Reporting Period, paragraphs 12-13 (dividends)
A company is a defendant in a lawsuit at year end. Legal counsel assesses that an outflow of resources to settle the claim is possible, but concludes it is not probable that the company will need to make any payment, and the possibility is not remote. Under IAS 37, how should the company account for this at year end?
ANo provision is recognised, but the company discloses the contingent liability, including an estimate of its financial effect and an indication of the uncertainties surrounding it, unless the possibility of any outflow is remote
BA provision must still be recognised at the best estimate of the possible outflow, because IAS 37 requires provisions for any obligation that is more than remote, not only for probable ones
CNothing is recognised or disclosed, because IAS 37 only requires action once an outflow becomes probable; a merely possible outflow carries no disclosure obligation at all
DThe company recognises a provision measured at 50% of the best estimate of the possible outflow, reflecting the intermediate likelihood between probable and remote
Correct answer: .
IAS 37 sets a three-tier probability framework: a provision is recognised only when an outflow of resources is probable; when an outflow is merely possible, rather than probable, but the possibility is not remote, no provision is recognised, and instead the entity discloses the contingent liability, including an estimate of its financial effect and an indication of the uncertainties relating to the amount or timing of any outflow, unless the possibility of any outflow at all is remote. Recognising a provision here would apply the probable-outflow recognition test to a fact pattern that legal counsel has assessed as merely possible, not probable, which is exactly the case IAS 37 reserves for disclosure rather than recognition. Concluding that nothing at all needs to be done ignores that disclosure, not silence, is what a possible-but-not-remote outflow requires. Measuring a provision at some intermediate fraction of the estimate invents a blending mechanism IAS 37 does not use; the standard's threshold for recognition is a yes-or-no probability test, not a sliding-scale partial recognition based on likelihood.
Source: IAS 37 Provisions, Contingent Liabilities and Contingent Assets, paragraphs 27-28 and 86 (contingent liabilities)
A company discloses the total amount paid to its key management personnel during the year as a single lump-sum figure in the related-party note, without any further breakdown. Under IAS 24, is this disclosure sufficient?
AYes, IAS 24 only requires the aggregate total; a further breakdown by benefit type is encouraged as best practice but is not mandatory
BNo, IAS 24 requires key management personnel compensation to be disclosed in total AND separately by category: short-term employee benefits, post-employment benefits, other long-term benefits, termination benefits, and share-based payment
CNo, IAS 24 requires the compensation to be broken down by each individual key management person named, rather than by benefit category
DYes, provided the company is a first-time adopter of IFRS in the year of disclosure, since IFRS 1 grants a transitional exemption from the categorised breakdown otherwise required by IAS 24
Correct answer: .
IAS 24 requires an entity to disclose key management personnel compensation both in total and broken down by category: short-term employee benefits, post-employment benefits, other long-term benefits, termination benefits, and share-based payment. A single lump-sum total, without that categorised breakdown, does not satisfy the standard, so the aggregate-only approach is insufficient rather than acceptable best practice. IAS 24 does not require the compensation to be attributed to each named individual; the disclosure operates at the level of key management personnel as a group and by benefit category, not on an individual-by-individual basis, so naming individuals is not the fix the standard actually calls for. There is also no IFRS 1 transitional exemption that lets a first-time adopter skip the categorised breakdown in the year of adoption; first-time adoption relief under IFRS 1 addresses comparative and opening-balance issues on transition, not an entity's ongoing IAS 24 disclosure obligations for key management personnel compensation.
Source: IAS 24 Related Party Disclosures, paragraph 17 (key management personnel compensation)
A company has a $2 million bank loan carrying an original maturity of two years from the reporting date. The loan agreement requires quarterly testing of a leverage-ratio covenant. At the reporting date, the company was in compliance with the covenant. Three weeks after the reporting date, but before the financial statements are authorised for issue, the company breaches the covenant for the first time, giving the lender an immediate right to demand repayment from that point onward. Under IAS 1, how should the loan be classified in the statement of financial position at the reporting date?
AAs non-current, because only conditions and rights existing at the reporting date determine classification; a covenant breach that first occurs after the reporting date does not retroactively remove the right to defer settlement that existed at that date, although the post-year-end breach may still need separate disclosure as a subsequent event
BAs current, because IAS 1 requires classification to reflect the entity's ability to avoid a demand for repayment at any time up to the date the financial statements are authorised for issue, not merely at the reporting date itself
CAs current, because a covenant breach occurring at any point during the twelve months following the reporting date automatically reclassifies the related loan, regardless of when the right to defer settlement existed
DSplit between current and non-current, in the same proportion as the number of days in the following year that elapsed before the breach occurred
Correct answer: .
IAS 1 classifies a liability as non-current only if the entity has, at the end of the reporting period, an existing right to defer settlement for at least twelve months; the amendments to IAS 1 clarify that only conditions with which an entity must comply on or before the reporting date affect that classification, and that classification is not affected by an event after the reporting period that removes or waters down the right, even though the event may need to be disclosed separately as a non-adjusting subsequent event. Here, the company was in compliance at the reporting date itself, so the right to defer settlement existed at that date and the loan is classified as non-current; the breach three weeks later, however material to users, does not change that classification because IAS 1's test looks back to the reporting date rather than forward to the authorisation date. The option requiring the right to be maintained all the way through to the authorisation date inverts this test: IAS 1 deliberately confines the assessment to conditions existing at the reporting date, which is precisely why a subsequent-period breach does not force reclassification. The option treating any breach within the following twelve months as an automatic trigger for reclassification ignores the reporting-date cut-off altogether. The proportional-split option invents a pro-rata mechanism that IAS 1 does not use anywhere in its current/non-current liability guidance; classification is a binary determination based on the right that existed at the reporting date, not an apportionment based on how much of the following year elapsed before a later event.
Source: IAS 1 Presentation of Financial Statements, paragraphs 69 and 72A-72B (classification of liabilities as current or non-current; covenants and events after the reporting period)
A company transfers a portfolio of trade receivables to a bank. Under the transfer agreement, the bank takes on collection of the receivables, but the company retains an obligation to reimburse the bank for a portion of any customer defaults, up to a specified cap. Management must decide whether to remove the transferred receivables from the statement of financial position, and if so, whether in full or only in part. Under the IASB's Conceptual Framework's approach to derecognition, what should primarily determine this decision?
AWhether legal title to the receivables has passed to the bank, which by itself is always determinative of full derecognition regardless of any risks or obligations the company has retained
BWhether the transfer was made for cash consideration, since the Conceptual Framework's derecognition guidance treats only non-cash transfers as capable of resulting in partial derecognition
CWhether the company has lost control of the receivables (or of the specific components transferred); because the company has retained an exposure to default losses up to the cap, deciding what to derecognise should aim to faithfully represent both the component the company no longer controls and any component, such as the retained reimbursement obligation, that it still holds, rather than being driven purely by the transfer's legal form
DWhether the transfer agreement legally labels the transaction as a 'sale' rather than a 'financing', since the Conceptual Framework's derecognition guidance follows whatever label the parties give the transaction
Correct answer: .
The Conceptual Framework describes derecognition, the removal of all or part of a recognised asset or liability from the statement of financial position, as normally occurring when an item no longer meets the definition of an asset or a liability, which for an asset means the entity has lost control of it. Where a transfer leaves the entity with a retained component, such as an obligation to reimburse the transferee for a portion of default losses, the Framework's guidance is that the derecognition assessment should aim to faithfully represent both the assets or liabilities the entity retains after the transaction and the change in the entity's assets and liabilities that the transaction caused, rather than treating the transaction as all-or-nothing; that can point to partial derecognition, recognising a new liability for the retained reimbursement exposure, or continued recognition of the transferred item, depending on which treatment best achieves that faithful representation. The option resting everything on legal title mistakes a single legal formality for the substance-based control test the Framework actually applies, and ignores that the company has retained a real economic exposure through the reimbursement obligation. The option limiting partial derecognition to non-cash transfers invents a restriction the Framework's derecognition discussion does not contain; the form of consideration received is not what drives whether a retained component exists. The option that follows whatever label the transfer agreement uses conflicts with the Framework's substance-based, control-oriented approach, under which the legal description parties choose for a transaction is not itself the basis for the derecognition assessment.
A company issues a financial instrument that entitles the holder to a share of the company's net assets on liquidation, but the instrument imposes no contractual obligation on the company to deliver cash or another financial asset to the holder at any point before liquidation occurs. Under the Conceptual Framework, which classification of this instrument from the issuer's perspective is consistent with the Framework's definitions of a liability and of equity?
AA liability, because any instrument a company issues to an external holder in exchange for consideration meets the Conceptual Framework's definition of a liability, irrespective of whether a contractual obligation to transfer an economic resource exists
BA liability, because the holder's right to a share of net assets on liquidation is itself an unconditional obligation to deliver cash that must be recognised as a liability for as long as the instrument is outstanding
CEquity, but only because the entity has made an accounting policy election to designate the instrument as equity rather than as a liability
DEquity, because the instrument does not meet the Conceptual Framework's definition of a liability, since there is no present obligation to transfer an economic resource before liquidation, so the residual claim it represents on the entity's net assets falls within the Framework's definition of equity as the residual interest in the assets of the entity after deducting all its liabilities
Correct answer: .
The Conceptual Framework defines a liability as a present obligation of the entity to transfer an economic resource as a result of past events, and defines equity as the residual interest in the assets of the entity after deducting all its liabilities. Because this instrument creates no obligation on the company to transfer cash or another asset at any point before liquidation, it does not meet the liability definition, so the claim it represents, a share of whatever net assets remain, falls by elimination into the Framework's residual definition of equity. The option treating any instrument issued for consideration as automatically a liability ignores that the liability definition turns specifically on the existence of a present obligation to transfer an economic resource, not on the mere fact that consideration changed hands. The option describing the liquidation right as an unconditional obligation to deliver cash mischaracterises the instrument: before liquidation there is no present obligation at all, and even on liquidation the holder's entitlement is to whatever residual net assets exist, not to a fixed or unconditional cash amount, which is exactly what distinguishes a residual equity claim from a debt obligation. The option resting classification on an accounting policy election is wrong because classification as a liability or equity follows from the substance of the contractual rights and obligations attached to the instrument under the Framework's definitions, not from a discretionary choice management can make.
Source: IASB Conceptual Framework for Financial Reporting (2018), paragraphs 4.3, 4.26, 4.63-4.64 (definitions of a liability and of equity)
A company presents its statement of profit or loss using the function of expense (cost of sales) method, showing cost of sales, distribution costs, and administrative expenses as its main expense line items, rather than analysing expenses by their nature. Under IAS 1, what additional disclosure, if any, does choosing this method require?
AThe company must disclose additional information on the nature of its expenses, including at least depreciation and amortisation expense and employee benefits expense, because the function of expense method can require arbitrary allocation judgements and otherwise provides less information about the nature of expenses than the alternative method
BNo additional disclosure is required, because IAS 1 treats the function of expense method as providing strictly more information to users than the nature of expense method in every case
CThe company must additionally present its entire statement of profit or loss a second time using the nature of expense method as supplementary information in the notes
DThe company must obtain a separate level of external audit assurance specifically over the judgements used to allocate costs between functions, beyond the assurance already covering the rest of the financial statements
Correct answer: .
IAS 1 permits an entity to analyse its expenses using either the nature of expense method or the function of expense method, choosing whichever provides information that is reliable and more relevant, but where an entity chooses the function of expense method it must disclose additional information on the nature of expenses, including at a minimum depreciation and amortisation expense and employee benefits expense, precisely because classifying by function can involve arbitrary allocations and otherwise withholds nature-based information that users find useful. The option claiming no additional disclosure is needed gets this backwards: it is exactly because the function method can obscure the nature of expenses that IAS 1 imposes this extra requirement, rather than treating that method as strictly superior. The option requiring a full second presentation of the entire statement by nature overstates what IAS 1 asks for; the standard calls for targeted additional disclosure of specific natural expense categories, not a duplicate primary statement. The option inventing a distinct audit-assurance requirement confuses a financial reporting disclosure requirement with an audit engagement matter; IAS 1 does not prescribe audit procedures at all, let alone a bespoke assurance level tied to this presentation choice.
Source: IAS 1 Presentation of Financial Statements, paragraphs 99-104 (analysis of expenses by nature or by function)
A company's other comprehensive income for the year includes a gain on revaluing a class of property under the revaluation model in IAS 16, and a foreign currency translation gain arising on consolidating a foreign subsidiary. Under IAS 1, how should these two items be presented within the statement of comprehensive income?
ABoth items in the same group, because IAS 1 groups items of other comprehensive income only according to which accounting standard gives rise to them, not according to whether they will later be reclassified to profit or loss
BBoth items in the same group, because every item of other comprehensive income is subsequently reclassified to profit or loss once the underlying asset is disposed of or the foreign operation is sold
CIn two separate groups: the property revaluation gain within the group of items that will not be reclassified subsequently to profit or loss, and the foreign currency translation gain within the group of items that will (or may) be reclassified subsequently to profit or loss when specified conditions are met
DBoth items in the same group, because neither a property revaluation surplus nor a foreign currency translation gain is ever reclassified to profit or loss under any circumstances
Correct answer: .
IAS 1 requires the other comprehensive income section to present line items classified by nature and grouped into those that will not be reclassified subsequently to profit or loss and those that will (or may) be reclassified subsequently to profit or loss when specified conditions are met. A revaluation surplus recognised under IAS 16 does not pass through profit or loss even when the related asset is eventually disposed of, since any transfer of the surplus to retained earnings happens directly within equity, so it belongs in the group that is never reclassified. A foreign currency translation reserve, by contrast, is reclassified to profit or loss under IAS 21 when the foreign operation to which it relates is disposed of, so it belongs in the other group. The option grouping items by which standard produced them ignores the explicit reclassification-based grouping IAS 1 requires. The option asserting that every comprehensive income item eventually passes through profit or loss is wrong precisely because the revaluation surplus does not, even on disposal of the asset. The option asserting that neither item is ever reclassified is wrong for the opposite reason: the translation reserve does flow through profit or loss on disposal of the foreign operation, which is exactly why the two items cannot share a group.
Source: IAS 1 Presentation of Financial Statements, paragraph 82A (grouping of items of other comprehensive income); IAS 21 The Effects of Changes in Foreign Exchange Rates (reclassification of the translation reserve on disposal)
After the reporting date, but before the financial statements are authorised for issue, an entity's largest customer unexpectedly enters liquidation and, separately, the entity's bank refuses to renew a credit facility maturing shortly. Taken together, management concludes that the entity has no realistic alternative but to cease trading and liquidate. No indication of this outcome existed at the reporting date. Under IAS 10, how should this development be reflected in the financial statements for the period that has just ended?
AAs a non-adjusting event, disclosed in the notes with a description of the event and an estimate of its financial effect, since the deterioration arose entirely after the reporting date
BAs an event that requires a fundamental change in the basis of accounting, so the financial statements can no longer be prepared on a going concern basis at all, because IAS 10 does not permit an entity to prepare its financial statements on a going concern basis once management determines, after the reporting period, that it intends to liquidate the entity or has no realistic alternative but to do so
CAs an adjusting event limited to writing down the specific trade receivable owed by the customer that entered liquidation, with the going concern basis of preparation otherwise unaffected
DAs a non-adjusting event requiring only a note disclosing a material uncertainty related to going concern, with the financial statements still prepared on a going concern basis
Correct answer: .
IAS 10 carves out a special rule for going concern: an entity must not prepare its financial statements on a going concern basis if management determines, at any point after the reporting period but before the financial statements are authorised for issue, that it intends to liquidate the entity or cease trading, or that it has no realistic alternative but to do so, and because the effect of that determination is so pervasive, it requires a fundamental change in the basis of accounting rather than an adjustment to specific amounts. This overrides the ordinary distinction between adjusting events, which reflect conditions existing at the reporting date, and non-adjusting events, which do not: even though nothing indicated this outcome at the reporting date itself, the post-year-end liquidation decision still forces a change in the fundamental basis on which the whole set of financial statements is prepared. The option treating this as a simple non-adjusting disclosure item understates what IAS 10 requires, since disclosure alone is not sufficient once management has made this determination. The option confining the effect to writing down one customer's receivable misses that the going concern determination affects the basis of preparation for the entire set of financial statements, not just one balance. The option limiting the response to a going-concern uncertainty note while still preparing the statements on a going concern basis is exactly the treatment IAS 10 prohibits once management has actually decided there is no realistic alternative to liquidation, as opposed to merely identifying uncertainty about the outcome.
Source: IAS 10 Events after the Reporting Period, paragraph 14 (going concern determined inappropriate after the reporting period)
A company has recognised a provision for the estimated cost of a product recall. It holds product liability insurance, and the insurer has issued written confirmation that it will reimburse the full cost of the recall once the recall is completed as planned; management assesses receipt of this reimbursement as virtually certain. Under IAS 37, how should the reimbursement be reflected in the financial statements?
AIt should not be recognised in the statement of financial position at all, and should instead be disclosed only as a contingent asset in the notes, because a right to reimbursement can never be recognised as an asset while the related provision remains unsettled
BIt should be recognised as a direct reduction of the carrying amount of the provision itself, rather than as a separate item in the statement of financial position
CIt should be recognised as a separate asset, measured at the full amount management expects to recover from the insurer even if that amount exceeds the carrying amount of the related provision
DIt should be recognised as a separate asset, measured at an amount that does not exceed the carrying amount of the related provision, because IAS 37 permits recognition of a reimbursement only when receipt is virtually certain, and even then requires it to be treated as a separate asset rather than netted against the provision on the face of the statement of financial position, although the related expense may be presented net of the reimbursement in profit or loss
Correct answer: .
IAS 37 permits recognition of a reimbursement receivable from another party only when it is virtually certain that the reimbursement will be received if the entity settles the obligation, and requires that reimbursement to be treated as a separate asset, capped at an amount that does not exceed the carrying amount of the provision itself; only in profit or loss, not in the statement of financial position, may the related expense be presented net of the reimbursement. Here, the insurer's written confirmation makes receipt virtually certain, so recognition as a separate asset is required rather than merely a contingent-asset disclosure. The option limiting the entity to a contingent-asset disclosure describes the treatment that applies when reimbursement is only probable, not virtually certain, and understates what this fact pattern actually requires. The option netting the reimbursement directly against the provision in the statement of financial position conflicts with IAS 37's explicit requirement that the reimbursement be presented as a separate asset there, even though net presentation is allowed in profit or loss. The option allowing the reimbursement asset to be measured above the provision's carrying amount ignores the explicit cap IAS 37 places on the amount recognised, regardless of how much the entity ultimately expects to recover.
An individual has significant influence over Company X through a substantial shareholding and a board seat. That individual's adult child, who has no personal shareholding or role at Company X, separately owns and controls Company Y, an unrelated business with no shareholding, contractual, or trading relationship with the individual or with Company X's parent. During the year, Company X sells goods to Company Y at normal market prices under a standard commercial contract. Under IAS 24, is Company Y a related party of Company X?
AYes, because the individual's child is a close member of the individual's family, and the individual has significant influence over Company X; an entity controlled by a close family member of a person who has significant influence over the reporting entity is itself a related party of that reporting entity, regardless of the pricing terms of any transaction between them
BNo, because the transaction between Company X and Company Y takes place at normal market prices under a standard commercial contract, and arm's-length pricing removes any counterparty from IAS 24's related party definition regardless of any family or influence connection
CNo, because Company Y has no shareholding, contractual, or trading relationship with the individual personally or with Company X's parent, so no related party relationship can arise through the individual's child
DYes, but only if Company Y is also required to be included within a set of consolidated financial statements together with Company X, since IAS 24 restricts its related party definition to entities within the same consolidation boundary
Correct answer: .
IAS 24 defines a person (or a close member of that person's family) as related to a reporting entity if that person has control, joint control, or significant influence over it, and separately provides that an entity is related to the reporting entity if it is controlled or jointly controlled by a person identified under that first definition. A close member of the family includes that person's children, so the individual's child is a close family member of someone with significant influence over Company X; because that child controls Company Y, Company Y meets IAS 24's related party definition with respect to Company X, irrespective of how the intercompany transaction is priced. The option treating arm's-length pricing as removing related party status confuses the separate question of related party status with the disclosure of transaction terms: pricing at market rates does not stop an entity from being a related party, it only affects what is said about the terms of transactions with that party. The option requiring a direct relationship between Company Y and the individual or the parent overlooks that IAS 24's related party definition operates through the chain of control by a close family member, not only through direct relationships. The option requiring inclusion within the same consolidated group imports a consolidation-boundary test that IAS 24's own related party definition, which is deliberately broader than the consolidation boundary, does not contain.
Source: IAS 24 Related Party Disclosures, paragraph 9 (definitions of a related party and of close members of the family of a person)
A company's revenue for the year would, on an accurate basis, show a small decline from the prior year. Management identifies an individually small overstatement in a revenue accrual, well below any percentage-of-revenue or percentage-of-profit threshold the company would ordinarily treat as material, but correcting it would change the reported year-on-year revenue trend from a decline to a modest increase. Under IAS 1's approach to materiality, may the company treat this misstatement as immaterial and leave it uncorrected purely because of its small size relative to revenue or profit?
AYes, because IAS 1 defines materiality solely by reference to a fixed percentage of revenue or profit, so any amount below that threshold can never be material regardless of its effect on a reported trend
BNo, but only because IAS 1 requires every individual misstatement, however small, to be corrected without any materiality assessment being applied at all
CNo, because materiality depends on both the nature and the magnitude of information; an amount that is quantitatively small can still be material where, because of what it represents, here, reversing an otherwise-declining revenue trend, omitting or misstating it could reasonably be expected to influence the decisions that primary users make on the basis of the financial statements
DYes, provided the company separately discloses the uncorrected misstatement and its effect on the revenue trend in the notes to the financial statements
Correct answer: .
IAS 1 states that information is material if omitting, misstating, or obscuring it could reasonably be expected to influence the decisions that primary users of the financial statements make, and that materiality is assessed by reference to the nature or the magnitude of the information, or both, in the context of the entity's particular circumstances. A qualitative factor, such as an item's effect on a reported trend, can make quantitatively small information material even where it falls below a percentage-based threshold the entity might use as a general starting point, because the mere fact that an amount is small in size does not, by itself, mean it cannot influence a user's assessment of the entity's performance. The option relying on a fixed percentage threshold as the sole test misstates IAS 1's materiality definition, which is not expressed as a bright-line quantitative rule. The option demanding correction of every misstatement regardless of materiality also misstates the standard: materiality assessment still applies to every item, it simply produces a different answer here because of the item's qualitative effect on the trend, not because a blanket zero-tolerance rule exists. The option allowing disclosure of the uncorrected misstatement to substitute for correcting it confuses disclosure with correction; once an item is assessed as material, IAS 1 requires the financial statements themselves to reflect it correctly, and a note describing a known material misstatement does not cure that misstatement.
Source: IAS 1 Presentation of Financial Statements, paragraph 7 (definition of material, as amended); IASB Conceptual Framework for Financial Reporting (2018), paragraph 2.11 (qualitative factors and materiality)
In the current year, a company discovers a material error that has affected several prior reporting periods. It is practicable to determine the error's effect on the immediately preceding comparative period, but the information needed to determine its period-specific effects on any periods before that is not available and cannot reasonably be obtained. Under IAS 8, how should the company correct this error?
AIt should restate the financial statements from the very first period in which the error occurred, using reasonable estimates to reconstruct the missing information for the earliest affected periods
BIt should restate the opening balances of assets, liabilities, and equity for the earliest period for which retrospective restatement is practicable, here, the immediately preceding comparative period, rather than attempting to reach back further where the period-specific effects cannot be determined
CIt should abandon retrospective correction entirely and instead recognise the entire cumulative effect of the error as an adjustment to profit or loss of the current period
DIt should restate every prior period presented, but limit the correction in periods for which information is unavailable to a proportional estimate based on the number of periods affected
Correct answer: .
IAS 8 requires a material prior period error to be corrected retrospectively, but where it is impracticable to determine the period-specific effects of the error on comparative information for one or more of the prior periods presented, the entity instead restates the opening balances of assets, liabilities, and equity for the earliest period for which retrospective restatement is practicable, which may be the current period. Because the effect on the immediately preceding comparative period can be determined here, that is the earliest period for which restatement is practicable, and it is the opening balances for that period that must be restated rather than reaching further back into periods where the necessary information genuinely does not exist. The option calling for reconstruction of missing information using reasonable estimates for the earliest periods conflicts with the premise of impracticability: IAS 8's impracticability exception exists precisely because that information is not available or cannot be obtained, so substituting invented estimates would not produce a faithful correction. The option abandoning retrospective correction altogether in favour of a full cumulative current-period profit-or-loss adjustment describes the different, more severe circumstance in IAS 8 where even the cumulative effect at the beginning of the current period cannot be determined for any prior period, a situation this fact pattern does not present, since the immediately preceding period's effect is determinable. The option applying a proportional estimate across periods invents a mechanism IAS 8's impracticability provisions do not include.
Source: IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors, paragraph 44 (impracticability of determining period-specific effects of a prior period error)