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: YYYY.MM.DD and newer
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. Note: Append to Batch only adds new transactions to the batch, but does not remove previously added transactions from the batch. |
| Build 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. |
| Delete | Deletes the transaction 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! |
| Grid Layout | Opens the Saved Grid Layout menu that allows the user to select another saved layout, create a new layout, save changes to a layout, or assign a saved layout as the default for the page. Once changes are made to a grid, such as columns are added or removed, the user can click the Saved Grid Layout icon and save the changes to the grid layout and name the new layout. The new layout can also be set as the default, instead of the System View. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific).
|
| Help | Opens the online WIKI help page for the current page.
|
| Print Reports | Opens the Print dialog, showing any applicable printable reports to be printed, downloaded, and/or emailed. |
| Process Payments | Opens Process Payments record view, where users can create, print and post check and ACH payments from the payment batch. |
| Fields | Description |
| 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 Settlement Batch page 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]. This is a system assigned value and is never editable by a user. 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 to the Fisherman Accounting Settlement Default preference 'Default Fisherman Checkbook ID'. This is editable prior to clicking the Build Batch button. 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 where the Currency is USD. Database Fields: ERPx_MFCheckbook.CheckbookDescription, ERPx_MFTransactionBatch.CheckbookSK |
| Fisherman | Identifies the name of the Fisherman, Fisherman & Tender, Tender or Loan. This is a text box that allows users to enter all or part of a Fisherman, Tender, or Loan account. This is not required to select transactions in the settlement batch, defaults as blank and is always editable. The transactions selected for the batch are filtered based on this. Database Field: ERPx_MFTransactionBatch.VendorSKCSV |
| Fisherman Class | Identifies the description of the Fisherman Class associated with the transaction.This is a multi-select load on demand lookup that allows users to select one or more Fisherman Classes. This is not required to select transactions in the settlement batch, defaults as blank, and is always editable. The transactions selected for the batch are filtered based on this. The lookup contains a list of all the 'Active' Fisherman Classes. Database Field: ERPx_MFTransactionBatch.VendorClassCSV |
| Included Transactions | 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 |
| Search | 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 |
| Season | 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 |
| Settlement Comment | 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 |
| Settlement Date | 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 |
| Trans Date Thru | Identifies the transaction date to use to filter transactions. This is a date picker that allows users to search for a transaction based on the GL Date of the transaction. This field must be on or before the 'Settlement Date' field. Else, the message "Trans Date Thru must be on or before the Settlement Date" will be displayed. This field defaults as blank and is not required to display transactions in the settlement batch. The transactions selected for the batch are filtered based on this. Database Field: ERPx_MFTransactionBatch.AsOfDate |
The bolded view is the default view, which will determine the view will automatically display in when opened. 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.
| Toolbar Icons | Description |
| Edit Amounts | 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 |
| 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 only the filtered contents will be exported. |
| Included Transactions | 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. |
| Mass Update | Opens the mass update dialog, which allows to mass update the following properties:
|
| 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 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. |
| Fields | Description |
|---|---|
| Amount to Settle | 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.
Database Field: ERPx_MFTransactionBatchTransaction.AmountToConsume |
| Distributed Description | Identifies a description of the distribution, including the name of the Vendor, Fisherman, Fisherman & Tender, Tender or Loan. This is displayed for Tender Resale, AP Invoice/Credit Memo and Balance Transfer transaction types and not displayed for all other transaction types. For Tender Resale transaction types, this field comes from the 'Tender' field on the 'Home' tab of the Tender Resale record view. For AP Invoice/Credit Memo transaction types, this field comes from the 'Vendor' field on the 'Home' tab of the Invoice/Credit Memo record view. For Balance Transfer transaction types, this field comes from the 'Transfer Balance From - Debit' field on the Items grid of the Balance Transfer record view. This is only editable by changing the Tender, Vendor or Transfer Balance To fields on the associated transactions while in a Status of New. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.FromVendorSK (Tender Resale), ERPx_APTransactionHeader.VendorSK (AP Invoice/Credit Memo), ERPx_APTransactionLine.FromDistributionAccountSK (Balance Transfer) |
| Doc Date | Identifies the date of the transaction. For Fish Tickets, this defaults from the 'Landed Date' field. For Adjustments, Balance Transfers and Tender Resales, this defaults from the 'Date' field. For AP Credit Memos/Invoices and Fisherman Sales, this defaults from the 'Doc Date' field. For check and ACH payments, this defaults from the 'Payment Date' field. This field is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.TicketDate (Fish Ticket), ERPx_APTransactionHeader.TransactionDate |
| Doc Description | Error rendering macro 'excerpt-include' : No link could be created for 'Description - Header'. This field comes from the header 'Description' field on the 'Home' tab of the associated transaction. This is always editable.Database Field: ERPx_APTransactionHeader.Description |
| 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 field comes from the 'Doc No' field on the 'Home' tab of the associated transaction. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionHeader.DocNumber |
| Fisherman Name | Identifies the name of the Fisherman, Fisherman & Tender, Tender or Loan. This is displayed as [Account Name] ([Account ID]) and comes from:
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 | Identifies the Description for the line item. This comes from the 'Description' field for a specific line on Tender Resale, AP Invoice/Credit Memo, Balance Transfer and Adjustment transaction types. This will be blank for Fish Ticket, Payment, Payment Receipt and Fisherman Sale transaction types. This field is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionLine.LineDescription |
| 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. | Displays the total amount of the transaction. For AP Invoice/Credit Memo, Adjustment, Tender Resale and Balance Transfer transaction types, this comes from the 'Extended' amount of the individual line item. For Fish Ticket and Payment Receipt transaction types, this comes from the 'Amount' field. For Fisherman Sale transaction types, this comes from the 'On Account' field. For Check and ACH payment transaction types, this comes from the 'Amount' field for the specific check or ACH payment. This field is always editable by changing the Price or Quantity of line items while the transaction is in a Status of New.
Database Fields: ERPx_APTransactionLine.ExtendedAmount, ERPx_APTransactionheader.ExtendedAmount, ERPx_APDeliveryTicketHeader.TotalNetAmount |
| 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 | Identifies the unique Transaction ID for each transaction. Clicking on this link opens the transaction record view for the selected record. This is a system assigned number that comes from the 'Transaction Class' and is required but 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 Field: ERPx_APTransactionHeader.TransactionID, ERPx_APDeliveryTicketHeader.TicketNumber |
| Transaction Type | Identifies the Transaction Type for each transaction. This comes from the Transaction Type selected when starting a new transaction. This is 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_APTransactionHeader.TransactionClassSK, ERPx_APDeliveryTicketHeader.TransactionClassSK |