It was somewhat disturbing and sad to read the editors comments on XBRL. Disturbing for two reasons. Firstly, it points to the lack of serious industry journalistic coverage of the business or market drivers for a global accounting standard that has been incubated, piloted, deployed over the past 8 years with obvious implementation successes, and secondly, it seems to suggest a rather “head in the sand” point of view that “we should let the capital markets work their magic to solve this problem.” It is sad to see the editor of a “compliance” magazine stoop to such dramatic headlines (XBRL Hell!) without doing the minimum required research to better serve its readership. “Eye candy?!” And puzzling nonetheless to see why a magazine focused on compliance issues should be so flippant about “letting the markets work their magic.” But then, it has always been far easier to be an Eeyore than a Tigger!
While the Editor focuses on the SEC program as the driving force and chides the regulators efforts to build a critical mass of early adopters, he completely misses the point in terms of why public companies need to, and will adopt a financial reporting standard that safeguards the accuracy and timeliness of public company disclosures. It is a point often missed when a technology is first hitting the market and is receiving understandable and predictable, anemic market uptake. While the majority of reporting and compliance people in any company are hired to perform a role that deals in very critical and visible information sharing in a very methodical and structured manner, and are managed by CFOs, IROs or Compliance Officers who are charged with policing the release of public information, the manner in which company information gets transported and ultimately consumed suffers systemic problems that are outside the control of these diligent and well meaning reporting groups. It would serve the Editor well to survey a handful of public companies and track the root cause of reporting problems, such as a correction in the media, such as improperly interpreted line items from their footnotes or base financial tables, such as the impact of some company restatements that stem from known poor internal information gathering.
So, while the editor should take comfort in knowing that XBRL is complex because information companies disclosures can be very complex, and XBRL is merely a reflection of a reality that isn’t going to change – highly complex, company specific, industry specific, geographical guided, regulator shaped, accounting rule based public disclosures, he should also be cognizant of the fact that solutions have emerged to make the process of adopting XBRL as easy as updating an Excel worksheet. While it may be useful to “talk XBRL” and rebut the technical issues cited in the editorial, it would serve your readers better to know that the benefits of XBRL are far larger, near term, and early adopters are now shouting louder than the noise that has filled the Eeyore’s camp.
First, the editor claims that
While a tipping point hasn’t been reached, changing market behavior with little immediate benefit until infomediaries and analysts institutionalize XBRL usage will continue to be a challenge. However, beyond compliance to the SEC’s directive, public companies are slowly beginning to understand that they have a reporting problem that directly impacts their company. And, while the SEC has its own analysis problem – the ability to process up to 40% of a million filings a year, public companies are suffering a (possible permanent) downturn in analyst coverage, media journalists improperly retyping facts about their company and investors reading information that has been filtered and massaged by junior data entry operators with little or no quality control.
As a result of misguided information like this one in ComplianceWeek, IROs/CFOs are still holding on to the view "tell me when I have to do it, and I'll do it, . .otherwise (door slam!)."
No comments:
Post a Comment