Build Payment Batch Record View 3.0
This record view also contains columns for each Attribute that is set up for the 'Vendors' attribute type. Because these are user defined, they are not included in the default view but can be added a saved layout. Vendor attributes are not included in the help documentation.
To view the help page for the NorthScope 2.0 Build Payment Batch Record View, please click here: Build Payment Batch Record View.
Software Version: 2023.06.30 and newer
Page Header
Header Toolbar
Toolbar Icons | Description |
|---|---|
Delete | |
Help | |
Process Payments | Opens Process Payments Record View for Vendors, where users can create, print and post check and ACH payments from the payment batch. |
Save | |
Save & Close |
d
Batch Properties Tab
Fields | Description |
Apply Expired Discounts | Determines if expired discounts should be applied or not. Any non-expired discounts are applied by default, but the discount amounts can be manually edited. This is a Yes/No lookup that is required. It defaults as "No" and is always editable. Database Field: EERPx_MFTransactionBatch.ApplyExpiredDiscounts |
Batch ID |
Database Field: ERPx_MFTransactionBatch.BatchID |
Checkbook |
The lookup contains a list of all the 'Active' Checkbooks. Database Fields: ERPx_MFCheckbook.CheckbookDescription, ERPx_MFTransactionBatch.CheckbookSK |
Include Transactions | Identifies the types of transactions to be included in the payment batch. This is a single-select standard lookup that is required to return results. This defaults to "Invoices, Credit Memos and Checks". If missing, the message "Include Transactions is required." will be displayed when the batch is built by clicking the Refresh or Save button. This field is always editable. This lookup contains the values in the APBuildCheckInclude Enumeration Class. Database Field: ERPx_MFTransactionBatch.APBuildCheckIncludeEN |
One Payment Per | Identifies whether payments should be applied per Document or per Vendor. One payment can be applied towards several invoices simultaneously and also several payment transactions can be used towards one invoice. This is a single-select standard lookup that is required to return results. It defaults as "Vendor" and is editable prior to building the batch (clicking the Refresh or Save button). Updating the value to "Document" will automatically update the 'Include Transactions' field to be "Invoices Only" and any Credit Memo's and Payments will be removed from the batch. After a payment batch is saved, this field is disabled. This lookup contains the values in the MFOneCheckPer Enumeration Class. Database Field: ERPx_MFTransactionBatch.MFOneCheckPerEN |
Payment Date | Identifies the date the payment will be applied, formatted from the users 'Date Format' preference. This is a date picker that defaults to the current date. It is required and if missing, will default to current date on Save. This date will automatically populate the 'Payment Date' field on the Process Payments Record View. This field is editable until payments are assigned, after this the field is disabled on Save. Note: The transactions displayed in the grid will be for Document Dates on or before the Payment Date entered. Database Field: EERPx_MFTransactionBatch.BatchDate |
Filters Tab
Fields | Description |
Discount Date as of | Identifies the Discount Date to use to filter transactions for the payment batch, formatted from the users 'Date Format' preference. Invoices and Credit Memos with a Discount Date on or before the defined 'Discount Date as of' field are added to the payment batch. This is a date picker that is not required to return results. This field defaults as blank and is always editable. Since payment transactions do not have Discount Dates, selecting a 'Discount Date as of' will not exclude payment transactions from the payment batch. Database Field: ERPx_MFTransactionBatch.DiscountDateAsOf |
Due Date as of | Identifies the Due Date to use to filter transactions for the payment batch, formatted from the users 'Date Format' preference. Invoices and Credit Memos with a Due Date on or before the defined 'Due Date as of' field are added to the payment batch. This is a date picker that is not required to return results. This field defaults as blank and is always editable. Since payment transactions do not have Due Dates, selecting a 'Due Date as of' will not exclude payment transactions from the payment batch. Database Field: ERPx_MFTransactionBatch.DueDateAsOf |
Search | Refer to this FAQ for advanced search options. The Search field can be used to search across the following fields:
|
Transaction Class | Identifies the transaction class(es) to be included in the payment batch. This is a multi-select lookup that is not required to return results. It defaults to All Transaction Classes and is always editable. This lookup contains a list of all active Transaction Classes where the TransactionTypeSK is either 1 (Invoice) or 2 (Credit Memo). In order to include transactions that are associated with an inactivated Transaction Class, the default option of no Transaction Classes selected should include transactions that are on inactive classes. Database Field: ERPx_MFTransactionBatch.TransactionClassSKCSV |
Vendor Class | Used to select a Vendor Class to filter transactions for the payment batch. This is a multi-select lookup that is not required to return results. It defaults as blank and is always editable. The lookup contains a list of all the 'Active' Vendor Classes. Database Fields: ERPx_MFTransactionBatch.VendorClassCSV |