A lookup to assign one or more conditions you want included in your search. This lookup contains:

• Voids & Replaced
• Unposted Transactions

A single-select lookup to identify which 'Date' field will be used. The lookup contains the following values:

• Doc Date
• GL Date

A non-required text box that defaults to blank and is used to search across multiple fields. When the page is 'Refreshed', the data returned will be limited by what was included in the Search box (in addition to any other Search Options). 

Refer to this FAQ for advanced search options.

The Search field can be used to search across the following fields: 

• Doc No
• Item & Doc Description
• Purchase Order
• Transaction
• Vendor ID
• Vendor Name

Used to select one or more Transaction Classes. The values in this lookup are listed alphabetically. If there is more than one Transaction Class for the Transaction Type, then the value in the lookup will display as [Transaction Type] - [Transaction Class]. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each.

The lookup contains a list of all 'Active' AP Transaction Classes.

Used to select one or more Vendors. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

A Vendor is a company or person that sells goods or services to your company. They are used in Purchasing and on Brokerage Sales Programs.

The lookup contains a list of all 'Active' Vendors. 

Used to select one or more Vendor Classes. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

Vendor Classes are used to identify default values that will be applied to new Vendor accounts and to group Vendor accounts together for reporting purposes. 

The lookup contains a list of all 'Active' AP Vendor Classes.

 Displays a drop down menu of related actions. The list of options includes: 

• IQ: PO Linked Lines -Opens an inquiry with all the Purchase Orders, AP Invoices, AP Credit Memos, and Inventory Receipt lines with this Purchase Order assigned. 
• RV: Transaction. Opens the Transaction Record View in a new Tab.
• RV: Purchase Order - Opens the record view of the Purchase Order. If there is not a linked PO, a message will appear indicating "There is no Purchase Order for this transaction." 
• Void Transaction: Opens the Void Transaction Window.
• View in PaperVision - This option is only visible when the preferences for PaperVision are configured.

 Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. 

When clicked, all the Reports that launch from the Print Dialog that are assigned to this page, and that the user has rights to (if Report Data Access is enabled) are displayed.

If you plan on sending the Vendor a 1099 statement at the end of the year, this is used to specify the 1099 statement box number where you are most likely to report amounts. This is informational only and does not drive functionality. This is a single-select lookup that defaults from the 1099 Type of the Vendor assigned to the transaction. This is required and is always editable even after the transaction is posted.  

This lookup contains all the values in the ERPx_APTenNinetyNineType table.

Database fields: ERPx_APTenNinetyNineType.TenNinetyNineTypeDescription, ERPx_APVendor.TenNinetyNineTypeSK, ERPx_APTransactionLine.TenNinetyNineTypeSK

Identifies the Extended amount of the line item. This is required and is calculated as [Quantity] * [Price] for each transaction line. This can only be edited by changing the Quantity and/or Price of the transaction line. Positive lines represent a purchase and negative lines represent a purchase credit.

Database Field: ERPx_APTransactionLine.ExtendedAmount

Identifies an alternate comment/description for a line item. This is most commonly used to either identify the Vendor's Item ID or to add more clarity to a generic/bulk Item ID.  This is not required and can be edited from the 'Comment' on the 'Home' tab of the Invoice/Credit Memo Record View. This is always editable, even after the transaction is Posted.

Database Field: ERPx_APTransactionHeader.Description

Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency' on the 'Properties' tab of the Invoice/Credit Memo Record View. This is not editable on the transaction.

The Currency identifies the kind of money used for transactions. For example, if a Customer or Vendor is setup with a Currency of "USD" then all transactions for them are stated in terms of US Dollars and all payments received or made must be in US Dollars.

Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_APTransactionHeader.CurrencySK

Identifies how the (extended) amount of the line item was, or will be, applied. Identifies the name of a Project, Employee, Fisherman, Tender or Fisherman Loan. This is not required and can be edited from the 'Distributed To' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New.

