Inventory transactions described
When importing subledger transactions from a CSV or Excel file you must assign fields in the file to Caseware fields in the subledger dataset type you select on import, so that the transaction data displays correctly in the engagement. This topic details the fields in the Inventory transactions subledger.
For more information on the subledger dataset descriptions, see Understand subledger data.
For more information on importing transaction data from CSV files, see Import the client’s transactions from a CSV.
| Field | Usage |
|---|---|
| Transaction ID ( inventory_transaction_transaction_id) | The transaction identifier associated with either the Procure to Pay or Order to Cash Subledger Audit Data Standards (ADS). Data type: Text Required: No Primary key: The value of this field is used to form the unique identifier of this entry. |
| Transaction Date ( inventory_transaction_transaction_date) | The date of activity, per associated transaction document if applicable. Data type: Date Required: No Primary key: Third alternate. If Transaction ID is not present in the data, the value of this field is concatenated with the values of the other alternate fields to form the unique identifier of the entry, for example |
| Inventory Product ID ( inventory_transaction_product_id) | The product identifier is a code that uniquely identifies an item that you carry in inventory. Data type: Text Required: Yes Primary key: First alternate. If Transaction ID is not present in the data, the value of this field is concatenated with the values of the other alternate fields to form the unique identifier of the entry, for example |
| Serial Number ( inventory_transaction_serial_number) | If serialized, the serial number is captured here. Although serial number is the common term, the value is not limited to numeric values. While it is uncommon for an item to be both serial and lot controlled (the serial number unambiguously identifies the item), it is not necessarily mutually exclusive. Data type: Text Required: No Primary key: Fourth alternate. If Transaction ID is not present in the data, the value of this field is concatenated with the values of the other alternate fields to form the unique identifier of the entry, for example |
| Lot Number ( inventory_transaction_lot_number) | If representing a lot, the lot number is captured here. Although lot number is the common term, the value is not limited to numeric values. Data type: Text Required: No Primary key: Fifth alternative. If Transaction ID is not present in the data, the value of this field is concatenated with the values of the other alternate fields to form the unique identifier of the entry, for example |
| Transaction Type ( inventory_transaction_transaction_type) | The codes that describe the primary inventory-specific actions that take place in inventory transactions related to the movement of goods, trade, quantity adjustments from internal business events and cost adjustments, due to market factors or damage. Data type: Enum Required: No Example values: Goods Received (GR), Goods Shipped (GS), Inventory Transfers (IT), Inventory Adjustments (IA), Other (OT) Primary key: Second alternate. If Transaction ID is not present in the data, the value of this field is concatenated with the values of the other alternate fields to form the unique identifier of the entry, for example |
| Transaction Type System ( inventory_transaction_transaction_type_system) | A transaction code that is local to the underlying accounting software system. Data type: Text Required: No |
| Transaction Time ( inventory_transaction_transaction_time) | The time the activity occurred, per associated transaction document if applicable. Data type: Date/time Required: No |
| Transaction Quantity ( inventory_transaction_transaction_quantity) | The quantity or item affected expressed in location stocking unit. Data type: Decimal Required: No |
| Transaction Cost Adjustment ( inventory_transaction_transaction_cost_adjustment) | The per unit increase or (decrease) in stocking cost. Data type: Decimal Required: No |
| Transaction Description ( inventory_transaction_transaction_description) | A description of the transaction. Data type: Text Required: No |
| Transaction Associated Order ID ( inventory_transaction_transaction_associated_order_id) | The Customer Order, (Vendor) Purchase Order or other document associated with the transaction. Should specify whether the number found in Transaction Associated Order Line ID is from the Procure to Pay or Order to Cash Subledger Audit Data Standards (ADS) by using the text Data type: Text Required: No |
| Transaction Associated Order Line ID ( inventory_transaction_transaction_associated_order_line_id) | The line item number from a Customer Order, (Vendor) Purchase Order, to differentiate between multiple items in a single order for different quantities. Should specify whether the number found in Transaction Associated Order Line ID is from the Procure to Pay or Order to Cash Subledger Audit Data Standards (ADS) by using the text Data type: Text Required: No |
| Transaction Associated Document ID ( inventory_transaction_transaction_associated_document_id) | The picking ticket, shipping notice, or other document created upon/associated with movement. Should specify whether the number found in Transaction Associated Order Line ID is from the Procure to Pay or Order to Cash Subledger ADS by using the text Data type: Text Required: No |
| Transaction Associated Document Line ID ( inventory_transaction_transaction_associated_document_line_id) | The line number for a document other than a Customer Order, or Vendor Purchase Order. The document should specify whether the number found in Transaction Associated Order Line ID is from the Procure to Pay or Order to Cash Subledger ADS by using the text Data type: Text Required: No |
| Inventory From Location ( inventory_transaction_inventory_from_location) | The storage location from where the inventory originated. Data type: Text Required: No |
| Inventory To Location ( inventory_transaction_inventory_to_location) | The storage location to where the inventory is being sent. Data type: Text Required: No |
| Inventory System Or External Source ( inventory_transaction_inventory_system_or_external_source) | Used to indicate entry information associated with transaction initiated from other ADS module (for example, P2P, O2C) or initiated from within inventory. If initiated from within inventory fields below are used to capture user and GL information. Data type: Text Required: No |
| Inventory GL Line Debit Account Number ( inventory_transaction_gl_line_debit_account_number) | The general ledger (GL) account number on which the debit side of the transaction has been posted. Data type: Text Required: No |
| Inventory GL Line Credit Account Number ( inventory_transaction_gl_line_credit_account_number) | The general ledger (GL) account number on which the credit side of the transaction has been posted. Data type: Text Required: No |
| Project ID ( inventory_transaction_project_id) | The unique identifier for the project. Typically autogenerated by the source system. Data type: Text Required: No |
| Supplier ID ( inventory_transaction_supplier_account_id) | The unique identifier for the supplier. Typically autogenerated by the source system. Data type: Text Required: No |
| Customer Account ID ( inventory_transaction_customer_account_id) | The unique identifier for the receiving customer. Typically auto-generated by the source system. Data type: Text Required: No |
| Inventory Organization Code ( inventory_transaction_inventory_organization_code) | The code of the inventory organization. Inventory Organization refers to the organizational unit, physical or virtual, where the inventory transaction and balances may be tracked and monitored. It provides inventory information to modules like purchase and sales. The simplest form of inventory organization is a warehouse. Data type: Text Required: No |
| Inventory Stocking UOM Code ( inventory_transaction_inventory_stocking_uom_code) | The standardized measurement unit used to count stock items and to express them as specific quantities. Data type: Text Required: No |
| Inventory Costing UOM Code ( inventory_transaction_inventory_costing_uom_code) | The code of the measurement unit for inventory's cost. Data type: Text Required: No |
| Inventory Required By ( inventory_transaction_inventory_required_by) | The person or organization that makes requisition for inventory. Data type: Text Required: No |
| Cost Organization Code ( inventory_transaction_cost_organization_code) | The code of the cost organization, which refers to the organizational unit/level where the cost of outbound inventory will be calculated. The calculation may be done at the corporate level, the stocking organization level or at the particular locations where inventory is stored. Data type: Text Required: No |
| Inventory Cost ( inventory_transaction_inventory_cost) | The cost per unit using the method found in Inventory Cost Method, in Inventory on Hand. Data type: Text Required: No |
| Business Unit Code ( inventory_transaction_business_unit_code) | Used to identify the business unit, region, branch, and so on at the level that financial statements are being audited. Data type: Text Required: No |
| Entered By ( inventory_transaction_entered_by) | The user identifier of the person who created the record. Data type: Text Required: No |
| Entered Date ( inventory_transaction_entered_date) | Date the transaction was entered into the source 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. Data type: Date Required: No |
| Entered Time ( inventory_transaction_entered_time) | The time this transaction was entered into the source system. ISO 8601 representing time in 24-hour time (hhmm), for example, 1:00 PM = 1300. Data type: Date/time Required: No |
| Approved By ( inventory_transaction_approved_by) | The user identifier of the person who approved changes. Data type: Text Required: No |
| Approval Date ( inventory_transaction_approved_by_date) | Date the entry was approved. Data type: Date Required: No |
| Approval Time ( inventory_transaction_approved_by_time) | The time the entry was approved. ISO 8601 representing time in 24-hour time (hhmm), for example, 1:00 PM = 1300. Data type: Date/time Required: No |
| Last Modified By ( inventory_transaction_last_modified_by) | The user identifier of the last person to modify this entry. Data type: Text Required: No |
| Last Modified Date ( inventory_transaction_last_modified_date) | The date the entry was last modified. Data type: Date Required: No |
| Last Modified Time ( inventory_transaction_last_modified_time) | The time the entry was last modified. ISO 8601 representing time in 24-hour time (hhmm), for example, 1:00 PM = 1300. Data type: Date/time Required: No |
| Functional Currency Code ( inventory_transaction_functional_currency_code) | The functional or group currency related to the balance (ISO 4217:2015). Data type: Text Required: No |
| Entered By ( inventory_transaction_posted_user_id) | The unique identifier of the person who posted the record. Typically autogenerated by the source system. Data type: Text Required: No |
| Entered Date ( inventory_transaction_posted_date) | The date when the transaction was posted into the source system. Data type: Date Required: No |
| Entered Time ( inventory_transaction_posted_time) | The time the particular transaction was posted. Data type: Date/time Required: No |
