Build Payment Batch Record View

Build Payment Batch Record View

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.

Software Version: 2022.03.18 and newer

[ 1 Page Header ] [ 2 Page Detail ] [ 2.1 Transactions Grid ] [ 2.1.1 Related Topics ] [ 2.1.1.1 Page Definitions ] [ 2.1.1.2 Technical Details ]

Page Header

Toolbar Icons

Description

Toolbar Icons

Description

Append to Batch

Updates the grid section with new transactions that match the filter criteria. This icon is only displayed after the initial batch is created to allow users to redefine search criteria and add additional transactions to the batch. 

 Append to Batch only adds new transactions to the batch, but does not remove previously added transactions from the batch.

Build Batch

Builds a payment batch based on filter criteria selected / entered. This icon is only displayed when a new batch is being created, and is replaced with "Append to Batch" after the initial payment batch is created. 

Delete

Grid Layout

Help

Print Reports

Process Payments

Opens Process Payments Record View for Vendors, where users can create, print and post check and ACH payments from the payment batch.

Fields

Description

Apply 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 prior to clicking the Build Batch button. After a payment batch is saved, this field is disabled.

Database Field: EERPx_MFTransactionBatch.BatchDate

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

 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 Build Batch button is clicked, 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 grid. 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

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 Vendor Preferences page. This is editable prior to clicking the Build Batch button. After a payment batch is saved, this field is disabled.

The lookup contains a list of all the 'Active' Checkbooks.

Database Fields: ERPx_MFCheckbook.CheckbookDescription, ERPx_MFTransactionBatch.CheckbookSK

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

Doc No

Identifies the document number of a transaction to be included in a payment batch. This is a text box that is not required to return results. If entered, it must be <= 150 characters. It defaults as blank and is always editable.

Database Field: ERPx_MFTransactionBatch.InvoiceNumber

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

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 as blank. If missing, the message "Include Transactions is required." will be displayed when the Build Batch button is clicked. 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 clicking the Build Batch button. Updating the value to "Document" will automatically update the 'Include Transactions' field to be "Invoices Only". 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

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 with no Transaction Classes selected 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

Used to enter a Vendor Name or Vendor ID to filter transactions for the payment batch. This is a text box that is not required to return results. It defaults as blank and is always editable.

Database Field: ERPx_MFTransactionBatch.VendorSKCSV

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