A Payment Batch is a process used to gather posted payable transactions, that have not been fully settled, and select/un-select transactions to be paid/applied resulting in a summarized list of Vendor Payments. The purpose of this page is to create, update and process Vendor payment batches. Users will be able to search for unapplied or partially applied invoice, credit memo and check payment transactions to include on the payment batch. Payment batches, when posted, automatically apply payable transactions and receivable transactions towards each other to settle vendor balances.

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	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.
Print	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.
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	Saves the changes made to the record.
Save & Close	Saves your changes and closes the page.

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	Displays the name of the batch. This is a single-select standard lookup that allows users to navigate between active batches. The field defaults to (Build New Batch) when the Build Payment Batch Record View is opened. Once the batch is built by clicking the Refresh or Save button, this field defaults to the username, formatted as [User First Name] + [User Last Name] + [Previous Batch Number + 1]. Selecting a Batch ID from the lookup will reload the page with the associated fields and transactions if any payments were saved in the batch. This is a system assigned value and is never editable by a user. A user may have several check batches simultaneously. Database Field: ERPx_MFTransactionBatch.BatchID
Checkbook	Identifies the Checkbook assigned to the transaction. This is a single-select standard lookup that allows users to select the checkbook that will be used to make the payments. This is required and defaults from the 'Default Vendor Checkbook ID' field on the Purchasing Preferences page, if blank, the message "Checkbook is required." will be displayed on Save. This is editable prior to building the batch (clicking the Refresh or Save button). After a payment batch is saved, this field is disabled. Checkbooks represent individual bank accounts (checking, savings, petty cash) that have funds deposited into, or payments made out of, that are reconciled to a bank statement. They are used in the Financial, Fisherman Accounting, Grower Accounting, Purchasing, and Sales Functional Areas to support receiving payments from customers, making payments, deposits, and other bank transactions. 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. The Discount Date represents the last date that Payment Term Discounts apply. 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. The Due Date represents the date the transaction must be paid by. 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	A non-required text box that defaults to blank and is used to search across all columns on the page. 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, if available). Refer to this FAQ for advanced search options. The Search field can be used to search across the following fields: Vendor Doc No Transaction
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. Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each. 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. 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. Database Fields: ERPx_MFTransactionBatch.VendorClassCSV

Page Detail

Transactions Grid

The purpose of this grid is to display and manage the individual transactions associated with the payment batch. Transactions that Credit the Accounts Payable Account will be displayed as positive and in black font. Transactions that Debit the Accounts Payable Account will be displayed as negative and in red font, as they will be subtracted from the payment amount. Transactions that are removed will be displayed in blue font. The default grid layout for this grid is grouped by Vendor Name. The group heading displays as "Vendor Name: [VendorName] + ([VendorID])".

