Links to Pages for All Past Meetings
IASB Board Meeting 19-23 October 2009, London

IASB Board Meeting Agenda

Monday 19 October 2009 (starting at noon)

  • Meeting of Representatives of IASB and Representatives of EFRAG (noon to 13:45h)
  • Financial Instruments – Replacement of IAS 39 (starting at 15:00h)

Tuesday 20 October 2009

Wednesday 21 October 2009

Thursday 22 October 2009

Friday 23 October 2009

IASB-FASB Joint Board Meeting 26-28 October 2009, Norwalk, Connecticut USA

Monday 26 October 2009

Tuesday 27 October 2009

Wednesday 28 October 2009

Notes from the IASB Board Meeting
19-23 October 2009

Monday 19 October 2009

Meeting of Representatives of IASB and EFRAG

Representatives of the EFRAG and IASB met for their regular meeting to discuss convergence-related issues.

The EFRAG Chairman started the discussion by expressing the support of EFRAG for the aim of achieving high-quality converged accounting standards as outlined by the G20. Nonetheless, he stressed that while EFRAG supported convergence, the high quality of those accounting standards had to be a priority that was not to be compromised.

The EFRAG praised the response of the IASB to the financial crisis related issues, especially the mixed measurement model proposed in the Classification and Measurement ED. Nonetheless, EFRAG was concerned by the potential decisions being made in the name of convergence. The Board responded that many constituents had shown their preference for a converged solution to financial instruments. In response, EFRAG reiterated its position that convergence should not be an one-way move to US GAAP but an improvement to quality of existing financial standards.

One member of EFRAG suggested that some changes of fair value of financial instruments not organised through an exchange or clearinghouse should be presented in OCI instead of profit or loss because:

  • they represented 'soft earnings' in comparison to 'hard earnings' and thus have less predictive power, and
  • they should not be used for profit distribution.
The Board responded that OCI classification would raise more complex issues (for example, recycling, impairment) and that stipulating what was classified as capital and what was distributable profit was the role of a prudential regulator and not an international accounting standard setter.

The EFRAG has expressed agreement with the overall direction of the expected loss model and hedge accounting proposals. Nonetheless, it articulated its position that a forward looking model for impairment should be developed and all convergence-related and implementation issues should be addressed before it was finalised. EFRAG stressed the importance of hedge accounting on a portfolio level.

The IASB Chairman responded by alluding to the timeline imposed by the G20. He noted that even though the classification and measurement IFRS was to be finalised the following month, if convergence was achievable after the FASB finalised its model, further changes to the model were probable.

On consolidation project, the Board noted that following changes to US GAAP, it planned to assess any need to change and discuss it with FASB. That could have impact on timing of the project.

On derecognition, the Board alluded to two approaches possible, an alternative approach and a more limited amendment to IAS 39 model (based on risks and not rewards). The Board expressed its view that a new ED on derecognition might be necessary.

On other proposals, the EFRAG commented that the amount of changes to IFRSs already issued and proposed is very large. It suggested that some projects could be deferred following unfavourable reaction from the constituents (for instance, income taxes) and some should be finalised in full and not split into phases (for instance, the employee benefits project). The IASB noted the the staff has recommended that the proposed amendment on IAS 19 on discount rates might not be finalised as constituents were polarised how to proceed. The EFRAG members showed their surprise on such a recommendation.

The EFRAG also showed its support to the full re-exposure the new liabilities standard in light of the significant time the IASB has taken to redeliberate the proposals in the ED. It noted that during period, opinions of constituents might have changed.

Finally, the EFRAG updated the Board on status of the pan-European projects.

Financial Instruments: Classification and Measurement

Gains and losses related to fair value measurements in level 3 of the hierarchy

The Board considered the requirement for separate presentation on the face of the statement of comprehensive income of the total gains and losses for the period related to fair value measurement in Level 3 of the hierarchy.

In the outreach related to the Classification and Measurement ED, the Board was told by some constituents (mainly regulators) that separate presentation of gains and losses related to unreliable fair value measurement was superior to a mere disclosure in the notes, as data presented on the face of the statement of comprehensive income were seen to carry more weight.

Most of the Board members disagreed, as they felt that such information was already available under the requirements of IFRS 7, and regulators had enough powers to require any disclosures desired in prudential reporting. Moreover, some Board members were concerned that such separate presentation would not address the true issues as valuation uncertainly as well as earnings volatility had less predictive power for future financial performance for users.

The Board finally decided not to require such separate presentation as part of Financial Instruments project. Some Board members suggested that Financial Statement Presentation project was the right place to address such an issue. Moreover, the Board agreed to discuss this issue together with the FASB during the October joint meeting along with the proposal to disclose both fair value and amortised cost of financial instruments on the face of the statement of financial position.

The IASB's plan is to publish a final IFRS on classification and measurement of financial instruments in November 2009

Tuesday 20 October 2009

Fair Value Measurement

Comment letter analysis

The staff presented a summary analysis of comment letters received in response to the IASB's Invitation to Comment and Exposure Draft of a proposed IFRS Fair Value Measurement. To date, 157 comment letters had been received. The staff noted that as issues are redeliberated, more detailed analyses of the comments received would be presented.

The staff noted that nearly all respondents were in favour of the project and that constituents generally identified the following:

  • having a single source of guidance would reduce complexity and improve consistency in the application of fair value measurements
  • the IASB and FASB should work together to develop fully-converged guidance for fair value measurement under both IFRSs and US GAAP
  • an exit price notion is not relevant for assets when an entity does not intend to sell the asset (that is, when it is being used in the operations of the business or it is a financial asset not held for trading)
  • a liability measure should reflect a settlement notion, not a transfer notion, if the liability cannot legally be transferred or if the entity does not intend to transfer it
  • some of the guidance for measuring fair value in inactive markets in the Expert Advisory Panel's report should be added to the final IFRS on fair value measurement guidance.

Board members noted that some of these items reflected constituents' opposition to measuring an item at fair value (the 'when' question) rather than disagreement with the ED's proposals about 'how' to measure fair value when an IFRS required such a measure.

In addition, some Board members noted that the use of 'fair' in 'fair value' was an emotive issue for many constituents. Some constituents seemed to think that the Board had only two buckets, cost and fair value, and that there was no place in IFRSs for current measures other than fair value. It might be better that the IFRS be neutral and refer to 'exit price', 'entry price', etc. The confusion also extended to whether approximations/ estimations of fair value determined using present value techniques could be described as 'fair value'.

Another Board member was concerned about the application of the IFRS in less developed economies and economies in transition. In many such jurisdictions, hypothetical markets were 'beyond their experience and imagination'. As part of the Board's outreach activities during redeliberations, specific consideration should be given to engaging with these jurisdictions – either through activities in Africa, South America, and South-east Asia, or through meetings to be held as part of, or as an adjunct to, meetings of the SAC; or through remote meetings, utilising technology. There was support for such activities.

Preliminary project plan

The staff presented a preliminary project plan outlining their proposed approach to redeliberating issues in the exposure draft (ED) and for addressing developments in US GAAP (including Accounting Standards Updates 2009-5 and 2009-12) subsequent to the publication of the ED in May 2009.

While approving the project plan, Board members expressed concern that the plan gave the impression that the staff was concentrating on 'playing catch-up' with US GAAP and would not address IASB constituents' concerns and suggestions for joint improvement in the standards. The staff noted this concern and stated that such issues would be discussed at the forthcoming joint IASB-FASB meeting later in October 2009.

Consolidation - Definition of Control of an Entity

The activities of the entity

The staff reminded the Board that ED10 proposed the following definition of control:

A reporting entity controls another entity when the reporting entity has the power to direct the activities of that other entity to generate returns for the reporting entity.

The Board discussed a staff recommendation that the IFRS should clarify that 'the activities' in the control definition refers to those activities of an entity that significantly affect the returns.

Several Board members expressed concerns with this clarification: some thought it too narrow and some did not think it captured common securitisation structures. One Board member noted that the Board (and staff) was often schizophrenic when using the term 'power': at the entity level, the returns were for the entity; but when layering the 'so as to benefit' criterion when assessing whether the entity should be consolidated, the returns had to benefit the owner, not the entity.

That Board member agreed that if [a parent] had both power and benefits, consolidation of the entity would be required. In addition, other Board members noted that synergies were indicative of control – an entity could not take advantage of synergies without having control of another entity – but they came after control was obtained and need not be present.

Another Board member challenged the main definition, and urged that the well-established notion of power to direct the strategic financial and operating policies of another entity should not be lost.

The Board accepted the staff recommendation without a vote.

Returns for the reporting entity

The Board agreed the staff recommendation that the definition and description of 'returns' should be retained in a manner similar to that in ED10. However, the Board would clarify which returns are relevant when assessing control.

The staff recommend that the final standard should also clarify that:

  • (a) to control another entity, a reporting entity must be exposed to variability of returns from its involvement with that entity. Without exposure to variability, a reporting entity is unable to benefit from any powers that it might have.
  • (b) returns received in the past are not relevant when assessing control. If a reporting entity is not exposed to variability of returns in the future, it is unable to benefit from any power that it might have. In such situations, a reporting entity uses any powers that it might have solely for the benefit of others, and therefore, would be acting as an agent.
  • (c) returns have the potential to be wholly positive, wholly negative or either positive or negative. Therefore, a reporting entity controls another entity if it has the power to direct the activities of that entity, and any of the following three possibilities exist:
    • (i) the reporting entity's future returns from its involvement could only ever be positive (e.g. a beneficial interest holder in an entity that has bought insurance to cover all potential losses).
    • (ii) the reporting entity's future returns from its involvement could only ever be negative (e.g. a reporting entity that provides a guarantee of payments to beneficial interest holders when assets default).
    • (iii) the reporting entity's future returns from its involvement could be either positive or negative (e.g. an equity shareholder in an entity)

