Archive for the ‘XBRL News’ Category

Preparing for the iXBRL Mandate – 2019 & Beyond

Friday, November 15th, 2019

RDG is one of the largest filers of iXBRL documents with the Securities & Exchange Commission.

Below are some details that we hope will shed some light for you regarding the iXBRL mandate.

What is iXBRL?:

iXBRL is short for Inline eXtensible Business Reporting Language. It is essentially a hybrid of your EDGAR & XBRL documents:   HTML + XBRL = iXBRL

Why iXBRL?:

Potential benefits the SEC has outlined regarding the move to iXBRL:

  • Gives the preparer full control over the presentation of XBRL disclosures within the HTML filing.
  • Helps eliminate inconsistencies between HTML and XBRL filings and improve the quality of the data.
  • Enhance the usability of disclosures (already tagged in XBRL) for reviewers and investors who no longer have to view the XBRL data separately from the EDGAR document.

When do you begin filing in iXBRL?

Filers will be required to file with iXBRL with their first Form 10-Q filed for a fiscal period ending on or after:

  • Large accelerated filers that use U.S. GAAP will be required to comply beginning with fiscal periods ending on or after June 15, 2019.
  • Accelerated filers that use U.S. GAAP will be required to comply beginning with fiscal periods ending on or after June 15, 2020.
  • All other filers will be required to comply beginning with fiscal periods ending on or after June 15, 2021.

To review the notes from our June 2019 Webinar on iXBRL implementation, please click here.

Protected: EDGAR System Update, Monday September 30th, Password Requirements

Friday, September 27th, 2019

This content is password protected. To view it please enter your password below:

Tagging Changes for Taxonomy Update

Friday, May 18th, 2018

Since the accounting landscape is constantly evolving, the FASB updates the US-GAAP taxonomy annually – adding concepts, removing others and sometimes restructuring existing sections.

Typically, RDG transitions to the latest taxonomy after the calendar year end filing period is complete and this year is no different.

From SEC.gov:

“The [SEC] strongly encourages companies to use the most recent version of taxonomy releases for their XBRL exhibits to take advantage of the most up-to-date tags related to new accounting standards and other improvements. The SEC suggests that filers consider transitioning to the 2018 taxonomies for the earliest reporting period that ends after March 12, 2018, but not for reporting periods that end before March 12, 2018.”

It is always our goal at RDG to create quality XBRL consistent with the most current structure of the taxonomy and latest industry standards. Because of this, tagging from one period to the next will not always be the same. If you would like one of our CPA, XBRL AICPA Certified team members to assist in a higher level review of your document please let us know.

For more information, please visit: Why did my XBRL tagging change from the last filing?

Please feel free to contact us if you have any questions or concerns.

Why did my XBRL tagging change from the last filing?

Tuesday, January 16th, 2018

One of the common questions we receive regarding XBRL tagging is, “Why did the tagging of the document change this period when compared to a previous filing?” This is a great question, with two short answers.

The first reason is that RDG Filings is consistently working to improve the quality of XBRL tagging on a quarterly basis to be consistent with the latest US-GAAP taxonomy and to remain in line with evolving industry standards.

The second is that the US-GAAP Financial Reporting Taxonomy is updated on an annual basis by FASB. This may or may not result in tagging changes in your document depending on which areas of the taxonomy are adjusted. These changes usually result in updates to best practices, style-guides , and Accounting Standards adjustments by FASB, AICPA and XBRL-US.

Typically, the taxonomy changes are released by FASB in the fourth quarter of the calendar year, but are not supported by the SEC’s EDGAR System until after the first calendar quarter of the next year, so most updates to tagging happen between the end of the first calendar quarter and the filing of any XBRL documents filed after that point.

Our role at RDG is to make sure all of our clients documents are in line with the most recent EDGAR and XBRL guidelines as well as best practices.  When tagging changes are necessary, we will point out what changes were made using our interactive ThunderDome XBRL Viewer.

We are proud of the fact that our XBRL data quality is at the top (99th percentile) of our industry quarter after quarter. There are only a few filing agents that can claim such consistency. The effort of improving XBRL data quality is why RDG Filings was one of the founding members of the XBRL.us Center for Data Quality and why quality and version control of your documents is our main objective.

IFRS Companies to Begin Filing XBRL in 2018

Tuesday, September 12th, 2017

On March 1, 2017 the SEC posted the IFRS Taxonomy.  A full eight years after the start of the XBRL mandate for US GAAP companies, the SEC has finally announced the mandate for IFRS companies to submit XBRL files for 20-F and 40-F filings.

IFRS filers will have to begin submitting XBRL exhibits with fiscal periods ending on or after December 15, 2017.

How does this impact SEC Foreign Private Issuers (FPI) that use IFRS?

