(either as an increase in or a reduction of revenue) at the date of the contract modification (ie the adjustment to revenue is made on a cumulative catch-up basis).

If the remaining goods or services are a combination of items (a) and (b), then the entity shall account for the effects of the modification on the unsatisfied (including partially unsatisfied) performance obligations in the modified contract in a manner that is consistent with the objectives of this paragraph.

Identifying performance obligations

22  At contract inception, an entity shall assess the goods or services

promised in a contract with a customer and shall identify as a performance obligation each promise to transfer to the customer either:

a series of distinct goods or services that are substantially the same and that have the same pattern of transfer to the customer (see paragraph 23).

 A series of distinct goods or services has the same pattern of transfer to the customer if both of the following criteria are met:

each distinct good or service in the series that the entity promises to

transfer to the customer would meet the criteria in paragraph 35 to be a

performance obligation satisfied over time; and

in accordance with paragraphs 39-40, the same method would be used to measure the entity's progress towards complete satisfaction of the performance obligation to transfer each distinct good or service in the series to the customer.

Promises in contracts with customers

A contract with a customer generally explicitly states the goods or services that an entity promises to transfer to a customer. However, the performance obligations identified in a contract with a customer may not be limited to the goods or services that are explicitly stated in that contract. This is because a contract with a customer may also include promises that are implied by an entity's customary business practices, published policies or specific statements if, at the time of entering into the contract, those promises create a valid expectation of the customer that the entity will transfer a good or service to the customer.

Performance obligations do not include activities that an entity must undertake to fulfil a contract unless those activities transfer a good or service to a customer. For example, a services provider may need to perform various administrative tasks to set up a contract. The performance of those tasks does not transfer a service to the customer as the tasks are performed. Therefore, those setup activities are not a performance obligation.

(either as an increase in or a reduction of revenue) at the date of the contract modification (ie the adjustment to revenue is made on a cumulative catch-up basis).

If the remaining goods or services are a combination of items (a) and (b),

then the entity shall account for the effects of the modification on the unsatisfied (including partially unsatisfied) performance obligations in the modified contract in a manner that is consistent with the objectives of this paragraph.

Identifying performance obligations

22  At contract inception, an entity shall assess the goods or services

promised in a contract with a customer and shall identify as a performance obligation each promise to transfer to the customer either:

a good or service (or a bundle of goods or services) that is distinct; or  a series of distinct goods or services that are substantially the same and that have the same pattern of transfer to the customer (see paragraph 23).

 A series of distinct goods or services has the same pattern of transfer to the customer if both of the following criteria are met:

each distinct good or service in the series that the entity promises to transfer to the customer would meet the criteria in paragraph 35 to be a performance obligation satisfied over time; and in accordance with paragraphs 39-40, the same method would be used to measure the entity's progress towards complete satisfaction of the performance obligation to transfer each distinct good or service in the series to the customer.

Promises in contracts with customers

A contract with a customer generally explicitly states the goods or services that an entity promises to transfer to a customer. However, the performance obligations identified in a contract with a customer may not be limited to the goods or services that are explicitly stated in that contract. This is because a contract with a customer may also include promises that are implied by an entity's customary business practices, published policies or specific statements if, at the time of entering into the contract, those promises create a valid expectation of the customer that the entity will transfer a good or service to the customer.

Performance obligations do not include activities that an entity must undertake to fulfil a contract unless those activities transfer a good or service to a customer. For example, a services provider may need to perform various administrative tasks to set up a contract. The performance of those tasks does not transfer a service to the customer as the tasks are performed. Therefore, those setup activities are not a performance obligation.

with other readily available resources. A readily available resource is a good or service that is sold separately (by the entity or another entity) or a resource that the customer has already obtained from the entity (including goods or services that the entity will have already transferred to the customer under the contract) or from other transactions or events. Various factors may provide evidence that the customer can benefit from a good or service either on its own or in conjunction with other readily available resources. For example, the fact that the entity regularly sells a good or service separately would indicate that a customer can benefit from the good or service on its own or with other readily available resources.

29  Factors that indicate that an entity's promise to transfer a good or service to a customer is separately identifiable (in accordance with paragraph 27(b)) include, but are not limited to, the following:

 the entity does not provide a significant service of integrating the good or service with other goods or services promised in the contract into a bundle of goods or services that represent the combined output for which the customer has contracted. In other words, the entity is not using the good or service as an input to produce or deliver the combined output specified by the customer. the good or service does not significantly modify or customise another good or service promised in the contract.

