XBRL and Regulatory Reporting in Australia

Written by Bill Donoghoe
Posted on February 1, 2012 Comments
February 1, 2012 | General | Barron King

The use of XBRL in Australia is being led by a government initiative, the Standard Business Reporting (SBR) project. Several hundred regulatory forms from various government agencies now have XBRL 2.1 Taxonomies incorporated into a common architecture.

In the SBR architecture the SBR Definitional Taxonomy layer contains the item, common tuple, dimension and dimension member definitions. Taxonomy files in this layer are used to build the taxonomies for each agency's forms, called Reporting Taxonomies. Each reporting taxonomy defines form specific definitional and presentation linkbases using concepts in the SBR Definitional Taxonomy.

The SBR architecture also provides Web Services where the SOAP message payload is an XBRL instance conforming to a particular reporting taxonomy. This has allowed the development of software packages that provide for electronic submission of the regulatory forms.

At this stage, form submissions to the Australian Prudential Regulation Authority (APRA) are performed using their Direct 2 APRA (D2A) software. This is due to the complex validation infrastructure which compares newly submitted data against values submitted in other forms and reporting periods. XBRL instances can be submitted to APRA using the D2A XBRL import facility.

The initial use of XBRL in Australia's regulatory environment has been as an alternative submission format. This provided a challenge in the development of the SBR XBRL Taxonomies because these taxonomies had to cater for the complexities in the existing forms. For APRA, the scale of the challenge was three hundred and fifty forms.

As an aid to understanding the XBRL taxonomies APRA developed a set of on-line documentation , called Plain English Taxonomy (PET), that exposes the XBRL taxonomy information and how that information maps to the data entry screens in the D2A software. It is envisaged that this documentation will assist reporting entities in adopting XBRL for their regulatory submissions.

The future for the use of XBRL in Australia has been boosted by the recent government announcement that the use of the SBR platform will be mandated for superannuation industry transactions.

The PET documentation can be viewed at: http://apra.gov.au/sbr-pet

More information about the SBR Project is available at: www.sbr.gov.au

 

IMA Promotes XBRL as Basis for Integrated Reporting

Written by Tammy Whitehouse
Posted on January 20, 2012 Comments
January 20, 2012 | General | Barron King

The Institute of Management Accountants is advocating the use of XBRL to facilitate broader adoption of integrated reporting to give stakeholders a deeper understanding of a company’s performance and prospects for future success.

The International Integrated Reporting Council published a discussion paper, Towards Integrated Reporting, Communicating Value in the 21st Century, making the case for integrated reporting and calling for feedback on how to drive acceptance and adoption. The IIRC defines integrated reporting as bringing together material information about an entity’s strategy, governance, performance, and prospects in a way that reflects the commercial, social, and environmental context in which it operates.

Looking well beyond the financial performance conveyed in a typical set of financial statements, an integrated report would provide a clear and concise understanding of how an entity creates and sustains value while also demonstrating good stewardship of its resources, according to the IIRC. The IMA’s XBRL Committee answered the discussion paper by pointing out that XBRL is the perfect tool to facilitate such reporting and drive more widespread adoption of it.

The IMA XBRL Committee is a standing advisory committee reporting to the IMA board, made up of experts in XBRL, internal and external corporate reporting, accounting and other standards, information technology, market adoption, research and academia. The committee says XBRL is already used by companies representing more than 75 percent of the world’s market capitalization for reporting financial information, making it the logical choice for extending the benefits it provides to financial reporting to the full scope of integrated reporting.

Brad J. Monterio, chair of the XBRL committee, said analysts, investors, regulators and even management are increasingly realizing that financial information alone is not enough to present a full picture of market performance. A growing number of hedge funds, venture capital funds, and private equity funds are paying close attention to integrated reporting, he said. “In some cases, they are looking only at companies that prepare this information,” he said.

The IIRC discussion paper is a platform for developing an integrated reporting framework for the global marketplace, Monterio said, so the IMA committee is looking at the framework from an XBRL perspective. “It’s a logical conclusion that if XBRL is becoming the standard for financial information to make it usable, can the same benefits be applied to nonfinancial information?” he said.

The IMA is encouraging the IIRC to develop an XBRL taxonomy in tandem with any integrated reporting framework to facilitate a more streamlined adoption. “CFOs and executive team members need to be aware that integrated reporting is the next stage of corporate reporting and the marketplace is placing value on this information.”

 

 

 

XBRL International Forms Task Force to Develop Taxonomy Guidance

Written by Tammy Whitehouse
Posted on January 12, 2012 Comments
January 12, 2012 | General | Barron King

XBRL International is looking for some XBRL experts, especially those who have experience with taxonomies, to join a task force to help develop and disseminate some taxonomy architecture guidance.

The consortium’s Best Practices Board wants to develop a comprehensive guideline document for taxonomy development to ensure interoperability. The document would be targeted at those working with taxonomy architecting, especially those with limited or no knowledge of XBRL and taxonomies, to relate some common principles of taxonomy architecting.

Shweta Gupta, BPB member who authored the invitation to participate in the Taxonomy Architecture Guidance Task Force , writes that the guideline document would define the various taxonomies that have been built catering to various domains, common and key principles that define architecture of the taxonomy, and the impacts of adopting a specific structure of taxonomy. Such a document is essential given the change face of business reporting and the pace of XBRL adoption occurring worldwide, he writes.

