Search Posts

XBRL-GL for Audit Data Collection

Posted on | By Nobuyuki | No comments

Visits: 62

Nobuyuki SAMBUICHI

ISO/TC295 Audit data services/SG1 Semantic model Convener

The AICPA (American Institute of Certified Public Accountants) has established a way to connect specific fields in a standard table file with elements in an XML format called XBRL-GL. This is done to facilitate audits and data collection processes.

The AICPA has created a set of standards known as the Audit Data Standard (ADS), which outlines how each element in the data should be connected to the XBRL-GL format. Additionally, the ISO 21378:2019 Audit Data Collection (ADC) standard was developed with strong support from the AICPA ADS.

To create a clear and meaningful model for the ISO 21378 standard, it is important to establish a mapping between the ADC and XBRL-GL formats. This mapping specifies how the elements in ADC relate to the elements in XBRL-GL.

1. Mapping between ADC, ADS and XBRL-GL

1.1. Mapping table

Below is a table that provides the specific mappings between the elements in ADC and XBRL-GL.

Table 1. Mapping between ADC, ADS and XBRL-GL

No.

Name

Datatype

Level

ADS

XBRL-GL

1

Journal_ID

String

1

Journal_ID

gl-cor:entryNumber

2

Journal_Number

String

1

gl-cor:uniqueID

3

GL_Account_Number

String

1

GL_Account_Number

gl-cor:accountMainID

4

Fiscal_Year

String

1

Fiscal_Year

gl-bus:fiscalYearEnd Note that gl-bus:fiscalYearEnd is at a higher level of the XBRL GL hierarchical structure than the detail lines are, an efficient structuring would include pre-grouping by bus:fiscalYearEnd

5

Accounting_Period

String

1

Period

gl-bus:postingCode

6

Effective_Date

Date

1

Effective_Date

gl-cor:postingDate

7

Journal_Line_Number

String

1

Journal_ID_Line_Number

gl-cor:lineNumber

8

JE_Type_Code

String

2

–

gl-cor:entriesType

9

JE_Header_Description

String

1

JE_Header_Description

gl-cor:entryComment

10

JE_Line_Description

String

1

JE_Line_Description

gl-cor:detailComment

11

Source_Code

String

1

Source

gl-cor:SourceJournalID (fixed/enumerated list) or gl-cor:sourceJournalDescription (free form)

12

Bill_Number

String

2

gl-cor:documentNumber

13

Bill_Type_Code

String

2

gl-cor:documentType

14

Bill_Date

Date

2

gl-cor:documentDate

15

Quantity

Decimal

2

gl-bus:measurableQuantity

16

UOM_Code

String

2

gl-bus:measurableUnitOfMeasure

17

Unit_Price

Decimal

2

gl-bus:measurableCostPerUnit

18

Functional_Amount

Decimal

1

Amount

gl-cor:amount

19

Functional_Currency_Code

String

1

Amount_Currency

gl-muc:amountCurrency

20

Reporting_Amount

Decimal

2

Reporting_Amount

gl-cor:amountTriangulationAmount

21

Reporting_Currency_Code

String

2

Reporting_Amount_Currency

gl-muc:amountTriangulationCurrency

22

Local_Amount

Decimal

2

Local_Amount

gl-muc:amountOriginalAmount

23

Local_Currency_Code

String

2

Local_Amount_Currency

gl-muc:amountOriginalCurrency

24

Transaction_Amount

Decimal

2

–

–

25

Transaction_Currency_Code

String

2

–

–

26

Settlement_Method_Code

String

2

–

–

27

Credit_Debit_Indicator

String

1

Amount_Credit_Debit_Indicator

gl-cor:debitCreditCode

28

Reversal_Indicator

String

1

Reversal_Indicator

gl-usk:reverse true = entry is to be reversed false with gl-usk:reversingDate = provided = entry is a reversal not provided = none of the above.

29

Reversal_Journal_ID

String

2

Reversal_Journal_ID

gl-usk:reversingStdId

30

Cancellation_Sign

Boolean

2

–

–

31

Created_User_ID

String

1

Entered_By

gl-cor:enteredBy

32

Created_Date

Date

1

Entered_Date

gl-cor:enteredDate

33

Created_Time

Time

2

Entered_Time

–

34

Approved_User_ID

String

2

Approved_By

gl-cor:entryResponsiblePerson

35

Approved_Date

Date

2

Approved_Date

gl-usk:nextDateRepeat

36

Posted_User_ID

String

2

–

–

37

Account_Segment_Employee

String

2

gl-cor:accountSubID withgl- cor:accountSubType of “Project”

38

Account_Segment_Project

String

2

gl-cor:accountSubID withgl- cor:accountSubType of “ank Account”

39

Account_Segment_Bank_Account

String

2

gl-cor:accountSubID withgl- cor:accountSubType of “ccount Segment”

40

Account_Segment_X

String

2

gl-cor:accountSubID withgl- cor:accountSubType of “Business_Unit”

41

Business_Segment_X

String

1

Business_Unit_Code

gl-cor:accountSubID withgl- cor:accountSubType of “Business_Unit”

–

–

–

–

Last_Modified_By

gl-bus:enteredByModified

–

–

–

–

Last_Modified_Date

gl-usk:lastDateRepeat

–

–

–

–

Segment01

XBRL GL tracks hierarchy ID, hierarchy description, and hierarchy type, so it can track code NA, description N. America, and type global area usinggl-cor:accountSubID,gl-cor:accountSubDescription, andgl-cor:accountSubType, respectively. Interrelations and hierarchies are captured bygl-cor:parentSubAccountType (What is the hierarchy type this unit rolls up to?).

–

–

–

–

Segment02

See above

–

–

–

–

Segment03

See above

–

–

–

–

Segment04

See above

–

–

–

–

