Are you ready to implement the FASB/IASB New Revenue Recognition Standard? With just a handful of months to go – The countdown is on! SECI is conducting training workshops throughout the U.S. to prepare filers for the changes and arm them with the tools for implementation. Workshop leaders use interactive lecture, examples and case studies to impart solid knowledge of the provisions of the FASB’s and IASB’s new revenue recognition standard and build an understanding of how the new standard changes revenue recognition accounting and also how it affects the related estimates and judgements. Upcoming workshops include August 24-25 in Grapevine, September 11-12 in Las Vegas and December 13-14 in New York City.
By: George M. Wilson & Carol A. Stacey
One of the “golden rules” of MD&A we discuss in our workshops is “no surprise stock drops”. (Thanks to Brink Dickerson of Troutman Sanders for the rules!) Actually, it is OK if management is surprised with a stock drop. However, it can be problematic if management previously knew of some issue that, when disclosed, causes a surprise stock drop for investors.
The classic start to a known trend enforcement case is a company announcement that results in a stock price drop. On February 26, 2014, UTi, a logistics company, filed an 8-K with news of a severe liquidity problem. UTi’s shares fell to $10.74, a decline of nearly 30% from the prior day’s close of $15.26.
The reason this is an SEC reporting issue is this paragraph from the MD&A guidance in Regulation S-K Item 303 paragraph (a)(3)(ii):
Describe any known trends or uncertainties that have had or that the registrant reasonably expects will have a material favorable or unfavorable impact on net sales or revenues or income from continuing operations. If the registrant knows of events that will cause a material change in the relationship between costs and revenues (such as known future increases in costs of labor or materials or price increases or inventory adjustments), the change in the relationship shall be disclosed. (emphasis added)
If management knows of some sort of uncertainty that could result in a material impact if it comes to fruition, they must evaluate whether they “reasonably expect” this to happen. If they do “reasonably expect” this to happen then it should be disclosed in MD&A.
When there is a surprise stock drop like the one experienced by UTi, the questions the SEC Enforcement Division will ask, to borrow from another context, are “what did management know about the problem” and “when did they know it?”
Enforcement Release, AAER 3877 revealed that the genesis of UTi’s liquidity problem was an issue in the implementation of a new IT system that created billing problems. And, it was clear from the facts, including an internal PowerPoint presentation, that management knew they had a problem well before they filed the 8-K.
However, in their 10-Q for their third quarter ended October 31, 2013, which was filed in December of 2013, UTi did not disclose the liquidity problem. In fact, they said:
Our primary sources of liquidity include cash generated from operating activities, which is subject to seasonal fluctuations, particularly in our Freight Forwarding segment, and available funds under our various credit facilities. We typically experience increased activity associated with our peak season, generally during the second and third fiscal quarters, requiring significant disbursements on behalf of clients. During the second quarter and the first half of the third quarter, this seasonal growth in client receivables tends to consume available cash. Historically, the latter portion of the third quarter and the fourth quarter tend to generate cash recovery as cash collections usually exceed client cash disbursements.
They also made no mention of the implementation problems with their new IT system. They actually said:
Freight Forward Operating System. On September 1, 2013, we deployed our global freight forwarding operating system in the United States. As of that date, based on a variety of factors, including but not limited to operational acceptance testing and other operational milestones having been achieved, we considered it ready for its intended use. Amortization expense with respect to the system began effective September 2013, and accordingly, we recorded amortization expense related to the new application of approximately $3.3 million during the third quarter ended October 31, 2013.
Hence the surprise when the 8-K disclosed the problems. Both the CEO and CFO are also named in the Enforcement Release and paid penalties.
As mentioned above, the probability standard for disclosure is “reasonably expects”. More about this complex probability assessment in our next post!
As always, your thoughts and comments are welcome!
The Financial Reporting Regulatory landscape is chock full of recent updates and new regulations, chief among them is the new FASB Revenue Recognition Standard and revised Lease Accounting. Most surveys agree that filers are well behind schedule in implementing the changes needed to comply. Practitioners at small and mid-sized companies will receive the essential information and advice needed to get up to speed by attending SEC Reporting & FASB Forum live program September 14-15 in Las Vegas.
How do the latest SEC, EITF, PCAOB and FASB updates affect your reporting? Attend FASB, SEC and PCAOB Update for SEC Reporting Professionals Workshop being held August 23rd in Grapevine, Tx. Get up to date in-depth information on all the latest developments and practical tips on applying existing financial reporting requirements, including pushdown accounting, debt issuance costs and commitment fees, discontinued operations and dispositions, segment reporting and goodwill impairment.
By: George M. Wilson & Carol A. Stacey
What do United Health Group, Alphabet, and Ford have in common? What if we also included Raytheon? That’s right, all these companies have early adopted the FASB’s new revenue recognition standard! Microsoft and Workday have also indicated that they plan to early adopt. Microsoft has indicated they will adopt as of July 1, 2017 and file their first 10-Q under the new method for the quarter-ended September 30, 2017. Workday has said that they will early adopt as of February 1, 2017 and hence their first 10-Q under the new method will be for the quarter-ended April 30, 2017, which should be filed soon. Here is a summary of some of the early adopters:
Early adopters who have filed with ASU 2014-09:
Alphabet January 1, 2017 Modified Retrospective
Ford January 1, 2017 Modified Retrospective
United Health Group January 1, 2017 Modified Retrospective
First Solar January 1, 2017 Full Retrospective
General Dynamics January 1, 2017 Full Retrospective
Raytheon January 1, 2017 Full Retrospective
Planned adoptions – no filing yet:
Workday February 1, 2017 Full Retrospective
Microsoft July 1, 2017 Full Retrospective
(If you know of any other companies that have early adopted it would be great if you could mention them in a comment on this post or email Carol or George – Thanks!)
As is always the case with a major new standard, it is helpful to learn from the experience of folks who have gone past the frontier to the leading, and hopefully not the bleeding, edge! Here are a few highlights and links to Form 10-Q’s with the new standard adopted.
From Alphabet’s Form 10-Q for the first quarter of 2017:
In May 2014, the FASB issued Accounting Standards Update No. 2014-09 (Topic 606) “Revenue from Contracts with Customers.” Topic 606 supersedes the revenue recognition requirements in Topic 605 “Revenue Recognition” (Topic 605), and requires entities to recognize revenue when control of the promised goods or services is transferred to customers at an amount that reflects the consideration to which the entity expects to be entitled to in exchange for those goods or services. We adopted Topic 606 as of January 1, 2017 using the modified retrospective transition method. See Note 2 for further details.
Alphabet’s disclosures, including how they decided to disaggregate revenues, make for interesting reading!
From Fords Form 10-Q for the quarter ended March 31, 2017:
On January 1, 2017, we adopted the new accounting standard ASC 606, Revenue from Contracts with Customers and all the related amendments (“new revenue standard”) to all contracts using the modified retrospective method. We recognized the cumulative effect of initially applying the new revenue standard as an adjustment to the opening balance of retained earnings. The comparative information has not been restated and continues to be reported under the accounting standards in effect for those periods. We expect the impact of the adoption of the new standard to be immaterial to our net income on an ongoing basis.
You can read about the impact of the change on revenues and review Fords Note 3 – Revenue to see how they decided to present the new disclosure for disaggregated revenues.
Raytheon, who had previously announced they would early adopt, did so in their Form 10-Q for the First Quarter of 2017, which you can find here.
Note 2: Accounting Standards
In May 2014, the Financial Accounting Standards Board (FASB) issued ASU 2014-09, Revenue from Contracts with Customers (Topic 606), which replaces numerous requirements in U.S. GAAP, including industry-specific requirements, and provides companies with a single revenue recognition model for recognizing revenue from contracts with customers. The core principle of the new standard is that a company should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the company expects to be entitled in exchange for those goods or services. The two permitted transition methods under the new standard are the full retrospective method, in which case the standard would be applied to each prior reporting period presented and the cumulative effect of applying the standard would be recognized at the earliest period shown, or the modified retrospective method, in which case the cumulative effect of applying the standard would be recognized at the date of initial application. In July 2015, the FASB approved the deferral of the new standard’s effective date by one year. The new standard is effective for annual reporting periods beginning after December 15, 2017. The FASB permits companies to adopt the new standard early, but not before the original effective date of annual reporting periods beginning after December 15, 2016. Effective January 1, 2017, we elected to early adopt the requirements of Topic 606 using the full retrospective method.
Raytheon’s disclosures for the full retrospective adoption, and the volume of their disclosures overall because of their government contracting business, are great reading for anyone facing similar issues.
From United Health Groups Form 10-Q for the quarter ended March 31, 2017:
In May 2014, the FASB issued ASU No. 2014-09, “Revenue from Contracts with Customers (Topic 606)” as modified by subsequently issued ASUs 2015-14, 2016-08, 2016-10, 2016-12 and 2016-20 (collectively ASU 2014-09). ASU 2014-09 superseded existing revenue recognition standards with a single model unless those contracts are within the scope of other standards (e.g., an insurance entity’s insurance contracts). The revenue recognition principle in ASU 2014-09 is that an entity should recognize revenue to depict the transfer of 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.
The Company early adopted the new standard effective January 1, 2017, as allowed, using the modified retrospective approach. A significant majority of the Company’s revenues are not subject to the new guidance. The adoption of ASU 2014-09 did not have a material impact on the Company’s consolidated financial position, results of operations, equity or cash flows as of the adoption date or for the three months ended March 31, 2017. The Company has included the disclosures required by ASU 2014-09 above.
General Dynamics early adopted with the full retrospective method. From their Form 10-Q for quarter one 2017:
The majority of our revenue is derived from long-term contracts and programs that can span several years. We account for revenue in accordance with ASC Topic 606, Revenue from Contracts with Customers, which we adopted on January 1, 2017, using the retrospective method. See Note Q for further discussion of the adoption, including the impact on our 2016 financial statements.
First Solar also early adopted and used the full retrospective transition method. Here is an excerpt from their Form 10-Q for quarter one of 2017:
In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers (Topic 606), to clarify the principles of recognizing revenue and create common revenue recognition guidance between U.S. GAAP and International Financial Reporting Standards. Under ASU 2014-09, revenue is recognized when a customer obtains control of promised goods or services and is recognized at an amount that reflects the consideration expected to be received in exchange for such goods or services. In addition, ASU 2014-09 requires disclosure of the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers.
We adopted ASU 2014-09 in the first quarter of 2017 using the full retrospective method. This adoption primarily affected our systems business sales arrangements previously accounted for under ASC 360-20, which had required us to evaluate whether such arrangements had any forms of continuing involvement that may have affected the revenue or profit recognition of the transactions, including arrangements with prohibited forms of continuing involvement. When such forms of continuing involvement were present, we reduced the potential profit on the applicable project sale by our maximum exposure to loss.
Microsoft and Workday will also be filing with the new standard this year, so watch for their first 10-Q’s this year. Here is Microsoft’s SAB 74 disclosure (not included here is the section in which they say it is their intent to also early adopt the new lease standard as of July 1, 2017), followed by Workday’s SAB 74 disclosure for revenue recognition.
Revenue from Contracts with Customers
In May 2014, the FASB issued a new standard related to revenue recognition. Under the standard, revenue is recognized when a customer obtains control of promised goods or services in an amount that reflects the consideration the entity expects to receive in exchange for those goods or services. In addition, the standard requires disclosure of the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers.
The guidance permits two methods of adoption: retrospectively to each prior reporting period presented (full retrospective method), or retrospectively with the cumulative effect of initially applying the guidance recognized at the date of initial application (modified retrospective method). We plan to adopt the standard using the full retrospective method to restate each prior reporting period presented.
The standard will be effective for us beginning July 1, 2018, with early adoption permitted as of the original effective date of July 1, 2017. We plan to adopt the standard effective July 1, 2017. While our ability to early adopt using the full retrospective method depends on system readiness, including software procured from third-party providers, and completing our analysis of information necessary to restate prior period consolidated financial statements, we remain on schedule and have implemented key system functionality to enable the preparation of restated financial information.
We have reached conclusions on key accounting assessments related to the standard. However, we are finalizing our assessment and quantifying the impacts related to accounting for costs incurred to obtain a contract based on guidance issued by the FASB Transition Resource Group as part of their November 2016 meeting. We will continue to monitor and assess the impact of any changes to the standard and interpretations as they become available.
The most significant impact of the standard relates to our accounting for software license revenue. Specifically, under the standard we expect to recognize Windows 10 revenue predominantly at the time of billing rather than ratably over the life of the related device. We expect to recognize license revenue at the time of contract execution rather than over the subscription period from certain multi-year commercial software subscriptions that include both software licenses and Software Assurance. Due to the complexity of certain of our commercial license subscription contracts, the actual revenue recognition treatment required under the standard will depend on contract-specific terms and in some instances may vary from recognition at the time of billing.
We expect revenue recognition related to our hardware, cloud offerings including Office 365, LinkedIn, and professional services to remain substantially unchanged.
We are nearing completion of retrospectively adjusting financial information for fiscal year 2016 and are progressing as planned for fiscal year 2017. We estimate our revenue would have been approximately $6 billion higher in fiscal year 2016 under the standard primarily due to the net change in Windows 10 revenue recognition.
We have closely assessed the new standard and monitored FASB activity, including the interpretations by the FASB Transition Resource Group for Revenue Recognition, throughout fiscal 2017. In the fourth quarter of fiscal 2017, we finalized our assessment of the new standard, including completing our contract reviews and our evaluation of the incremental costs of obtaining a contract. Based on our assessment, we decided to early adopt the requirements of the new standard in the first quarter of fiscal 2018, utilizing the full retrospective method of transition.
The impact of adopting the new standard on our fiscal 2017 and fiscal 2016 revenues is not material. The primary impact of adopting the new standard relates to the deferral of incremental commission costs of obtaining subscription contracts. Under Topic 605, we deferred only direct and incremental commission costs to obtain a contract and amortized those costs over the term of the related subscription contract, which was generally three years. Under the new standard, we defer all incremental commission costs to obtain the contract. We amortize these costs over a period of benefit that we have determined to be five years.
As always, your thoughts and comments are welcome! And if you hear of or know of any other early adopters please put that in a comment to this post, or email George or Carol
SEC Reporting and Practice Skills Workshop for
Hone your SEC reporting skills at this interactive Workshop designed specifically for lawyers. Attendees will build the foundational knowledge and practical experience necessary to prepare and review the SEC’s periodic and current reporting forms. Learn the structure and details of Forms 10-K, 10-Q, and 8-K, with particular emphasis on challenging and complex disclosures and how to effectively use the SEC’s guidance. This definitive course is perfect for beginners or as a refresher for experienced SEC reporting professionals.
Key Topics Will Include:
- Key disclosures and issues in Forms 10-K, 10-Q, and 8-K, and the proxy statement
- All-important sources of SEC reporting rules and guidance, including Regulations S-X and S-K, and the Staff Accounting and Staff Legal Bulletins
- How to communicate with the public within the constraints of the SEC’s rules
- How to ensure compliance by executives with Section 16 reporting
- Latest developments, including the Dodd-Frank pay ratio and pay vs. performance disclosures
What You Should Bring:
Bring your company’s or a client’s most recent public disclosures: 10-K, 10-Q, recent 8-K and one or more press releases. If you work with a private company, filings from a company in the same industry are a reasonable alternative
Dates & Locations:
June 29-30: New York City
October 2-3: Dallas/Grapevine
October 26-27: Chicago
The complicated world of SEC reporting has now gotten even more challenging! Be sure you are prepared to comply with the recently enacted changes and have a plan in place to deal with the SEC staff “hot buttons”. Attend SECI’s live workshop SEC Reporting Skills Workshop 2017 being held April 24-25 in Chicago, May 8-9 in McLean, Va., May 16-17 in Dallas and May 24-25 in San Francisco with additional dates and locations listed on the SECI website.
By George M. Wilson & Carol A. Stacey
Foreign Private Issuers (FPI’s) who file using IFRS have been in a conundrum about XBRL because there was no usable IFRS taxonomy. The SEC excepted these FPI’s from XBRL until an appropriate taxonomy was developed.
The SEC indicated that FPI’s who use IFRS may begin to submit XBRL financial statements immediately, and that they MUST submit XBRL financial statements for periods ending on or after December 15, 2017.
As always, your thoughts and comments are welcome!
Are you prepared to effectively deal with current and evolving SEC reporting issues, particularly SAB 74 disclosures and recently issued accounting standards in your first quarterly report on Form 10-Q this year? Attend our April 28th One Hour Video Briefing, First Quarter 2017 Form 10-Q Hot Topics as our expert faculty review the key issues to address in your Form 10-Q quarterly reporting.
By: George M. Wilson & Carol A. Stacey
Good accounting requires good communication. Many times information that is well-removed from the financial reporting and accounting functions has impacts on the financial statements or other parts of the SEC reporting process, especially MD&A. The Sarbanes Oxley Act built on the internal accounting controls guidance in section 13(b) of the FCPA Act in expanding the evaluation, audit and reporting requirements for internal control over financial reporting, or ICFR, and creating the concept of disclosure controls and procedures, or DCP.
A recent enforcement action brings home, at this important year-end time, the importance of effective disclosure controls throughout the company, with perhaps redundant controls that search beyond traditional financial reporting functions for issues that may impact the financial statements or require disclosure in other parts of a periodic report. It reinforces the idea that responsibility for disclosure is a company-wide obligation, and that companies need to build reliable infrastructures to ensure that investors receive all of the information they are supposed to receive.
ICFR and its related requirements have been part of the reporting process for decades. ICFR is formally defined in Exchange Act Rule 13(a)-15 as:
a process designed by, or under the supervision of, the issuer’s principal executive and principal financial officers, or persons performing similar functions, and effected by the issuer’s board of directors, management and other personnel, to provide reasonable assurance regarding the reliability of financial reporting and the preparation of financial statements for external purposes in accordance with generally accepted accounting principles and includes those policies and procedures that:
(1) Pertain to the maintenance of records that in reasonable detail accurately and fairly reflect the transactions and dispositions of the assets of the issuer;
(2) Provide reasonable assurance that transactions are recorded as necessary to permit preparation of financial statements in accordance with generally accepted accounting principles, and that receipts and expenditures of the issuer are being made only in accordance with authorizations of management and directors of the issuer; and
(3) Provide reasonable assurance regarding prevention or timely detection of unauthorized acquisition, use or disposition of the issuer’s assets that could have a material effect on the financial statements.
ICFR is all about the financial statements and that of course includes all of the relevant disclosures in the footnotes to the financial statements.
Here is how SOX expanded this process and formally defined disclosure controls in Exchange Act Rule 13(a)-15:
For purposes of this section, the term disclosure controls and procedures means controls and other procedures of an issuer that are designed to ensure that information required to be disclosed by the issuer in the reports that it files or submits under the Act (15 U.S.C. 78a et seq.) is recorded, processed, summarized and reported, within the time periods specified in the Commission’s rules and forms. Disclosure controls and procedures include, without limitation, controls and procedures designed to ensure that information required to be disclosed by an issuer in the reports that it files or submits under the Act is accumulated and communicated to the issuer’s management, including its principal executive and principal financial officers, or persons performing similar functions, as appropriate to allow timely decisions regarding required disclosure.
What is clear in this definition is that DCP relates to the entire report, not just the financial statements. And, both ICFR and DCP are relevant to the financial statements.
The terms “accumulate and communicate” are particularly relevant for this case. DCP clearly applies to the concept of a known trend in MD&A, which may not be relevant to the financial statements. It also applies to information that may be relevant to accounting for contingencies, even when that information is in an operational area.
In the enforcement case mentioned above the company paid “a $1 million penalty to settle charges that deficient internal accounting controls prevented the company from properly assessing the potential impact on its financial statements of a defective ignition switch found in some vehicles.” Further,
“[t]he SEC’s order finds that the company’s internal investigation involving the defective ignition switch wasn’t brought to the attention of its accountants until November 2013 even though other (company) personnel understood in the spring of 2012 that there was a safety issue at hand. Therefore, during at least an 18-month period, accountants at the (company) did not properly evaluate the likelihood of a recall occurring or the potential losses resulting from a recall of cars with the defective ignition switch.
This case clearly addressed accounting for contingencies and the related GAAP disclosures. In other situations there may not be a contingency disclosure, but there could be a known trend in MD&A. Both are relevant issues as we work through year-end. What this all builds to is that the disclosure process, including both ICFR and DCP, has to reach beyond the information required for financial statement reporting.
It is all about communication! And this might be a good time to communicate this issue to your disclosure committee and all the parts of your organization.
As always, your thoughts and comments are welcome!