SEC Forms 20-F and 40-F (and some 6-Ks*) will require XBRL tags to be applied to each number in the Base Financials, including all of the facts in the Notes to the Financial Statements.

It cannot be denied that this will require some additional work for IFRS companies’ financial reporting teams.  However, there is value in IFRS companies beginning to file XBRL structured data and adding their data to the currently existing wealth of structured data that has been submitted to the SEC by US GAAP companies since 2009.  XBRL structured data is computer-readable and enhances the value, access, and usability of the financial information that SEC issuers file.

RDG filings is one of the leading providers of full-service XBRL tagging solutions in the country, and we create the highest quality XBRL data available.  We have been filing XBRL under the US GAAP taxonomy since the beginning of the mandate, and we are very excited that the IFRS taxonomy is finally going to be made live.  As one of the founding members of the XBRL US Center for Data Quality, RDG has the experience and the expertise to provide IFRS companies with excellent customer service and the highest quality XBRL data.

RDG has always made a strong commitment to creating the highest quality, most useable XBRL data possible, and we employ Certified Public Accountants and experienced auditing/accounting professionals to provide personal service to all of our clients.  As a result of this commitment, the XBRL data that RDG builds has been ranked by a leading independent expert as being filed error free 99% of the time.

Don’t Wait

Don’t wait until you are drafting your 20-F or your 40-F to begin preparing for the XBRL tagging process.  The template creation and set up process is not insignificant, and it pays to begin the process early.  Please contact us to ask any questions and get a realistic and transparent flat-rate quote.  Some providers may try to overcharge you for this service, so it is very much worth your while to take a few moments to do your due diligence.

(*Unless an issuer has a Form F-3 shelf registration that it wants to keep current, there is no requirement for quarterly or semiannual financial statements or earnings press releases that are submitted to the SEC on Form 6 K to include the information in XBRL format.)

We will be looking forward to hearing from you. Get in touch with us anytime!

Stewart Walker

415.643.6017

XBRL FAQ: What is Bleed-Through?

Tuesday, May 3rd, 2016

Bleed-through is a common phenomenon on the SEC’s XBRL Viewer, as well as on RDG’s own Thunderdome® Viewer (which was designed to resemble the SEC’s Viewer, but with more information and features).  To explain it in a nutshell: Bleed-through is a natural result of how the SEC’s Viewer interprets XBRL code.  It is both normal and expected by the SEC.

Below is a common example of bleed-through.  The first table presented is directly from the company’s EDGAR document (it’s from a disclosure table in Note 1). The second is the same table, but how it is presented in the SEC’s XBRL Viewer.

Bleed Through Table 1

Bleed Through Table 2

 

The difference in the XBRL Viewer is the addition of the first line, “Net trade income (loss).”  Plainly those “Net trade income (loss)” numbers do not ‘belong’ in the Note 1 disclosure table.

So, why are they there?  Well, the short-answer is that due to the nature of XBRL and the function of the SEC’s XBRL Viewer, the numbers are “bleeding through” from the Operations Statement.  You can see that table from the EDGAR document here:

 

Bleed Through Table 3

 

The longer answer is that both the “Net trade income (loss)” line in the disclosures table in Note 1 and the “Net trade income (loss)” line in the Operations Statement are tagged with the same primary concept (us-gaap_NetIncomeLoss).  However, only the occurrence of that concept in the Note 1 table has had a dimension applied to it.

This bleed-through issue is not symptomatic of a problem with the tagging.  This document is tagged properly and it is entirely in line with the SEC XBRL requirements and FASB best practices.  The bleed-through is a direct result of the SEC’s XBRL Viewer, and to-date, the SEC has taken no steps to correct it.

Here’s what is happening on the SEC’s Viewer:  When the Viewer displays any fact that has been tagged with a dimension, the Viewer will also grab and display all other facts throughout the document that share the same tag but that do not include a dimension. In this case, the “Net trade income (loss)” line in the Operations Statement is tagged with the same primary concept as it is in the Note 1 disclosure table, but in the Note 1 table that concept is also dimensionalized.  As a result the SEC Viewer presents the “Net trade income (loss)” line from the Operations Statement in the Note 1 table.

This is classic bleed-through, and it has been causing headaches for people reviewing XBRL tagging since the inception of the mandate.

So, can it be fixed?  Firstly, it is important to understand that the SEC does not want filers adjusting their tagging simply to make the presentation in the XBRL Viewer look better. The reality of XBRL is that it is not intended for human consumption.  It is designed to make Financial Statements & Notes machine-readable.  When XBRL is tagged properly – each fact stands alone, free of the original document, getting context only from its own tag, date, and any dimensions.  From a “machine-readable” point of view, it does not matter where in the document the fact is located, so long as it is tagged correctly.  This is why the SEC did not build the Viewer to present the XBRL in an entirely human-readable format.  It is also why the SEC expects to see bleed-through, and does not consider it an issue.

