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

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

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 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

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 Vendor Preferences page. This is editable prior to clicking the Build Batch 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

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

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

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

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

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.

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

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

This button displays the following options: “Include Filtered” and “Include Selected”. This allows users to add previously removed transactions back to the payment batch by selecting/filtering the transactions in the grid and clicking “Include Transactions” and choosing either “Include Filtered” or Include Selected”.

Included transactions credit the Accounts Payable Account are displayed in black font. Included transactions debit the Accounts Payable Account are displayed in red font.

 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 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. 

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.

This button displays the following options: “Remove Filtered” and “Remove Selected”. If filter criteria have been entered in the grid, and “Remove Filtered” is clicked, the filtered transactions will be removed from the payment batch. If the check box next to the transaction is checked and the “Remove Selected” is clicked, those transactions checked will be removed from the settlement batch.

Removed transactions are displayed in blue font.

Clicking the Edit Amounts toolbar icon opens a dialog box that allows users to edit the Discount Amount to Take (if applicable) and Max Amount to Pay. The 'Discount Amount to Take' field defaults from the 'Terms Discount Taken' column. This field is disabled if the Payment Terms of the transaction do not allow for discounts. The 'Amount' field defaults from the 'Max Amount to Pay' column.

The 'Amount' entered in the dialog box 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 & Close. Additionally, the 'Discount Amount to Take' entered in the dialog box cannot be greater than the 'Original Terms Discount Amt.' field. If so, the message "Cannot set a Discount Amount to Take greater than is left on the transaction" will be displayed on Save & Close.

The Edit Amounts toolbar icon will only open a dialog box when a single transaction is selected.  

Database Fields: ERPx_MFTransactionBatchTransaction.DiscountToConsume, ERPx_MFTransactionBatchTransaction.AmountToConsume

Identifies the maximum amount to be paid for the document. This is a non-editable text box that is required. This field is calculated as [Open Amount] - [Terms Discount Taken] - [Previous Payment Applications]. This field can be edited by clicking the 'Edit Amounts' icon in the grid header and entering a amount in the 'Amount' field on the Edit Amounts dialog box. This field is always editable from the Edit Amounts dialog box.

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 Field: ERPx_MFTransactionBatchTransaction.AmountToConsume

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.

Displays the original discount amount. This is a non-editable text box that is not required. It is calculated based on the Payment Terms associated with the transaction by using the [Percent of Discount] x [Amount] if the Payment Terms of the transaction allows for discounts. This field is for information only and never editable. It is not stored in the database.

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.

Identifies the amount of discount applied to the transaction. This is a non-editable text box that is not required. It defaults from the 'Orig. Terms Discount Amt.' 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. This field is only editable on the Edit Amounts dialog box if the Payment Terms of the transaction allows for discounts.

Database Field: ERPx_MFTransactionBatchTransaction.DiscountToConsume