A text box to enter the amount of the payment received. This defaults to 0.00, is required and must be >= 0.00 to Approve and/or Post. This field is only editable after a 'Customer' has been selected and while the transaction Status is "New". Editing this value and saving the transaction will re-calculate the 'Applied Amt.' and 'Unapplied Amt.' fields.

Database Field: ERPx_ARTransactionHeader.ExtendedAmount

A single-select lookup to identify which checkbook the receipt will be deposited into. The value defaults as follows:

1. If the Checkbook that is assigned to the Customer is in either the Customer Currency or the Home Currency then default to the Customer Checkbook, else
2. If the Checkbook that is assigned to the "Default Payment Receipt Checkbook" Sales Preference is in either the Customer Currency or the Home Currency then default from the Preference, else
3. Set to blank and require a value before enabling the rest of the data fields

This field is enabled after a 'Customer' has been selected and while the transaction Status is "New". The lookup contains the list of all the 'Active' checkbooks assigned to the Customer or the Home Currency. 

Database Field: ERPx_ARTransactionHeader.CheckbookSK

A text box to enter a comment. This defaults to blank and is not required. This field is always editable even after the transaction is posted. This must be <= 60 characters.

Database Field: ERPx_ARTransactionHeader.Description

A single-select lookup to select the Customer you received the payment from. This defaults to blank but is required before anything other than the 'Receipt Date' can be edited. If not assigned, the message "Customer is required." will be displayed. Because this value determines the initial value assigned for the 'Checkbook'. if it is changed after it has been assigned, a message will appear as: "Changing the Customer will reset the Checkbook and/or Receipt Currency." This field is editable while the transaction Status is "New".

The lookup contains the list of all 'Active' customers, including the customer accounts that are on hold, displayed as Customer Name (Customer ID). 

Database Field: ERPx_ARTransactionHeader.CustomerSK

 A calculated field to display the total unapplied credit balance for the Customer. This is calculated by summarizing the unapplied amounts from all negative Quick Sales (including settled Accounts Receivable sales programs), negative Sales Orders, Returns and negative Price Adjustments that belong to the current customer. This shows as blank if the customer does not have any unapplied credit balance transactions. This field is only visible for unposted Payment Receipts, it is not visible after the Payment Receipt is posted. This is a calculated field that is not stored in the database.

A calculated field to display the current accrued Rebate balance for the customer. This amount is calculated as the sum of the 'Program Balance' (as seen on the 'Program Balances' page) for all Rebate Programs where the Program's Payee is the current customer. This shows as blank if the customer does not have any open rebates. This field is only visible for unposted Payment Receipts, it is not visible after the Payment Receipt is posted. This is a calculated field that is not stored in the database.

A calculated field to display the total of the open Rebates and Credits for the customer. It is calculated as ([Open Credit Amt.] + [Open Rebate Amt.]). This defaults to blank if no unapplied credit balances and no unsettled Rebates exist for the corresponding Customer. This field is only visible for unposted Payment Receipts, it is not visible after the Payment Receipt is posted. This is a calculated field that is not stored in the database.

A text box to enter the number of the payment you received, most often associated with the Check #. This field defaults to blank and is not required. This field is always editable, even after the transaction is posted. This must be <= 50 characters.

 If the same combination of Customer, Receipt Type and Payment # exist on an open or Posted Payment Receipt, the message "Duplicate Payment Receipts are not allowed. Payment # [Payment#] on [TransNumber] was keyed on [ReceiptDate] for this customer." will be displayed on Save. 

 If the same combination of Customer and Payment # exist on an open or Posted Payment Receipt but with a different Receipt Type, the message "Potential Duplicate Transaction. [ReceiptType] Receipt with Payment # [Payment#] on [TransNumber] was keyed on [ReceiptDate] for this customer." will be displayed on Save as a warning that it might be a duplicate but this will not prevent the data from saving. 

Database Field: ERPx_ARTransactionHeader.DocNumber

A date field to enter the date the Receipt was actually received. This defaults to the current date and is required to Approve and/or Post. If not, the message "Receipt Date is required." will be displayed. This field is only editable while the transaction Status is "New".

Database Field: ERPx_ARTransactionHeader.TransactionDate