the good or service is not highly dependent on, or highly interrelated with, other goods or services promised in the contract. For example, the fact that a customer could decide to not purchase the good or service without significantly affecting the other promised goods or services in the contract might indicate that the good or service is not highly dependent on, or highly interrelated with, those other promised goods or services.

If a promised good or service is not distinct, an entity shall combine that good or service with other promised goods or services until it identifies a bundle of goods or services that is distinct. In some cases, that would result in the entity accounting for all the goods or services promised in a contract as a single performance obligation.

Satisfaction of performance obligations

An entity shall recognise revenue when (or as) the entity satisfies a

performance obligation by transferring a promised good or service (ie an asset) to a customer. An asset is transferred when (or as) the customer obtains control of that asset.

For each performance obligation identified in accordance with paragraphs 22-30, an entity shall determine at contract inception whether it satisfies the performance obligation over time (in accordance with paragraphs 35-37) or satisfies the performance obligation at a point in time (in accordance with paragraph 38). If an entity does not satisfy a performance obligation over time, the performance obligation is satisfied at a point in time.

Goods and services are assets, even if only momentarily, when they are received and used (as in the case of many services). Control of an asset refers to the ability to direct the use of, and obtain substantially all of the remaining benefits from, the asset. Control includes the ability to prevent other entities from directing the use of, and obtaining the benefits from, an asset. The benefits of an asset are the potential cash flows (inflows or savings in outflows) that can be obtained

directly or indirectly in many ways, such as by:

ng the asset to produce goods or provide services (including public services);

 using the asset to enhance the value of other assets; using the asset to settle liabilities or reduce expenses; selling or exchanging the asset;  pledging the asset to secure a loan; and holding the asset.

When evaluating whether a customer obtains control of an asset, an entity shall consider any agreement to repurchase the asset (see paragraphs B64-B76).

Performance obligations satisfied over time

An entity transfers control of a good or service over time and, therefore, satisfies a performance obligation and recognises revenue over time, if one of the following criteria is met:

the customer simultaneously receives and consumes the benefits

provided by the entity's performance as the entity performs (see paragraphs B3-B4);

the entity's performance creates or enhances an asset (for example, work in progress) that the customer controls as the asset is created or enhanced (see paragraph B5); or

the entity's performance does not create an asset with an alternative use to the entity (see paragraph 36) and the entity has an enforceable right to payment for performance completed to date (see paragraph 37).

An asset created by an entity's performance does not have an alternative use to an entity if the entity is either restricted contractually from readily directing the asset for another use during the creation or enhancement of that asset or limited practically from readily directing the asset in its completed state for another use. The assessment of whether an asset has an alternative use to the entity is made at contract inception. After contract inception, an entity shall not update the assessment of the alternative use of an asset unless the parties to the contract approve a contract modification that substantively changes the performance obligation. Paragraphs B6-B8 provide guidance for assessing whether an asset has an alternative use to an entity.

An entity shall consider the terms of the contract, as well as any laws that apply to the contract, when evaluating whether it has an enforceable right to payment for performance completed to date in accordance with paragraph 35(c). The right to payment for performance completed to date does not need to be for a

fixed amount. However, at all times throughout the duration of the contract, the entity must be entitled to an amount that at least compensates the entity for performance completed to date if the contract is terminated by the customer or another party for reasons other than the entity's failure to perform as promised. Paragraphs B9-B13 provide guidance for assessing the existence and enforceability of a right to payment and whether an entity's right to payment would entitle the entity to be paid for its performance completed to date.

Performance obligations satisfied at a point in time

If a performance obligation is not satisfied over time in accordance with paragraphs 35-37, an entity satisfies the performance obligation at a point in time. To determine the point in time at which a customer obtains control of a promised asset and the entity satisfies a performance obligation, the entity shall consider the requirements for control in paragraphs 31-34. In addition, an entity shall consider indicators of the transfer of control, which include, but are