To be successful, the task force should consist of national and jurisdictional taxonomy owners to assure interoperability issues are addressed, ultimately increasing the effectiveness and data re-usability of XBRL, Gupta writes. The board could conduct a preliminary study to outline the various XBRL taxonomies created around the world, providing some high-level comparison of their architecture and properties. Gupta envisions such a study would demonstrate a need for streamlining taxonomy architecture and defining globally accepted practices for taxonomy architectures and development.

The board envisions using XBRL International’s conference in Abu Dhabi as a platform to present a paper on taxonomy diversity and the need for interoperability. Gupta also hopes to see an agreement among taxonomy owners to follow a documented approach. The 24th XBRL International Conference in March will include a taxonomy summit as an attempt to have taxonomy owners and stakeholders address the need for a sustainable taxonomy infrastructure and to seek a commitment to resources to be able to review and approve taxonomies and develop supportive documentation to ensure interoperability.

The most important goal for the task force will be to document the principles that are common across taxonomy profiles, identifying key factors that make the architecture work. Task force member would begin by listing various taxonomies created across XBRL adoption, then study different taxonomy architectures at the national level to create observation documents. The observations will include the task force members’ comments on the architecture, scalability, flexibility, taxonomy domain coverage, etc. Observation documents will then serve as input to the ultimate TAG document.

XBRL experts interested in participating in the task force effort must e-mail tagtf@xbrl.org by Jan. 20, 2012.

 

XBRL: 2011 Sets a Stage for Better Consumption

Written by Qinlin Luo
Posted on January 4, 2012 Comments
January 4, 2012 | General | Barron King

XBRL is revolutionary. But until its benefits are seen, this doesn’t matter.

2011: a review of XBRL in the United States

The year of 2011 marks several milestones in terms of the increase in quantity and the improvement in quality of XBRL data. Such changes will lead to widespread consumption of XBRL data for the year 2012 and beyond.

On the quantity side:

  • Starting June 15, 2011, every company listed in the United States has been required to file their financial statements in XBRL, although many large companies have been doing so for more than two years.
  • Over 7,800 companies have submitted their financial statements in XBRL to the SEC.
  • There are more granular data from the footnotes: XBRL Level 4 detailed footnote tagging makes more this data easily accessible.
  • Many financial analysts will be satisfied if they have the most recent three to five years of financial data. Many large companies have had close to five years of XBRL data available now.

On the quality side:

  • More insights, better guidance: Armed with filing data from over 5,000 first-time XBRL filers in 2011, XBRL US, the FASB, and the SEC have been identifying common errors (see SEC’s Staff Observations) and conducting dozens of trainings, webinars and workshops to help companies prepare their XBRL filings.
  • More accurate and complete: With the expiration of the limited liability provisions for XBRL exhibits two years after their first mandatory submission date, public companies will  be more serious about the accuracy and completeness of XBRL-tagged data (see XBRL Assurance Committee).
  • Smarter XBRL software makes validation easier for preparers.

Consumption: the new theme in 2011

The two biggest XBRL events in 2011 reflected the shift of attention from preparation to consumption.

  • Get More Out of XBRL” is the theme of the 3rd Annual XBRL US National Conference, held between Sept. 26-27 in Nashville, TN.
  • Enhancing Business Performance” is the theme of the 23rd XBRL International Conference, held between Oct. 25-27 in Montreal, Canada.

XBRL Challenge: a new push in consumption

XBRL Challenge is a contest organized by XBRL US to promote the awareness of XBRL. Participants will develop “open source analytical applications for investors that leverage corporate XBRL data”. The deadline to submit the application is Jan. 31, 2012. XBRL US will reward the final winner in February of 2012 with a grand prize of US$20,000.

Getting application developers involved in XBRL is a great idea. They can make consumption by investors easier. They can create a new generation of financial applications.

As a software developer with a finance background, I fully understand the potential of XBRL. The global standard computer language can fundamentally change how financial data is defined, organized, and exchanged. The language defines the attributes of each data and its relationship to others. The standard taxonomy defines common terms used in the dataset. The language and taxonomy are the nuts and bolts for financial application development. Financial data can be dissembled and re-assembled by computer programs. Financial analysts can interact with the richer financial dataset in new ways.

On the other hand, the XBRL standard is complex, even for software developers. Unlike HTML, XBRL uses many XML files, and each serves its own purpose. Grasping XBRL is challenging.

Challenges bring talents. Application developers will make XBRL transparent to end users. Some system or data providers may also make application developers’ life easier.

As Philip Moyer said in a recent XBRL Challenge webinar, there is a critical mass of XBRL data now. Get application developers involved. Let them play with the data. Good things will usually follow.

Let’s expect to see some amazing apps using XBRL data in 2012.

 

FERF Survey Offers Glimpse at XBRL Experiences to Date

Written by Tammy Whitehouse
Posted on December 22, 2011 Comments
December 22, 2011 | General | Barron King

Tier 1 XBRL filers consider the XBRL-related activity to be the biggest bottleneck in their financial reporting function, according to a recent study by the Financial Executives Research Foundation, and they consider the review process to be the most challenging part of the overall XBRL experience.