Segment05

See above

1.2. What is the European Triangular currency?

User

What is the European Triangular currency?

ChatGPT

In Europe, the term “triangular amount” refers to a method of calculating the local currency equivalent of a transaction involving three currencies. It is commonly used when there is a transaction between two entities in different countries, and a third currency is involved as an intermediary or reference currency.

Here’s how it works:

  1. Functional Currency: Each entity involved in the transaction has its own functional currency, which is the primary currency used for its financial reporting and operations.

  2. Transaction Currency: The currency in which the transaction is denominated or conducted. This is the currency mentioned in the transaction document, such as an invoice.

  3. Triangular Currency: This is the third currency used as a reference point to calculate the local currency equivalent of the transaction. Often, the euro is used as the triangular currency in Europe due to its widespread use and stability.

To determine the triangular amount in Europe, the following steps are typically followed:

  1. Convert Transaction Currency to Triangular Currency: The transaction currency amount is converted to the triangular currency using the applicable exchange rate between the two currencies.

  2. Convert Triangular Currency to Local Currency: The triangular currency amount obtained in the previous step is further converted to the local currency using the exchange rate between the local currency and the triangular currency.

By performing these currency conversions, the triangular amount represents the local currency equivalent of the original transaction. It helps reconcile different currencies involved in the transaction and ensures consistency in financial reporting across entities operating in different countries within Europe.

It’s worth noting that the specific calculation methods and exchange rates used may vary depending on the relevant accounting regulations and practices in each country.

User

What is the reporting currency in this scenario?

ChatGPT

In the scenario mentioned, the reporting currency refers to the currency in which the financial results and statements of the entity are presented to stakeholders, such as investors, regulators, or management. It is the currency used for external reporting purposes.

The reporting currency is typically determined based on the entity’s headquarters or the country where it is primarily operating. It is chosen to provide meaningful and consistent financial information to users who may have different currencies or reporting requirements.

In the context of the triangular amount calculation, the reporting currency is not directly involved. The focus is primarily on the functional currency, transaction currency, and the triangular currency. The reporting currency would come into play when presenting the financial statements and results to stakeholders.

For example, let’s consider a multinational company with headquarters in the United Kingdom (UK) and operations in multiple countries across Europe. The functional currency for the UK headquarters would be the British Pound (GBP), while subsidiaries in other European countries might have their respective functional currencies (e.g., Euro for a subsidiary in Germany). In a transaction between the UK headquarters and a subsidiary in Germany, the transaction currency might be Euro, and the triangular currency used for conversion purposes could still be Euro. However, when presenting consolidated financial statements to stakeholders, the reporting currency would typically be the British Pound (GBP) since it reflects the entity’s headquarters and is the currency used for external reporting.

It’s important to note that the reporting currency can vary based on an entity’s circumstances, such as its jurisdiction, listing requirements, or the preferences of management and stakeholders.

1.3. Bookkeepping in the subsidiary

User

Which currency is used to record book? Local currency, transaction currency, functional curremcy, reporting currency, triangular currency?

Explain with the following scenario. An entity is in England reporting their annual report in GBP.

The purchase by the subsidialy in Swiss the transaction based on Schweizer Franken from France Factory. How they book journal entry?

ChatGPT

In the scenario you described, where an entity is based in England and reports their annual report in GBP (British Pound), let’s consider the purchase made by their subsidiary in Switzerland, with the transaction denominated in Swiss Francs (CHF) from a factory in France.

In this case, the different currencies relevant to recording the book entry would be:

  1. Transaction Currency: The transaction currency is Swiss Francs (CHF) since the purchase was made by the subsidiary in Switzerland.

  2. Functional Currency: The functional currency of the subsidiary in Switzerland would typically be the Swiss Franc (CHF). It represents the primary currency used for their financial reporting and operations. Therefore, the subsidiary’s books would record the transaction in their functional currency (CHF).

  3. Reporting Currency: The reporting currency of the entity based in England is GBP (British Pound) since their annual report is prepared and presented in GBP. The subsidiary’s transaction would need to be translated into GBP for consolidation purposes when preparing the consolidated financial statements.

Now, let’s consider how the journal entry would be booked for this scenario:

When the subsidiary in Switzerland makes the purchase in Swiss Francs (CHF) from the factory in France, the journal entry would typically be recorded in the subsidiary’s functional currency (CHF). The specific accounts debited and credited would depend on the nature of the purchase (e.g., inventory, accounts payable).

For example, the journal entry might look as follows:

Debit: Inventory (CHF)
Credit: Accounts Payable (CHF)

This initial journal entry would reflect the purchase transaction in the subsidiary’s functional currency (CHF).

Later, during the consolidation process, when preparing the consolidated financial statements, the subsidiary’s books would need to be translated into the reporting currency (GBP). This translation would involve converting the subsidiary’s functional currency amounts (CHF) to GBP using the appropriate exchange rate. The resulting amounts would then be included in the consolidated financial statements in GBP.

It’s important to note that the triangular currency concept mentioned earlier would not be directly applicable in this scenario, as it typically relates to transactions involving three currencies, whereas this purchase involves only two currencies (CHF and GBP).

User

What if the purchase transaction from France is in EUR?

ChatGPT

If the purchase transaction from France is denominated in Euros (EUR), the accounting treatment would be slightly different. Let’s consider the scenario where the subsidiary in Switzerland makes a purchase in Euros from a factory in France.

In this case, the relevant currencies for recording the book entry would be:

  1. Transaction Currency: The transaction currency is Euros (EUR) since the purchase is made in Euros from the factory in France.

  2. Functional Currency: The functional currency of the subsidiary in Switzerland is typically the Swiss Franc (CHF). The subsidiary’s books would record the transaction in their functional currency (CHF). However, the subsidiary may need to keep records or have an internal reporting in Euros for transactional purposes.

  3. Reporting Currency: The reporting currency of the entity based in England is GBP (British Pound) since their annual report is prepared and presented in GBP. The subsidiary’s transaction would need to be translated into GBP for consolidation purposes when preparing the consolidated financial statements.

