Revenue for Telecoms
2cdncba
2cdncba
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
124 | <strong>Revenue</strong> <strong>for</strong> <strong>Telecoms</strong> – Issues In-Depth<br />
| 6 Step 5: Recognize revenue when or as the entity satisfies a per<strong>for</strong>mance obligation<br />
Observations<br />
Determining which measure of progress to apply is not a free choice<br />
ASU 2014-09.BC159<br />
[IFRS 15.BC159]<br />
The new standard requires a telecom entity to select a method that is consistent<br />
with the objective of depicting its per<strong>for</strong>mance. A telecom entity there<strong>for</strong>e does<br />
not have a free choice of which method to apply to a given per<strong>for</strong>mance obligation<br />
– it needs to consider the nature of the good or service that it promised to transfer<br />
to the customer (see 3.4.2). Accordingly, judgment is required when identifying<br />
an appropriate method of measuring progress.<br />
Most telecom network services will be recognized using an output<br />
measure<br />
Output measures such as minutes, texts, amount of data consumed or time<br />
elapsed will usually prove to be appropriate measures of progress <strong>for</strong> telecom<br />
network services. Telecom entities need to consider carefully the nature of<br />
the promises in the contract – e.g. those promises made in prepaid contracts<br />
or contracts with rollover minutes. When the billing to the customer does not<br />
directly correspond to the telecom entity’s per<strong>for</strong>mance in these types of plans,<br />
the telecom entity may need to adjust any contract assets, contract liabilities or<br />
accounts receivable related to the contract.<br />
Some telecom network services may be recognized as they are billed<br />
606-10-55-18<br />
[IFRS 15.B16]<br />
Telecom services billings are often based on output measures, as described<br />
above. However, as a practical expedient, a telecom entity may recognize<br />
revenue using the amount that it has the right to invoice, if this amount directly<br />
corresponds with the value that is transferred to the customer. The amount that<br />
the telecom entity has the right to invoice does not need to be based on a fixed<br />
amount per unit <strong>for</strong> this practical expedient to be applied.<br />
If a contract includes fixed fees in addition to per-unit invoicing, substantive<br />
contractual minimums or payments to the customer such as rebates, discounts<br />
or signing bonuses, then the use of the practical expedient may be precluded<br />
because the invoiced amounts do not correspond to the value that the customer<br />
receives. Furthermore, to apply the practical expedient to a contract, all goods<br />
and services in the contract will need to qualify.<br />
When the practical expedient is used, the telecom entity is not required to<br />
disclose the remaining transaction price to be received under the contract.<br />
See 12.1.3 in Issues In-Depth, Edition 2016 <strong>for</strong> further details on disclosures<br />
required by the new revenue standard.<br />
Home<br />
© 2016 KPMG LLP, a Delaware limited liability partnership and the US member firm of the KPMG network of<br />
independent member firms affiliated with KPMG International Cooperative, a Swiss entity. All rights reserved.<br />
© 2016 KPMG IFRG Limited, a UK company, limited by guarantee. All rights reserved.