Staff Paper Date October 2009

Transcription

1 IASB Meeting Agenda reference Appendix to Paper 7 Staff Paper Date October 2009 Project Liabilities amendments to IAS 37 Topic In June 2005, the Board published for comment an Exposure Draft of Proposed Amendments to IAS 37 Provisions, Contingent Liabilities and Contingent Assets. This appendix is a staff summary of the tentative decisions that the Board has reached since then, in the light of comments received. It lists all decisions that either reaffirm or change the exposure draft proposals. Its purpose is to support Paper 7, which asks the Board to decide whether and how to re-expose the proposals for further comment. The Board discussed some topics at several meetings and modified its decisions as the discussions progressed. This appendix excludes initial decisions that the Board modified at a later meeting. The decisions are tentative. Tentative decisions do not change existing requirements. Decisions become effective only when the Board has incorporated them in a new or amended standard. Page 1 of 18

2 1 Format and scope Topic Tentative decision Comparison with exposure draft proposals 1.1 Format 1.2 Scope The output of the project should be a new IFRS, not an amended version of IAS 37. (September 2009) The revised IAS 37 should apply to all liabilities not within the scope of other standards. The standard should clarify explicitly that performance obligations measured applying IAS 18 Revenue on the basis of consideration received (deferred revenue) are not within the scope of the revised IAS 37. The Board formatted the exposure draft as an amended version of IAS 37. However, the amendments were too extensive to be marked in the draft. The change will affect only the layout of the standard. It will not affect the requirements, nor significantly affect the way in which the requirements are expressed. Clarifies a point that was implicit in the exposure draft. Page 2 of 18

3 2 Liability definition Topic Tentative decision Comparison with exposure draft proposals 2.1 Contingent liability 2.2 Expected to result in an outflow... of resources 2.3 Present obligation The revised IAS 37 should eliminate the notion of a contingent liability. (July 2006) The revised IAS 37 should clarify the meaning of the term expected in the definition. The term does not imply that there must be a particular degree of certainty that an outflow of benefits will occur before an item meets the definition of a liability. Present obligations that are capable of resulting in an outflow of resources meet the definition of a liability, even if the likelihood of an outflow is low. (May 2006) To emphasise the differences between liabilities and business risks, and to clarify the definition of a constructive obligation, the revised standard should state that: - an obligation exists when an entity has a duty or responsibility to act or perform in a particular way - the duty or responsibility is to another party - and exists independently of future events. (July 2007) The exposure draft described a present obligation as something that the entity has little, if any, discretion to avoid settling. This phrase is ambiguous and difficult to apply. The staff should consider whether to retain the phrase in the revised standard and, if so, where to position it. (July 2007) This was not explicit in the exposure draft. But it was implicit in the discussion of stand-ready obligations. The redrafting will change the emphasis from little if any discretion to avoid to duty or responsibility to perform. It addresses commentators concerns that the former phrase is ambiguous. The phrase duty or responsibility to act or perform in a particular way was not used in the exposure draft. But it is the phrase used to describe an obligation in paragraph 60 of the IASB Framework. So it is not new. Page 3 of 18

4 Topic Tentative Decision Comparison with exposure draft proposals 2.4 Distinguishing liabilities from business risks. 2.5 Stand-ready obligations The revised IAS 37 should include further guidance clarifying that: - the existence of a present obligation distinguishes a liability from a business risk. (March 2007, July 2007) - both business risks and liabilities cause a potential outflow of economic benefits. Hence the possibility of such an outflow does not distinguish a liability from a business risk. (July 2007) A stand-ready obligation is one in which there is uncertainty about the outflow of economic benefits, not uncertainty about whether a present obligation exists. (July 2007) Uncertainty about past events can make it uncertain whether a liability exists. In contrast, a stand-ready obligation arises if there is uncertainty about future events. The hamburger and hospital examples were examples in which it was uncertain whether a present obligation existed. (May 2007) The label stand-ready obligation might be confusing for some people but is a helpful short-hand term. The staff should consider other phrases or terms when drafting the standard. (March 2007) Emphasis added in response to concerns from commentators (reported in May 2006) that stand-ready obligations appeared to include a limitless number of items, including those currently regarded as business risks. Additional clarification to help explain why stand-ready obligations do not include business risks. Page 4 of 18

