XBRL Founder Stumped by Income Statement Analysis

Written by Tammy Whitehouse
Posted on October 21, 2011 Comments
October 21, 2011 | General | Barron King

In his continuing dig into XBRL submissions to assess utility and functionality, Charles Hoffman is finding income statement data hard to figure out.

Hoffman is often credited with founding the concept of XBRL and inspiring the American Institute of Certified Public Accountants to invest in developing it. He has been studying more than 5,500 XBRL filings to the Securities and Exchange Commission to get a sense of the semantic model of financial reports that XBRL produces.

The assessment of the balance sheet and the cash flow were straightforward enough, he said. But the income statement is a lot more challenging. In fact, he calls it maddening.

“The income statement has a lot more moving parts,” he said. Not all income statement elements apply to all filers in the same way. Items like income from operations, discontinued operations, noncontrolling interests, extraordinary items, perhaps even income taxes make it impossible to build a one-size-fits-all income statement.

That makes it hard for filers to sort through the GAAP Taxonomy, he says, and find the concepts that are appropriate to their particular data. If companies had a series of examples to follow, it might give them a clearer roadmap to submitting data that would ultimately be more comparable, he says.

The income statement also doesn’t carry subtotals in the same way as the balance sheet or the cash flow statement, making it more difficult at time to cross reference or verify numbers, he said. All of that, combined with the nature of XBRL user software, makes it difficult for users of income statement data to find what they might be looking for, he said.

To illustrate, Hoffman says he has discovered that filers are generally using three different concepts in the Taxonomy to report net income or loss. He worries perhaps there is too much ambiguity as to which of the three most chosen concepts should be used under different reporting scenarios.

Of nearly 4,000 filings he has examined, nearly three-fourths report income (or loss) from continuing operations before taxes, but a wide variety of labels are used, and many filers even created extensions for this concept, giving it the exact same name as the concept provided by that name. Hoffman wonders if some filers carried it forward from an earlier XBRL submission when the taxonomy in place did not have a concept for this item.

He found revenue for 84 percent of the filings where he searched for it. He’s pretty sure the other 16 percent report revenue somewhere, but he’s just not sure where. “There are so many different ways to report revenue,” he said. Some companies provide a total for revenue, making it easier to find, but some do not, making it much more difficult to find, he said.

Hoffman said he’s hopeful his exercise will help practitioners focus more on how to make XBRL more consistent across companies and therefore more useful to users of financial information.

 

 

XBRL: Compliance Exercise or Cost-Cutting Opportunity?

Written by Robert Pinsker
Posted on October 14, 2011 Comments
October 14, 2011 | General | Barron King

Is XBRL another regulatory compliance burden (hello, Sarbanes-Oxley Act) or is it an opportunity for companies to leverage an open-source (that is, “free”) technology to become more operationally efficient and cut costs (hello, Sarbanes-Oxley Act software)? If this sounds redundant to you, it should. I have been involved with XBRL since 2001. When I think about how far XBRL has come since then, I cannot help remembering my favorite movie trilogy, Back to the Future. At the end of the third movie, Marty (played by Michael J. Fox) wondered aloud why his future changed with a single choice—that is, not drag racing with another car whose driver called him “chicken”. Doc Brown (played by Christopher Lloyd) told Marty, “Your future is not set. It is whatever you want it to be.” Although those words are somewhat cheesy, they have resonated in my life choices since I first watched that movie.

So what does a moderately-popular movie trilogy have to do with XBRL? Plenty, in my opinion. XBRL has obviously grown into a global technological phenomenon, thanks in large part to regulators. Doc Brown’s response to Marty is the same kind of response CEOs, CFOs, and CIOs should be listening to: XBRL can be whatever they want it to be, meaning it can be simply a compliance burden (furnishing XBRL documents to regulators) or much, much more. How much more? Well, that is up to the individual management teams. Here are some examples.

There is a well-known European-based bank that successfully implemented an XBRL project over five years ago. This bank streamlined its operations and financial reporting by having all of its customer transactions entered by the customer into the bank’s website, which had XBRL embedded in it. After building a custom taxonomy, all data submitted (literally millions of lines of code, mostly credit reporting) was automatically tagged in accordance with the private taxonomy and entered into the bank’s database. Since the data was tagged in XBRL, it was reusable for internal sharing purposes across its hundreds of branches and was easily converted to the taxonomy required by regulators, whether foreign or domestic. A process that cost thousands of Euros has saved millions of Euros over the course of a few years.

