Add One-Time Payment

In addition, the Add One-Time Payment script can also be called from other places (zones, maps, etc) in the system where your implementation allows the capture of a one-time payment.

The Payment Date defaults to the current date.

The Payment Amount is the amount of the customer's debt to be relieved by the payment. Note, this amount is defaulted using an algorithm plugged in on the Installation Record. Please refer to the Automatic Payment Amount Calculation algorithm, (C1-APAM-DFLT) for more information on the calculation.

The Tenders - Existing Payment Options grid is shown if the Payor Account has existing self-service payment methods and/or a currently effective recurring bill auto pay enrollment. Select a Payment Option and specify the Tender Amount.

The Tenders - New Auto Pay Options and Other Tender Types grid is used for new automatic payment methods, cash tender type(s) and other non-cash/non-auto pay tender types (e.g. check). Select a Tender Type and specify the applicable information. A new checking/savings payment method can be saved, to make it available for future one-time payments, including self-service payments. Specify the Tender Amount.

Match Type and Match Value are shown used if either of the following conditions is true:

• The Payor Account 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.

If the Payor Account ID's customer class is designated as non-CIS (i.e., the person making the payment isn't a customer), the following information appears in the above window:

• 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.

Use Distribute Action to describe what you'd like to have happen when you click the OK button:

• Choose Distribute and Freeze if OK if this is a simple payment that should require no manual intervention. "Simple payment" means:
  • The account is both the tendering account and the account whose debt is being relieved by the payment
  • The payment date is the current date
  • The payment should be distributed amongst the account's service agreements using standard distribution logic

  If this option is selected, the system distributes the Payment Amount amongst the account's service agreements. If the distribution is successful, the system automatically freezes the payment. If the distribution is not successful or is on hold due to web debit account validation, the payment will be in the Error or Incomplete state, respectively. When the Payment Event page appears, you can view the error and then correct it. After the cause of the error is corrected, you must distribute and freeze the payment manually (this can be done on several pages including Payment Event - Main and Payment - Main). If any new auto pay methods are checking/savings bank accounts that have never been used on prior recurring auto pays and/or prior self-service one-time payments, the bank accounts will be subject to web debit account validation if the system is configured to do so. The One-Time Payment service task is created to manage bank account validation. The service task is linked to the payment event, which remains in Incomplete status until the validation is complete. The service task will either complete or delete the payment event, depending on the validation results. Refer to Web Debit Account Validation for more details.

• Choose Manual Distribution if you need to manually distribute the payment amongst the account's service agreements or if you want to process the payment event manually (e.g. if you need to define multiple payee accounts). If this option is selected, the system creates a payment event, a tender and a payment and then transfers you to the Payment - Manual Distribution page where you can define the amount to be allocated to each of the account's service agreements. After you've distributed the payment, don't forget to freeze it. If allocating the payment to multiple payee accounts, navigate to the Payment Event - Main page and make any changes before distributing and freezing the payment.