FERF surveyed more than 300 different public companies on their XBRL experiences so far and discovered Tier 1 companies find the XBRL process to be the biggest headache in their reporting function. They consider the review process and getting educated to be the most challenging aspects of XBRL. Tier 1 companies also noted that mapping and tag selection remains a challenge, but they ranked it behind the review process and education in terms of difficulty.

When ranking their concerns about XBRL generally, Tier 1 companies were most focused in 2011 on the legal liability – and with good reason as the SEC’s limited liability protection for XBRL submissions expired for Tier 1 companies this year. Nearly every Tier 1 company named legal liability as their biggest concern, but close behind they also showed some angst over the cost-benefit equation. Many of the largest companies are still skeptical that investors and other users of financial statement data are finding any real use for the data presented in the XBRL format. They also worry about having adequate resources to get the XBRL filing done on time.

Now that they’ve been at it for a few years, more than 90 percent of Tier 1 companies said their biggest concern about the tagging process specifically is how to get it done more efficiently. Distant behind that primary focus, they’re also thinking about how to control the ongoing cost of XBRL and how to better define and control the process.

Tier 1 companies worry more than smaller companies about the risk of having two different sets of financial data available to investors – that submitted in XBRL, plus their traditional HTML filings. And they worry more than smaller companies about auditor involvement in the XBRL submission.

So far, the SEC does not require an audit of the XBRL submission, although many financial reporting experts speculate it will be required eventually. An increasing number of Tier 1 companies are voluntarily bringing their auditors in to check over the XBRL submission just to add an extra layer of protection as they faced full liability for the accuracy of the filing this year.

Another interesting detail from the study: Tier 1 companies were widely dispersed in terms of how much time they spend on their XBRL submission, whether performing it in-house or outsourcing it to a third party.

Among companies that outsourced the process, 15 percent spent less than 40 hours on XBRL, 31 percent spent 41 to 80 hours, 12 percent spent 81 to 120 hours, and 32 percent spent more than 120 hours. The numbers aren’t significantly different for companies that handled the XBRL process internally: 8 percent spent less than 40 hours, 31 percent spent 41 to 80 hours, 23 percent spent 81 to 120 hours, and 38 percent spent more than 120 hours.

 

 

XBRL Gives New Visibility to Balance Sheet Outliers, Study Suggests

Written by Tammy Whitehouse
Posted on December 15, 2011 Comments
December 15, 2011 | General | Barron King

Companies marching through the paces of detailed XBRL tagging don’t like to hear it, but we’re still just on the cusp of seeing real utility in the repository of data that is starting to build via XBRL. Investors have a long way to go to learn how to use the data to make investment decisions.

Regulators, on the other hand, have had a bigger head start, and the Securities and Exchange Commission is rolling up its sleeves to determine how it can use the data to better regulate capital markets. The SEC has said it is gradually getting more of its accountants up to speed on using XBRL to perform its routine filing reviews.

A recent academic study out of the University of Virginia demonstrates how XBRL data can be mined and managed in a way that makes it much easier to spot outlier elements in balance sheets and income statements. Those outliers can be indicative of any number of things – from investment opportunities to possible fraud, the authors conclude.

Randy Cogill, a professor in systems and information engineering at the University of Virginia, and his assistant, Steve Yang, applied graph similarity measurement to XBRL-rendered financial statements to measure structural differences in those financial statements. Graph similarity measurement has been used in applications such as text mining, pattern recognition, and computer vision, among others.

The authors selected a sample of 44 public companies in the retail and energy sectors for their analysis. They formulated the financial statement similarity measurement problem as a generalized graph similarity problem and constructed a graph similarity metric to measure the similarity of financial statements. They confirmed that the graph similarity metric is sensitive to structural changes in balance sheets, laying a foundation for discovering more important monetary movement patterns in financial statements, the authors say.

Yang said one of the benefits of XBRL data is that it lends itself to such modeling and measurement so that users of the information can extract any information they need. With so much information to digest, it’s the best way to glean meaningful insights. He envisions the findings could be useful for investors, who might build automated tools to help select financial information that is most important to them.

He also sees the benefit for regulators, who can use the tools to identify outliers that command extra attention. “It could be that they will find a deviation is because someone is doing something wrong,” he said, whether intentionally or unintentionally. “They can extract very valuable information from this complex structure.

 

FEI Committee Appeals to the SEC for XBRL Relief

Written by Tammy Whitehouse
Posted on November 30, 2011 Comments
November 30, 2011 | General | Barron King

Given the amount of data that must be tagged and the compressed filing time frames for public companies, XBRL tagging is having an adverse effect on reporting cycle times and review processes. At least that’s the view of the Committee on Corporate Reporting at the Financial Executives International.

Committee Chairman Loretta Cangialosi is appealing to SEC Chairman Mary Schapiro to amend certain XBRL requirements. Cangialosi reminded Schapiro that the committee has raised concerns with the SEC before about the filing time lines and cost-benefit issues related to detailed tagging of footnote information.

True, the SEC has engaged in extensive outreach with preparers, users of financial statements and XBRL service providers, she acknowledged. But the problem hasn’t gone away, she said. There’s just too much data to tag with too little time to properly tag it all and meet filing deadlines, she contends.