A single-select lookup to identify the type of the Receipt. This defaults to "Check" but can be changed. This is required to Approve and/or Post. This field is only editable while the transaction Status is "New". 

The lookup contains all the values in the MFCashReceiptType Enumeration Class which includes Card, Cash, Check, Electronic, and Other.

 If the same combination of Customer, Receipt Type and Payment # exist on an open or Posted Payment Receipt, the message "Duplicate Payment Receipts are not allowed. Payment # [Payment#] on [TransNumber] was keyed on [ReceiptDate] for this customer." will be displayed on Save. 

 If the same combination of Customer and Payment # exist on an open or Posted Payment Receipt but with a different Receipt Type, the message "Potential Duplicate Transaction. [ReceiptType] Receipt with Payment # [Payment#] on [TransNumber] was keyed on [ReceiptDate] for this customer." will be displayed on Save as a warning that it might be a duplicate but this will not prevent the data from saving. 

Database Field: ERPx_ARTransactionHeader.CashReceiptTypeEN

A single-select lookup to set the Status of the Receipt. This defaults to New but can be changed to Approved or Ready to Post. Setting this to Approved, and saving, runs all the posting validations and disables all the fields except the Comment, Payment #, and Status. Setting this to Ready to Post, and saving, posts the transaction, disables all the fields except the Comment and Payment #, and posts the journal entry.

The lookup contains the list of New, Approved, and Ready to Post.

Database Field: ERPx_ARTransactionHeader.TransactionStatusSK

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.

Database Field: ERPx_MFCheckbook.CurrencySK

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.

Database Field: ERPx_ARTransactionHeader.CheckbookSK

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. 

Database Field: ERPx_ARTransactionHeader.CreatedDate

A non-editable text box to identify the currency of the receipt. Receipts may not always be in the same currency as the Checkbook. 

Database Field: ERPx_ARTransactionHeader.CurrencySK

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.

Database Field: ERPx_ARTransactionHeader.CustomerSK

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. 

Database Field: ERPx_ARTransactionHeader.LastUpdated

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. 

Database Field: ERPx_ARTransactionHeader.LastUser

A non-editable text box to identify the Transaction #. This is a system assigned value that is not editable by a user.

Database Field: ERPx_ARTransactionHeader.TransactionID

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.

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:

• If the 'From Currency' on the Exchange Table matches the Receipt currency, then the 'Calculation Method' will default from the 'Calculation Method' on the Exchange Table.
• If the 'From Currency' on the Exchange Table matches the 'Home Currency', the 'Calculation Method' will be the opposite as it is on the Exchange Table.

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.

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.

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.

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.

A text box to enter/override the amount that you want applied to an invoice. This defaults to 0.00 and will auto-fill if the 'Apply' button is checked. This is not required but if entered it must be <= to the Transaction's 'Unapplied Amount'. If not, the message "You cannot over apply a transaction. Applied Amount has been set to 0." each time you tab out of the field or when the Save icon is clicked. This field is editable until Approved/Posted. If the invoice you are applying to is on a separate unposted receipt, the message "Transaction [Sale TransactionID] is on an open Payment Receipt: [Receipt TransactionID] and cannot be applied until that Receipt is Posted." will be displayed on Save.

Database Field: ERPx_ARSettlementApplication.AppliedAmount

A date field to enter the date the sales transaction is applied to the Payment Receipt transaction. This defaults as follows:

• If the Receipts 'Receipt Date' <= the current date (e.g., applying a Receipt that was posted last week), then default to the current date for all sales transactions with a 'Receipt Date' <= the current date ELSE
• If the Receipts 'Trans. Date' > the current date (e.g., entering a Receipt with a future date), then default to the Receipt Date for all transactions with a 'Trans. Date' <= the Receipt date

This is required for any record with a positive amount in either the 'Applied Amount', 'Discount Amount', or 'Write Off Amount' fields.

On Save, the 'Apply Date' is validated to ensure:

• It's in a Fiscal Period that is open for Sales. If not, the message "The Fiscal Period is not open for Sales." will be displayed.  This only applies if there is an application journal entry created (Discount, Write-Off or Currency Gain/Loss)
• It precedes the transactions 'Trans. Date'. If so, the message "The Apply Date must be >= the transactions 'Trans. Date'." will be displayed.
• It precedes the Receipt Date. If so, the message "The Apply Date must be >= the Receipt' 'Trans. Date'." will be displayed.