not limited to, the following:

 The entity has a present right to payment for the asset—if a customer is presently obliged to pay for an asset, then that may indicate that the customer has obtained the ability to direct the use of, and obtain substantially all of the remaining benefits from, the asset in exchange. The customer has legal title to the asset—legal title may indicate which party to a contract has the ability to direct the use of, and obtain substantially all of the remaining benefits from, an asset or to restrict the access of other entities to those benefits. Therefore, the transfer of legal title of an asset may indicate that the customer has obtained control of the asset. If an entity retains legal title solely as protection against the customer's failure to pay, those rights of the entity would not preclude the customer from obtaining control of an asset. The entity has transferred physical possession of the asset—the customer's physical possession of an asset may indicate that the customer has the ability to direct the use of, and obtain substantially all of the remaining benefits from, the asset or to restrict the access of other entities to those benefits. However, physical possession may not coincide with control of an asset. For example, in some repurchase agreements and in some consignment arrangements, a customer or consignee may have physical possession of an asset that the entity controls. Conversely, in some bill-and-hold arrangements, the entity may have physical possession of an asset that the customer controls. Paragraphs B64-B76, B77-B78 and B79-B82 provide guidance on accounting for repurchase agreements, consignment arrangements and bill-and-hold arrangements, respectively.

The customer has the significant risks and rewards of ownership of the asset—the transfer of the significant risks and rewards of ownership of an asset to the customer may indicate that the customer has obtained the ability to direct the use of, and obtain substantially all of the remaining benefits from, the asset. However, when evaluating the risks and rewards of ownership of a promised asset, an entity shall exclude any

risks that give rise to a separate performance obligation in addition to the performance obligation to transfer the asset. For example, an entity may have transferred control of an asset to a customer but not yet satisfied an additional performance obligation to provide maintenance services related to the transferred asset.

The customer has accepted the asset—the customer's acceptance of an asset may indicate that it has obtained the ability to direct the use of, and obtain substantially all of the remaining benefits from, the asset. To evaluate the effect of a contractual customer acceptance clause on when control of an asset is transferred, an entity shall consider the guidance in paragraphs B83-B86.

Measuring progress towards complete satisfaction of a

performance obligation

For each performance obligation satisfied over time in accordance with paragraphs 35-37, an entity shall recognise revenue over time by measuring the progress towards complete satisfaction of that performance obligation. The objective when measuring progress is to depict an entity's performance in transferring control of goods or services promised to a customer (ie the satisfaction of an entity's performance obligation).

An entity shall apply a single method of measuring progress for each performance obligation satisfied over time and the entity shall apply that method consistently to similar performance obligations and in similar circumstances. At the end of each reporting period, an entity shall remeasure its progress towards complete satisfaction of a performance obligation satisfied over time.

Methods for measuring progress

Appropriate methods of measuring progress include output methods and input methods. Paragraphs B14-B19 provide guidance for using output methods and input methods to measure an entity's progress towards complete satisfaction of

a performance obligation. In determining the appropriate method for

measuring progress, an entity shall consider the nature of the good or service that the entity promised to transfer to the customer.

When applying a method for measuring progress, an entity shall exclude from the measure of progress any goods or services for which the entity does not transfer control to a customer. Conversely, an entity shall include in the measure of progress any goods or services for which the entity does transfer control to a customer when satisfying that performance obligation.

As circumstances change over time, an entity shall update its measure of progress to reflect any changes in the outcome of the performance obligation. Such changes to an entity's measure of progress shall be accounted for as a change in accounting estimate in accordance with IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors.

Reasonable measures of progress

An entity shall recognise revenue for a performance obligation satisfied over time only if the entity can reasonably measure its progress towards complete satisfaction of the performance obligation. An entity would not be able to reasonably measure its progress towards complete satisfaction of a performance obligation if it lacks reliable information that would be required to apply an appropriate method of measuring progress.

In some circumstances (for example, in the early stages of a contract), an entity may not be able to reasonably measure the outcome of a performance obligation, but the entity expects to recover the costs incurred in satisfying the performance obligation. In those circumstances, the entity shall recognise revenue only to the extent of the costs incurred until such time that it can reasonably measure the outcome of the performance obligation.

Measurement

When (or as) a performance obligation is satisfied, an entity shall recognise as revenue the amount of the transaction price (which excludes estimates of variable consideration that are constrained in accordance with paragraphs 56-58) that is allocated to that performance obligation.

Determining the transaction price

An entity shall consider the terms of the contract and its customary business practices to determine the transaction price. The transaction price is the amount of consideration to which an entity expects to be entitled in exchange for transferring promised goods or services to a customer, excluding amounts collected on behalf of third parties (for example, some sales taxes). The consideration promised in a contract with a customer may include fixed amounts, variable amounts, or both.