5 Topic Tentative decision Comparison with exposure draft proposals 2.6 Uncertainty about existence of present obligation The revised IAS 37 should provide more guidance on situations (eg litigation) in which it is uncertain whether a present obligation exists. (May 2006) The guidance should acknowledge that it might be uncertain whether an entity has a present obligation if it is uncertain: (a) (b) whether a transaction or event has occurred; whether a transaction or event that has occurred gives rise to a present obligation; or (c) how the law or regulations apply to that event. (July 2007) The revised IAS 37 should emphasise that: (a) (b) (c) identifying whether a liability exists requires judgement. management should use all available evidence, which might include the entity s own experience with similar items, other entities experience with similar items, opinions of experts and additional evidence provided by events that occurred after the balance sheet date. the sources of evidence listed in (b) are not exhaustive. The final standard should include further application guidance or be accompanied by illustrative examples. (June 2006, July 2007) The revised IAS 37 should not specify an explicit probability threshold for identifying liabilities in situations of uncertainty. (October 2007) The proposed guidance is similar to existing guidance (in paragraph 16 of IAS 37), some of which was omitted from the exposure draft. Commentators asked for more guidance than that included in the exposure draft. The guidance is important. It clarifies that, even although the probability recognition criterion is being deleted from the revised standard (see Decision 3.1), entities defending legal claims do not necessarily recognise liabilities. Management needs to reach a judgement about whether a liability exists Page 5 of 18

6 Topic Tentative decision Comparison with exposure draft proposals 2.7 Constructive obligations The final standard should emphasise the need for a present obligation (ie a duty or responsibility to another party). A management decision or an intention to incur a future outflow of economic benefits does not in itself amount to a constructive obligation. (July 2007) The standard should not define legal and constructive obligations as separate types of obligation some constructive obligations can be legally enforceable. The existing definitions should be deleted and replaced by guidance within the text of the standard. (July 2007) Changed wording, consistent with proposed changes to guidance on the meaning of present obligation (see Decision 2.3) Eliminates an apparent contradiction in the exposure draft. 2.8 Illustrative Example 1 Disputed lawsuit The conclusion proposed in the exposure draft ie that the start of legal proceedings obliges the entity to stand-ready to perform as the court directs was wrong. Rather, the start of legal proceedings is just one piece of evidence that would be relevant to the assessment of whether the entity has an obligation. The illustrative example should be modified accordingly. (June 2006) Change in conclusion new conclusion in line with current practice, constituent views and other decisions reported in this section. Page 6 of 18

7 3 Liability recognition criteria Topic Tentative decision Comparison with exposure draft proposals 3.1 Probability recognition criterion (which requires entities to recognise liabilities only if it is probable that an outflow of resources will be required to settle the obligation). 3.2 Reliable measurement criterion The criterion should be deleted from IAS 37 (February 2008): - it gives a flawed result, ie that some obligations (eg guarantees) are not recognised when the liability arises. - it has little impact in practice in most cases in which a liability is identified, it is probable that there will be some outflow. - it is inconsistent with the proposed measurement requirements, which require entities to take into account all possible outcomes. - it delays the inclusion of decision-useful information in the financial statements. (June 2006) The practical benefits of the criterion (ie that it stops entities having to identify and recognise liabilities for which the costs of recognition exceed the benefits) do not justify its retention. (February 2008) The revised standard should continue to refer to the circumstances in which a liability cannot be measured reliably as extremely rare. There is no need for additional guidance to help preparers identify these circumstances. (June 2009) Page 7 of 18

