Payment Event - Main Information
The Main page contains core payment event information. Open this page using .
The Description of Page section below describes the fields on this page. Refer to How To for a description of how to perform common payment event maintenance functions.
Description of Page
Cash-only customers. When you attempt to add a new payment event, the system warns you if the account remitting the tender is a cash-only customer and the tender's tender type is not cash. An account is considered cash-only if their current cash-only points exceed the cash-only threshold maintained on the Installation record or account’s CIS Division. A customer's cash-only points are maintained on Account - Credit Rating.
Pay Event Info contains a concatenation of the payment date, amount, and the name of the main customer on the account that remits the tender. If multiple tenders exist, the customer's name is not displayed. If the payment event is associated with a single distribution detail, the rule name and the description of the rule value are displayed as well. If multiple distribution details exist, Multiple Distribution Details Exist is displayed instead. If document numbering has been enabled, the assigned document number will appear. If the payment was made in an alternate currency, the message Alternate Currency Used is displayed. Pay Event Info is only displayed after the payment event has been added to the database.
Refer to Alternate Currency Payments and Document Numbers for more information. Payment Event ID is the system-assigned unique identifier of the payment event.
The area under Pay Event Info provides warnings about the payment event. Possible warnings are Unfrozen Payments and The Payment Event is Unbalanced. A warning is also issued to the cashier to remind them to turn in funds - see Turn Ins.
If multiple distribution details are linked to the payment event, the distribution rule, value, and amount for each distribution detail displays.
Payment Date is the business date associated with the payment event.
If you change the payment date and this event's tender(s) are automatic payments, the extract date (i.e., the date the automatic payment is sent to the financial institution) will be changed to equal the payment date. Refer to Automatic Payments for more information.
Payment(s) contains the total number and value of payments linked to the event.
Tender(s) contains the total number and value of tenders linked to the event.
Amount Tendered contains the amount that was tendered by the customer.
The system displays a Cash Back Amount if the customer tenders more than they are paying (refer to Cash Back for details).
If the payment event becomes unbalanced , a Recalculate Cash Back button appears. If this button is clicked, the system creates, deletes or recalculates the cash back tender. Refer to Cash Back for details.
While most payment events contain a single payment, the system allows many payments to exist under a payment event (when the payment event's tender(s) are distributed amongst multiple accounts). If a payment event has a large number of payments, you can use the Account Filter to limit the payments that appear in the Payments grid. The following options are available:
- Account. Use this option if you only want to see the payment linked to an Account ID.
- All. Use this option to view all payments linked to the payment event.
- Person Name. Use this option to restrict payments linked to accounts whose main customer has a primary name that matches Person Name.
The Payments grid contains the payment(s) linked to the payment event. The following points describe the attributes in this scroll; refer to How To for instructions describing how to perform common maintenance activities.
- Account ID references the payment's account. The name of the account's main customer is displayed adjacent.
- Payment Amount is the amount of the account's debt relieved by the payment. The adjacent context menu allows you to drill down to the details of the payment (this is where you can see the payment's payment segments and where you can override the distribution of the payment).
- Payment Status is the payment's status. If the payment's status is Error, the error message is displayed adjacent. Refer to Payment Lifecycle for the potential values and how to handle a payment when it exists in a given state.
-
Match Type and Match Value should only be
used if either of the following conditions is true:
- This Account ID belongs to an open item customer class. In this situation, specify a Match Type to define how the payment should be matched to the customer's open-items and use Match Value to define the open-items covered by the payment. For example, if this payment is in respect of a bill, specify a match type of "bill id" and a match value of the bill id being paid.
- The customer wants to restrict the distribution of the payment to a specific service agreement. In this situation, specify a Match Type of "service agreement ID" and a Match Value of the respective service agreement ID.
- The remaining columns are only used if the payment is linked to
an Account ID that belongs to a customer class that is used
for non-CIS payments. Refer to Setting Up Customer Classes for more information. If such
an account exists, the following fields must be defined.
- Non CIS Name is the name of the person remitting the payment.
- Reference Number is the reference number of the item being paid (e.g., the property tax reference number).
- Non CIS Comments are used to describe anything unusual about the non-CIS payment.
- Note, you can also define a comment for a non-CIS payment. To define a comment, use the context menu adjacent to Payment Amount to drill to Payment - Main.
- Payment ID is the unique, system-assigned identifier of the payment. This value only appears after the payment has been added to the database.
Refer to Payment Actions and Payment Event Actions for information about the action buttons on this page. Refer to How To for a description of typical business processes that use these buttons.