Revenue Recognition Steps Under PFRS 15
Revenue Recognition Steps Under PFRS 15
According to PFRS 15, revenue from a performance obligation that is satisfied over time is recognized over time as the entity progresses towards the complete satisfaction of the obligation .
Under PFRS 15, a contract with a customer is eligible for revenue recognition if both contracting parties acknowledge, whether explicitly or implicitly, the rights and obligations created under the contract .
The key steps for revenue recognition under PFRS 15 are: 1) Identify the performance obligation in the contract, 2) Recognize revenue when (or as) the entity satisfies a performance obligation, 3) Determine the transaction price, 4) Allocate the transaction price to the performance obligations in the contract. The correct sequence is IV, I, III, V, II .
Under PFRS 15, the transaction price is allocated to each performance obligation identified in a contract based on the relative stand-alone prices of the distinct goods or services promised to be transferred .
PFRS 15 requires that when goods or services are bundled, each component must be evaluated for distinctness. If distinct, revenue for each component is recognized separately based on its stand-alone selling price, impacting both the timing and pattern of revenue recognition within bundled arrangements .
According to PFRS 15, a good or service is considered distinct if: 1) The customer can benefit from the good or service either on its own or together with other resources that are readily available to the customer, and 2) The promise to transfer the good or service is separately identifiable from other promises in the contract .
A company must demonstrate that each promised good or service in the contract is distinct, meaning the customer can benefit from it on its own or with other readily available resources, and that it is separable from other promises in the contract .
Under PFRS 15, a performance obligation that can be accounted for separately includes: 1) A promise to transfer a distinct good or service, 2) A promise to transfer a distinct bundle of goods or services, 3) A promise to transfer a series of distinct goods or services that are substantially the same and have the same pattern of transfer. Additionally, a promise implied by business practices that creates a valid expectation can also be considered .
PFRS 15 acknowledges implicit promises as performance obligations that can arise from customary business practices. If a contract creates a valid expectation on the customer's part that an entity will satisfy a promise—even if not explicitly stated—it must be considered when recognizing revenue .
It might be incorrect to not recognize revenue upon partial delivery of goods because, under PFRS 15, revenue is recognized when (or as) performance obligations are satisfied. If the goods that are delivered first are deemed distinct and independently beneficial to the customer, revenue associated with those goods should be recognized at the time of delivery, subject to the contract's terms and conditions .