But the opportunity to streamline operating efficiencies should not stop there. Given recent regulatory mandates, many of the bank’s customers are required to format their financial information in XBRL. The next opportunity is to have the customers send this data to the bank the same time that it is sent to the regulator. Rather than re-entering the data to or from one or  more spreadsheets, the data is already formatted in XBRL. It is already easily usable by the bank and convertible into any format the bank prefers. Again, this is all done without the inefficiency of re-entering data and thus lowers credit risk.

Does a bank have to be subject to the SEC’s XBRL mandate to take advantage of this opportunity? No. All U.S. banks, for example, have been reporting their call reports in XBRL to the FDIC for over five years. I suspect that there have been similar practices and requirements globally. Does a company have to be a bank to take advantage of this XBRL capability? Again, no. Any company of any size that uses the Internet in its business operations or financial reporting can build a taxonomy to suit its needs. Alternatively, the company can have one custom-built for it by someone knowledgeable in XBRL and use a basic taxonomy editor. There is no need for expensive and potentially disruptive disclosure management software just to leverage XBRL in the fashion described above. Of course, if the company wants to upgrade consolidation or other disclosure management activities, implementing this type of software with or without XBRL is another option.

So can a data standard such as XBRL be successful in more internal, supply-chain management activities? One does not have to turn any farther than the health information technology domain for the answer. Health Level Seven (HL7) currently represents the global authority on standards for interoperability of health information technology, with members in over 55 countries (see HL7.org). HL7 provides standardization in domains such as patient demographics, clinical observations, patient care, and problem-oriented records. There are obvious differences between XBRL and HL7, but HL7 has been a successful global exercise of data standard in the healthcare reporting space. There is no reason why XBRL cannot duplicate this success in the financial reporting space.

To summarize, almost all XBRL implementations to date have been due to compliance with regulations. Management almost always has numerous concerns about strong regulatory compliance, and there are incentives to maintain this compliance. However, organizations worldwide have the opportunity to leverage XBRL much more than they currently are. All they need is a 25th hour in the day, 8th day in the week, and someone who is knowledgeable about building custom taxonomies.

Well, one out of three still gets you into the baseball All-Star game every year. Let the expansion in XBRL-based uses begin!

 

XBRL Founder Generally Impressed with Early Filings

Written by Tammy Whitehouse
Posted on October 6, 2011 Comments
October 6, 2011 | General | Barron King

Charles Hoffman, often credited with founding XBRL, has been studying more than 5,500 XBRL filings to the Securities and Exchange Commission to get a sense of the semantic model of financial reports that is emerging through the XBRL process. He’s curious to see how well SEC filings adhere to that model.

He analyzed both 10-Ks and 10-Qs looking for some patterns of consistency in how companies are selecting tags to relate common financial reporting concepts. Hoffman found that 21 different generators were responsible for creating his sample of 5,525 filings, which logically suggests there might be more diversity in implementation than if the entire sample were generated by a single source or only a few sources.

The analysis focused on some fundamental elements that should be common among virtually all financial reports for public companies: assets, liabilities, equity, profit, loss, cash, revenue, basic entity information and the like. Despite the large number of sources, 3,170 of the filings, or 57 percent, had a combination of all the key characteristics where Hoffman was hoping to see some patterns.

It’s an impressive indicator of the quality of the XBRL submissions given how new the technology is, in Hoffman’s view. “There is definitely a leveragable semantic model peering out from that set of 5,525 SEC financial filings,” he wrote.

Hoffman found every sample reported the concept for the entity’s name, but only 21 percent reported the concept for their trading symbol. He surmises registrants must not find the trading symbol concept to be useful. While every sample reported the document period end date, Hoffman found on closer examination that about 20 filings reported it as the submission date or some other date rather than the balance sheet date.

While 97 percent of all filings reported a concept for assets and for liabilities and equity, he found five filings where they didn’t balance, either in the HTML or the XBRL filings. Hoffman found that 96 percent of filings reported one of four concepts for equity – stockholders equity, stockholders equity including the portion attributable to noncontrolling interest, partners’ capital, and partners’ capital including the portion attributable to noncontrolling interest – and he sensed some inconsistency in the use of the equity concepts.

Hoffman was disturbed to note that net income/loss is being reported under three different concepts. There are separate concepts in the taxonomy for profit/loss, net income/loss, and net income/loss available to common stockholders. “Basically, there is ambiguity as to which of the three of those concepts to use in different reporting scenarios,” he wrote.

Hoffman says his next move will be to drill another level lower into the cash flow statement, which he expects to be easy. Then he will take on the income statement, which he expects to be more difficult because there is more variety in how companies report income, so it will be more difficult to detect patterns. “A bottom-up approach may be superior to a top-down approach,” he wrote.