Administrator Guide > Collection |
The Solution.Collection page (System Management > Solutions > Collection) allows administrators to manage several features in the Framework. This page serves as a centralized hub for important Framework settings.
This tab contains general collections settings.
The following fields are displayed:
Field | Function | ||
Default Letter User |
This drop down contains a listing of all users currently in Framework, both active and inactive. The user defined in this field is added to those letters where collector name is a merge field in the template when the letter is generated via an automated queue.
|
||
Monitor Mode |
This drop-down determines how dashboards in the Framework are to be updated. By default, Monitor Mode is set to Batch.
Batch: Batch runs the Monitor process once a day. This means users do not see the values in dashboards until the following work day when the Batch process runs. Real Time: Real Time updates the dashboards throughout the day as the end-users work in the system. This number is in minutes. Akcelerant does not recommend anything less than 60 minutes (1 hour) as if the process is constantly running it could potentially slow down the server, as the process is constantly hitting the database to obtain the necessary data to update the information on the dashboards. |
||
Monitor Last Run Time | This determines what time the Monitor process runs at the end of the day. | ||
Monitor Margin Update | Specify a percentage to be used throughout the Monitor process to determine how trend arrows are defined in the Monitor Margin Update field. If the Monitor Margin Percentage is set at 2%, then 98%-102% performance calculations are represented by a yellow dash, indicating “Even.” Performance calculations under 98% are represented by a red “Down” arrow. Performance calculations over 102% are represented by a green “Up” arrow. If the Monitor Margin Percentage is set at 5%, 95%-100% would be “Even,” fewer than 95% would be “Down” and over 105% would be “Up.” | ||
Monitor Update Interval | Determine how often the monitor and queue home page are updated. | ||
Default Contact Start Time | Determine the default start time an account created within the Framework can begin to be worked. | ||
Default Contact End Time | Determine the default end time an account created within the Framework can be worked. | ||
Prevent account work ordering across queue classifications checkbox | If checked, Delinquency and Recovery queues are separated into 2 tabs within the Collection Queue Work Order page in System Management. This prevents accounts that may fall into both queue classifications from being worked across both. |
This tab allows administrators to configure settings for when emails are sent using the Send Email workflow step. If necessary, define a header and footer to display by default when an email is sent. These settings can be changed manually from within the workflow step.
Also, administrators can manage the list of “From” email addresses that a user can choose from when sending an email using the Send Email workflow step. Clicking Add “From” Email Address populates a new line item in the grid. Click within the line item and enter in an email address. When finished click Save or click Cancel to erase the text entered. Click the checkbox to make it a default selection. To delete an email address from the list, highlight an item in the grid and click Delete.
Within the Promise Settings tab, define the company settings for Promise to Pay. In the top section, determine the minimum/maximum payments, days and amounts for promises. If a user exceeds any of these settings set forth by an administrator, a message appears to them indicating the promise to pay needs management approval. Management approval occurs in System Management > Collections > Promise Approval.
The following fields display within this tab:
Field | Description |
Maximum Promise Payments | Determines the maximum number of promise payment a user can take as part of a promise to pay. |
Maximum Promise Days | Determines the maximum number days in which the user can set the due date of the first payment. |
Maximum Promise Tolerance | Determines the maximum discount percentage that can be applied to a promise. |
Minimum Promise Payment | Determines the minimum promise amount a user can take when obtaining a promise to pay. |
Within the Next Contact Date Options section, determine how an account’s next contact date is adjusted when a promise is created, edited or broken. The following options are available to choose from within the drop-downs:
![]() |
Set NCD is only available for the "On Broken Promise" Next Contact Date Option. |
These Next Contact Date Options are used in conjunction with Payment Types (System Management > Payment Types) to adjust the Next Contact Date appropriately. When a promise is created or edited and the Next Contact Date is automatically adjusted, or when the user is prompted to adjust the Next Contact Date, the Next Contact Date on the account is updated to the number of days defined for the payment type used for the promise. When a promise is broken, and the Next Contact Date is set, it is updated to the number of days defined for the payment type.
In the above screen shot, the "On Create Promise" Next Contact Date Option is set to "Always Adjust NCD." If a promise is created on an account to make the payments by check, which has a Promise Delay of two days, then the Next Contact Date on the account is automatically adjusted to two days after the date the last payment is due.
The Queue Settings tab allows administrators manage options that affect queuing in the Framework.
The following options display in this tab:
Field | Description | ||
Queue Refresh In Process |
Displays as “YES” when a Queue Refresh is currently processing. Change the option to “NO” to stop the Queue Refresh process.
|
||
Queue Method |
Select the method of queuing to be applied in the Framework.
Basic: With Basic Queuing, queues are built using account criteria and accounts fall into an individual queue. An evaluation of the person does not occur. Advanced: With Advanced Queuing, system administrators can author simple or complex business rules to determine Queue Eligibility and use account and/or account holder attributes to organize and assign accounts and persons to a collections queue. This method of queuing provides the ability to not only queue individual accounts, but also the person and all of their eligible, non-queued accounts as well. With Advanced Queuing, administrators can define Queuing Rules in System Management> Collections > Rules Management to determine Queue Eligibility and automatically assign a person and all of their accounts to specific queues as rule conditions are met. Please see the Advanced Queuing topic within this Guide for more information. To learn more about authoring Business Rules, click here.
|
The following fields display on this page:
Field | Description |
Default FMV Discount % | Set the default Fair Market Value percentage. This value appears by default in the Equity Analysis screen. |
Default FMV Discount $ | Set the default Fair Market Value dollar amount. This value appears by default in the Equity Analysis screen. |