“Whether this activity is performed internally or outsourced to third-party service providers, the commitment of resources is significant and the effect on reporting cycle times and review processes has been adverse,” she wrote to Schapiro.

Whether companies perform the tagging in-house or outsource it to third-party service providers, companies are struggling with the reporting cycle times and review processes. “Based on current trends in the volume of disclosure provided in registrant filings, we expect this effect to become more pronounced and costly in the future,” she wrote.

Cangialosi contends only a fraction of the tagged information is actually used by data aggregators and other financial statement users. Instead, those users are primarily interested in tagged information in the basic financial statements, with only a small subset looking at the detailed tagging of specific footnotes.

“We estimate that roughly 75 percent of the volume of XBRL tagging is not actually used by investors and yet the tagging of the entire data set is contributing to delays in filings and diffusion of data preparation and review efforts across the registrant population,” she wrote. Just have a look at the number of hits on corporate websites, Cangialosi contends, where the average is in the single digits.

The committee is calling on the SEC to develop a more focused approach to detailed tagging that limits its application to the core financial statements and the standardized, comparable footnote data that is used by analysts and investors. The group also hopes to see the SEC develop a way for registrations to efficiently and effectively submit a single filing that incorporates XBRL information instead of requiring companies to continue to file both in HTML and XBRL. Cangialosi also calls on the SEC to exempt wholly owned subsidiaries that qualify for abbreviated disclosure rules from detailed tagging, especially when considering their data is consolidated to a parent company’s financial statements.

 

 

XBRL Asks for Input on Abstract Model

Written by Tammy Whitehouse
Posted on November 15, 2011 Comments
November 15, 2011 | General | Barron King

At the recent XBRL International conference in Montreal, the XBRL International consortium released the first draft of its Abstract Model , developed by its Abstract Modelling Task Force (AMTF). The abstract model is meant to establish a common framework for communicating and understanding the XBRL technology.

The abstract model should be of particular interest to software engineers, who are looking for a common language to communicate and understand the XBRL technology, the consortium said. The task force developed the abstract model to give developers a strong foundation for implementing XBRL solutions. The Abstract Model includes use case diagrams, class diagrams, object diagrams, and sequence diagrams. The draft model represents an important element the strategic core vision developed by the XBRL Standards Board to continue the momentum of the XBRL standard

Conor O’Kelly, chairman of XBRL International Standards Board, said the task force welcomes market feedback on the abstract model to help assure it will increase comparability, make XBRL easier to use, and lower barriers to XBRL software development. The working draft represents a meta-model for XBRL 2.1 and Dimensions 1.0, separating the semantics defined in those specifications from their syntactical representation.

In developing the abstract model, the Standards Board envisions it will lead to the production of training materials, the definition of standard API signatures, and the reorganization of existing specifications. Ultimately, the goal is to enhance data comparability and develop application profiles.

The task force acknowledges there have been significant advancements lately in other modules related to the core XBRL 2.1 and Dimensions 1.0 specifications. Specifications such as formulae, rendering, and versioning have all added substantial features and capabilities on top of the two existing core specficiations, the task force said.

The scope of this modeling project, however, was defined at the outset to be inclusive of only the XBRL 2.1 and Dimensions 1.0 specifications, the task force notes. As such, the task force “has been respectful of this scope boundary, and has thus been careful to ensure that all constructs in the abstract model are traceable back to either the XBRL 2.1 or Dimensions 1.0 specifications,” it says.

In addition to publishing the working draft, XBRL International also is looking for a few good candidates to assume a leadership role as chair of the Abstract Modeling Task Force. The new chair will oversee comments and revisions to the working draft of the Abstract Model and will guide the consortium in leveraging the output of the group both internally and in the marketplace. The incoming chair also will advise the Standards Board on future model development.

 

Academic Study Gives Hope for Investor Acceptance of XBRL Technology

Written by Tammy Whitehouse
Posted on November 4, 2011 Comments
November 4, 2011 | General | Barron King

A group of academics studying XBRL acceptance have determined investors are warming up to using XBRL-enabled technology to do their research and make investment decisions.

In their study of the effects of exclusive technology choice on the analysis of financial information, a trio of accounting professors found that 66 percent of nonprofessional investors chose XBRL-enabled technology to complete a financial analysis task because they perceived it would reduce the time it would take for them to complete the task.

The 34 percent of nonprofessional investors who chose spreadsheets over XBRL-enabled technology said they preferred it because of prior experience they had using that technology. No one in the study chose document exchange software, such as PDFs, to complete the task.

The authors – Diane Janvrin of Iowa State University, Robert Pinsker of Florida Atlantic University, and Maureen Francis Mascha of the University of Wisconsin-Oshkosh – said the findings are important because recent evidence suggests investors are slow to adopt XBRL-enabled technology despite regulatory mandates that require companies to submit their financial statements in XBRL.

The study notes that some U.S. companies see the XBRL submission requirement as a compliance exercise, not one that provides any further benefit to the company itself. That suggests XBRL and its underlying technology may be under-utilized in terms of providing increased efficiency, increased reusability, and increased transparency of reported data, the authors said.

Acknowledging some limitations to their study, the authors said participants had only three reporting technology options to choose from, but in real life they likely have others. The experiment assumed a cost-free investing environment, and it failed to take into account that nonprofessional investors in the real world likely would have to purchase XBRL-enabled tools, while PDFs and spreadsheets are probably right at their fingertips. The study also assumed the nonprofessional investors would have a basic working knowledge of the underlying format of financial statements, which is probably not the case for all nonprofessional investors.

