The purpose of this page is to create and update Fisherman Settlement batches for payments. Users will be able to search and include transactions on the payment batch for one or more fishermen, fishermen & tenders, tenders and loans.
Software Version: 2020.05.22 and newer
Table of Contents | ||
---|---|---|
|
Page Header
...
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.
Note: Append to Batch only adds new transactions to the batch, but does not remove previously added transactions from the batch.
...
Builds a batch (selects open transactions) based on the criteria a user has selected / entered. This icon is only displayed when a new batch is being created, it is replaced with "Append to Batch" after the initial batch is created.
...
Database Field: ERPx_MFTransactionBatch.BatchID
...
The lookup contains a list of all the 'Active' Checkbooks where the Currency is USD.
Database Fields: ERPx_MFCheckbook.CheckbookDescription, ERPx_MFTransactionBatch.CheckbookSK
...
Database Field: ERPx_MFTransactionBatch.VendorSKCSV
...
The lookup contains a list of all the 'Active' Fisherman Classes.
Database Field: ERPx_MFTransactionBatch.VendorClassCSV
...
Identifies the types of transactions to be included in the settlement batch. This is a multi-select load on demand lookup that allows users to lookup transactions by the specified transaction types. This is defaulted as blank and required to display transactions in the settlement batch. If missing, the message "Include Transactions is required." will be displayed when the Build Batch button is clicked. This field is always editable. The transactions selected for the batch are filtered based on this.
The lookup contains the following values: All, Adjustment, Balance Transfer, Credit Memo, Fish Ticket, Fisherman Sale, Invoice, Payment, Payment Receipt and Tender Resale
Database Field: ERPx_MFTransactionBatch.IncludedTransactionTypeSKCSV
...
This is a text box to enter all or part of a Transaction ID, Doc No, Ticket Number, Landing Number, or Delivery Number. This is defaulted as blank and is not required to display transactions in the settlement batch. This field is always editable. The transactions selected for the batch are filtered based on this.
Database Field: ERPx_MFTransactionBatch.Search
...
Identifies the Season associated with the transaction. This is a text box that allows users to limit the Fish Ticket Transactions by Season. It defaults as blank and is not required to display transactions in the settlement batch. This field is always editable. The Fish Tickets selected for the batch are filtered based on this.
Database Field: ERPx_MFTransactionBatch.SeasonSearch
...
Identifies the comment associated with the settlement batch. This is a text box that defaults as blank. It is not required, but if entered, it must be <= 250 characters. This field is always editable.
Database Field: ERPx_MFTransactionBatch.BatchComment
...
Identifies the date the settlement will be applied. 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 page. This field must be on or after the 'Trans Date Thru' field. If not, the message "Trans Date Thru must be on or before the Settlement Date" will be displayed. This field is editable prior to clicking the Build Batch button.
Database Field: EERPx_MFTransactionBatch.BatchDate
...
Database Field: ERPx_MFTransactionBatch.AsOfDate
Page Detail
Transactions Grid
The purpose of this grid is to display and manage the individual transactions associated with the settlement batch. Transactions that Credit the Settlement Accrual Account will be displayed as positive and in black font. Transactions that Debit the Settlement Accrual Account will be displayed as negative and in red font as they are will be subtracted from the payment amount. Users can edit the 'Hold Back Amt.' and 'Amount to Settle' fields for any Credit balance transaction (transaction that Credits the Settlement Accrual Account). The default grid layout for this grid is grouped by Fisherman Name. The group heading displays as "Fisherman Name: [VendorName] + ([VendorID]) + PO Amount: [POAmount]". The PO Amount comes from the 'Open PO's' field on the Fisherman Balance list view and if 0.00, then will not be appended to the Fisherman Name.
...
Clicking the Edit Amounts toolbar icon opens a dialog box that allows users to edit the amount to settle. It defaults to the Open Amount of the selected transaction. Users may enter the Amount and when Saved, the Amount will populate in the 'Amount to Settle' field. If the transaction that was edited is a payable transaction then the 'Hold Back Amt.' field will be recalculated as [Open Amt.] - [Amount to Settle] on the Build Settlement Batch page.
The 'Amount' field 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, if the 'Hold Back Comment' field was previously populated, the 'Hold Back Comment' field will be cleared if the user edits the 'Amount' field.
Note: The Edit Amounts toolbar icon will only open a dialog box when a single transaction is selected.
Database Field: ERPx_MFTransactionBatchTransaction.AmountToConsume
...
This button displays the following options: “Include Filtered” and “Include Selected”. This allows users to add previously removed transactions back to the batch by selecting/filtering the transactions in the grid and clicking “Include Transactions” and choosing either “Include Filtered” or Include Selected”.
Note: Removed transactions are displayed in blue font.
...
- Hold Back Comment: A text box that defaults to blank. Assigns the text to the selected/filtered transactions when Apply is clicked.
- Hold Back Method: A single-select lookup that defaults to "Hold back all Transactions by a fixed Amount", but also has an option for "Hold back all Transactions by a fixed Percent". Takes the 'Hold Back Percent / Amount' value in conjunction with the selected method and assigns the calculated amount to the 'Hold Back Amt.' field and the 'Amount to Settle' field for the selected/filtered transactions when Apply is clicked.
- Hold Back Percent / Amount: A text box that defaults to blank. Takes the 'Hold Back Method' selection in conjunction with the value entered and assigns the calculated amount to the 'Hold Back Amt.' field and the 'Amount to Settle' field for the selected/filtered transactions when Apply is clicked.
Hold Back Amounts and Hold Back Comments will only apply to transactions where the 'Payable (GL Credit)" value is "Yes".
...
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 settlement 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. If there was value in the 'Hold Back Comment' field, it will be cleared when the transaction is removed from the settlement batch.
Note: Removed transactions are displayed in blue font.
...
Identifies the maximum amount to be paid for the document. This field is calculated as [Open Amount] - [Hold Back Amt.]. This field can be changed by clicking the 'Edit Amounts' icon in the grid header and entering a amount in the 'Amount' field or by entering a value in the 'Hold Back Amount' field on the Mass Update dialog box. This field is always editable.
For transactions that Credit the Settlement Accrual Account, this field will display as positive (for example $100.00) regardless of the 'Show Credit balances on the Fisherman Balance page and aging reports as:' default preference. For transactions that Debit the Settlement Accrual Account, this field will display as negative (for example -$100.00) regardless of the 'Show Credit balances on the Fisherman Balance page and aging reports as:' default preference.
Database Field: ERPx_MFTransactionBatchTransaction.AmountToConsume
...
Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.FromVendorSK (Tender Resale), ERPx_APTransactionHeader.VendorSK (AP Invoice/Credit Memo), ERPx_APTransactionLine.FromDistributionAccountSK (Balance Transfer)
...
Database Field: ERPx_APDeliveryTicketHeader.TicketDate (Fish Ticket), ERPx_APTransactionHeader.TransactionDate
...
Database Field: ERPx_APTransactionHeader.Description
...
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. Insert excerpt Def - Payment Batch Def - Payment Batch nopanel true
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
Table of Contents | ||
---|---|---|
|
Page Header
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.
| ||||||||||||||||
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 |
Database Field: ERPx_MFTransactionBatch.BatchID | ||||||||||||||||
Checkbook |
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.
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.
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
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 |
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])".
Toolbar Icons | Description | |||||||||||||||||||||
Edit Amounts | 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.
Database Fields: ERPx_MFTransactionBatchTransaction.DiscountToConsume, ERPx_MFTransactionBatchTransaction.AmountToConsume | |||||||||||||||||||||
Excel |
| |||||||||||||||||||||
Included Transactions | 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”.
| |||||||||||||||||||||
Remove Transactions | 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.
| |||||||||||||||||||||
Fields | Description | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Checkbox |
| |||||||||||||||||||||
Doc Date |
Database Fields: ERPx_APTransactionHeader.TransactionDate (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.CreatedDate (Payment) | |||||||||||||||||||||
Doc No |
Database Field: ERPx_APTransactionHeader.DocNumber 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) | |||||||||||||||||||||
Discount Date | ||||||||||||||||||||||
Open Amt. | Displays the amount due for payment on the transaction. This field is required and calculated by taking the Original Transaction Amount and subtracting any applications that have previously been made. This field is never editable.
| Orig. Trans. Amt. | ||||||||||||||||||||
Insert excerpt | Amount - Original | Amount - Original | ||||||||||||||||||||
nopanel | true | |||||||||||||||||||||
Payable (GL Credit) | Displays whether or not the transaction is a payable. The value will display as "Yes" if the transaction resulted in a Credit to the Settlement Accrual Account. The value will display as blank if the transaction resulted in a Debit to the Settlement Accrual Account. This field is not stored in the database and is never editable. | |||||||||||||||||||||
Transaction | Account Name Account Name |
This field is always editable while the transaction is in a Status of New. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK (Payment Receipt, Fisherman Sale & Tender Resale), ERPx_APTransactionLine.ToDistributionAccountSK (Adjustment & Balance Transfer), ERPx_APTransactionHeader.VendorSK (AP Invoice & AP Credit Memo), ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK (Fish Ticket), ERPx_APSettlementTransaction.SettleToEntitySK (Payment) | ||||||||||||||||||||
Hold Back Amt. | Identifies the hold back amount to be paid for the payable document. This field comes from a fixed amount or percentage of the Original Transaction Amount that has been held back using the Mass Update button in the grid header. This field is also auto calculated as [Open Amt.] - [Amount to Settle] for a payable document when the user clicks the 'Edit Amounts' button and enters an amount. For payable transactions that credit the Settlement Accrual Account, this field is always editable. For receivable transactions that debit the Settlement Accrual Account, this field displays "0.00" and is not editable. This value is not stored in the database.
| |||||||||||||||||||||
Hold Back Comment | Identifies the hold back comment for the transaction. This field comes from a combination of the values entered/selected on the 'Hold Back Amount', 'Hold Back Comment' and 'Hold Back Method' fields on the Mass Update dialog box. If no values are entered for the 'Hold Back Comment' field on the Mass Update dialog box, the 'Hold Back Comment' field on the Build Settlement Batch will be "Hold Back Amount: " + [Hold Back Amount] or "Hold Back Percent: " + [Hold Back Amount], depending on the user selection for the 'Hold Back Method' field. If a value is entered on the 'Hold Back Comment' field on the Mass Update dialog box, the 'Hold Back Comment' field on the Build Settlement Batch will be [Hold Back Comment] + "Amount: " or "Percent: " + [Hold Back Amount]. This field is not required, but if entered, it must be <= 100 characters. For payable transactions that credit the Settlement Accrual Account, this field is always editable. For receivable transactions that debit the Settlement Accrual Account, this field is not editable.
Database Field: ERPx_MFTransactionBatchTransaction.HoldBackComment | Line Description | ||||||||||||||||||||
Insert excerpt | Description - Item | Description - Item | ||||||||||||||||||||
nopanel | true | |||||||||||||||||||||
Transaction ID | Transaction ID | nopanel | true |
Database Field: ERPx_APTransactionHeader.DiscountDate | ||||||||||||||||||
Due Date |
Database Field: ERPx_APTransactionHeader.DueDate | |||||||||||||||||||||
Max Amount to Pay | 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.
Database Field: ERPx_MFTransactionBatchTransaction.AmountToConsume | |||||||||||||||||||||
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.
| |||||||||||||||||||||
Orig. Trans. Amt. |
Database Fields: ERPx_APTransactionHeader.ExtendedAmount (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.Amount (Payment) | |||||||||||||||||||||
Orig. Terms Discount Amt. | 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. | |||||||||||||||||||||
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 a non-editable text box that is not required. It defaults from the 'Orig. Terms Discount Amt.' field when:
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 | |||||||||||||||||||||
Transaction |
Database Fields: ERPx_APTransactionHeader.TransactionID (Invoice/Credit Memo), ERPx_MFCheckbookTransaction.TransactionID (Payment) | |||||||||||||||||||||
Transaction Class |
Database Fields: APTransactionClass.TransactionClassDescription, ERPx_APTransactionHeader.TransactionClassSK | |||||||||||||||||||||
Transaction Type |
Database Field: Fields: ERPx_APTransactionType.TransactionName, ERPx_APTransactionClass.TransactionTypeSK, ERPx_APTransactionHeader.TransactionIDTransactionClassSK (Invoice/Credit Memo), ERPx_APDeliveryTicketHeader.TicketNumber MFCheckbookTransaction.TransactionTypeSK (Payment) | |||||||||||||||||||||
Vendor Name |
Database Fields: ERPx_APVendor.VendorName (ERPx_APTransactionTypeAPVendor.TransactionNameVendorID), ERPx_APTransactionHeader.TransactionClassSKVendorSK (Invoice/Credit Memo), ERPx_APDeliveryTicketHeader.TransactionClassSKMFCheckbookTransaction.EntitySK (Payment) |
Related Topics
Expand | ||
---|---|---|
| ||
Page Definitions |
...