The actual issue is when some filers attempt to “fix” bleed-through by adjusting the tagging with the presentation in mind.  We do not recommend these sorts of “presentation fixes” because they often contradict SEC guidelines and FASB best practice.  So in the case above – as with almost all bleed-through cases – we simply leave it be.  It is tagged properly, and it is machine-readable.  The SEC wants it tagged this way, and they expect the bleed-through that results.

The SEC’s Updated XBRL Viewer – Improvements are Accompanied by Some Bugs

Tuesday, August 11th, 2015

The SEC has updated their XBRL viewer, and in many ways the changes are improvements.  The new XBRL viewer (3.2.0.727) was deployed this summer, replacing the previous version (2.4.1.9).  Additionally, the update was a necessary step with regard to future enhancements the SEC will be making to the viewer.  However, in the short term, this update includes some bugs that we wanted to alert you to. This post will describe the changes the SEC made to their viewer and explain some of the bugs that have come from this update.  We invite you to contact us if you have any questions or if you’d like more specific information.

To put the viewer update in context, it’s important to know that the previous SEC viewer originally was created using the .NET framework over 6 years ago.  However, the SEC’s validation engine (Arelle) was built using a coding framework called Python.  The different programming languages made integrating the two platforms difficult.  Additionally, the .NET framework caused some problems running the renderer on non-Windows machines.

To address these issues, the SEC has built the new viewer using the Python platform so that integration with the Arelle validator is now seamless.  While this does not impact the end user to any significant degree, it helps developers and the SEC a great deal.

Now we will address the bugs that have popped up as a result of this viewer update.

Uncategorized Items

“Uncategorized Facts” are typically only presented as such if the facts are not assigned a specific presentation. The updated viewer is erroneously identifying certain facts as “uncategorized” even when they have been assigned a presentation.  This issue is most commonly tied to US-GAAP concepts that appear on both the Income and Cash Flows Statements.  Apparently, the viewer will place shared facts from the Cash Flows in the “uncategorized” section and ‘forgets’ that those facts were already used on the Income Statement.  This means the viewer did not need to display those facts as uncategorized because they were indeed displayed on the Income Statement.  The new viewer also fails to distinguish between actual uncategorized facts and facts the viewer is choosing not to display.

The SEC is aware of this bug, and we believe it will be addressed with their next Viewer update, but they have not yet provided a timeframe for the correction.

Total Columns

Where the previous viewer displayed a “Total” column only when the presentation was an equity table, the update has caused the viewer to display a “Total” column whenever there are multiple contexts that end on the same date in the same presentation.  This change does allows for tables other than the equity table to render with a “Total” column, but it leads to certain other issues when viewing reports (e.g.: The Document and Entity Information can now render with a “Total” column, or Operations tables may render with two “Total” columns).

We do not yet know if the SEC considers this a bug, or if they will address it with their next Viewer update.

 

If you have any questions or would like any further detail, please feel free to contact us anytime.

Stewart Walker – SVP, Director of Sales

(415) 643-6017

RDG Filings is Honored to be a Founding Member of the XBRL US Center for Data Quality

Friday, June 26th, 2015

Since the inception of the XBRL mandate, RDG has strived to set the standard for XBRL data quality, and we are proud to be among the leaders in the XBRL community.  That is why—along with Merrill, RR Donnelley, Vintage-a division of PR Newswire, and Workiva—RDG Filings is delighted to be a Founding Member of the XBRL US Center for Data Quality.

The formation of the Center for Data Quality—announced yesterday—is the culmination of months of work by the XBRL US, the Founding Members, and many more people to whom we are grateful.

The Founding Members provide XBRL tagging services and software to a majority of public companies, and they have come together in shared commitment to the importance of improving the quality of the XBRL data that is filed with the SEC.

The advent of the XBRL mandate has been a tremendous improvement to the existing HTML/EDGAR format, and XBRL has become the worldwide standard for the reporting and analysis of financial information.  However, the full benefits and potential of XBRL have not yet been realized because much of the XBRL currently filed with the SEC contains errors and inconsistencies.  As a direct result of valid concerns about its accuracy and reliability, investors and analysts have been reluctant to utilize the available XBRL data.

The XBRL US Center for Data Quality believes that the errors and inconsistencies currently restraining XBRL’s true potential are primarily the result of:

  • Absence of unambiguous guidance for using the US GAAP taxonomy
  • Lack of corporate awareness of errors in their filings

Investors, analysts, the SEC, and the market in general will benefit greatly from the utilization of XBRL data, and RDG Filings is happy to join forces with other leaders in the XBRL community to ensure that the quality and utility of the data improves dramatically.  The Data Quality Committee will develop:

  • Guidance to provide for uniform, consistent tagging of financial data and to clarify those specific circumstances where custom tags are appropriate
  • Automated validation rules to detect input errors and verify compliance with the Committee’s guidance