This field is always editable.

Database Field: ERPx_ARSettlementApplication.ApplicationDate

A non-editable text box to display the calculated discount amount that the sales invoice is still eligible for. This is calculated for all sales invoices that were posted with a Payment Term that contained a discount (e.g., 2%10 Net 30). If the 'Trans. Date' of the document being applied falls within the discount days of the sales invoice date then an amount will be shown, otherwise it will be 0.00. This value in this field is informational only, a user is still able to override the actual 'Discount Amount'.  This is a calculated field that is not stored in the database.

A non-editable text box to display the 'Description' that was entered on the header of a Quick Sale transaction, this is blank for sales invoices and price adjustments. This field is not editable from here but can be edited on the source transaction even after it was posted.

Database Field: ERPx_ARTransactionHeader.Description

A text box to enter a discount for a specific sales invoice. This defaults to 0.00. This is not required and can be any value >= 0.00 and <= the 'Unapplied Amount' for the corresponding line item. If a value is entered that exceeds the 'Unapplied Amount', the message "You cannot over apply a transaction. Discount Amount has been set to 0." each time you tab out of the field or when the Save icon is clicked. This field is always editable. If the invoice you are applying to is on a separate unposted receipt, the message "Transaction [Sale TransactionID] is on an open Payment Receipt: [Receipt TransactionID] and cannot be applied until that Receipt is Posted." will be displayed on Save.

If the 'Discount Amount' is changed, then on Save, a journal entry will be created that Debits the "Terms Discounts Taken" and Credits the "Accounts Receivable" GL Accounts assigned to the Customer, in the amount of the difference between the previous amount and the new amount of the Discount Taken.

Database Field: ERPx_ARSettlementApplication.TakenDiscountAmount

A date field to display the last day the Payment Terms discount is applicable. This is displayed for all Sales transactions that were posted with a Payment Term that contains a discount (e.g., 2%10 Net 30) and is calculated by adding the number of discount days to the invoice date for sales Invoices and to the Doc Date for Quick Sales. This field will be blank for all Sales Invoices, Price Adjustments, and Quick Sales that were posted with a Payment Terms that did not include a discount. This field is not editable from here but can be edited on the source transaction for Quick Sales even after they were posted, but not for Sales Invoices or Price Adjustments. This is a calculated field based on the payment terms assigned to the order that is not stored in the database.

A non-editable text box to display the 'Doc No' of a Quick Sale transaction. This only applies to Quick Sales so it will always be blank for Sales Invoices and Price Adjustment transactions. This field is not editable from here but can be edited on the source transaction, even after it is posted. 

Database Field: ERPx_ARTransactionHeader.DocNumber

A date field to display the date the payment is due. This is displayed for all transactions in the grid and is calculated by adding the number of due days to the invoice date for sales Invoices and to the Doc Date for Quick Sales. This field is not editable from here but can be edited on the source transaction for Quick Sales even after they were posted, but not for Sales Invoices or Price Adjustments. This is a calculated field based on the payment terms assigned to the order that is not stored in the database.

Open Amount

A non-editable text box to display the open amount of the transaction. This is calculated by subtracting all previous Applied Amounts (from payments and Rebates), Discount Amounts, and Write Off Amounts from the transactions 'Orig. Amount'. Only transactions with an 'Open Amount' > 0.00 will be shown in this grid.  This is a calculated field that is not stored in the database.

A non-editable text box to display the open unsettled rebate amount for the corresponding transaction.  This value will update if a settlement for the associated transaction is posted.  This is a calculated field that is not stored in the database.

A non-editable text box to display the sales transaction amount. This is looked up from the transaction and will always be > 0.00 as zero-dollar transactions do not show in this grid. 

Database Field for SO Transactions: ERPx_SOOrderHeader.ExtendedAmount

Database Field for AR Transactions: ERPx_ARTransactionHeader.ExtendedAmount

