Cash Receipt Header

The following fields are conditionally required based on site specific setup on the System Options table:

• Deposit Ticket - required if the Use Deposit Reconciliation flag on the System Options table is selected and the Print Deposit Ticket flag on System Options is not selected or if the Print Deposit Ticket flag is selected and the Suppress Pend Print field is selected on the CR Vendor Line. If the Use Deposit Reconciliation flag is selected and the Print Deposit Ticket flag is not selected on the System Options table for the current Fiscal Year, or if the Suppress Pend Print flag is selected on the Vendor Line(s) of the Cash Receipt, and the Infer Deposit Ticket Number flag on Transaction Control is selected for the selected Transaction Code, then the value in the Deposit Ticket field is inferred from the Next Available Deposit Ticket Number field on the Bank table if blank on Validate/Submit.

• Deposit Date - required if the Use Deposit Reconciliation flag on the System Options table is selected and the Print Deposit Ticket flag on System Options table is not selected. This field is also required if the Require Deposit Date Only flag on System Options is selected. If the Use Deposit Reconciliation flag is selected and the Print Deposit Ticket flag is not selected, or if the Require Deposit Date Only flag is selected on the System Options table for the current Fiscal Year, or if the Suppress Pend Print flag is selected on the Vendor Line(s) of the Cash Receipt, and the Infer Deposit Date flag on Transaction Control is selected for the selected Transaction Code, then the value in the Deposit Date field is inferred from the Application System Date parameter on the Application Parameters table if blank on Validate/Submit.

If the Transaction Total Required field on the Transaction Control table is selected, the Transaction Total field on the Header of the CR transaction is required and must equal the system calculated Actual Amount field on the transaction. If the Transaction Total Required field is not selected, the Transaction Total field on the CR is optional, but if populated, will still be verified against the Transaction Actual Amount.

The Transaction Total field along with the Central Statement Customer and Central Statement Billing Profile fields are used when recording a payment against a central statement using the Auto Apply action.

The Payment Type field is defaulted from System Option. If this field is populated and the Payment Type field on the Vendor Line is blank, the value is inferred to the Vendor Line upon the validation / submission of the CR transaction.

The Alternate Bank Account field on the header of the CR transaction type allows the user to select a bank without viewing the sensitive banking information. This picklist is populated using the Valid Transaction Code Department Bank Combination (VHDRBNK) page, limiting to only allowed banks and not every bank, as with the standard Bank Account field. When a value is entered or selected for this field, the value is pushed to the standard Bank Account field. As the Valid Transaction Code Department Bank Combination page is being used, a user may not even have to choose a bank as the Deposit Default setting can provide a default to the standard Bank Account field. When using the alternate field, it is wise to protect the standard bank field to remove the pick that shows sensitive information. Leaving it visible will allow users to see a default or see a value uploaded or interfaced.

The following action exists on the Header of the CR:

Auto Apply -  This action exists on the Header tab of all Cash Receipt transactions, except the Cash Receipt Advance (CRA). If you want to apply a payment against a receivable or collection transaction or line, or a customer account, you need to specify it along with the amount to apply in the vendor tab and select the Auto Apply check box. You can optionally prioritize the payment order. If you want to apply a payment against a central statement that may cover one or more customer accounts, you need to specify the Transaction Total, Central Statement Customer, and Central Statement Billing Profile in the Header tab. In this case, the payment order is determined by the applicable posting order defined in the System Options table. After specifying the information, click the Auto Apply button for the system to automatically populate the accounting line(s) as follows:

• On a new CR transaction:

• An edit will prevent the Auto Apply action if you try to apply a payment against a central statement specified on the header and a reference transaction or line, or a customer account on the vendor line simultaneously. You can specify Auto Apply information at the header level or the vendor line level, but not both.

• A receivable or collection transaction or line, or a customer account must be specified along with the amount to apply. Users can optionally prioritize the payment order.

• The system searches for open non-memo collection lines or open receivable lines matching the specified criteria. Disputed – No Auto Cash Application lines are not eligible and are not applied. Negative lines are applied first, and the system uses the vendor line amount plus the total of applied negative line amounts to liquidate positive lines. The positive lines are applied based on the payment order; within the same payment order lines with the oldest due date are applied first.

• If a Receivable (RE) or Collection (CL) line is referenced on the vendor/customer line, one accounting line is generated referencing that line. Overpayment is not allowed.

• If a Receivable or Collection transaction only (with no line number) is referenced on the vendor/customer line, accounting lines are populated based on the order discussed above. If there is an overpayment within tolerance, the overpayment will be included in the last applied line. If there is an overpayment outside of tolerance, a separate line will record the overpayment against the customer account.

• If a customer account is referenced on the vendor/customer line, accounting lines are populated based on the order discussed above. Any overpayment will be recorded on a separate line against the customer account.

• If a central statement is referenced on the header, vendor lines are created along with accounting lines based on the order discussed above. Any overpayment will be recorded on a separate line under the last vendor line.

·        On a modification CR transaction:

·      Revert the accounting lines to the final version. If the vendor line amount has decreased, the decrease is deducted from any unreserved credit balance lines, followed by the accounting lines starting with the last accounting line until the entire deduction has been taken. If the vendor line amount has increased, the system will look for lines to apply payments to as in the new transaction case. Note that Auto Apply cannot be used against a central statement on a modification CR transaction.

These automatically generate accounting lines on the Cash Receipt transaction determine how the payment received is applied. For more information about payment application or tolerance in Advantage Financial, see Applying Payments.

There is a hidden Contact Information section on the header, that when made visible, allows the tracking of a person that is not the Created By or Last Modified By users, should there be questions about the content later. Unlike other similar contact fields found on transactions, this is not from the Contact (CNTAC) page but from the User Information (SCUSER) page. This information is also not controlled by the Transaction Control option – Transaction Header Contact Required. If required, a Configurable Validation (BORULE) is necessary.