RDG Filings agrees with Barry Melancon, CEO of the American Institute of CPAs, and Chair of the XBRL US Board of Directors, when he says that in order to “realize the full economic benefit of XBRL, investors and other consumers must have access to accurate and reliable XBRL data.”  Melancon applauded the formation of the Center for Data Quality as an “industry-funded initiative” that will “make it substantially easier for companies to create consistent, good quality financial statements in XBRL format.”

RDG Filings—along with the other Founding Members of the XBRL US Center for Data Quality—has always made a commitment to creating quality code that is of the greatest value and utility for analysts and investors.  There is a “clear demand for timely, structured, machine-readable data,” and we are excited about the work the Center will do to fulfill the potential that XBRL holds for public companies and the investment community.

Feel free to contact me any time.

Stewart Walker – SVP, Director of Sales

(415) 643-6017

XBRL Is Back In The Crosshairs — Rep. Hurt Is At It Again

Monday, April 27th, 2015

Despite repeated legislative defeats, Representative Hurt from Virginia’s 5th district has re-introduced legislation to create a two-tier caste system among publicly traded companies.

According to this most recent legislation (which is identical to language that failed to pass in 2014), some companies would continue reporting their quarterly and annual financial information in the XBRL format, as they have since 2011.  Other companies, however, would suddenly be exempt from this requirement, and they would revert back to a reporting standard that was cutting edge in 1996.

As this new legislation—HR 1965—is identical to HR 4164 which was introduced in 2014, you can read our post regarding that legislation for more detail.  However, the main points are the same:

If this poorly considered bill manages to gain passage—either on its own or as an amendment to a larger bill—the partial elimination of the XBRL filing requirement would be deeply damaging to the national standards of public disclosure and financial reporting.  Additionally, the SEC’s ability to discover investor fraud would be unnecessarily and dramatically hamstrung by this bill.  Lastly, and rather ironically even by congressional standards, this bill will be considerably detrimental to the same companies that it is meant to help, because exempting small companies from XBRL reporting will create a permanent underclass of less visible, and undiscoverable investment opportunities.

It’s a bad bill with dubious benefits and destructive consequences.

Feel free to contact me any time.

Stewart Walker – SVP, Director of Sales

415.643.6017

Once Again, The SEC Bolsters XBRL

Monday, February 23rd, 2015

Even as the misguided efforts to minimize the reach of XBRL reporting continue in Congress, the SEC has increasingly endorsed and strengthened its commitment to this important advancement in financial disclosure and data availability.  Recently, the SEC has taken aggressive steps to promote and protect XBRL data.

On February 19th, 2015, SEC Commissioner Luis Aguilar endorsed the Investor Advisory Committee’s (IAC) 2013 recommendation to have issuers provide information in an interactive data format.  Speaking at the SEC Speaks conference, Commissioner Aguilar promoted the SEC’s adoption of machine-readable XBRL format and promoted the notion that it would be a great benefit to investors Proxy information were also presented in XBRL.  Commissioner Aguilar said: “For instance, it has been suggested that the better use of 21st century technology in the proxy process may facilitate how shareholders can more effectively receive and understand how their companies are performing, and to better put that performance into perspective.  Indeed, it’s only logical to expect that better informed investors would likely participate in greater numbers.”

Aguilar went on to endorse the IAC’s recommendation that the SEC “immediately prioritize tagging important information with respect to various corporate governance issues, including portions of the proxy statement that relate to executive compensation and matters voted upon by shareholders.”  His support is supported by the fact that “tagging the voting data and results contained in certain forms could result in more informed voting and investment decisions, and would facilitate comparisons among public companies.”

At the same SEC Speaks conference, the SEC’s Investor Advocate, Rick Fleming, criticized the regressive XBRL proposal put forward by Representative Robert Hurt.

Representative Hurt’s proposal would create an exemption from the XBRL filing requirements for certain small companies, which would exclude more than 60 percent of all public companies.  Mr. Fleming said that if this were signed into law, it “would seriously impede the ability of the SEC to bring disclosure into the 21st Century.”  He continued, “If Congressional action is needed, it should be used to press the SEC to move forward in its efforts to make disclosure more accessible and useful for investors.”

The SEC has only increased its commitment to the XBRL reporting requirement, and they have also massively increased its use of the data.  Investment decisions by analysts and enforcement decisions by the SEC will increasingly be driven by the information provided in the XBRL data, and for that reason RDG has, since its very inception, been committed to having the best people creating the highest quality code.

XBRL is the future of financial disclosure, and RDG can help public companies create excellent and usable data.  Please contact us to learn more about our Full Service Tagging Services and our XBRL Quality Assurance Services.

Feel free to contact me any time.

Stewart Walker – SVP, Director of Sales

415.643.6017