8 Topic Tentative decision Comparison with exposure draft proposals 3.3 Recognition exemptions There should be no exemptions from the recognition requirements on the grounds of disclosure of prejudicial information. The Board cannot accommodate concerns about the operation of different legal jurisdictions in one standard. Exemptions would compromise the usefulness of the information provided in the financial statements. The prejudicial information disclosure exemption will remain in IAS 37, and is sufficient. (July 2006) The proposed changes to IAS 37 don t introduce any new factors that will cause additional problems in the US legal environment. (June 2009) Page 8 of 18

9 4 Liability measurement Topic Tentative decision Comparison with exposure draft proposals 4.1 Clarifying the measurement requirement The revised standard should clarify the meaning of the proposed measurement requirement. (September 2006, December 2007) The revised standard should state that: 1 The requirement is to measure the amount that the entity would rationally pay on the reporting date to be relieved of the present obligation. (July 2009) 2 The amount that the entity would rationally pay to be relieved of the present obligation is the lowest of: - the value the entity would gain if it did not have to fulfil the obligation; - the amount the entity would have to pay the counterparty to cancel the obligation; and - the amount the entity would have to pay a third party to transfer the obligation to that party. (July 2009) 4 If there is no evidence that the entity could cancel the obligation or transfer it to a third party for a lower amount, the entity measures the liability at the value it would gain if it did not have to fulfil the obligation. (July 2009) Continues on next page / The decision to clarify the measurement requirement responds to comments that the requirement proposed in the exposure draft was unclear. The additional guidance does not change the requirement proposed in the exposure draft. But it is based on one possible interpretation of the requirement. It is a different interpretation from that widely applied in practice at present. The Board did not discuss this (or other) interpretations in the exposure draft. Page 9 of 18

10 Topic Tentative decision Comparison with exposure draft proposals / Continued 5 An entity estimates the value it would gain if it did not have to fulfil the obligation using expected present value techniques. The calculations take into account: - the outflows of resources expected to be required to fulfil the obligation (the probability-weighted average of the possible outcomes); - the time value of money; and - if the amount or timing of the outflows is uncertain, any additional amount the entity would rationally pay to be relieved of risk. (September 2009) 6 An entity should measure the resource outflows at their value, not cost. If the obligation is to provide a service at a future date, the entity measures the service outflows at the amount it would rationally pay a contractor at the future date to carry out the service on its behalf. - if a market exists for such services, the amount is the price that a contractor would charge. - if no market exists, the entity would estimate the amount. (September 2009) The Board directed the staff to develop guidance explaining how, in the absence of a market, an entity would use a building block approach to estimate the amount it would rationally pay a contractor to carry out the service. (September 2009) [Staff note: The entity would estimate how much it would charge another party to undertake the service. This amount would take into account the expected costs and the margin the entity would require for providing the service.] Page 10 of 18

11 Topic Tentative decision Comparison with exposure draft proposals 4.2 Rationale for measurement requirement 4.3 Application guidance 4.4 Risk adjustments The Basis for Conclusions should explain more fully how the proposed measurement requirement derives from the existing one. (December 2007) The Basis for Conclusions should also explain more fully why the Board thinks the requirement provides relevant and reliable information. (September 2006, December 2007) The revised standard should give more guidance on applying the proposed requirements (ie expected present value techniques). This should be based on existing well-established guidance in other standards, such as IAS 36 Impairment. This guidance and other application guidance in the exposure draft should be moved to an appendix, not included in the body of the standard. (Sept 2006) The standard should not give more guidance about the risks that entities should take into account when applying a risk adjustment to the expected cash flows. (February 2008) However, it should be clear that a risk adjustment would be required only if, and to the extent that, uncertainty about the expected outflows affects the amount that an entity would rationally pay to be relieved of an obligation. (April 2009) No change to requirements. Basis for Conclusions will contain more detail. Additional guidance, to reassure constituents that calculations will not necessarily be as complex as they fear. No new concepts introduced. Although this point was not explicit in the exposure draft guidance, it was implicit in the wording. Page 11 of 18

