Tag Archives: form 10-k

Learn About Recent Whistleblower Developments

Hot Topic, , , , , , , , , , ,

By: George M. Wilson & Carol A. Stacey

 

We have done several posts about whistleblowing and the related SOX and Dodd-Frank whistle blower regimens. It is hard to overstate the importance of whistleblowers in the SEC’s enforcement efforts.
On April 25, 2017, the SEC announced a $4 million payout to a whistleblower who provided industry-specific experience and expertise to the staff as they conducted their investigation. In that release they also announced that whistleblower payouts now total approximately $153 million!
Keeping abreast of whistleblowing developments is an important part of governance and compliance.   To help in this process we are offering our Corporate Whistleblowing program on June 28. This program will provide in-depth perspectives on recent regulatory and legal developments, including:

  • What direction the federal whistleblower protection programs will likely take under the new administration
  • What to expect in case law and regulatory enforcement developments in the coming year
  • Best practices in responding to whistleblower reports
  • Key ethical considerations in conducting internal investigations of issues raised by whistleblowers.

 

As always, your thoughts and comments are welcome!

Master SEC Reporting and Prepare to Tackle New Challenges

SEC Hot Topic, , , , , , , , , , , , , , , , , , ,

 

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.

http://www.pli.edu/Content/SEC_Reporting_Skills_Workshop_2017/_/N-1z10od0Z4k?ID=290559

XBRL for Foreign Private Issuers Using IFRS

Hot Topic, , , , , , , , , , , , , ,

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.

A usable IFRS XBRL taxonomy was formally announced by the SEC on March 1, 2017. The announcement includes a link to the IFRS XBRL Taxonomy that FPI’s must use.

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!

First Quarter 2017 Form 10-Q Hot Topics – SAB 74 and Beyond!

Hot Topic, , , , , , , , , , , , , , ,

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.

http://www.pli.edu/Content/Seminar/First_Quarter_2017_Form_10_Q_Hot_Topics_SAB/_/N-4kZ1z109q6?No=25&Ns=sort_date%7c0&ID=312741

Revenue Recognition – Raytheon Sets the Pace!

Hot Topic, , , , , , , , , ,

By: George M. Wilson & Carol A. Stacey

 

Reed Wilson, our Form 10-K In-Depth Workshop leader, closely follows reporting by major companies. He found that Raytheon, in its fourth-quarter earnings release, announced it has adopted the new revenue recognition standard as of January 1, 2017, a full year before the required adoption date. Raytheon also elected the full retrospective adoption method. (Nice catch Reed!) You can find the earnings release here.

Here is an excerpt from the earnings release:

Effective January 1, 2017, the Company adopted the new revenue recognition standard utilizing the full retrospective transition method. Under this method, the standard was applied to each prior reporting period presented and the cumulative effect of applying the standard was recognized at the earliest period shown. The impact of adopting the new standard on the Company’s 2015 and 2016 net sales and operating income was not material. The 2016 net sales, effective tax rate and EPS from continuing operations in the financial outlook table below have been recast to reflect this change.

While it will obviously be a while until Raytheon reports a full quarter on the new method, this SAB 74 disclosure from its third-quarter Form 10-Q provides the story of the company’s adoption process. It provides an understanding of the steps in the process, and the depth of the process. Notice the comment about frequent reports over a two-year period! And all this work was in spite of the fact that the new standard did not have a material impact for Raytheon!

 

Note 2: Accounting Standards

 

In May 2014, the Financial Accounting Standards Board (FASB) issued Accounting Standards Update (ASU) 2014-09, Revenue from Contracts with Customers (Topic 606), which will replace numerous requirements in U.S. GAAP, including industry-specific requirements, and provide 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 will permit companies to adopt the new standard early, but not before the original effective date of annual reporting periods beginning after December 15, 2016.

 

In 2014, we established a cross-functional implementation team consisting of representatives from across all of our business segments. We utilized a bottoms-up approach to analyze the impact of the standard on our contract portfolio by reviewing our current accounting policies and practices to identify potential differences that would result from applying the requirements of the new standard to our revenue contracts. In addition, we identified, and are in the process of implementing, appropriate changes to our business processes, systems and controls to support recognition and disclosure under the new standard. The implementation team has reported the findings and progress of the project to management and the Audit Committee on a frequent basis over the last two years.

 