The authors say the results of their hypothesis testing provide evidence that nonprofessional investors are drawn to efficiency in performing tasks necessary to make investing decisions, and that means they are more likely to choose XBRL-enabled technology. However, they point out that the study suggests acceptance of the technology, not necessarily usage. The authors recommend future study that would further zero in on other factors or variables that might drive investor use of XBRL-enabled technology.

 

 

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.

 

Can Accounting Standards and XBRL Taxonomies Be Written in Tandem?

Written by Olivier Servais
Posted on September 28, 2011 Comments
September 28, 2011 | General | Barron King

As XBRL continues to evolve and as accounting standards continue to change, we’re working at the IFRS Foundation to integrate the further development of both accounting standards and the IFRS Taxonomy into a seamless process.

The organizational structure for the development of the IFRS Taxonomy is a little different under the International Accounting Standards Board than it is for the GAAP Taxonomy under the Financial Accounting Standards Board. In the U.S. case, FASB is both the accounting standard setter and the keeper of the XBRL Taxonomy. In our case, the IASB is the standard setter; but its overseer, the IFRS Foundation, is responsible for maintaining and updating the IFRS Taxonomy.

This presents us with some tricky, but not insurmountable, logistical challenges in keeping the taxonomy and the accounting standards developing synchronistically. Our XBRL team keeps close tabs on the agenda of the IASB to assure our taxonomy development follows as closely as possible the accounting standard setting process.

The goal is to assure the Taxonomy keeps pace with changes in accounting standards so that companies filing in XBRL aren’t left wondering if the tags they are selecting are currently compliant with their reporting obligations. It seems paramount on us as participants in the regulatory pipeline to assure companies that this is one risk they need not worry to mitigate.

While there was a significant start-up to developing the Taxonomy and bringing it current with existing standards, now the focus is to look around the bend at standards that are in development and develop the tags in tandem with the standard setting process. Today, when the IASB releases a new standard, we can follow them by only about a week with the XBRL tags that are necessary to assure compliance with the new standard.

It leads to a question about whether this standard-setting and taxonomy-writing process might one day in fact be performed by the same entity. It’s a legitimate question, but recent events raise reasonable doubt about whether it is possible.

For example, our XBRL team was recently called upon to produce some 300 additional tags in the IFRS Taxonomy that can be used to describe common reporting practices among IFRS filers. These are tags that reflect things companies commonly include in their financial statements, but that are not necessarily explicitly required under IFRS.

The goal is to give companies using the more principles-based IFRS some additional tags that will minimize their need to create customized extensions, thus enhancing their overall comparability. But as these tags are not reflective of statutory requirements, does it make sense for them to be written by the accounting standard setter itself? In this respect, there may remain an ongoing need for the XBRL Taxonomies to be developed and maintained by bodies other than the accounting standard setters.

 

 

SEC Staff Answers Burning Questions on Units of Measure in XBRL

Written by Tammy Whitehouse
Posted on September 16, 2011 Comments
September 16, 2011 | General | Barron King

Staff members at the Securities and Exchange Commission have parceled out a new bit of XBRL guidance by adding another Q&A to their staff interpretations and frequently asked questions on interactive data disclosures.

The SEC’s Office of Interactive Disclosures focused this time on units of measure and how they are used in interactive data filing. Those staff members apparently are seeing confusion, so they thought it might helpful to explain for the benefit of all who are dealing with XBRL filings.

Depending on the element or tag in the taxonomy that is selected and the amount that is being reported, every amount expressed in an XBRL submission is linked with three things: an “XBRL item type,” an underlying “data type,” and a “unit,” or unit of measure. A common XBRL item type such as “Monetary” can be further described with a data type, as in a “Non Negative Monetary” data type, which excludes negative amounts.

Typically, that is still not enough to completely define a given amount that a company might need to report in its financial statements. That’s where units come into play. Data types use unit types to further define or characterize the information that is being reported. In many cases, the unit is US dollars, but it might also be megawatts, millions of barrels, millions of bushels, or employees.

The staff explains that the “Pure” XBRL item type is used most frequently with elements that describe percentages, rates, and ratios, and it is used most frequently with the “pure” unit. But here’s where the staff has seen some confusion. The SEC is having a hard time comprehending how the pure unit could be used to describe any item type other than the pure XBRL item type, and it can’t see how the pure unit makes sense with anything other than ratios, rates, or percentages.

So here’s the staff’s advice: if you’re thinking of using the pure unit with anything other than a pure XBRL item type, and if you’re thinking of using the pure unit with anything other than a ratio, a rate, or a percentage – don’t do it.

The staff says a standard units registry is expected to be provided in a future version of the Document and Entity Information Taxonomy to further refine direct selections. In the meantime, the filers should select the unit type that most closely fits the item and data type. The Q&A guidance also provides a table showing some common associations among XBRL item types, data types, and units.

 

 

 

 

Convergence Applies to XBRL Architecture, Not Just Accounting Standards

Written by Olivier Servais
Posted on September 9, 2011 Comments
September 9, 2011 | General | Barron King

