| Line | Field Name | Data Type | Description |
|---|---|---|---|
| 1 | str:apPaymentData | Table | Accounts payable payment details by payment made to supplier. |
| 2 | term:approvedBy | Term (Text/String) | User ID (from User_Listing file) for person who approved the entry. |
| 3 | term:approvedDateTime | Term (Date) | The DateTime the entry was approved. |
| 4 | term:batchId | Term (Text/String) | Systems generated ID for batch |
| 5 | term:description | Term (Text/String) | Description of the payment. |
| 6 | term:glCreditAccountNumber | Term (Text/String) | GL account number on which the credit side of the transaction has been posted. |
| 7 | term:glDebitAccountNumber | Term (Text/String) | GL account number on which the debit side of the transaction has been posted. |
| 8 | term:lastModifiedBy | Term (Text/String) | User_ID (from User_Listing file) for the last person modifying this entry. |
| 9 | term:lastModifiedDateTime | Term (Date) | The date and time the entry was last modified before posting. |
| 10 | term:lineAccountId | Term (Text/String) | General Ledger Account code of the GL-revenue-account. Can be including sub-account id. It can contain many different levels to identify the Account. It could include cost centres such as company, division, region, group and branch/department. |
| 11 | term:lineAnalysisAmountCurrencyAmount | Term (Decimal) | Transaction monetary amount in local currency. |
| 12 | term:lineAnalysisAnalysisAmount | Term (Decimal) | The functional or group currency related to the receipt amount. See ISO 4217 coding. |
| 13 | term:lineAnalysisAnalysisAmountCurrencyCode | Term (Text/String) | Transaction monetary amount recorded in the reporting currency. |
| 14 | term:lineAnalysisAnalysisAmountExchangeRate | Term (Decimal) | The exchange rate used. CurrencyAmount x ExchangeRate = Amount |
| 15 | term:lineAnalysisAnalysisId | Term (Text/String) | Analysis ID: e.g. 1200-HDOF-TR (for cost center treasury in the headoffice), P-4800-123 (for project 123 in branch 4800) |
| 16 | term:lineAnalysisAnalysisIdDescription | Term (Text/String) | Description of the AnalysisID: e.g. Headoffice-Treasury. |
| 17 | term:lineAnalysisAnalysisType | Term (Text/String) | Analysis type identifier: e.g. CC (for Cost Center), DEP (for department), etc |
| 18 | term:lineAnalysisAnalysisTypeDescription | Term (Text/String) | Description of the AnalysisType, e.g. Cost Center |
| 19 | term:lineApprovedBy | Term (Text/String) | User ID (from User_Listing file) for person who approved the entry. |
| 20 | term:lineApprovedDateTime | Term (Date) | The date and time the entry was approved. |
| 21 | term:lineBusinessUnitCode | Term (Text/String) | Used to identify the business unit, region, branch, and so on at the level that financial statements are being audited. Must match the Business_Unit_Code in the Business_Unit_Listing file. |
| 22 | term:lineDebitCreditIndicator | Term (Text/String) | Indicates whether the amounts on line-level are debit or credit amounts. Entry must correspond to entry reflected in General Ledger Entry. Signing of line amounts is relative to this indicator. E.g. a return can lead to a negative amount |
| 23 | term:lineDescription | Term (Text/String) | Description of Invoice Line. |
| 24 | term:lineLastModifiedDate | Term (Text/String) | The date the entry was last modified. |
| 25 | term:lineLineNumber | Term (Text/String) | Line item number of the invoice. |
| 26 | term:lineModifiedBy | Term (Text/String) | User_ID (from User_Listing file) for the last person modifying this entry. |
| 27 | term:linePaymentAmountLocalCurrencyCode | Term (Text/String) | The currency for local reporting requirements. See ISO 4217 coding. |
| 28 | term:linePaymentAmountReporting | Term (Decimal) | Transaction monetary amount recorded in the reporting currency. |
| 29 | term:linePaymentAmountReportingCurrency | Term (Decimal) | The reporting currency related to the payment amount for nonconsolidated reporting. See ISO 4217 coding. |
| 30 | term:linePaymentLineAmount | Term (Decimal) | Transaction monetary amount recorded in the functional or group currency. No multicurrency translation should need to be performed on this amount because all transactions should be recorded in a single currency. |
| 31 | term:linePaymentLineAmountCurrencyAmount | Term (Decimal) | Transaction monetary amount in local currency. |
| 32 | term:linePaymentLineAmountCurrencyCode | Term (Text/String) | Three-letter currency code according to ISO 4217 standard. Example: EUR for the Euros or USD for American Dollars. |
| 33 | term:linePaymentLineAmountExchangeRate | Term (Decimal) | The exchange rate used. CurrencyAmount x ExchangeRate = Amount |
| 34 | term:lineSettlementCurrencyAmount | Term (Decimal) | Amount in foreign currency |
| 35 | term:lineSettlementCurrencyCode | Term (Text/String) | Three-letter currency code according to ISO 4217 standard. Example: EUR for the Euros or USD for American Dollars. |
| 36 | term:lineSettlementPaymentMechanism | Term (Text/String) | Payment mechanism |
| 37 | term:lineSettlementSettlementAmount | Term (Decimal) | In the headers default currency. |
| 38 | term:lineSettlementSettlementAmountExchangeRate | Term (Decimal) | The exchange rate used. CurrencyAmount x ExchangeRate = Amount |
| 39 | term:lineSettlementSettlementDate | Term (Date) | Date settled |
| 40 | term:lineSettlementSettlementDiscount | Term (Decimal) | Description Settlement / Other Discount |
| 41 | term:lineSourceDocumentId | Term (Text/String) | The source document to which the line relates |
| 42 | term:lineSupplierId | Term (Text/String) | Identifier of the supplier to whom payment is due or from whom unused credits have been applied. Must match the Supplier_Account_ID in the Supplier_Listing_YYYYMMDD file. |
| 43 | term:lineSystemEntryDateTime | 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. |
| 44 | term:lineSystemEntryUser | Term (Text/String) | User_ID (from User_Listing file) for person who created the record. |
| 45 | term:lineTaxInformationTaxAmount | Term (Decimal) | In the headers default currency. |
| 46 | term:lineTaxInformationTaxAmountCurrencyAmount | Term (Decimal) | Amount in foreign currency |
| 47 | term:lineTaxInformationTaxAmountCurrencyCode | Term (Text/String) | Three-letter currency code according to ISO 4217 standard. Example: EUR for the Euros or USD for American Dollars. |
| 48 | term:lineTaxInformationTaxAmountExchangeRate | Term (Decimal) | The exchange rate used. CurrencyAmount x ExchangeRate = Amount |
| 49 | term:lineTaxInformationTaxBase | Term (Text/String) | The base on which the tax is calculated. This can be an amount, or a quantity, eg. Litres. |
| 50 | term:lineTaxInformationTaxBaseDescription | Term (Text/String) | Description of the value in the TaxBase. Eg. Litres for excises on alcoholic bevarages. |
| 51 | term:lineTaxInformationTaxCode | Term (Text/String) | Tax Code for lookup in tables |
| 52 | term:lineTaxInformationTaxDeclarationPeriod | Term (Text/String) | The identification of the declaration/return in which the taxamount is reported to the Revenue body |
| 53 | term:lineTaxInformationTaxExemptionReason | Term (Text/String) | Tax exemption or reduction reason or rationale |
| 54 | term:lineTaxInformationTaxPercentage | Term (Decimal) | Tax percentage. |
| 55 | term:lineTaxInformationTaxType | Term (Text/String) | Tax type for look-up in tables |
| 56 | term:lineTaxPointDate | Term (Date) | Tax Point date where recorded or if not recorded then the Invoice date |
| 57 | term:paymentId | Term (Text/String) | Unique identifier for each payment received. This ID may need to be created by concatenating fields (for example, customer and payment number) to uniquely identify each transaction. |
| 58 | term:paymentMethod | Term (Text/String) | The code value or indicator of the method by which the transaction debit or credit amount was extinguished or apportioned to the debt by the supplier (for example, check, wire transfer, cash, and so on). Must match the Payment_Type in the Payment_Type_Listing_YYYYMMDD file. |
| 59 | term:paymentRefNo | Term (Text/String) | Unique identifier for each payment made. This ID may need to be created by concatenating fields (for example, supplier and payment number) to uniquely identify each transaction. |
| 60 | 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. |
| 61 | term:periodYear | Term (Text/String) | Fiscal year in which the Purchase_Order_Date occurred YYYY fordelimited, CCYY-MM-DD fiscal year end(ISO 8601) for extensible business reporting language global ledger taxonomy framework (XBRL GL). |
| 62 | term:postingStatus | Term (Text/String) | Status of the transactions posting to the GL (for example, Posted, Not Posted). |
| 63 | term:referenceDate | Term (Date) | Date on an externally generated transaction (for example, check date or wire transfer date). |
| 64 | term:referenceNumber | Term (Text/String) | Identification number for an internally or externally generated transaction (for example, check number, wire transfer number, or original document ID). |
| 65 | term:segment01 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 66 | term:segment02 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 67 | term:segment03 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 68 | term:segment04 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 69 | term:segment05 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 70 | 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). |
| 71 | term:systemEntryDateTime | 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. |
| 72 | term:systemEntryUser | Term (Text/String) | User_ID (from User_Listing file) for person who created the record. |
| 73 | term:systemId | Term (Text/String) | Unique number created by the system for the document |
| 74 | term:transactionDate | Term (Date) | The date the payment was made or credit was applied. |
| 75 | 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 |