Now, let’s consider how the journal entry would be booked for this revised scenario:

When the subsidiary in Switzerland makes the purchase in Euros (EUR) from the factory in France, the journal entry would typically be recorded in the subsidiary’s functional currency (CHF). The specific accounts debited and credited would depend on the nature of the purchase.

For example, the journal entry might look as follows:

Debit: Inventory (CHF)
Credit: Accounts Payable (CHF)

The initial journal entry would reflect the purchase transaction in the subsidiary’s functional currency (CHF), even if the transaction was conducted in Euros (EUR).

During the consolidation process, when preparing the consolidated financial statements, the subsidiary’s books in CHF would need to be translated into the reporting currency (GBP). Additionally, the subsidiary’s EUR amounts would also need to be converted into GBP.

To achieve this, the subsidiary’s Euro-denominated transaction would first be converted into the functional currency (CHF) using the applicable exchange rate. Then, the CHF amount would be translated into GBP using the appropriate exchange rate.

The resulting amounts in GBP would be included in the consolidated financial statements.

It’s important to note that the triangular currency concept would not be directly applicable in this scenario since there are only two currencies involved (EUR and GBP). The functional currency (CHF) is the primary currency for the subsidiary’s financial reporting, while the reporting currency (GBP) is used for the consolidated financial statements.

User

Do we need to book amount in transaction currency for journal entry?
Avove example in a subsidiary books transaction in functional currency not transaction currency.
When do we need posting functional currency in journal entry?

ChatGPT

In accounting, the decision to book amounts in the transaction currency or functional currency for journal entries depends on the specific circumstances and accounting principles followed by an organization. Here’s an explanation of when the functional currency might be used in journal entries:

Transaction Currency: The transaction currency represents the currency in which a specific transaction is denominated or conducted. It is the currency mentioned in the transaction document, such as an invoice or purchase order. In some cases, journal entries may be recorded directly in the transaction currency, especially when there are specific reporting or regulatory requirements to do so.

Functional Currency: The functional currency is the primary currency used by an entity for its financial reporting and operations. It is determined based on various factors, including the country of operation, economic environment, and management’s judgment. Journal entries are typically recorded in the functional currency to ensure consistency in financial reporting and internal controls.

In the example you mentioned with the subsidiary, the journal entry was recorded in the functional currency (e.g., Swiss Francs) rather than the transaction currency (e.g., Euros). This is a common practice, especially when the functional currency is different from the transaction currency. By recording transactions in the functional currency, it allows for better integration with the overall financial reporting and internal control systems of the subsidiary.

The decision to post amounts in the functional currency in a journal entry can be influenced by factors such as:

Regulatory requirements: Local accounting regulations or tax laws may specify the currency in which certain transactions should be recorded or reported.
Consolidation purposes: When preparing consolidated financial statements, transactions of subsidiaries with different functional currencies may need to be translated into the reporting currency (e.g., the currency of the parent company).
Management reporting: If an entity’s internal reporting and analysis are performed in the functional currency, it may be beneficial to record journal entries in that currency for consistency and ease of analysis.
It’s important to consult the applicable accounting standards, regulatory requirements, and internal policies of your organization to determine the specific currency in which journal entries should be recorded. Additionally, working with a qualified accountant or financial professional can provide further guidance tailored to your specific situation.

2. Example instance document

The first reccomendation in 2007 designed by Nobu.
XBRL Global Ledger Framework (RECOMMENDATION)

Subsequent updates.
XBRL Global Ledger Taxonomy Framework 2015

The followiing example file is downloadable from above “XBRL Global Ledger Taxonomy Framework 2015“

2.1. Sample Journal entries file for XBRL Global Ledger Framework with annotations Version 1.0.91021.1

This file contains data fields considered very important to representing its subject. Annotations have been provided for the “most important” of those fields. XBRL GL has many other fields that could be helpful in expressing the information, but have been omitted because their presence is more circumstantial. This file was created for educational purposes only, does not represent real company data and we welcome suggestions on improvement. Contact xbrlgl@xbrl.org with comments.