A non-editable text box to display the discount amount the transaction was eligible for when it was posted. This is calculated for all Sales transactions posted with a Payment Term that contained a discount (e.g., 2%10 Net 30). If the transaction contained a Payment Term with a discount, an amount will be shown, otherwise it will be 0.00. This is calculated by multiplying the Payment Terms Discount Amount by the Invoice Amount. This is informational only; a user is still able to override the actual 'Discount Taken' amount even if the transaction did not have an original discount.  This is a calculated field that is not stored in the database.

A non-editable text box to display the Payment Term ID of the Payment Term the transaction was posted with. This defaults from the Customer but can be changed on the transaction prior to posting.

Database Field for SO Transactions: ERPx_SOOrderHeader.PaymentTermSK

Database Field for AR Transactions: ERPx_ARTransactionHeader.PaymentTermSK

A non-editable text box to display the Purchase Order number of the transactions. This field will be blank for all Sales Invoices, Price Adjustments, and Quick Sales that were posted without a PO. This field is not editable from here but can be edited on the source transaction for Quick Sales even after they were posted, but not for Sales Invoices or Price Adjustments. 

Database Field for SO Transactions: ERPx_SOOrderHeader.PurchaseOrder

Database Field for AR Transactions: ERPx_ARTransactionHeader.PurchaseOrderID

A text box to enter/override the Rebate amount that you want applied to an invoice. This defaults to 0.00 and is not required but if entered it must be <= to the Transaction's 'Unapplied Amount' for the corresponding line item. If not, the message "You cannot over apply a transaction. Rebate Amount has been set to 0." each time you tab out of the field or when the Save icon is clicked. Additionally, the Rebate Amount must be <= the Open Rebate Amt. if not the message "The Rebate Amount entered exceeds the Open Rebate Amt." will be displayed when the record is saved as Ready to Post/Posted. This field is editable while in 'New' Status. If the invoice you are applying to is on a separate unposted receipt, the message "Transaction [Sale TransactionID] is on an open Payment Receipt: [Receipt TransactionID] and cannot be applied until that Receipt is Posted." will be displayed on Save.

Database Field: ERPx_ARSettlementApplication.RebateAmount

A non-editable text box to display the balance remaining after entry of any 'Applied Amount', 'Rebate Amount' and 'Discount Amount'. This is calculated as ([Original Amount] - [sum of all applied amounts including the current applied amount] - [Discount Amt.] - [Rebate Amt.]). This field is not directly editable but changes as the 'Applied Amount', 'Rebate Amount' and 'Discount Amount' values are edited. This is a calculated field that is not stored in the database.

A date field to show the date of the transaction. For Sales Invoice and Price Adjustments this will be the Invoice Date and for Quick Sales this is the Doc Date. This field is not editable.

Database Field for SO Transactions: ERPx_SOOrderHeader.OrderDate

Database Field for AR Transactions: ERPx_ARTransactionHeader.TransactionDate

A hyperlink to show the Transaction ID for each transaction. Clicking on the hyperlink opens the transaction record view.

Database Field for SO Transactions: ERPx_SOOrderHeader.OrderID

Database Field for AR Transactions: ERPx_ARTransactionHeader.TransactionID

A non-editable text box to display how much is still open for each transaction. This is calculated as ([Remaining Amount] - [Write Off Amount]). This field is not directly editable but changes as the values in 'Applied Amount', 'Rebate Amount', Discount Amount', or 'Write Off Amount' change. This is a calculated field that is not stored in the database.

A text box to enter a write off for a specific transaction. This defaults to 0.00. This is not required and can be any value >= 0.00 and <= the 'Unapplied Amount' for the corresponding line item. If not, the message "You cannot over apply a transaction. Write Off Amount has been set to 0." each time you tab out of the field or when the Save icon is clicked. This field is always editable. If the invoice you are applying to is on a separate unposted receipt, the message "Transaction [Sale TransactionID] is on an open Payment Receipt: [Receipt TransactionID] and cannot be applied until that Receipt is Posted." will be displayed on Save.   

If the 'Write Off Amount.' value is changed, then on Save, a journal entry will be created that Debits the "Write Off GL Account" and Credits the "Accounts Receivable" GL Accounts assigned to the Customer, in the amount of the difference between the previous amount and the new amount of the Write Off Amount. 