The nature, timing and amount of consideration promised by a customer affect the estimate of the transaction price. When determining the transaction price, an entity shall consider the effects of all of the following:

variable consideration (see paragraphs 50-55 and 59);  constraining estimates of variable consideration (see paragraphs 56-58);  the existence of a significant financing component in the contract (see paragraphs 60-65); non-cash consideration (see paragraphs 66-69); and consideration payable to a customer (see paragraphs 70-72).

49    For the purpose of determining the transaction price, an entity shall assume

that the goods or services will be transferred to the customer as promised in accordance with the existing contract and that the contract will not be cancelled, renewed or modified

Variable consideration

If the consideration promised in a contract includes a variable amount, an entity shall estimate the amount of consideration to which the entity will be entitled in exchange for transferring the promised goods or services to a customer.

An amount of consideration can vary because of discounts, rebates, refunds, credits, price concessions, incentives, performance bonuses, penalties or other similar items. The promised consideration can also vary if an entity's entitlement to the consideration is contingent on the occurrence or non-occurrence of a future event. For example, an amount of consideration would be variable if either a product was sold with a right of return or a fixed amount is promised as a performance bonus on achievement of a specified milestone.

The variability relating to the consideration promised by a customer may be explicitly stated in the contract. In addition to the terms of the contract, the promised consideration is variable if either of the following circumstances

exists:

the customer has a valid expectation arising from an entity's customary business practices, published policies or specific statements that the entity will accept an amount of consideration that is less than the price stated in the contract. That is, it is expected that the entity will offer a price concession. Depending on the jurisdiction, industry or customer this offer may be referred to as a discount, rebate, refund or credit.

other facts and circumstances indicate that the entity's intention, when entering into the contract with the customer, is to offer a price concession to the customer.

53 An entity shall estimate an amount of variable consideration by using either of the following methods, depending on which method the entity expects to better predict the amount of consideration to which it will be entitled:

The expected value—the expected value is the sum of probability-weighted amounts in a range of possible consideration amounts. An expected value may be an appropriate estimate of the amount of variable consideration if an entity has a large number of contracts with similar characteristics.

The most likely amount—the most likely amount is the single most likely

amount in a range of possible consideration amounts (ie the single most likely outcome of the contract). The most likely amount may be an appropriate estimate of the amount of variable consideration if the contract has only two possible outcomes (for example, an entity either achieves a performance bonus or does not).

An entity shall apply one method consistently throughout the contract when estimating the effect of an uncertainty on an amount of variable consideration to which the entity will be entitled. In addition, an entity shall consider all the information (historical, current and forecast) that is reasonably available to the entity and shall identify a reasonable number of possible consideration amounts. The information that an entity uses to estimate the amount of

Refund liabilities

An entity shall recognise a refund liability if the entity receives consideration from a customer and expects to refund some or all of that consideration to the customer. A refund liability is measured at the amount of consideration received (or receivable) for which the entity does not expect to be entitled (ie amounts not included in the transaction price). The refund liability (and corresponding change in the transaction price and, therefore, the contract liability) shall be updated at the end of each reporting period for changes in circumstances. To account for a refund liability relating to a sale with a right of return, an entity shall apply the guidance in paragraphs B20-B27.

Constraining estimates of variable consideration

An entity shall include in the transaction price some or all of an amount of variable consideration estimated in accordance with paragraph 53 only to the extent that it is highly probable that a significant reversal in the amount of cumulative revenue recognised will not occur when the uncertainty associated with the variable consideration is subsequently resolved.

In assessing whether it is highly probable that a significant reversal in the amount of cumulative revenue recognised will not occur once the uncertainty related to the variable consideration is subsequently resolved, an entity shall consider both the likelihood and the magnitude of the revenue reversal. Factors that could increase the likelihood or the magnitude of a revenue reversal include, but are not limited to, any of the following:

the amount of consideration is highly susceptible to factors outside the

entity's influence. Those factors may include volatility in a market, the judgement or actions of third parties, weather conditions and a high risk of obsolescence of the promised good or service.

the uncertainty about the amount of consideration is not expected to be resolved for a long period of time.

the entity's experience (or other evidence) with similar types of contracts is limited, or that experience (or other evidence) has limited predictive value.

