You must define a variety of business rules for every division in which an account type has taxpayers. Open
tab to maintain this information.Description of Page
The Account Type Controls scroll contains business rules governing accounts that belong to a Division and Account Type. The following fields should be defined for each Division:
Use Min Compliance Review Freq (Days) to define the maximum number of days that can elapse between the reviews of an account's debt by the overdue monitor. Note, a value of zero (0) means that accounts in this account type will be reviewed every day.
Use Compliance Review Grace Days to define the number of days that algorithms may add to a given due date when requesting that an account should be reviewed by the overdue monitor. For example, when completing a bill, an algorithm inserts a record into the account review dates collection setting the review date to the bill due date plus the number entered here.
The grid that follows contains Algorithms that control important functions in the system. You must define the following for each algorithm:
Specify the System Event with which the algorithm is associated (see the table that follows for a description of all possible events).
Specify the Sequence and Algorithm for each system event. You can set the Sequence to 10 unless you have a System Event that has multiple Algorithms. In this case, you need to tell the system the Sequence in which they should execute.
These algorithms are typically significant system processes. The absence of an algorithm may prevent the system from operating correctly.
You can define algorithms for the following System Events:
System Event |
Optional / Required |
Description |
Autopay Amount Over Limit |
Optional |
This algorithm is called to handle the situation when a system-initiated automatic payment is created that exceeds the taxpayer's maximum withdrawal limit. Specifically, this algorithm is called when: - The account has a maximum withdrawal limit on their automatic payment options - The system attempts to create an automatic payment that exceeds this amount - The automatic payment algorithm that's plugged into the installation record has logic that invokes this algorithm when the above conditions are true. For more information refer to system event Automatic Payment Creation in Installation Options — Algorithms. If you do not plug-in this type of algorithm and the above situation is detected, the automatic payment will be created and no error will be issued. Refer to How To Implement Maximum Withdrawal Limits for more information. Click here to see the algorithm types available for this system event. |
FT Freeze |
Optional |
When an FT is frozen, this algorithm is called to do additional work. For example, if you wish to schedule compliance review when an account’s balance changes, you may need such an algorithm to handle creating an account review trigger depending on the financial transaction type. Click here to see the algorithm types available for this system event. |
Levy an NSF Charge |
Optional |
This algorithm is called when a payment is canceled with a cancellation reason that indicates an NSF. Refer to NSF Cancellations for more information about what happens when a payment is canceled due to non-sufficient funds. Only One Algorithm. Only one algorithm to levy an NSF charge may be defined for an account type / division combination. Click here to see the algorithm types available for this system event. |
Overpayment Distribution |
Required |
When a taxpayer pays more than they owe, this algorithm is called to determine what to do with the excess funds. Refer to Overpayment Obligations for a description on how to configure the system to handle your overpayment requirements. Only One Algorithm. Only one overpayment distribution algorithm may be defined for an account type / division combination. Click here to see the algorithm types available for this system event. |
Payment Cancellation |
Optional |
Algorithms of this type are called when a payment is canceled. Click here to see the algorithm types available for this system event. |
Payment Distribution |
Required |
This algorithm is called to distribute a payment amongst an account's obligations. Refer to Payment Distribution for more information about how payment distribution works. Only One Algorithm. Only one payment distribution algorithm may be defined for an account type / division combination. Click here to see the algorithm types available for this system event. |
Payment Freeze |
Optional |
When a payment is frozen, this algorithm is called to do additional work. For example, you may need such an algorithm to recalculate penalty and interest charges on receipt of a payment Click here to see the algorithm types available for this system event. |
Additional Details
The following controls are only applicable if your implementation uses Classic Billing functionality.
Use Days Till Bill Due to define the number of days after the bill freeze date that the taxpayer's bill is due. If the due date is a weekend or company holiday, the system will move the due date forward to the next workday (using the workday calendar defined on the account's division).
You can define algorithms for the following billing related System Events :
System Event |
Optional / Required |
Description |
Bill Cancel |
Optional |
This algorithm provides the ability to include additional cancel logic when canceling online. Algorithms of this type can be called in two modes: D (Determine Bill Page Buttons) and X (Cancel Bill). Mode 'D' governs whether an action button to cancel the bill will appear on the Bill page and mode 'X' performs the actual cancellation logic. Click here to see the algorithm types available for this system event. |
Bill Completion |
Optional |
When a bill for an account is completed, bill completion algorithms are called to do additional work. Refer to the description of the Complete button under Bill Lifecycle for a description of when this algorithm is called during the completion process. Click here to see the algorithm types available for this system event. |
Bill Eligibility |
Optional |
Algorithms for this plug-in spot are called when generating a bill in batch billing. It provides the ability to determine if an account is ineligible for billing and should therefore be skipped from further processing. If an eligibility algorithm is not used, a bill is created for any account in the open bill cycle and is later deleted by the billing process if it detects that there in no information linked to the bill. Click here to see the algorithm types available for this system event. |
Bill Segment Freeze / Cancel |
Optional |
When a bill segment for an account in this account type / division is frozen or canceled, an algorithm of this type may be called to do additional work. Refer to Bill Segment Lifecycle for more information about freezing and canceling bill segments. Click here to see the algorithm types available for this system event. |
FT Freeze |
Optional |
If you practice Open Item Accounting, you will need an FT Freeze algorithm to handle the cancellation of match events when a financial transaction is canceled that appears on a match event. Refer to How Are Match Events Cancelled? for more information about cancellation. Note: Open Item Accounting is only applicable
to Classic Billing functionality.
Click here to see the algorithm types available for this system event. |
Override Due Date |
Optional |
An account's bill due date will be equal to the bill date plus its account type's Days Till Due. If you need to override this method for accounts in a specific account type, specify the appropriate algorithm here. Only One Algorithm. Only one due date override algorithm may be defined for an account type / division combination. Click here to see the algorithm types available for this system event. |
Post Bill Completion |
Optional |
When an account type has algorithms of this type, they are called after the completion of a bill for an account linked to this account type. Refer to the description of the Complete button under Bill Lifecycle for a description of when this algorithm is called during the completion process. Click here to see the algorithm types available for this system event. |
Pre Bill Completion |
Optional |
When an account type has algorithms of this type, they are called immediately before completion starts for an account linked to this account type. These algorithms have the potential of:
Refer to the description of the Complete button under Bill Lifecycle for a description of when this algorithm is called during the completion process. Click here to see the algorithm types available for this system event. |
Payment Freeze |
Optional |
If you practice Open Item Accounting, you will need a Payment Freeze algorithm to link the payment's financial transactions to the match event that was originally created when the payment was distributed. Refer to Payments and Match Events for more information. Note: Open
Item Accounting is only applicable to Classic Billing functionality.
Click here to see the algorithm types available for this system event. |
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]