12 5 Reimbursement rights Topic Tentative decision Comparison with exposure draft proposals 5.1 Measurement objective 5.2 Measurement guidance 5.3 Asset cap The revised standard should not prescribe a measurement objective for reimbursement rights. (June 2009) The revised standard should state explicitly that the assumptions used to measure a reimbursement right should be consistent with those used to measure the related liability. (June 2009) An asset cap in the existing IAS 37 limits the amount recognised for a reimbursement right to the amount to the amount recognised for the related liability. The revised standard should omit the asset cap. (June 2009) This was not explicit in exposure draft proposals, but is the logical way of applying them. New proposal. Not discussed in exposure draft. NB The change would affect only the measurement of reimbursement rights relating to recognised liabilities. It would not extend the range of reimbursement rights that entities can recognise. The change might have little or no effect in practice if reimbursements rarely exceed actual loses. Page 12 of 18

13 6 Disclosure Topic Tentative decision Comparison with exposure draft proposals 6.1 Possible obligations The revised standard should retain the existing IAS 37 requirement to disclose information about possible obligations, ie situations of uncertainty (typically arising from legal, arbitration or governmental proceedings in progress or pending against the entity) in which management has judged that the entity does not have a present obligation. (December 2008) An entity should disclose, unless the possibility of any outflow of economic benefits is remote: - a description of the circumstances; - an indication of the financial effects; - an indication of the uncertainties relating to the amounts or timing of any outflow of economic benefits; and - the possibility of reimbursement. (June 2009) The revised standard should help preparers identify when disclosure is required, by giving examples and cross-referring between the disclosure requirement and guidance on uncertainty about the existence of obligations. (June 2009) New proposal but consistent with other conclusions and existing requirements. The Board omitted this existing disclosure requirement from the exposure draft. It did so because, applying the exposure draft proposals, the requirement would become redundant in practice. It would be redundant because an entity involved in a legal dispute would always have to recognise a liability (ie to act as the court directs). Because the Board has reversed this conclusion (see Decision 2.8), it also needs to reinstate the disclosure requirement for possible obligations, to avoid loss of disclosure about legal disputes. The information that the Board proposes to require entities to disclose is essentially the same as the information they have to disclose for contingent liabilities at present. Page 13 of 18

14 Topic Tentative decision Comparison with exposure draft proposals 6.2 Restructuring activities The revised standard should require entities to disclose details of restructuring activities. (April 2008) Entities should disclose: - a description of the restructuring activity, including the facts and circumstances leading to the expected activity and the expected completion date; - for each reportable segment, the total amount of costs expected to be incurred in connection with the activity, the amount incurred in the period, and the cumulative amount incurred to date; and - the expected timing of any outflow of economic benefits. Entities should disclose this information in the period in which they first implement a restructuring plan or announce its main features to those affected. They should continue disclosing the information until the restructuring is completed. (April 2009) Not in exposure draft. However, the proposed disclosure requirement does no more than ensure that entities will continue to disclose the same information about restructuring activities as they disclose at present. The decision addresses commentator concerns that the proposed change in recognition requirements for restructuring costs (see Decision 7.1) will lead to loss of disclosure. Page 14 of 18

15 7 Application guidance Liabilities amendments to IAS 37 Topic Tentative decision Comparison with exposure draft proposals 7.1 Restructuring activities 7.2 Onerous contracts Having announced a restructuring plan, management of an entity might have little or no discretion, from a commercial viewpoint, to avoid completing the plan. However, this commercial pressure does not amount to an obligation-- ie a duty or responsibility to another party to complete the plan. (April 2008) Entities should measure liabilities for onerous leases net of sublease rentals that the entity could reasonably obtain, irrespective of the entity s intentions. Minor drafting changes are needed: - to avoid implying that a decline in the market price of products or services necessarily makes a contract for their purchase onerous; and - to clarify what the Board means by actions in the requirements for contracts that become onerous because of the entity s own actions. (The decision to describe an obligation as a duty or responsibility to another party see Decision 2.3 will better explain the proposal.) Minor wording improvements will make application easier. Page 15 of 18