Database Fields: ERPx_APVendor.VendorName, ERPx_MFEmployee.EmployeeName, ERPx_GLProject.ProjectDescription, ERPx_APTransactionLine.ToDistributionAccountSK

Identifies the type of distribution based on the selected Distributed To field.  (Project, Fisherman, Tender or Loan). This is not required and is derived from the 'Distributed To' on the Item grid of the Invoice/Credit Memo Record View. This is only editable by changing the Distributed To field on the transaction. This contains the associated value in the MFDistributionType  Enumeration Class.

Database Field: ERPx_APTransactionLine.ToMFDistributionTypeEN

Identifies the date of the transaction. This is required and can be edited from the 'Doc Date' on the 'Home' tab of the Invoice/Credit Memo Record View. This is always editable, even after the transaction is Posted.

Database Field: ERPx_APTransactionHeader.TransactionDate

Identifies the Doc No (document number) for the transaction. Unlike a Transaction ID that is system assigned based on the Transaction Class of the Transaction Type, this is a manually entered value. This is required and can be edited from the 'Doc No' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the transaction/Invoice # assigned by your Vendor. This is always editable while the transaction is in a Status of New.

Database Field: ERPx_APTransactionHeader.DocNumber

Identifies the date the transaction posted (or will post) to the general ledger.  This is required and can be edited from the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View. If not manually edited, this will be automatically set to match the 'Doc Date' when the transaction is saved with a Status of either Approved or Ready to Post. This is always editable while the transaction is in a Status of New.

Database Field: ERPx_APTransactionHeader.GLDate

Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View. This can only be edited by changing the GL Date.

Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View. This can only be edited by changing the GL Date.

Identifies the Description associated with the Item ID assigned to a transaction line, journal line detail or master file record. This is required.

Database Field: ERPx_APTransactionLine.ItemSK, ERPx_IMItem.ItemDescription

Identifies the ID of the Item.  This is required.

Database Field: ERPx_APTransactionLine.ItemSK, ERPx_IMItem.ItemID

Identifies the Last Updated Date & Time of the line item on the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user.

Database Field: ERPx_APTransactionLine.LastUpdated

Identifies the type of item and its behavior in the system. Item Types fall under two main categories: 

1. Item Types that maintain perpetual inventory balances 
   1. Inventory
2. Item Types that do not maintain perpetual inventory balances
   1. AP Expense 
   2. Freight
   3. Misc
   4. Tax

Identifies an alternate comment/description for a line item. This is most commonly used to either identify the Vendor's Item ID or to add more clarity to a generic/bulk Item ID.  This is not required and is always editable even after the transaction is posted.

Database Field: ERPx_APTransactionLine.LineComment

Identifies the payable account number for the line item. This is required and comes from the Vendor's 'Accounts Payable' on the 'GL Accounts' tab of the Vendors List View. Because this defaults from the Vendor, it is not editable on the transaction.

The GL Account that is assigned for the "Accounts Payable" Account Type, on the Accounts tab of the Vendor Record View and Vendor Class Record View. This is the account where accounts payable amounts are posted for the selected Vendor. 

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APVendor.APGLAcctRef

Identifies the name of the payable account number for the line item. This is required and comes from the Vendor's 'Accounts Payable' on the 'GL Accounts' tab of the Vendors List View. Because this defaults from the Vendor, it is not editable on the transaction.

The GL Account that is assigned for the "Accounts Payable" Account Type, on the Accounts tab of the Vendor Record View and Vendor Class Record View. This is the account where accounts payable amounts are posted for the selected Vendor. 

Database Fields: ERPx_GLAccount.Description, ERPx_APVendor.APGLAcctRef

Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. This is not required and can be edited from the 'PO #' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the purchase order you used when making the purchase. This is always editable while the transaction is in a Status of New.

 This field is only used for Purchase Orders setup in NorthScope. The 'Reference' field should be used to record a PO# on a transaction when the PO# does not exist in NorthScope. 

Database Field: ERPx_APTransactionHeader.PurchaseOrderID 