Convergence is a term we hear a great deal these days to describe efforts to reduce the major differences between International Financial Reporting Standards and other major systems of accounting, especially the Generally Accepted Accounting Principles followed in the United States.

However, convergence can also be used to describe the efforts under way among XBRL teams in various countries. At the IFRS Foundation, our XBRL team is working with the XBRL team at the Financial Accounting Standards Board and the team in Japan developing the Electronic Disclosure for Investors NETwork (EDINET) to reduce significant differences in our respective Taxonomies.

While IFRS and GAAP preparers in particular may find some differences in the way specific tags are named, or specific definitions for those tags are worded, the goal is to assure the tags in the IFRS and GAAP taxonomies for comparable elements are essentially the same. Both XBRL teams have worked through existing standards to develop tags, so now going forward it is our goal to produce tags in tandem with the issuance of standards.

For example, the XBRL teams for IFRS and GAAP meet twice monthly to discuss new standards that are being developed by the FASB and the International Accounting Standards Board. At these sessions, we work to identify and refine the tags that will be necessary to reflect those standards that are developing, mindful to assure they will carry the same essential meanings in both IFRS and GAAP. Then as we update our respective Taxonomies and received feedback and comments on those changes, we can further assess the extent to which they both reflect the accounting standards and assure the greatest possible level of comparability.

We follow a similar process in working with the EDINET team at Japan’s Financial Services Agency, although this system of electronic, data-interactive filing is not quite as mature as XBRL for IFRS and GAAP at this point in time.

The goal is to assure that preparers and users of XBRL-submitted data can use any tool in the marketplace – Hitachi, SAP, Oracle, or any other of the myriad choices that are developing – and encounter no technical difficulties when they switch from filings submitted under different accounting conventions. We want to assure users can navigate whatever tool they’ve chosen without any difference in how the tags function or define financial data submitted under different sets of accounting standards.

As preparers and users of financial statements continue to navigate through XBRL architecture to find and use financial statement data, XBRL teams will be listening for feedback on how well we’ve met the objective of assuring comparability.

 

IFRS Foundation Issues New Interim Release to 2011 Taxonomy

Written by Tammy Whitehouse
Posted on August 30, 2011 Comments
August 30, 2011 | General | Barron King

The IFRS Foundation has published more interim releases for its 2011 IFRS Taxonomy to reflect new accounting standards that have been issued in the past few months. The latest releases focus on fair value measurement, disclosures regarding interests in other entities, other comprehensive income, and employee benefits.

The latest interim release provides new tags related to Presentation of Items of Other Comprehensive Income (amendments to IAS 1) and IAS 19 Employee Benefits, both issued by the International Accounting Standards Board in June. Only a few weeks prior, the IFRS Foundation also published an interim release to provides tags related to IFRS 13 Fair Value Measurement and IFRS 12 Disclosure of Interests in Other Entities, issued by IASB in May.

The Foundation decided to issue the interim release to get the tags developed and accessible to companies for use immediately rather than waiting for an annual taxonomy update. It represents a step in the direction of integrating the development of new tags with the development of the accounting rules they define, a stated goal of the IFRS Foundation, in the hopes that it might minimize the possibility that companies could select inappropriate or obsolete tags to describe emerging accounting requirements. By contrast, the Financial Accounting Standards Board in the United States accepts comments on the U.S. GAAP Taxonomy continually, and seeks comments periodically on prospective taxonomy updates, but issues updates to the taxonomy on an annual basis.

The Foundation earlier published an interim release related to common-practice concepts to reflect disclosures companies commonly make under IFRS. Those tags were developed not necessarily because any specific standard explicitly requires the disclosures. Instead, the disclosures are common enough that having tags associated with them will identify them as comparable to other like disclosures made by other companies, making all XBRL-submitted information more comparable.

The U.S. Securities and Exchange Commission in particular has urged the IFRS Foundation to expand the IFRS Taxonomy to make IFRS financial statements submitted in U.S. capital markets more comparable. So far, the SEC has not yet endorsed an IFRS taxonomy for IFRS filers in the United States, leaving those companies dangling under a requirement to submit their financial statements in XBRL with no approved method for doing so. The SEC has not released those companies from the XBRL submission obligation, but has indicated it will not take enforcement action against IFRS filers that do not meet the 2011 XBRL submission requirement.

The IFRS Taxonomy interim releases allow entities to report electronically using the latest IFRS without needing to create custom extensions or risk making an erroneous tag selection. The IFRS Foundation says the additional items in the latest interim release are consistent with the XBRL architecture of the 2011 taxonomy as described in its 2011 taxonomy guide and its Global Filing Manual. All interim releases are due to be incorporated into the 2012 IFRS Taxonomy, which is scheduled to be published in the first quarter of 2012.

 

ISACA/IFAC Paper Provides How-To Guide on Leveraging XBRL

Written by Tammy Whitehouse
Posted on August 24, 2011 Comments
August 24, 2011 | General | Barron King

Looking past the compliance exercise, some leading companies are starting to take note of the effectiveness, efficiency, and reliability of management reporting that is inherent in XBRL. The International Federation of Accountants and ISACA have teamed up to produce a paper, Leveraging XBRL for Value in Organizations, that is loaded with ideas on how to leverage XBRL, not just live with it.

