AP Invoices represent transactions that carry amounts the company owes for purchasing goods or services from a Vendor. AP Credit Memos represent transactions that carry amounts owed to the company because of returns and/or credits on goods or services previously purchased from a Vendor. The purpose of this page is to view, add, edit, remove, and post individual AP Invoices and Credit Memo transactions. These rules do not apply to Invoices linked to auto created Freight Purchase Orders.
Software Version: 2023.09.29 and newer
To view the help page for the NorthScope 2.0 Invoice/Credit Memo Record View, please click here: AP Invoices/Credit Memo Record View
Page Header
Header Toolbar
Toolbar Icons | Description |
---|---|
Delete | Deletes the transaction, batch, or master file record. When clicked, users will be prompted with: "Are you sure you want to delete this record?". Click "OK" to confirm, or "Cancel" to return without deleting. WARNING: Records cannot be recovered once they are deleted! |
Help | Opens the online WIKI help page for the current page. |
More Actions | Displays a drop down menu of related actions. The list of options includes:
|
New | Allows users to select the type of transaction or record they want to add. The list contains all the 'Active' Invoice and Credit Memo Transaction Class IDs displayed as [TransactionType] - [ClassID]. For example: "Invoice - Home Office". Note: The Transaction Class will not display after the Transaction Type if the Class ID is named "Default". |
Notes | Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled. Notes are used throughout the application to add additional details to Master Files and Transactions. Transactions and Master Files that support Notes store the text of the note in one or more 'Note Types' as a way to classify/organize notes. |
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. | |
Save | Saves the changes made to the record. |
Save & Close | Saves your changes and closes the page. |
Home Tab
INV# or MM#: [TransID] PO#: [PO] REQ#: [REQ#] Vendor Name (Currency) | |
Fields | Description |
---|---|
Comment | Identifies the header comment/description of the transaction or batch. This is text box that defaults as blank for manually entered transactions and is not required but If entered, it must be <=150 characters. If a 'PO #' is entered/selected for this transaction, and the PO contains a 'Comment', the Comment from the PO will populate here, but can be overwritten. This is always editable even after the transaction is posted. For transactions auto-generated from a Grower Ticket, this defaults to the value 'Created from Grower Ticket'. Database Field: ERPx_APTransactionHeader.Description |
Doc Date | Identifies the date of the transaction. This is a date picker to assign/edit a date for the transaction (to control Aging and payment term dates). This defaults to blank on New and is required to Approve or Post the transaction. If missing, the message "Doc Date is required." will be displayed on Save. The Doc Date must be on or before the GL Date when Approving or Posting the Invoice/Credit Memo. If not, the message "The GL Date must be on or after the Doc Date." will be displayed on Save. This is editable while the transaction is in a Status of "New". For transactions auto-generated from an Inventory Receipt, this defaults from the Receipt Date on the linked receipt transaction. For transactions auto-generated from a Grower Ticket, this defaults to the Ticket Delivery Date. Database Field: ERPx_APTransactionHeader.TransactionDate |
Doc No | 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 a text box to enter the document number your Vendor assigned to the invoice/credit memo. This defaults to blank, is required, must be unique by Vendor, and must be <= 50 characters. This is editable while the transaction in a status of "New". If missing, the message "Doc No is required." will be displayed on Approve or Ready to Post. If not unique for the Vendor assigned to the transaction, the message "Duplicate Doc No's are not allowed. Please enter a valid Doc No." will be displayed on Save. Note: If the transaction was created from a posted Grower Ticket, this value defaults to the Ticket Number of the corresponding ticket. Database Field: ERPx_APTransactionHeader.DocNumber |
Freight PO Amt. | Displays the total amount of source Freight Purchase Order. This is only applicable and visible for AP Invoices linked to a Freight Purchase Order, and only includes line items that were automatically added (not manually added lines). This is a calculated field that is not stored in the database. Note: This is only applicable for Invoice type transactions. |
Freight Variance Amt. | Displays the total variance between the amounts on the source Freight Purchase Order and the AP Invoice. This is only applicable and visible for AP Invoices linked to a Freight Purchase Order, and only includes line items that were automatically added from the source purchase order, (not manually added lines). This value is updated after Save when applicable line items are updated. This is a calculated field that is not stored in the database. Note: This is only applicable for Invoice type transactions. |
PO # | A Purchase Order # (aka PO #) is the unique identifier of a Purchase Order. Once a valid PO# has been selected, or manually entered, all the Purchase Order line items (with a remaining quantity) that are not already on the transaction will be auto-added to the transaction and both the 'PO #' and 'Vendor Name' values will be set and disabled. The 'Find PO#' window searches across all "valid" PO's. If a 'Vendor Name' has been entered on the transaction then only "valid" PO's for that Vendor will be returned, if the 'Vendor Name' is blank then all valid PO's will be returned across all Vendors. A 'PO #' is considered valid for AP Invoices based on:
A 'PO #' is considered valid for AP Credit Memos based on:
Database Fields: ERPx_APTransactionHeader.PurchaseOrderSK, ERPx_APPoHeader.PurchaseOrderID |
Reference | Identifies the Reference entered for the transaction. This is text box that defaults to blank and is not required, but if entered, it must be <=100 characters. This is always editable even after the transaction is posted. The Reference will not default from the Reference on a linked Purchase Order. These are treated as separate reference fields. 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. Database Field: ERPx_APTransactionHeader.Reference |
Status | Identifies the Status of the transaction. This is a single-select lookup that is required. It defaults as "New" and is always editable until the transaction is Posted. The Statuses that apply to transactions in this Record 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. Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. 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 with the exception any fields that are always editable and updates the Transaction Status to "Posted". 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. When an AP Invoice that is linked to a Purchase Order is Posted, if the Purchase Order Type is "Single Invoice and Receipt" and a receipt has already been posted, the Purchase Order Status will be auto-changed to "Closed". Database Fields: ERPx_APTransactionHeader.TransactionStatusSK |
Vendor Name | Identifies the name of the Vendor assigned to the transaction or master file. This is set in the Vendor Record View. This is a single-select lookup that is required, if missing the message "Vendor Name is required" is displayed on Save.
The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Vendors. Database Fields: Database Field: ERPx_APTransactionHeader.VendorSk, ERPx_APVendor.VendorName |
Properties Tab
Fields | Description |
---|---|
Group: 1 | |
GL Date | Identifies the date the transaction posted (or will post) to the general ledger. This is a date picker that defaults as blank and is required to Approve or Post the transaction. If it has not been manually assigned, it will be automatically set to the 'Doc Date' when the transaction is either Approved or Posted. To Approve or Post the transaction, the GL Date must fall within a Fiscal Period that is open for Purchasing and must be on or after the 'Doc Date'.
This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionHeader.GLDate |
Doc Date | Identifies the date of the transaction. This is a non editable control that shows the 'Doc Date' from the Home Tab. This is informational only from here. Database Field: ERPx_APTransactionHeader.TransactionDate |
Payment Terms | Identifies the Payment Terms assigned to the transaction. This is a single-select lookup that defaults from the Payment Terms assigned to the Primary Vendor on the Purchase Order, or the selected Vendor if the transaction is not linked to a Purchase Order. This is required and if missing, the message "Payment Terms are required when approving or posting transactions." will be displayed on Save. This is editable while in a status of New. Payment Terms identify the terms your company extends to your Customers and that your Vendors extend to you. Payment Terms are used to calculate aging and payment discounts. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Payment Terms. Database Fields: ERPx_MFPaymentTerms.PaymentTermName, APTransactionHeader.PaymentTermSK |
Discount Percent | This is a textbox that identifies the Discount percent associated with the Payment Terms, formatted to 5 decimal places. This is editable while the transaction is in a 'New' status and will be reset if the Payment Terms are changed. If the Payment Terms does not have a discount (e.g., "Net 30") this will default to 0.00000. Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. Database Fields: ERPx_MFPaymentTerms.DiscountPercent, APTransactionHeader.DiscountPercent |
Discount Days | This is a numeric textbox that identifies the Discount Days associated with the Payment Terms. This is editable and required if a Discount Percent is specified, if missing, the message "Discount Days is required" will be displayed on Save. The value must be >= 0 when specified. Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. Database Field: ERPx_APTransactionHeader.DiscountDays |
Due Days | This is a numeric textbox that identifies the Due Days associated with the Payment Terms. This is always required and must be >= 0 and >= 'Discount Days' value, if missing the message "Due Days is required" will be displayed on Save. This is editable while the transaction is in 'New' status. Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. Note: If the 'Due Date' value is changed, this value will be recalculated. Database Field: ERPx_APTransactionHeader.DueDays |
Discount Amount | This is a calculated field that identifies the total Discount Amount. It is calculated as Total [Invoice Amount] * [Payment Terms Discount Percent]. If the Payment Terms does not have a discount (e.g., "Net 30") this will be blank. |
Discount Date | Identifies the Discount Date of the transaction. This is a date picker that defaults as [Doc Date] + [Payment Terms Discount Days] and is required on transactions with a 'Payment Terms' that contain a Discount. For Payment Terms that do not include a discount it is blank and disabled. This is always editable, even after the transaction is Posted and can be edited to any date that is both:
Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. Note: Changing this for a posted transaction will only have an effect if the transaction has an open/unapplied balance. The Discount Date represents the last date that Payment Term Discounts apply. Database Field: ERPx_APTransactionHeader.DiscountDate |
Due Date | Identifies the Due Date of the transaction. This is a date picker that defaults as [Doc Date] + [Payment Terms Due Days] and is required. This is always editable, even after the transaction is Posted and can be edited to any date that is both:
Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. |