A Board member was concerned about the use of 'variability in returns' and the opportunities for defeasance trusts and similar structures to be used once again to achieve off-balance sheet treatment for items. The staff acknowledged the potential difficulty, but was trying to avoid too definitive guidance.

Power to direct: protective and participating rights

The Board discussed a staff recommendation that the IFRS characterise 'power' as follows:

  • Power refers to a reporting entity's current ability to enforce its will in directing the activities of an entity that significantly affect the returns. A reporting entity has that current ability if a mechanism is in place that ensures that the reporting entity has substantive decision-making rights that mean that it can enforce its will in directing the activities that matter as and when decisions are required to be taken or the reporting entity would like decisions to be taken.
  • Power need not be exercised.
  • Power need not be absolute.
  • Power is assessed on the basis of current facts and circumstances.

A Board member noted that 'current ability' would be the tension point and that the staff's proposed wording would not resolve the tension that exists. The staff responded that much of that tension concerns the effect of options, a topic that would be addressed later.

The Board did not object to this clarification, subject to its forthcoming discussion of options.

Rights of a reporting entity

The Board discussed whether to:

  • add guidance discussing participating rights as follows:
    • participating rights are rights that, if held by one party, are sufficient to give that party the ability to enforce its will in directing the activities of an entity that significantly affect the returns. If their exercise requires agreement by more than one party, participating rights prevent other parties from controlling the entity to which they relate.
    • participating rights must be substantive
    • rights that are exercisable only when specified circumstances arise or events happen are participating rights in some circumstances and protective rights in others
  • include the guidance on protective rights included in B1 and B2 of ED10

A Board member thought that the discussion focussed too much on rights and omitted any discussion of obligations – if an entity has rights it must have obligations to another entity.

In addition, Board members were concerned that some of the discussion of operational barriers to exercising an entity's rights to exercise control over another might have significant unintended consequences for entities in administration/ bankruptcy protection and urged the staff to investigate this further.

Subject to other minor clarifications, the staff recommendations were agreed.

Sharing power

The staff prefaced this discussion by noting that they did not want to change the definition of 'joint control'. Rather, this discussion was about situations in which multiple parties had decision-making authority over the activities of an entity. In particular, the discussion focussed on situations in which entities have discrete and unilateral power over bundles of activities (sometimes called 'silos').

The Board agreed the staff recommendation that when two or more parties have discrete decision-making authority over the activities of an entity, the party that has the ability to direct the activities that most significantly affect the returns meets the power element of the control definition.

In doing so, several Board members expressed grave concern about how the discussion of shared power (the Consolidation IFRS) and joint control (the Joint Activities IFRS) were explained and distinguished, given that the expected release date of the two IFRSs were different and that the forerunner could not refer to conclusions in an IFRS that was not yet balloted: it could only refer to existing IFRS. The staff acknowledged that the two standards were not scheduled to be released at the same time and noted the concern raised.

Involvement in the design of a structured entity

The Board discussed a staff recommendation that the IFRS clarify that understanding the purpose and design of an entity was an important factor to consider when assessing control of that entity, and that involvement in the design of an entity is not, in isolation, sufficient to conclude that the reporting entity controlled that entity. The staff's intention was that involvement in the design of a structured entity was indicative but not determinative of control.

Board members were uncomfortable with the recommendation as drafted. Control of the risks and benefits was often the more crucial assessment to be made. It was necessary to understand the entity's purpose and who controls those policies.

The Board agreed that, in assessing control of any entity, including a structured entity, a full understanding of all relevant facts and circumstances was necessary. This could include who designed the structure and why, the source of assets and financing, as well as who controls the operating policies and which entity has the risks and benefits.

The staff agreed to rework its proposals and return at a subsequent Board meeting.

Continuous assessment of control

With little discussion, the Board affirmed that a reporting entity should assess control continuously and that the IFRS should clarify the application of that requirement.

Financial Statement Presentation

The statement of comprehensive income

The Board briefly considered the proposal to present a single statement of comprehensive income. The Board concluded that this topic would be addressed later this week as part of another project (proposed amendments to IAS 1) in response to a similar expected FASB proposal (as part of its financial instruments project).

The Board agreed to retain the requirement to identify and indicate on the statement of comprehensive income the category or section to which each item of other comprehensive income (OCI) (apart from a foreign currency translation adjustment on a consolidated subsidiary and proportionately consolidated joint ventures) related. The Board also discussed implications of this decision on some items in OCI (for example, cash flow hedge reserves) as it could mean that they might be split between the respective sections.

Income tax allocation and presentation

The Board agreed to propose in the forthcoming ED to retain the existing requirements on intraperiod tax allocation in the statement of comprehensive income. This may result in an entity presenting income tax expense or benefit in the discontinued operations and OCI sections in addition to determining the income tax effect for continuing operations (the income tax section).

The Board also tentatively agreed that existing requirement to disclose the amount allocated to each component of OCI should be retained. Nonetheless, the staff noted that this issue might be reconsidered following the decision on a single statement of comprehensive income later in the week.

Finally, the Board agreed that an entity should present current and deferred income tax assets and liabilities recognised and related cash flows in an income tax section on the statement of financial position and statement of cash flows.

Disaggregation by Function and Nature

The Board continued its discussions on the level of disaggregation in the financial statements. This was an educational session, and no formal decisions were taken.

The Board discussed a disaggregation principle that would require an entity to consider disaggregation by function, nature, and measurement basis in financial statements as a whole in a manner that provided transparency to that entity's business model and best representation how the entity used its resources to generate income and cash flows. This disaggregation principle would then apply not only to the statement of comprehensive income but also to the statement of financial position and the statement of cash flows.

Whilst the majority of the Board was contended with the overall direction of embodied in that principle, they expressed their concerns on how the principle was articulated. Some Board members were particularly concerned that the wording was too vague and a more rigorous wording would be required to ensure discipline to provide a proper level of consistency and comparability. Otherwise, they feared, it would give the preparers a carte blanche in determining the level of disaggregation. Especially, the representatives of analysts among the Board members were concerned that applying the proposed principle could lead to essential information not being disclosed. On the other hand, some other Board members felt that some level of flexibility was necessary and it reflected different characteristics of different industries (for example, financial institutions).

On balance, the Board saw merit in the proposed principle but asked the staff to reformulate it, articulate more clearly the objectives and accompany the principle with additional application guidance and examples how that principle might impact the presentation of primary financial statements. The Board will reconsider this principle on the joint meeting with the FASB next week.

The Board considered where in the financial statements the disaggregated information should be presented. Most of the Board members were concerned that the level of disaggregation would lead to the primary financial statement being too cluttered with data leading to reduction in relevance and understandability.

Whilst most of the Board members concurred with the proposal to present disaggregated information on the face of the financial statements for entities with one reportable segment and to present that information in its segment note for an entity with more than one reportable segment, they were concerned that segment note was based on a different measurement basis (non GAAP numbers). The presentation of disaggregated information would be reconsidered at the October joint meeting with the FASB. Nonetheless, the Board thought that the forthcoming ED might ask the question whether segment reporting note should be amended to reflect the GAAP measures.

Insurance Contracts

Unbundling

The Board considered when an insurance contract that contains insurance, deposit (financial) and service components should be accounted for as if they were separate contracts (unbundling). The Board considered the requirement to unbundle when the components were not interdependent.

After a long debate, during which the Board discussed consistency of this requirement with the proposed guidance for multiple segment contracts in the revenue recognition project, the Board asked the staff to redefine the conditions and guidance when the contract was interdependent and could not be unbundled (that is, valued separately).

Presentation of the performance statement

The Board continued with an educational session on presentation of insurance contracts in the performance statement.

The Board was presented with five presentation options:

  • (a) Treat all premiums (including the portion that pays for the deposit component) for all insurance contracts as revenue.
  • (b) Unbundle all (or specified) insurance contracts into an insurance component, as in (a) and a deposit component – a fee approach.
  • (c) Treat all premiums for all insurance contracts as deposits, and all claims and expenses as repayments of deposits. Use the margin model for the margin.
  • (d) For insurance contracts that meet specified criteria (for instance, life insurance contracts, or long duration contracts), treat all premiums for all contracts as deposits, as in (c). For all other insurance contracts, treat all premiums as revenue, as in (a).
  • (e) Permit insurers to choose for each class of insurance contracts between a revenue presentation, as in (a), and a deposit presentation, as in (c).

After a thorough discussion, during which the Board considered the level of granularity required, the Board seemed to revert to unearned premium model for short term policies and (c) or (d) for other insurance contracts. The Board will reconsider these models at its November meeting, after received feedback from insurance working group.

Deposit floor for Insurance contracts

The Board rediscussed the issue of deposit floor for insurance contracts. The implication of usage of measurement model based on expected cash flows resulting from insurance contracts was that no deposit floor applied for measuring insurance contracts.

In the debate on this implication of the measurement model, the Board discussed the scope of an insurance contract as well as consistency of the deposit floor in banks and insurance.