Fields	Description
Toolbar Icons	Description
Clear Filtered	Provides a quick way to de-select all records for payment. When clicked, the values in the 'Amt. to Pay' and 'Terms Discount Taken' columns will be set to 0.00.
Column Filter Show/Hide	Toggles between displaying and hiding a filter row in the grid under the column headers. The filter row will be displayed by default if the Quick Column Filter is also implemented in the page. When enabled, this will allow users to type in text to filter by a specific column.
Excel	Exports the contents of the grid to an Excel file that will automatically download. The contents that export are those that are visible to the user. Therefore, if the user has filtered the view, or excluded columns, only the contents in the grid will be exported.
Group By Show/Hide	Toggles between displaying and hiding a row in the grid above the column headers to enable grouping by one or more column(s). Once displayed, users may drag and drop column headers to group by a specific column. Once the grid is grouped by a column(s), a subtotal footer row will display in the grouping for columns that have a page footer total.
Include Filtered	Provides a quick way to select all records for payment. When clicked, all the records within the filter where the 'Amt. to Pay' = 0.00 will be populated as: [Open Amt.] - [Terms Discount Taken].
Quick Column Filter	Used to filter across all columns in the grid. When the user types text into the Quick Column Filter text box, the grid's Filter Row will be automatically hidden. The text in the Quick Column Filter text box automatically replaces any existing Filter Row filters. The results of the data immediately refresh as you enter text.
Refresh	Re-queries the contents of the grid/page based on the Search Options or the default values for grids that do not support Search Options. This ONLY re-queries the contents of columns that are currently visible, if you add a new column the contents will be empty until you click 'Refresh' again. Builds a payment batch based on filter criteria selected / entered. This also allows users to add additional transactions to the batch if the filter/search criteria is redefined.
Saved Layouts	Displays the column layout lookup and related icons. This tool allows users to select a previously saved layout, create a new layout, save changes to a layout, forget/delete a layout and/or assign a saved layout as the default for the page. Once changes are made to the layout, such as columns are added or removed, the user can click the Save Layout icon and save the changes to the column layout. The visibility of the Filter Row is also saved with a saved layout. The new layout can also be set as the default. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific). Default layouts can be removed by clicking the 'Set as Default' button again when the current default layout is selected. Please note that existing saved grid layouts will display the Filter Row as hidden by default.
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Amt. to Pay	This is an editable text box that defaults to 0.00 and is required to process a payment. The amount entered cannot be greater than the 'Open Amt.' field. If so, the message "The Amount cannot be greater than is left on the transaction." will be displayed on Save. Database Field: ERPx_MFTransactionBatchTransaction.AmountToConsume
Currency	Identifies the Currency assigned to the transaction. This is a non-editable text box that is required. For Invoice and Credit Memo transactions, this defaults from the 'Currency' field on the 'Properties' tab of the Invoice/Credit Memo Record View. 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
Discount Date	Identifies the Discount Date of the transaction. This is a non-editable text box, formatted from the users 'Date Format' preference, that is not required. This field is only displayed if the Payment Terms of the transaction allows for discounts. It defaults from the 'Discount Date' field on the 'Properties' tab of the Invoice Record View. This field is for information only and never editable. The Discount Date represents the last date that Payment Term Discounts apply. Database Field: ERPx_APTransactionHeader.DiscountDate
Doc Date	Identifies the date of the transaction. This is a non-editable text box, formatted from the users 'Date Format' preference, that is required. For Invoice and Credit Memo transactions, this defaults from the 'Doc Date' field on the 'Home' tab of the Invoice Record View. For Payment transactions, this defaults from the date the payment was created. This field is for information only and never editable. Database Fields: ERPx_APTransactionHeader.TransactionDate (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.CreatedDate (Payment)
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 non-editable text box that is required. For Invoice and Credit Memo transactions, this defaults from the 'Doc No' field on the 'Home' tab of the associated transaction. For Payment transactions, this defaults from the 'Payment Number' field in the Payment grid of the Process Payments Record View. This field is for information only and never editable. Database Fields: ERPx_APTransactionHeader.DocNumber (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.TransactionID (Payment)
Due Date	Identifies the Due Date of the transaction. This is a non-editable text box, formatted from the users 'Date Format' preference, that is sometimes required. This field is only required on Invoice and Credit Memo transactions. It defaults from the 'Due Date' field on the 'Properties' tab of the Invoice Record View. This field is for information only and never editable. The Due Date represents the date the transaction must be paid by. Database Field: ERPx_APTransactionHeader.DueDate
Exchange table	A non-editable text box to show the ID of the 'Exchange Table' that was assigned to the transaction when it posted. This field will be blank for transactions that were posted in the Home Currency.
From Currency	A non-editable text box that displays the Currency from the transaction.
Last Updated By	Identifies the name of the user that last updated the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. It defaults from the 'Last Updated By' field on the 'Properties' tab of the Invoice Record View. This field is for information only. Database Field: ERPx_APTransactionHeader.LastUser
Open Amt.	Displays the amount due for payment on the transaction. This is a non-editable text box that is required. It is calculated as [Orig. Trans. Amt] - previous applications. This field is for information only and never editable. This field is not stored in the database. For transactions that Credit the Accounts Payable Account, this field will display as positive. For transactions that Debit the Accounts Payable Account, this field will display as negative.
Orig. Terms Discount Amt.	Displays the original discount amount. This is a non-editable text box that is not required. It defaults from the 'Discount Amount' filed on the 'Properties' tab of the Invoice Record View. This field is for information only and never editable. Database Field: ERPx_APTransactionHeader.DiscountAmount
Orig. Trans. Amt.	Displays the total amount of the transaction. This is a non-editable text box that is required. For Invoice and Credit Memo transactions, this defaults from the 'Amount' field on the 'Home' tab of the Invoice Record View. For Payment transactions, this comes from the 'Amount' field for the specific check or ACH payment on the Process Payments Record View. This field is for information only and never editable. For transactions that Credit the Accounts Payable Account, this field will display as positive. For transactions that Debit the Accounts Payable Account, this field will display as negative. Database Fields: ERPx_APTransactionHeader.ExtendedAmount (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.Amount (Payment)
Payment Exchange Rate	A non-editable text box that displays the 'Rate' (exchange rate) that applies to the 'Payment Date' from the header source transaction being applied on the 'Exchange Table' assigned to the record. This is set to 1.0000000 for all 'Payments' where the transaction Currency matches the 'Home Currency'. This is a looked-up value that is not editable from here.
Payment Exchange Rate Calc. Method	A non-editable text box to show the 'Calculation Method' being used to convert each application's currency (the 'From Currency') to the Home Currency (the 'To Currency'). This will either be "Multiply" or "Divide" and is set as follows: If the Payment Currency is in the Home Currency, then this will be set to "Multiply" If the 'From Currency' on the Exchange Table matches the 'Payment' Currency and the 'To Currency' on the Exchange Table matches the Home Currency, then the 'Calculation Method' on the transaction will match the 'Calculation Method' from the Exchange Table. If the 'From Currency' on the Exchange Table matches the 'Home Currency' and the 'To Currency' on the Exchange Table matches the Payment Currency, then the Inverse Exchange method will be used and the 'Calculation Method' on the transaction will be the opposite as it is on the Exchange Table.
Payment Gain/Loss	A non-editable text box to identify if the application results in a currency gain or loss. If the result is positive then we have a currency gain, if it is negative, we have a currency loss, and if it is 0.00 then this line is not part of the gain/loss journal entry. If any of the line items have a non-zero value in this field, then a currency gain/loss journal entry will be made on save. This will always be a separate Journal Entry because it must be made in the Home Currency. The journal entry is created, using the Apply Date of each transaction that had a non-zero value as follows: If the transaction results in a currency gain: Debit the Accounts Payable GL Account that was assigned to the transaction Credit the Company Currency's 'Realized Gain' GL Account. If the transaction results in a currency loss: Debit the Company Currency's 'Realized Loss' GL Account. Credit the Accounts Payable GL Account that was assigned to the transaction.
Purchase Exchange Rate	A non-editable text box that displays the 'Rate' (exchange rate from the currency exchange table) that applied to the Invoice transaction when it posted. This is set to 1.0000000 for all transactions that were posted in the 'Home Currency'. This is a looked-up value that is not editable from here.
Purchase Exchange Rate Calc. Method	A non-editable text box to show the 'Calculation Method' being used to convert each transaction's currency (the 'From Currency') to the Home Currency (the 'To Currency'). This will either be "Multiply" or "Divide" and is set as follows: If the Invoice/ Credit Memo transaction was in the Home Currency, then this will be set to "Multiply" If the 'From Currency' on the Exchange Table matches the Purchasing Currency and the 'To Currency' on the Exchange Table matches the Home Currency, then the 'Calculation Method' on the transaction will match the 'Calculation Method' from the Exchange Table. If the 'From Currency' on the Exchange Table matches the 'Home Currency' and the 'To Currency' on the Exchange Table matches the Purchase Currency, then the Inverse Exchange method will be used and the 'Calculation Method' on the transaction will be the opposite as it is on the Exchange Table.
Terms Discount Amt. Not Taken	Displays the discount amount that has not been used yet. This is a non-editable text box that is not required. It is calculated as [Orig. Terms Discount Amt.] - [Terms Discount Taken] if the Payment Terms of the transaction allows for discounts. Else, it will default as "0.00". This field will be automatically updated if the 'Terms Discount Taken' field is updated. This field is for information only and never editable. It is not stored in the database.
Terms Discount Taken	Identifies the amount of discount applied to the transaction. This is an editable text box that is not required. It defaults from the ' Terms Discount Amt. Not Taken' field when: The discount is not expired. The discount is expired, but the ‘Apply Expired Discounts’ is set to Yes. This defaults to "0.00" if the discount is expired and the ‘Apply Expired Discounts’ is set to No. It also defaults to "0.00" when the Payment Terms of the transaction do not allow for discounts. The amount entered cannot be greater than the ' Terms Discount Amt. Not Taken' field, otherwise the message "Cannot set a Discount Amount to Take greater than is left on the transaction" will be displayed on Save. This field is only editable if the Payment Terms of the transaction allows for discounts. Database Field: ERPx_MFTransactionBatchTransaction.DiscountToConsume
To Currency	A non-editable text box that displays the Home Currency.
Transaction	Identifies the unique Transaction ID for each transaction. Clicking on this link opens the transaction record view for the selected record. For Invoice and Credit Memo transactions, this is a system assigned number that comes from the associated Transaction Class and is required. For Payment transactions, this is a system assigned number that comes from the 'Next Check #' field for the associated Checkbook on the Checkbooks List View and is required. This field is never editable. 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 Fields: ERPx_APTransactionHeader.TransactionID (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.TransactionID (Payment)
Transaction Class	The unique identifier of the Transaction Class. This is a non-editable text box that is required for Invoice and Credit Memo transactions. It defaults from the 'Transaction Class' field on the 'Properties' tab of the Invoice Record View. This is blank for check / ACH payments. This field is for information only and never editable. Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each. Database Fields: APTransactionClass.TransactionClassDescription, ERPx_APTransactionHeader.TransactionClassSK
Transaction Type	Identifies the Transaction Type for each transaction. This is a non-editable text box that is required. This defaults from the Transaction Type selected when creating a new transaction. This field is for information only and 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_APTransactionClass.TransactionTypeSK, ERPx_APTransactionHeader.TransactionClassSK (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.TransactionTypeSK (Payment)
Vendor	Identifies the Vendor assigned to the transaction. It is displayed as VendorName (VendorID). This is a non-editable text box that is required. For Invoice and Credit Memo transactions, it defaults from the 'Vendor' field on the 'Home' tab of the Invoice Record View. For Payment transactions, this defaults from the 'Account' field on the Payments grid of the Process Payments Record View. This field is for information only and never editable. 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. Database Fields: ERPx_APVendor.VendorName (ERPx_APVendor.VendorID), ERPx_APTransactionHeader.VendorSK (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.EntitySK (Payment)
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 non-editable text box that is required. For Invoice and Credit Memo transactions, it defaults from the 'Vendor' field on the 'Home' tab of the Invoice Record View. For Payment transactions, this defaults from the 'Account' field on the Payments grid of the Process Payments Record View. This field is for information only and never editable. 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. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.EntitySK (Payment)

Page Header

Header Toolbar

Batch Properties Tab

Filters Tab

Page Detail

Transactions Grid

Related Topics

Page Definitions

Technical Details

Browser not supported