<?xml version="1.0" encoding="UTF-8"?>
<xbrli:xbrl xmlns:xbrli="http://www.xbrl.org/2003/instance"
	xmlns:xbrll="http://www.xbrl.org/2003/linkbase"
	xmlns:xlink="http://www.w3.org/1999/xlink"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:gl-cor="http://www.xbrl.org/int/gl/cor/2015-03-25"
	xmlns:gl-muc="http://www.xbrl.org/int/gl/muc/2015-03-25"
	xmlns:gl-bus="http://www.xbrl.org/int/gl/bus/2015-03-25"
	xmlns:gl-plt="http://www.xbrl.org/int/gl/plt/2015-03-25"
	xmlns:iso4217="http://www.xbrl.org/2003/iso4217"
	xmlns:iso639="http://www.xbrl.org/2005/iso639" xsi:schemaLocation="http://www.xbrl.org/int/gl/plt/2015-03-25 ../plt/case-c-b-m-u-t/gl-plt-all-2015-03-25.xsd"> // (1)
	<xbrll:schemaRef xlink:type="simple" xlink:arcrole="http://www.w3.org/1999/xlink/properties/linkbase" xlink:href="../plt/case-c-b-m-u-t/gl-plt-all-2015-03-25.xsd"/>
	<xbrli:context id="now"> // (2)
		<xbrli:entity>
			<xbrli:identifier scheme="http://www.xbrl.org/xbrlgl/sample">SAMPLE</xbrli:identifier>
		</xbrli:entity>
		<xbrli:period> // (3)
			<xbrli:instant>2004-10-03</xbrli:instant>
		</xbrli:period>
	</xbrli:context>
	<xbrli:unit id="usd"> // (4)
		<xbrli:measure>iso4217:USD</xbrli:measure>
	</xbrli:unit>
	<xbrli:unit id="NotUsed">
		<xbrli:measure>pure</xbrli:measure>
	</xbrli:unit>
	<gl-cor:accountingEntries> // (5)
		<gl-cor:documentInfo> // (6)
			<gl-cor:entriesType contextRef="now">journal</gl-cor:entriesType> // (7)
			<gl-cor:uniqueID contextRef="now">001</gl-cor:uniqueID> // (8)
			<gl-cor:language contextRef="now">iso639:en</gl-cor:language>
			<gl-cor:creationDate contextRef="now">2005-07-05</gl-cor:creationDate> // (9)
			<gl-bus:creator contextRef="now">XBRL GL Working Group</gl-bus:creator>
			<gl-cor:entriesComment contextRef="now">A best practice journal entries instance document</gl-cor:entriesComment> // (10)
			<gl-cor:periodCoveredStart contextRef="now">2005-06-01</gl-cor:periodCoveredStart> // (11)
			<gl-cor:periodCoveredEnd contextRef="now">2005-06-30</gl-cor:periodCoveredEnd>
			<gl-bus:sourceApplication contextRef="now">XABRA</gl-bus:sourceApplication>
			<gl-muc:defaultCurrency contextRef="now">iso4217:usd</gl-muc:defaultCurrency>
		</gl-cor:documentInfo>
		<gl-cor:entityInformation> // (12)
			<gl-bus:organizationIdentifiers> // (13)
				<gl-bus:organizationIdentifier contextRef="now">ABC Company</gl-bus:organizationIdentifier>
				<gl-bus:organizationDescription contextRef="now">Company Name</gl-bus:organizationDescription>
			</gl-bus:organizationIdentifiers>
		</gl-cor:entityInformation>
		<gl-cor:entryHeader> // (14)
			<gl-cor:enteredBy contextRef="now">Otto Wellwood</gl-cor:enteredBy>
			<gl-cor:enteredDate contextRef="now">2005-07-01</gl-cor:enteredDate>
			<gl-cor:sourceJournalID contextRef="now">gj</gl-cor:sourceJournalID> // (15)
			<gl-bus:sourceJournalDescription contextRef="now">JE</gl-bus:sourceJournalDescription> // (16)
			<gl-cor:entryType contextRef="now">standard</gl-cor:entryType> // (17)
			<gl-cor:entryNumber contextRef="now">50</gl-cor:entryNumber> // (18)
			<gl-cor:entryComment contextRef="now">The comment for this entry</gl-cor:entryComment> // (19)
			<gl-cor:entryDetail> // (20)
				<gl-cor:lineNumber contextRef="now">1</gl-cor:lineNumber> // (21)
				<gl-cor:account> // (22)
					<gl-cor:accountMainID contextRef="now">10100</gl-cor:accountMainID> // (23)
					<gl-cor:accountMainDescription contextRef="now">Rent</gl-cor:accountMainDescription> // (24)
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode> // (25)
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType> // (26)
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">500</gl-cor:amount> // (27)
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode> // (28)
				<!-- <gl-cor:signOfAmount contextRef="now"/> --> // (29)
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate> // (30)
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">1130</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Rettaler Property Ltd</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">V</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus> // (31)
				<!-- <gl-cor:detailComment contextRef="now"/> --> // (32)
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">2</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10200</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Chequing</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">500</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">1130</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Rettaler Property Ltd</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">V</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
		</gl-cor:entryHeader>
		<gl-cor:entryHeader>
			<gl-cor:enteredBy contextRef="now">Vanessa Witherspoon</gl-cor:enteredBy>
			<gl-cor:enteredDate contextRef="now">2005-07-03</gl-cor:enteredDate>
			<gl-cor:sourceJournalID contextRef="now">gj</gl-cor:sourceJournalID>
			<gl-bus:sourceJournalDescription contextRef="now">JE</gl-bus:sourceJournalDescription>
			<gl-cor:entryType contextRef="now">standard</gl-cor:entryType>
			<gl-cor:entryNumber contextRef="now">431</gl-cor:entryNumber>
			<gl-cor:entryComment contextRef="now">The comment for this entry</gl-cor:entryComment>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">1</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10300</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Undeposited Funds</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">435.84</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">9098</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Ludwick, Dave</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">C</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">invoice</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">2</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10400</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Retail Sales</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">229</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">9098</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Ludwick, Dave</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">C</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">invoice</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">3</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10500</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Inventory Asset</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">100</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">9098</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Ludwick, Dave</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">C</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">invoice</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">4</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10600</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Cost of Goods Sold</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">100</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">9098</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Ludwick, Dave</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">C</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">invoice</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">5</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10400</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Retail Sales</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">149.99</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">9098</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Ludwick, Dave</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">C</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">invoice</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">6</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10500</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Inventory Asset</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">80</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">9098</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Ludwick, Dave</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">C</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">invoice</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">7</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10600</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Cost of Goods Sold</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">80</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">9098</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Ludwick, Dave</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">C</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">invoice</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">8</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10700</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">GST Payable</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">26.53</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">9098</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Ludwick, Dave</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">C</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">invoice</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">9</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10800</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">PST Payable</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">30.32</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">9098</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Ludwick, Dave</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">C</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">invoice</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
		</gl-cor:entryHeader>
		<gl-cor:entryHeader>
			<gl-cor:enteredBy contextRef="now">Otto Wellwood</gl-cor:enteredBy>
			<gl-cor:enteredDate contextRef="now">2005-07-05</gl-cor:enteredDate>
			<gl-cor:sourceJournalID contextRef="now">gj</gl-cor:sourceJournalID>
			<gl-bus:sourceJournalDescription contextRef="now">JE</gl-bus:sourceJournalDescription>
			<gl-cor:entryType contextRef="now">standard</gl-cor:entryType>
			<gl-cor:entryNumber contextRef="now">584</gl-cor:entryNumber>
			<gl-cor:entryComment contextRef="now">The comment for this entry</gl-cor:entryComment>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">1</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">10100</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Chequing</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">684.88</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">2</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20100</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Expenses</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">750</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">3</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20100</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Expenses</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">85</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">4</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20100</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Expenses</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">28.4</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">5</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20200</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Liabilities</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">28.4</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">6</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20200</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Liabilities</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">28.4</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">7</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20100</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Expenses</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">23.1</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">8</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20200</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Liabilities</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">23.1</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">9</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20200</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Liabilities</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">16.5</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">10</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20200</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Liabilities</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">105.22</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">11</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20100</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Expenses</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">30</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">12</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">20200</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Payroll Liabilities</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">30</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:identifierReference>
					<gl-cor:identifierCode contextRef="now">331</gl-cor:identifierCode>
					<gl-cor:identifierDescription contextRef="now">Alison Logan-Smith</gl-cor:identifierDescription>
					<gl-cor:identifierType contextRef="now">E</gl-cor:identifierType>
				</gl-cor:identifierReference>
				<gl-cor:documentType contextRef="now">check</gl-cor:documentType>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
		</gl-cor:entryHeader>
	</gl-cor:accountingEntries>
