Defining Overdue Processing Options
The system periodically monitors how much your customers owe to ensure they haven't violated your collection rules. When a violation is detected, the system initiates the appropriate activities (e.g., letters, disconnect notices, collection agency referrals, and eventually write off). The topics in this section describe how to configure the system to manage your overdue processing requirements.
Note: Collecting on unpaid bills. The overdue processing module has
been designed to collect on virtually anything from an unpaid bill
to an unmatched financial transaction. You tell the system what you
collect on by configuring the various overdue processing control tables.
In this release, the base-package is delivered with algorithms that
support collecting on overdue bills. If your organization practices
balance-forward accounting (i.e., collection is based on overdue contract
balances), you will not use this functionality. Rather, you will use
the functionality described under Defining Credit and Collections Options.
CAUTION: Straightforward rules = straightforward set up.
Setting up this module is as challenging as your organization's collection
rules. If you have simple rules, the set up process will be straightforward.
If your rules are complicated (e.g., they differ based on the type
of customer, the age of debt, the type of service, etc.), your setup
process will be more challenging.
Related Topics:
Parent Topic: Oracle Revenue Management and Billing Administrative Processes