Tag Archives: lease standard

Overcome the Challenges Resulting from the FASB’s New Lease Accounting Standard!

The FASB’s new lease accounting standard presents complex accounting, internal control, systems and implementation challenges. Attend SECI’s live interactive workshop, Implementing the FASB’s New Leases Accounting Standard Workshop being held May 17th in Dallas with additional dates and locations this fall. Attendees will learn the conceptual underpinnings, overall structure and details of this new standard as it applies to both lessees and lessors. Implementation considerations, system issues and related topics will be discussed in detail and concepts will be reinforced by use of examples and case studies.

http://www.pli.edu/Content/Seminar/Implementing_the_FASB_s_New_Lease_Accounting/_/N-4kZ1z10dmc?fromsearch=false&ID=309311&t=WLH7_DPAD

Jeepers – More Whistleblower Enforcement Cases? – Do We Have the Message Yet?

By: George M. Wilson & Carol A. Stacey

Just a few weeks ago we did the latest in a series of posts about the SEC’s Whistleblower program. That post focused on two significant enforcement cases where companies attempted to impede whistleblowers. For other posts in our whistleblower series, see:

Our post discussing the background of the SOX and Dodd/Frank whistleblower programs

Our post about the total amount being paid-out to whistleblowers exceeding $100,000,000 (It is even more today!)

Our post discussing a company having to pay a $500,000 fine for firing a whistleblower

SEEMS LIKE THE MESSAGE SHOULD BE CLEAR BY NOW! Don’t try to limit how employees can blow the whistle.

But, the Enforcement Division is not done!

In a case announced on January 17 a company paid a $650,000 fine for including language trying to restrict whistleblower rights in over 1,000 severance arrangements. After removing the language the company also voluntarily agreed to conduct annual training for employees about their whistleblowing rights.

In a case announced on January 21 the SEC found a company that actively searched for a whistleblower, to the point of essentially threatening employees. The reason for the hunt was clear, the treasurer and the company had manipulated information related to hedge accounting and was actively trying to hide the fact that certain hedging relationships were not effective. When the SEC began to ask questions about the issue, the company suspected someone had blown the whistle. The company tried to ferret out the whistleblower, compounding their offenses. The company and the treasurer both paid fines.

There is a very important reason for these cases. In many situations a fraud would go undetected if it were not for the conscience and courage of whistleblowers.

It would seem that the SEC is actively searching for more enforcement cases to make the point that it is illegal for a company to try and prevent or impede employees from blowing the whistle.

Not to be too preachy, and hopefully to be a bit practical, here are two thoughts:

For all of us who may see a need to blow the whistle, know that this is never easy, and know that you have rights and protections.

For companies, don’t try to hide problems and make sure any agreements surrounding employee departures don’t have these kinds of restrictions!

 

As always, your thoughts and comments are welcome!

XBRL for Foreign Private Issuers Using IFRS

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!

Solid Knowledge and Tips Needed to Successfully Navigate SEC Reporting

Financial reporting professionals that are armed with the foundational knowledge and practical experience are better prepared to complete and review the SEC’s periodic and current reporting forms, including the 10-K Annual Report, the 10-Q Quarterly Report and the 8-K Current Report. Attend an upcoming SECI live workshop, SEC Reporting Skills, being held in March in San Francisco, New York and San Diego with additional dates and locations.

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

Non-GAAP Measures – The Saga Continues

By: George M. Wilson & Carol A. Stacey

The sometimes fuzzy distinction between non-GAAP liquidity measures and non-GAAP performance measures is a major concern of the SEC’s Non-GAAP Compliance and Disclosure Interpretations (C&DI’s) and the comment letters the Staff issues focused on this topic. In the middle of this grey question are EBITDA and “adjusted EBITDA”. Whether these measures are liquidity measures or performance measures can be a very complex, subjective question. To take some of the grey away the SEC included this C&DI in their May 2016 changes:

Question 103.02

Question: If EBIT or EBITDA is presented as a performance measure, to which GAAP financial measure should it be reconciled?

Answer: If a company presents EBIT or EBITDA as a performance measure, such measures should be reconciled to net income as presented in the statement of operations under GAAP. Operating income would not be considered the most directly comparable GAAP financial measure because EBIT and EBITDA make adjustments for items that are not included in operating income. In addition, these measures must not be presented on a per share basis. See Question 102.05.  (emphasis added) [May 17, 2016]

 

The last sentence in this answer is all about the potential confusion between EBITDA and cash flow from operations. GAAP and the SEC guidance specifically prohibit presenting cash flow per share because of the potential confusion between earnings per share and cash flow per share. (This goes all the way back to ASR 142 and old SFAS 95!) EBITDA, even when intended by management as an operations measure, is so close to this line that it cannot be presented on a per share basis.

 

