Collector Setup Quick Reference
Main Menu > System Administration > Maintain Collectors > Setup Collectors
Key items that the system needs to have setup so that collectors can efficiently and effectively work accounts in the system.
Note: Within the DAKCS system a collector code should be setup before creating a user name and login for any employee. All collector codes that are setup must have a name or description entered into the system to be active within Beyond.
Collector code – Anyone accessing the system will need a collector code assigned to their individual login setup.
- Codes can be alpha or numeric or a combination of the two. Collector codes are case sensitive.
- Collector codes can also represent a “bucket” of accounts and do not have to always be associated to an actual user. (Think of this and accounts that are worked by many collectors out of the same bucket.)
Key permissions for active collector codes associated with a login.
- Maximum days to advance the follow up days on accounts
- A collector pull table should be entered to ensure that accounts will be ordered by priority.
- Is a collector allowed to work accounts in any order that they desire? Do you want collectors to work their queue in a specific order without the ability to change that order?
- Allocate new business should be set if specific codes are allowed to have new business associated to the specific collector code
- How far out is a collector allowed to add a PDC transaction? This will control not only the setup of payments but also editing of existing payment plans setup
- Are collectors allowed to manually request letters? If so what letters can the request?