In principle, a first-time adopter should prepare financial statements as if it had always applied IFRSs. Although entities routinely have to apply new accounting standards by way of prior year adjustment, adopting IFRSs, a new basis of accounting, is a challenging undertaking and poses a distinct set of problems. One cannot underestimate the magnitude of the effort involved in adopting a large number of new accounting standards. The requirements of individual standards will often differ significantly from those under an entity's previous GAAP and information may need to be collected that was not required under the previous GAAP.
IFRS 1 – First-time Adoption of International Financial Reporting Standards – has a rather limited objective, to ensure that an entity's first IFRS financial statements, and its interim financial reports for part of the period covered by those first IFRS financial statements, contain high quality financial information that:
It is important for users to be mindful of this objective as it provides the principal rationale underlying many of the decisions reflected in the standard, in particular the various exceptions that require, and exemptions that allow, a first-time adopter to deviate from the general rule (i.e. a retrospective application).
Although IFRS 1 owes its existence to the 2005 adoption of IFRSs by EU companies whose securities are traded on an EU regulated market,1 one of the IASB's aims was ‘to find solutions that would be appropriate for any entity, in any part of the world, regardless of whether adoption occurs in 2005 or at a different time’. [IFRS 1.BC3]. IFRS 1 had to be written in a way that completely ignores a first-time adopter's previous GAAP. This means that first-time adoption exemptions are made available to all first-time adopters, including those whose previous GAAP was very close to IFRSs. A first-time adopter that so desires will be able to make considerable adjustments to its opening IFRS statement of financial position, using the available exemptions in IFRS 1, even if the differences between its previous GAAP and IFRSs were only minor. Yet, it may also be required to make considerable adjustments due to the requirement to use the same IFRS standards for all periods presented in the first IFRS financial statements.
Another issue is the potential for lack of comparability between different first-time adopters, and between first-time adopters and entities already applying IFRSs. [IFRS 1.BC9]. The IASB ultimately decided that it was more important to achieve ‘comparability over time within a first-time adopter's first IFRS financial statements and between different entities adopting IFRSs for the first time at a given date; achieving comparability between first-time adopters and entities that already apply IFRSs is a secondary objective.’ [IFRS 1.BC10].
A revised IFRS 1 was issued in November 2008, which retains the substance of the previous version of the standard but within a changed structure. [IFRS 1.BC3B]. The standard has been further amended as a result of the IASB's annual improvements process, consequential amendments resulting from issuance of new standards, as well as to provide limited exceptions and exemptions that address specific matters. This approach always carried the risk that its complexity might eventually overwhelm its practical application. All these amendments are incorporated into the applicable sections of this chapter.
This chapter generally discusses the requirements of IFRS 1 for accounting periods beginning on or after 1 January 2020 unless otherwise stated and reflects the amendments to the original version of IFRS 1 referred to at 1.1 above.
This chapter does not deal with the first-time adoption of the earlier versions of IFRS 1. A detailed discussion of the first-time adoption using the earlier versions of the standard can be found in Chapter 5 of the previous editions of this book, International GAAP 2019 and prior editions. Especially, entities (e.g. insurance companies) that elect to continue applying IAS 39 – Financial Instruments: Recognition and Measurement – should refer to previous editions of IGAAP for guidance.
IFRS 1 defines the following terms in connection with the transition to IFRSs: [IFRS 1 Appendix A]
Date of transition to IFRSs: The beginning of the earliest period for which an entity presents full comparative information under IFRSs in its first IFRS financial statements.
First IFRS financial statements: The first annual financial statements in which an entity adopts International Financial Reporting Standards, by an explicit and unreserved statement of compliance with IFRSs.
First IFRS reporting period: The latest reporting period covered by an entity's first IFRS financial statements.
First-time adopter: An entity that presents its first IFRS financial statements.
International Financial Reporting Standards: Standards and Interpretations issued by the International Accounting Standards Board (IASB). They comprise:
Opening IFRS statement of financial position: An entity's statement of financial position (i.e. balance sheet) at the date of transition to IFRSs.
Previous GAAP: The basis of accounting that a first-time adopter used immediately before adopting IFRSs.
As at the time of writing, there was no specific project dealing with IFRS 1 other than the accounting treatment of cumulative translation differences of a subsidiary that becomes a first-time adopter later than its parent (see 5.9.1.A below). However, the IASB is currently pursuing a number of projects. Consideration will be given at the time of deliberations to how new standards or amendments may impact a first-time adopter of IFRSs and resulting consequential amendments to IFRS 1 will be included in the new standards or amendments. Entities contemplating conversion to IFRSs should monitor the IASB's agenda in order to anticipate how future standards or amendments may affect their conversions.
An entity's first IFRS financial statements are the first annual financial statements in which the entity adopts IFRSs, by making in those financial statements an explicit and unreserved statement of compliance with IFRSs. [IFRS 1.3, Appendix A]. The standard provides description of the circumstances in which an entity is a first-time adopter and therefore is within the scope of this standard. These circumstances are discussed below.
An entity's financial statements are considered its first IFRS financial statements, and thus fall within the scope of IFRS 1, when it presented its most recent previous financial statements:
An entity whose most recent previous financial statements contained an explicit and unreserved statement of compliance with IFRSs can never be considered a first-time adopter. This is the case even in the following circumstances:
The IASB could have introduced special rules that would have required an entity that significantly departed from IFRSs to apply IFRS 1. However, the IASB considered that such rules would lead to ‘complexity and uncertainty’. [IFRS 1.BC5]. In addition, this would have given entities applying ‘IFRS-lite’ (entities not applying IFRSs rigorously in all respects e.g. applying IFRSs except for certain standards and interpretations) an option to side step the requirements of IAS 8 – Accounting Policies, Changes in Accounting Estimates and Errors – to disclose departures from IFRSs as errors. [IFRS 1.BC6].
The following examples illustrate certain scenarios in connection with determining whether an entity is a first-time adopter.
It is clear that the scope of IFRS 1 is very much rules-based, which, as the example above illustrates, can lead to different answers in similar situations and sometimes to counter-intuitive answers.
An entity will be a first-time adopter if it has previously prepared financial statements in accordance with IFRSs but only for internal purposes. The entity may have:
IFRSs are intended to be applied in the preparation of general-purpose financial statements. Accordingly, financial statements that are restricted for specific use or incomplete reporting packages should not be deemed to comply with IFRSs. An entity that is a subsidiary of an IFRS reporting parent may be able to use the amounts reported for it in the group's financial statements when it adopts IFRSs for its own financial statements (see 5.9.1 below).
Finally, IFRS 1 applies also to a first-time adopter that did not present financial statements for previous periods. [IFRS 1.3(d)]. For example, when an entity transfers its operations into a new company prior to an issue to the public, the new company would be a first-time adopter if the entity never applied IFRSs in the past.
An entity that is already applying IFRSs in preparing its financial statements cannot apply IFRS 1 to changes in its accounting policies. Instead, such an entity should apply:
An entity that presents its first IFRS financial statements is a first-time adopter, [IFRS 1 Appendix A], and should apply IFRS 1 in preparing those financial statements. [IFRS 1.2(a)]. It should also apply the standard in each interim financial report that it presents in accordance with IAS 34 – Interim Financial Reporting – for a part of the period covered by its first IFRS financial statements. [IFRS 1.2(b)]. Therefore, a first-time adopter does not apply IFRS 1 to a ‘trading statement’, an ‘earnings press release’ or other financial report issued at its interim reporting date that is not described as complying with IAS 34 or IFRSs. In Extract 5.1 below, AGF Mutual Funds described its adoption of IFRSs in its interim or semi-annual financial statements.
IFRS 1 does not prohibit an entity from applying IFRS 1 more than once and, in fact, requires it in some cases. [IFRS 1.3(a)]. The IASB explained this issue with an example of an entity that had applied IFRS 1 in connection with a foreign listing, subsequently delisted from the foreign exchange and no longer presented IFRS financial statements, but is now adopting IFRSs again together with other entities in its local jurisdiction – see Example 5.4 below. This was clarified by the Board in the Annual Improvements to IFRSs 2009‑2011 Cycle, issued in May 2012. IFRS 1 was amended to clarify that an entity that stopped applying IFRSs in the past and chooses, or is required, to resume preparing IFRS financial statements has the option to apply IFRS 1 again. [IFRS 1.4A]. The Board reasoned that the entity should on cost-benefit grounds be allowed, rather than required, to apply IFRS 1 again. [IFRS1.BC6C]. If the entity chooses not to reapply IFRS 1, it must retrospectively restate its financial statements in accordance with IAS 8 as if it had never stopped applying IFRSs while disclosing (in addition to the disclosures required by IAS 8) the reasons why it stopped applying IFRSs and why it resumed applying IFRSs, as well as the reasons for choosing the retrospective restatement method. [IFRS1.4B, 23A, 23B].
An entity may prepare two complete sets of financial statements, e.g. one set of financial statements based on its national GAAP and another set for distribution to foreign investors based on US GAAP. Applying the definition of ‘previous GAAP’ (i.e. ‘the basis of accounting that a first-time adopter used immediately before adopting IFRSs’ [IFRS 1 Appendix A] ) to such a dual reporting entity is not straightforward, as the examples below illustrate:
An entity should apply judgement when the constraints above do not all identify the same GAAP as the previous GAAP.
IFRS 1 only requires disclosure of reconciliations between an entity's previous GAAP and IFRSs. However, it will be advisable for an entity to provide disclosures, on a voluntary basis, that contain sufficient information to enable users to understand the material reconciling items between the IFRS financial statements and the financial statements that were not prepared under its previous GAAP. Some national regulators (e.g. the US Securities and Exchange Commission), in fact, expect such disclosures (see 8.1.2 below).2
If an entity treats its national GAAP as its previous GAAP then it may want or need to present an explanation of the differences between US GAAP and IFRSs to aid former users of the US GAAP financial statements.
As illustrated in Extract 5.2 below, when Infosys adopted IFRSs it treated Indian GAAP as its previous GAAP even though it continued to report under Indian GAAP for statutory purposes. However, Infosys provided additional reconciliations between US GAAP and its previous GAAP.
One consequence of the ongoing harmonisation of accounting standards around the world is that many national GAAPs are now virtually identical to IFRSs. However, differences between these national GAAPs and IFRSs often exist regarding the scope, transitional provisions, effective dates and actual wording of standards. In addition, some national GAAPs contain accounting alternatives not permitted by IFRSs.
When an entity reporting under such a national GAAP (e.g. Singapore GAAP) adopts IFRSs there will often not be major changes required in its accounting policies to comply with IFRSs. However, under IFRS 1 it is not relevant whether or not a previous GAAP was very similar to IFRSs. Therefore, regardless of the absence of significant differences in accounting policies, that entity would be a first-time adopter when it includes an explicit and unreserved statement of compliance with IFRSs for the first time. So, even if the entity's accounting policies were already fully aligned with IFRSs:
Notwithstanding the above, we believe an entity that:
does not have to re-apply IFRS 1 the first time that it makes an explicit and unreserved statement of compliance with IFRSs.
For example, if an entity that meets the requirements described above decides to make an explicit and unreserved statement of compliance with IFRSs for the first time, either voluntarily or required to do so by a regulatory requirement related to an IPO, the entity would not be required to re-apply IFRS 1.
At the date of transition to IFRSs, an entity should prepare and present an opening IFRS statement of financial position that is the starting point for its accounting under IFRSs. [IFRS 1.6]. The date of transition to IFRSs is the beginning of the earliest comparative period presented in an entity's first IFRS financial statements. [IFRS 1 Appendix A]. Therefore the date of transition for an entity reporting under IFRSs for the first time at 31 December 2020 and presenting one year of comparative figures is 1 January 2019. For entities that adopt IFRSs at the beginning of a year, it is recommended that they consider the filing requirements for interim financial reports that a regulator in their jurisdiction may impose. For example, a regulator may require the opening IFRS statement of financial position to be presented in the first IFRS interim financial report even though this is not an IFRS 1 presentation requirement (see 6.6 below).
An entity's first annual IFRS financial statements must include at least three statements of financial position (i.e. balance sheets), two statements of profit or loss and other comprehensive income, two separate statements of profit or loss (if presented), two statements of cash flows and two statements of changes in equity and related notes for all statements presented, including the comparative information. [IFRS 1.21]. The beginning of the earliest comparative period for which the entity presents full comparative information under IFRSs will be treated as its date of transition to IFRSs. The diagram below shows how for an entity with a December year-end the above terms are related:
The diagram above also illustrates that there is a period of overlap, for the financial year 2018, which is reported first under the entity's previous GAAP and then as a comparative period under IFRSs. The following example illustrates how an entity should determine its date of transition to IFRSs.
The fundamental principle of IFRS 1 is to require full retrospective application of the standards in force at the end of an entity's first IFRS reporting period, but with limited exceptions for the opening IFRS statement of financial position. IFRS 1 requires a first-time adopter to use the same accounting policies in its opening IFRS statement of financial position and for all periods presented in its first IFRS financial statements. However, this may not be straightforward, since to achieve this, the entity should comply with each IFRS effective at the end of its first IFRS reporting period fully retrospectively, after taking into account a number of allowed exemptions from certain IFRSs and mandatory exceptions to retrospective application of other IFRSs in accordance with IFRS 1 (see 3.5 below). [IFRS 1.7].
The requirement to apply the same accounting policies to all periods also prohibits a first-time adopter from applying previous versions of standards that were effective at earlier dates. [IFRS 1.8]. As well as enhancing comparability, the IASB believes that this gives users comparative information that is based on IFRSs that are superior to superseded versions of those standards and avoids unnecessary costs. [IFRS 1.BC11].
For similar reasons, IFRS 1 also permits an entity to choose to apply either the current standard or a new standard that is not yet mandatory if that standard allows early application. [IFRS 1.8]. Whichever standard is selected it would need to be applied consistently throughout the periods presented in its first IFRS financial statements on a retrospective basis, unless IFRS 1 provides an exemption or an exception that permits or requires otherwise. [IFRS 1.BC11A]. The diagram below summarises these requirements in IFRS 1.
It should be noted that depending on the end of its first IFRS reporting period, an entity may or may not have the option to choose which version of a particular standard it may apply, as can be seen in the example below.
Unless the exceptions and exemptions at 3.5 below apply, in preparing its opening IFRS statement of financial position, an entity should:
Any change in accounting policies on adoption of IFRSs may cause changes in the amounts recorded under previous GAAP in respect of events and transactions that occurred before the date of transition. The effects of these changes should be recognised at the date of transition to IFRSs in retained earnings or, if appropriate, in another category of equity. [IFRS 1.11]. For example, an entity that applies the revaluation model under IAS 16 – Property, Plant and Equipment – (see Chapter 18) in its first IFRS financial statements would recognise the difference between cost and the revalued amount of property, plant and equipment in a revaluation reserve. By contrast, an entity that had applied a revaluation model under its previous GAAP, but decided to apply the cost model under IAS 16, would reallocate the revaluation reserve to retained earnings or a separate component of equity not described as a revaluation reserve (see 7.4.3 below).
A first-time adopter is under no obligation to ensure that its IFRS accounting policies are similar to or as close as possible to its previous GAAP accounting policies. Therefore, for example, a first-time adopter could adopt the IAS 16 revaluation model despite the fact that it applied a cost model under its previous GAAP or vice versa. However, a first-time adopter would need to take into account the guidance in IAS 8 to ensure that its choice of accounting policy results in information that is relevant and reliable. [IAS 8.10‑12].
The requirement to prepare an opening IFRS statement of financial position and ‘reset the clock’ at that date poses a number of challenges for first-time adopters. Even a first-time adopter that already applies a standard that is directly based on IFRSs may decide to restate items in its opening IFRS statement of financial position (see 2.3.1 above). This happens, for example, in the case of an entity applying a property, plant and equipment standard that is based on IAS 16 before an entity's date of transition to IFRSs because the entity may decide to use a deemed cost exemption for certain of its assets as allowed by IFRS 1.
Some exemptions in IFRS 1 refer to ‘fair value’ and ‘deemed cost’, which the standard defines as follows: [IFRS 1 Appendix A]
Deemed cost: An amount used as a surrogate for cost or depreciated cost at a given date. Subsequent depreciation or amortisation assumes that the entity had initially recognised the asset or liability at the given date and that its cost was equal to the deemed cost.
Fair value: The price that would be received to sell an asset or paid to transfer a liability in an orderly transaction between market participants at the measurement date (see Chapter 14 and IFRS 13 – Fair Value Measurement). The fair values determined by a first-time adopter should reflect the conditions that existed at the date for which they were determined, i.e. the first-time adopter should not apply hindsight in measuring the fair value at an earlier date.
The transitional provisions in other standards only apply to entities that already report under IFRSs. Therefore, a first-time adopter is not able to apply those transitional provisions unless specified by the requirements in IFRS 1. [IFRS 1.9]. Exceptions to this general rule are covered in the later parts of this chapter that deal with the exceptions to the retrospective application of other IFRSs (see 4 below) and the exemptions from other IFRSs (see 5 below).
It is important to note that the transition rules for first-time adopters and entities that already report under IFRSs may differ significantly.
The IASB considers ‘case by case when it issues a new IFRS whether a first-time adopter should apply that IFRS retrospectively or prospectively. The Board expects that retrospective application will be appropriate in most cases, given its primary objective of comparability over time within a first-time adopter's first IFRS financial statements. However, if the Board concludes in a particular case that prospective application by a first-time adopter is justified, it will amend the IFRS on first-time adoption of IFRSs.’ [IFRS 1.BC14].
IAS 8 allows exceptions from retrospective application for entities that cannot apply a requirement after making every reasonable effort to do so. There is no such relief in IFRS 1. The Interpretations Committee agreed ‘that there were potential issues, especially with respect to “old” items, such as property, plant and equipment. However, those issues could usually be resolved by using one of the transition options available in IFRS 1’ (see 3.5 below).3 For example, an entity could elect to use fair value as deemed cost at the transition date if an entity is unable to apply IAS 36 – Impairment of Assets – on a fully retrospective basis (see 7.12 below). Therefore no ‘impracticability relief’ was added to the standard for first-time adopters. The transition options usually involve using certain surrogate values as deemed cost and are discussed at 5.5 below.
IFRS 1 establishes two types of departure from the principle of full retrospective application of standards in force at the end of the first IFRS reporting period: [IFRS 1.12]
Mandatory exceptions: IFRS 1 prohibits retrospective application of IFRSs in some areas, particularly where this would require judgements by management about past conditions after the outcome of a particular transaction is already known. The mandatory exceptions in the standard cover the following situations: [IFRS 1.13‑17, Appendix B]
The reasoning behind most of the exceptions is that retrospective application of IFRSs in these situations could easily result in an unacceptable use of hindsight and lead to arbitrary or biased restatements, which would be neither relevant nor reliable.
Optional exemptions: In addition to the mandatory exceptions, IFRS 1 grants limited optional exemptions from the general requirement of full retrospective application of the standards in force at the end of an entity's first IFRS reporting period, considering the fact that the cost of complying with them would be likely to exceed the benefits to users of financial statements. The standard provides exemptions in relation to: [IFRS 1 Appendix C, D1]
In addition to the above, IFRS 1 grants certain exemptions that are intended to have short-term applications. These are included in Appendix E to the standard. At the time of this update, there are no short-term exemptions that are expected to apply beyond 2019. First-time adopters should monitor IFRS developments for any new short-term exemptions that may be issued after the publication of this edition.
It is specifically prohibited under IFRS 1 to apply exemptions by analogy to other items. [IFRS 1.18].
Application of these exemptions is entirely optional, i.e. a first-time adopter can pick and choose the exemptions that it wants to apply. Importantly, the IASB did not establish a hierarchy of exemptions. Therefore, when an item is covered by more than one exemption, a first-time adopter has a free choice in determining the order in which it applies the exemptions.
IFRS 1 provides a number of mandatory exceptions that specifically prohibit retrospective application of some aspects of other IFRSs as listed in 3.5 above. Each of the exceptions is explained in detail below.
IFRS 1 requires an entity to use estimates under IFRSs that are consistent with the estimates made for the same date under its previous GAAP – after adjusting for any difference in accounting policy – unless there is objective evidence that those estimates were in error in accordance with IAS 8. [IFRS 1.14, IAS 8.5].
Under IFRS 1, an entity cannot apply hindsight and make ‘better’ estimates when it prepares its first IFRS financial statements. This also means that an entity is not allowed to consider subsequent events that provide evidence of conditions that existed at that date, but that came to light after the date its previous GAAP financial statements were finalised. If an estimate made under previous GAAP requires adjustment because of new information after the relevant date, an entity treats this information in the same way as a non-adjusting event after the reporting period under IAS 10 – Events after the Reporting Period. Effectively, the IASB wishes to prevent entities from using hindsight to ‘clean up’ their balance sheets as part of the preparation of the opening IFRS statement of financial position. In addition, the exception also ensures that a first-time adopter need not conduct a search for, and change the accounting for, events that might have otherwise qualified as adjusting events.
IFRS 1 provides the following guidance on estimates:
In both situations, it accounts for the revisions to those estimates in the period in which it makes the revisions in the same way as a non-adjusting event after the reporting period under IAS 10. [IFRS 1.15, IG3, IAS 10.10].
The requirements above apply both to estimates made in respect of the date of transition to IFRSs and to those in respect of any of the comparative periods, in which case the reference to the date of transition to IFRSs above are replaced by references to the end of that comparative period. [IFRS 1.17].
The flowchart below shows the decision-making process that an entity needs to apply in dealing with estimates at the transition date and during any of the comparative periods included in its first IFRS financial statements.
The general prohibition in IFRS 1 on the use of hindsight in making estimates about past transactions does not override the requirements in other IFRSs that base classifications or measurements on circumstances existing at a particular date, e.g. the distinction between finance leases and operating leases for a lessor. [IFRS 1.IG4].
IFRS 1 requires an entity that is unable to determine whether a particular portion of an adjustment is a transitional adjustment or a change in estimate to treat that portion as a change in accounting estimate under IAS 8, with appropriate disclosures as required by IAS 8. [IFRS 1.IG58B, IAS 8.32‑40]. The distinction between changes in accounting policies and changes in accounting estimates is discussed in detail in Chapter 3.
If a first-time adopter concludes that estimates under previous GAAP were made in error, it should distinguish the correction of those errors from changes in accounting policies in its reconciliations from previous GAAP to IFRSs (see 6.3.1 below). [IFRS 1.26].
The example below illustrates how an entity should deal with estimates on the transition date and in comparative periods included in its first IFRS financial statements. [IFRS 1.IG Example 1].
Some of the potential consequences of applying IAS 37 resulting in changes in the way an entity accounts for provisions are addressed at 7.13 below.
IFRS 1 requires a first-time adopter to apply the derecognition requirements in IFRS 9 – Financial Instruments – prospectively to transactions occurring on or after the date of transition to IFRSs but need not apply them retrospectively to transactions that had already been derecognised. For example, if a first-time adopter derecognised non-derivative financial assets or non-derivative financial liabilities under its previous GAAP as a result of a transaction that occurred before the date of transition to IFRSs, the entity shall not recognise those assets or liabilities under IFRSs unless they qualify for recognition as a result of a later transaction or event. [IFRS 1.B2]. However, a first-time adopter may apply the derecognition requirements in IFRS 9 retrospectively from a date of the entity's choosing, provided that the information needed to apply IFRS 9 to financial assets and financial liabilities derecognised as a result of past transactions was obtained at the time of initially accounting for those transactions. [IFRS 1.B3]. This will effectively prevent most first-time adopters from restating transactions that occurred before the date of transition to IFRSs.
A first-time adopter that derecognised non-derivative financial assets and financial liabilities before the date of transition to IFRSs and chose not to restate retrospectively will not have to recognise these items under IFRSs even if they meet the IFRS 9 recognition criteria. [IFRS 1.IG53‑54]. However, IFRS 10 – Consolidated Financial Statements – contains no specific transitional or first-time adoption provisions except for those for non-controlling interests (see 4.8 below). Accordingly, its consolidation requirements should be applied fully retrospectively by first-time adopters. For example, an entity may have derecognised, under its previous GAAP, non-derivative financial assets and financial liabilities when they were transferred to a structured entity as part of a securitisation programme. If that entity is considered to be a controlled entity under IFRS 10, those assets and liabilities will be re-recognised on transition to IFRSs by way of the application of IFRS 10 rather than through application of IFRS 9. Of course, if the structured entity itself then subsequently achieved derecognition of the items concerned under the entity's previous GAAP (other than by transfer to another structured entity or member of the entity's group), then the items remain derecognised on transition. Some arrangements for the transfer of assets, particularly securitisations, may last for some time, with the result that transfers might be made both before and after (or on) the date of transition to IFRSs under the same arrangement. IFRS 1 clarifies that transfers made under such arrangements fall within the first-time adoption exception only if they occurred before the date of transition to IFRSs. Transfers on or after the date of transition to IFRSs are subject to the full requirements of IFRS 9. [IFRS 1.IG53].
From 4.4 to 4.7 below, we discuss the hedge accounting treatment for first-time adopters under IFRS 9.
First-time adoption issues relating to hedge accounting in the opening IFRS statement of financial position are discussed at 4.5 below and subsequent measurement issues are discussed in 4.6 below. Hedge accounting is dealt with comprehensively in Chapter 53.
Summary:
Paragraphs B5 and B6 of IFRS 1 refer to ‘hedge relationship of a type’ and ‘conditions for hedge accounting’ when specifying the recognition of hedging relationships in the opening IFRS statement of financial position and subsequent accounting, respectively. These descriptions were not modified to reflect requirements of IFRS 9. However, IFRS 9 does not set out hedge relationship types or conditions for hedge accounting. Instead, it sets out qualifying criteria in paragraph 6.4.1, which consist of (a) eligibility, (b) formal designation and documentation, and (c) hedge effectiveness. Therefore, the wording in paragraphs B5 and B6 of IFRS 1 is obsolete, and IFRS 1 is relatively unclear as to whether the same two-step approach above (i.e. ‘type’ test and ‘condition’ test) continues to apply.
In our view, the IASB did not intend to change the requirements of IFRS 1 for recognising a hedging relationship in the opening IFRS statement of financial position or the subsequent accounting upon issuance of IFRS 9 and we expect the IASB to amend the wording to clarify that the reference to ‘a hedging relationship of a type that does not qualify for hedge accounting’ in paragraph B5 of Appendix B to IFRS 1 relates only to the qualifying criterion in paragraph 6.4.1(a) of IFRS 9 (i.e. eligible hedging instruments and hedged items) and the ‘conditions for hedge accounting’ in paragraph B6 of Appendix B to IFRS 1 relates to the qualifying criteria in paragraph 6.4.1(b)-(c) of IFRS 9. Discussions in 4.4 to 4.7 below are based on this view.
A transition requirement of IFRS 9 for hedge accounting permits an existing IFRS user to choose as its accounting policy to continue to apply the hedge accounting requirements of IAS 39 instead of the requirements in Chapter 6 of IFRS 9. [IFRS 9.7.2.21]. First-time adopters do not have this choice because paragraph 9 of IFRS 1 prohibits first-time adopters from applying the transition provisions in other IFRSs when adopting IFRS, except as specified in Appendices B-E. [IFRS 1.9]. Further, paragraphs B4 to B6 of IFRS 1 contain mandatory exceptions for hedge accounting, but they do not refer to the transition requirements of IFRS 9, and the basis for conclusion attached to IFRS 9 under the heading ‘Transition related to the hedge accounting requirements’ states ‘The IASB decided not to change the requirements of IFRS 1 for hedge accounting. The IASB noted that a first-time adopter would need to look at the entire population of possible hedging relationships and assess which ones would meet the qualifying criteria of the new hedge accounting model’. [IFRS 9.BC7.52]. Accordingly, a first-time adopter is not allowed to apply IAS 39 to a macro-hedging arrangement and its various components would have to be separately accounted for under IFRS 9. This is in contrast to an existing IFRS user, who would be permitted to apply IAS39 hedge accounting.
Under its previous GAAP an entity's accounting policies might have included a number of accounting treatments for derivatives that formed part of a hedge relationship. For example, accounting policies might have included those where the derivative was:
Whatever the previous accounting treatment, a first-time adopter should isolate and separately account for all derivatives in its opening IFRS statement of financial position as assets or liabilities measured at fair value. [IFRS 1.B4(a)].
All derivatives are measured at fair value through profit or loss, other than those that are financial guarantee contracts, a commitment to provide a loan at a below-market interest rate, or a loan commitment that is subject to the impairment requirements of IFRS 9, as well as those that are designated and effective as hedging instruments. Accordingly, the difference between the previous carrying amount of these derivatives (which may have been zero) and their fair value should be recognised as an adjustment of the balance of retained earnings at the date of transition to IFRSs. [IFRS 1.IG58A]. If an entity cannot determine whether a particular portion of an adjustment is a transition adjustment (i.e. a change in accounting policy) or a change in estimate, it must treat that portion as a change in accounting estimate. [IFRS 1.IG58B, IAS 8.32‑40]. The distinction between changes in accounting policies and changes in accounting estimates is discussed in detail in Chapter 3 at 4.2.
Hedge accounting policies under an entity's previous GAAP might also have included one or both of the following accounting treatments:
In all cases, an entity is required to eliminate deferred gains and losses arising on derivatives that were reported in accordance with previous GAAP as if they were assets or liabilities. [IFRS 1.B4(b)]. In contrast to adjustments made to restate derivatives at fair value, the implementation guidance does not specify in general terms how to deal with adjustments to eliminate deferred gains or losses, i.e. whether they should be taken to retained earnings or a separate component of equity.
The requirement to eliminate deferred gains and losses does not appear to extend to those that have been included in the carrying amount of other assets or liabilities that will continue to be recognised under IFRSs. For example, under an entity's previous GAAP, the carrying amount of non-financial assets such as inventories or property, plant and equipment might have included the equivalent of a basis adjustment (i.e. hedging gains or losses were considered an integral part of the asset's cost). Of course, entities should also consider any other provisions of IFRS 1 that apply to those hedged items, e.g. whether any of the exemptions such as those for business combinations (see 5.2 below) or deemed cost (see 5.5 below) will be used.
The following diagram illustrates the treatment of hedge accounting in the opening IFRS statement of financial position and subsequent periods. Hedge accounting in the opening IFRS statement of financial position will be discussed in the sub-sections following the diagram and hedge accounting after transition to IFRSs is dealt with at 4.6 below.
The standard states that a first-time adopter must not reflect a hedging relationship in its opening IFRS statement of financial position if that hedging relationship is of a type that does not qualify for hedge accounting under IFRS 9, which consists only of eligible hedging instruments and eligible hedged items in paragraph 6.4.1(a). As examples of this it cites many hedging relationships where the hedging instrument is a stand-alone written option or a net written option; or where the hedged item is a net position in a cash flow hedge for another risk other than foreign currency risk. [IFRS 1.B5]. Previous GAAP hedge documentation and effectiveness that were not fully compliant with the criteria in paragraph 6.4.1(b)-(c) of IFRS 9 do not mean that the hedge relationship is of a type that does not qualify for hedge accounting under IFRS 9. (See 4.6 below for requirements for post transition date hedge accounting).
However, if an entity designated a net position as a hedged item under its previous GAAP, it may designate as a hedged item under IFRS an individual item within that net position, or a net position that meets the requirements in paragraph 6.6.1 of IFRS 9, provided that it does so no later than the date of transition to IFRSs. [IFRS 1.B5]. In other words, such designation would allow the hedge relationship to be reflected in the opening IFRS statement of financial position.
On the other hand, a hedge relationship designated under an entity's previous GAAP should be reflected in its opening IFRS statement of financial position if that hedging relationship consists of eligible hedging instruments and eligible hedged items in paragraph 6.4.1(a), regardless of whether or not the hedge designation, documentation and effectiveness for hedge accounting under IFRS 9 (paragraph 6.4.1 (b)-(c)) are met on the transition date. [IFRS 1.B4-B6, IG60A-60B].
A first-time adopter is not permitted to designate hedges retrospectively in relation to transactions entered into before the date of transition to IFRSs. [IFRS 1.B6]. Instead it must apply the requirements prospectively.
In the basis for conclusions, it is explained that:
While the IASB referred to IAS 39's criteria in the basis for conclusion quoted above, it has since reinforced the basis for conclusion when it issued IFRS 9, which says the following:
If a first-time adopter, in anticipation of the adoption of IFRS, decides to designate a transaction as a hedge under IFRS 9 and completes the required documentation sometime before the transition date to IFRS, some have questioned whether upon adoption of IFRS hedge accounting should be applied prior to the transition date. In our view, as long as the hedge is properly designated and documented in accordance with IFRS 9.6.4.1 prior to the date of transition, the first-time adopter should apply hedge accounting from the date that it met the requirement. As explained in 4.5.2.A above, a first-time adopter cannot designate a transaction retrospectively as a hedge under IFRS.
A first-time adopter may have deferred gains and losses on a cash flow hedge of a forecast transaction under its previous GAAP. If, at the date of transition, the hedged forecast transaction is not highly probable, but is expected to occur, the entire deferred gain or loss should be recognised in the cash flow hedge reserve within equity. [IFRS 1.IG60B]. This is consistent with the treatment required for deferred gains or losses on cash flow hedges applicable after the transition to IFRS (other than losses not expected to be recovered) (see Chapter 53). [IFRS 9.6.5.11].
How should an entity deal with such a hedge if, at the date of transition to IFRSs, the forecast transaction is highly probable? It would make no sense if the hedge of the transaction that is expected to occur were required to be reflected in the opening IFRS statement of financial position, but the hedge of the highly probable forecast transaction (which is clearly a ‘better’ hedge) were not.
Therefore, it must follow that a cash flow hedge should be reflected in the opening IFRS statement of financial position in the way set out above if the hedged item is a forecast transaction that is highly probable (see Example 5.9 below). Similarly, it follows that a cash flow hedge of the variability in cash flows attributable to a particular risk associated with a recognised asset or liability (such as all or some future interest payments on variable rate debt) should also be reflected in the opening IFRS statement of financial position. To do otherwise would allow an entity to choose not to designate (in accordance with IFRS 9) certain cash flow hedges, say those that are in a loss position, until one day after its date of transition, thereby allowing associated hedging losses to bypass profit or loss completely. However, this would effectively result in the retrospective de-designation of hedges to achieve a desired result, thereby breaching the general principle of IFRS 1 (i.e. a first-time adopter cannot designate a hedge relationship retrospectively).
If, at the date of transition to IFRSs, the forecast transaction was not expected to occur, consistent with the requirements of paragraphs 6.5.6‑6.5.7 and 6.5.12(b) of IFRS 9, a first-time adopter should reclassify any related deferred gains and losses that are not expected to be recovered into retained earnings.
If a first-time adopter has, under its previous GAAP, deferred or not recognised gains and losses on a fair value hedge of a hedged item that is not measured at fair value, the entity should adjust the carrying amount of the hedged item at the date of transition. The adjustment, which is essentially the effective part of the hedge that was not recognised in the carrying amount of the hedged item under the previous GAAP, should be calculated as the lower of:
IFRS 1 does not provide explicit guidance on reflecting foreign currency net investment hedges in the opening IFRS statement of financial position. However, IFRS 9 requires that ongoing IFRS reporting entities account for those hedges similarly to cash flow hedges. [IFRS 9.6.5.13]. It follows that the first-time adoption provisions regarding cash flow hedges (see 4.5.3 above) also apply to hedges of foreign currency net investments.
A first-time adopter that applies the exemption to reset cumulative translation differences to zero (see 5.7 below) should not reclassify pre-transition gains and losses on the hedging instruments that were recognised in equity under previous GAAP to profit or loss upon disposal of a foreign operation. Instead, those pre-transition gains and losses should be recognised in the opening balance of retained earnings to avoid a disparity between the treatment of the gains and losses on the hedged item and the hedging instrument. This means that the requirement to reset the cumulative translation differences also applies to related gains and losses on hedging instruments.
The implementation guidance explains that hedge accounting can be applied prospectively only from the date the hedge relationship is fully designated and documented. In other words, after the transition to IFRS, hedge accounting under IFRS 9 can be applied only if the qualifying criteria in paragraph 6.4.1 of IFRS 9 are met. Therefore, if the hedging instrument is still held at the date of transition to IFRSs, the designation, documentation and effectiveness of a hedge relationship must be completed on or before that date if the hedge relationship is to qualify for hedge accounting from that date. [IFRS 1.IG60].
Before the date of transition to IFRSs an entity may have designated as a hedge a transaction under previous GAAP that is a type that qualifies for hedge accounting under IFRS 9, which consists only of eligible hedging instruments and eligible hedged items in paragraph 6.4.1(a), but does not meet other qualifying criteria in IFRS 9 (i.e. 6.4.1 (b)‑(c)) at the transition date. In these cases it should follow the general requirements in IFRS 9 for discontinuing hedge accounting subsequent to the date of transition to IFRSs – these are dealt with in Chapter 53. [IFRS 1.B6].
For cash flow hedges, any net cumulative gain or loss that was reclassified to the cash flow hedge reserve on the transition date to IFRS (see 4.5.3 above) should remain there until: [IFRS 1.IG60B]
The requirements above do little more than reiterate the general requirements of IFRS 9, i.e. that hedge accounting can only be applied prospectively if the qualifying criteria are met, and entities should experience few interpretative problems in dealing with this aspect of the hedge accounting requirements.
The following examples illustrate the guidance considered at 4.5 to 4.6 above.
A first-time adopter must apply IFRS 10 retrospectively, except for the following requirements that apply prospectively from its date of transition to IFRSs: [IFRS 1.B7]
However, if a first-time adopter restates any business combination that occurred prior to its date of transition to comply with IFRS 3 – Business Combinations – it must also apply IFRS 10, including these requirements, from that date onwards (see 5.2.2 below). [IFRS 1.C1].
IFRS 9 requires a financial asset to be measured at amortised cost if it meets two tests that deal with the nature of the business that holds the assets and the nature of the cash flows arising on those assets. [IFRS 9.4.1.2]. Also, the standard requires a financial asset to be measured at fair value through other comprehensive income if certain conditions are met. [IFRS 9.4.1.2A]. These are described in detail in Chapter 48. Paragraph B8 of IFRS 1 requires a first-time adopter to assess whether a financial asset meets the conditions on the basis of the facts and circumstances that exist at the date of transition to IFRSs.
If it is impracticable to assess a modified time value of money element under paragraphs B4.1.9B-B4.1.9D of IFRS 9 on the basis of the facts and circumstances that exist at the transition date, the first-time adopter should assess the contractual cash flow characteristics of that financial asset on the basis of the facts and circumstances that existed at that date without taking into account the requirements related to the modification of the time value of money element in paragraphs B4.1.9B-B4.1.9D of IFRS 9. [IFRS 1.B8A]. Similarly, if it is impracticable to assess whether the fair value of a prepayment feature is insignificant under B4.1.12(c) of IFRS 9 on the basis of the facts and circumstances that exist at the transition date, paragraphs B8B of IFRS 1 require an entity to assess the contractual cash flow characteristics of that financial asset on the basis of the facts and circumstances that existed at that date without taking into account the exception for prepayment features in B4.1.12 of IFRS 9. These are discussed in more detail in Chapter 48 at 6.
Paragraph B8C of IFRS 1 states that if it is impracticable (as defined in IAS 8) for an entity to apply retrospectively the effective interest method in IFRS 9, the fair value of the financial asset or the financial liability at the date of transition to IFRSs should be the new gross carrying amount of that financial asset or the new amortised cost of that financial liability at the date of transition to IFRSs.
Paragraph B8D of IFRS 1 requires a first-time adopter to apply the impairment requirements in section 5.5 of IFRS 9 retrospectively subject to paragraphs B8E‑B8G of IFRS 1.
At the date of transition to IFRSs, paragraph B8E of IFRS 1 requires a first-time adopter to use reasonable and supportable information that is available without undue cost or effort to determine the credit risk at the date that the financial instruments were initially recognised (or for loan commitments and financial guarantee contracts the date that the entity became a party to the irrevocable commitment in accordance with paragraph 5.5.6 of IFRS 9) and compare that to the credit risk at the date of transition to IFRSs. [IFRS 9.B7.2.2-B7.2.3].
A first-time adopter may apply the guidance in paragraph B8F of IFRS 1 to determine whether there has been a significant increase in credit risk since initial recognition. However, a first-time adopter would not be required to make that assessment if that would require undue cost or effort. Paragraph B8G of IFRS 1 requires such a first-time adopter to recognise a loss allowance at an amount equal to lifetime expected credit losses at each reporting date until that financial instrument is derecognised (unless that financial asset is low credit risk at a reporting date).
When IFRS 9 requires an entity to separate an embedded derivative from a host contract, the initial carrying amounts of the components at the date the instrument first satisfied the recognition criteria in IFRS 9 should reflect circumstances that existed at that date. If the initial carrying amounts of the embedded derivative and host contract cannot be determined reliably, the entire combined contract should be designated at fair value through profit or loss (IFRS 1.IG55).
Paragraph B9 of IFRS 1 requires a first-time adopter to assess whether an embedded derivative should be separated from the host contract and accounted for as a derivative based on conditions that existed at the later of the date it first became a party to the contract and the date a reassessment is required by IFRS 9. [IFRS 9.B4.3.11]. It should be noted that IFRS 9 does not permit embedded derivatives to be separated from host contracts that are financial assets.
It is common practice in certain countries for the government to grant loans to entities at below-market interest rates in order to promote economic development. A first-time adopter may not have recognised and measured such loans in its previous GAAP financial statements on a basis that complies with IFRSs. IAS 20 – Accounting for Government Grants and Disclosure of Government Assistance – requires such loans to be recognised at fair value with the effect of the below-market interest rate separately accounted for as a government grant. [IAS 20.10A]. The IASB has provided transition relief to first-time adopters in the form of an exception that requires government loans received to be classified as a financial liability or an equity instrument in accordance with IAS 32 – Financial Instruments: Presentation – and to apply the requirements in IFRS 9 and IAS 20 prospectively to government loans existing at the date of transition to IFRSs. Therefore a first-time adopter will not recognise the corresponding benefit of the government loan at a below-market rate of interest as a government grant. A first-time adopter that did not, under its previous GAAP, recognise and measure a government loan at a below-market rate of interest on a basis consistent with IFRS requirements will use its previous GAAP carrying amount of the loan at the date of transition as the carrying amount of the loan in the opening IFRS statement of financial position and apply IFRS 9 to the measurement of such loans after the date of transition to IFRSs. [IFRS 1.B10].
Alternatively, an entity may apply the requirements in IFRS 9 and IAS 20 retrospectively to any government loan originated before the date of transition, provided the information needed to do so had been obtained when it first accounted for the loan under previous GAAP. [IFRS 1.B11].
The requirements and guidance above do not preclude an entity from designating previously recognised financial instruments at fair value through profit or loss (see 5.11.2 below). [IFRS 1.B12].
The requirements that a government loan with a below-market interest rate is not restated from its previous GAAP amount are illustrated in the following example:
IFRS 17 – Insurance Contracts – was issued in May 2017 and will be effective for annual reporting periods beginning on or after 1 January 2021 (however, an effective date of 1 January 2022 is proposed in the Exposure Draft issued in June 2019 as a part of a revision of the standard to address implementation challenges raised by stakeholders). Early application is permitted for entities that apply IFRS 9 and IFRS 15 – Revenue from Contracts with Customers – on or before the date of initial application of IFRS 17. An entity must apply the transition provisions in paragraphs C1 to C24 and C28 in Appendix C of IFRS 17 to contracts within the scope of IFRS 17 (see Chapter 56 – Insurance Contracts – at 17). The references in those paragraphs in IFRS 17 to the transition date must be read as the date of transition to IFRS. [IFRS 1.B13]. Therefore first time adopters and entities moving from IFRS 4 – Insurance Contracts – will apply the same transition rules.
As noted at 3.5 above, IFRS 1 grants limited optional exemptions from the general requirement of full retrospective application of the standards in force at the end of an entity's first IFRS reporting period. [IFRS 1.12(b)]. Each of these exemptions is explained in detail below.
The business combinations exemption in IFRS 1 is probably the single most important exemption in the standard, as it permits a first-time adopter not to restate business combinations that occurred prior to its date of transition to IFRSs. The detailed guidance on the application of the business combinations exemption is contained in Appendix C to IFRS 1 and is organised in the sections as follows: [IFRS 1 Appendix C]
The business combinations exemption applies only to business combinations that occurred before the date of transition to IFRSs and only to the acquisition of businesses as defined under IFRS 3 (see 5.2.1 below). [IFRS 1 Appendix C]. Therefore, it does not apply to a transaction that, for example, IFRSs treat as an acquisition of an asset (see 5.2.1.A below).
As noted above, the business combination exemption applies only to the acquisition of a business as defined under IFRS 3. Therefore, a first-time adopter needs to consider whether past transactions would qualify as business combinations under IFRS 3. That standard defines a business combination as ‘a transaction or other event in which an acquirer obtains control of one or more businesses. Transactions sometimes referred to as “true mergers” or “mergers of equals” are also business combinations as that term is used in this IFRS.’ [IFRS 3 Appendix A]. The definition of a business, which was amended in 2018, is ‘an integrated set of activities and assets that is capable of being conducted and managed for the purpose of providing goods or services to customers, generating investment income (such as dividends or interest) or generating other income from ordinary activities.’ [IFRS 3 Appendix A]. In addition, IFRS 3 states that ‘if the assets acquired are not a business, the reporting entity shall account for the transaction or other event as an asset acquisition’ (see 5.2.1.A below). [IFRS 3.3]. Distinguishing a business combination from an asset acquisition is described in detail in Chapter 9.
In October 2012, the IASB issued Investment Entities (Amendments to IFRS 10, IFRS 12 and IAS 27) (see 5.9.5 below). Amongst other changes, the amendment also makes it clear that Appendix C of IFRS 1, which deals with the business combinations exemption, should be applied only to business combinations within the scope of IFRS 3. This means that the exemption does not apply to mergers of entities that are not business combinations under IFRS 3. So a first-time adopter which had such mergers under previous GAAP should retrospectively apply IFRS applicable to those mergers. If the mergers are those of entities under common control, as there is no specific guidance under IFRS on accounting for them, we discuss this issue in Chapter 10.
Because IFRS 3 provides such a specific definition of a business combination (as described in Chapter 9), it is possible that under some national GAAPs, transactions that are not business combinations under IFRS 3, e.g. asset acquisitions, may have been accounted for as if they were business combinations. If so, a first-time adopter will need to restate such transactions, as discussed in the following example.
If in the example above the entity had accounted for the transaction as an asset acquisition rather than a business combination under previous GAAP, it would need to determine whether the transaction meets the definition of a business combination in IFRS 3 in order to qualify for use of the exemption.
A first-time adopter must account for business combinations occurring after its date of transition under IFRS 3, i.e. any business combinations during the comparative periods need to be restated in accordance with IFRS 3 while it may elect not to apply IFRS 3 retrospectively to business combinations occurring before the date of transition. However, if a first-time adopter does restate a business combination occurring prior to its date of transition to comply with IFRS 3 it must also restate any subsequent business combinations under IFRS 3 and apply IFRS 10 from that date onwards. [IFRS 1.C1]. In other words, as shown on the time line below, a first-time adopter is allowed to choose any date in the past from which it wants to account for all business combinations under IFRS 3 and would not restate business combinations that occurred prior to such date. It must be noted that a first-time adopter availing itself of this option is required to apply the version of IFRS 3 effective at the end of its first IFRS reporting period to any retrospectively restated business combinations.
Even if a first-time adopter elects not to restate certain business combinations, it may still need to restate the carrying amounts of the acquired assets and assumed liabilities, as described at 5.2.4 below.
Although there is no restriction that prevents retrospective application by a first-time adopter of IFRS 3 to all past business combinations, in our opinion, a first-time adopter should not restate business combinations under IFRS 3 that occurred before the date of transition when this would require use of hindsight.
Extracts 5.3 below and 5.12 at 6.3 below illustrate the typical disclosure made by entities that opted not to restate business combinations that occurred before their date of transition to IFRSs, while Extract 5.4 below illustrates disclosures by an entity that chose to restate certain business combinations that occurred prior to its date of transition.
The exemption for past business combinations applies also to past acquisitions of investments in associates, interests in joint ventures and interests in joint operations (in which the activity of the joint operation constitutes a business, as defined in IFRS 3). The date selected for the first restatement of business combinations will also be applied to the restatement of these other acquisitions. [IFRS 1.C5].
The application of the business combination exemptions in IFRS 1 has the following consequences for that business combination (see 5.2.3 to 5.2.10 below).
IFRS 3 mandates a business combination to be accounted for as an acquisition or reverse acquisition. An entity's previous GAAP may be based on a different definition of, for example, a business combination, an acquisition, a merger and a reverse acquisition. An important benefit of the business combinations exemption is that a first-time adopter will not have to determine the classification of past business combinations in accordance with IFRS 3. [IFRS 1.C4(a)]. For example, a business combination that was accounted for as a merger or uniting of interests using the pooling-of-interests method under an entity's previous GAAP will not have to be reclassified and accounted for under the acquisition method, nor will a restatement be required if the business combination would have been classified under IFRS 3 as a reverse acquisition by the acquiree. However, an entity may still elect to do so if it so wishes without using hindsight (see 5.2.2 above).
In its opening IFRS statement of financial position, a first-time adopter should recognise all assets acquired and liabilities assumed in a past business combination, with the exception of: [IFRS 1.C4(b)]
The entity must exclude items it recognised under its previous GAAP that do not qualify for recognition as an asset or liability under IFRSs (see 5.2.4.A below).
If the first-time adopter recognised under its previous GAAP items that do not qualify for recognition under IFRSs, these must be excluded from the opening IFRS statement of financial position.
An intangible asset, acquired as part of a business combination, that does not qualify for recognition as an asset under IAS 38 – Intangible Assets – should be derecognised, with the related deferred tax and non-controlling interests, with an offsetting change to goodwill, unless the entity previously deducted goodwill directly from equity under its previous GAAP (see 5.2.5 below).
All other changes resulting from derecognition of such assets and liabilities should be accounted for as adjustments of retained earnings or another category of equity, if appropriate. [IFRS 1.C4(c)]. For example:
An asset acquired or a liability assumed in a past business combination may not have been recognised under the entity's previous GAAP. However, this does not mean that such items have a deemed cost of zero in the opening IFRS statement of financial position. Instead, the acquirer recognises and measures those items in its opening IFRS statement of financial position on the basis that IFRSs would require in the statement of financial position of the acquiree. [IFRS 1.C4(f)].
If the acquirer had not recognised an assumed contingent liability under its previous GAAP that still exists at the date of transition to IFRSs, the acquirer should recognise that contingent liability at that date unless IAS 37 would prohibit its recognition in the financial statements of the acquiree. [IFRS 1.C4(f)].
The change resulting from the recognition of such assets and liabilities should be accounted for as an adjustment of retained earnings or another category of equity, if appropriate. However, if the change results from the recognition of an intangible asset that was previously subsumed within goodwill, it should be accounted for as an adjustment of that goodwill (see 5.2.5 below). [IFRS 1.C4(b), C4(g)(i)].
Intangible assets acquired as part of a business combination that were not recognised under a first-time adopter's previous GAAP will rarely be recognised in the opening IFRS statement of financial position because either: (1) they cannot be capitalised in the acquiree's own statement of financial position under IAS 38; or (2) capitalisation would require the use of hindsight which is not permitted under IAS 38 (see 7.14 below).
For assets and liabilities that are accounted for on a cost basis under IFRSs, the carrying amount in accordance with previous GAAP of assets acquired and liabilities assumed in that business combination is their deemed cost immediately after the business combination. This deemed cost is the basis for cost-based depreciation or amortisation from the date of the business combination. [IFRS 1.C4(e)].
The standard does not specifically define ‘immediately after the business combination’, but it is commonly understood that this takes account of the final determination of the purchase price allocation and final completion of purchase accounting. In other words, a first-time adopter would not use the provisionally determined fair values of assets acquired and liabilities assumed in applying the business combinations exemption.
IFRS 1 is silent as to whether the relevant carrying amounts of the identifiable net assets and goodwill are those that appeared in the financial statements drawn up immediately before the transition date or any restated balance appearing in a later set of previous GAAP accounts. Since the adjustments that were made under previous GAAP effectively resulted in a restatement of the balances at the transition date in a manner that is consistent with the approach permitted by IFRSs, it is in our opinion appropriate to reflect those adjustments in the opening IFRS statement of financial position. Since the adjustments are effectively made as at the transition date, it is also appropriate to use the window period permitted by previous GAAP provided that this does not extend into the first IFRS reporting period. This is because any restatements in that period can only be made in accordance with IFRS 3. In effect, the phrase ‘immediately after the business combination’ in paragraph C4(e) of IFRS 1 should be interpreted as including a window period allowed by the previous GAAP that ends at the earlier of the end of the window period and the beginning of the first IFRS reporting period.
Although the use of cost-based measurements under previous GAAP might be considered inconsistent with the requirements of IFRSs for assets and liabilities that were not acquired in a business combination, the IASB did not identify any situations in a business combination in which it would not be acceptable to bring forward cost-based measurements made under previous GAAP. [IFRS 1.BC36]. For example, assume an entity that adopts IFRSs with a transition date of 1 January 2019 and, as required, applies IFRS 3 to business combinations occurring on or after 1 January 2019. Under the entity's previous GAAP, it acquired a business in 2013 and the purchase accounting resulted in negative goodwill. At that time, the negative goodwill was eliminated by reducing the amounts assigned to long-lived assets (PP&E and intangible assets) on a pro rata basis. In this situation, the negative goodwill adjustment to PP&E and intangible assets is ‘grandfathered’ and is not adjusted in the opening IFRS statement of financial position. The negative goodwill adjustment to PP&E and intangible assets was part of the original purchase accounting and is not a subsequent measurement difference between completing the purchase price allocation and 1 January 2019 and therefore the adjustment forms part of the deemed cost of PP&E and intangible assets.
By contrast, under previous GAAP, the entity may have recognised amortisation of intangible assets from the date of acquisition. If this amortisation is not in compliance with IAS 38, it is not ‘grandfathered’ under the business combination exemption and therefore should be reversed on transition (note that the adjusted carrying amount should be tested for impairment if there are impairment indicators pursuant to the requirements of IAS 36 at the date of transition; see 7.12 below).
IFRS 1 makes it clear that in-process research and development (IPR&D) that was included within goodwill under an entity's previous GAAP should not be recognised separately upon transition to IFRSs unless it qualifies for recognition under IAS 38 in the financial statements of the acquiree. [IFRS 1.C4(h)(i)]. However, IFRS 1 is silent on the treatment of IPR&D that was identified separately by an entity under the business combinations accounting standard of its previous GAAP, but which was immediately written off to profit or loss.
There are two possible scenarios. If previous GAAP requires IPR&D to be written off as an integral part of the business combination accounting under that GAAP then the carrying amount of IPR&D ‘immediately after the business combination’ would be zero. While we understand that there may be different views, it is our view that IFRS 1 does not allow reinstatement of the amount of IPR&D that was previously written off under this scenario.
However, if that write-off is not an integral part of the business combination accounting (e.g. the previous GAAP merely requires accelerated amortisation) then the carrying amount ‘immediately after the business combination’ would be the amount allocated to IPR&D by the business combinations standard under previous GAAP. In our view, reinstatement of the amount of IPR&D that was written off under this scenario is appropriate.
The above distinction may be largely irrelevant if the business combination takes place several years before the transition to IFRSs because, in practice, the IPR&D may have been amortised fully or may be impaired before the date of transition.
IFRSs require subsequent measurement of some assets and liabilities on a basis other than original cost, such as fair value for certain financial instruments or on specific measurement bases for share-based payments (IFRS 2) and employee benefits (IAS 19). Even if a first-time adopter does not apply IFRS 3 retrospectively to a business combination, such assets and liabilities must be measured on that other basis in its opening IFRS statement of financial position. Any change in the carrying amount of those assets and liabilities should be accounted for as an adjustment of retained earnings, or other appropriate category of equity, rather than as an adjustment of goodwill. [IFRS 1.C4(d)].
The following example, which is based on one within the implementation guidance in IFRS 1, illustrates many of the requirements discussed above. [IFRS 1.IG Example 2].
Under the business combinations exemption, a first-time adopter takes the carrying amount of goodwill under its previous GAAP at the date of transition to IFRSs as a starting point and only adjusts it as follows: [IFRS 1.C4(g)]
Application of the above guidance may sometimes be more complicated than expected as is illustrated in the example below.
In economic terms it might be contended that the ‘deferred marketing costs’ intangible asset in the example above comprises the value that would have been attributable under IFRSs to the acquired customer relationships. However, unless Entity A concluded that not recognising the customer relationship intangible asset was an error under its previous GAAP, it would not be able to recognise the customer relationship intangible asset upon adoption of IFRSs.
Under IFRS 1, assets acquired and liabilities assumed in a business combination prior to the date of transition to IFRSs are not necessarily valued on a basis that is consistent with IFRSs. This can lead to ‘double counting’ in the carrying amount of assets and goodwill as is illustrated in the example below.
The IASB accepted that IFRS 1 does not prevent the implicit recognition of internally generated goodwill that arose after the date of the business combination. It concluded that attempts to exclude such internally generated goodwill would be costly and lead to arbitrary results. [IFRS 1.BC39].
As the business combinations exemption also applies to associates and joint arrangements, a transition impairment review should be carried out on investments in associates and joint arrangements if they include an element of goodwill. However, the goodwill embedded in the amount of an investment in an associate or an investment in a joint venture will not be subject to a separate impairment test. Rather the entire carrying amount of the investment is reviewed for impairment following the requirements of IAS 36. In performing this impairment review of the investment in associate or joint venture, in our view, an investor does not reverse a previous GAAP impairment that was recognised separately on the notional goodwill element embedded in the investment. However, if the previous GAAP impairment had been recognised as a reduction of the entire investment (without attribution to any particular embedded account), the first-time adopter is able to reverse such impairment if it is assessed to no longer be necessary. Consider the two scenarios below:
IFRS 1 prohibits restatement of goodwill for most other adjustments reflected in the opening IFRS statement of financial position. Therefore, a first-time adopter electing not to apply IFRS 3 retrospectively is not permitted to make any adjustments to goodwill other than those described above. [IFRS 1.C4(h)]. For example, a first-time adopter cannot restate the carrying amount of goodwill:
Differences between the goodwill amount in the opening IFRS statement of financial position and that in the financial statements under previous GAAP may arise, for example, because:
Although IFRS 1 does not specifically address accounting for negative goodwill recognised under a previous GAAP, negative goodwill should be derecognised by a first-time adopter because it is not permitted to recognise items as assets or liabilities if IFRSs do not permit such recognition. [IFRS 1.10]. Negative goodwill clearly does not meet the definition of a liability under the IASB's Conceptual Framework and its recognition is not permitted under IFRS 3. While not directly applicable to a first-time adopter, the transitional provisions of IFRS 3 specifically require that any negative goodwill is derecognised upon adoption. [IFRS 3.B69(e)].
If a first-time adopter deducted goodwill from equity under its previous GAAP then it should not recognise that goodwill in its opening IFRS statement of financial position. Also, it should not reclassify that goodwill to profit or loss if it disposes of the subsidiary or if the investment in the subsidiary becomes impaired. [IFRS 1.C4(i)(i)]. Effectively, under IFRSs such goodwill ceases to exist, as is shown in the following example based on the implementation guidance in IFRS 1. [IFRS 1.IG Example 5].
The prohibition on reinstating goodwill that was deducted from equity may have a significant impact on first-time adopters that hedge their foreign net investments.
If a first-time adopter deducted goodwill from equity under its previous GAAP, adjustments resulting from the subsequent resolution of a contingency affecting the purchase consideration, at or before the date of transition to IFRSs, should be recognised in retained earnings. [IFRS 1.C4(i)(ii)]. Effectively, the adjustment is being accounted for in the same way as the original goodwill that arose on the acquisition, rather than having to be accounted for in accordance with IFRS 3. This requirement could affect, for example, the way a first-time adopter accounts for provisional amounts relating to business combinations prior to its date of transition to IFRSs.
A first-time adopter need not apply IAS 21 retrospectively to fair value adjustments and goodwill arising in business combinations that occurred before the date of transition to IFRSs. [IFRS 1.C2, IG21A]. This exemption is different from the ‘cumulative translation differences’ exemption, which is discussed at 5.7 below.
IAS 21 requires any goodwill arising on the acquisition of a foreign operation and any fair value adjustments to the carrying amounts of assets and liabilities arising on the acquisition of that foreign operation to be treated as assets and liabilities of the foreign operation. Thus they are expressed in the functional currency of the foreign operation and are translated at the closing rate in accordance with the requirements discussed in Chapter 15. [IAS 21.47]. For a first-time adopter it may be impracticable, especially after a corporate restructuring, to determine retrospectively the currency in which goodwill and fair value adjustments should be expressed. If IAS 21 is not applied retrospectively, a first-time adopter should treat such fair value adjustments and goodwill as assets and liabilities of the entity rather than as assets and liabilities of the acquiree. As a result, those goodwill and fair value adjustments are either already expressed in the entity's functional currency or are non-monetary foreign currency items that are reported using the exchange rate applied in accordance with previous GAAP. [IFRS 1.C2].
If a first-time adopter chooses not to take the exemption mentioned above, it must apply IAS 21 retrospectively to fair value adjustments and goodwill arising in either: [IFRS 1.C1, C3]
In practice the exemption may be of limited use for a number of reasons:
First, the exemption permits ‘goodwill and fair value adjustments’ to be treated as assets and liabilities of the entity rather than as assets and liabilities of the acquiree. Implicit in the exemption is the requirement to treat both the goodwill and the fair value adjustments consistently. However, the IASB apparently did not consider that many first-time adopters, under their previous GAAP, will have treated fair value adjustments as assets or liabilities of the acquiree, while at the same time treating goodwill as an asset of the acquirer. As the exemption under IFRS 1 did not foresee this particular situation, those first-time adopters will need to restate either their goodwill or fair value adjustments. In many cases restatement of goodwill is less onerous than restatement of fair value adjustments.
Secondly, the paragraphs in IFRS 1 that introduce the exemption were drafted at a later date than the rest of the Appendix of which they form part. Instead of referring to ‘first-time adopter’ these paragraphs refer to ‘entity’. Nevertheless, it is clear from the context that ‘entity’ should be read as ‘first-time adopter’. This means that the exemption only permits goodwill and fair value adjustments to be treated as assets and liabilities of the first-time adopter (i.e. ultimate parent). In practice, however, many groups have treated goodwill and fair value adjustments as an asset and liabilities of an intermediate parent. Where the intermediate parent has a functional currency that is different from that of the ultimate parent or the acquiree, it will be necessary to restate goodwill and fair value adjustments.
The decision to treat goodwill and fair value adjustments as either items denominated in the parent's or the acquiree's functional currency will also affect the extent to which the net investment in those foreign subsidiaries can be hedged (see also 4.5.5 above).
Under its previous GAAP a first-time adopter may not have consolidated a subsidiary acquired in a past business combination. In that case, a first-time adopter applying the business combinations exemption should measure the carrying amounts of the subsidiary's assets and liabilities in its consolidated financial statements at the transition date at either: [IFRS 1.IG27(a)]
The deemed cost of goodwill is the difference at the date of transition between:
The cost of an investment in a subsidiary in the parent's separate financial statements will depend on which option the parent has taken to measure the cost under IFRS 1 (see 5.8.2 below).
A first-time adopter is precluded from calculating what the goodwill would have been at the date of the original acquisition. The deemed cost of goodwill is capitalised in the opening IFRS statement of financial position. The following example, which is based on one within the guidance on implementation of IFRS 1, illustrates this requirement. [IFRS 1.IG Example 6].
If the cost of the subsidiary (as measured under IFRS 1, see 5.8.2 below) is lower than the proportionate share of net asset value at the date of transition to IFRSs, the difference is taken to retained earnings, or other category of equity, if appropriate.
Slightly different rules apply to all other subsidiaries (i.e. those not acquired in a business combination but created) that an entity did not consolidate under its previous GAAP, the main difference being that goodwill should not be recognised in relation to those subsidiaries (see 5.8 below). [IFRS 1.IG27(c)].
Note that this exemption requires the use of the carrying value of the investment in the separate financial statements of the parent prepared using IAS 27 – Separate Financial Statements. Therefore, if a first-time adopter, in its separate financial statements, does not opt to measure its cost of investment in a subsidiary at its fair value or previous GAAP carrying amount at the date of transition, it is required to calculate the deemed cost of the goodwill by comparing the cost of the investment to its share of the carrying amount of the net assets determined on a different date. [IFRS 1.D15]. In the case of a highly profitable subsidiary this could give rise to the following anomaly:
A first-time adopter may have consolidated an investment under its previous GAAP that does not meet the definition of a subsidiary under IFRSs. In this case the entity should first determine the appropriate classification of the investment under IFRSs and then apply the first-time adoption rules in IFRS 1. Generally such previously consolidated investments should be accounted for as either:
Deferred tax is calculated based on the difference between the carrying amount of assets and liabilities and their respective tax base. Therefore, deferred taxes should be recalculated after all assets acquired and liabilities assumed have been adjusted under IFRS 1. [IFRS 1.C4(k)].
IFRS 10 defines non-controlling interest as the ‘equity in a subsidiary not attributable, directly or indirectly, to a parent.’ [IFRS 10 Appendix A]. This definition is discussed in Chapter 6. Non-controlling interests should be calculated after all assets acquired, liabilities assumed and deferred taxes have been adjusted under IFRS 1. [IFRS 1.C4(k)].
Any resulting change in the carrying amount of deferred taxes and non-controlling interests should be recognised by adjusting retained earnings (or, if appropriate, another category of equity), unless they relate to adjustments to intangible assets that are adjusted against goodwill. See Example 5.29 below. [IFRS 1.IG Example 4].
In terms of treatment of a deferred tax, there is a difference depending on whether the first-time adopter previously recognised acquired intangible assets in accordance with its previous GAAP or whether it had subsumed the intangible asset into goodwill (in both cases, a deferred tax liability was not recognised under its previous GAAP but is required to be recognised under IFRS). In the first case it must recognise a deferred tax liability and adjust non-controlling interests and opening reserves accordingly. By contrast, in the second case it would have to decrease the carrying amount of goodwill, recognise the intangible assets and a deferred tax liability and adjust non-controlling interests as necessary, as discussed at 5.2.5 above. The IASB discussed this issue in October 2005, but decided not to propose an amendment to address this inconsistency.4
Example 5.29 below illustrates how to account for restatement of intangible assets, deferred tax and non-controlling interests where previous GAAP requires deferred tax to be recognised.
The business combination exemption does not extend to contingent consideration that arose from a transaction that occurred before the transition date, even if the acquisition itself is not restated due to the use of the exemption. Therefore, such contingent consideration, other than that classified as equity under IAS 32, is recognised at its fair value at the transition date, regardless of the accounting under previous GAAP. If the contingent consideration was not recognised at fair value at the date of transition under previous GAAP, the resulting adjustment is recognised in retained earnings or other category of equity, if appropriate. Subsequent adjustments will be recognised following the provisions of IFRS 3. [IFRS 3.40, 58].
IFRS 2 applies to accounting for the acquisition of goods or services in equity-settled share-based payment transactions, cash-settled share-based payment transactions and transactions in which the entity or the counterparty has the option to choose between settlement in cash or equity. There is no exemption from recognising share-based payment transactions that have not yet vested at the date of transition to IFRSs. The exemptions in IFRS 1 clarify that a first-time adopter is not required to apply IFRS 2 fully retrospectively to equity-settled share-based payment transactions that have already vested at the date of transition to IFRSs. IFRS 1 contains the following exemptions and requirements regarding share-based payment transactions:
Many first-time adopters that did not use fair value-based share-based payment accounting under previous GAAP will not have published the fair value of equity instruments granted and are, therefore, not allowed to apply IFRS 2 retrospectively to those share-based payment transactions;
There are a number of interpretation issues concerning these exemptions and requirements:
IFRS 1 only permits retrospective application of IFRS 2 if the entity has ‘disclosed publicly’ the fair value of the equity instruments concerned, but IFRSs do not define what is meant by ‘disclosed publicly’. While IFRS 1 does not specifically require public disclosure of the fair value of an entity's share-based payment transactions in its previous financial statements, it is clear that IFRS 1 requires fair value to have been published contemporaneously. In addition, the requirements in IFRS 1 to disclose publicly the fair value of share-based payment transactions can be met even if the fair value is only disclosed in aggregate rather than for individual awards.
The ‘date of transition to IFRSs’ to which those exemptions refer is the first day of the earliest comparative period presented in a first-time adopter's first IFRS financial statements. This effectively means that an entity could accelerate the vesting of an award that was otherwise due to vest after the date of transition to IFRSs in order to avoid applying IFRS 2 to that award.
A first-time adopter can choose which of the exemptions under (a) and (d) it wants to apply, i.e. there is no specific requirement to select the exemptions in a consistent manner.
Under IFRS 1, a first-time adopter is ‘encouraged’, but not required, to apply IFRS 2 to certain categories of share-based payment transactions (see (a) and (d) above). IFRS 1 does not specifically prohibit a literal reading of ‘encouraged’, which could, for example, allow a first-time adopter to decide to apply IFRS 2 only to some share-based payment transactions granted before 7 November 2002. We believe that it would generally be acceptable for a first-time adopter to apply IFRS 2 only to share-based payment transactions:
There is a slight ambiguity concerning the interpretation of the exemption under (c) above, because paragraph D2 of IFRS 1 refers only to the modification of awards. This could allow a literal argument that IFRS 1 does not prescribe any specific treatment when an entity cancels or settles, as opposed to modifying, an award to which IFRS 2 has not been applied. However, paragraph D2 also requires an entity to apply paragraphs 26‑29 of IFRS 2 to ‘modified’ awards. These paragraphs deal not only with modification but also with cancellation and settlement; indeed paragraphs 28 and 29 are not relevant to modifications at all. This makes it clear that the IASB intended IFRS 2 to be applied not only to modifications, but also to any cancellation or settlement of an award to which IFRS 2 has not been applied, unless the modification, cancellation or settlement occurs before the date of transition to IFRSs. [IFRS 1.D2, IFRS 2.26‑29].
These are not specifically addressed in the first-time adoption rules. It therefore appears that, where such transactions give rise to recognition of both an equity component and a liability component, the equity component is subject to the transitional rules for equity-settled transactions and the liability component to those for cash-settled transactions. This could well mean that the liability component of such a transaction is recognised in the financial statements, whilst the equity component is not.
It is not entirely clear what lies behind the exemption under (d) above, since a first-time adopter would never be required to report a share-based payment transaction (or indeed any transaction) settled before the date of transition.
Extract 5.5 from Manulife Financial Corporation (Manulife) provides an illustration of typical disclosures made by entities that applied the share-based payments exemption. In the extract below, Manulife applied the exemption not to apply IFRS 2 to share-based payment transactions that were fully vested at the transition date. The extract also illustrates the implicit limitation of the share-based payment exemption for awards that were granted after 7 November 2002 and that were still vesting at the date of transition to IFRS.
There is no explicit requirement in IFRS 1 or IFRS 2 that any voluntary retrospective application of IFRS 2 must be based on the fair value previously published. This might appear to allow a first-time adopter the flexibility of using a different valuation for IFRS 2 purposes than that previously used for disclosure purposes. However, the requirements of IFRS 1 in relation to estimates under previous GAAP (see 4.2 above) mean that the assumptions used in IFRS must be consistent with those used in the originally disclosed valuation. The entity will also need to consider the implications of the assertion, in effect, that there is more than one fair value for the same transaction.
A first-time adopter may elect to take advantage of the transitional provisions in IFRS 1 which allow it not to apply IFRS 2 to equity-settled share-based payment transactions that were vested before the date of transition to IFRS, despite having recognised a cost for those transactions in accordance with its previous GAAP. Neither IFRS 1 nor IFRS 2 clearly indicates the appropriate treatment of the costs of share-based payment transactions that were recognised under the previous GAAP. There are mixed views on this issue in different jurisdictions, some of which are being driven by local regulatory expectations. In practice, either of the following approaches is considered acceptable, provided that the treatment chosen is disclosed in the financial statements if the previously recognised costs are material:
A first-time adopter may apply the transitional provisions in IFRS 4. [IFRS 1.D4].
The claims development information (see Chapter 55) need not be disclosed for claims development that occurred more than five years before the end of the first IFRS reporting period. For entities taking advantage of this relief, the claims development information will be built up from five to ten years in the five years following adoption of IFRSs. Additionally, if it is ‘impracticable’ for a first-time adopter to prepare information about claims development that occurred before the beginning of the earliest period for which full comparative information is presented, this fact should be disclosed. [IFRS 4.44].
Furthermore, the IASB issued the amendments to IFRS 4 – Applying IFRS 9 – Financial Instruments – with IFRS 4 Insurance Contracts – in September 2016. The amendments permit insurers to either defer the application of IFRS 9 or use an ‘overlay approach’. See Chapter 55 at 10 for more details of these approaches and treatments for first-time adopters.
As discussed in 4.13, IFRS 17 was issued in May 2017 and may be adopted prior to its mandatory effective date of 1 January 2021. IFRS 17 supersedes IFRS 4. Accordingly, this exemption does not apply to entities that choose early adoption of IFRS 17.
IFRS 1 requires full retrospective application of standards effective at the end of a first-time adopter's first IFRS reporting period. [IFRS 1.7]. Therefore, in the absence of the deemed cost exemption, the requirements of, for example, IAS 16, IAS 38, IAS 40 – Investment Property – and IFRS 6 – Exploration for and Evaluation of Mineral Resources – would have to be applied as if the first-time adopter had always applied these standards. This could be quite onerous because:
Given the significance of items like property, plant and equipment in the statement of financial position of most first-time adopters and the sheer number of transactions affecting property, plant and equipment, restatement is not only difficult but would often also involve huge cost and effort. Nevertheless, a first-time adopter needs a cost basis for those assets in its opening IFRS statement of financial position. Therefore, the IASB decided to introduce the notion of a ‘deemed cost’ that is not the ‘true’ IFRS compliant cost basis of an asset, but a surrogate that is deemed to be a suitable starting point.
There are five separate deemed cost exemptions in IFRS 1:
To deal with the problem of restatement of long-lived assets upon first-time adoption of IFRSs, the standard permits a first-time adopter – for the categories of assets listed below – to measure an item in its opening IFRS statement of financial position using an amount that is based on its deemed cost: [IFRS 1.D5, D6]
A first-time adopter cannot use this deemed cost approach by analogy for any other assets or for liabilities. [IFRS 1.D7].
The use of fair value or revaluation as deemed cost for intangible assets will be very limited in practice because of the definition of an active market in IFRS 13. An active market is defined as one in which transactions for the item take place with sufficient frequency and volume to provide pricing information on an ongoing basis. [IFRS 13 Appendix A]. It is therefore unlikely that a first-time adopter will be able to apply this exemption to any intangible assets (see Chapter 17).
It is important to note that this exemption does not take classes or categories of assets as its unit of measure, but refers to ‘an item of property, plant and equipment,’ and similarly for investment property, right-of-use assets under IFRS 16 and intangible assets. [IFRS 1.D5]. IAS 16 does not ‘prescribe the unit of measure for recognition, i.e. what constitutes an item of property, plant and equipment. Thus, judgement is required in applying the recognition criteria to an entity's specific circumstances’ (see Chapter 18). [IAS 16.9]. A first-time adopter may therefore apply the deemed cost exemption to only some of its assets. For example, it could apply the exemption only to:
The IASB argued that it is not necessary to restrict application of the exemption to classes of assets to prevent arbitrarily selective revaluations, because IAS 36 ‘requires an impairment test if there is any indication that an asset is impaired. Thus, if an entity uses fair value as deemed cost for assets whose fair value is above cost, it cannot ignore indications that the recoverable amount of other assets may have fallen below their carrying amount. Therefore, the IFRS does not restrict the use of fair value as deemed cost to entire classes of asset.’ [IFRS 1.BC45]. Nevertheless, it seems doubtful that the quality of financial information would benefit from a revaluation of a haphazard selection of items of property, plant and equipment. Therefore, a first-time adopter should exercise judgement in selecting the items to which it believes it is appropriate to apply the exemption.
Extracts 5.6 and 5.7 below are typical disclosures of the use of the ‘fair value or revaluation as deemed cost’ exemption.
The deemed cost that a first-time adopter uses is either:
The revaluations referred to in (b) above need only be ‘broadly comparable to fair value or reflect an index applied to a cost that is broadly comparable to cost determined in accordance with IFRSs’. [IFRS 1.BC47]. It appears that in the interest of practicality the IASB is allowing a good deal of flexibility in this matter. The IASB explains in the basis for conclusions that ‘it may not always be clear whether a previous revaluation was intended as a measure of fair value or differs materially from fair value. The flexibility in this area permits a cost-effective solution for the unique problem of transition to IFRSs. It allows a first-time adopter to establish a deemed cost using a measurement that is already available and is a reasonable starting point for a cost-based measurement.’ [IFRS 1.BC47].
IFRS 1 describes the revaluations referred to in (b) above as a ‘previous GAAP revaluation’. Therefore, in our view, such revaluations can be used as the basis for deemed cost only if they were recognised in the first-time adopter's previous GAAP financial statements. A previous GAAP impairment (or reversal of an impairment) that resulted in the recognition of the related assets at fair value in the previous GAAP financial statements may be recognised as a previous GAAP revaluation for purposes of applying this exemption if it represents the fair value under IFRS 13 and not another measure such as fair value less costs of disposal. However, when the previous GAAP impairment was determined for a group of impaired assets (e.g. a cash generating unit as defined in IAS 36, see Chapter 20), the recognised value of an individual asset needs to represent its fair value under IFRS 13 and not another measure such as fair value less costs of disposal for purposes of this exemption.
If revaluations under previous GAAP did not satisfy the criteria in IFRS 1, a first-time adopter measures the revalued assets in its opening IFRS statement of financial position on one of the following bases: [IFRS1.IG11]
A first-time adopter that uses the exemption is required to disclose the resulting IFRS 1 adjustment separately (see 6.5.1 below).
If the deemed cost of an asset was determined before the date of transition then an IFRS accounting policy needs to be applied to that deemed cost in the intervening period to determine what the carrying amount of the asset is in the opening IFRS statement of financial position. This means that a first-time adopter that uses previous GAAP revaluation as the deemed cost of an item of property, plant and equipment will need to start depreciating the item from the date when the entity established the previous GAAP revaluation and not from its date of transition to IFRSs. [IFRS 1.IG9]. The example below illustrates the application of this requirement.
At its date of transition to IFRSs, a first-time adopter is allowed under IFRS 1 to measure each item of property, plant and equipment, investment properties, right-of-use assets under IFRS 16 and intangible assets at an amount based on:
The fact that IFRS 1 offers so many different bases for measurement does not disturb the IASB as it reasons that ‘cost is generally equivalent to fair value at the date of acquisition. Therefore, the use of fair value as the deemed cost of an asset means that an entity will report the same cost data as if it had acquired an asset with the same remaining service potential at the date of transition to IFRSs. If there is any lack of comparability, it arises from the aggregation of costs incurred at different dates, rather than from the targeted use of fair value as deemed cost for some assets. The Board regarded this approach as justified to solve the unique problem of introducing IFRSs in a cost-effective way without damaging transparency.’ [IFRS 1.BC43]. Although this is valid, it still means that an individual first-time adopter can greatly influence its future reported performance by carefully selecting a first-time adoption policy for the valuation of its assets. Users of the financial statements of a first-time adopter should therefore be mindful that historical trends under the previous GAAP might no longer be present in an entity's IFRS financial statements.
A first-time adopter may use fair value measurements that arose from an event such as a privatisation or initial public offering as deemed cost for IFRSs at the date of that measurement. [IFRS 1.D8].
IFRS 1 describes these revaluations as ‘deemed cost in accordance with previous GAAP’. Therefore, to the extent that they related to an event that occurred prior to its date of transition or during the period covered by the first IFRS financial statements, they can be used as the basis for deemed cost only if they were recognised in the first-time adopter's previous GAAP financial statements. As discussed in 5.5.2.C below, a first-time adopter is also allowed to use event-driven fair values resulting from such events that occurred subsequent to the first-time adopter's date of transition to IFRSs, but during the period covered by the first IFRS financial statements.
The ‘fair value or revaluation as deemed cost’ exemption discussed at 5.5.1 above only applies to items of property, plant and equipment, investment property, right-of-use assets under IFRS 16 and certain intangible assets. [IFRS 1.D5‑D7]. The event-driven deemed cost exemption, however, is broader in scope because it specifies that when a first-time adopter established a deemed cost in accordance with previous GAAP for some or all of its assets and liabilities [emphasis added] by measuring them at their fair value at one particular date … the entity may use such event-driven fair value measurements as deemed cost for IFRSs at the date of that measurement. [IFRS 1.D8, IFRS 1.BC46].
There are two important limitations in the scope of this exemption:
If revaluations under previous GAAP did not satisfy the criteria in IFRS 1, a first-time adopter measures the revalued assets in its opening IFRS statement of financial position on one of the following bases: [IFRS1.IG11]
Finally, although a first-time adopter may use an event-driven fair value measurement as deemed cost for any asset or liability, it does not have to use them for all assets and liabilities that were revalued as a result of the event.
Under some previous GAAPs an entity may have prepared its financial statements using ‘push down’ accounting, that is, the carrying amount of its assets and liabilities is based on their fair value at the date it became a subsidiary of its parent. If such a subsidiary subsequently adopts IFRSs, it will often require a very significant effort to determine the carrying amount of those assets and liabilities on a historical costs basis at the date of transition.
The event-driven deemed cost exemption applies to events ‘such as a privatisation or initial public offering.’ [IFRS 1.D8]. This list of events is clearly not meant to be exhaustive, but rather describes events that result in re-measurement of some or all assets and liabilities at their fair value. An acquisition that results in an entity becoming a subsidiary is a change of control event similar to a privatisation or an initial public offering. In our view, the application of ‘push down’ accounting results in event-driven fair value measurements that may be used as deemed cost for IFRSs at the date of that measurement.
The exemption can only be used, however, if ‘push down’ accounting resulted in the recognition of the related assets and liabilities at their fair value. For example, previous GAAP may not have required remeasurement to full fair value in the case of a partial acquisition or a step-acquisition, or if there was a bargain purchase that was allocated, for example, to reduce the fair values of long-lived assets. In these cases, the entity would not qualify for the event-driven deemed cost exemption, since the event did not result in the measurement of its assets and liabilities at their fair value.
Some previous GAAPs require an entity that emerges from bankruptcy or undertakes a legal reorganisation to apply ‘fresh start’ accounting, which involves recognition of assets and liabilities at their fair value at that date.
In our view, the application of ‘fresh start’ accounting results in an event-driven fair value measurement that may be used as deemed cost for IFRSs at the date of that measurement. [IFRS 1.D8]. The use of the exemption is limited to instances that resulted in the recognition of the related assets and liabilities at their full fair value (i.e. it cannot be used in the case of a partial step-up towards fair value).
The event-driven revaluation exemption allows a first-time adopter to recognise in its first IFRS financial statements fair values from events whose measurement date is after the date of transition to IFRSs but during the periods covered by the first IFRS financial statements. The event-driven fair value measurements are recognised as deemed cost at the date that the event occurs. An entity should recognise the resulting adjustments directly in retained earnings (or if appropriate, another category of equity) at the measurement date. [IFRS 1.D8(b)].
The Board explicitly considered whether to allow a first-time adopter that uses a revaluation subsequent to the date of transition to ‘work back’ to the deemed cost on the date of transition to IFRSs by adjusting the revaluation amounts to exclude any depreciation, amortisation or impairment between the date of transition to IFRSs and the date of that measurement. [IFRS 1.BC46B]. The Board rejected this approach ‘because making such adjustments would require hindsight and the computed carrying amounts on the date of transition to IFRSs would be neither the historical costs of the revalued assets nor their fair values on that date.’ [IFRS 1.BC46B]. Accordingly, at the date of transition to IFRS, the entity should either establish the deemed cost by applying the criteria in paragraphs D5 to D7 of IFRS 1 or measure assets and liabilities under the other requirements in IFRS 1. [IFRS 1.D8(b)]. This restriction seems to limit the usefulness of the exemption for first time adopters; however, it should provide relief from the need to keep two sets of books subsequent to the event.
It is common practice in some countries to account for exploration and development costs for oil and gas properties in development or production phases in cost centres that include all properties in a large geographical area, e.g. under the ‘full cost accounting’ method. However, this method of accounting generally uses a unit of account that is much larger than that is acceptable under IFRSs. Applying IFRSs fully retrospectively would pose significant problems for first-time adopters because it would also require amortisation ‘to be calculated (on a unit of production basis) for each year, using a reserves base that has changed over time because of changes in factors such as geological understanding and prices for oil and gas. In many cases, particularly for older assets, this information may not be available.’ [IFRS 1.BC47A]. Even when such information is available, the effort and cost to determine the opening balances at the date of transition would usually be very high.
For these entities, use of the fair value as deemed cost exemption (see 5.5.1 above), however, was not considered to be suitable because: [IFRS 1.BC47B]
‘Determining the fair value of oil and gas assets is a complex process that begins with the difficult task of estimating the volume of reserves and resources. When the fair value amounts must be audited, determining significant inputs to the estimates generally requires the use of qualified external experts. For entities with many oil and gas assets, the use of this fair value as deemed cost alternative would not meet the Board's stated intention of avoiding excessive cost.’
The IASB therefore decided to grant an exemption for first-time adopters that accounted under their previous GAAP for ‘exploration and development costs for oil and gas properties in the development or production phases … in cost centres that include all properties in a large geographical area.’ [IFRS 1.D8A]. Under the exemption, a first-time adopter may elect to measure oil and gas assets at the date of transition to IFRSs on the following basis: [IFRS 1.D8A]
For this purpose, oil and gas assets comprise only those assets used in the exploration, evaluation, development or production of oil and gas. [IFRS 1.D8A].
A first-time adopter that uses the exemption under (b) above should disclose that fact and the basis on which carrying amounts determined under previous GAAP were allocated. [IFRS 1.31A].
To avoid the use of deemed costs resulting in an oil and gas asset being measured at more than its recoverable amount, the Board also decided that oil and gas assets that were valued using this exemption should be tested for impairment at the date of transition to IFRSs as follows: [IFRS 1.D8A]
The deemed cost amounts should be reduced to take account of any impairment charge.
Finally, a first-time adopter that applies the deemed cost exemption for oil and gas assets in the development or production phases in (b) above should also apply the exception to the IFRIC 1 – Changes in Existing Decommissioning, Restoration and Similar Liabilities – exemption to the related decommissioning and restoration obligation (see 5.13.2 below). [IFRS 1.D21A].
Extract 5.8 below presents disclosure of the use of the ‘deemed cost for oil and gas assets’ exemption.
Entities that hold items of property, plant and equipment, right-of-use assets under IFRS 16 or intangible assets that are used, or were previously used, in operations subject to rate regulation might have capitalised, as part of the carrying amounts, amounts that do not qualify for capitalisation in accordance with IFRSs. For example, when setting rates, regulators often permit entities to capitalise an allowance for the cost of financing the asset's acquisition, construction or production. This allowance typically includes an imputed cost of equity. IFRSs do not permit an entity to capitalise an imputed cost of equity. [IFRS 1.BC47F]. The IASB decided to permit a first-time adopter with operations subject to rate regulations to elect to use the previous GAAP carrying amount of such an item at the date of transition to IFRSs as deemed cost. [IFRS 1.D8B]. In the Board's view, this exemption is consistent with other exemptions in IFRS 1 in that it ‘avoids excessive costs while meeting the objectives of the IFRS.’ [IFRS 1.BC47I].
Operations are subject to rate regulation if they are governed by a framework for establishing the prices that can be charged to customers for goods or services and that framework is subject to oversight and/or approval by a rate regulator (as defined in IFRS 14 – Regulatory Deferral Accounts). [IFRS 1.D8B, IFRS 14 Appendix A].
Without this exemption, a first-time adopter with operations subject to rate regulations would have had either to restate those items retrospectively to remove the non-qualifying amounts, or to use fair value as deemed cost (see 5.5.1 above). Both alternatives, the Board reasoned, pose significant practical challenges, the cost of which can outweigh the benefits. [IFRS 1.BC47G]. Typically, once amounts are included in the total cost of an item of property, plant and equipment, they are no longer tracked separately. Therefore, their removal would require historical information that, given the age of some of the assets involved, is probably no longer available and would be difficult to estimate. For many of these assets, it may be impractical to use the fair value exemption as such information may not be readily available. [IFRS 1.BC47H].
A first-time adopter that applies this exemption to an item need not apply it to all items. At the date of transition to IFRSs, the first-time adopter should test for impairment in accordance with IAS 36 each item for which it used the exemption. [IFRS 1.D8B].
Extract 5.9 below illustrates disclosure of the use of the deemed cost exemption for property, plant and equipment and intangible assets used in operations subject to rate regulation although IFRS 14 is not applied.
While the current exemption in paragraph D8B of IFRS 1 provides a one-time relief to determine the transition date balances of the eligible property, plant and equipment, right-of-use assets under IFRS 16 and intangible assets, IFRS 14 is wider in scope (see 5.20 below).
In January 2016 the IASB issued IFRS 16 – Leases – which was effective for annual reporting periods beginning on or after 1 January 2019 with an earlier application permitted. The consequential amendments to IFRS 1 (paragraph D9-D9E) provide first-time adopters with some exemptions from full retrospective application of IFRS 16.
Firstly, a first-time adopter may assess whether a contract existing at the date of transition contains a lease by applying IFRS 16 to these contracts on the basis of facts and circumstances existing at that date. [IFRS 1.D9].
In addition, a first-time adopter that is a lessee may apply the following approach to all of its leases (subject to the practical expedients described below):
Notwithstanding the exemption above, a first-time adopter that is a lessee should measure the right-of-use asset at fair value at the transition date for leases that meet the definition of investment property in IAS 40 and are measured using the fair value model in IAS 40 from the transition date. [IFRS 1.D9C].
Additionally a first-time adopter that is a lessee may apply one or more of the following practical expedients at the transition date (applied on a lease-by-lease basis):
Lease payments, lessee, lessee's incremental borrowing rate, commencement date of the lease, initial direct costs and lease term are defined in IFRS 16 and are used in IFRS 1 with the same meaning. [IFRS 1.D9E].
IAS 21 requires that, on disposal of a foreign operation, the cumulative amount of the exchange differences deferred in the separate component of equity relating to that foreign operation (which includes, for example, the cumulative translation difference for that foreign operation, the exchange differences arising on certain translations to a different presentation currency and any gains and losses on related hedges) should be reclassified to profit or loss when the gain or loss on disposal is recognised. [IAS 21.48, IFRS 1.D12]. This also applies to exchange differences arising on monetary items that form part of a reporting entity's net investment in a foreign operation in its consolidated financial statements. [IAS 21.32, 39, IFRS 1.D12].
Full retrospective application of IAS 21 would require a first-time adopter to restate all financial statements of its foreign operations to IFRSs from their date of inception or later acquisition onwards, and then determine the cumulative translation differences arising in relation to each of these foreign operations. A first-time adopter need not comply with these requirements for cumulative translation differences that existed at the date of transition. If it uses this exemption: [IFRS 1.D13]
If a first-time adopter chooses to use this exemption, it should apply it to all foreign operations at its date of transition, which will include any foreign operations that became first-time adopters before their parent. Any existing separate component of the first-time adopter's equity relating to such translation differences would be transferred to retained earnings at the date of transition.
An entity may present its financial statements in a presentation currency that differs from its functional currency. IFRS 1 is silent on whether the cumulative translation differences exemption should be applied to all translation differences or possibly separately to differences between the parent's functional currency and the presentation currency. However, IAS 21 does not distinguish between the translation differences arising on translation of subsidiaries into the functional currency of the parent and those arising on the translation from the parent's functional currency to the presentation currency. In our opinion, the exemption should therefore be applied consistently to both types of translation differences.
Since there is no requirement to justify the use of the exemption on grounds of impracticality or undue cost or effort, an entity that already has a separate component of equity and the necessary information to determine how much of it relates to each foreign operation in accordance with IAS 21 (or can do so without much effort) is still able to use the exemption. Accordingly, an entity that has cumulative exchange losses in respect of foreign operations may consider it advantageous to use the exemption if it wishes to avoid having to recognise these losses in profit or loss if the foreign operation is sold at some time in the future.
The extract below illustrates how companies typically disclose the fact that they have made use of this exemption.
Although IFRS 1 is not entirely clear whether this exemption extends to similar gains and losses arising on related hedges, we believe it is entirely appropriate for this exemption to be applied to net investment hedges as well as the underlying gains and losses.
Paragraph D13, which contains the exemption, explains that a first-time adopter need not comply with ‘these requirements.’ [IFRS 1.D13]. The requirements referred to are those summarised in paragraph D12 which explain that IAS 21 requires an entity:
The problem arises because paragraph D12 does not refer to the recognition of hedging gains or losses in other comprehensive income and accumulation in a separate component of equity (only the subsequent reclassification thereof). Accordingly, a very literal reading of the standard might suggest that an entity is required to identify historical gains and losses on such hedges. However, even if this position is accepted, the basis on which this might be done is not at all clear.
It is clear that the reasons cited by the IASB for including this exemption apply as much to related hedges as they do to the underlying exchange differences. The fact that IFRS 1 can be read otherwise might be seen as little more than poor drafting.
A first-time adopter must consolidate all subsidiaries (as defined in IFRS 10) unless IFRS 10 requires otherwise. [IFRS 1.IG26]. First-time adoption of IFRSs may therefore result in the consolidation for the first time of a subsidiary not consolidated under previous GAAP, either because the subsidiary was not regarded as such before, or because the parent did not prepare consolidated financial statements. If a first-time adopter did not consolidate a subsidiary under its previous GAAP, it must recognise the assets and liabilities of that subsidiary in its consolidated financial statements at the date of transition at either: [IFRS 1.IG27(a)]
If the newly-consolidated subsidiary was acquired in a business combination before the date of the parent's transition to IFRSs, goodwill is the difference between the parent's interest in the carrying amount determined under either (a) or (b) above and the cost in the parent's separate financial statements of its investment in the subsidiary. This is no more than a pragmatic ‘plug’ that facilitates the consolidation process but does not represent the true goodwill that might have been recorded if IFRSs had been applied to the original business combination (see 5.2.7 above). [IFRS 1.C4(j), IG27(b)]. Therefore, if the first-time adopter accounted for the investment as an associate under its previous GAAP, it cannot use the notional goodwill previously calculated under the equity method as the basis for goodwill under IFRSs.
If the parent did not acquire the subsidiary, but established it, it does not recognise goodwill. [IFRS 1.IG27(c)]. Any difference between the carrying amount of the subsidiary and the identifiable net assets as determined in (a) or (b) above would be treated as an adjustment to retained earnings, representing the accumulated profits or losses that would have been recognised as if the subsidiary had always been consolidated.
The adjustment of the carrying amounts of assets and liabilities of a first-time adopter's subsidiaries may affect non-controlling interests and deferred tax, as discussed at 5.2.9 above. [IFRS 1.IG28].
When an entity prepares separate financial statements, IAS 27 requires a first-time adopter to account for its investments in subsidiaries, joint ventures and associates either: [IFRS 1.D14]
However, if a first-time adopter measures such an investment at cost then it can elect to measure that investment at one of the following amounts in its separate opening IFRS statement of financial position: [IFRS 1.D15]
A first-time adopter may choose to use either of these bases to measure its investment in each subsidiary, joint venture or associate where it elects to use a deemed cost. [IFRS 1.D15].
For a first-time adopter that chooses to account for such an investment using the equity method procedures in accordance with IAS 28:
A first-time adopter that applies the exemption should disclose certain additional information in its financial statements (see 6.5.2 below).
Within groups, some subsidiaries, associates and joint ventures may have a different date of transition to IFRSs than the parent/investor, for example, because national legislation required IFRSs after, or prohibited IFRSs at, the date of transition of the parent/investor. As this could have resulted in permanent differences between the IFRS figures in a subsidiary's own financial statements and those it reports to its parent, the IASB introduced a special exemption regarding the assets and liabilities of subsidiaries, associates and joint ventures.
IFRS 1 contains detailed guidance on the approach to be adopted when a parent adopts IFRSs before its subsidiary (see 5.9.1 below) and when a subsidiary adopts IFRSs before its parent (see 5.9.2 below).
These provisions also apply when IFRSs are adopted at different dates by an investor in an associate and the associate, or a venturer in a joint venture and the joint venture. [IFRS 1.D16‑D17]. In the discussion that follows ‘parent’ includes an investor in an associate or a venturer in a joint venture, and ‘subsidiary’ includes an associate or a joint venture. References to consolidation adjustments include similar adjustments made when applying equity accounting. IFRS 1 also addresses the requirements for a parent that adopts IFRSs at different dates for the purposes of its consolidated and its separate financial statements (see 5.9.4 below).
If a subsidiary becomes a first-time adopter later than its parent, it should in its financial statements measure its own assets and liabilities at either:
IFRS 1 does not elaborate on exactly what constitutes ‘consolidation procedures’ but in our view it would encompass adjustments required in order to harmonise a subsidiary's accounting policies with those of the group, as well as purely ‘mechanical’ consolidation adjustments such as the elimination of intragroup balances, profits and losses.
The following example, which is based on the guidance on implementation of IFRS 1, illustrates how an entity should apply these requirements. [IFRS 1.IG Example 8].
Under option (b) a subsidiary would prepare its own IFRS financial statements, completely ignoring the IFRS elections that its parent used when it adopted IFRSs for its consolidated financial statements.
Under option (a) the numbers in a subsidiary's IFRS financial statements will be as close to those used by its parent as possible. However, differences other than those arising from business combinations will still exist in many cases, for example:
The IASB seems content with the fact that the exemption will ease some practical problems, [IFRS 1.BC62], though it will rarely succeed in achieving more than a moderate reduction of the number of reconciling differences between a subsidiary's own reporting and the numbers used by its parent.
More importantly, the choice of option (a) prevents the subsidiary from electing to apply any of the other voluntary exemptions offered by IFRS 1, since the parent had already made the choices for the group at its date of transition. Therefore, option (a) may not be appropriate for a subsidiary that prefers to use a different exemption (e.g. fair value as deemed cost) for property, plant and equipment due, for example, to a tax reporting advantage. Also, application of option (a) would require the subsidiary to adopt a new IFRS that becomes effective during any of the periods presented in the same manner it was adopted by the parent and is more difficult when a parent and its subsidiary have different financial years. In that case, IFRS 1 would seem to require the IFRS information for the subsidiary to be based on the parent's date of transition to IFRSs, which may not even coincide with an interim reporting date of the subsidiary; the same applies to any joint venture or associate.
Example 5.33 below explains interaction between D16 (a) of IFRS 1 (i.e. option (a) above) and the business combination exemptions in Appendix C of IFRS 1 applied by its parent.
A subsidiary may become a first-time adopter later than its parent, because it previously prepared a reporting package under IFRSs for consolidation purposes but did not present a full set of financial statements under IFRSs. The above election of D16 of IFRS 1 (a) may be ‘relevant not only when a subsidiary's reporting package complies fully with the recognition and measurement requirements of IFRSs, but also when it is adjusted centrally for matters such as review of events after the reporting period and central allocation of pension costs.’ [IFRS 1.IG31]. Adjustments made centrally to an unpublished reporting package are not considered to be corrections of errors for the purposes of the disclosure requirements in IFRS 1. However, a subsidiary is not permitted to ignore misstatements that are immaterial to the consolidated financial statements of the group but material to its own financial statements.
If a subsidiary was acquired after the parent's date of transition to IFRSs then it cannot apply option (a) because there are no carrying amounts included in the parent's consolidated financial statements, based on the parent's date of transition. Therefore, the subsidiary is unable to use the values recognised in the group accounts when it was acquired, since push-down of the group's purchase accounting values is not allowed in the subsidiary's financial statements. However, if the subsidiary had recognised those amounts in its previous GAAP financial statements, it may be able to use the same amounts as deemed costs under IFRSs pursuant to the ‘event-driven’ deemed cost exemption (see 5.5.2 above).
The exemption is also available to associates and joint ventures. This means that in many cases an associate or joint venture that wants to apply option (a) will need to choose which shareholder it considers its ‘parent’ for IFRS 1 purposes if more than one investor/joint venturer have already applied IFRS and determine the IFRS carrying amount of its assets and liabilities by reference to that parent's date of transition to IFRSs.
The IFRS Interpretations Committee considered whether, applying paragraph D16 of IFRS 1, a subsidiary that becomes a first-time adopter later than its parent and has foreign operations, on which translation differences are accumulated as part of a separate component of equity, can recognise the cumulative translation differences at an amount that would be included in the parent's consolidated financial statements, based on the parent's date of transition to IFRS.
In September 2017, the Committee reached the conclusion that the cumulative translation differences are neither assets nor liabilities while the requirement applies to assets and liabilities and hence the requirement does not permit the subsidiary to recognise the cumulative translation differences at the amount as above. The Committee also concluded that the requirement cannot be applied to the cumulative translation differences by analogy because paragraph 18 of IFRS 1 clearly prohibits an entity from applying the exemptions in IFRS 1 by analogy to other items.
Accordingly, in this circumstance the subsidiary accounts for the cumulative translation differences applying paragraphs D12 – D13 of IFRS 1 (see 5.7 above).
However, in December 2017 the Board discussed the Committee's recommendation to propose an amendment to IFRS 1 to require a subsidiary that applies paragraph D16 (a) of IFRS 1 to measure cumulative translation differences using the amounts reported by its parent, based on the parent's date of transition to IFRS (subject to any adjustments made for consolidation procedures and for the effects of the business combination in which the parent acquired the subsidiary). In May 2019, the Board issued Exposure Draft – Annual Improvements to IFRS Standards 2018-2020 and proposed the amendment above. At the date of publication, this proposed amendment has not been finalised.
If a parent becomes a first-time adopter later than its subsidiary, the parent should, in its consolidated financial statements, measure the subsidiary's assets and liabilities at the carrying amounts that are in the subsidiary's financial statements, after adjusting for consolidation and for the effects of the business combination in which the entity acquired the subsidiary. The same applies for associates or joint ventures, substituting equity accounting adjustments. [IFRS 1.D17].
Unlike other first-time adoption exemptions, this exemption does not offer a choice between different accounting alternatives. In fact, while a subsidiary that adopts IFRSs later than its parent can choose to prepare its first IFRS financial statements by reference to its own date of transition to IFRSs or that of its parent, the parent itself must use the IFRS measurements already used in the subsidiary's financial statements, adjusted as appropriate for consolidation procedures and the effects of the business combination in which it acquired the subsidiary. [IFRS 1.BC63]. However, this exemption does not preclude the parent from adjusting the subsidiary's assets and liabilities for a different accounting policy, e.g. cost model or revaluation model for accounting for property, plant and equipment.
The following example, which is based on the guidance on implementation of IFRS 1, illustrates how an entity should apply these requirements. [IFRS 1.IG Example 9].
When a subsidiary adopts IFRSs before its parent, this will limit the parent's ability to choose first-time adoption exemptions in IFRS 1 freely as related to that subsidiary, as illustrated in the example below. However, this does not mean that the parent's ability to choose first-time adoption exemptions will always be limited. For example, a parent may still be able to deem a subsidiary's cumulative translation differences to be zero because IFRS 1 specifically states that under the option ‘the cumulative translation differences for all [emphasis added] foreign operations are deemed to be zero at the date of transition to IFRSs’ (see 5.7 above). [IFRS 1.D13].
The requirements of IFRS 1 for a parent and subsidiary with different dates of transition do not override the following requirements of IFRS 1: [IFRS 1.IG30]
An entity may sometimes become a first-time adopter for its separate financial statements earlier or later than for its consolidated financial statements. Such a situation may arise, for example, when a parent avails itself of the exemption under paragraph 4 of IFRS 10 from preparing consolidated financial statements and prepares its separate financial statements under IFRSs. Subsequently, the parent may cease to be entitled to the exemption or may choose not to use it and would, therefore, be required to apply IFRS 1 in its first consolidated financial statements.
Another example might be that, under local law, an entity is required to prepare its consolidated financial statements under IFRSs, but is required (or permitted) to prepare its separate financial statements under local GAAP. Subsequently the parent chooses, or is required, to prepare its separate financial statements under IFRSs.
If a parent becomes a first-time adopter for its separate financial statements earlier or later than for its consolidated financial statements, it must measure its assets and liabilities at the same amounts in both financial statements, except for consolidation adjustments. [IFRS 1.D17]. As drafted, the requirement is merely that the ‘same’ amounts be used, without being explicit as to which set of financial statements should be used as the benchmark. However, it seems clear from the context that the IASB intends that the measurement basis used in whichever set of financial statements first comply with IFRSs must also be used when IFRSs are subsequently adopted in the other set.
IFRS 10 requires a parent that is an ‘investment entity’ as defined in the standard (see Chapter 6) to account for most of its subsidiaries at fair value through profit or loss in its consolidated financial statements rather than through consolidation. This exception from normal consolidation procedures does not apply to:
In IFRS 1, there are exemptions relating to a parent adopting IFRSs earlier or later than its subsidiary. Below, we deal with situations where:
In this case, the subsidiary that is required to be measured at fair value through profit or loss is required to measure its assets and liabilities under the general provisions of IFRS 1, based on its own date of transition to IFRSs (i.e. option (b) in 5.9.1 above), [IFRS 1.D16(a)], rather than (as would generally be permitted under option (a) in 5.9.1 above) by reference to the carrying value of its assets and liabilities in the consolidated financial statements of its parent, which is based on the fair value of the subsidiary's equity. This effectively prevents the accounting anomaly of the subsidiary measuring its net assets at the fair value of its own equity on transition to IFRSs.
In this case, the parent is required to consolidate its subsidiaries and is not able to use the exception to consolidation in IFRS 10. [IFRS 1.D17]. If the provisions in 5.9.2 above were to be applied, the effect would be that the parent would bring any investments in subsidiaries accounted for at fair value through profit or loss by the subsidiary into the parent's consolidated statement of financial position at their fair value. This result would be contrary to the intention of the investment entities concept that such an accounting treatment is applied only by a parent that is itself an investment entity and D17 of IFRS 1 specifically prohibits this.
IAS 32 requires compound financial instruments (e.g. many convertible bonds) to be split at inception into separate equity and liability components on the basis of facts and circumstances existing when the instrument was issued. [IAS 32.15, 28]. If the liability component is no longer outstanding, a full retrospective application of IAS 32 would involve identifying two components, one representing the original equity component and the other (retained earnings) representing the cumulative interest accreted on the liability component, both of which are accounted for in equity (see Chapter 47). A first-time adopter does not need to make this possibly complex allocation if the liability component is no longer outstanding at the date of transition to IFRSs. [IFRS 1.D18]. For example, in the case of a convertible bond that has been converted into equity, it is not necessary to make this split.
However, if the liability component of the compound instrument is still outstanding at the date of transition to IFRSs then a split is required to be made (see Chapter 47). [IFRS 1.IG35-IG36].
The following discusses the application of the exemption in D19 through D19C regarding designation of previously recognised financial instruments to certain financial assets and financial liabilities.
IFRS 9 permits a financial asset to be designated as measured at fair value through profit or loss if the entity satisfies the criteria in IFRS 9 at the date the entity becomes a party to the financial instrument. [IFRS 9.4.1.5].
Paragraph D19A of IFRS 1 allows a first-time adopter to designate a financial asset as measured at fair value through profit or loss on the basis of facts and circumstances that exist at the date of transition to IFRSs. [IFRS 1.D19A]. If this exemption is used, paragraph 29 of IFRS 1 would require certain additional disclosures (see 6.4 below).
IFRS 9 permits a financial liability to be designated as a financial liability at fair value through profit or loss if the entity meets the criteria in IFRS 9 at the date the entity becomes a party to the financial instrument. [IFRS 9.4.2.2].
Paragraph D19 of IFRS 1 allows a first-time adopter to designate, at the transition date, a financial liability as measured at fair value through profit or loss provided the liability meets the criteria in paragraph 4.2.2 of IFRS 9 at that date. If this exemption is used, paragraph 29A of IFRS 1 would require certain additional disclosures (see 6.4 below). [IFRS 1.D19].
At initial recognition, an entity may make an irrevocable election to designate an investment in an equity instrument not held for trading or contingent consideration recognised by an acquirer in a business combination to which IFRS 3 applies as at fair value through other comprehensive income in accordance with IFRS 9. [IFRS 9.5.7.5].
Paragraph D19B of IFRS 1 allows a first-time adopter to designate an investment in such an equity instrument as at fair value through other comprehensive income on the basis of facts and circumstances that exist at the date of transition to IFRSs. [IFRS 1.D19B].
IFRS 9 requires a fair value gain or loss on a financial liability that is designated as at fair value through profit or loss to be presented as follows unless this presentation creates or enlarges an accounting mismatch in profit or loss: [IFRS 9.5.7.7]
Paragraph D19C of IFRS 1 requires a first-time adopter to determine whether the treatment in paragraph 5.7.7 of IFRS 9 would create an accounting mismatch in profit or loss on the basis of facts and circumstances that exist at the date of transition to IFRSs (see Chapter 48). [IFRS 1.D19C].
First-time adopters are granted similar transition relief in respect of the day 1 profit requirements of IFRS 9 as is available to existing IFRS reporters. [IFRS 1.BC83A]. Consequently, first-time adopters may apply the requirements of paragraph B5.1.2A(b) of IFRS 9 about a deferral of day 1 gain/loss prospectively to transactions entered into on or after the date of transition to IFRSs. [IFRS 1.D20].
Under IAS 16 the cost of an item of property, plant and equipment includes ‘the initial estimate of the costs of dismantling and removing the item and restoring the site on which it is located, the obligation for which an entity incurs either when the item is acquired or as a consequence of having used the item during a particular period for purposes other than to produce inventories during that period.’ [IAS 16.16(c)]. Therefore, a first-time adopter needs to ensure that property, plant and equipment cost includes an item representing the decommissioning provision as determined under IAS 37. [IFRS 1.IG13].
An entity should apply IAS 16 in determining the amount to be included in the cost of the asset, before recognising depreciation and impairment losses which cause differences between the carrying amount of the decommissioning liability and the amount related to decommissioning costs to be included in the carrying amount of the asset.
An entity accounts for changes in decommissioning provisions in accordance with IFRIC 1 but IFRS 1 provides an exemption for changes that occurred before the date of transition to IFRSs and prescribes an alternative treatment if the exemption is used. [IFRS 1.IG13, IG201-IG203]. In such cases, a first-time adopter should:
From the above example it is clear that the exemption reduces the amount of effort required to restate items of property, plant and equipment with a decommissioning component. In many cases the difference between the two methods will be insignificant, except where an entity had to make major adjustments to the estimate of the decommissioning costs near the end of the life of the related assets.
A first-time adopter that elects the deemed cost approaches discussed in 5.5 above and elects to use the IFRIC 1 exemption to recognise its decommissioning obligation should be aware of the interaction between these exemptions that may lead to a potential overstatement of the underlying asset. In determining the deemed cost of the asset, the first-time adopter would need to make sure that the fair value of the asset is exclusive of the decommissioning obligation in order to avoid the potential overstatement of the value of the asset that might result from the application of the IFRIC 1 exemption.
A first-time adopter that applies the deemed cost exemption for oil and gas assets in the development or production phases accounted for in cost centres that include all properties in a large geographical area under previous GAAP (see 5.5.3 above) should not apply the IFRIC 1 exemption (see 5.13.1 above) or IFRIC 1 itself, but instead:
The IASB introduced this requirement because it believed that the existing IFRIC 1 exemption would require detailed calculations that would not be practicable for entities that apply the deemed cost exemption for oil and gas assets. [IFRS 1.BC63CA]. This is because the carrying amount of the oil and gas assets is deemed already to include the capitalised costs of the decommissioning obligation.
Service concession arrangements are contracts between the public and private sector to attract private sector participation in the development, financing, operation and maintenance of public infrastructure (e.g. roads, bridges, hospitals, water distribution facilities, energy supply and telecommunication networks). [IFRIC 12.1, 2].
IFRS 1 allows a first-time adopter to apply the transitional provision in IFRIC 12. [IFRS 1.D22]. IFRIC 12 requires retrospective application unless it is, for any particular service concession arrangement, impracticable for the operator to apply IFRIC 12 retrospectively at the start of the earliest period presented, in which case it should:
This exemption was used by many Brazilian companies with service concession arrangements and a typical disclosure of the use of the exemption is given in Extract 5.11 below from the financial statements of Eletrobras:
For many first-time adopters, full retrospective application of IAS 23 – Borrowing Costs – would be problematic as the adjustment would be required in respect of any asset held that had, at any point in the past, satisfied the criteria for capitalisation of borrowing costs. To avoid this problem, IFRS 1 allows a modified form of the transitional provisions set out in IAS 23, which means that the first-time adopter can elect to apply the requirements of IAS 23 from the date of transition or from an earlier date as permitted by paragraph 28 of IAS 23. From the date on which an entity that applies this exemption begins to apply IAS 23, the entity:
IAS 23 applies to borrowing costs that are directly attributable to the acquisition, construction or production of a qualifying asset, that is defined in IAS 23. If a first-time adopter established a deemed cost for an asset (see 5.5 above) then it cannot capitalise borrowing costs incurred before the measurement date of the deemed cost (see 5.15.2 below). [IFRS 1.IG23].
There are limitations imposed on capitalised amounts under IAS 23. IAS 23 states that when the carrying amount of a qualifying asset exceeds its recoverable amount or net realisable value, the carrying amount is written down or written off in accordance with the requirement of other standards. [IAS 23.16]. Once an entity uses the ‘fair value as deemed cost exemption’ described at 5.5 above and has recognised an asset at fair value, in our view, the entity should not increase that value to capitalise interest incurred before that date. Interest incurred subsequent to the date of transition may be capitalised on a qualifying asset, subject to the requirements of IAS 23 (see Chapter 21).
IFRIC 19 – Extinguishing Financial Liabilities with Equity Instruments – deals with accounting for transactions whereby a debtor and creditor might renegotiate the terms of a financial liability with the result that the debtor extinguishes the liability fully or partially by issuing equity instruments to the creditor. The transitional provisions of IFRIC 19 require retrospective application only from the beginning of the earliest comparative period presented. [IFRIC 19.13]. The Interpretations Committee concluded that application to earlier periods would result only in a reclassification of amounts within equity. [IFRIC 19.BC33].
The Board provided similar transition relief to first-time adopters, effectively requiring application of IFRIC 19 from the date of transition to IFRSs. [IFRS 1.D25].
If an entity has a functional currency that was, or is, the currency of a hyperinflationary economy, it must determine whether it was subject to severe hyperinflation before the date of transition to IFRSs. [IFRS 1.D26]. A currency of a hyperinflationary economy has been subject to severe hyperinflation if it has both of the following characteristics:
The functional currency of an entity ceases to be subject to severe hyperinflation on the ‘functional currency normalisation date’, when the functional currency no longer has either, or both, of these characteristics, or when there is a change in the entity's functional currency to a currency that is not subject to severe hyperinflation. [IFRS 1.D28].
If the date of transition to IFRSs is on, or after, the functional currency normalisation date, the first-time adopter may elect to measure all assets and liabilities held before the functional currency normalisation date at fair value on the date of transition and use that fair value as the deemed cost in the opening IFRS statement of financial position. [IFRS 1.D29].
Preparation of information in accordance with IFRSs for periods before the functional currency normalisation date may not be possible. Therefore, entities may prepare financial statements for a comparative period of less than 12 months if the functional currency normalisation date falls within a 12-month comparative period, provided that a complete set of financial statements is prepared, as required by paragraph 10 of IAS 1, for that shorter period. [IFRS 1.D30]. It is also suggested that entities disclose non-IFRS comparative information and historical summaries if they would provide useful information to users of financial statements – see 6.7 below. The Board noted that an entity should clearly explain the transition to IFRSs in accordance with IFRS 1's disclosure requirements. [IFRS 1.BC63J]. See Chapter 16 regarding accounting during periods of hyperinflation.
A first-time adopter may apply the transition provisions in Appendix C of IFRS 11 – Joint Arrangements (see Chapter 12) with the following exception:
In surface mining operations, entities may find it necessary to remove mine waste materials (‘overburden’) to gain access to mineral ore deposits. This waste removal activity is known as ‘stripping’. A mining entity may continue to remove overburden and to incur stripping costs during the production phase of the mine. IFRIC 20 – Stripping Costs in the Production Phase of a Surface Mine – considers when and how to account separately for the benefits arising from a surface mine stripping activity, as well as how to measure these benefits both on initial recognition and subsequently. [IFRIC 20.1, 3, 5].
First-time adopters may apply the transitional provisions set out in IFRIC 20, [IFRIC 20.A1‑A4], except that the effective date is deemed to be 1 January 2013 or the beginning of the first IFRS reporting period, whichever is later. [IFRS 1.D32].
IFRS 14 gives a first-time adopter that is a rate-regulated entity the option to continue with the recognition of rate-regulated assets and liabilities under previous GAAP on transition to IFRS. IFRS 14 provides entities with an exemption from compliance with other IFRSs and the conceptual framework on first-time adoption and subsequent reporting periods, until the comprehensive project on rate regulation is completed. First-time adopters, whose previous GAAP prohibited the recognition of rate-regulated assets and liabilities, will not be allowed to apply IFRS 14 on transition to IFRS. We discuss the requirements of IFRS 14 in detail below.
IFRS 14 defines the following terms in connection with regulatory deferral accounts. [IFRS 14 Appendix A].
Rate regulated activities: An entity's activities that are subject to rate regulation.
Rate regulation: A framework for establishing the prices that can be charged to customers for goods or services and that framework is subject to oversight and/or approval by a rate regulator.
Rate regulator: An authorised body that is empowered by statute or regulation to establish the rate or a range of rates that bind an entity. The rate regulator may be a third-party body or a related party of the entity, including the entity's own governing board, if that body is required by statute or regulation to set rates both in the interest of the customers and to ensure the overall financial viability of the entity.
Regulatory deferral account balance: The balance of any expense (or income) account that would not be recognised as an asset or a liability in accordance with other standards, but that qualifies for deferral because it is included, or is expected to be included, by the rate regulator in establishing the rate(s) that can be charged to customers.
An entity is permitted to apply IFRS 14 in its first IFRS financial statements, if the entity conducts rate-regulated activities and recognised amounts that qualify as regulatory deferral account balances in its financial statements under its previous GAAP. [IFRS 14.5]. The entity that is within the scope of, and that elects to apply, IFRS 14 should apply all of its requirements to all regulatory deferral account balances that arise from all of the entity's rate-regulated activities. [IFRS 14.8].
The entity that elected to apply IFRS 14 in its first IFRS financial statements should apply IFRS 14 also in its financial statements for subsequent periods. [IFRS 14.6].
In some cases, other standards explicitly prohibit an entity from recognising, in the statement of financial position, regulatory deferral account balances that might be recognised, either separately or included within other line items such as property, plant and equipment, in accordance with previous GAAP accounting policies. However, in accordance with paragraph 9 and 10 of IFRS 14, an entity that elects to apply this standard in its first IFRS financial statements applies the exemption from paragraph 11 of IAS 8. [IFRS 14.10]. In other words, on initial application of IFRS 14, an entity should continue to apply its previous GAAP accounting policies for the recognition, measurement, impairment, and derecognition of regulatory deferral account balances except for any changes permitted by the standard and subject to any presentation changes required by the standard. [IFRS 14.11]. Such accounting policies may include, for example, the following practices: [IFRS 14.B4]
The accounting policy for the regulatory deferral account balances, as explained above, must, of course, be consistent from period to period unless there is an appropriate change in accounting policies. [IFRS 14.12].
The regulatory deferral account balances to be recognised are restricted to the incremental amounts from what are permitted or required to be recognised as assets and liabilities under other IFRS. [IFRS 14.7]. Therefore, the measurement of these balances effectively entails a two-step process:
The differences would represent the regulatory deferral account debit or credit balances to be recognised by the entity under IFRS 14.
Some items of expense (income) may be outside the regulated rate(s) because, for example, the amounts are not expected to be accepted by the rate regulator or because they are not within the scope of the rate regulation. Consequently, such an item is recognised as income when earned or expense as incurred, unless another standard permits or requires it to be included in the carrying amount of an asset or liability. [IFRS 14.B3].
The following are examples of the types of costs that rate regulators might allow in rate-setting decisions and that an entity might, therefore, recognise in regulatory deferral account balances: [IFRS 14.B5]
An entity should not change its accounting policies in order to start to recognise regulatory deferral account balances. [IFRS 14.13]. Also, changes in its accounting policies for the recognition, measurement, impairment and derecognition of regulatory deferral account balances are only allowed if it would result in financial statements that are more relevant to the economic decision-making needs of users and no less reliable, or more reliable and no less relevant to those needs. The judgement of relevance and reliability is made using the criteria in IAS 8. [IFRS 14.13, IAS 8.10]. It should be noted that IFRS 14 does not exempt entities from applying paragraphs 10 or 14‑15 of IAS 8 to changes in accounting policy. [IFRS 14.14].
The application guidance in IFRS 14 clarifies that regulatory deferral account balances usually represent timing differences between the recognition of items of income or expenses for regulatory purposes and the recognition of those items for financial reporting purposes. When an entity changes an accounting policy on the first-time adoption of IFRS or on the initial application of a new or revised standard, new or revised timing differences may arise that create new or revised regulatory deferral account balances. The prohibition in paragraph 13 of this standard that prevents an entity from changing its accounting policy in order to start to recognise regulatory deferral account balances does not prohibit the recognition of the new or revised regulatory deferral account balances that are created because of other changes in accounting policies required by IFRS. This is because the recognition of regulatory deferral account balances for such timing differences would be consistent with the existing recognition policy and would not represent the introduction of a new accounting policy. Similarly, paragraph 13 of this standard does not prohibit the recognition of regulatory deferral account balances arising from timing differences that did not exist immediately prior to the date of transition to IFRS but are consistent with the entity's accounting policies established in accordance with paragraph 11 of IFRS 14, for example, storm damage costs. [IFRS 14.B6].
This standard requires an entity to present regulatory deferral account debit balances and credit balances and the net movement in those balances as separate line items in the statement of financial position and the statement(s) of profit or loss and other comprehensive income respectively. The totals of regulatory deferral account balances should not be classified as current or non-current. The separate line items should be distinguished from other items that are presented under other IFRSs by the use of sub-totals, which are drawn before the regulatory line items are presented. [IFRS 14.20, 21, 23, IFRS 14.IE1].
The net movements in all regulatory deferral account balances for the reporting period that relate to items recognised in other comprehensive income should be presented in the other comprehensive income section of the statement of profit or loss and other comprehensive income. Also, paragraph 22 of IFRS 14 requires separate line items to be used for the net movement related to items that, in accordance with other standards, either will not or will be reclassified subsequently to profit or loss when specific conditions are met. [IFRS 14.22, IFRS 14.IE1].
In relation to a deferred tax asset or deferred tax liability that is recognised as a result of recognising regulatory deferral account balances, the entity should not include that deferred tax amount within the total deferred tax asset (liability) balances. Instead, an entity is required to present the deferred tax asset or liability either:
Similarly, when an entity recognises the movement in a deferred tax asset (liability) that arises as a result of recognising regulatory deferral account balances, the entity should not include the movement in that deferred tax amount within the tax expense (income) line item that is presented in the statement(s) of profit or loss and other comprehensive income under IAS 12. Instead, the entity should present the movement either:
IFRS 14 requires additional earnings per share amounts to be presented. When an entity presents earnings per share in accordance with IAS 33 – Earnings per Share – the entity has to present additional basic and diluted earnings per share calculated using earnings amount required by IAS 33 but excluding the movements in regulatory deferral account balances. Furthermore, the earnings per share amount under IFRS 14 has to be presented with equal prominence to the earnings per share required by IAS 33 for all periods presented. [IFRS 14.26, IFRS 14.B14].
When an entity applying IFRS 14 presents a discontinued operation, paragraph B20 of IFRS 14 requires the movement in regulatory deferral account balances that arose from the rate-regulated activities of the discontinued operation to be excluded from the line items required by paragraph 33 of IFRS 5. Instead, the movement should be presented either (a) within the line item that is presented for movements in the regulatory deferral account balances related to profit or loss; or (b) as a separate line item alongside the related line item that is presented for movements in the regulatory deferral account balances related to profit or loss. [IFRS 14.25, IFRS 14.B20].
Similarly, notwithstanding the requirements of paragraph 38 of IFRS 5, when an entity presents a disposal group, the total of the regulatory deferral account debit balances and credit balances that are part of the disposal group are presented either (a) within the line items that are presented for the regulatory deferral account debit balances and credit balances; or (b) as separate line items alongside the other regulatory deferral account debit balances and credit balances. [IFRS 14.25, IFRS 14.B21].
If an entity chooses to include the regulatory deferral account balances and movements in those balances that are related to the disposal group or discontinued operation within the related regulated deferral account line items, it may be necessary to disclose them separately as part of the analysis of the regulatory deferral account line items described by paragraph 33 of IFRS 14. [IFRS 14.B22].
The standard requires an entity to disclose information that enables users to assess:
In order to help users of the financial statements assess the nature of, and the risks associated with, an entity's rate-regulated activities, an entity is required to disclose the following for each type of rate-regulated activity: [IFRS 14.30]
The disclosures required above may be provided in the notes to the financial statements or incorporated by cross-reference from the financial statements to some other statement such as a management commentary or a risk report that is available to users of the financial statements on the same terms as the financial statements and at the same time. [IFRS 14.31].
IFRS 14 also requires entities to explain the basis on which regulatory deferral account balances are recognised and derecognised, and how they are measured initially and subsequently, including how regulatory deferral account balances are assessed for recoverability and how impairment losses are allocated. [IFRS 14.32].
Furthermore, for each type of rate-regulated activity, an entity is required to disclose the following information for each class of regulatory deferral account balance:
When rate regulation affects the amount and timing of an entity's income tax expense (income), the entity must disclose the impact of the rate regulation on the amounts of current and deferred tax recognised. In addition, the entity must separately disclose any regulatory deferral account balance that relates to taxation and the related movement in that balance. [IFRS 14.34].
It is also important to note that when an entity provides disclosures in accordance with IFRS 12 – Disclosure of Interests in Other Entities – for an interest in a subsidiary, associate or joint venture that has rate-regulated activities and for which regulatory deferral account balances are recognised in accordance with IFRS 14, the entity must disclose the amounts that are included for the regulatory deferral account debit and credit balances and the net movement in those balances for the interests disclosed under IFRS 12. [IFRS 14.35, IFRS 14.B25-B28].
When an entity concludes that a regulatory deferral account balance is no longer fully recoverable or reversible, it must disclose that fact, the reason why it is not recoverable or reversible and the amount by which the regulatory deferral account balance has been reduced. [IFRS 14.36].
Any specific exception, exemption or additional requirements related to the interaction of IFRS 14 with other standards are contained within IFRS 14. In the absence of any such exception, exemption or additional requirements, other standards must apply to regulatory deferral account balances in the same way as they apply to assets, liabilities, income and expenses that are recognised in accordance with other standards. The following sections outline how some other IFRSs interact with the requirements of IFRS 14. In particular, the following sections clarify specific exceptions to, and exemptions from, other IFRSs and additional presentation and disclosure requirements that are expected to be applicable. [IFRS 14.16, IFRS 14.B7-B28].
An entity may need to use estimates and assumptions in the recognition and measurement of its regulatory deferral account balances. For events that occur between the end of the reporting period and the date when the financial statements are authorised for issue, an entity has to apply IAS 10 to identify whether those estimates and assumptions should be adjusted to reflect those events. [IFRS 14.B8].
Entities are required to apply the requirements of IAS 12 to rate-regulated activities, to identify the amount of income tax to be recognised. [IFRS 14.B9]. In some rate-regulatory schemes, rate regulators may permit or require an entity to increase its future rates in order to recover some or all of the entity's income tax expense. In such circumstances, this might result in the entity recognising a regulatory deferral account balance in the statement of financial position related to income tax, in accordance with its accounting policies established in accordance with paragraphs 11‑12 of IFRS 14. The recognition of this regulatory deferral account balance that relates to income tax might itself create an additional temporary difference for which a further deferred tax amount would be recognised. [IFRS 14.B10].
As a rate-regulated entity is allowed to continue applying previous GAAP accounting policies, the requirements under IAS 36 do not apply to the separate regulatory deferral account balances recognised. However, IAS 36 may require an entity to perform an impairment test on a CGU that includes regulatory deferral account balances. An impairment test would be required if:
In such situations, the requirements under paragraphs 74‑79 of IAS 36, for identifying the recoverable amount and the carrying amount of a CGU, should be applied to decide whether any of the regulatory deferral account balances recognised are included in the carrying amount of the CGU for the purpose of the impairment test. The remaining requirements of IAS 36 should then be applied to any impairment loss that is recognised as a result of this test (see Chapter 20). [IFRS 14.B16].
If an entity acquires a business, paragraph B18 of IFRS 14 provides an exception to the core principle of IFRS 3 (that is, to recognise the assets acquired and liabilities assumed at their acquisition-date fair value) for the recognition and measurement of an acquiree's regulatory deferral account balances at the date of acquisition. In other words, the acquiree's regulatory deferral account balances are recognised in the consolidated financial statements of the acquirer in accordance with the acquirer's previous GAAP policies for the recognition and measurement of regulatory deferral account balances, irrespective of whether the acquiree recognises those balances in its own financial statements. [IFRS 14.B18].
If a parent entity recognises regulatory deferral account balances in its consolidated financial statements under IFRS 14, the same accounting policies have to be applied to the regulatory deferral account balances arising in all of its subsidiaries. This should apply irrespective of whether the subsidiaries recognise those balances in their own financial statements. [IFRS 14.B23, IFRS 10.19].
Similarly, accounting policies for the recognition, measurement, impairment and derecognition of regulatory deferral account balances of an associate or joint venture will have to conform to those of the investing entity in applying the equity method. [IFRS 14.B24, IAS 28.35‑36].
The requirements of IFRS 15 are discussed in Chapter 27‑32. Paragraph D34 of IFRS 1 requires first-time adopters to apply IFRS 15 on a retrospective basis, with the option of applying the practical expedients in paragraph C5 of IFRS 15. Here are the practical expedients in paragraph C5 of IFRS 15:
For the purposes of IFRS 15, paragraph D35 of IFRS 1 defines a completed contract as a contract for which the entity has transferred all of the goods or services as identified in accordance with previous GAAP.
A first-time adopter may elect to apply one, some or all of these expedients. However, if an entity elects to use any of them, it must apply that expedient consistently to all contracts within all reporting periods presented. In addition, an entity is required to disclose the following information:
IFRIC 22 – Foreign Currency Transactions and Advance Consideration – addresses how to determine the date of the transaction for the purpose of determining the exchange rate to use on initial recognition of the related asset, expense or income (or part of it) on the derecognition of a non-monetary asset or non-monetary liability arising from the payment or receipt of advance consideration in a foreign currency. [IFRIC 22.7]. The Interpretation applies to a foreign currency transaction (or part of it) when an entity recognises a non-monetary asset or non-monetary liability arising from the payment or receipt of advance consideration before the entity recognises the related asset, expense or income (or part of it). [IFRIC 22.4].
A first-time adopter need not apply the Interpretation to assets, expenses and income in the scope of the Interpretation that were initially recognised before the date of transition to IFRSs. [IFRS 1.D36].
IFRS 9 allows some contracts to buy or sell a non-financial item to be designated at inception as measured at fair value through profit or loss. [IFRS 9.2.5]. Despite this requirement, paragraph D33 of IFRS 1 allows an entity to designate, at the date of transition to IFRSs, contracts that already exist on that date as measured at fair value through profit or loss but only if they meet the requirements of paragraph 2.5 of IFRS 9 at that date and the entity designates all similar contracts at fair value through profit or loss. [IFRS 1.D33].
An entity's first IFRS financial statements should include at least three statements of financial position, two statements of profit or loss and other comprehensive income, two separate statements of profit or loss (if presented), two statements of cash flows and two statements of changes in equity and related notes, including comparative information for all statements presented. [IFRS 1.21].
A first-time adopter is required to present notes supporting its opening IFRS statement of financial position that is clarified as a part of the Annual Improvements to IFRSs 2009‑2011 Cycle issued in May 2012. The Board explained that a first-time adopter should not be exempted from presenting three statements of financial position and related notes because it might not have presented this information previously on a basis consistent with IFRSs. [IFRS 1.BC89B].
IFRS 1 does not exempt a first-time adopter from any of the presentation and disclosure requirements in other standards, [IFRS 1.20], with the exception of certain presentation and disclosures regarding:
IAS 1 requires, except where a standard or interpretation permits or requires otherwise, comparative information in respect of the previous period for all amounts reported in the current period's financial statements and comparative information for narrative and descriptive information when it is relevant to an understanding of the current period's financial statements. [IAS 1.38].
Normally IFRSs require comparative information that is prepared on the same basis as information relating to the current reporting period. However, if an entity presents historical summaries of selected data for periods before the first period for which it presents full comparative information under IFRSs, e.g. information prepared under its previous GAAP, IFRS 1 does not require such summaries to comply with the recognition and measurement requirements of IFRSs. Furthermore, some entities present comparative information under previous GAAP in addition to the comparative information required by IAS 1. [IFRS 1.22].
If an entity presents, in the IFRS financial statements, historical summaries or comparative information under its previous GAAP, it should: [IFRS 1.22]
As an entity is only allowed to apply IFRS 1 in its first IFRS financial statements, a literal reading of IFRS 1 would seem to suggest that the above guidance is not available to an entity that prepares its second IFRS financial statements. In practice this need not cause a significant problem because this type of information is generally presented outside the financial statements, where it is not covered by the requirements of IFRSs.
Although IFRS 1 does not specifically require disclosure of the information in (a) and (b) above when the historical summaries or comparative information are presented outside the financial statements, these explanations would clearly be of benefit to users.
A first-time adopter is required to explain how the transition from its previous GAAP to IFRSs affected its reported financial position, financial performance and cash flows. [IFRS 1.23]. The IASB decided ‘that such disclosures are essential … because they help users understand the effect and implications of the transition to IFRSs and how they need to change their analytical models to make the best use of information presented using IFRSs.’ [IFRS 1.BC91].
As discussed at 3.5 and 5 above, IFRS 1 offers a wide range of exemptions that a first-time adopter may elect to apply. However, perhaps surprisingly, the standard does not explicitly require an entity to disclose which exemptions it has applied and how it applied them. In the case of, for example, the exemption relating to cumulative translation differences, it will be rather obvious whether or not an entity has chosen to apply the exemption. In other cases, users will have to rely on a first-time adopter disclosing those transitional accounting policies that are relevant to an understanding of the financial statements. In practice most first-time adopters voluntarily disclose which IFRS 1 exemptions they elected to apply and which exceptions apply to them, as is illustrated below by Extract 5.12.
If a first-time adopter did not present financial statements for previous periods, this fact should be disclosed. [IFRS 1.28]. In practice this may apply to entities that did not prepare consolidated accounts under their previous GAAP or for a newly established entity. In such cases and others, a disclosure of how the transition to IFRSs affected the entity's reported financial position, financial performance and cash flows cannot be presented, because relevant comparative information under the entity's previous GAAP does not exist.
A first-time adopter is required to present:
These reconciliations should be sufficiently detailed to enable users to understand the material adjustments to the statement of financial position, statement of profit or loss (if presented) and statement of profit or loss and other comprehensive income. [IFRS 1.25]. While the standard does not prescribe a layout for these reconciliations, the implementation guidance contains an example of a line-by-line reconciliation of the statement of financial position, statement of profit or loss and other comprehensive income. [IFRS 1.IG Example 11]. This presentation may be particularly appropriate when a first-time adopter needs to make transitional adjustments that affect a significant number of line items in the primary financial statements. If the adjustments are less pervasive a straightforward reconciliation of equity, total comprehensive income and/or profit or loss may provide an equally effective explanation of how the adoption of IFRSs affects the reported financial position, financial performance and cash flows.
If a first-time adopter becomes aware of errors made under previous GAAP, it should distinguish the correction of errors from changes in accounting policies in the above reconciliations. [IFRS 1.26]. This means that the adoption of IFRSs should not be used to mask the error.
The example below illustrates how these requirements apply to an entity whose first IFRS financial statements are for the period ending on 31 December 2020 and whose date of transition to IFRSs is 1 January 2019.
First-time adopters should not apply the requirements of IAS 8 relating to the changes in accounting policies because that standard does not apply to the changes in accounting policies an entity makes when it adopts IFRSs or changes in those policies until after it presents its first IFRS financial statements. [IFRS 1.27].
A first-time adopter should explain changes in accounting policies or in its use of exemptions during the period between its first IFRS interim financial report and its first IFRS annual financial statements (see 6.6 below) and update the reconciliations of equity and total comprehensive income discussed herein. [IFRS 1.27A]. This requirement is necessary since the first-time adopter is exempt from the requirements of IAS 8 concerning reporting of such changes. [IFRS 1.BC97].
A first-time adopter that continues to publish financial statements under previous GAAP after adopting IFRSs must consider carefully the starting point of the reconciliations required by IFRS 1 in the first IFRS financial statements because the requirements to produce reconciliations do not consider this situation. Paragraph 24 of IFRS 1 results in different applications depending on the timing of issuance of the previous GAAP financial statements in relation to the first-time adopter's first IFRS reporting period. We believe a first-time adopter, that continues to publish previous GAAP financial statements and has already issued those financial statements for the first IFRS reporting period prior to the issuance of the first IFRS financial statements, has a choice of presenting reconciliations of equity and total comprehensive income:
However, if the first IFRS financial statements were issued prior to the previous GAAP financial statements for the period, then IFRS 1 can only mean the previous GAAP financial statements for the immediate preceding year.
The extract below from the 2011 financial statements of Bombardier Inc. complies with the versions of IFRS 1 and IAS 1 that were effective in 2011. However, it still provides a good example of an entity that not only provides summary reconciliations of equity and profit or loss, but also line-by-line reconciliations, as suggested by the Implementation Guidance of IFRS 1, and detailed explanations of the reconciling items.
The exceptions and exemptions used by Bombardier on transition are shown in Extract 5.12 above. The following extract does not include all of Bombardier's detailed explanations of the reconciling items.
If a first-time adopter recognised or reversed any impairment losses on transition to IFRSs it should disclose the information that IAS 36 would have required if the entity had recognised those impairment losses or reversals in the period beginning with the date of transition to IFRSs (see Chapter 20). [IFRS 1.24]. This provides transparency about impairment losses recognised on transition that might otherwise receive less attention than impairment losses recognised in earlier or later periods. [IFRS 1.BC94].
The reconciliation disclosures required by IFRS 1 are generally quite lengthy. While IFRS 1 allows an entity's first interim report under IAS 34 to give certain of these disclosures by way of cross-reference to another published document, [IFRS 1.32‑33], there is no corresponding exemption for disclosure in the entity's first annual IFRS financial statements. Therefore, a first-time adopter should include all disclosures required by IFRS 1 within its first annual IFRS financial statements in the same way it would need to include other lengthy disclosures such as those on business combinations, financial instruments and employee benefits. Any additional voluntary information regarding the conversion to IFRSs that was previously published but that is not specifically required by IFRS 1 need not be repeated in the first IFRS financial statements.
If, on transition, a first-time adopter designates a previously recognised financial asset or financial liability as a ‘financial asset or financial liability at fair value through profit or loss’ (see 5.11.1 and 5.11.2 above), paragraphs 29 – 29A of IFRS 1 require it to disclose:
Although it is related to the designations made under IAS 39, the extract below provides a good illustration of the above disclosure requirement.
If a first-time adopter uses fair value as deemed cost for any item of property, plant and equipment, investment property, right-of-use asset under IFRS 16 or an intangible asset in its opening IFRS statement of financial position (see 5.5.1 above), it should disclose for each line item in the opening IFRS statement of financial position: [IFRS 1.30]
This disclosure is illustrated in Extracts 5.6 and 5.7 at 5.5.1 above.
If a first-time adopter measures its investments in subsidiaries, joint ventures or associates at deemed cost in the parent (joint venturer or investor) company's opening IFRS statement of financial position (see 5.8.2 above), the entity's first IFRS separate financial statements should disclose:
If a first-time adopter uses the deemed cost exemption in paragraph D8A(b) of IFRS 1 for oil and gas assets (see 5.5.3 above), it should disclose that fact and the basis on which carrying amounts determined under previous GAAP were allocated. [IFRS 1.31A].
If a first-time adopter uses the exemption for assets used in operations subject to rate regulation (see 5.5.4 above), it should disclose that fact and the basis on which carrying amounts were determined under previous GAAP. [IFRS 1.31B].
If a first-time adopter uses the exemption to elect fair value as the deemed cost in its opening IFRS statement of financial position for assets and liabilities because of severe hyperinflation (see 5.17 above), it should disclose an explanation of how, and why, the first-time adopter had, and then ceased to have, a functional currency that has both of the following characteristics: [IFRS 1.31C]
If a first-time adopter presents an interim financial report under IAS 34 for part of the period covered by its first IFRS financial statements: [IFRS 1.32]
For an entity presenting annual financial statements under IFRSs, it is not compulsory to prepare interim financial reports under IAS 34. Therefore, the above requirements only apply to first-time adopters that prepare interim reports under IAS 34 on a voluntary basis or that are required to do so by a regulator or other party. [IFRS 1.IG37].
Examples 5.38 and 5.39 below show which reconciliations should be included in half-year reports and quarterly reports, respectively.
As can be seen from the tables in Example 5.38, the additional reconciliations and explanations required under (b) above would be presented out of context, i.e. without the statement of financial position, statement of profit or loss (if presented), statement of profit or loss and other comprehensive income and statement of cash flows to which they relate. For this reason, we believe a first-time adopter should either (1) include the primary financial statements to which these reconciliations relate or (2) refer to another published document that includes these primary financial statements. The following example showing the various reconciliations to be included in the financial statements of a first-time adopter is based on the Illustrative Examples of IFRS 1: [IFRS 1.IG Example 10]
If a first-time adopter issues interim financial report in accordance with IAS 34 for part of the period covered by its first IFRS financial statements and changes accounting policies or its use of exemptions contained in IFRS 1, the first-time adopter is required to explain the changes in each such interim financial report in accordance with paragraph 23 and update the reconciliation required by paragraph 32 (a) and (b) of IFRS 1. [IFRS 1.32(c)].
Interim financial reports under IAS 34 contain considerably less detail than annual financial statements because they assume that users of the interim financial report also have access to the most recent annual financial statements. [IFRS 1.33]. However, they would be expected to provide disclosure relating to material events or transactions to allow users to understand the current interim period. Therefore, a first-time adopter needs to consider what IFRS disclosures are material to an understanding of the current interim period. A full set of IFRS accounting policy disclosures and related significant judgements and estimates should be included as well as information on the IFRS 1 exemptions employed. In addition, consideration should be given to both new disclosures not previously required under previous GAAP, and disclosures made under previous GAAP but for which the amounts contained therein have changed significantly due to changes in accounting policies resulting from the adoption of IFRSs.
It is also important to note that such disclosures apply to balances in both the opening and comparative year-end statement of financial position, each of which could be included in the first IFRS interim financial report (see 6.6.1 above). First-time adopters should expect to include significantly more information in their first IFRS interim report than would normally be included in an interim report (alternatively, it could cross refer to another published document that includes such information). [IFRS 1.33].
Examples of additional annual disclosures under IFRSs to be included in the entity's first IAS 34 compliant interim financial report could include disclosures relating to retirement benefits, income taxes, goodwill and provisions, amongst other items that significantly differ from previous GAAP and those required IFRS disclosures that are more substantial than previous GAAP.
As the adoption of IFRSs may have a significant impact on their financial statements, many entities will want to provide information on its expected impact. There are certain difficulties that arise as a result of the application of IFRS 1 when an entity decides to quantify the impact of the adoption of IFRSs. In particular, IFRS 1 requires an entity to draw up an opening IFRS statement of financial position at its date of transition based on the standards that are effective at the end of its first IFRS reporting period. Therefore, it is not possible to prepare IFRS financial information – and assess the full impact of IFRSs – until an entity knows its date of transition to IFRSs and exactly which standards will be effective at the end of its first IFRS reporting period.
If an entity wanted to quantify the impact of the adoption of IFRSs before its date of transition, it would not be able to do this in accordance with IFRS 1. While an entity would be able to select a date and apply by analogy the requirements of IFRS 1 to its previous GAAP financial information as of that date, it would not be able to claim that such additional information complied with IFRSs. An entity should avoid presenting such additional information if it is believed that the information, despite being clearly marked as not IFRS compliant, would be misleading or misunderstood.
If an entity wants to quantify the impact of the adoption of IFRSs in advance of the release of its first IFRS financial statements but after its date of transition, there may still be some uncertainty regarding the standards that apply. If so, an entity should disclose the nature of the uncertainty, as is illustrated by the extract below from the IFRS announcement of Canadian Imperial Bank of Commerce, and consider describing the information as ‘preliminary’ IFRS information.
The exceptions and exemptions of IFRS 1 are explained at 4 and 5 above, respectively. This section provides an overview of the detailed application guidance in IFRS 1 (to the extent that it is not covered in 4 and 5 above) and some of the practical application issues that are not directly related to any of the exceptions or exemptions. These issues are discussed on a standard by standard basis as follows:
A statement of cash flows prepared under IAS 7 may differ in the following ways from the one prepared under an entity's previous GAAP:
IFRS 1 requires disclosure of an explanation of the material adjustments to the statement of cash flows, if a first-time adopter presented one under its previous GAAP (see 6.3.1 above). The extract below illustrates how an IFRS statement of cash flows may differ from the one under previous GAAP.
Normally when an entity that is already using IFRS changes an accounting policy, it should apply IAS 8 to such a change. IFRS 1 requires that a first-time adopter should apply the same accounting policies in its opening IFRS statement of financial position and throughout all periods presented in its first IFRS financial statements. [IFRS 1.7]. Therefore, the change in accounting policies should be treated as a change in the entity's opening IFRS statement of financial position and the policy should be applied consistently in all periods presented in its first IFRS financial statements.
A first-time adopter may find that it needs to change IFRS accounting policies after it has issued an IFRS interim report but before issuing its first IFRS financial statements. Such a change in accounting policies could relate either to the ongoing IFRS accounting policies or to the selection of IFRS 1 exemptions.
IAS 8 does not apply to the changes in accounting policies an entity makes when it adopts IFRSs or to changes in those policies until after it presents its first IFRS financial statements. [IFRS 1.27]. Therefore, ‘if during the period covered by its first IFRS financial statements an entity changes its accounting policies or its use of the exemptions contained in this IFRS’, it should explain the changes between its first IFRS interim financial report and its first IFRS financial statements in accordance with paragraph 23 of IFRS 1 (see 6.3.1 above) and update the reconciliations required by paragraphs 24(a) and (b) of IFRS 1 (see 6.3.1 above). [IFRS 1.27A]. A similar requirement applies to the disclosures in a first-time adopter's interim financial reports (see 6.6 above). [IFRS 1.32(c)].
The distinction between changes in accounting policies and changes in accounting estimates is discussed in detail in Chapter 3.
An entity that adopts IFRSs needs to assess carefully the impact of information that has become available since it prepared its most recent previous GAAP financial statements because the new information:
There are no particular provisions in IFRS 1 with regard to the first-time adoption of IAS 12, although the implementation guidance notes that IAS 12 requires entities to provide for deferred tax on temporary differences measured by reference to enacted or substantively enacted legislation by the end of the reporting period. [IFRS 1.IG5‑6].
The full retrospective application of IAS 12 poses several problems that may not be immediately obvious. First, IAS 12 does not require an entity to account for all temporary differences. For example, an entity is not permitted under IAS 12 to recognise deferred tax on:
In addition, a change in deferred tax should be accounted for in other comprehensive income or equity, instead of profit or loss, when the tax relates to an item that was originally accounted for in other comprehensive income or equity. [IAS 12.61A].
Therefore, full retrospective application of IAS 12 requires a first-time adopter to establish the history of the items that give rise to temporary differences because, depending on the type of transaction, it may not be necessary to account for deferred tax, or changes in the deferred tax may need to be accounted for in other comprehensive income or equity.
The main issue for many first-time adopters of IFRSs will be that their previous GAAP either required no provision for deferred tax, or required provision under a timing difference approach. They also need to be aware that many of the other adjustments made to the statement of financial position at transition date will also have a deferred tax effect that must be accounted for – see, for example, the potential deferred tax consequences of recognising or derecognising intangible assets where an entity uses the business combinations exemption, described at 5.2.4.A and 5.2.5 above. Entities that reported under US GAAP must also bear in mind that IAS 12, though derived from FASB's Accounting Standard Codification 740 – Income Taxes, is different in a number of important respects.
In some cases IFRS 1 allows an entity, on transition to IFRSs, to treat the carrying amount of plant, property or equipment revalued under its previous GAAP as its deemed cost as of the date of revaluation for the purposes of IFRSs (see 5.5.1 above).
Where an asset is carried at deemed cost on transition but the tax base of the asset remains at original cost, or an amount based on original cost, the previous GAAP revaluation will give rise to a temporary difference which is typically a taxable temporary difference associated with the asset. IAS 12 requires deferred tax to be recognised at transition on any such temporary difference.
If, after transition, the deferred tax is required to be remeasured, e.g. because of a change in tax rate, or a re-basing of the asset for tax purposes, the entity elects the cost model of IAS 16 and the asset concerned was revalued outside profit or loss under previous GAAP, the question arises as to whether the resulting deferred tax income or expense should be recognised in, or outside, profit or loss.
In our view, either approach is acceptable, so long as it is applied consistently.
The essence of the argument for recognising such income or expense in profit or loss is whether the reference in paragraph 61A of IAS 12 to the tax effects of ‘items recognised outside profit or loss’ means items recognised outside profit or loss under IFRSs, or whether it can extend to the treatment under previous GAAP. [IAS 12.61A].
Those who argue that it must mean solely items recognised outside profit or loss under IFRSs note that an asset carried at deemed cost on transition is not otherwise treated as a revalued asset for the purposes of IFRSs. For example, any impairment of such an asset must be accounted for in profit or loss. By contrast, any impairment of plant, property or equipment treated as a revalued asset under IAS 16 would be accounted for outside profit or loss – in other comprehensive income – up to the amount of the cumulative revaluation gain previously recognised.
Those who hold the contrary view that it need not be read as referring only to items recognised outside profit or loss under IFRSs may do so in the context that the entity's previous GAAP required tax income and expense to be allocated between profit or loss, other comprehensive income and equity in a manner similar to that required by IAS 12. It is argued that it is inappropriate that the effect of transitioning from previous GAAP to IFRSs should be to require recognition in profit or loss of an item that would have been recognised outside profit or loss under the ongoing application of either previous GAAP or IFRSs. The counter-argument to this is that there are a number of other similar inconsistencies under IFRS 1.
A more persuasive argument for the latter view might be that, whilst IFRSs do not regard such an asset as having been revalued, it does allow the revalued amount to stand. IFRSs are therefore recognising an implied contribution by owners in excess of the original cost of the asset which, although it is not a ‘revaluation’ under IFRSs, would nevertheless have been recognised in equity on an ongoing application of IFRSs.
While IFRS 1 provides exemptions from applying IFRS 2 to share-based payment transactions that were fully vested prior to the date of transition to IFRSs, there are no corresponding exemptions from the provisions of IAS 12 relating to the tax effects of share-based payment transactions. Therefore, the provisions of IAS 12 relating to the tax effects of share-based payments apply to all share-based payment transactions, whether they are accounted for in accordance with IFRS 2 or not. A tax-deductible share-based payment transaction is treated as having a carrying amount equivalent to the total cumulative expense recognised in respect of it, irrespective of how, or indeed whether, the share-based payment is itself accounted for.
This means that on transition to IFRSs, and subject to the restrictions on recognition of deferred tax assets (see Chapter 33), a deferred tax asset should be established for all share-based payment awards outstanding at that date, including those not accounted for under the transitional provisions.
Where such an asset is remeasured or recognised after transition to IFRSs, the general rule regarding the ‘capping’ of the amount of any tax relief recognised in profit or loss to the amount charged to the profit or loss applies (see Chapter 33 at 10.8.1). Therefore, if there was no profit or loss charge for share-based payment transactions under the previous GAAP, all tax effects of share-based payment transactions not accounted for under IFRS 2 should be dealt with within equity. [IAS 12.68C].
The adjustments arising from different accounting policies under previous GAAP and IFRS should be recognised directly in retained earnings (or, if appropriate, another category of equity) at the date of transition to IFRSs. [IFRS 1.11].
IAS 12 requires current tax and deferred tax that relates to items that are recognised, in the same or a different period, directly in equity, to be recognised directly in equity. However, as drafted, IAS 12 can also be read as requiring any subsequent remeasurement of such tax effects to be accounted for in retained earnings because the amount to be remeasured was originally recognised in retained earnings. This could give rise to a rather surprising result, as illustrated by Example 5.40 below.
We question whether it was really the intention of IAS 12 that these remeasurements be recognised in retained earnings. There is a fundamental difference between an item that by its nature would always be recognised directly outside profit or loss (e.g. certain foreign exchange differences or revaluations of plant, property and equipment) and an item which in the normal course of events would be accounted for in profit or loss, but when recognised for the first time (such as in Example 5.40 above) is dealt with as a ‘catch up’ adjustment to opening retained earnings. If it had done so, all the charge for environmental costs (and all the related deferred tax) would have been reflected in profit or loss in previous income statements. Therefore, it is our view that subsequent changes to such items recognised as a ‘catch-up’ adjustment upon transition to IFRSs should be recognised in profit or loss.
IAS 19 requires an entity, in accounting for a post-employment defined benefit plan, to recognise actuarial gains and losses relating to the plan in other comprehensive income. At the same time, service cost and net interest on the net defined benefit liability (asset) is recognised in profit or loss.
In many jurisdictions, tax relief for post-employment benefits is given on the basis of cash contributions paid to the plan fund (or benefits paid when a plan is unfunded).
This significant difference between the way in which defined benefit plans are treated for tax and financial reporting purposes can make the allocation of tax between profit or loss and other comprehensive income somewhat arbitrary.
The issue is of particular importance when a first-time adopter has large funding shortfalls on its defined benefit schemes and at the same time can only recognise part of its deferred tax assets. In such a situation the method of allocation may well affect the after-tax profit in a given year. In our view (see Chapter 33), these are instances of the exceptional circumstances envisaged by IAS 12 when a strict allocation of tax between profit or loss and other comprehensive income is not possible. Accordingly, any reasonable method of allocation may be used, provided that it is applied on a consistent basis.
One approach might be to compare the funding payments made to the scheme in a few years before the adoption of IFRS with the charges that would have been made to profit or loss under IAS 19 in those periods. If, for example, it is found that the payments were equal to or greater than the charges to profit or loss, it could reasonably be concluded that any surplus or deficit on the statement of financial position is broadly represented by items that have been accounted for in other comprehensive income.
The implementation guidance discussed in this section applies to property, plant and equipment as well as investment properties that are accounted for under the cost model in IAS 40. [IFRS 1.IG62].
If a first-time adopter's depreciation methods and rates under its previous GAAP are acceptable under IFRSs then it accounts for any change in estimated useful life or depreciation pattern prospectively from when it makes that change in estimate (see 4.2 above). However, if the depreciation methods and rates are not acceptable and the difference has a material impact on the financial statements, a first-time adopter should adjust the accumulated depreciation in its opening IFRS statement of financial position retrospectively. [IFRS 1.IG7]. Additional differences may arise from the requirement in IAS 16 to review the residual value and the useful life of an asset at least each financial year end, [IAS 16.51], which may not be required under a first-time adopter's previous GAAP.
If a restatement of the depreciation methods and rates would be too onerous, a first-time adopter could opt instead to use fair value as the deemed cost. However, application of the deemed cost exemption is not always the only approach available. In practice, many first-time adopters have found that, other than buildings, there are generally few items of property, plant and equipment that still have a material carrying amount after more than 30 or 40 years of use. Therefore, the carrying value that results from a fully retrospective application of IAS 16 may not differ much from the carrying amount under an entity's previous GAAP.
An entity may use fair value as deemed cost for an item of property, plant and equipment still in use that it had depreciated to zero under its previous GAAP (i.e. the asset has already reached the end of its originally assessed economic life). Although IFRS 1 requires an entity to use estimates made under its previous GAAP, paragraph 51 of IAS 16 would require the entity to re-assess the remaining useful life and residual value at least annually. [IAS 16.51]. Therefore, the asset's deemed cost should be depreciated over its re-assessed economic life and taking into account its re-assessed residual value.
The same applies when an entity does not use fair value or revaluation as deemed cost. If there were indicators in the past that the useful life or residual value changed but those changes were not required to be recognised under previous GAAP, the IFRS carrying amount as of the date of transition should be determined by taking into account the re-assessed useful life and the re-assessed residual value. Often, this is difficult, as most entities would not have re-assessed the useful lives contemporaneously with the issuance of the previous GAAP financial statements. Accordingly, the fair value as deemed cost exemption might be the most logical choice.
A first-time adopter that chooses to account for some or all classes of property, plant and equipment under the revaluation model needs to present the cumulative revaluation surplus as a separate component of equity. IFRS 1 requires that ‘the revaluation surplus at the date of transition to IFRSs is based on a comparison of the carrying amount of the asset at that date with its cost or deemed cost.’ [IFRS 1.IG10].
A first-time adopter that uses fair value as the deemed cost for those classes of property, plant and equipment would be required to reset the cumulative revaluation surplus to zero. Therefore any previous GAAP revaluation surplus related to assets valued at deemed cost cannot be used to offset a subsequent impairment or revaluation loss under IFRSs. The following example illustrates the treatment of the revaluation reserve at the date of transition based on different deemed cost exemptions applied under IFRS 1.
IAS 16 requires a ‘parts approach’ to the recognition of property, plant and equipment. Thus a large item such as an aircraft is recognised as a series of ‘parts’ that may have different useful lives. An engine of an aircraft may be a part. IAS 16 does not prescribe the physical unit of measure (the ‘part’) for recognition i.e. what constitutes an item of property, plant and equipment. [IFRS 1.IG12]. Instead the standard relies on judgement in applying the recognition criteria to an entity's specific circumstances. [IAS 16.9]. However, the standard does require an entity to:
Based on this, it is reasonable to surmise that parts can be relatively small units. Therefore, it is possible that even if a first-time adopter's depreciation methods and rates are acceptable under IFRSs, it may have to restate property, plant and equipment because its unit of measure under previous GAAP was based on physical units significantly larger than parts as described in IAS 16. Accounting for parts is described in detail in Chapter 18.
In practice, however, there is seldom a need to account for every single part of an asset separately. Very often there is no significant difference in the reported amounts once all significant parts have been identified. Furthermore, as explained in Chapter 18, an entity may not actually need to identify the parts of an asset until it incurs the replacement expenditure.
Other than the exemption in D9 of IFRS 1 there are no exemptions regarding lease accounting available to a first-time adopter that is a lessor. Therefore, at the date of transition to IFRSs, a lessor classifies a lease as operating or financing on the basis of circumstances existing at the inception of the lease. [IFRS 16.66]. Lease classification is reassessed only if there is a lease modification. Changes in estimates (for example, changes in estimates of the economic life or the residual value of the underlying asset) or changes in circumstances (for example, default by the lessee) do not give rise to a new classification of a lease. [IFRS 1.IG14]. See Chapter 23 for further discussion about modifying lease terms under IFRS 16.
A first-time adopter that has received amounts that do not yet qualify for recognition as revenue under IFRS 15 (e.g. the proceeds of a sale that does not qualify for revenue recognition) should recognise those amounts as a liability in its opening IFRS statement of financial position and adjust the liability for any significant financing component as required by IFRS 15. [IFRS 1.IG17]. It is therefore possible that revenue that was already recognised under a first-time adopter's previous GAAP will need to be deferred in its opening IFRS statement of financial position and recognised again (this time under IFRSs) as revenue at a later date.
Conversely, it is possible that revenue deferred under a first-time adopter's previous GAAP cannot be recognised as a contract liability in the opening IFRS statement of financial position. A first-time adopter would not be able to report such revenue deferred under its previous GAAP as revenue under IFRSs at a later date. See Chapter 27‑32 for matters relating to revenue recognition under IFRS 15.
IAS 19 requires the disclosures set out below about sensitivity of defined benefit obligations. Therefore for an entity's first IFRS financial statements careful preparation must be done to compile the information required to present the sensitivity disclosure for the current and comparative periods. IAS 19 requires an entity to disclose: [IAS 19.145]
An entity's first IFRS financial statements reflect its defined benefit liabilities or assets on at least three different dates, that is, the end of the first IFRS reporting period, the end of the comparative period and the date of transition to IFRSs (four different dates if it presents two comparative periods). If an entity obtains a full actuarial valuation at one or two of these dates, it is allowed to roll forward (or roll back) to another date but only as long as the roll forward (or roll back) reflects material transactions and other material events (including changes in market prices and interest rates) between those dates. [IFRS 1.IG21].
A first-time adopter's actuarial assumptions at its date of transition should be consistent with the ones it used for the same date under its previous GAAP (after adjustments to reflect any difference in accounting policies), unless there is objective evidence that those assumptions were in error (see 4.2 above). The impact of any later revisions to those assumptions is an actuarial gain or loss of the period in which the entity makes the revisions. [IFRS 1.IG19].
If a first-time adopter needs to make actuarial assumptions at the date of transition that were not necessary for compliance with its previous GAAP, those actuarial assumptions should not reflect conditions that arose after the date of transition. In particular, discount rates and the fair value of plan assets at the date of transition should reflect the market conditions at that date. Similarly, the entity's actuarial assumptions at the date of transition about future employee turnover rates should not reflect a significant increase in estimated employee turnover rates as a result of a curtailment of the pension plan that occurred after the date of transition. [IFRS 1.IG20].
If there is a material difference arising from a change in assumptions at the transition date, consideration needs to be given to whether there was an error under previous GAAP. Errors cannot be recognised as transition adjustments (see 6.3.1 above).
IAS 19 requires immediate recognition of all past service costs. [IAS 19.103]. Accordingly, a first-time adopter that has unrecognised past service costs under previous GAAP must recognise such amount in retained earnings at the date of transition, regardless of whether the participants are fully vested in the benefit.
A first-time adopter needs to confirm whether all entities included within the financial statements have appropriately determined their functional currency. IAS 21 defines an entity's functional currency as ‘the currency of the primary economic environment in which the entity operates’ and contains detailed guidance on determining the functional currency. [IAS 21.8‑14].
If the functional currency of an entity is not readily identifiable, IAS 21 requires consideration of whether the activities of the foreign operation are carried out as an extension of the reporting entity, rather than being carried out with a significant degree of autonomy. [IAS 21.11]. This requirement often leads to the conclusion under IFRSs that intermediate holding companies, treasury subsidiaries and foreign sales offices have the same functional currency as their parent.
Many national GAAPs do not specifically define the concept of functional currency, or they may contain guidance on identifying the functional currency that differs from that in IAS 21. Consequently, a first-time adopter that measured transactions in a currency that was not its functional currency under IFRS would need to restate its financial statements because IFRS 1 does not contain an exemption that would allow it to use a currency other than the functional currency in determining the cost of assets and liabilities in its opening IFRS statement of financial position. The exemption that allows a first-time adopter to reset the cumulative exchange differences in equity to zero cannot be applied to assets or liabilities (see 5.7 above). The IFRIC considered whether a specific exemption should be granted to first-time adopter to permit entities to translate all assets and liabilities at the transition date exchange rate rather than applying the functional currency approach in IAS 21 but declined to offer first-time adopters any exemptions on transition on the basis that the position under IFRS 1 and IAS 21 was clear.5
The principal difficulty relates to non-monetary items that are measured on the basis of historical cost, particularly property, plant and equipment, since these will need to be re-measured in terms of the IAS 21 functional currency at the rates of exchange applicable at the date of acquisition of the assets concerned, and recalculating cumulative depreciation charges accordingly. It may be that, to overcome this difficulty, an entity should consider using the option in IFRS 1 whereby the fair value of such assets at the date of transition is treated as being their deemed cost (see 5.5.1 above).
There are a number of first-time adoption exemptions that have an impact on the accounting for investments in associates and joint ventures:
Otherwise there are no specific first-time adoption provisions for IAS 28, which means that a first-time adopter of IFRSs is effectively required to apply IAS 28 as if it had always done so. For some first-time adopters, this may mean application of the equity method for the first time. For the majority of first-time adopters, however, the issue is likely to be that they are already applying the equity method under their previous GAAPs and will now need to identify the potentially significant differences between the methodologies of the equity method under their previous GAAP and under IAS 28.
In particular there may be differences between:
A first-time adopter of IFRSs is required by IFRS 1 to perform an impairment test in accordance with IAS 36 to any goodwill recognised at the date of transition to IFRSs, regardless of whether there is any indication of impairment. [IFRS 1.C4(g)(ii)]. IFRS 1 specifically notes that its provisions with regard to past business combinations apply also to past acquisitions of investments in associates, interests in joint ventures and interests in joint operations (in which the activity of the joint operation constitutes a business, as defined in IFRS 3). [IFRS 1.C5]. Therefore, a transition impairment review must be undertaken for investments in associates or joint venture whose carrying value includes an element of goodwill. This impairment review will, however, need to be carried out on the basis required by IAS 28 as described in Chapter 11. See also 5.2.5 above.
The IASB decided not to exempt first-time adopters from retrospective application of IAS 29 because hyperinflation can make unadjusted financial statements meaningless or misleading. [IFRS 1.BC67].
Therefore, in preparing its opening IFRS statement of financial position a first-time adopter should apply IAS 29 to any periods during which the economy of the functional currency or presentation currency was hyperinflationary. [IFRS 1.IG32]. However, to make the restatement process less onerous, a first-time adopter may want to consider using fair value as deemed cost for property, plant and equipment (see 5.5.1 above). [IFRS 1.D5, IG33]. This exemption is also available to other long-lived assets such as investment properties, right-of-use assets under IFRS 16 and certain intangible assets. [IFRS 1.D7]. If a first-time adopter applies the exemption to use fair value or a revaluation as deemed cost, it applies IAS 29 to periods after the date for which the revalued amount or fair value was determined. [IFRS 1.IG34].
The ‘business combinations’ exemption described at 5.2 above is also applicable to joint ventures and joint operations in which the activity of the joint operation constitutes a business, as defined by IFRS 3. Also, the first-time adoption exemptions that are available for investments in associates can also be applied to investments in joint ventures (see 7.9 above) and the requirements to test the investment in associates for impairment at the transition date regardless of whether there were indicators of impairment will need to be applied also to investments in joint ventures (see 5.2.5 and 7.9.1 above). [IFRS 1.C4(g)(ii)].
With respect to joint operations, the requirements of IFRS 11 may well result in the ‘re-recognition’ of assets that were transferred to others and therefore not recognised under previous GAAP. A joint operator is required to recognise its assets and liabilities, including its share of those assets that are jointly held and liabilities that are jointly incurred, based on the requirements of IFRSs applicable to such assets or liabilities. [IFRS 11.20‑23].
As far as goodwill is concerned, first time adopters of IFRSs are required by IFRS 1 to subject all goodwill carried in the statement of financial position at the date of transition to an impairment test, regardless of whether there are any indicators of impairment (see 5.2.5 above). [IFRS 1.C4(g)(ii)].
While IFRS 1 does not specifically call for an impairment test of other assets, a first-time adopter should be mindful that there are no exemptions in IFRS 1 from full retrospective application of IAS 36. The implementation guidance reminds a first-time adopter to:
As impairment losses for non-financial long-lived assets other than goodwill can be reversed under IAS 36, in many instances, there will be no practical difference between applying IAS 36 fully retrospectively and applying it at the transition date. Performing the test under IAS 36 at transition date should result in re-measuring any previous GAAP impairment to comply with the approach in IAS 36 and recognition of any additional impairment or reversing any previous GAAP impairment that is no longer necessary.
The estimates used to determine whether a first-time adopter recognises an impairment loss or provision at the date of transition to IFRSs should be consistent with estimates made for the same date under previous GAAP (after adjustments to reflect any difference in accounting policies), unless there is objective evidence that those estimates were in error. [IFRS 1.IG40]. If a first-time adopter needs to make estimates and assumptions that were not necessary under its previous GAAP, they should not reflect conditions that arose after the date of transition to IFRSs. [IFRS 1.IG41].
If a first-time adopter's opening IFRS statement of financial position reflects impairment losses, it recognises any later reversal of those impairment losses in profit or loss unless IAS 36 requires that reversal to be treated as a revaluation. This applies to both impairment losses recognised under previous GAAP and additional impairment losses recognised on transition to IFRSs. [IFRS 1.IG43].
An impairment test might be more appropriate if a first-time adopter makes use of any of the deemed cost exemptions. In arguing that it is not necessary to restrict application of the deemed cost exemption to classes of assets to prevent selective revaluations, the IASB effectively relies on IAS 36 to avoid overvaluations:
The main issue for a first-time adopter in applying IAS 37 is that IFRS 1 prohibits retrospective application of some aspects of IFRSs relating to estimates. This is discussed in detail at 4.2 above. Briefly, the restrictions are intended to prevent an entity from applying hindsight and making ‘better’ estimates as at the date of transition. Unless there is objective evidence that those estimates were in error, recognition and measurement are to be consistent with estimates made under previous GAAP, after adjustments to reflect any difference in accounting policies. The entity has to report the impact of any later revisions to those estimates as an event of the period in which it makes the revisions. [IFRS 1.IG40]. An entity cannot use hindsight in determining the provisions to be included under IAS 37 at the end of the comparative period within its first IFRS financial statements as these requirements also apply at that date. [IFRS 1.14‑17].
At the date of transition, an entity may also need to make estimates that were not necessary under its previous GAAP. Such estimates and assumptions must not reflect conditions that arose after the date of transition to IFRSs. [IFRS 1.IG41].
If application of IAS 37 changes the way an entity accounts for provisions it needs to consider whether there are any consequential changes, for example:
The above list is not exhaustive and a first-time adopter should carefully consider whether changes in other provisions have a consequential impact.
An entity's opening IFRS statement of financial position: [IFRS 1.IG44]
IAS 38 imposes a number of criteria that restrict capitalisation of internally generated intangible assets. An entity is prohibited from using hindsight to conclude retrospectively that the recognition criteria are met, thereby capitalising an amount previously recognised as an expense. [IAS 38.71]. A first-time adopter of IFRSs must be particularly careful that, in applying IAS 38 retrospectively as at the date of transition, it does not capitalise costs incurred before the standard's recognition criteria were met. Therefore, a first-time adopter is only permitted to capitalise the costs of internally generated intangible assets when it:
In other words, it is not permitted under IFRS 1 to reconstruct retrospectively the costs of intangible assets.
If an internally generated intangible asset qualifies for recognition at the date of transition, it is recognised in the entity's opening IFRS statement of financial position even if the related expenditure had been expensed under previous GAAP. If the asset does not qualify for recognition under IAS 38 until a later date, its cost is the sum of the expenditure incurred from that later date. [IFRS 1.IG47]. However, a first-time adopter that did not capitalise internally generated intangible assets is unlikely to have the type of documentation and systems required by IAS 38 and will therefore not be able to capitalise these items in its opening IFRS statement of financial position. Going forward, a first-time adopter will need to implement internal systems and procedures that enable it to determine whether or not any future internally generated intangible assets should be capitalised (for example, in the case of development costs).
Capitalisation of separately acquired intangible assets will generally be easier because there is usually contemporaneous documentation prepared to support the investment decisions. [IFRS 1.IG48]. However, if an entity that used the business combinations exemption did not recognise an intangible asset acquired in a business combination under its previous GAAP, it would only be able to do so upon first-time adoption if the intangible asset were to qualify for recognition under IAS 38 in the acquiree's statement of financial position (see 5.2.4.B above). [IFRS 1.IG49].
If a first-time adopter's amortisation methods and rates under previous GAAP are acceptable under IFRSs, the entity does not restate the accumulated amortisation in its opening IFRS statement of financial position. Instead, the entity accounts for any change in estimated useful life or amortisation pattern prospectively from the period when it makes that change in estimate. If an entity's amortisation methods and rates under previous GAAP differ from those acceptable in accordance with IFRSs and those differences have a material effect on the financial statements, the entity would adjust the accumulated amortisation in its opening IFRS statement of financial position. [IFRS 1.IG51].
The useful life and amortisation method of an intangible asset should be reviewed at least each financial year end (see Chapter 17), which is often something that is not required under a first-time adopter's previous GAAP. [IAS 38.104].
A foreign private issuer that is registered with the US Securities and Exchange Commission (SEC) is normally required to present two comparative periods for its statement of profit or loss and other comprehensive income (or statement of profit or loss, if presented), statement of cash flows and statement of changes in equity. Converting two comparative periods to IFRSs was considered to be a significant burden to companies. Therefore, in April 2005, the SEC published amendments to Form 20‑F that provided for a limited period a two-year accommodation for foreign private issuers that were first-time adopters of IFRSs.6 In March 2008, the SEC extended indefinitely the two-year accommodation to all foreign private issuers that are first-time adopters of IFRSs as issued by the IASB.7
The amendment states that ‘an issuer that changes the body of accounting principles used in preparing its financial statements presented pursuant to Item 8.A.2 of its Form 20-F (“Item 8.A.2”) to International Financial Reporting Standards (“IFRS”) issued by the International Accounting Standards Board (“IASB”) may omit the earliest of three years of audited financial statements required by Item 8.A.2 if the issuer satisfies the conditions set forth in the related Instruction G. For purposes of this instruction, the term “financial year” refers to the first financial year beginning on or after January 1 of the same calendar year.’ The accommodation only applies to an issuer that (a) adopts IFRSs for the first time by an explicit and unreserved statement of compliance with IFRSs as issued by the IASB and (b) the issuer's most recent audited financial statements are prepared in accordance with IFRSs.
First-time adopters that rely on the accommodation are allowed, but not required, to include any financial statements, discussions or other financial information based on their previous GAAP. If first-time adopters do include such information, they should prominently disclose cautionary language to avoid inappropriate comparison with information presented under IFRSs. The SEC did not mandate a specific location for any previous GAAP information but did prohibit presentation of previous GAAP information in a side-by-side columnar format with IFRS financial information.
In addition, the accommodation only requires entities to provide selected historical financial data based on IFRSs for the two most recent financial years instead of the normal five years. Selected historical financial data based on US GAAP is not required for the five most recent financial years. Although the SEC does not prohibit entities from including selected financial data based on previous GAAP in their annual reports, side-by-side presentation of data prepared under IFRSs and data prepared under previous GAAP is prohibited. In addition, inclusion of previous GAAP selected financial data will trigger the requirement for the corresponding reconciled US GAAP selected financial data.8
Where a narrative discussion of its financial condition is provided, the accommodation requires management to focus on the financial statements prepared under IFRSs as issued by the IASB for the past two financial years.
IFRS 1 requires a first-time adopter to present reconciliations from its previous GAAP to IFRSs in the notes to its financial statements and allows certain exemptions from full retrospective application of IFRSs in deriving the relevant data. Under the SEC's accommodation, any issuer relying on any of the elective exemptions or mandatory exceptions from IFRSs that are contained within IFRS 1 will have to disclose additional information which includes:
In November 2008, the Center for Audit Quality SEC Regulations Committee's International Practices Task Force (‘IPTF’) provided guidance as to the reconciliation requirements of an SEC foreign private issuer the first time it presents IFRS financial statements in its Form 20‑F, when that issuer previously used US GAAP for its primary financial statements filed with the SEC. 9 Among others, the IPTF guidance addresses the concern that the reconciliations called for by IFRS 1, which are prepared using the issuer's local GAAP rather than US GAAP, would not have sufficient information to help US investors to bridge from the prior US GAAP financial statements filed with the SEC to IFRSs. Accordingly, the IPTF guidance requires additional detailed reconciliations in these circumstances from US GAAP to IFRSs either in a one step or a two-step format (see below).
The reconciliation requirements for each of the scenarios are described below:
Although IFRS 1 provides detailed rules on disclosures to be made in an entity's first IFRS financial statements and in interim reports covering part of its first IFRS reporting period, it does not provide any guidance on presenting a reconciliation to IFRSs in financial reports before the start of the first IFRS reporting period. An entity wishing to disclose information on the impact of IFRSs in its last financial statements under its previous GAAP cannot claim that such information is prepared and presented in accordance with IFRSs because it does not disclose all information required in full IFRS financial statements and it does not disclose comparative information.
As the extract below illustrates, in practice, some entities get around this problem by disclosing pro forma IFRS information and stating that the pro forma information does not comply with IFRSs.
In certain countries, publicly listed companies are required by regulation to disclose the potential impact that recently issued accounting standards will have on their financial statements when such standards are adopted in the future. The Canadian Securities Administrators (the CSA) in their Management's Discussion & Analysis (MD&A form)10 require this disclosure for changes in accounting policies that registrants expect to make in the future. In connection with the transition to IFRSs, the CSA issued a Staff Notice11 clarifying that ‘changes in an issuer's accounting policies that an issuer expects to make on changeover to IFRSs are changes due to new accounting standards and therefore fall within the scope of the MD&A form.’ Among other matters, the CSA Staff Notice requires certain disclosures of companies that have developed an IFRS changeover plan, in interim and annual MD&A forms starting three years before the first IFRS financial statement date, including the following:
The CSA Staff Notice also specified requirements for update for periods up to the year of changeover, including discussion of the impact of transition for issuers that are well advanced in their plans.
An entity that is planning to adopt IFRS should take note of the regulatory requirements in its jurisdiction or the exchange where it is listed to determine the form of communication that is required in advance of publishing its first IFRS financial statements.