We have been closely monitoring FASB activity related to the new standard, as well as working with various non-authoritative groups to conclude on specific interpretative issues. In the first half of 2016, we made significant progress toward completing our evaluation of the potential changes from adopting the new standard on our future financial reporting and disclosures. Our progress was aided by the FASB issuing ASU 2016-10, Identifying Performance Obligations and Licensing, which amended the current guidance on performance obligations and provided additional clarity on this topic, and the significant progress of the non- authoritative groups in concluding on specific interpretative issues. We also made significant progress on our contract reviews and detailed policy drafting. Based on our evaluation, we expect to early adopt the requirements of the new standard in the first quarter of 2017 and anticipate using the full retrospective transition method.

 

The impact of adopting the new standard on our 2015 and 2016 total net sales and operating income is not expected to be material. We also do not expect a material impact to our consolidated balance sheet. The immaterial impact of adopting ASU 2014-09 primarily relates to the deferral of commissions on our commercial software arrangements, which previously were expensed as incurred but under the new standard will generally be capitalized and amortized over the period of contract performance, and policy changes related to the recognition of revenue and costs on our defense contracts to better align our policies with the new standard. The impact to our results is not material because the analysis of our contracts under the new revenue recognition standard supports the recognition of revenue over time under the cost-to-cost method for the majority of our contracts, which is consistent with our current revenue recognition model. Revenue on the majority of our contracts will continue to be recognized over time because of the continuous transfer of control to the customer. For U.S. government contracts, this continuous transfer of control to the customer is supported by clauses in the contract that allow the customer to unilaterally terminate the contract for convenience, pay us for costs incurred plus a reasonable profit, and take control of any work in process. Similarly, for non-U.S. government contracts, the customer typically controls the work in process as evidenced either by contractual termination clauses or by our rights to payment for work performed to date to deliver products or services that do not have an alternative use to the company. Under the new standard, the cost-to-cost measure of progress continues to best depict the transfer of control of assets to the customer, which occurs as we incur costs. In addition, the number of our performance obligations under the new standard is not materially different from our contract segments under the existing standard. Lastly, the accounting for the estimate of variable amounts is not expected to be materially different compared to our current practice.

 

 

As always, your thoughts and comments are welcome!

Whistleblower Reminders

Hot Topic, , , , , , , , , , , , , , , , , , ,

By: George M. Wilson & Carol A. Stacey

 

On December 19 and 20, 2016, as a year-end reminder, the SEC’s Enforcement Division announced two more cases to emphasize that companies MUST NOT do anything to impede employees from blowing the whistle.

You can find a lot more background about this issue in this post.

In the first case NeuStar Inc. paid a fine of $180,000 for putting restrictive language in severance agreements.

The SEC found that NeuStar was “routinely entering into severance agreements that contained a broad non-disparagement clause forbidding former employees from engaging with the SEC and other regulators ‘in any communication that disparages, denigrates, maligns or impugns’ the company.” The agreements were structured harshly. Departed employees would lose all but $100 of their severance pay if they violated the agreement. This language impeded at least one former employee from contacting the SEC.

In the second case Oklahoma City-based SandRidge Energy Inc. agreed to pay a fine of $1.4 million. Even though the company reviewed their severance arrangements several times after new Dodd/Frank rules were put in place, they continued to include language “restricting” former employees from blowing the whistle to regulators.

The SEC found that “SandRidge fired an internal whistleblower who kept raising concerns about the process used by SandRidge to calculate its publicly reported oil-and-gas reserves.”

The message is clear – Don’t try to limit a former employee’s ability to blow the whistle! Instead, take steps to investigate the matter!

As always, your thoughts and comments are welcome!

Why, Oh Why, Is It Always Segments?

Hot Topic, , , , , , , , , , , , , , , , , , , , ,

By: George M. Wilson & Carol A. Stacey