The paper points out how companies can align the internal measurement and communication of key performance metrics with the external compliance requirements by embedding XBRL into their internal processes. When using the same technology to generate and transmit information inside the organization as they already use to comply with external reporting requirements, they reduce overall costs. And when they use the same definitions for important metrics both internally and externally, they minimize risk and better align internal and external communications.

ISACA and IFAC develop the paper to provide accounting and assurance professionals with guidance they can rely on to leverage value from XBRL initiatives and compliance requirements, said Roger Debreceny, a member of ISACA and co-developer of the XBRL paper. “Understanding how to embed XBRL within an organization’s information processes can enhance management communication, increasing the value of the information used within an enterprise,” he said.

Roger Tabor, chair of IFAC’s Professional Accountants in Business Committee, said the paper serves as a starting point to integrate XBRL into a company’s information management processes. “Many organizations have not yet realized how useful XBRL can be for them,” he said.

XBRL is growing as a mandatory reporting method in countries around the world for a variety of purposes. In addition to the financial reporting requirement to various securities regulators, it is used for sharing data among regulatory services, for various types of reporting to government agencies and banks, for statistical reporting, for submitting credit risk reports to commercial banks, and for corporate tax reporting. Inside some corporate organizations, XBRL is becoming the basis for some internal management reporting, statistical reporting, internal audit and other internal control functions, and it’s being used to integrate dispersed reporting and accounting systems.

IFAC and ISACA point out that the extensibility and flexibility that are inherent to XBRL make it adaptable to a wide variety of different uses and requirements. Companies can automate data collection in ways never before imaginable. As an example, data from different company divisions with different accounting systems can be assembled quickly, inexpensively, and efficiently if the sources of data all originate through XBRL. Once it is gathered there, it can be sliced and diced into any number of reports with a minimum of effort, using various subsets of the data.

And the paper shares an important reminder about the accuracy that comes from such automation. Once the data enters the XBRL system, it can be sorted and sifted in innumerable ways with no re-keying of information, which can naturally lead to errors and misinterpretations, which ultimately increases costs.

 

 

XBRL in Chile: On the Road to Transparency?

Written by Isabel Villavicencio
Posted on August 17, 2011 Comments
August 17, 2011 | General | Barron King

Around 2005, the SBIF (Superintendency of Banks and Financial Institutions) and the SVS (Superintendency of Securities and Insurance) started to discuss XBRL. They were the first Chilean institutions to do so.

Six years later, the SBIF has made no concrete progress; it is still just talking about XBRL. Banco Central de Chile (Central Bank of Chile) and Bolsa de Comercio de Santiago (Santiago Stock Market) have expressed interest in XBRL, but that is the extent of their involvement.

Meanwhile, the SVS implemented the Chilean taxonomies based on the IFRS (International Financial Reporting Standards) Foundation, starting with SVS CL-CI 2008. However, XBRL technology is being used only by a few software companies and some advanced users. It is still far from reaching the promised level of transparency for financial information.

Take, for example, the recent La Polar crisis of confidence in retail markets. La Polar (Empresas La Polar SA ) is a regulated retail company that mishandled customer debt for years. This mishandling inflated its stock prices. Yet La Polar used XBRL to report to SVS for the last two years.

Who validated La Polar's reporting? Who audited its financial statements? Why did nobody detect its crisis, whether before or after XBRL was used in its financials? Given the lack of effect that XBRL had on La Polar, how can we say that transparency bestows any advantage at all?

Just making taxonomies and collecting files does not produce a more transparent market. SVS established conditions for regulated companies to report in XBRL, but it did not monitor the process as it affected real numbers and real companies.

Before IFRS, the SVS provided regulated companies with free software tools such as the SEIL for filling out forms. The reporting format was pretty much ad hoc. The SVS then took the files generated by these software tools and turned them into .pdf files.

Currently, because XBRL is an open and international standard, every regulated company has to provide its own reporting tool. The SVS posts announcements on the IFRS section of its web, waiting for companies to take up the XBRL. Still, as soon as deadlines arrive, crises spring up everywhere.

  • Some companies objected to XBRL's "complexity," saying that XBRL allows only basic financial statements to be filed, not the notes Some companies said they were able to report only the basic financial statements, not the notes, due the complexity of the XBRL implementation for notes– and the notes contain the largest part of IFRS taxonomies. The SVS accepted this and allowed the notes to be optional for all companies. Only one of several hundred companies sent notes in any case. Thus the SVS lost relevant information that it used to gather with the aid of SEIL tools and disseminated to investors as well as the general public. Transparency, in this case, translated to less information.
  • Some companies sent their reports only in .pdf form, because they had heard news only of IFRS, not of XBRL.
  • Some companies used demo XBRL tools and some used IT consultants to prepare their XBRL reports. Unfortunately, the data in the resulting reports had the wrong information.
  • In a very few cases, companies sent XBRL financial reports in .pdf form. Only in a few cases the companies sent information consistent in both formats: PDF and XBRL.

Were there any penalties for companies that did not send their reports? How about penalties for companies that sent the wrong information? Did the SVS admit any mistakes in their strategies or change them? While I was there, none of this occurred.

