OUR THOUGHTS ON:

Final Revenue Recognition Standards Issued

Audit

By Donald Applegarth

PRIMARY CONTACT: Donald Applegarth CPA (Pittsburgh)

The FASB has issued Accounting Standards Update (ASU) No. 2014-09, Revenue from Contracts with Customers: Topic 606, and the IASB has issued IFRS 15, Revenue from Contracts with Customers. The issuance of these documents completes the joint effort by the FASB and the IASB to improve financial reporting by creating common revenue recognition guidance for U.S. GAAP and IFRS.

This ASU affects any entity that either enters into contracts with customers to transfer goods or services or enters into contracts for the transfer of nonfinancial assets unless those contracts are within the scope of other standards (e.g., insurance contracts or lease contracts). This ASU will supersede the revenue recognition requirements in Topic 605, Revenue Recognition, and most industry-specific guidance. This ASU also supersedes some cost guidance included in Subtopic 605-35, Revenue Recognition—Construction-Type and Production-Type Contracts. In addition, the existing requirements for the recognition of a gain or loss on the transfer of nonfinancial assets that are not in a contract with a customer (e.g., assets within the scope of Topic 360, Property, Plant, and Equipment, and intangible assets within the scope of Topic 350, Intangibles—Goodwill and Other) are amended to be consistent with the guidance on recognition and measurement (including the constraint on revenue) in this ASU.

The core principle of the guidance is that an entity should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. To achieve that core principle, an entity should apply the following steps:

  • Step 1: Identify the contract(s) with a customer.
  • Step 2: Identify the performance obligations in the contract.
  • Step 3: Determine the transaction price.
  • Step 4: Allocate the transaction price to the performance obligations in the contract.
  • Step 5: Recognize revenue when (or as) the entity satisfies a performance obligation.

For a public entity, the amendments in this ASU are effective for annual reporting periods beginning after December 15, 2016, including interim periods within that reporting period. Early application is not permitted.

For all other entities (nonpublic entities), the amendments in this ASU are effective for annual reporting periods beginning after December 15, 2017, and interim periods within annual periods beginning after December 15, 2018. A nonpublic entity may elect to apply this guidance earlier, however, only as of the following:

  • An annual reporting period beginning after December 15, 2016, including interim periods within that reporting period (public entity effective date);
  • An annual reporting period beginning after December 15, 2016, and interim periods within annual periods beginning after December 15, 2017; or
  • An annual reporting period beginning after December 15, 2017, including interim periods within that reporting period.

An entity should apply the amendments in this ASU using one of the following two methods:

1.  Retrospectively to each prior reporting period presented and the entity may elect any of the following practical expedients:

  • For completed contracts, an entity need not restate contracts that begin and end within the same annual reporting period.
  • For completed contracts that have variable consideration, an entity may use the transaction price at the date the contract was completed rather than estimating variable consideration amounts in the comparative reporting periods.
  • For all reporting periods presented before the date of initial application, an entity need not disclose the amount of the transaction price allocated to remaining performance obligations and an explanation of when the entity expects to recognize that amount as revenue.

2. Retrospectively with the cumulative effect of initially applying this ASU recognized at the date of initial application. If an entity elects this transition method it also should provide the additional disclosures in reporting periods that include the date of initial application of:

  • The amount by which each financial statement line item is affected in the current reporting period by the application of this ASU as compared to the guidance that was in effect before the change.
  • An explanation of the reasons for significant changes.

© 2014 Schneider Downs. All rights-reserved. All content on this site is property of Schneider Downs unless otherwise noted and should not be used without written permission.

You’ve heard our thoughts… We’d like to hear yours

The Schneider Downs Our Thoughts On blog exists to create a dialogue on issues that are important to organizations and individuals. While we enjoy sharing our ideas and insights, we’re especially interested in what you may have to say. If you have a question or a comment about this article – or any article from the Our Thoughts On blog – we hope you’ll share it with us. After all, a dialogue is an exchange of ideas, and we’d like to hear from you. Email us at contactSD@schneiderdowns.com.

Material discussed is meant for informational purposes only, and it is not to be construed as investment, tax, or legal advice. Please note that individual situations can vary. Therefore, this information should be relied upon when coordinated with individual professional advice.

© 2018 Schneider Downs. All rights-reserved. All content on this site is property of Schneider Downs unless otherwise noted and should not be used without written permission.

comments