16 8 Consequential amendments to IFRS 3 Business Combinations Topic Tentative decision Reason for amendment 8.1 General 8.2 Recognition of contingent liabilities Requirements for contingent liabilities in IFRS 3 need to be replaced with requirements that refer to items within the scope of the revised IAS 37. This is because: - the term contingent liability will be deleted from the revised IAS 37. So any references will have to be to another population of items within the scope of that standard. - when the probability recognition criterion is deleted from IAS 37, there will no longer be different recognition criteria in the two standards. Some exceptions in IAS 37 will no longer be necessary. Replace the existing requirement (to recognise contingent liabilities if they are present obligations that can be measured reliably) in paragraphs 22 and 23 of IFRS 3 with a requirement to recognise liabilities within the scope of the revised IAS 37 if their fair values can be measured reliably. Explained below for each separate decision. Amendment preserves existing IFRS 3 requirement while making IFRS 3 terminology consistent with revised IAS 37 terminology. State that, except in extremely rare cases, an entity will be able to determine a reliable measure of the fair value of such liabilities. Reference reminds readers of relevant guidance already in IAS 37. Page 16 of 18

17 Topic Tentative decision Reason for amendment 8.3 Subsequent measurement 8.4 Disclosures about acquisitions in period. 8.5 Disclosures of adjustments from previous acquisitions The special requirements for subsequent measurement of contingent liabilities should be deleted. Without these special requirements, entities will subsequently measure all liabilities within the scope of IAS 37 and assumed in a business combination in accordance with the measurement requirements of the revised IAS 37. IFRS 3 should retain its requirement to disclose details of the nature of and uncertainties surrounding contingent liabilities assumed as part of business combinations in the period. (IFRS 3, paragraph B64(j)) The requirement should apply to all assumed liabilities and possible obligations within the scope of IAS 37. It should continue to cross-refer to the disclosure requirements in the revised IAS 37. Delete paragraph B67(c) of IFRS 3, which requires entities to disclose additional information about adjustments to contingent liabilities that have been recognised applying IFRS 3 but would not have been recognised applying IAS 37. The special requirements will no longer have a significant practical impact when the recognition requirements of the two standards are aligned. Contingent liability is no longer a defined term. The amendment will expand the population of items for which disclosure is required. But the information required is the same as that required at the end of the reporting period for all liabilities and possible obligations within the scope of IAS 37. So entities will not have to disclose additional information they will just have to give the information separately for liabilities assumed in business combinations in the period. The disclosure requirement will not be required when the recognition requirements of the two standards are aligned. Page 17 of 18

18 9 Consequential amendments to IFRIC 5 Rights to Interests arising from Decommissioning, Restoration and Environmental Funds Topic Tentative decision Reason for amendment 9.1 Rights to reimbursement from funds 9.2 Obligations to make additional contributions IFRIC 5 at present requires a contributor 1 to measure rights to reimbursement at the lower of: - the amount of the decommissioning obligation recognised; and - the contributor s share of the fair value of the net assets of the fund attributable to contributors. This requirement should be deleted and replaced with a requirement for contributors to recognised and measure rights to reimbursement for recognised liabilities in accordance with the revised IAS 37. The requirements in IFRIC 5 should be amended to: - allow for the possibility that some obligations are financial liabilities within the scope of IAS 32 and IAS 39 rather than IAS 37; and - delete the probability recognition criterion. The existing requirement aims to interpret the existing requirements for reimbursement rights in IAS 37. It needs to change if the asset cap is deleted from IAS 37 (see Decision 5.3). The proposed new requirement is one of three options considered by the Board. Changes necessary to reflect in IFRIC 5 past revisions to the scope of IAS 39 and the proposed deletion of the probability recognition criterion from IAS 37 (see Decision 3.1). 1 Specifically a contributor that does not have control, joint control or significant influence over a fund to which it contributes. Page 18 of 18