Identifies the Purchase Order line item that the AP Invoice/Credit Memo line item is linked to. This is a single-select lookup that is not required. This is editable while the transaction is in a Status of "New". 

 The Price and Quantity will not default from the Purchase Order line item. 

Database Field: ERPx_APTransactionLine.POLineSK

Identifies the price of the line item. This is required and can be edited from the 'Price' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New.

Database Fields: ERPx_APTransactionLine.Price

Identifies the GL Account the purchase line will post to. This is required and can be edited from the 'Purchase GL Account' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New. 

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APTransactionLine.AccountSK

Identifies the name of the General Ledger account assigned as the purchase account on the line item. This is required and can be edited from the 'Purchase GL Account' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New. 

Database Fields: ERPx_GLAccount.Description, ERPx_APTransactionLine.AccountSK

Identifies the quantity of the line item. This is required and can be edited from the 'Quantity' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New. 

Database Fields: ERPx_APTransactionLine.Quantity

Identifies the Reference entered for the transaction. This is text box that is not required and is always editable even after the transaction is posted.

A Reference number is used to record an additional tracking number that associates this transaction to another system. For example, if a transaction was imported from a 3rd party system this could be used to store the unique identifier from that system's transaction. 

Identifies the Status of the transaction. This can be edited from the 'Status' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the status of the transaction. This is always editable while the transaction is in a Status of 'New' or 'Approved'.

Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type.  The Statuses that apply to transaction in this List View include:

New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist.  

Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned.

Posted: Signifies the transaction has been posted and/or applied to a transactions (e.g. Payment Receipt). When a transaction is posted, it updates the General Ledger and/or On Hand Item Balances. While in the Status of 'Posted' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable.

Void: Signifies a previously posted transaction has been voided. This status is only available for transactions that support voiding posted records (not all transactions support this). Voided transactions remain in the database and can be viewed from history inquiries.

Replaced: Signifies the transaction was voided or corrected. When a transaction is corrected or Voided, the Status of the original transaction is changed to 'Replaced' and a new transaction is cloned and marked as 'Void'. This is done to ensure that a reversal journal entry can be created and posted in an open fiscal period to record the Void.

Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK

Identifies the unique Transaction ID for each transaction. Clicking on this link opens the AP Invoice / Credit Memo Record View for the selected record. This is a system assigned number that comes from the 'Transaction Class' and is required but is not editable by users.

Transaction numbers are system assigned IDs to differentiate unique transactions. Transaction ID's are unique by the unique combination of 'Transaction Type' + 'Transaction Class'.

Database Field: ERPx_APTransactionHeader.TransactionID

The unique identifier of the Transaction Class. This is required and comes from the 'Transaction Class ID' on the 'Properties' tab of the Invoice/Credit Memo Record View. This is not editable.

Transaction Classes are used to differentiate transactions within a Transaction Type. For example, Transaction Classes of Fresh and Frozen can be setup for the Transaction Type of 'Sales Order'. Transaction Classes are used in all functional areas throughout the application.

Database Fields: ERPx_APTransactionClass.TransactionClassDescription, ERPx_APTransactionHeader.TransactionClassSK

Identifies the Transaction Type for each transaction. This is required and comes from the Transaction Type selected when starting a new transaction. This is never editable.

Transaction Types are used to differentiate unique types transactions within the system. Transactions with the same Transaction Type share the same record view pages and business rules. Transaction Types can be further classified using Transaction Classes. Every transaction in the system is assigned a Transaction Type.

Database Fields: ERPx_APTransactionType.TransactionName, ERPx_APTransactionHeader.TransactionClassSK

Identifies the unit of measure that the units are stored in (Box, Bag, Case, Each, Tote, etc.) for a line item or on the transaction. This is not required and can be edited from the 'UOM' on the Item grid of the Invoice/Credit Memo Record View. This is only editable while the transaction is in a Status of New. 

Database Fields: ERPx_IMUOM.UOMID, ERPx_APTransactionLine.QuantityUOMSK