If you have been involved with SEC reporting for more than say, five minutes, you have heard about or discussed with someone the SEC’s focus on operating segments. Segment related disclosures are included in several Form 10-K Items, including:

Item 1 – Description of the business,

Item 2 – Properties,

Item 7 – MD&A, and of course

Item 8 – Financial Statements.

Almost every SEC conference or workshop addresses the importance of segment disclosures.

The latest segment “message” from the SEC is in the November 7, 2016 Accounting and Auditing Enforcement Release dealing with PowerSecure.

It is the same familiar message we heard in the Sony case in 1998 and the PACCAR case in 2013. When companies avoid making proper GAAP disclosures for operating segments to try and bury problems in one part of a business with profits from another part of their business, trouble will result.

In the “classic” Sony case the company used profits from its music business to mask problems in its movie business. This case also has a great known trend disclosure problem and becomes an almost scary “double trouble” example. To escalate this case to “triple trouble” the SEC also made it clear that Sony’s assignment of MD&A to the IR manager was not appropriate by naming that person in the case and forcing Sony to reassign this responsibility to the CFO. With all that was going on with Sony the SEC went so far as to require the company to engage its auditors to “examine” MD&A. Surprisingly, under the attest standards, auditors can issue a full opinion report on MD&A!

In the PACCAR case problems in new truck sales were hidden with profits from truck parts sales. This SEC Complaint includes a very detailed summary of the operating segment disclosure requirements, discussing in detail how PACCAR’s management viewed the business and how, in the SEC’s judgement, PACCAR was not following the GAAP requirements. It includes this language:

“However, in reporting its truck and parts results as a single segment, PACCAR did not provide investors with the same insight into the Company as PACCAR’s executives.”

This story line repeats in PowerSecure. For the periods in question PowerSecure reported one segment when that was not how management actually viewed the business:

“PowerSecure also misapplied ASC 280 by concluding that its CODM – who was determined to be the Chief Executive Officer (“CEO”) – did not regularly review operating results below the consolidated level to make decisions about resource allocations and to assess performance. This was inconsistent with the way in which the CEO regularly received, reviewed, and reported on the results of the business and how the company was structured. On a monthly basis, the CEO received financial results that reflected a measure of profitability on a more disaggregated level than the consolidated entity. Further, on a quarterly basis, the CEO met with each business unit some of the business unit leaders had business unit level budgets and forecasts and received incentive compensation based, at least in part, upon the results of their business unit.“

The message is clear, don’t use segments to try and hide problems! As a last reminder, don’t forget that these disclosure requirements may go to an even lower level than operating segments in MD&A. Regulation S-K Item 303 makes this clear:

“Where in the registrant’s judgment a discussion of segment information or of other subdivisions of the registrant’s business would be appropriate to an understanding of such business, the discussion shall focus on each relevant, reportable segment or other subdivision of the business and on the registrant as a whole.”

As always, your thoughts and comments are welcome!

 

Third Annual Form 10-K Tune-Up

10-K Tips, , , , , , , , , , , , , , , ,

As you draft your annual Form 10-K it is always a challenge to be sure that you deal effectively with new and emerging issues and the ever-evolving focus areas of the SEC. Register for our January 23rd One Hour Briefing, Form 10-K Tune-Up. Review the key issues to address in this year’s Form 10-K, including the latest in SEC Staff comments about non-GAAP measures; new accounting standards, revenue recognition, leases and financial instruments.

http://www.pli.edu/Content/Seminar/Third_Annual_Form_10_K_Tune_Up_/_/N-4kZ1z10jog?Ns=sort_date%7c0&ID=301955

A Control Environment and History Follow-Up

Hot Topic, , , , , , , , , , , , , , , , , , , , ,

By: George M. Wilson & Carol A. Stacey

 

This famous quote has been in our thoughts over the last several months:
“Those who cannot remember the past are condemned to repeat it.”

George Santayana, the poet and essayist, wrote these famous words in his book The Life of Reason. Many other people including Winston Churchill have thoughtfully incorporated this fundamental principle of life in speeches and remarks.

Another favorite variation of the idea comes from Mark Twain:
“History doesn’t repeat itself, but it does rhyme.”