the entity has a practice of either offering a broad range of price concessions or changing the payment terms and conditions of similar contracts in similar circumstances.

the contract has a large number and broad range of possible

consideration amounts.

58  An entity shall apply paragraph B63 to account for consideration in the form of

a sales-based or usage-based royalty that is promised in exchange for a licence of intellectual property.

Reassessment of variable consideration

At the end of each reporting period, an entity shall update the estimated transaction price (including updating its assessment of whether an estimate of variable consideration is constrained) to represent faithfully the circumstances present at the end of the reporting period and the changes in circumstances during the reporting period. The entity shall account for changes in the transaction price in accordance with paragraphs 87-90.

The existence of a significant financing component in the contract

In determining the transaction price, an entity shall adjust the promised amount of consideration for the effects of the time value of money if the timing of payments agreed to by the parties to the contract (either explicitly or implicitly) provides the customer or the entity with a significant benefit of financing the transfer of goods or services to the customer. In those circumstances, the contract contains a significant financing component. A significant financing component may exist regardless of whether the promise of financing is explicitly stated in the contract or implied by the payment terms agreed to by the parties to the contract.

The objective when adjusting the promised amount of consideration for a significant financing component is for an entity to recognise revenue at an amount that reflects the price that a customer would have paid for the promised goods or services if the customer had paid cash for those goods or services when (or as) they transfer to the customer (ie the cash selling price). An entity shall consider all relevant facts and circumstances in assessing whether a contract contains a financing component and whether that financing component is significant to the contract, including both of the following:

(a)       the difference, if any, between the amount of promised consideration and the cash selling price of the promised goods or services; and

(b)       the combined effect of both of the following:

(i)        the expected length of time between when the entity transfers the promised goods or services to the customer and when the customer pays for those goods or services; and

(ii)       the prevailing interest rates in the relevant market.

62   Notwithstanding the assessment in paragraph 61, a contract with a customer would not have a significant financing component if any of the following factors exist:

the customer paid for the goods or services in advance and the timing of

the transfer of those goods or services is at the discretion of the customer.

a substantial amount of the consideration promised by the customer is

variable and the amount or timing of that consideration varies on the basis of the occurrence or non-occurrence of a future event that is not substantially within the control of the customer or the entity (for example, if the consideration is a sales-based royalty).the difference between the promised consideration and the cash selling price of the good or service (as described in paragraph 61) arises for reasons other than the provision of finance to either the customer or the entity, and the difference between those amounts is proportional to the reason for the difference. For example, the payment terms might provide the entity or the customer with protection from the other party failing to adequately complete some or all of its obligations under the contract

As a practical expedient, an entity need not adjust the promised amount of consideration for the effects of a significant financing component if the entity expects, at contract inception, that the period between when the entity transfers a promised good or service to a customer and when the customer pays for that good or service will be one year or less.

To meet the objective in paragraph 61 when adjusting the promised amount of consideration for a significant financing component, an entity shall use the discount rate that would be reflected in a separate financing transaction between the entity and its customer at contract inception. That rate would reflect the credit characteristics of the party receiving financing in the contract, as well as any collateral or security provided by the customer or the entity, including assets transferred in the contract. An entity may be able to determine that rate by identifying the rate that discounts the nominal amount of the promised consideration to the price that the customer would pay in cash for the goods or services when (or as) they transfer to the customer. After contract inception, an entity shall not update the discount rate for changes in interest rates or other circumstances (such as a change in the assessment of the customer's credit risk).

An entity shall present the effects of financing (interest revenue or interest expense) separately from revenue from contracts with customers in the statement of comprehensive income. Interest revenue or interest expense is recognised only to the extent that a contract asset (or receivable) or a contract liability is recognised in accounting for a contract with a customer.

Non-cash consideration

To determine the transaction price for contracts in which a customer promises consideration in a form other than cash, an entity shall measure the non-cash consideration (or promise of non-cash consideration) at fair value.

If an entity cannot reasonably estimate the fair value of the non-cash consideration, the entity shall measure the consideration indirectly by reference to the stand-alone selling price of the goods or services promised to the customer (or class of customer) in exchange for the consideration.

The fair value of the non-cash consideration may vary because of the form of the consideration (for example, a change in the price of a share to which an entity is entitled to receive from a customer). If the fair value of the non-cash consideration promised by a customer varies for reasons other than only the

صفحه     1     2      3      4      5