I would like to see the SVS give XBRL the importance that it deserves. However, I doubt that will happen until their customers, their users, and the public call out for it. I hope that their users don't wait for more La Polar-type tragedies before they make their voices heard, making politicians seethe with rage calling for greater transparency – but without admitting to their earlier laziness and neglect.

 

XBRL on the new Frontier: Integrated Reporting in Healthcare

Written by James St.Clair
Posted on August 10, 2011 Comments
August 10, 2011 | General | Barron King

The global phenomenon that is XBRL in financial reporting has at times dominated, if not monopolized, the discussions of XBRL’s potential to improve transparency and interoperability  in any industry for financial and performance purposes.  To that end, probably no other industry is in the midst of a financial and performance revolution like healthcare.

While “Healthcare reform” has been a white-hot topic in the US for the last 2 years, the revolution began before that, and has affected every country in the world. Industrialized nations as a whole have recognized several critical trends in global health:

  • The explosion of Information Technology and its impact on healthcare delivery, especially mobile technology
  • The spiraling costs of delivering an episode of care, in all countries, and the limits of Entitlement and National Insurance programs to support them.
  • The changes in the quality and availability of healthcare, and in global demographics that affect that availability.

The Health Information Management Systems Society (HIMSS) has been actively involved in the revolution in health technology, and joined forces with the Medical Banking Institute (MBI) after recognizing the significant relationship between global finance and global health delivery. The MB Tech Integration Task Force is an initiative to research and analyze "the latent integration of banking technology, infrastructure and credit with healthcare administrative operations" and define the need and technical avenues of the integration of data represented in our concept of a “Medical Banking Information Supply Chain”.  Leveraging the definition of this supply chain such that may be represented in XBRL, is intended to facilitate interoperability in a way that is open, flexible and international in scope.

The benefits may include dramatic reductions in development of proprietary applications and interchange standards for software vendor, industry groups, and government agencies alike. Also, everyone will benefit from increased services from care providers and financial institutions due to more flexible interchange formats and reduced development efforts. Lastly, care providers, governments, NGOs, relief agencies, financial institutions and other system developers will enjoy reduced development costs and schedules when integrating their systems with analysis, reporting and compliance systems.

 

2011 – New XBRL Requirements For All SEC Filing Companies

Written by Gary Purnhagen
Posted on July 29, 2011 Comments
July 29, 2011 | General | Barron King

A major milestone in the SEC’s XBRL mandate will be achieved in August. It will be the first time that all companies with a 12/31 fiscal year-end date will be required to submit XBRL exhibits with their second quarter 10-Q. While all Large Accelerated Filers (LAF) companies were required to submit XBRL exhibits after June 15, 2010, all remaining filers, including smaller reporting companies will now also be required to begin submitting these exhibits.

The Securities and Exchange Commission’s XBRL mandate grouped all public companies into three groups, or tiers, based on their filing status. The first tier, Large Accelerated Filers (LAF) with a public float over $5 Billion (approx. 500 companies) were first required to begin submitting XBRL exhibits back in 2009. In 2010, all remaining LAFs were phased into the XBRL mandate (approx. 1,000 companies). This year, approximately 7,000 companies will begin submitting XBRL exhibits. Each of these groups will be addressing a new aspect of the rules.

Tier Three: All non-LAF companies are in this group. For the first twelve months after June 15, 2011, these companies are required to tag all line items in their primary financial statements and “block” tag their footnotes and schedules. Ideally, in preparation for the XBRL requirements with their second quarter 10-Q filing in late August, they have already completed their selection of their tags that accurately reflect the accounting concepts behind each line item in their primary financial statements, and went through a “practice run” with their last 10-Q filing in May. This would give them a good idea as to the impact that this additional requirement will have on their filings. It is important to remember that these companies will still have to file their documents in the HTML or ASCII format, and that they will have to allow for more time to create the XBRL format. Therefore, they will have to put “pencils down” earlier than they may have been accustomed to in the past.

Tier Two: LAF companies that have a public float under $5 Billion fall into this category, and they began submitting XBRL exhibits last year in 2010. As of June 15, 2011, they are now required to begin tagging their footnotes and schedules on a detailed level. Besides tagging their primary financial statements, they will also be required to tag:

  • All Accounting policies in the Significant Accounting Policies Footnote
  • Each table within each footnote as a separate block of text
  • Within each footnote, each amount (i.e. monetary value, percentage, and number) separately

This additional tagging requirement will substantially increase the number of tags required in the XBRL exhibits and the amount of time required to create them. Companies required to submit these detailed tagged XBRL exhibits will need to know just how much additional time is required to create them with the additional tags. On average, the jump in the number of tags from the first year is 150 tags to 900.

Tier One: The LAF companies that have been submitting XBRL exhibits since 2009, and began tagging their footnotes and schedules on a detailed level last year, will now lose their limited liability protection for filings after June 15, 2011. The SEC rules allowed this limited liability protection for 24 months after a registrant was phased into the XBRL mandate. This clause in the rules provided protection against federal securities laws if the XBRL exhibits did not comply with the XBRL rules, as long as it was deemed that the company did not deliberately attempt to mislead the public. Unfortunately, this is quite vague, and these companies should discuss this with their Auditors and Legal counsel.

So while the SEC’s XBRL mandate has a multi-year phase-in of the requirements; at this point all companies that have SEC filing requirements are now required to submit XBRL exhibits when they are filing new financials.