Database Field: ERPx_ARSettlementApplication.WriteoffAmount

A single-select lookup to select the GL Account used for the Write Off. This defaults from the "Writeoffs" GL Account assigned to the Customer but is only required for records that have an amount in the 'Write Off Amt.' field. If missing, and a write off amount has been entered on save, the message "Write Off GL Account cannot be blank when a Write Off Amount is provided." will be displayed.    

The lookup contains the list of all 'Active' GL Accounts where "Use in SO" = Yes.

Database Field: ERPx_ARSettlementApplication.WriteoffAccountSK

A non-editable text box to show the ID of the 'Exchange Table' that was assigned to the sale transaction when it posted. This field will be blank for sales transactions that were posted in the Home Currency. 

A non-editable text box that displays the Currency ID from the Sales transaction.

A non-editable text box that displays the 'Rate' (exchange rate) that applies to the 'Receipt Date' from the header source transaction being applied (most often a Payment Receipt but could also be a return, negative price adjustment, negative sales invoice, or negative quick sale transactions) on the 'Exchange Table' assigned to the record. This is set to 1.00 for all 'Payment Receipts' where the 'Receipt Currency' matches the 'Home Currency'. This is a looked-up value that is not editable from here. 

A non-editable text box to show the 'Calculation Method' being used to convert each application's currency (the 'From Currency') to the Home Currency (the 'To Currency'). This will either be "Multiply" or "Divide" and is set as follows:

• If the Receipt Currency is in the Home Currency, then this will be set to "Multiply"
• If the 'From Currency' on the Exchange Table matches the 'Receipt' Currency and the 'To Currency' on the Exchange Table matches the Home Currency, then the 'Calculation Method' on the transaction will match the 'Calculation Method' from the Exchange Table.
• If the 'From Currency' on the Exchange Table matches the 'Home Currency' and the 'To Currency' on the Exchange Table matches the Receipt Currency, then the Inverse Exchange method will be used and the 'Calculation Method' on the transaction will be the opposite as it is on the Exchange Table.

A non-editable text box to identify if the application results in a currency gain or loss. This value is always in the Home Currency and is calculated by:

(([Applied Amount] + [Discount Amount] + [Write Off Amount]) * [Receipt Exchange Rate]) - 

(([Applied Amount] + [Discount Amount] + [Write Off Amount]) * [Sale Exchange Rate]).

If the result is positive then we have a currency gain, if it is negative, we have a currency loss, and if it is 0.00 then this line is not part of the gain/loss journal entry. 

If any of the line items have a non-zero value in this field, then a currency gain/loss journal entry will be made on save. This will always be a separate Journal Entry because it must be made in the Home Currency. The journal entry is created, using the Apply Date of each transaction that had a non-zero value as follows:

If the transaction results in a currency gain:

• Debit the Accounts Receivable GL Account that was assigned to the transaction
• Credit the Company Currency's 'Realized Gain' GL Account.

If the transaction results in a currency loss:

• Debit the Company Currency's 'Realized Loss' GL Account.
• Credit the Accounts Receivable GL Account that was assigned to the transaction.

A non-editable text box that displays the 'Rate' (exchange rate from the currency exchange table) that applied to the sale transaction when it posted. This is set to 1.00 for all Sale transactions that were posted in the 'Home Currency'. This is a looked-up value that is not editable from here. 

A non-editable text box to show the 'Calculation Method' being used to convert each sale transaction's currency (the 'From Currency') to the Home Currency (the 'To Currency'). This will either be "Multiply" or "Divide" and is set as follows:

• If the Sale transaction was in the Home Currency, then this will be set to "Multiply"
• If the 'From Currency' on the Exchange Table matches the 'Sales' Currency and the 'To Currency' on the Exchange Table matches the Home Currency, then the 'Calculation Method' on the transaction will match the 'Calculation Method' from the Exchange Table.
• If the 'From Currency' on the Exchange Table matches the 'Home Currency' and the 'To Currency' on the Exchange Table matches the Sale Currency, then the Inverse Exchange method will be used and the 'Calculation Method' on the transaction will be the opposite as it is on the Exchange Table.

A non-editable text box that displays the Home Currency ID.