</xbrli:xbrl>

  1. The “root” of every XBRL file (“instance document”) is xbrl.

  2. Contexts, mandatory according to the XBRL 2.1, Specification, are not meant to describe the information in XBRL GL and appear only by convention. All facts are instant and developers are encouraged to duplicate/provide the date the XBRL GL information is created as the period’s date.

  3. The XBRL GL WG recommends using the file creation data as the period.

  4. Units of measure in XBRL GL are handled within the measurable or multicurrency elements. Units are provided by convention and should not be relied upon in interpreting XBRL GL data.

  5. The container for XBRL GL, accountingEntries, is not the root of an XBRL GL file – the root, as with all XBRL files, is xbrl. This means that a single XBRL GL file can store one or more virtual XBRL GL files, through one or more accountingEntries structures with data inside. The primary key to understanding an XBRL GL file is the entriesType. A single physical XBRL GL file can have multiple accountingEntries structures to represent both transactions and master files; the differences are signified by the appropriate entriesType enumerated values.

  6. Because entriesType is strongly suggested, documentInfo will be required.

  7. This field, entriesType, provides the automated guidance on the purpose of the XBRL GL information.

  8. Like a serial number, this field, uniqueID, provides a place to uniquely identify/track a series of entries. It is like less relevant for ad-hoc reports. XBRL GL provides for later correction through replacement or augmentation of transferred information.

  9. The date associated with the creation of the data reflected within the associated accountingEntries section. Somewhat like a “printed date” on a paper report.

  10. A description related to the batch of information express in the accountingEntries structure. Why was this batch of information put together and published? It would be helpful to put that information in the entriesComment.

  11. The period of time reflected by the journal entries. Ideally, all entries have their accounting significance within that period, and all of the entries with an accounting signification within that period are included.

  12. Typically, an export from an accounting system does not carry with it information specifically about the company. However, the name of the company would be a very good thing to include with the file, making the entityInformation tuple necessary.

  13. The name of the company would be a very good thing to include with the file; this structure and its content are where that would be stored.

  14. Journal entries require entry in entryHeader and entryDetail. Few files can be represented using only documentInfo and entityInformation sections, but it is certainly possible.

  15. This is an enumerated entry that ties the source journal from the reporting organization to a fixed list that helps in data interchange.

  16. Since sourceJournalID is enumerated (you must pick one of the entries already identified within XBRL GL), sourceJournalDescription lets you capture the actual code or term used to descibe the source journal by the organization.

  17. An enumerated field to differentiate between details that represent actual accounting entries – as opposed to entries for budget purposes, planning purposes, or other entries that may not contribute to the financial statements.

  18. When capturing journal entries, you have a series of debits and credits that (normally) add up to zero. The hierarchical nature of XBRL GL keeps the entry detail lines associated with the entry header by a parent-child relationship. The unique identifier of each entry is entered here.

  19. The reason for making an entry goes here.

  20. Individual lines of journal entries will normally require their own entryDetail section – one primary amount per entryDetail line. However, you can list different accounts within the same entryDetail line that are associated with that amount. For example, if you capitalize for US GAAP and expense for IFRS.

  21. A unique identifier for each entry detail line within an entry header, this should at the least be a counter.

  22. If account information is represented elsewhere or as a master file, some of the fields below would not need to be here (signified by *).

  23. The account number is the basis for posting journal entries. In some cases, accounting systems used by small organizations do not use account numbers/codes, but only use a descriptive name for the account.

  24. In most cases, the description is given to help a human reader; the accountMainID would be sufficient for data exchange purposes. As noted previously, some implementations use the description as the primary identifier of the account.

  25. Accounts serve many purposes, and in a large company using more sophisticated software, the company may wish to record the account used for the original entry and a separate consolidating account. The Japanese system may require a counterbalancing account for each line item. And an entry may be recorded differently for US GAAP, IFRS and other purposes. This code is an enumerated code to help identify accounts for those purposes.

  26. In an international environment, the “chart of accounts” will include not only traditional accounts, like Cash, Accounts Payable/Due to Creditors or Retained Earnings, but also extensions to some of the accounts. Accounts Payable may be extended to include the creditors/vendors themselves. Therefore, in XBRL GL, accounts can be specifically identified as the “traditional” accountm or to identify a customer, vendor, employee, bank, job or fixed asset. While this may overlap with the customers, vendors and employees of the identifier structure, fixed-assets in the measurable structure, jobs in the jobInfo structure and other representations, they can also be represented here as appropriate to the jurisidiction.

  27. What is a journal entry without a (monetary) amount? While XBRL GL may usher in journal entries that also incorporate quantities, to reflect the detail of business metrics, the (monetary) amount is another key and obvious fields. XBRL GL has been designed to reflect how popular accounting systems store amounts – some combination of a signed amount (e.g., 5, -10), a separate sign (entered into signOfAmount) and a separate place to indicate the number is associated with a debit or credit (debitCreditCode).

  28. Depending on the originating system, this field may contain whether the amount is associated with a debit or credit. Interpreting the number correctly for import requires an understanding of the three related amount fields – amount, debitCreditCode and sign of amount.

  29. Depending on the originating system, this field may contain whether the amount is signed (+ or -) separately from the amount field itself. Interpreting the number correctly for import requires an understanding of the three related amount fields – amount, debitCreditCode and sign of amount.

  30. This date is the accounting significance date, not the date that entries were actually entered or posted to the system.

  31. This enumerated field is used to specifically state whether the entries have been posted to the originating system or not.

  32. A comment at the individual entry detail level.

