| Line | Field Name | Data Type | Description |
|---|---|---|---|
| 1 | str:glDetail | Table | General ledger detail transactions by journal entry for each general journal entry. |
| 2 | term:amount | Term (Decimal) | Transaction monetary amount recorded in the functional or group currency for the entity under audit. No multicurrency translation should need to be performed on this amount because all transactions are recorded in a single currency. |
| 3 | term:amountCreditDebitIndicator | Term (Text/String) | Indicates whether the amount is a credit or debit C=credit ‚D=debit. |
| 4 | term:amountCurrency | Term (Text/String) | The functional or group currency related to the balance. See ISO 4217 coding. |
| 5 | term:approvedBy | Term (Text/String) | User ID (from User_Listing file) for person who approved the entry. |
| 6 | term:approvedDateTime | Term (Date) | The DateTime the entry was approved. |
| 7 | term:businessUnitCode | Term (Text/String) | Used to identify the business unit, region, branch, and so on at the level that financial statements are being audited and for which the trial balance is generated. For example, you may use a code aligned with the concept of a reportable segment as defined in FASB Accounting Standards Codification (ASC) 280, Segment Reporting. |
| 8 | term:effectiveDate | Term (Date) | Date the customer declared active. |
| 9 | term:enteredBy | Term (Text/String) | User_ID (from User_Listing file) for person who created the record. |
| 10 | term:enteredDateTime | Term (Date) | The date the transaction was entered into the system. This is sometimes referred to as the creation date. This should be a system-generated date (rather than user-entered date), when possible. This date does not necessarily correspond with the date of the transaction itself. |
| 11 | term:fiscalYear | Term (Text/String) | Fiscal year in which Effective_Date occurred YYYY for delimited, CCYY-MM-DD fiscal year end (ISO 8601) for Extensible Business Reporting Language Global Ledger taxonomy framework (XBRL GL). |
| 12 | term:glAccountNumber | Term (Text/String) | Identifier for the GL financial quarterly periods. GL_Account_Number in this file must match the GL_Account_Number used in the Trial_Balance and Chart_Of_Accounts files. |
| 13 | term:jeHeaderDescription | Term (Text/String) | Description of the entire journal entry as described by the journal entry header. |
| 14 | term:jeLineDescription | Term (Text/String) | Description of the individual line within the journal entry. |
| 15 | term:journalEntryType | Term (Text/String) | |
| 16 | term:journalId | Term (Text/String) | Identifier that is unique for each journal entry. May require concatenation of multiple fields. |
| 17 | term:journalIdLineNumber | Term (Text/String) | Identifier that is unique for each line within a journal entry. |
| 18 | term:lastModifiedBy | Term (Text/String) | User_ID (from User_Listing file) for the last person modifying this entry. |
| 19 | term:lastModifiedDate | Term (Date) | The date the entry was last modified before posting. |
| 20 | term:localAmount | Term (Decimal) | Amount in the local country currency where the transaction originated. |
| 21 | term:localAmountCurrency | Term (Text/String) | The currency used for local country reporting requirements (for example, USD, EUR; see ISO 4217 coding). |
| 22 | term:period | Term (Text/String) | Fiscal period in which the Effective_Date occurs.Examples include W1‚W53 for weekly periods, M1‚M12 for monthly periods, and Q1‚Q4 for quarterly periods. |
| 23 | term:reportingAmount | Term (Decimal) | The amount recorded in the currency in which a reporting entity prepares its financial statements. |
| 24 | term:reportingAmountCurrency | Term (Text/String) | The currency which a reporting entity prepares its financial statements (for example, USD, EUR; see ISO 4217 coding). |
| 25 | term:reversalIndicator | Term (Text/String) | Indicates whether this entry is a reversal or to be reversed. A1=entry is a reversal, A2=entry is to be reversed, and empty (A3)=none of the above or system generated indicators. For XBRL GL, this is a Boolean, in which true indicates it is to be reversed; ‚false with provision of a reversingDate indicates the entry is a reversal. |
| 26 | term:reversalJournalId | Term (Text/String) | When the Reversal_Indicator=1, this identifies the Journal_ID of the entry being reversed. |
| 27 | term:segment01 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 28 | term:segment02 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 29 | term:segment03 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 30 | term:segment04 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 31 | term:segment05 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 32 | term:sourceId | Term (Text/String) | Posting source (code for source from which the journal entry originated, such as sales journal, cash receipts journal, general journal, payroll journal, accountant manual entry, spreadsheet, and so on). |
| 33 | term:tags | Term (Text/String) | |
| 34 | term:taxCode | Term (Text/String) | |
| 35 | term:transactionId | Term (Text/String) | Cross-reference to GL posting. It can contain many different levels to identify the transaction. It could include cost centres such as company, division, region, group and branch/department |
| 36 | term:userDefined1 | Term (Text/String) | |
| 37 | term:userDefined2 | Term (Text/String) |