The lesson here is that if we learn history we can hopefully avoid making the same or similar mistakes in the future. As we discussed a couple of posts back, recent public company news shows that many organizations have not been learning from the past.

 

One person who can help us learn about history we do not want to repeat is Cynthia Cooper. She was the WorldCom head of internal audit who built and lead the team that worked almost “under cover” to find the largest fraud ever discovered. This was a tone at the top fraud, involving the CEO, CFO and CAO. Her book is a sometimes-chilling story of how bad tone at the top results in fraud.

 

Sharron Watkins is another person who can help us learn how to not repeat history. She was the Enron Vice President, a direct report to Andy Fastow, who blew the whistle about Enron’s accounting irregularities. And we all know perhaps too much about that fraud which was even the subject of a book and related movie “Enron: The Smartest Guys in the Room”.

 

Corporate ethics will never be easy, but as history and current events show, it does matter. If leadership of an organization sends the message that making money is the most important thing an organization does, if it sends the message that if you don’t make money you will be fired, if it sends the message that other values can be sacrificed if you make money, the ultimate result is inevitable. In countless frauds over centuries, from Ivar Kreuger, the match king in the early 1900s, to Equity Funding in the 1970s, to Madoff, to Enron, to the companies we are talking about today, this lesson has been proven time and time again.

 

These stories can help us learn and avoid the mistakes others have made. They can be the focus of training and learning. They can be the foundation for building awareness and support for these issues in organizations large and small.

 

As always, your thoughts and comments are welcome.

Three Years of Fun – Planning the “Big Three” New FASB Statement Transitions

Hot Topic, , , , , , , , , , , , , , , , , , , , , , , , ,

by: George M. Wilson & Carol A. Stacey, SEC Institute

We have all heard about the major projects the FASB has completed in recent years. Together with their implementation dates for public companies and allowed transition methods they are:

Revenue recognition: January 1, 2018. (F/Y’s beginning after December 15, 2017)

Early adoption is allowed to the original effective date, F/Y’s beginning after 12/15/16). Either a retrospective or modified retrospective with a cumulative effect adjustment transition may be used.
Leases: January 1, 2019. (F/Y’s beginning after December 15, 2018)

Early adoption is allowed. A retrospective transition must be used. The retrospective approach includes several practical accommodations.

Financial Instrument Impairment: January 1, 2020 (F/Y’s beginning after December 15, 2019)

Early adoption to years beginning after December 15, 2018 is allowed. The transition method is essentially a “modified retrospective approach with a cumulative effect adjustment” with adjustments for certain types of financial instruments.
The revenue recognition and lease changes have been widely discussed, but the financial instruments impairment change has not been as “hot” a topic. It could be problematic for some companies as it will apply to all financial instruments, including accounts receivable. Many companies could face significant challenges gathering the information to move from the current incurred loss model to the new expected loss model.
While the impact of each new standard will vary from company to company, every company needs to think about how to manage these three transitions. Will it be best for your company to adopt all three at once, or will it be best to adopt them sequentially? Or perhaps mix and match a bit?
There are several considerations in these implementation date decisions. How they will affect investor relations is a major issue. The time and other resources required, systems issues and ICFR impact are among the other inputs to this decision. Each company has to evaluate these considerations based on their own circumstances.
Given the potential magnitude of these changes and their widespread discussion in the reporting environment, disclosures about these changes have become more and more important to users. With the recent SEC Staff Announcement at the September EITF meeting about SAB 74 (SAB Codification Topic 11-M) disclosures, disclosing where you are in this process has become almost required. The more or less simple “standard” disclosures about “we have not selected a transition method” and “we do not yet know the impact” may not be enough. Qualitative information about where you are in the process may be a required disclosure.

There are strong incentives to move diligently on these transitions and to tell investors where you are in the process. And, anyway, who really wants to look unprepared?
Three years of sequential fun or big change? Spread it out or rip off the Band-Aid? Slow burn or big bang? We all get to decide what will be best for our company and our investors, the key issue is to make this decision on a timely basis!

 

As always, your thoughts and comments are welcome!