2.2. Sample Journal entries with timing differences file for XBRL Global Ledger Framework with annotations Version 1.0.91021.1

This file contains data fields considered very important to representing its subject. Annotations have been provided for the “most important” of those fields. XBRL GL has many other fields that could be helpful in expressing the information, but have been omitted because their presence is more circumstantial. This file was created for educational purposes only, does not represent real company data and we welcome suggestions on improvement. Contact xbrlgl@xbrl.org with comments.

<?xml version="1.0" encoding="UTF-8"?>
<!-- The "root" of every XBRL file ("instance document") is xbrl. -->
<xbrli:xbrl xmlns:xbrli="http://www.xbrl.org/2003/instance" xmlns:xbrll="http://www.xbrl.org/2003/linkbase" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:gl-cor="http://www.xbrl.org/int/gl/cor/2015-03-25" xmlns:gl-muc="http://www.xbrl.org/int/gl/muc/2015-03-25" xmlns:gl-bus="http://www.xbrl.org/int/gl/bus/2015-03-25" xmlns:gl-plt="http://www.xbrl.org/int/gl/plt/2015-03-25" xmlns:iso4217="http://www.xbrl.org/2003/iso4217" xmlns:iso639="http://www.xbrl.org/2005/iso639" xsi:schemaLocation="http://www.xbrl.org/int/gl/plt/2015-03-25 ../plt/case-c-b-m-u-t/gl-plt-all-2015-03-25.xsd">
	<xbrll:schemaRef xlink:type="simple" xlink:arcrole="http://www.w3.org/1999/xlink/properties/linkbase" xlink:href="../plt/case-c-b-m-u-t/gl-plt-all-2015-03-25.xsd"/>
	<xbrli:context id="now"> // (1)
		<xbrli:entity>
			<xbrli:identifier scheme="http://www.xbrl.org/xbrlgl/sample">SAMPLE</xbrli:identifier>
		</xbrli:entity>
		<xbrli:period> // (2)
			<xbrli:instant>2004-10-03</xbrli:instant>
		</xbrli:period>
	</xbrli:context>
	<xbrli:unit id="usd"> // (3)
		<xbrli:measure>iso4217:USD</xbrli:measure>
	</xbrli:unit>
	<xbrli:unit id="NotUsed">
		<xbrli:measure>pure</xbrli:measure>
	</xbrli:unit>
	<gl-cor:accountingEntries> // (4)
		<gl-cor:documentInfo> // (5)
			<gl-cor:entriesType contextRef="now">entries</gl-cor:entriesType> // (6)
			<gl-cor:uniqueID contextRef="now">001</gl-cor:uniqueID> // (7)
			<gl-cor:language contextRef="now">iso639:en</gl-cor:language>
			<gl-cor:creationDate contextRef="now">2005-07-05</gl-cor:creationDate> // (8)
			<gl-bus:creator contextRef="now">XBRL GL Working Group</gl-bus:creator>
			<gl-cor:entriesComment contextRef="now">A best practice example of entries with book to tax differences instance document</gl-cor:entriesComment> // (9)
			<gl-cor:periodCoveredStart contextRef="now">2005-06-01</gl-cor:periodCoveredStart> // (10)
			<gl-cor:periodCoveredEnd contextRef="now">2005-06-30</gl-cor:periodCoveredEnd>
			<gl-bus:sourceApplication contextRef="now">Hitachi mapping tool</gl-bus:sourceApplication>
			<gl-muc:defaultCurrency contextRef="now">iso4217:usd</gl-muc:defaultCurrency>
		</gl-cor:documentInfo>
		<gl-cor:entityInformation> // (11)
			<gl-bus:organizationIdentifiers> // (12)
				<gl-bus:organizationIdentifier contextRef="now">ABC Company</gl-bus:organizationIdentifier>
				<gl-bus:organizationDescription contextRef="now">Company Name</gl-bus:organizationDescription>
			</gl-bus:organizationIdentifiers>
		</gl-cor:entityInformation>
		<gl-cor:entryHeader> // (13)
			<gl-cor:enteredBy contextRef="now">Otto Wellwood</gl-cor:enteredBy>
			<gl-cor:enteredDate contextRef="now">2005-07-01</gl-cor:enteredDate>
			<gl-cor:sourceJournalID contextRef="now">gj</gl-cor:sourceJournalID> // (14)
			<gl-bus:sourceJournalDescription contextRef="now">JE</gl-bus:sourceJournalDescription> // (15)
			<gl-cor:entryType contextRef="now">standard</gl-cor:entryType> // (16)
			<gl-cor:entryNumber contextRef="now">1</gl-cor:entryNumber> // (17)
			<gl-cor:entryComment contextRef="now">Current period depreciation expense</gl-cor:entryComment> // (18)
			<gl-cor:bookTaxDifference contextRef="now">temporary</gl-cor:bookTaxDifference> // (19)
			<gl-cor:entryDetail> // (20)
				<gl-cor:lineNumber contextRef="now">1</gl-cor:lineNumber> // (21)
				<gl-cor:account> // (22)
					<gl-cor:accountMainID contextRef="now">6200</gl-cor:accountMainID> // (23)
					<gl-cor:accountMainDescription contextRef="now">Depreciation expense</gl-cor:accountMainDescription> // (24)
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode> // (25)
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">5000</gl-cor:amount> // (26)
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode> // (27)
				<!-- <gl-cor:signOfAmount contextRef="now"/> --> // (28)
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate> // (29)
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus> // (30)
				<gl-cor:detailComment contextRef="now">Current period depreciation expense - books</gl-cor:detailComment>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">2</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">1451</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Accumulated Depreciation</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">5000</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
				<gl-cor:detailComment contextRef="now">Current period depreciation expense - books</gl-cor:detailComment>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail> // (31)
				<gl-cor:lineNumber contextRef="now">3</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">6200</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Depreciation Expense</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">tax</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">6000</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
				<gl-cor:detailComment contextRef="now">Current period depreciation expense - tax</gl-cor:detailComment>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">4</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">1421</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Accumulated Depreciation</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">tax</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">6000</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
			</gl-cor:entryDetail>
		</gl-cor:entryHeader>
		<gl-cor:entryHeader> // (32)
			<gl-cor:enteredBy contextRef="now">Otto Wellwood</gl-cor:enteredBy>
			<gl-cor:enteredDate contextRef="now">2005-07-01</gl-cor:enteredDate>
			<gl-cor:sourceJournalID contextRef="now">gj</gl-cor:sourceJournalID>
			<gl-bus:sourceJournalDescription contextRef="now">JE</gl-bus:sourceJournalDescription>
			<gl-cor:entryType contextRef="now">standard</gl-cor:entryType>
			<gl-cor:entryNumber contextRef="now">2</gl-cor:entryNumber>
			<gl-cor:entryComment contextRef="now">Current period tax exempt interest</gl-cor:entryComment>
			<gl-cor:bookTaxDifference contextRef="now">permanent</gl-cor:bookTaxDifference>
			<gl-cor:entryDetail> // (33)
				<gl-cor:lineNumber contextRef="now">1</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">1300</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Accrued interest</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">500</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
				<gl-cor:detailComment contextRef="now">Record current period interest earned</gl-cor:detailComment>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">2</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">5200</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Interest income</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">usgaap</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">500</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
				<gl-cor:detailComment contextRef="now">Record current period interest earned</gl-cor:detailComment>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail> // (34)
				<gl-cor:lineNumber contextRef="now">3</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">1300</gl-cor:accountMainID>
					<gl-cor:accountMainDescription contextRef="now">Accrued Interest</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">tax</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">500</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">D</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
				<gl-cor:detailComment contextRef="now">Record current period tax exempt interest earned</gl-cor:detailComment>
			</gl-cor:entryDetail>
			<gl-cor:entryDetail>
				<gl-cor:lineNumber contextRef="now">4</gl-cor:lineNumber>
				<gl-cor:account>
					<gl-cor:accountMainID contextRef="now">9999</gl-cor:accountMainID> // (35)
					<gl-cor:accountMainDescription contextRef="now">Clearing</gl-cor:accountMainDescription>
					<gl-cor:accountPurposeCode contextRef="now">tax</gl-cor:accountPurposeCode>
					<gl-cor:accountType contextRef="now">account</gl-cor:accountType>
				</gl-cor:account>
				<gl-cor:amount contextRef="now" decimals="2" unitRef="usd">500</gl-cor:amount>
				<gl-cor:debitCreditCode contextRef="now">C</gl-cor:debitCreditCode>
				<gl-cor:postingDate contextRef="now">2005-06-30</gl-cor:postingDate>
				<gl-cor:postingStatus contextRef="now">posted</gl-cor:postingStatus>
				<gl-cor:detailComment contextRef="now">Record current period tax exempt interest earned</gl-cor:detailComment>
			</gl-cor:entryDetail>
		</gl-cor:entryHeader>
	</gl-cor:accountingEntries>
