Startseite Partner Suche Impressum Kontakt Diskussionsforum

-

-

Aktuelle Jobs

-

 

Jobbörse

 

-

Allgemein

-

 

Diskussionsforum

 

 

IFRS/IAS  

 

Newsletter  

Musterabschluss

Abschlüsse

-

Dienstleistungen

-

 

IFRS Anwendergruppe

 

 

Umstellungen auf IFRS  

Software/IFRS-Toolkit

-

Grundlagen

-

 

Was sind IFRS/IAS?

 

 

Was ist der IASB?  

 

Umstellungsprozess  

 

Endorsement  

Glossar

-

Mittelstand

-

 

IFRS für KMU  

-

Literatur

-

 

Presse

 

 

Aufsatzdatenbank  

 

Fachbücher  

Broschüren

-

Texte deutsch

-

 

Framework

 

 

Standards  

Interpretations

-

Texte englisch

-

 

Framework

 

 

Standards  

Interpretations

-

Sonstiges

-

 

Gästebuch

 

 

Archive  

 

Links  

 

Über uns  

Sitemap


-

INTERNATIONAL ACCOUNTING STANDARD 37 (2006)

Previous | Index | Next

  Source

-

Commission Regulation (EC) No 1725/2003 of 29 September 2003 adopting certain international accounting standards in accordance with Regulation (EC)   No 1606/2002 of the European Parliament and of the Council

  Content

-

Reimbursements

53. Where some or all of the expenditure required to settle a provision is expected to be reimbursed by another party, the reimbursement should be recognised when, and only when, it is virtually certain that reimbursement will be received if the enterprise settles the obligation. The reimbursement should be treated as a separate asset. The amount recognised for the reimbursement should not exceed the amount of the provision.

54. In the income statement, the expense relating to a provision may be presented net of the amount recognised for a reimbursement.

