Application Guide for Oracle Self-Service E-Billing (Consumer Edition) > Payment Processing Use Cases >
Setting Up and Managing Recurring Payments
Users can use this use case to pay monthly charges automatically and set up an automatic recurring payment to a payee at regular intervals for a user-specified amount. The user can edit any recurring payment that is still active. The changes are applied to all future payments. The user can also decide whether to apply the changes to the next outgoing scheduled payment. The user can cancel a recurring payment, which stops any future automatic payments. If a recurring payment is canceled, the user has the option to cancel any payments that are already scheduled. The user can cancel the scheduled payment or only the future payments in the recurring payment definition. Table 19 lists and describes the functions.
Table 19. Setting Up and Managing Recurring Payments
|
|
Name |
Set Up and Manage Recurring Payments |
Feature Area |
Payment |
Description |
Lets a user set up and manage recurring payments against their associated billing accounts. |
Users |
Consumer user |
Trigger |
The user clicks the Payments tab and the Recurring Payment subtab. |
Configurations |
Scheduled Payment Sidebar has a display default of 10 most recent scheduled payments. This limit can be configurable. |
Standard Features |
- Multiple payment accounts
- Email notification of payment event
- Paging
- Sorting
|
Main Path for Setting Up and Managing Recurring Payments
The following paths describe how to set up and manage recurring payments. Viewing Recurring Payments
The user follows this main path to view recurring payments:
- The user chooses to view recurring payments.
Oracle Self-Service E-Billing displays the Recurring Payment page. The recurring payments previously created by the user are displayed with the following column headings:
- Billing Account Number
- Amount Type (Total amount due, Total amount within X threshold, Fixed amount)
- Pay Interval (A number of days before due date, a specific day of the month (values entered when the recurring payment was created).
- Effective Period (Until canceled, a specific number of payments, or until a date)
- The user can choose from the following options:
- Delete selected recurring payment (for one billing account at a time).
- Edit selected recurring payment (for one billing account at a time).
- Add recurring payment (continue with use case main path).
Adding a Recurring Payment
The user follows this main path to add a recurring payment:
- The user clicks Add Recurring Payment from the Recurring Payments page.
- The user clicks Billing Accounts.
The user selects multiple billing accounts to which a new recurring payment is applied.
- The user clicks Payment Account.
Field of payment accounts previously saved by the user (payment accounts created by other users are not displayed). The user has an option to create a new payment account.
- The user chooses a payment amount options:
- Total Amount Due (Default)
- Total Amount Within Threshold (The user enters threshold amount and receives a notification if amount due exceeds threshold)
- Fixed Amount (The user enters a fixed amount)
- Payment Date. The user selects an option and enters a value:
- The number of business days before due date (Default 2 days before due date)
- On a specific day of every month
- The user defines the effective duration of the recurring payment, defining a value for X where specified.
- Until Canceled (Default)
- For X payments
- Until date X (Text box and popup calendar)
- The user clicks Save.
The Recurring Payment Confirmation page appears.
- The user can modify the selected accounts.
- The user clicks Confirm to save the recurring payment
Oracle Self-Service E-Billing displays a confirmation message and adds the recurring payment to the list of scheduled recurring payments.
Alternate Paths for Setting Up and Managing Recurring Payments
Alternate paths can occur when setting up and managing recurring payments. Creating a New Payment Account
The following alternative path can occur when creating a new payment account: 1 Oracle Self-Service E-Billing takes user to Payment Accounts page and New Payment Account functionality. Both bank and credit card accounts are permitted for recurring payments.
- User enters a one-time payment for an account that already has a scheduled recurring payment.
- Oracle Self-Service E-Billing displays a notification that a recurring payment already exists for this account. Oracle Self-Service E-Billing notifies the user that if the payment is scheduled, then a double payment might occur.
- The user can click Confirm or Cancel.
Viewing and Editing Recurring Payments
An alternative path can occur when creating a new payment account. The alternative path is identical to the main path with the following exceptions:
- Recurring payments can only be edited one-at-a-time. Group editing of a recurring payment is not in scope.
- Information for the user prior to editing a recurring payment: After editing a recurring payment, any scheduled payment is canceled. A new payment is scheduled in its place based on the new recurring payment options.
- Editing recurring payments includes restrictions. The limitations are as follows:
- Payment Amount: A recurring payment cannot change from Total Amount to Fixed Amount (or vice-versa).
- Payment Date: A recurring payment cannot change from X Days Before Due Date to On the X Day of Every Month (or vice-versa).
- Present the user only with available edit options.
- A new recurring payment must be created if an edit option is desired but not available.
Canceling Recurring Payments
The user can cancel a recurring payment, which stops any future automatic payments. If a recurring payment is canceled, the user has the option to cancel any payments that are already scheduled. The user decides whether to cancel the scheduled payment or just the future payments in the recurring payment definition. Roles and Permissions - Viewing Payment Activity
Any user with permission to view payment activity must be able to view any payment made against any billing account to which the user has access. This includes check payments posted through the mail. Administrator Roles
The administrator user might experience performance delays when dealing with large numbers of accounts.
|