</xbrli:xbrl>

  1. Contexts, mandatory according to the XBRL 2.1, Specification, are not meant to describe the information in XBRL GL and appear only by convention. All facts are instant and developers are encouraged to duplicate/provide the date the XBRL GL information is created as the period’s date.

  2. The XBRL GL WG recommends using the file creation data as the period.

  3. Units of measure in XBRL GL are handled within the measurable or multicurrency elements. Units are provided by convention and should not be relied upon in interpreting XBRL GL data.

  4. The container for XBRL GL, accountingEntries, is not the root of an XBRL GL file – the root, as with all XBRL files, is xbrl. This means that a single XBRL GL file can store one or more virtual XBRL GL files, through one or more accountingEntries structures with data inside. The primary key to understanding an XBRL GL file is the entriesType. A single physical XBRL GL file can have multiple accountingEntries structures to represent both transactions and master files; the differences are signified by the appropriate entriesType enumerated values.

  5. Because entriesType is strongly suggested, documentInfo will be required.

  6. This field, entriesType, provides the automated guidance on the purpose of the XBRL GL information. The value “entries” is less specific than “journal” or “ledger”.

  7. Like a serial number, this field, uniqueID, provides a place to uniquely identify/track a series of entries. It is like less relevant for ad-hoc reports. XBRL GL provides for later correction through replacement or augmentation of transferred information.

  8. The date associated with the creation of the data reflected within the associated accountingEntries section. Somewhat like a “printed date” on a paper report.

  9. A description related to the batch of information express in the accountingEntries structure. Why was this batch of information put together and published? It would be helpful to put that information in the entriesComment.

  10. The period of time reflected by the journal entries. Ideally, all entries have their accounting significance within that period, and all of the entries with an accounting signification within that period are included.

  11. Typically, an export from an accounting system does not carry with it information specifically about the company. However, the name of the company would be a very good thing to include with the file, making the entityInformation tuple necessary.

  12. The name of the company would be a very good thing to include with the file; this structure and its content are where that would be stored.

  13. Journal entries require entry in entryHeader and entryDetail. Few files can be represented using only documentInfo and entityInformation sections, but it is certainly possible.
    Accounting for taxes and reconciliation between multiple GAAPs can be faciliated with XBRL GL. The advent of the US M-3 form is one example of needing better tools to handle book to tax differences.
    This instance will represent two journal entries, one representing a permanent book to tax difference and the next representing a timing difference. The entries may not be best practices entries, but we hope they help express the power of XBRL GL.
    Many companies do not record book and tax entries simultaneously, but do a later series of adjustments for tax purposes. This example does not illustrate that situation, but XBRL GL does allow a wide variety of other tax related representations and circumstances.

    Entry 1: A timing difference example: depreciation lives and methods differ between book and tax, resulting in different entries for the period.

    A/C 6200 Depreciation expense 5000
    A/C 1451 Accumulated Depreciation 5000
    Current period depreciation expense – books

    A/C 6200 Depreciation expense 6000
    A/C 1451 Accumulated Depreciation 6000
    Current period depreciation expense – tax

  14. This is an enumerated entry that ties the source journal from the reporting organization to a fixed list that helps in data interchange.

  15. Since sourceJournalID is enumerated (you must pick one of the entries already identified within XBRL GL), sourceJournalDescription lets you capture the actual code or term used to descibe the source journal by the organization.

  16. An enumerated field to differentiate between details that represent actual accounting entries – as opposed to entries for budget purposes, planning purposes, or other entries that may not contribute to the financial statements.

  17. When capturing journal entries, you have a series of debits and credits that (normally) add up to zero. The hierarchical nature of XBRL GL keeps the entry detail lines associated with the entry header by a parent-child relationship. The unique identifier of each entry is entered here.

  18. The reason for making an entry goes here. As both book and tax entries in out example go into one entryHeader, there is a common comment.

  19. The more sophisticated tool for tracking book to tax differences may be the various organizationAccountingMethod related elements, but bookTaxDifference is pretty clear; the entries as captured within this entryHeader are creating a permanent or timing difference! Our first entry, depreciation, represented the timing difference, so we use the enumerated value “temporary”.

  20. Individual lines of journal entries will normally require their own entryDetail section – one primary amount per entryDetail line. However, you can list different accounts within the same entryDetail line that are associated with that amount. In this case, we will not try to merge the one example of book and tax line being the same into one entryDetail line.

  21. A unique identifier for each entry detail line within an entry header, this should at the least be a counter.

  22. If account information is represented elsewhere or as a master file, some of the fields below would not need to be here (signified by *)

  23. The account number is the basis for posting journal entries. In some cases, accounting systems used by small organizations do not use account numbers/codes, but only use a descriptive name for the account.

  24. In most cases, the description is given to help a human reader; the accountMainID would be sufficient for data exchange purposes. As noted previously, some implementations use the description as the primary identifier of the account.

  25. mainAccountType, not depicted here, could also help by specifically identifying that the accounting is an income, expense, gain or loss; these are the primary M-3 oriented items.
    XBRL GL has more than one tool to differentiate between book and tax entries. One is through the accountPurposeCode. The other is through the organizationAccountingMethod elements. For simplicity in this example, we will use the accountPurposeCode.

  26. What is a journal entry without a (monetary) amount? While XBRL GL may usher in journal entries that also incorporate quantities, to reflect the detail of business metrics, the (monetary) amount is another key and obvious fields. XBRL GL has been designed to reflect how popular accounting systems store amounts – some combination of a signed amount (e.g., 5, -10), a separate sign (entered into signOfAmount) and a separate place to indicate the number is associated with a debit or credit (debitCreditCode).

  27. Depending on the originating system, this field may contain whether the amount is associated with a debit or credit. Interpreting the number correctly for import requires an understanding of the three related amount fields – amount, debitCreditCode and sign of amount.

  28. Depending on the originating system, this field may contain whether the amount is signed (+ or -) separately from the amount field itself. Interpreting the number correctly for import requires an understanding of the three related amount fields – amount, debitCreditCode and sign of amount.

  29. This date is the accounting significance date, not the date that entries were actually entered or posted to the system.

  30. This enumerated field is used to specifically state whether the entries have been posted to the originating system or not.

  31. Our tax side of this entry is very similar to the book entry – it has a different amount and a different accountType.

  32. Entry 2: A permanent difference example: Tax-exempt interest

    A/C 1300 Accrued Interest 500
    A/C 5200 Interest income 500
    Record current period interest earned

    A/C 1300 Accrued Interest 500
    A/C 9999 Clearing 500
    Record current period tax exempt interest earned

  33. Our second entry, tax exempt income, represented the permanent difference, so we use the enumerated value “permanent”.
    Book side to entry.

  34. Our tax side of this entry.

  35. Sorry about this for the accounting purists.

Category: ChatGPT, ISO, TC295

コメントを残す

メールアドレスが公開されることはありません。 ※ が付いている欄は必須項目です