XBRL Tag Reference
This is NOT an official reference, just a place where I'm putting some notes.
<gl-cor:accountingEntries >
To me, this is basically the root element. It encloses all the content.
<gl-cor:documentInfo >
This tag contains the information about the document itself. What generated it, when it was created, the accounting period covered, etc.
<gl-cor:entityInformation >
About the company.
<gl-cor:entryHeader >
About the entry - who entered it, when it was entered, which journal it was entered in, comment, entry number.
<gl-cor:entryDetail >
The details! Which account, amount of transaction, posting date, status.
The gl-gen-2006-10-25.xsd file has some really useful enumerations in it:
Here's the enumeration for the postingStatus tag:
I'm sure people will note that XBRL is not the most efficient storage format. There is a lot of redundancy that is not necessary for storage, but remember that XBRL is a reporting language. The data can be stored any which way you like, and at some point if it is in XML format, it can easily be transformed to XBRL via XSLT. Nevertheless, because of the clarity of the specification, it can be used to help model a database. This is really good stuff.
<gl-cor:accountingEntries >
To me, this is basically the root element. It encloses all the content.
<gl-cor:documentInfo >
This tag contains the information about the document itself. What generated it, when it was created, the accounting period covered, etc.
<gl-cor:entityInformation >
About the company.
<gl-cor:entryHeader >
About the entry - who entered it, when it was entered, which journal it was entered in, comment, entry number.
<gl-cor:entryDetail >
The details! Which account, amount of transaction, posting date, status.
The gl-gen-2006-10-25.xsd file has some really useful enumerations in it:
Here's the enumeration for the postingStatus tag:
I'm sure people will note that XBRL is not the most efficient storage format. There is a lot of redundancy that is not necessary for storage, but remember that XBRL is a reporting language. The data can be stored any which way you like, and at some point if it is in XML format, it can easily be transformed to XBRL via XSLT. Nevertheless, because of the clarity of the specification, it can be used to help model a database. This is really good stuff.