55. Sometimes, an enterprise is able to look to another party to pay part or all of the expenditure required to settle a provision (for example, through insurance contracts, indemnity clauses or suppliers' warranties). The other party may either reimburse amounts paid by the enterprise or pay the amounts directly.

56. In most cases the enterprise will remain liable for the whole of the amount in question so that the enterprise would have to settle the full amount if the third party failed to pay for any reason. In this situation, a provision is recognised for the full amount of the liability, and a separate asset for the expected reimbursement is recognised when it is virtually certain that reimbursement will be received if the enterprise settles the liability.

57. In some cases, the enterprise will not be liable for the costs in question if the third party fails to pay. In such a case the enterprise has no liability for those costs and they are not included in the provision.

58. As noted in paragraph 29, an obligation for which an enterprise is jointly and severally liable is a contingent liability to the extent that it is expected that the obligation will be settled by the other parties.

Changes in provisions

59. Provisions should be reviewed at each balance sheet date and adjusted to reflect the current best estimate. If it is no longer probable that an outflow of resources embodying economic benefits will be required to settle the obligation, the provision should be reversed.

60. Where discounting is used, the carrying amount of a provision increases in each period to reflect the passage of time. This increase is recognised as borrowing cost.

Use of provisions

61. A provision should be used only for expenditures for which the provision was originally recognised.

62. Only expenditures that relate to the original provision are set against it. Setting expenditures against a provision that was originally recognised for another purpose would conceal the impact of two different events.

Application of the recognition and measurement rules

Future operating losses

63. Provisions should not be recognised for future operating losses.

64. Future operating losses do not meet the definition of a liability in paragraph 10 and the general recognition criteria set out for provisions in paragraph 14.

65. An expectation of future operating losses is an indication that certain assets of the operation may be impaired. An enterprise tests these assets for impairment under IAS 36, impairment of assets.

Onerous contracts

66. If an enterprise has a contract that is onerous, the present obligation under the contract should be recognised and measured as a provision.

67. Many contracts (for example, some routine purchase orders) can be cancelled without paying compensation to the other party, and therefore there is no obligation. Other contracts establish both rights and obligations for each of the contracting parties. Where events make such a contract onerous, the contract falls within the scope of this Standard and a liability exists which is recognised. Executory contracts that are not onerous fall outside the scope of this Standard.

68. This Standard defines an onerous contract as a contract in which the unavoidable costs of meeting the obligations under the contract exceed the economic benefits expected to be received under it. The unavoidable costs under a contract reflect the least net cost of exiting from the contract, which is the lower of the cost of fulfilling it and any compensation or penalties arising from failure to fulfil it.

69. Before a separate provision for an onerous contract is established, an enterprise recognises any impairment loss that has occurred on assets dedicated to that contract (see IAS 36, impairment of assets).

Restructuring

70. The following are examples of events that may fall under the definition of restructuring:

(a) sale or termination of a line of business;

(b) the closure of business locations in a country or region or the relocation of business activities from one country or region to another;

(c) changes in management structure, for example, eliminating a layer of management; and

(d) fundamental reorganisations that have a material effect on the nature and focus of the enterprise's operations.

71. A provision for restructuring costs is recognised only when the general recognition criteria for provisions set out in paragraph 14 are met. Paragraphs 72 to 83 set out how the general recognition criteria apply to restructurings.

72. A constructive obligation to restructure arises only when an enterprise:

(a) has a detailed formal plan for the restructuring identifying at least:

(i) the business or part of a business concerned;

(ii) the principal locations affected;

(iii) the location, function, and approximate number of employees who will be compensated for terminating their services;

(iv) the expenditures that will be undertaken; and

(v) when the plan will be implemented; and

(b) has raised a valid expectation in those affected that it will carry out the restructuring by starting to implement that plan or announcing its main features to those affected by it.

73. Evidence that an enterprise has started to implement a restructuring plan would be provided, for example, by dismantling plant or selling assets or by the public announcement of the main features of the plan. A public announcement of a detailed plan to restructure constitutes a constructive obligation to restructure only if it is made in such a way and in sufficient detail (i.e. setting out the main features of the plan) that it gives rise to valid expectations in other parties such as customers, suppliers and employees (or their representatives) that the enterprise will carry out the restructuring.

74. For a plan to be sufficient to give rise to a constructive obligation when communicated to those affected by it, its implementation needs to be planned to begin as soon as possible and to be completed in a timeframe that makes significant changes to the plan unlikely. If it is expected that there will be a long delay before the restructuring begins or that the restructuring will take an unreasonably long time, it is unlikely that the plan will raise a valid expectation on the part of others that the enterprise is at present committed to restructuring, because the timeframe allows opportunities for the enterprise to change its plans.

75. A management or board decision to restructure taken before the balance sheet date does not give rise to a constructive obligation at the balance sheet date unless the entity has, before the balance sheet date:

(a) started to implement the restructuring plan; or

(b) announced the main features of the restructuring plan to those affected by it in a sufficiently specific manner to raise a valid expectation in them that the entity will carry out the restructuring.

If an entity starts to implement a restructuring plan, or announces its main features to those affected, only after the balance sheet date, disclosure is required under IAS 10 Events after the Balance Sheet Date, if the restructuring is material and non-disclosure could influence the economic decisions of users taken on the basis of the financial statements.

76. Although a constructive obligation is not created solely by a management decision, an obligation may result from other earlier events together with such a decision. For example, negotiations with employee representatives for termination payments, or with purchasers for the sale of an operation, may have been concluded subject only to board approval. Once that approval has been obtained and communicated to the other parties, the enterprise has a constructive obligation to restructure, if the conditions of paragraph 72 are met.

77. In some countries, the ultimate authority is vested in a board whose membership includes representatives of interests other than those of management (e.g. employees) or notification to such representatives may be necessary before the board decision is taken. Because a decision by such a board involves communication to these representatives, it may result in a constructive obligation to restructure.

78. No obligation arises for the sale of an operation until the enterprise is committed to the sale, i.e. there is a binding sale agreement.

79. Even when an enterprise has taken a decision to sell an operation and announced that decision publicly, it cannot be committed to the sale until a purchaser has been identified and there is a binding sale agreement. Until there is a binding sale agreement, the enterprise will be able to change its mind and indeed will have to take another course of action if a purchaser cannot be found on acceptable terms. When the sale of an operation is envisaged as part of a restructuring, the assets of the operation are reviewed for impairment, under IAS 36, impairment of assets. When a sale is only part of a restructuring, a constructive obligation can arise for the other parts of the restructuring before a binding sale agreement exists.

80. A restructuring provision should include only the direct expenditures arising from the restructuring, which are those that are both:

(a) necessarily entailed by the restructuring; and

(b) not associated with the ongoing activities of the enterprise.

81. A restructuring provision does not include such costs as:

(a) retraining or relocating continuing staff;

(b) marketing; or

(c) investment in new systems and distribution networks.

These expenditures relate to the future conduct of the business and are not liabilities for restructuring at the balance sheet date. Such expenditures are recognised on the same basis as if they arose independently of a restructuring.

82. Identifiable future operating losses up to the date of a restructuring are not included in a provision, unless they relate to an onerous contract as defined in paragraph 10.

83. As required by paragraph 51, gains on the expected disposal of assets are not taken into account in measuring a restructuring provision, even if the sale of assets is envisaged as part of the restructuring.

 

Previous | Index | Next

 


 

Anzeige

Newsletter:

Name

E-Mail

-

Partner

-

RöverBrönner KG

-

Mediadaten

-

 

Zugriffszahlen

 

Onlinewerbung

-

Veranstalter

-

 

AvenDATA GmbH

 

 

Digitale Signatur

 

 

GDPdU Portal

 

 

Unternehmens-nachfolge

 

 

Verfahrens-dokumentation

 

 

AvenDATA GmbH. Kaiserin-Augusta-Allee 14 . D-10553 Berlin . Deutschland
  Tel +49 30 700 157 500 . Fax +49 30 700 157 599  . E-mail: webmaster@ifrs-portal.com