In an interesting sequence of comment letters and responses the SEC has pushed its concerns about these kinds of non-GAAP measures to a new level. After a number of back and forth letters with a registrant focusing on whether a “non-GAAP adjusted net income” was a performance or liquidity measure the staff included this language in a late round comment:

 

Finally, in light of our discussions about this matter, we will evaluate the industry practices you described to us and consider whether additional comprehensive non-GAAP staff guidance is appropriate.

 

It is extremely unusual, as was even reported in The Wall Street Journal on February 13, 2017, to see a statement like this in a comment letter.

 

Even more eyebrow-raising is this comment in the SEC’s closing letter:

 

Although we do not agree with your view, in light of the circumstances, we have completed our review of your filing. We remind you that the company and its management are responsible for the accuracy and adequacy of their disclosures, notwithstanding any review, comments, action or absence of action by the staff. (emphasis added)

 

If you are presenting an EBITDA or similar measure it would be smart to review these letters.

 

You can find the first of the comment letter series here. The company’s responses (CORRESP documents) and the follow-up comment letters (UPLOAD documents) appear in this EDGAR list.

 

As always, your thoughts and comments are welcome.

When Disclosure Obligations Reach Beyond Financial 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!

Whistleblower Reminders

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?

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!

 

Disclosure Effectiveness – The Saga Continues

By: George M. Wilson & Carol A. Stacey

A not so long, long time ago (OK, sorry Arlo Guthrie), and over a very reasonable period, the SEC began its Disclosure Effectiveness initiative. As you have likely heard (and can read about here), the Staff has sought comment and feedback about a variety of issues, including a lengthy release dealing with Regulation S-K and another dealing with various “financial statements of others” requirements in Regulation S-X.

The latest disclosure simplification development is a 26-page Staff report required by the FAST Act titled “Report on Modernization and Simplification of Regulation S-K”. It addresses a variety of areas ranging from properties to risk factors. Included are several interesting ideas such as requiring year-to-year comparisons in MD&A for only the current year and prior year and including hyperlinks to prior filings for prior comparisons.

The report is a thoughtful and interesting step in this challenging process.

As always, your thoughts and comments are welcome!

Year-End Planning – More or Less Concluded – Keeping Up with SEC Focus Areas

By George M. Wilson & Carol A. Stacey

In recent weeks we have been posting about areas to deal with in advance of year-end. So far we have addressed:

Issues in the Statement of Cash Flows

Evaluating and Auditing ICFR

The New Item 16 Form 10-K Summary

Recently Issued Accounting Standards and a Few Example Comments

SAB 74/Topic 11-M – News from the SEC at the September EITF Meeting

Disclosure Effectiveness

Should You Consider Any Issues for OCA Consultation?

A Year End Planning Detail – No More Mailing the ARS to the SEC!

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

 

As we are getting ever closer to year-end this is also a good time to proactively review areas where financial reporting problems frequently occur and take steps to assure we have all the “i’s” dotted and “t’s” crossed in these areas.

Unusually complex accounting issues, difficult estimates and sensitive disclosures all become the focus of SEC comments. This is not because the Staff thinks they are important in and of themselves, but rather because these are areas where the Staff frequently uncovers problems in the comment process. Clearly if we do not deal with them appropriately, they involve risk of restatement and amendment.

There are a variety of ways you can keep up with the CorpFin Staff’s frequent comment areas. Every year at our Annual Reporting Forums in November and December, our Conference for Mid-Size and Smaller Companies in September and our Mid-Year Programs in May and June current and former Staffers discuss the areas where they have concerns.

Here is the list from our most recent programs:

  • Segments
  • Statement of Cash Flows
  • Income Taxes
  • Consolidation
  • Business Combinations
  • Fair Value
  • Goodwill
  • Revenue Recognition
  • Non-GAAP Measures & Metrics
  • Internal Control over Financial Reporting

Beyond hearing from the Staff and those in the know, many organizations research comment letters and summarize the areas and frequency of comments within these areas.   You can find these summaries on the web pages for most of the national CPA firms. Here are links to some of them:

EY SEC Comments and Trends

Deloitte’s SEC Comment Letter Series

PWC’s SEC Comment Letter Trends

Other companies build databases of comments which can be researched by comment area, CorpFin Office and even by reviewer. Two companies who sell these kinds of tools are Audit Analytics and Intelligize. However, remember the Staff’s caution that their comments are fact-specific to each registrant and you should never cut and paste from another letter.

If you have any other good sources of information about these issues, please leave them in a comment to this post, and, as usual, your thoughts and comments are welcome!