The purpose of the Payment Receipt Record View is to enter payments received by Fishermen, Fishermen & Tenders, Tenders and Loans. From here, users can open the 'Apply Documents' window, review the Journal Details, and post the receipt. When receipts are posted, the Fisherman Balances and Fisherman Aging are updated and the receipt becomes available to the Checkbook Deposit transaction. Payment Receipts make a journal entry when they are posted.
Software Version: 2020.05.22 and newer
Page Header
Header Toolbar
| Toolbar Icons | Description |
|---|---|
| Apply Documents | Opens the Apply Fishing Transactions record view allowing the user to apply this receipt to one or more open transactions. The Apply Documents button is disabled when the 'Amount' field is 0 and other required fields are not completed. |
| Delete | Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". 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.
|
| Journal Details | Opens the Journal Details window showing the Journal Entry for this transaction.
The Journal Details Window for this transaction will include:
|
| New | Allows users to select the type of transaction or record they want to add. The list contains:
|
| Opens the Print dialog, showing any applicable printable reports to be printed, downloaded, and/or emailed. | |
| Save | Saves the changes made to the record.
|
If a Payment Receipt that has been fully or partially applied is deleted (prior to posting), all applications will be automatically removed. | Fields | Description |
| Amount | Identifies the dollar amount of the payment received. This is a text box that is required. This defaults to 0.00 and must be > 0.00 to Approve and/or Post. If not, the message "Amount must be greater than 0.00." will be displayed. This field is only editable while the transaction Status is "New" and while no applications exist for the receipt. Editing this value and saving the transaction will re-calculate the 'Remaining' field. Linked Database Field: ERPx_APTransactionHeader.ExtendedAmount |
| Checkbook | Identifies the checkbook where the receipt will be deposited into. This is a single-select standard lookup that is required. This defaults using the following logic:
This is required to Approve and/or Post, or to open the Apply Fishing Transactions list view. This field is enabled and only editable while the transaction Status is "New". 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.CheckbookID, ERPx_APTransactionHeader.CheckbookSK |
| Description | Identifies the description associated with the payment receipt. This is a text box where users can enter a comment for the associated receipt but is not required. If entered, it must be <= 60 characters. This defaults to blank and is always editable, even after the transaction is posted. Linked Database Field: ERPx_APTransactionHeader.Description |
| Payment # | Identifies the number of the payment received, most often associated with the Check #. This is a text box that is not required. If entered, the value must be <= 50 characters. This defaults to blank and is always editable, even after the transaction is posted. Linked Database Field: ERPx_APTransactionHeader.DocNumber |
| Received From | Identifies the name of the Fisherman, Fisherman & Tender, Tender or Loan. This is a single-select standard lookup to select who the payment is coming from. It defaults to blank, but is required. If not assigned, the message "Received From is required." will be displayed. This field is only editable while the transaction Status is "New" and the 'Applied Amount' is blank or 0.00. A Fisherman is an Account Type used to identify someone that catches fish and sells them to a processing facility. A Tender is a vessel that is attendant to other vessels and is used to transport or ferry unprocessed fish or shellfish received from another vessel to a shoreside processor or mothership. Tender vessels operate, in most circumstances, as an agent for a specific processor and take deliveries from harvesting vessels. A Fisherman & Tender is an Account Type used to identify someone that catches fish during one season and provides Tendering services during another. The lookup contains the current assigned value and a list of all the 'Active' Fishermen, Fishermen & Tenders, and Tenders and Loans that have not been excluded from the "Cash Receipt" Transaction on the 'Excluded Transaction' tab of the Fisherman & Tender Record View. Linked Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK |
| Receipt Date | Identifies the date the receipt was received. This is a date picker that defaults to the current date. It is required to Approve and/or Post or to open the Apply Fishing Transactions list view. If not, the message "Receipt Date is required." will be displayed. This field is only editable while the transaction Status is "New" and is disabled once an application for this receipt has been made.
Linked Database Field: ERPx_APTransactionHeader.TransactionDate |
| Receipt Type | Identifies the type of the receipt. This is a single-select standard lookup the is required to Approve and/or Post. This defaults to "Check". This field is only editable while the transaction Status is "New". The lookup contains all the values in the MFCashReceiptType Enumeration Class. Linked Database Field: ERPx_APTransactionHeader.CashReceiptTypeEN |
| Remaining | Identifies how much of the receipt still needs to be applied. This is a non-editable text box that is required. This defaults from 'Amount' entered but will re-calculate as the receipt is applied. Receipts can be posted without applying, but if they have been applied, this amount will be >= 0.00 and < 'Amount'. This is a calculated field that is not editable on this page. This field is not stored in the database. |
| Status | Identifies the Status of the transaction. This is a single-select standard lookup that defaults as 'New' and is required. This is always editable while the transaction is in a Status of 'New' or 'Approved'. Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type. The Statuses that apply to transactions in this List View include: New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist. Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned. Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted". Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK |