| Line | Field Name | Data Type | Description |
|---|---|---|---|
| 1 | str:salesOrderData | Table | Sales order information for customer sale per accounts receivable subsystem. |
| 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:billingAddressAdditionalAddressDetail | Term (Text/String) | |
| 6 | term:billingAddressAddressType | Term (Text/String) | Field to differentiate between multiple addresses. To indicate the type of address. Choose from the predefined enumeration. (examples: StreetAddress PostalAddress, BillingAddress) |
| 7 | term:billingAddressBuilding | Term (Text/String) | |
| 8 | term:billingAddressCity | Term (Text/String) | |
| 9 | term:billingAddressCountry | Term (Text/String) | Two-letter country code according to ISO 3166-1 alpha 2 standard. Example NL for the Netherlands. |
| 10 | term:billingAddressNumber | Term (Text/String) | |
| 11 | term:billingAddressPostalCode | Term (Text/String) | |
| 12 | term:billingAddressRegion | Term (Text/String) | Country specific code to indicate regions / provinces within the tax authority. Preferably described according to ISO 3166-2. Example: GB-KEN for Kent county in the United Kingdom. |
| 13 | term:billingAddressStreetName | Term (Text/String) | |
| 14 | term:branchStoreNumber | Term (Text/String) | Branch or Storenumber, additional segregation of customer/supplier, used if not included as part of the customer/supplier id |
| 15 | 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. |
| 16 | term:customerId | Term (Text/String) | Unique code for the customer |
| 17 | term:customerInfoName | Term (Text/String) | Name of the customer |
| 18 | term:glPostingDate | Term (Date) | Date posting to GL |
| 19 | term:lastModifiedBy | Term (Text/String) | User_ID (from User_Listing file) for the last person modifying this entry. |
| 20 | term:lastModifiedDate | Term (Date) | The date the entry was last modified before posting. |
| 21 | 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. |
| 22 | term:lineAnalysisAmount | 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. |
| 23 | term:lineAnalysisId | Term (Text/String) | Value of the analysisID: f.i. which cost center applies |
| 24 | term:lineAnalysisType | Term (Text/String) | Analysis code identifier: cost center, cost unit, cost type, project, etc. Refers to the MasterFile AnalysisTypeTable |
| 25 | term:lineApprovedBy | Term (Text/String) | User ID (from User_Listing file) for person who approved the entry. |
| 26 | term:lineApprovedDateTime | Term (Date) | The date and time the entry was approved. |
| 27 | term:lineCreditNoteReason | Term (Text/String) | Credit note reason or rationale |
| 28 | term:lineCreditNoteReference | Term (Text/String) | Credit note reference (where applicable) to original invoice |
| 29 | 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 |
| 30 | term:lineDeliveryDate | Term (Date) | The date of the delivery |
| 31 | term:lineDescription | Term (Text/String) | Description of Invoice Line. |
| 32 | term:lineFromDate | Term (Date) | Startdate of the deliveries |
| 33 | term:lineGoodsServicesId | Term (Text/String) | Indicator showing if goods or service |
| 34 | term:lineLineNumber | Term (Text/String) | Line item number of the invoice. |
| 35 | term:lineMovementReference | Term (Text/String) | Unique reference to the movement. |
| 36 | term:lineOrderLineAmount | Term (Decimal) | |
| 37 | term:lineOrderLineAmountCurrencyAmount | Term (Decimal) | Transaction monetary amount in local currency. |
| 38 | term:lineOrderLineAmountCurrencyCode | Term (Text/String) | The currency for local reporting requirements. See ISO 4217 coding. |
| 39 | term:lineOrderLineAmountExchangeRate | Term (Decimal) | |
| 40 | term:lineOrderUOM | Term (Text/String) | Purchase order line base unit of measure. |
| 41 | term:linePiDate | Term (Date) | |
| 42 | term:lineProductCode | Term (Text/String) | Unique identifier for each purchased product. This ID may need to be created by concatenating fields (for example, business unit, product number, year, and so on) to uniquely identify each product. |
| 43 | term:lineProductDescription | Term (Text/String) | Product (plain English) description to indicate the name or other identifying characteristics of the product. |
| 44 | term:lineProductGroup01 | Term (Text/String) | Product descriptor #1, for example, tires or accessories. |
| 45 | term:lineProductGroup02 | Term (Text/String) | Product descriptor #2, for example, brand. |
| 46 | term:lineProductId | Term (Text/String) | Unique identifier for each sales product. This ID may need to be created by concatenating fields (for example, business unit, product number, year, and so on) to uniquely identify each product. |
| 47 | term:lineQuantity | Term (Text/String) | Quantity of goods and services supplied. |
| 48 | term:lineShipFromAdditionalAddressDetail | Term (Text/String) | |
| 49 | term:lineShipFromAddressType | Term (Text/String) | Field to differentiate between multiple addresses. To indicate the type of address. Choose from the predefined enumeration. (examples: StreetAddress PostalAddress, BillingAddress) |
| 50 | term:lineShipFromBuilding | Term (Text/String) | |
| 51 | term:lineShipFromCity | Term (Text/String) | |
| 52 | term:lineShipFromCountry | Term (Text/String) | Two-letter country code according to ISO 3166-1 alpha 2 standard. Example NL for the Netherlands. |
| 53 | term:lineShipFromDeliveryDate | Term (Date) | Date goods are delivered |
| 54 | term:lineShipFromDeliveryId | Term (Text/String) | Identification of the delivery |
| 55 | term:lineShipFromLocationId | Term (Text/String) | Warehouse where goods held - also to identify work-in-progress, or stock-in-transit |
| 56 | term:lineShipFromNumber | Term (Text/String) | |
| 57 | term:lineShipFromPostalCode | Term (Text/String) | |
| 58 | term:lineShipFromRegion | Term (Text/String) | Country specific code to indicate regions / provinces within the tax authority. Preferably described according to ISO 3166-2. Example: GB-KEN for Kent county in the United Kingdom. |
| 59 | term:lineShipFromStreetName | Term (Text/String) | Unique consignment reference number |
| 60 | term:lineShipFromUCR | Term (Text/String) | Location of goods in warehouse |
| 61 | term:lineShipFromWarehouseId | Term (Text/String) | Warehouse where goods held - also to identify work-in-progress, or stock-in-transit |
| 62 | term:lineShippingCostsAmount | Term (Decimal) | In the headers default currency. |
| 63 | term:lineShippingCostsAmountCurrencyAmount | Term (Decimal) | Amount in foreign currency |
| 64 | term:lineShippingCostsAmountCurrencyCode | Term (Text/String) | Three-letter currency code according to ISO 4217 standard. Example: EUR for the Euros or USD for American Dollars. |
| 65 | term:lineShippingCostsAmountExchangeRate | Term (Decimal) | The exchange rate used. CurrencyAmount x ExchangeRate = Amount |
| 66 | term:lineShipToAdditionalAddressDetail | Term (Text/String) | |
| 67 | term:lineShipToAddressType | Term (Text/String) | Field to differentiate between multiple addresses. To indicate the type of address. Choose from the predefined enumeration. (examples: StreetAddress PostalAddress, BillingAddress) |
| 68 | term:lineShipToBuilding | Term (Text/String) | |
| 69 | term:lineShipToCity | Term (Text/String) | |
| 70 | term:lineShipToCountry | Term (Text/String) | Two-letter country code according to ISO 3166-1 alpha 2 standard. Example NL for the Netherlands. |
| 71 | term:lineShipToDeliveryDate | Term (Date) | Date goods are delivered |
| 72 | term:lineShipToDeliveryId | Term (Text/String) | Identification of the delivery |
| 73 | term:lineShipToLocationId | Term (Text/String) | Location of goods in warehouse |
| 74 | term:lineShipToNumber | Term (Text/String) | |
| 75 | term:lineShipToPostalCode | Term (Text/String) | |
| 76 | term:lineShipToRegion | Term (Text/String) | Country specific code to indicate regions / provinces within the tax authority. Preferably described according to ISO 3166-2. Example: GB-KEN for Kent county in the United Kingdom. |
| 77 | term:lineShipToStreetName | Term (Text/String) | |
| 78 | term:lineShipToUCR | Term (Text/String) | Unique consignment reference number |
| 79 | term:lineShipToWarehouseId | Term (Text/String) | Warehouse where goods held - also to identify work-in-progress, or stock-in-transit |
| 80 | term:lineSubsequentPi | Term (Text/String) | |
| 81 | 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. |
| 82 | term:lineSystemEntryUser | Term (Text/String) | User_ID (from User_Listing file) for person who created the record. |
| 83 | term:lineTaxInformationTaxAmount | Term (Decimal) | In the headers default currency. |
| 84 | term:lineTaxInformationTaxBase | Term (Text/String) | The base on which the tax is calculated. This can be an amount, or a quantity, eg. Litres. |
| 85 | term:lineTaxInformationTaxBaseDescription | Term (Text/String) | Description of the value in the TaxBase. Eg. Litres for excises on alcoholic bevarages. |
| 86 | term:lineTaxInformationTaxCode | Term (Text/String) | Tax Code for lookup in tables |
| 87 | term:lineTaxInformationTaxDeclarationPeriod | Term (Text/String) | The identification of the declaration/return in which the taxamount is reported to the Revenue body |
| 88 | term:lineTaxInformationTaxExemptionReason | Term (Text/String) | Tax exemption or reduction reason or rationale |
| 89 | term:lineTaxInformationTaxPercentage | Term (Decimal) | Tax percentage. |
| 90 | term:lineTaxInformationTaxType | Term (Text/String) | Tax type for look-up in tables |
| 91 | term:lineTaxPointDate | Term (Date) | Tax Point date where recorded or if not recorded then the Invoice date |
| 92 | term:lineToDate | Term (Date) | Enddate of the deliveries |
| 93 | term:lineUnitPrice | Term (Decimal) | Unit price for the unit/group of units per UOM in the headers default currency |
| 94 | term:lineUOMToUOMBaseConversionFactor | Term (Decimal) | Conversion factor of the InvoiceUOM to UOM Base. Only needed when InvoiceUOM is reported and is different from the UOM Base. |
| 95 | term:orderDate | Term (Date) | The date of the purchase order, regardless of the date the order is entered. |
| 96 | term:orderDocumentReference | Term (Text/String) | Identification number or code on the purchase order. The date of the purchase order, regardless of the date the order is entered. |
| 97 | term:orderNo | Term (Text/String) | Unique identifier for each purchase order. This ID may need to be created by concatenating fields (for example, document number, document type, and year) to uniquely identify each purchase order. |
| 98 | term:orderType | Term (Text/String) | |
| 99 | term:paymentTerms | Term (Text/String) | Payments terms for this invoice |
| 100 | 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. |
| 101 | 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). |
| 102 | term:postingStatus | Term (Text/String) | Status of the transactions posting to the GL (for example, Posted, Not Posted). |
| 103 | term:receiptNumbers | Term (Text/String) | The number(s) of the receipt(s) on this consolidated invoicerecord. Can be a single number, a range or a list. |
| 104 | term:salesOrderAmountLocal | Term (Decimal) | Sales monetary amount recorded in the local currency. |
| 105 | term:salesOrderId | Term (Text/String) | Sales order ID for invoiced items. Must match Sales_Order_ID in the Sales_Orders_YYYYMMDD_YYYYMMDD file. If no sales order, leave blank. |
| 106 | term:salesOrderLocalCurrency | Term (Text/String) | The currency for local reporting requirements. See ISO 4217 coding. |
| 107 | term:segment01 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 108 | term:segment02 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 109 | term:segment03 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 110 | term:segment04 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 111 | term:segment05 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 112 | term:selfBillingIndicator | Term (Text/String) | Indicator showing if a self-billing agreement exists between the customer and the supplier |
| 113 | term:settlementAmount | Term (Decimal) | In the headers default currency. |
| 114 | term:settlementCurrencyAmount | Term (Decimal) | Amount in foreign currency |
| 115 | term:settlementCurrencyCode | Term (Text/String) | Three-letter currency code according to ISO 4217 standard. Example: EUR for the Euros or USD for American Dollars. |
| 116 | term:settlementExchangeRate | Term (Decimal) | The exchange rate used. CurrencyAmount x ExchangeRate = Amount |
| 117 | term:settlementPaymentMechanism | Term (Text/String) | Payment mechanism |
| 118 | term:settlementSettlementDate | Term (Date) | Date settled |
| 119 | term:settlementSettlementDiscount | Term (Decimal) | Description Settlement / Other Discount |
| 120 | term:shipFromAdditionalAddressDetail | Term (Text/String) | |
| 121 | term:shipFromAddressType | Term (Text/String) | Field to differentiate between multiple addresses. To indicate the type of address. Choose from the predefined enumeration. (examples: StreetAddress PostalAddress, BillingAddress) |
| 122 | term:shipFromBuilding | Term (Text/String) | |
| 123 | term:shipFromCity | Term (Text/String) | |
| 124 | term:shipFromCountry | Term (Text/String) | Two-letter country code according to ISO 3166-1 alpha 2 standard. Example NL for the Netherlands. |
| 125 | term:shipFromDeliveryDate | Term (Date) | Date goods are delivered |
| 126 | term:shipFromDeliveryId | Term (Text/String) | Identification of the delivery |
| 127 | term:shipFromLocationId | Term (Text/String) | Location of goods in warehouse |
| 128 | term:shipFromNumber | Term (Text/String) | |
| 129 | term:shipFromPostalCode | Term (Text/String) | |
| 130 | term:shipFromRegion | Term (Text/String) | Country specific code to indicate regions / provinces within the tax authority. Preferably described according to ISO 3166-2. Example: GB-KEN for Kent county in the United Kingdom. |
| 131 | term:shipFromStreetName | Term (Text/String) | |
| 132 | term:shipFromUCR | Term (Text/String) | Unique consignment reference number |
| 133 | term:shipFromWarehouseId | Term (Text/String) | Warehouse where goods held - also to identify work-in-progress, or stock-in-transit |
| 134 | term:shipToAdditionalAddressDetail | Term (Text/String) | |
| 135 | term:shipToAddressType | Term (Text/String) | Field to differentiate between multiple addresses. To indicate the type of address. Choose from the predefined enumeration. (examples: StreetAddress PostalAddress, BillingAddress) |
| 136 | term:shipToBuilding | Term (Text/String) | |
| 137 | term:shipToCity | Term (Text/String) | |
| 138 | term:shipToCountry | Term (Text/String) | Two-letter country code according to ISO 3166-1 alpha 2 standard. Example NL for the Netherlands. |
| 139 | term:shipToDeliveryDate | Term (Date) | Date goods are delivered |
| 140 | term:shipToDeliveryId | Term (Text/String) | Identification of the delivery |
| 141 | term:shipToLocationId | Term (Text/String) | Location of goods in warehouse |
| 142 | term:shipToNumber | Term (Text/String) | |
| 143 | term:shipToPostalCode | Term (Text/String) | |
| 144 | term:shipToRegion | Term (Text/String) | Country specific code to indicate regions / provinces within the tax authority. Preferably described according to ISO 3166-2. Example: GB-KEN for Kent county in the United Kingdom. |
| 145 | term:shipToStreetName | Term (Text/String) | |
| 146 | term:shipToUCR | Term (Text/String) | Unique consignment reference number |
| 147 | term:shipToWarehouseId | Term (Text/String) | Warehouse where goods held - also to identify work-in-progress, or stock-in-transit |
| 148 | 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). |
| 149 | term:supplierId | 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. |
| 150 | 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. |
| 151 | term:systemEntryUser | Term (Text/String) | User_ID (from User_Listing file) for person who created the record. |
| 152 | term:systemId | Term (Text/String) | Unique number created by the system for the document |
| 153 | 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 |