

Still, XBRL GL is in no way intended as a substitute or replacement for ERP systems or ETL applications. This sounds a lot like the value proposition of ETL (Extract, Transform, and Load) applications: interoperability between different, and generally incompatible, systems or modules along with the quest for a common format to represent data no matter where it comes from or goes to. In contrast, XBRL GL, the standardized Global Ledger, is a standard format to represent financial and nonfinancial data at the detail level, move the data between different systems and applications, and provide context for drilling down from summary reporting (XBRL FR) to the detail data that flows to it.

This becomes more obvious as the scope of XBRL use is expanded beyond its best known purpose, business reporting, known as XBRL FR.
#Gl iphix net manual#
Project Nunavut, which will be described next month, is the fulfillment.Īt first consideration, many benefits of the eXtensible Business Reporting Language (XBRL) appear to be the same as those of existing, broadly used applications: Centralizing all reporting from disparate modules of the information system, different applications contained within a single enterprise system or a single data warehouse, and eliminating manual reentry and reconciliation of data are all promises of ERP systems. XBRL GL, the standardized Global Ledger, and Web services are the start. In this article, I will discuss the technical and domain standards that can make this solution a possibility. What would be the value to your organization if the data in it could flow together, regardless of the source, and be accessed by any application-even a standard search engine? Not only is it possible, but it’s no more expensive than the solutions that organizations use to consolidate data today, and it can bring benefits far beyond that of an ERP (Enterprise Resource Planning) system alone–perhaps even reducing the need for a new ERP system. Exposing enterprise data: XBRL GL, Web services, and Google, Part 1
