This site uses cookies to provide you with a more responsive and personalised service. By using this site you agree to our use of cookies. Please read our cookie notice for more information on the cookies we use and how to delete or block them.
The full functionality of our site is not supported on your browser version, or you may have 'compatibility mode' selected. Please turn off compatibility mode, upgrade your browser to at least Internet Explorer 9, or try using another browser such as Google Chrome or Mozilla Firefox.

Heads Up — ASC 606 is here — How do your revenue disclosures stack up?

Published on: Jul 11, 2018

Download PDF
Volume 25, Issue 9

by Kaycee Dolan, Eric Knachel, and Rob Moynihan, Deloitte & Touche LLP

Introduction

Calendar-year-end public business entities adopted the FASB’s new revenue standard (ASC 6061) in the first quarter of 2018.2 While some companies made wholesale changes to their financial statements, the effect of the new requirements was less significant for others. However, all entities were affected by the standard’s new and modified quantitative and qualitative disclosure guidance, which significantly increased the amount of information disclosed about revenue activities and related transactions.

This Heads Up provides insight into our review of the disclosures in the public filings of a sample of companies that adopted the standard as of the first quarter of 2018. Entities may benefit from evaluating the disclosure trends we have observed as a result of this review. For a comprehensive discussion of the new revenue standard, see Deloitte’s A Roadmap to Applying the New Revenue Recognition Standard (the “Revenue Roadmap”).

Key Takeaways

Key Takeaways

  • From a big-picture perspective, we observed that in many instances, the revenue disclosures were at least three times as long as the prior-year disclosures.
  • Most entities in our sample (over 85 percent) elected to adopt the new revenue standard by using the modified retrospective approach.
  • The new revenue standard’s requirement to provide more comprehensive disclosures is likely to significantly affect an entity’s financial statements regardless of the standard’s effect on recognition patterns.
  • We observed diversity in the type and amount of information that entities disclosed. While some companies provided robust and thorough disclosures, particularly on the nature of performance obligations and on the significant judgments and estimates involved, others did not.
  • Many entities have chosen to add a separate and specific revenue footnote that contains the required disclosures.
  • When providing disaggregated revenue disclosures, the majority of entities in our sample used two or fewer categories. The most commonly selected categories presented in tabular disclosure were (1) product lines and (2) geographical regions.
  • Most entities in our sample elected multiple practical expedients related to their ASC 606 disclosures, most commonly those related to remaining performance obligations.
  • We expect entities to continue to refine the information they disclose as (1) they review peer companies’ disclosures, (2) accounting standard setters clarify guidance, and (3) regulators continue to issue comments.

View the rest of the Heads Up.

____________________

1 FASB Accounting Standards Codification Topic 606, Revenue From Contracts With Customers.

2 Public business entities reporting under U.S. GAAP are required to adopt the new revenue standard for annual reporting periods (including interim reporting periods within those annual periods) beginning after December 15, 2017. Early adoption was permitted as of reporting periods (including interim periods) beginning after December 15, 2016. For nonpublic entities, the new revenue standard is effective for annual periods beginning after December 15, 2018, and early adoption is also permitted.

Download

Correction list for hyphenation

These words serve as exceptions. Once entered, they are only hyphenated at the specified hyphenation points. Each word should be on a separate line.