The Board tentatively confirmed that no deposit floor applied in measuring insurance contracts. Nonetheless, the Board asked the staff to further analyse the implications of that decisions on more complex insurance products. Moreover, the Board directed the staff to analyse possible arbitrage opportunities arising from this decision in groups consisting of both a bank and an insurance company.

Timetable

Given the decisions taken on the previous sessions (including lack of final decisions on several subjects), the Board decided to reconsider the timetable for the project at its November meeting.

Wednesday 21 October 2009

Credit Risk in Liability Measurement

The Board continued its discussion of the comments received on its Discussion Paper Credit Risk in Liability Measurement and deliberated the next steps for this work stream.

There was broad consensus that on initial measurement credit risk should be included in the measurement of at least some liabilities.

Some of the respondents thought that credit risk should always be included, although those respondents would limit this answer to financial liabilities. A few respondents thought that credit risk should always be included in initial measurement of all liabilities. Very few respondents would never include credit risk in initial measurement.

On subsequent measurement, views were more divided. Many agreed that credit risk should be included sometimes, although a significant number thought that it should not be included. Only a few would include credit risk at all times – again, this was in the context of financial liabilities.

The Chairman sought to clarify the preference among respondents for the 'frozen credit spread' approach and whether this was consistent with fair value. Staff acknowledged that using a frozen spread approach could lead to a measurement that diverged from fair value. (If the risk-free rate declined and the margin on AA-rated debt increased, an entity would mark away from market/fair value.) The staff noted that the DP had attempted to observe that there were two bits to the frozen spread approach, but only a few respondents had commented on it (see, for example, HSBC's comments).

Many Board members were frustrated by the lack of response from constituents about how to measure the frozen credit spread – often spending more time commenting on what should or should not be measured at an amount reflecting credit risk.

Staff noted also that constituents' apparent support for a frozen credit spread approach was probably a product of profound dislike for the other possible approaches discussed in the DP. However, the approach needed to be put in the context of a particular standard to obtain better and harder data.

The Board moved to discuss staff recommendations for this work stream and the information gained from the DP and made the following decisions:

  • The Board agreed that no further work on credit risk in liability measurement as a separate work-stream should be undertaken.

  • The Board would be required to make decisions about liability measurement in individual standards-level projects.

  • The Board agreed that the definition of 'fair value' should not be modified as a result of the DP. Decisions about how 'fair value' is applied belong properly in the Fair Value Measurement project and individual standards-level projects.

It was possible that, in any particular project, the Board might agree a measurement attribute as fair value 'as modified' (for example, fair value 'less costs of disposal'). Board members noted that this decision might be troublesome to constituents.

Should the notion that credit risk is inherent in the measurement of fair value be included in the IASB's Framework? The staff noted that most applications of fair value to liabilities occur in the context of financial instruments. Several other IFRSs require current information to be incorporated in liability measurement (but not fair value as defined), including IAS 19 and IAS 37. Board members seemed to think the idea of embedding the notion credit risk being included in liability measurement in the Framework as a general concept was the right approach. How the concept was applied would be left to the Fair Value Measurement standard and other IFRSs.

The Board discussed non-performance risk, and its interaction with credit risk. Non-performance risk was a notion introduced by the FASB in Statement of Financial Reporting Concepts No. 7 (CON 7) and was an attempt by the FASB to address the physical as well as the financial incapacity to discharge an obligation. The Board discussed this issue for some time, essentially coming to a common understanding of what CON 7 was saying and how its concepts might be applied in an IASB context.

The Board agreed with the staff's assessment that the interaction of non-performance risk and credit risk could not be addressed satisfactorily at a concepts level, but needs to be addressed explicitly in each project when a liability measure is at issue. (This approach would be applied to all future projects, not existing IFRSs or projects in an advanced state of deliberations.)

Liabilities – Amendments to IAS 37

Decision about re-exposure

The staff presented one issue to the Board: whether re-exposure of the IAS 37 amendments package was necessary or whether the Board could proceed directly to issue an IFRS. In doing so, they reviewed with the Board the criteria for re-exposure in the IASB's Due Process Handbook, paragraphs 46-48, and the decision summary of redeliberations.

Three options were proposed:

  1. Issue an IFRS without re-exposure;
  2. Undertake a limited-scope re-exposure of selected changes to the propels; or
  3. Re-expose the entire standard.

After an extended debate, the Board agreed that it would:

  • Ballot the IFRS and prepare the Basis for Conclusions for the IFRS other than the measurement guidance and release this as a Near-final Draft on the IASB's Website; and
  • Expose for public comment its proposed clarification of the measurement requirements. Those requirements, in the Board's view, are a re-articulation of the current measurement requirements in IAS 37, not a new measurement basis. Based on decisions reached in July and September 2009, the revised standard would state that:
    • the requirement is to measure the amount that the entity would rationally pay on the reporting date to be relieved of the present obligation.
    • 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.
    • 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.
    • 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.
    • 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.

    Board members stressed that the ED of the proposed clarification of the measurement approach and the near-final draft of the IFRS should be available at the same time.

The Board gave notice that it intended to incorporate the guidance in IFRICs 1, 5, and 6 in the IFRS in accordance with its existing practice of incorporating IFRIC guidance in revised IFRSs wherever possible. The cap on the reimbursement right in IFRIC 5 would be abolished.

At least five Board members indicated that they would dissent to the ED on the basis of the measurement approach being adopted.

Financial Instruments – Classification and Measurement

Scope

The Board revisited its earlier tentative decision on the scope of the forthcoming IFRS. Many Board members had become increasingly concerned that introduction of the frozen credit spread for financial liabilities would create severe unintended consequences (for instance, measurement of derivatives embedded in financial hosts and implications for fair value option). Moreover, this particular decision would make convergence with FASB increasingly difficult.

The Board expressed its desire to rediscuss this issue and consider additional outreach activities. Therefore, the Board unanimously decided to exclude financial liabilities from the scope of the forthcoming IFRS. The Board would rediscuss this issue immediately after the IFRS is issued and try to come with a common solution with the FASB on treatment of financial liabilities.

Effective Date

The Board discussed the proposed mandatory effective date for the IFRS. Some Board members thought that the IFRS should be mandatorily adopted only as a whole package at the same time (with all the other parts of the IAS 39 replacement) and preferably at the same time as the second phase of the insurance contracts project. On the other hand, some Board members felt that in this way comparability would be impeded for a relatively long period of time. Finally, the Board agreed that a mandatory effective date of the finalised guidance on classification and measurement of financial instruments would be for annual periods beginning on 1 January 2013 or later. The Board noted that until then, constituents should have sufficient time to prepare for all the phases of the IAS 39 replacement project. Nonetheless, the Board noted that if there was a need to delay further the mandatory effective date, for example due to the Impairment phase adoption, that would be possible.

The Board agreed without much discussion to permit early application of the final IFRS and to require the transition disclosures for all entities adopting the new IFRS (not just for entities adopting them early as proposed in the ED).

Nevertheless, some Board members expressed their concerns that permitting early adoption might lead to lack of comparability and consistency in financial reporting.

Transition

The Board discussed transition requirements. As the discussion progressed, some of the Board members become increasingly concerned that proposed transition could lead to a complete free choice and would lead to window-dressing of financial statements.

After a substantial discussion the Board agreed to permit determining the date of initial application of this IFRS at any date between issue of the IFRS and 31 December 2010. Thereafter, an entity could determine the date of initial application at the beginning of the reporting period only.

The Board agreed not to require restatement of comparative periods in 2009-2011 period. However, for all the periods after 1 January 2012 comparative information would have to be provided. The Board also agreed with the principle (consequential amendment to IFRS 1) that first-time adopters should not be in a more onerous position in restating comparative periods that entities already applying current IAS 39. The Board also decided not to require early adoption of subsequent guidance (other phases of IAS 39 replacement project) if any previous guidance was adopted. Nonetheless, the Board agreed to limit the number of choices by requiring early adoption of any preceding final guidance if subsequent guidance was early adopted.

Some Board members were concerned that requiring restating of comparative periods would lead to lower quality of the data as well as practical problems (for example, with financial instruments already derecognised). Nonetheless, the majority of the Board were of the opinion that such a requirement is necessary to ensure a basic level of comparability and consistency.

On the other issues the Board decided to finalise the guidance as proposed in the ED on impracticability of retrospective application and disclosure requirements.

The Board decided not to permit 'grandfathering' of the accounting for hybrid contracts with financial hosts given its decision on scoping liabilities out of the IFRS.

The Board also agreed to remove the provision for discontinuance of hedge accounting relationships that did not qualify under the new classification model as they would be effectively a null set.

Finally, the Board decided not to provide any guidance on potential transition relief for future phases of IAS 39 replacement project.

Transitional insurance issues

The Board considered the interaction between classification and measurement phase of the IAS 39 replacement project and Phase II of the project on insurance contracts. The Board agreed that if the effective dates of these projects are different, additional accounting mismatches might occur. Nonetheless, as the Board believed that mandatory adoption in 2013 might be achievable for both of these projects, it did not provide any additional relief for insurance companies (such as temporary exemption to maintain an AFS portfolio). The Board agreed that as part of the transitional requirements of the insurance contracts IFRS, a transitional option to reclassify financial assets on adoption of Phase II of insurance contracts should be considered. The Board also agreed to include such discussion in the Basis for Conclusions of the Classification and Measurement IFRS.

The Board also considered consequential amendment of IFRS 4 to modify shadow accounting for insurance contracts or financial instruments containing a discretionary participation feature (allow adjustment to the insurance liability to be recognised in other comprehensive income (OCI) if a realised gain or loss on an asset is recognised in OCI). The Board decided against such a change as it believed that OCI presentation for equity instruments was a choice, and thus an accounting mismatch might be avoided by not using the option.

Thursday 22 October 2009

Post-employment Benefits

Post-employment Benefits: IFRIC 14 – The Limit on a Defined Benefit Asset, Minimum Funding Requirements and their Interaction

The Board received a staff analysis of comments received as a result of its proposed amendment of IFRIC 14 Prepayment of a Minimum Funding Requirement (ED/2009/4). It also redeliberated its conclusions in that exposure draft (ED).

The staff briefly introduced its comment letter analysis. The staff noted that some respondents wished the IASB to extend its amendments to the measurement of surpluses, not only repayments, but the Board agreed with the staff that such an extension was beyond the scope of the project.

The Board agreed to proceed with the amendment to IFRIC 14 such that it address only the treatment of a prepayment of a minimum funding requirement.

The Board considered whether to provide additional guidance on the definition of 'unconditional right to a refund' in IFRIC 14. The Board agreed that no elaboration was necessary.

The ED proposed to delete IFRIC 14 paragraph 22. In response to concerns raised by respondents about whether the other amendments proposed replaced all the requirements of paragraph 22, the Board decided to retain the paragraph.

The Board agreed that the amendments should be applied from the beginning of the earliest comparative period presented in the first financial statements in which the entity applies IFRIC 14.

Post-employment Benefits – IAS 19 Discount Rate

The Board received a staff analysis of comments received on its proposed amendment of IAS 19 Discount Rate for Employee Benefits (ED/2009/10). It also redeliberated its conclusions in that exposure draft (ED).

The staff noted that 100 comment letters were received; in addition, there had been correspondence with constituents since the staff papers for this meeting had been released.

The staff said that the comments were polarised: those who were in favour of the change were strongly so; those against were equally strong in their opposition. In addition, it was apparent that the exposure process had highlighted a number of areas in which the proposal would create problems of which the staff were previously unaware. The Board's proposals could lead to greater diversity in practice rather than less. As a result, the staff presented three alternatives:

  • Require government bond rates to be used when it is difficult to estimate a high quality corporate bond rate, rather than when there is no deep market in high quality corporate bonds. The staff would consider further what is meant by 'difficult' if the Board decides to proceed on this option;
  • Continue with the ED proposal to eliminate the requirement to use a government bond rate; or
  • Keep the existing requirement to refer to a government bond rate when there is no deep market in high quality corporate bonds – in other words, stop the project.

Board members engaged in a vigorous debate. Some challenged that staff analysis as simplistic and disingenuous. Others noted that the proposed amendment illustrated the danger of forcing an entity to use a measurement input that matched neither the currency nor duration of its defined benefit obligation.

Board members expressed dissatisfaction with all three alternatives. However, ultimately there was not sufficient support among Board members to ratify the amendments. Consequently, the requirement in IAS 19 paragraph 78 to use the government bond rate in the absence of a high-quality corporate bond rate would remain in force.

Next steps for proposed amendments to IAS 19 relating to termination benefits

The staff reminded the Board that it had published an Exposure Draft of proposed amendments to IAS 19 addressing termination benefits in June 2005 (this was issued in conjunction with the proposed amendments to IAS 37).

The Board had considered comments received and had concluded its redeliberations in May 2008. However, the amendments had not been balloted or published pending further deliberations on IAS 37. With the conclusion of redeliberations on IAS 37, the staff asked for the Board's intentions for the IAS 19 issues.

The Board directed the staff to prepare a ballot draft of the amendments and that the amendments should be issued as soon as they are ready. No Board members indicated their intention to dissent. Ms McConnell indicated that she would likely abstain, since all redeliberations occurred prior to her appointment as an IASB member.

Timing of effective date and transition

The staff proposed that the amendments to IFRIC 14 and IAS 19 for termination benefits should be effective for annual periods beginning on or after 1 January 2013, with early application permitted.

Board members reacted angrily to this suggestion, noting that the Board had been told that constituents wanted these amendments quickly and yet the staff was proposing an effective date several years in the future, while permitting early adoption. As such, the staff were suggesting that the Board promote non-comparability. IFRIC 14 was admittedly flawed, yet the staff were reluctant to require the improved version to be implemented.

In their defence, the staff suggested that they were trying to avoid multiple changes being inflicted on constituents. However, Board members noted that this defence was predicated on the Board completing its work on post-employment benefits accounting by 2013, something that the Board might not be able to achieve.

The Board directed that the amendments be effective for annual financial reporting periods beginning on or after 1 January 2011, with early adoption permitted.

Financial Statement Presentation – Other Comprehensive Income

The Board discussed a proposal for a possible limited scope amendment to IAS 1 Financial Statement Presentation. This amendment might be necessary to preserve a degree of comparability between the presentation of the statement of comprehensive income between IFRS and US GAAP, depending on the actions that the FASB might take in its Financial Instruments: Recognition and Measurement project.

Specifically, the staff presented a proposal to remove the option in IAS 1 paragraph 81 to present a statement displaying the components of profit or loss and a second statement beginning with profit or loss and displaying components of other comprehensive income (the 'two statement' option). The staff stressed that nothing in their proposal would change the items that could or should be presented in OCI, or whether an item should be reclassified upon derecognition.

Board members expressed surprise that the staff was bringing this proposal forward at this time. The latest version of IAS 1 had been in effect for less than ten months, and the last time the Board had suggested a single statement of comprehensive income it had faced near universal opposition. Now was not the time to reignite the embers of opposition and provide additional ammunition to those ill-disposed towards the IASB.

Noting the foregoing arguments, a Board member warned that, should they proceed with this proposal, all Board members voting in favour of the proposal before exposure must have the backbone to maintain their position afterwards: it was unlikely that the exposure process would raise any information or insight of which it was unaware already.

The Chairman noted that the proposal would need to be addressed carefully and as a true US GAAP convergence item. He noted also that the topic would be discussed with the FASB at its joint public meeting on 26-28 October, after which the IASB would be in a better position to judge whether the amendment would be needed.

The Board tentatively agreed to eliminate the alternative in IAS 1 paragraph 81 that permits the 'two statement approach' to presenting the statement of comprehensive income.

The Board also tentatively agreed to require that the single statement of comprehensive income be displayed with two sections: profit or loss and other comprehensive income.

By a majority (at least two opposed), the Board tentatively agreed that

  • components of OCI that would not be reclassified into profit or loss in future periods should be displayed together, and
  • components of OCI that would be reclassified into profit or loss in future periods should be displayed together.

The Board tentatively agreed to remove the option to permit an entity to display components of OCI net of tax. In addition, the Board agreed that income taxes related to items reported in OCI should be allocated between the two sub-classifications.

The Board will make a further determination about this possible project after the joint meeting with the FASB on 26-28 October 2009.

Financial Instruments – Classification and Measurement

Interaction between decisions on concentration of credit risk and other non-recourse instruments

The Board discussed the accounting for proportionate non-recourse instruments from the perspective of the holder. The majority of the Board agreed that the IFRS should include additional guidance that an entity had to ensure that any payments arising under the contract were consistent with the principle of all payments being payments of principal and interest (representing time value of money and credit risk). This required 'looking through' the non-recourse instruments to the underlying ring-fenced assets.

The Board discussed this principle in detail. Some Board members were concerned that the words did not reflect the principle that should have been articulated (in effect the difference between the credit risk and owner risk). The Board asked the staff to draft the principle to reflect that the holder always had to assess the repayment and its source. In case of non-recourse loans that meant that the promised return was evaluated for whether it represented compensation for credit risk or another economic substance.

One Board member in particular was concerned about this principle as he considered a non-recourse loan to be a loan with an embedded option. Consequently he would deny amortised cost accounting for all non-recourse loans as they did not exhibit basic loan features.

Summary of decisions

The Board considered the decisions taken during the process of redeliberation of the classification and measurement phase of the Financial Instruments project.

The Board clarified that with respect to underlying portfolio of investments in contractually linked instruments, additional credit protection (such as guarantees) for the underlying instruments would not prohibit amortised cost accounting.

With regards to reclassifications, the Board specified that following the identification of a change in the business model, an entity should reclassify the financial instruments in question from the start of the following period (including interim periods).

At least three Board members (and an additional Board member tentatively) indicated that they would dissent to the ED on the basis of the approach being adopted.

Friday 23 October 2009

Consolidation

Agency Relationships

The Board held a preliminary discussion of the effects of an agency relationship in consolidation. The topic will be discussed at next week's joint meeting between the IASB and FASB on 26-28 October 2009.

The staff noted that the FASB had recently amended its consolidation standards with respect to variable interest entities in which it addressed the effects on consolidation of the power to remove an agent ('kick-out' rights) and the remuneration of the agent. The IASB project seeks to address the same issues, but in a wider context, since the forthcoming IFRS would apply to all entities. Crucially, the IASB staff and the FASB are in slightly different positions at the moment. This discussion was intended to gain a preliminary understanding of why the two sides were where they were and what the key differences were.

No decisions were made at this session.

Removal rights

In SFAS 167, the FASB concluded that, in the context of variable interest entities, kick-out rights should be excluded from the determination of the primary beneficiary [that is, the accounting 'parent'] unless those rights are held by a single party. A Board member noted that it was highly unlikely that the FASB would revisit this conclusion, as the FASB was very concerned that to conclude otherwise would open the standard to structuring opportunities. However, the decision had been contentious and one not taken lightly.

IASB members were troubled by the absolute nature of this conclusion but acknowledged the difficulty in some circumstances of determining whether an entity acting in an agency capacity was in control of the entity it was managing. The Board seemed sympathetic with the staff view that kick-out rights could be held by more than one party; however, the greater the number of parties that held kick-out rights, the less likely it would be that those rights were substantive. At the same time, they wanted to hear from the FASB directly their thinking on removal rights, especially to understand their concerns about structuring opportunities and other possible abuses.

Remuneration

The staff presented three potential views of how remuneration of the agent might affect the determination of control. One view put forward by some respondents to ED10, that when (for example) a fund manager held anything less than 100% of the units if a fund should not be deemed to control the fund, was rejected by all Board members and was not discussed.

View 1 would apply the definition of control to conclude that a reporting entity controls another entity when it has decision-making authority to direct the activities, and receives a variable return from its involvement with the entity. This is the FASB's view, except that in issuing SFAS 167, the FASB viewed the issue from the agent's point of view.

View 3 would acknowledge that there are situations in which a reporting entity's returns might be more than insignificant and yet that reporting entity would still use the decision-making authority delegated to it to generate returns for other parties. When there is evidence that the reporting entity uses the delegated authority for its own benefit rather than for the benefit of other parties, it would be presumed to control the managed entity.

During the discussion, it was noted that the FASB would agree that a substantive kick-out right should be included in the determination of control; and that a substantial variable interest in the returns of an entity would be indicative of control.

The Board discussed examples distinguishing Views 1 and 3 and noted that in the IASB's analysis (that is, not considering SFAS 167) the control/consolidation decision would be different only when the manager acted in a dual capacity: as a manager and as an owner. The sense of the meeting (in the absence of any votes) was that a majority of the IASB favoured the approach in View 3. One Board member noted that he favoured View 3, but was also a 'single kick-out right' person because he did not think anything else would be operational.

Another Board member noted that he was becoming uncomfortable with using kick-out rights as an indicator of control in voting interest entities (that is, not structured entities, but operating entities). He was thinking in terms of joint ownership entities in which the owners appoint one of the owners to act as operator/manager under contract. He was still thinking about how such an arrangement might be analysed using the IASB's approach.

The IASB staff noted that they continued to work with the FASB to understand issues around the tension points that cause a different conclusion in the assessment of control.

Non-contractual agency relationships

The Board held a brief discussion of whether the forthcoming IFRS should include a list of examples of parties that often act for the reporting entity (without an assumption that they always act on behalf of the reporting entity). The Board seemed to agree that such a list might be helpful, but that any list provided should not be seen as definitive.

Derecognition of Financial Instruments

Bankruptcy remoteness concept

The Board analysed the legal isolation test with reference to the derecognition model. The Board discussed the issues that were connected with the application of the legal isolation test in US GAAP (a transfer must be bankruptcy-remote for an asset or component of an asset to be eligible for derecognition as a result of the transfer.

The Board decided not to include the legal isolation criteria in its derecognition approach as it believed that derecognition criteria should be driven by accounting principles and not specific legal rules. In the view of one Board member, determining what was and what was not a sale in financial statements should be based on accounting principles and not determined with reference to law. The Board was also concerned that introduction of the legal isolation test would be inconsistent with the Framework.

On the other hand, the Board stressed that bankruptcy remoteness concept should be reflected in measurement of the instruments and clarified by appropriate disclosures.

Accounting for repurchase agreements and similar transactions

The Board considered accounting for repo transactions in response to a very strong opposition among constituents to the proposals in the ED (which proposed to treat these transactions as sale transactions). The Board was told that these transactions were almost universally perceived as financing and that their treatment as sale transactions would increase volatility in profit or loss that had no economic substance. Moreover, several Board members noted that proposed treatment would be inconsistent with treatment of sale and leaseback transactions and might be contrary to substance over form principle embodied in the Framework.

On the other hand, other Board members preferred more conceptual arguments in favour of the proposed treatment (for example, differences to collateralised loans, existence of two sources of credit risk).

After an extended debate the Board acknowledged that some of the transactions, generally referred as repos, might have economic substance of a loan and some might have the economic substance of a sale. Consequently, the Board asked the staff to propose a criterion that would try to capture this distinction. In addition, the Board decided to discuss this question with the FASB in an attempt to coordinate views on this matter.

Accounting for retained interests

After a short discussion, the Board agreed to treat retained interests representing a proportionate interest in the asset previously recognised as part of the asset previously recognised. In all other cases, the Board decided to treat retained interest as a new asset and measure it at fair value on initial recognition. Subsequently retained interest should be accounted for on the basis of classification and measurement guidance on financial instruments.

The derecognition approach

The Board discussed two possible derecognition approaches, the amended IAS 39 approach and a modified alternative approach (modified by the accounting for repos and retained interests). The Board tentatively agreed with the alternative approach. Nonetheless, the Board agreed to discuss this approach with the FASB with the aim to achieve convergence. The Chairman noted that in light of this decision, re-exposure of the derecognition ED was probable.

This summary is based on notes taken by observers at the IASB meeting and should not be regarded as an official or final summary.

Notes from the Joint IASB-FASB Board Meeting
26-28 October 2009

Monday 26 October 2009

Revenue Recognition

Project Timetable

The staff began the meeting by discussing the timetable of this project. The Boards plan to issue an exposure draft in the second quarter of 2010, and a final standard in June 2011.

Segmentation of a Contract

The staff then explained that the purpose of the discussion was to decide on further guidance to clarify the recognition and measurement provisions outlined in the discussion paper. The primary concern relates to the extent to which an entity would be required to identify separate performance obligations and allocate consideration to each performance obligation (that is, segmentation of a contract). The model in the discussion paper directs entities to separate (or segment) contracts on the basis of when the promised goods and services are transferred to the customer.

The staff noted that comment letters indicated that the model as articulated in the Discussion Paper is not operational for contracts with many performance obligations (for example, does a performance obligation exist for each brick, nail, and labor hour?). The staff indicated that the discussion paper did not adequately convey the Boards intent and that clarifying language regarding segmentation will be necessary in the exposure draft.

The staff explained that segmentation is about measurement rather than recognition. An entity would identify the performance obligations and then aggregate based on established criteria. The staff proposed that the transaction price should be allocated to the segments of a contract rather than to individual performance obligations in the contract. Entities should separate contracts into segments when there is evidence that a market exists for those segments on a standalone basis. Standalone value as described in US GAAP is not a consideration in determining when segments exist. Rather, the entity should consider materiality, when goods and services are transferred, and the margins of the promised goods and services in determining the segments that exist within an arrangement.

While the Boards generally agreed with the staff's approach, they expressed concern that the segmentation model would add complexity to the model. Some board members requested more clarity on how an entity would determine the market to use in determining segments when multiple markets exist. For instance, two markets exist for a particular segment. One market consists of two performance obligations, and the other consists of six performance obligations. The staff noted that in this circumstance, the entity should use the market with the highest level of performance obligations (that is, the market consisting of two performance obligations).

One FASB member noted that the model should take a 'bottom up' approach. Under that approach, entities would first identify performance obligations and then determine whether or not these performance obligations should be aggregated into segments. The staff agreed that 'segmentation of contracts' could be better described as 'aggregation of performance obligations'. The Boards directed the staff members to further refine and articulate the model with respect to segmentation.

The staff proposed that allocation of the transaction price to the different segments within a contract should be based on the stand-alone selling price of the segment. If the standalone selling price is not directly observable, the entity should estimate the selling price of the segment. The staff further noted that when estimating selling price, entities should maximise the use of observable inputs, but the model should not prescribe any specific method of estimating selling price.

The staff also proposed that the residual method is not an acceptable allocation method. Instead, any discount should be allocated on the basis of the relative stand-alone selling price to the segments in the arrangement. Residual value may be used only as an input and not as a method of allocating a discount to segments within an arrangement.

The Boards agreed with the staff's recommendations. Several members of the Boards noted that the selling price hierarchy in Issue 08-1 [ASU 2009-13] should be included in this model to provide a framework for estimating selling price. Additionally, the Boards noted that robust disclosures would be needed. While the Boards agreed to that the residual method should not be used as an allocation method, several members expressed concern that if the residual method is allowed as an input, entities may not consider other inputs in allocating transaction price.

Recognising Revenue in a Segment of a Contract

The staff members proposed that an entity should exercise judgment and select from various methods of measuring goods and services transferred to a customer in a segment of a contract. The Boards agreed with the staff and instructed them to clarify that, while the general concept of recognizing revenue is based on the transfer of control, as a practical consideration, methods such as units of output, units of input, etc, may be used as a proxy in determining whether control has transferred to the customer. Once a method for recognising revenue for a particular segment is determined, that method should be used consistently for that segment within the contract and within other contracts.

Discontinued Operations (Amendments to IFRS 5)

What Constitutes a Discontinued Operation

The FASB and IASB resumed their discussions around what constitutes a discontinued operation. The staff presented a paper discussing a proposed definition for a discontinued operation, considering:

  1. what the appropriate starting point would be for a definition,
  2. whether it should include a significance criterion, and
  3. whether a definition should include a continuing involvement criterion.

Several members of both Boards questioned whether discontinued operations should continue to be presented on the face of the financial statements or whether footnote disclosures alone were more appropriate. FASB staff said that users overwhelmingly support showing discontinued operations on the face of the financial statements. Ultimately, both Boards voted to continue to require the presentation of discontinued operations on the face of the financial statements.

A few Board members questioned whether the proposed definition of discontinued operations was too arbitrary and would allow different users to reach different conclusions on what meets the definition. This could present opportunities for earnings management.

Some members of the IASB questioned whether the current definition under IFRS 5 was more appropriate and suggested amendments were not needed to IFRS 5. The FASB staff noted the proposed definition was similar to IFRS 5 except the staff tried to add some principles where it made sense from an analysis point of view. The IASB indicated that they would like to retain the current definition under IFRS 5.

Next Steps in the Project

The FASB staff outlined the next steps for this project. The FASB staff will consider differences between their proposed definition and the IFRS 5 definition and determine whether they believe that changing the current definition to the IFRS 5 definition will be an improvement to financial reporting. Further, the FASB staff will perform an analysis of the disclosure requirements under IFRS 5 and determine whether they believe those disclosures are adequate or if additional disclosures may be needed. The FASB indicated that they would like to discuss the staff's findings and considerations during November.

Financial Instruments – Replacement of IAS 39

Presentation

The Boards discussed whether both fair value and amortised cost information should be prominently disclosed on the face of the financial statements (for example, through parenthetical disclosure or reconciling information on the face of the financial statements). One benefit would be to allow investors to more easily compare financial statements prepared under the FASB's and IASB's respective approaches. Additionally, it was noted that some investors are looking for both fair value and amortised cost information in a timely manner. Some questioned whether providing both fair value and amortised cost on the face of the statement of financial position would be confusing to readers of financial statements.

A majority of the IASB members present indicated that they would not necessarily object to requiring entities to provide both fair value and amortised cost information on the face of the statement of financial position for financial instruments that under the IASB's approach are classified as amortised cost. The IASB agreed to consider this issue further at a future board meeting along with the issue of whether requiring prominent disclosure of changes in fair value in separate pro-forma statements to illustrate the impact on accumulated other comprehensive income and shareholders' equity. (The FASB has previously agreed to propose prominent disclosure on the financial statements of both fair value and amortised cost information for financial instruments that under the FASB's approach are classified as fair value through other comprehensive income.)

Core Principles

Subject to further refinement, the two Boards agreed on the following core principles for convergence of the FASB's and IASB's approaches to the accounting for financial instruments (note – the core principles outlined below are based on observer notes of the deliberations and are subject to refinement by the Boards):

  1. The new requirements should enhance comparability for the benefit of investors.
  2. The new requirements should provide transparency of risk exposures in management business strategies.
  3. Prominent and timely fair value information is relevant for financial instruments with highly variable cash flows or held for trading purposes.
  4. Both amortised cost and fair value information is relevant for financial instruments with principal amounts held for collection or payment of the contractual cash flows rather than for sale or settlement with a third party.
  5. The new requirements should be less complex to implement.
  6. The impairment approach for financial assets held for collection of contractual cash flows should be consistent.

Related to principle 4, some Board members expressed concern about the relevance of fair value information for financial liabilities due to the impact of own credit risk on fair value measurements of liabilities. The Boards agreed to post to their respective project websites the core principles for accounting for financial instruments after the refinements are made.

Work Plan for Convergence

The FASB staff informed the Boards that the FASB anticipates issuing an exposure draft on the accounting for financial instruments project in the first quarter of 2010. In addition, the following work plan was identified:

  • Both Boards will jointly deliberate improvements to hedge accounting in November and December.
  • The expert advisory panel will focus on both the IASB's and FASB's proposed impairment models.
  • Understand differences and identify specific financial instruments that will be impacted by the classification and measurement models being developed by the two Boards.
  • Jointly deliberate issues related to credit risk in liability measurement.
  • Issue final standard in late 2010.

Impairment

The Boards exchanged questions about their respective approaches to credit impairment which focused on what information can be used to determine whether a credit impairment exists. IASB members asked whether the FASB's approach could result in the recognition of a loss on initial recognition of a portfolio of loans if there is an expectation of credit losses in the portfolio. FASB members indicated that they had not yet deliberated the details of FASB's approach. No decisions were made.

Consolidation

The purpose of this session was to (1) discuss the convergence approach, if any, to be taken by both Boards in finalising their projects on consolidation and (2) identify consolidation issues for deliberation by both Boards at future joint meetings.

Convergence Project Plan

The staff recommended that the Boards work together and ultimately issue a converged standard on consolidations.

The Boards deliberated various options for proceeding to finalise their respective projects. The Boards agreed with the staff on working together to issue a converged standard on consolidation. Going forward, the Boards would jointly deliberate the various consolidation issues identified before the IASB finalises its new consolidation standard. The FASB would then expose the final IASB standard, redeliberate the guidance based on public comments received on the exposure draft, and then proceed to issue a final FASB standard. The IASB final standard and FASB exposure draft should be completed by late March or early April 2010, with both Boards issuing their final standards by the end of 2010.

The IASB noted that its current model provides the same criteria for voting interest entities as it does for structured entities. The FASB indicated that in proceeding with the project, the same criteria should apply to both voting interest entities and variable interest entities.

Issues for Redeliberation

The staff pointed out that while the basic control models were converged between FASB Statement 167 and IASB ED 10, there remained differences between the IASB's and FASB's guidance on kick-out rights that should be deliberated at future joint meetings. There are also a number of issues that both Boards had yet to consider or deliberate which also would require discussion over the next few months.

The Boards held preliminary discussions on kick-out rights regarding when they can be ignored, when they can be considered substantive, and how the kick-out right provisions should be applied to various scenarios. In particular, the IASB asked many questions about why Statement 167 requires kick-out rights be ignored unless they are held by a single enterprise. The FASB indicated that it is an anti-abuse provision because they believe kick-out rights are generally non-substantive. The Boards asked the staff to finalise the list of issues that should be deliberated and prepare to present these issues with examples at the next joint meeting in December 2009.

Financial Instruments with the Characteristics of Equity

The staff described a new proposal (Approach 4.1) for distinguishing between liability and equity instruments and asked the Boards whether they were interested in pursuing this approach. Staff explained the difference between Approach 4.1 and Approach 4, which the Boards had discussed previously. Under Appriach 4, shares that are issued pursuant to the contract (that is, all share-settled instruments) would be classified as liabilities regardless of their terms. Under the new Approach 4.1, share-settled instruments would be subject to a separate classification principle, under which the shares that an entity is not using as currency would be classified as equity. In particular, an instrument required to be settled by issuing equity instruments would be equity unless:

  • (a) either party has a cash settlement option,
  • (b) it requires net settlement in shares or either party has a net settlement option, or
  • (c) the contract exposes either party to risks of changes in value other than those resulting from share price changes, time value of money, counterparty performance risk, and possibly foreign currency.

This classification principle would result in equity classification of certain share-settled instruments like preferred shares convertible into common shares, forwards to sell shares, physically settled written call options, and stock options. These instruments would have been classified as a liability under Approach 4.

Puttable or mandatorily redeemable instruments would be classified as equity if they are redeemable upon death or retirement, or upon the holder ceasing to participate in the activities of an entity. All other puttable or mandatorily redeemable instruments would be separated or classified as liabilities in their entirety.

Some Board members questioned whether convertible debt instruments should be classified as liabilities as proposed under Approach 4.1 or whether the convertible instrument should be bifurcated. Some suggested that this issue may be better addressed as part of the Financial Instruments Project.

Several members raised concern about the arbitrage and structuring opportunities with Approach 4.1, including unstated cash settlement features. For example, Approach 4.1 would allow an entity to avoid liability classification by writing a gross physically settled written call option (which would be classified as equity) and not having sufficient authorised and unissued shares available to satisfy the contract, in which case the entity would pay the holder cash instead of shares. The economics of the transaction would be the same as if the issuer had written the derivative to be cash settled; the derivative to be cash settled however would be classified as a liability.

Some members from both Boards raised concerns that under Approach 4.1 the information about the effects of dilution by particular instruments to shareholders would not be reflected in the financial statements. It was suggested that shareholders should be informed about the dilutive effect of certain instruments through appropriate presentation in the financial statements.

It was also explained that in relation to developing a definition of a liability in the conceptual framework that is consistent with Approach 4.1, the staff intended to keep the definition of a liability similar to what is in the current framework (that is, a liability requires a transfer of cash or assets) and to provide exceptions to the definition for share-settled instruments classified as a liability and for cash-settled instruments classified as equity.

Most members agreed to pursue Approach 4.1 and to consider ways to resolve arbitrage issues inherent in Approach 4.1.

Tuesday 27 October 2009

Financial Statement Presentation – Other Comprehensive Income

Proposal for limited scope amendment to IAS 1 Presentation of Financial Statements

The staff recommended that the Board eliminate the option in paragraph 81 of IAS 1 that permits an entity to present all items of income and expense recognised in a period in two statements. In recommending that the two statement option be removed, the staff recommended that the Board decide to require that a single statement of comprehensive income be displayed with two sections: profit or loss and other comprehensive income (OCI).

The Board tentatively agreed with the staff recommendation to require a single statement of comprehensive income with the two sections (as described above). The Board also emphasised that this proposal would not change items that can or must be presented in OCI or whether an item must be reclassified upon derecognition.

The staff recommended that the Board tentatively decide to require that components of OCI that will not be reclassified into profit or loss in future periods be displayed together and that components of OCI that will be reclassified into profit or loss in future periods be displayed together. The Board agreed with the staff's recommendation to display items with similar reclassification requirements together.

Lastly, the staff recommended that the Board tentatively decide (a) to remove the option that allows an entity to display components of OCI net of income tax effects and (b) that the income tax effect of an OCI item be displayed with the related OCI item in the statement of comprehensive income. The Board tentatively agreed to remove the option to permit an entity to display components of OCI net of tax. In addition, the Board agreed that income taxes related to items reported in OCI should be allocated between those items that will not be reclassified into profit or loss in future periods and those items that will be reclassified into profit or loss in future periods.

The IASB and FASB agreed to work together to develop exposure drafts to amend their respective requirements under IAS 1 and the FASB Accounting Standards Codification in order to allow the Boards to expose the proposals at the same time. The FASB indicated that it would be beneficial if the timing of the proposal could coincide with the pending release of the exposure draft on Financial Instruments: Recognition and Measurement later this year.

Financial Statement Presentation

The staff addressed the following four topics regarding the discussion paper, Preliminary Views on Financial Statement Presentation:

  1. The statement of cash flows
  2. The reconciliation schedule
  3. Disaggregation by function and nature
  4. Classification: section and category definitions

Statement of Cash Flows

Presentation of Cash Flows Using the Direct Method

The staff began the discussion with a refresher of the feedback received from preparers and users of financial statements during an April 2009 meeting. The main theme of the feedback from preparers and the users was discussed with regards to the use of the direct method of cash flow presentation. Preparers believe that using the direct method is costly and may provide little benefit while users generally believe that this method is useful when prepared using disaggregated information. In hearing both groups, the staff believes that there may be support for a direct method of presentation supplemented with additional indirect information in the financial statements.

As such, the staff presented two alternatives to present cash flow information. In the first alternative, an entity would prepare its statement of cash flows using a less disaggregated (than as described in the discussion paper) direct method of presentation while presenting indirect information in the notes to its financial statements. Under the second alternative, the entity would prepare its statement of cash flows using an improved indirect method of presentation coupled with supplemental disclosures.

The Boards agreed with the staff's recommendation of using the first alternative when presenting information on the statement of cash flows. They believe that an entity should be required to present line items for cash receipts and payments in each section (and category) of the statement. In addition, they believe that an entity should reconcile operating income to cash flows from operations because it will provide the most meaningful information to users (e.g., changes in working capital assets and liabilities). The Boards also expressed the view that the upcoming exposure draft should only require a single method of cash flow presentation and not provide alternative methods.

Disclosing Non-Cash Information

Also discussed during the staff's research and user/preparer outreach discussed above was the notion that non-cash information does not necessarily represent cash flows and as a result, reduces a user's ability to assess the quality of reported earnings. While acknowledging this concern, the staff recommended to the Boards that the requirement in the discussion paper be retained. That is, an entity should be required to disclose non-cash information in notes to financial statements. The Boards agreed with this recommendation.

Other Cash Flow Related Disclosures

The staff recommended to the Boards that disclosure of repatriation limitations and other restrictions on cash should be disclosed in the footnotes to the financial statements. The Boards agreed with the staff's recommendation as they believe the information can be useful to a capital provider.

The Reconciliation Schedule

Because many users and preparers had questioned the proposed reconciliation schedule, through comment letters and user/preparer outreach, the staff discussed whether the Boards should reconsider this schedule to reconcile cash flows to comprehensive income. Concerns were focused mainly on the scale of the reconciliation, the particular accounts being reconciled, and the notion that the focus of the reconciliation should be on the distinction of changes in assets and liabilities that are attributable to remeasurement from those that are not.

The staff recommended a proposal that includes a revised reconciliation schedule that would analyse only the changes in 'significant' line items and that remeasurements be displayed separately on the statement of comprehensive income. While not specifically defining significant, the staff recommended to the Boards the following list of factors that an entity may use when determining which changes in line items to analyse:

  • the significance of the ending balance with respect to total assets or total liabilities
  • the significance of a change in the account balance with respect to revenues or expenses
  • the significance of the activity flowing through the account with respect to revenues or expenses
  • the use of assumptions or judgments in measuring the asset or liability and the degree of uncertainty or variability in the measurement due to risk exposure and the nature of that exposure (for example, credit, foreign exchange, interest rate)
  • the nature and magnitude of transactions or events that are non-routine or non-repetitive
  • any other transaction or event that could affect the future investment or credit decisions of a reasonable investor, creditor, or other user of financial statements

The Boards agreed with the staff's recommendation to revise the reconciliation schedule to only analyse changes in significant line items. However, the Boards did not reach agreement on the separate depiction of remeasurements. Some Board members questioned whether the depiction of remeasurements improved financial statement presentation while others questioned how entities would display this information (2 or 3 column reconciliations versus footnote disclosures). The staff was encouraged to consider further analysis on the merits of such information and the method for which to display it.

Disaggregation by Function and Nature

In light of feedback from various groups, the staff refined its thoughts on (a) the level of disaggregation an entity should present in its financial statements (Issue 1) and (b) where disaggregated information should be presented to be most decision useful in predicting future cash flows (Issue 2). The staff recommended to the Boards that in Issue 1, the discussion paper proposal that specifically requires disaggregation by function and nature on the statement of comprehensive income would be replaced by a disaggregation principle that requires an entity to consider disaggregation by function, nature, and measurement bases in the financial statements as a whole. This would mean the Boards would not specifically require an entity to disaggregate information in the statement of comprehensive income by function and nature. In Issue 2, the staff recommended that an entity that has only one reportable segment present its disaggregated information on the face of its primary statements and that an entity that has more than one reportable segment should present its disaggregated information in its segment note.

For both issues, the Boards conceptually agreed with the staff's recommendation. For Issue 1, the Boards encouraged the staff to further refine a principle for which an entity would base its disaggregation on. For Issue 2, while the Boards agreed with the staff's recommendation that an entity with multiple reportable segments present its information in its segment note, they questioned why the proposal would require an entity with only one reportable segment to present its information only on the face of the primary statements. They encouraged the staff to consider whether an entity with a single reportable segment should be allowed to present its information in its segment note as well.

Classification: section and category definitions

The staff discussed the following recommendations, all of which the Boards agreed with, relating to the section and category definitions to be used in the upcoming exposure draft:

  1. A treasury category should not be included in the financing section.
  2. Retain an operating and investing category in the business section of each of the financial statements. Those categories require a reporting entity to make a distinction between business activities that are active in nature (operating category) and business activities that are passive in nature (investing category).
  3. Equity should be a category in the financing section.

The staff clarified that any decisions made on the related to the section and category definitions were be used as a basis for future deliberations. As such, the staff indicated that the definitions will continue to evolve.

Next Steps

While not discussed at the meeting, information regarding the staff's next steps and the overall technical plan was provided in a handout at the meeting. The handout listed the following items to be discussed in November thru January leading up to the publication of an exposure draft in April 2010:

  • Statement of financial position
  • Financial services entity issues
  • Non-controlling interests
  • Basket transactions
  • Foreign currency exchange transactions
  • Segment disclosures
  • Bringing it all together – the core presentation principles and the resulting financial statements.
  • Nonpublic entity scope issue
  • Overall costs and benefits of the presentation model
  • Transition and effective date.

Wednesday 28 October 2009

Fair Value Measurement

The IASB published the exposure draft Fair Value Measurement in May 2009 and received 156 comment letters at the time of the posting of the agenda paper.

Most respondents to the exposure draft urged convergence on the guidance for fair value measurement under IFRSs and US GAAP. The respondents were concerned with the use of different words in IFRSs and US GAAP might result in different approaches under fair value measurement and possibly different fair value conclusions. The staff presented three types of differences (please refer to the IASB Agenda Paper 11 for further details on each of the differences noted below):

  • Type 1: Differences due to decisions taken by the IASB relating to
    • (a) scope,
    • (b) reference market,
    • (c) highest and best use,
    • (d) blockage factor,
    • (e) day 1 gains or losses,
    • (f) valuation premise and financial instruments,
    • (g) measurement of liabilities, and
    • (h) measurement of equity instruments
  • Type 2: Differences to clarify some of the principles of Topic 820, namely
    • (a) highest and best use,
    • (b) valuation premise, and
    • (c) valuation techniques)
  • Type 3: Differences in grammar, spelling and style

The staff then presented three approaches to the Boards on dealing with the differences that currently exist in the fair value measurement guidance. The approaches were:

  • Approach 1: Eliminate all decision and wording differences. This approach requires both Boards to redeliberate all issues where differences have been identified.
  • Approach 2: Eliminate Type 2 wording differences only. Under this approach the Boards would use the same words except for when each Board has reached a different decision.
  • Approach 3: Continue as before. The IASB would publish an IFRS on fair value measurement guidance independently.

However, both Boards would monitor the activities of the other to minimise differences between the two standards. This is the approach undertaken so far in the project.

The Boards agreed to follow Approach 1 for the fair value measurement project moving forward.

Insurance Contracts

Resolution of significant differences in technical decisionsby the two Boards

The staff used this meeting to reconcile the significant areas where the Boards have reached different decisions. The resolution of the differences on the project is integral to the timely completion of deliberations and subsequent issuances of an exposure draft. The staff presented three areas where the Boards had reached different conclusions:

  1. Policyholder accounting
  2. Measurement objective
  3. Acquisition costs

Policyholder accounting

The scope of the project initially included accounting by both the issuer of the insurance contract (the insurer) and the purchaser of the insurance contract (the policyholder). However, the IASB tentatively decided at a previous meeting not to address policyholder accounting in the exposure draft. The FASB had not yet discussed whether policyholder accounting should be included or excluded from the exposure draft.

The Boards discussed whether policyholder accounting should be included or excluded from the exposure draft. The Boards agreed that the staff should further evaluate the potential scope of the project and come back at a later Board meeting to discuss whether policyholder contracts should be within the scope of the Exposure Draft.

Measurement objective

The Boards discussed the measurement approaches for insurance contracts. At previous Board meetings, the IASB tentatively selected the measurement approach being developed in the project to amend IAS 37, modified to exclude day one gains, and the FASB tentatively selected a current fulfilment approach with a composite margin.

The Boards discussed the similarities and differences between the two measurement models. The Boards noted that the words used to describe the models were causing confusion and emphasised the importance of using the correct words. The Boards agreed that the staff would present to the Boards at a future meeting the concepts of both measurement models, using the correct words to describe each model.

Acquisition Costs

Previously both Boards had reached a tentative decision that acquisition costs should be expensed. Subsequently, the IASB had tentatively decided that at inception an insurer should recognise revenue premium to cover acquisition costs incurred. Therefore, acquisition costs should be limited to the incremental costs of issuing (that is, selling, underwriting, and initiating) an insurance contract and should not include other direct costs. In contrast, the FASB had believed the insurer should not recognise any revenue (or income) to offset the acquisition costs incurred.

The Boards extensively questioned why insurance contracts would recognise revenue differently from other industries. Many Board members believe that no performance obligation is satisfied upon signing of the contract and, therefore, no revenue should be recognised at inception. It was tentatively decided by the Boards that an insurer would not recognise any premium at inception to offset the acquisition costs.

Leases

Lessor Models under a Right-of-Use Approach

The staff began the leases portion of the meeting discussing potential models that could be used for lessors in accounting for leases. One model is the derecognition approach. Under this approach, the lessor is viewed as having transferred a portion or all of the leased asset to the lessee in exchange for a right to receive rental payments. The lessor derecognises the leased asset because it no longer controls the right to use that asset during the lease term. As such, the lessor derecognises the leased asset and recognises a receivable. The lessor continues to recognise those rights that have not been transferred to the lessee (the residual value of the asset).

Another model is the performance obligation approach. Under this approach, the lessor is viewed as having granted the lessee the right to use its economic resource (the leased asset) in exchange for the right to receive rental payments. The lessor does not lose control of the leased property and continues to recognise the leased asset. The lessor would recognise a receivable for the right to receive rental payments and a corresponding liability for the obligation to permit use of the leased asset.

The staff also discussed two other models: the current operating lease approach and the dual-model approach. The current operating lease approach would retain the current guidance for operating leases for lessors. The dual-model approach recognises that not all leases are the same and would provide guidance on when to use each model.

Both Boards decided on the performance obligation approach. Members supporting this approach noted that 'possession' of a leased asset is not synonymous with 'control' and that the derecognition approach confuses the underlying asset with a separable right to use the asset. The Boards directed the staff to perform further analysis on how this model would (a) be impacted by impairment, (b) affect manufacturing lessors, and (c) affect investment properties.

The Boards discussed the financial statement presentation of the receivable, leased asset, and obligation. Some Board members indicated that they may support a net presentation approach in which the receivable and obligation are netted, but no decision was made at this meeting. The Boards asked the staff to perform further analysis of possible presentation approaches under performance obligation approach.

Should lessees use the right-of-use approach?

The staff asked the Boards to confirm their prior decision that lessees apply a right-of-use approach for a simple lease contract. The staff did not ask the Boards to discuss the scope of the lease project, the definition of a lease, or leases with options and contingent rentals. These topics will be discussed at future meetings. The staff also acknowledged that the Boards will need to consider how lease accounting applies to short-term leases and immaterial leases. The Boards unanimously confirmed their decision to proceed with a right-of-use approach.

In-substance purchases/sales

The staff proposed that lease contracts that are purchases/sales of the leased item should be excluded from the scope of the new lease standard. The Boards agreed that sales/purchases should be excluded from the scope of the new lease standard.

The staff next recommended that an entity should consider applicable revenue recognition guidance in determining whether a sale/purchase of a leased item has occurred. The Boards expressed concern with this approach as there are different views on what 'transfer of control' means with regard to lease transactions, and therefore they rejected this recommendation.

The Boards agreed that the determination of whether a sale/purchase has occurred should be based on the specific terms of the lease. For example, Board members generally agreed that if title transfers at the end of a lease, then a sale/purchase has occurred. The Boards decided that the new lease standard should provide guidance on how an entity should determine whether a sale/purchase has occurred and directed the staff to develop criteria that would assist entities in this assessment.

The staff also asked Board members whether they supported creating a separate accounting model for transactions that were within the scope of the new lease standard but that had sales/purchases features. The Board members affirmed that only one model (the right-of-use model) should exist in the new lease standard and that another model for leases with some sales/purchases features should not be developed.

Timing of initial recognition

The staff proposed to the Boards that entities should recognise assets and liabilities from the lease transaction upon contract signing. Further, the staff recommended that between contract signing and delivery of the leased asset(s), the unit of account is the contract as a whole and that the contract position should be presented net in the statement of financial position. Upon delivery, the lease asset and lease obligation would be presented on a gross basis. The Boards agreed with the staff's recommendation.

Next, the staff recommended that entities should initially and subsequently measure the assets and liabilities (the net contract position) in a contract on a cost basis. The Boards agreed with the proposal but clarified that the cost would be subject to impairment under other applicable standards. In other words, if there was impairment on a lease contract between contract signing and delivery of the leased asset, the entity would 'write-down' the asset and the contract would be in a net liability position. If the lessee decided to cancel the contract, it would derecognise the net lease contract and record an obligation in the amount of the penalty to cancel the contract. The Boards also agreed with the staff to require additional disclosures in situations where the time between contract signing and delivery is long and/or the rights and obligations are significant.

Income Taxes

The IASB staff began the meeting by providing a summary of the general comments received from constituents on the IASB's Income Tax exposure draft (ED). The ED was published on 31 March 2009, with comments due on 31 July 2009. The IASB received 168 comment letters.

The IASB staff pointed out that most respondents supported the two objectives of the project, which were convergence with US GAAP and improvements to the current accounting in IAS 12. However, the IASB staff explained that while most respondents were supportive of the overall objectives, many respondents felt that the ED failed to achieve these objectives due primarily to the following two reasons:

  1. The FASB suspended the project and has no specific plan to resume it.
  2. The proposed changes in the ED were viewed not as improvements but rather as the introduction of complex new rules.

The IASB staff then noted that as a result, there was very limited support amongst respondents for finalising the ED in its current form. Rather, many respondents suggested making certain improvements to IAS 12 in the short-term while also adding a new longer-term joint project with the FASB and/or a fundamental review of accounting for income taxes.

The Boards then discussed the direction of the income tax project. Some Board members expressed concern that not moving forward with the income tax project could be perceived by some that the FASB and IASB aren't committed to the convergence effort, as this was a project outlined in the Memorandum of Understanding. They further noted that not reaching convergence on income tax accounting could become a stumbling block to the US adoption of IFRS. Most Board members agreed that while a fundamental review and overhaul of accounting for income taxes is needed, the resources and time required for such an undertaking are not currently available. As such, the Boards agreed to delay such a fundamental review until some of the other existing projects are completed and discussed the possibility of the IASB making a few amendments to IAS 12 in the short-term.

The potential short-term amendments to IAS 12 that were discussed focused on convergence with US GAAP, specifically regarding the current recognition exceptions contained in IAS 12. Board members expressed differing views on how practical it would be to make these short-term amendments. The IASB staff pointed out that a majority of respondents to the ED were not in favour of making changes to the recognition exceptions currently contained in IAS 12 and noted that the FASB and IASB would need to work together and both amend their respective standards to reach full convergence in this area.

The IASB staff closed the discussion by mentioning that the direction of the IASB's income tax project will be discussed further at the IASB meetings over the coming month.

Technical Plan

The IASB staff indicated that the IASB website will be updated next week to reflect any changes in the timing of projects as a result of decisions reached over the last three days.

This summary is based on notes taken by observers at the joint IASB-FASB meeting and should not be regarded as an official or final summary.

The IASB publishes summaries of the deliberations at Board meetings in its newsletter IASB Update. Past issues of IASB Update are available on IASB's Website. On Individual Project Pages on the IASB Website you will find links to observer notes and excerpts from IASB Update relating to that project.


Top of Page Legal   |   Privacy

Material on this website is © 2010 Deloitte Global Services Limited, or a member firm of Deloitte Touche Tohmatsu Limited, or one of their affiliates. See Legal for additional copyright and other legal information.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited, a UK private company limited by guarantee, and its network of member firms, each of which is a legally separate and independent entity. Please see deloitte.com\about for a detailed description of the legal structure of Deloitte Touche Tohmatsu Limited and its member firms.

© 2010 Deloitte Global Services Limited.