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 Customer 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: YYYY.MM.DD and newer
Page Header
Header Toolbar
Toolbar Icons | Description |
---|---|
Apply Documents | Opens the Apply Fishing Transactions list 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. |
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! If a Payment Receipt that has been fully or partially applied is deleted (prior to posting), all applications will be automatically removed. |
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). The bolded view is the default view, which will determine the view will automatically display in when opened. |
Help | Opens the online WIKI help page for the current page. This icon is only visible on pages that are documented in the online help. |
Journal Details | Opens the Journal Details window showing the Journal Entry for this transaction. Until the transaction Approved or Posted, this is a temporary journal entry so no Journal ID will be assigned. The Journal Details Window for this transaction will include:
|
New | Allows the user to create a new master file record or transaction by opening a blank record view page. This icon is always enabled. |
Notes | Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled. |
Opens the Print dialog, showing any applicable printable reports to be printed, downloaded, and/or emailed. | |
Save | Saves the changes made to the record. It is only necessary to click the Save button when a change is detected on the page. When a change has been made, a ‘ + ‘ character is displayed prior to the page name in the page title bar (light blue bar in the upper left corner of the page). Clicking Save reloads the page. |
Home Tab
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 after a 'Customer' has been selected and 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 'Applied' and 'Unapplied' fields. Linked Database Field: ERPx_ARTransactionHeader.ExtendedAmount |
Applied Amt. | Identifies how much of the receipt has been applied. This is a non-editable text box that is required. This defaults to 0.00 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. This is a calculated field that is not editable. This field is not stored in the database. |
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 after the Fisherman is selected:
This is required before you can enter/edit the remaining receipt fields, Approve and/or Post, or to open the Apply Fishing Transactions list view. If not assigned, the message "Checkbook is required" will be displayed. This field is enabled after a 'Fisherman' has been selected and while the transaction Status is "New". This field is only editable after a 'Fisherman' has been selected and while the transaction Status is "New" and no applications for this receipt have been made. 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 |
Comment | Identifies the comment associated with the payment receipt. This is a text box that is not required. This defaults to blank and is only editable after a 'Fisherman' has been selected. If entered, it must be <= 60 characters. This field is always editable. Linked Database Field: ERPx_ARTransactionHeader.Description |
Currency | Identifies the currency of the receipt. This is a non-editable single-select standard lookup that is required. It defaults to "USD" and cannot be edited. Linked Database Field: ERPx_ARTransactionHeader.CurrencySK |
Fisherman | 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 before anything other than the 'Receipt Date' can be edited. If not assigned, the message "Fisherman is required." will be displayed. Because this value determines the initial values assigned for the 'Checkbook', if it is changed after it has been assigned, a message will appear as: "Changing the Fisherman will reset the Checkbook." This field is only editable while the transaction Status is "New" and the 'Applied Amount' is blank or 0.00. The lookup contains the current assigned value and a list of all the 'Active' Fishermen, Fishermen & Tenders, and Tenders and Loans not on hold. Linked Database Field: ERPx_ARTransactionHeader.CustomerSK |
Payment # | Identifies the number of the payment received, most often associated with the Check #. This is a text box that is not required. This field defaults to blank and is only editable after a 'Fisherman' has been selected. This field is always editable, even after the transaction is posted. Linked Database Field: ERPx_ARTransactionHeader.DocNumber |
Receipt Date | Identifies the date the receipt was received. This is a date picker field 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. If you need to change the 'Receipt Date' after an application has been made, you must unapply all the transactions that are currently applied. Linked Database Field: ERPx_ARTransactionHeader.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 after a 'Fisherman' has been selected and while the transaction Status is "New". The lookup contains all the values in the MFCashReceiptType Enumeration Class. Linked Database Field: ERPx_ARTransactionHeader.CashReceiptTypeEN |
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 |
Unapplied Amt. | 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. |
Properties Tab
Fields | Description |
Checkbook Currency | A non-editable text box to identify the Currency ID for the currency assigned to the Checkbook. Receipts cannot be posted if this value is missing. Linked Database Field: ERPx_MFCheckbook.CurrencySK |
CheckbookSK | A non-editable text box to identify the SK value of the Checkbook assigned to the Transaction. This is a looked-up value, that is primarily used for support. Linked Database Field: ERPx_ARTransactionHeader.CheckbookSK |
Created | A non-editable text box to identify the Created Date & Time of the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. Linked Database Field: ERPx_ARTransactionHeader.CreatedDate |
Created By | A non-editable text box to identify the name of the user that created the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. Linked Database Field: ERPx_ARTransactionHeader.CreatedBy |
CustomerSK | A non-editable text box to identify the SK value of the Customer on the Transaction. This is a looked-up value, that is primarily used for support. Linked Database Field: ERPx_ARTransactionHeader.CustomerSK |
GL Date | The date the transaction posted (or will post) to the general ledger. If unassigned when the transactions Status is changed to "Approve" or "Ready to Post", it will default from the Transaction Date. To Approve or Post, the GL Date must be in a valid period that is open for posting. If not the message, "The Fiscal Period is not open." will be displayed on Save. For Payment Receipts only, If blank, the value will be automatically updated as follows:
The GL Date must be >= the 'Receipt Date'. If not, the message "GL Date must be >= the Receipt Date." will be displayed on Save. The GL Date must fall within a Fiscal Period that is open for Sales. If not, the message, "The Fiscal Period is not open." will be displayed on Save. Linked Database Field: ERPx_ARTransactionHeader.GLDate |
Last Updated | A non-editable text box to identify the Last Updated Date & Time of the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. Linked Database Field: ERPx_ARTransactionHeader.LastUpdated |
Last Updated By | A non-editable text box to identify the name of the user that last updated the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. Linked Database Field: ERPx_ARTransactionHeader.LastUser |
Receipt Currency | A non-editable text box to identify the currency of the receipt. Receipts may not always be in the same currency as the Checkbook. Linked Database Field: ERPx_ARTransactionHeader.CurrencySK |
Transaction ID | A non-editable text box to identify the Transaction #. This is a system assigned value that is not editable by a user. Linked Database Field: ERPx_ARTransactionHeader.TransactionID |
TransactionSK | Error rendering macro 'excerpt-include' : No link could be created for 'Transaction SK - RV'. Linked Database Field: ERPx_ARTransactionHeader.TransactionHeaderSK |
MC: Exchange Date | This field is used to convert the transaction total 'Receipt Amount' to the 'Home Currency' amount. This is a non-editable text box to show the date range of the 'Rate' (Exchange Rate) on the 'Exchange Table' being used to convert the 'Receipt Amount' to the 'Home Currency' amount. This is only displayed and required when the Receipt currency is not in the 'Home Currency'. This is looked-up using the 'Receipt Date', not the 'GL Date'. This is displayed as: From [Rate From] to [Rate to]. For example, "From 10/01/19 to 10/07/19". The date values are formatted based on the User Preference for 'Date Format'. This value is a looked up from the 'Exchange Table' and not stored in the database while the transaction is in a Status of "New". When the Status is changed to either "Approved" or "Ready to Post" the value is updated and written to the database. For posted transactions, this is the value that existed when the transaction posted. |
MC: Exchange Rate | This field is used to convert the transaction total 'Receipt Amount' to the 'Home Currency' amount. This is a non-editable text box to show the 'Calculation Method' and 'Rate' being used to convert the 'Receipt Amount' to the 'Home Currency' amount. This is only displayed and required when the Receipt's currency is not in the 'Home Currency'. It is set as follows:
This is formatted as: [Calculation Method] by [Rate]. For Example, "Multiply by 1.0250" or "Divide by 1.0250". This value is a looked up from the 'Exchange Table' and not stored in the database while the transaction is in a Status of "New". When the Status is changed to either "Approved" or "Ready to Post" the value is updated and written to the database. For posted transactions, this is the value that existed when the transaction posted. |
MC: Exchange Table | This field is used to convert the transaction total 'Receipt Amount' to the 'Home Currency' amount. This is a non-editable text box that displays the 'Exchange Table ID' used to convert the 'Receipt Amount' to the 'Home Currency' amount. This is only displayed and required when the Receipt's currency is not in the 'Home Currency'. This is assigned as the first Exchange Table containing both the 'Home Currency' and the foreign currency assigned to the Receipt, with a valid 'Rate' (exchange rate) for the 'Receipt Date'. If there are no Rates that cover the 'Receipt Date' then the last Rate will be used. If there are no Exchange Tables containing both the 'Home Currency' and the foreign currency then this will be blank and the message "A valid exchange does not exist between [ReceiptCurrencyID] and [HomeCurrencyID]." will be displayed on Save after the Status is changed to Approve and/or Ready to Post. This value is a looked up from the 'Exchange Table' and not stored in the database while the transaction is in a Status of "New". When the Status is changed to either "Approved" or "Ready to Post" the value is updated and written to the database. For posted transactions, this is the value that existed when the transaction posted. |
MC: Currency Conversion | This field is used to convert the transaction total 'Receipt Amount' to the 'Home Currency' amount. This is a non-editable text box that displays the currencies on the 'Exchange Table' being used to convert the 'Receipt Amount' to the 'Home Currency' amount. This is formatted as: "From [Receipt Currency] to [Home Currency]". This is only displayed and required when the Receipt's currency is not in the 'Home Currency'. This value is a looked up from the 'Exchange Table' and not stored in the database while the transaction is in a Status of "New". When the Status is changed to either "Approved" or "Ready to Post" the value is updated and written to the database. For posted transactions, this is the value that existed when the transaction posted. |
MC: Home Currency Amount | This field is used to convert the transaction total 'Receipt Amount' to the 'Home Currency' amount. This is a non-editable text box that displays the Receipt Amount converted to the Home Currency. This is only displayed and required when the Receipt's currency is not in the 'Home Currency'. This value is a looked up from the 'Exchange Table' and not stored in the database while the transaction is in a Status of "New". When the Status is changed to either "Approved" or "Ready to Post" the value is updated and written to the database. For posted transactions, this is the value that existed when the transaction posted. |