Tag Archives: TAX ACCOUNTING

A Really Good Question – Form S-3 and the New Revenue Recognition Standard

In a recent post we discussed a potential complication in the registration process and Form S-3 in particular if you retrospectively implement the new revenue recognition standard. You can review the post here. The issue arises if you file an S-3 in 2018 after you adopt the new revenue recognition standard but before your 10-K for 2018 is filed. The 2018 Form 10-K will have annual financial statements for 2018, 2017 and 2016 retrospectively applying the new standard. However, if you file an S-3, or have an S-3 shelf registration in place, before you file the 2018 Form 10-K, your S-3 would be required to have three fiscal years, now 2017, 2016 and 2015 that apply the new standard.

Thus, you could be required to report an extra year, 2015, on the new revenue recognition standard if you want to access the capital markets with an S-3, or an S-3 shelf registration, during 2018.

Whether or not the SEC can or will have any relief from this issue is not finalized. So stay tuned!

In our post we set up the example with an S-3 filed after the first-quarter 2018 form 10-Q is filed.

This all lead to a really great question from a reader:

 

In the hypothetical, if an issuer were to file an S-3 in the first quarter of 2018 (before its 3Q financials go stale and before the 2018 10-Q is filed), does Item 11 of Form S-3 require the company to file an 8-K with its recast 2015 financials reflecting the full retrospective adoption of the new standard before the issuer may take-down securities?

The answer to this question? Well, there is not a detailed rule anywhere that deals with the issue.

We researched the question and the closest guidance we could find was in the CorpFin Financial Reporting Manual Topic 11:

“Companies may transition to ASU No. 2014-09 and IFRS 15 (collectively, the “new revenue standard”) using one of two methods:

Retrospectively to each prior period presented, subject to the election of certain practical expedients (“full retrospective method”). A calendar year-end company that adopts the new revenue standard using this method must begin recording revenue using the new standard on January 1, 2018. In its 2018 annual report, the company would revise its 2016 and 2017 financial statements and record the cumulative effect of the change recognized in opening retained earnings as of January 1, 2016.

Retrospectively with the cumulative effect of initially applying the new revenue standard recognized at the date of adoption (“modified retrospective method”). A calendar year-end company that adopts the new revenue standard using this method must begin recording revenue using the new standard on January 1, 2018. At that time, the company must record the cumulative effect of the change recognized in opening retained earnings and financial statements for 2016 and 2017 would remain unchanged. The standard also sets forth additional disclosures required by companies that adopt the new standard using this method.

That language sure sounds like if you file after January 1, 2018, you need three years, 2015, 2016 and 2017 based on the new standard.

That said, stay tuned, we will all continue our research! And what is more fun than a really deep SEC research question?

As always, and especially with this one, your thoughts and comments are welcome!

Some XBRL News and A Few Tidbits

XBRL has not really been in the news much lately, but on March 29, 2016 the SEC released a second DERA study about tagging processes. The study, titled “Staff Observations of Custom Axis Tags” is at:

www.sec.gov/structureddata/reportspubs/osd_assessment_custom-axis-tags.html

Here is an excerpt from the introduction of the report:

As part of our ongoing process to monitor registrant compliance with the requirements to report their financial information in their eXtensible Business Reporting Language (XBRL) exhibits, staff in the SEC Division of Economic and Risk Analysis recently assessed certain aspects of the XBRL exhibits that affect the data quality of the disclosures provided. Specifically, the staff examined the use of custom axis tags in XBRL exhibits that reporting companies submitted with their annual reports on Form 10-K. An axis tag in XBRL allows a filer to divide reported elements into different dimensions (e.g., revenue by geographical area, fair value measurement levels, components of total equity (e.g., common, preferred)) while also showing the relationships between separately reported elements.

……………

The staff’s analysis resulted in a few key observations. First, unlike our previous staff observations that revealed a lower average rate of custom line item tags among large filers, staff observed a higher average use of custom axis tags as filer size increased, with the rate of custom axis tags highest for large accelerated filers. Second, for a random sample of filings that staff reviewed, staff observed instances of filers creating custom axis tags unnecessarily when an appropriate standard axis tag existed in the U.S. GAAP taxonomy.

 

This is an interesting development, and clearly demonstrates the SEC’s work to help make XBRL information more reliable and useful.

The earlier information the SEC has issued about XBRL include:

A “Dear CFO” letter about calculation structures that is at:

www.sec.gov/divisions/corpfin/guidance/xbrl-calculation-0714.htm

This earlier DERA study of extension use at:

www.sec.gov/dera/reportspubs/assessment-custom-tag-rates-xbrl.html

 

Getting XBRL Right

Next, here is a good reminder to make sure that your XBRL submissions are prepared properly and tagging is done appropriately. While XBRL is not subject to ICFR and there is no requirement for any sort of auditor review, XBRL submissions are subject to your disclosure controls and procedures. As a result you should have appropriate controls to assure that your XBRL submission:

“is recorded, processed, summarized and reported, within the time periods specified in the Commission’s rules and forms.”

The above quote is from the definition of Disclosure Controls and Procedures in Exchange Act Rule 13a-15 which is at:

www.ecfr.gov/cgi-bin/text-idx?SID=8e0ed509ccc65e983f9eca72ceb26753&node=17:4.0.1.1.1&rgn=div5#se17.4.240_113a_615

This requirement is highlighted in a recent Form 10-K/A filed by Goldman Sachs to make some corrections in their XBRL submission. Goldman filed their original 10-K on February 19, 2016 and on March 1, 2016 filed a Form 10-K/A. As is required by the Exchange Act Rules for amendments, Goldman included this explanatory note:

EXPLANATORY NOTE

Due to an error by our external financial printer, our Annual Report on Form 10-K for the fiscal year ended December 31, 2015 (Original Form 10-K) was filed with an incorrect version of Exhibit 101, which provides items from our Original Form 10-K formatted in eXtensible Business Reporting Language.

This Amendment No. 1 on Form 10-K/A (Amendment) to our Original Form 10-K, filed on February 19, 2016, is being filed in accordance with Rule 12b-15 under the Securities Exchange Act of 1934 for the sole purpose of including the correct version of Exhibit 101.

This Amendment does not amend or otherwise update any other information in the Original Form 10-K and does not reflect events occurring after the date of the Original Form 10-K.

Goldman was perhaps doing something that is appropriate, which we discuss in our workshops. After the filing someone likely double checked the XBRL submission and found the problem, and they fixed it as soon as possible. This is an example of disclosure controls in action on a detective basis, and again, while the SEC has not really indicated that they will do a lot of review of XBRL submissions, we need to make sure they are done appropriately. And, who knows, it is possible the SEC pointed this out to Goldman.

 

Taxonomy Update

On March 7, 2016 the SEC updated the EDGAR system to accept the 2016 XBRL taxonomies previously released by the FASB. The announcement is at:

www.sec.gov/structureddata/announcement/osd-announcement-030716—xbrl-taxonomy-update.html

 

Using XBRL Information

While we still don’t hear a lot about users taking advantage of all the information in the XBRL database, user tools are continuing to evolve. One tool that provides a nice way to access and use XBRL data comes from a company called Calcbench. If you do peer group analysis or are searching for comparable disclosures, this is a very useful tool. You can learn more at:

www.calcbench.com

 

As usual your thoughts and comments, including any insights you have about people using XBRL or XBRL user tools, is welcome!

Comment of the Week – Market Risk Reminder

 

We have been discussing the topic of Market Risk Disclosures a lot in this environment of volatile exchange rates, bumpy commodity prices and uncertain interest rates. This disclosure is one of the most confusing parts of Regulation S-K. Without going into a whole lot of details about S-K Item 305 (which we covered in an earlier blog at seciblog.pli.edu/?p=489), as we move towards the end of the first quarter it will continue to be important to focus on getting this disclosure right.

 

So, with this post as a reminder, here is a quick example in a recent comment:

Item7A. Quantitative and Qualitative Disclosures About Market Risk, page 63

  1. Please provide an analysis on whether your “cash flow hedges,” discussed in the second- to-last paragraph of page 63, are material, such that you would need to provide the disclosure in Item 305(a) of Regulation S-K. Please see General Instruction 5.B to Item 305(a) and (b).

 

As usual, your thoughts and comments are welcome!

Another SEC Accounting Enforcement

 

The most recent fruit of the SEC Enforcement Division’s on-going efforts to find and bring financial reporting cases is against Monsanto Company and several individuals. It was announced on February 9, 2016. You can read the release here:

www.sec.gov/news/pressrelease/2016-25.html

 

The case involves some of the classic financial reporting problem areas including revenue recognition, manipulation of expenses and ICFR.

 

The settlement includes fines for both the company and individuals as well as two officers being barred from SEC practice. Interestingly, the settlement also requires the company to hire a compliance consultant to deal with the enforcement related issues.

 

The CEO and CFO, while not named in the case, voluntarily repaid bonuses and share based payment awards that would not have been paid if financial results had not been manipulated. This was essentially a voluntary clawback. As a result, the SEC did not have to bring a case based on the clawback provisions of SOX.

 

As always, your thoughts and comments are welcome!