An Account Owner is a Responsible User who retains ownership of an account as it moves from state to state, cycles through delinquency, etc. The ownership is invoked using ownership type parameters and expiration time period parameters defined on the Collector Assignment table.
When an account meets a Collector Assignment rule, the assigned user will also become the Account Owner if the rule includes a selected Account Ownership Type. Account Ownership is invoked by establishing one of the mutually exclusive parameter values used to determine the expiration of ownership. Start of ownership is assumed to be the point at which the Collector is assigned. Based on the Account Ownership Type defined, further processing is done to determine the Account Ownership expiration appropriately:
Assignment # of Days – This allows management to assign the account to an owner for a specified number of calendar days. When this type is selected, CACS calculates an Ownership End Date by using WORK-DATE + number of calendar days specified. If the calculated end date falls on a non-processing day the next processing date will be used.
Reassign on Day of Month – This allows management to assign the account to an owner until a specific day of the month is reached. When this type is selected, CACS calculates an Ownership End Date using the Day (DD) value specified in the Collector Assignment rule. The calculation sets the End Date with a value of when the Day (DD) specified next occurs on the calendar, taking into account months with fewer days than the Day of Month value specified. If the calculated end date falls on a non-processing day the next processing date will be used.
Reassign on Cycle Activity – This allows management to assign the account to an owner until the account receives its next cycle transaction. This AO type does not require any date field to be populated. Instead expiration occurs when the Cycle number assigned to the account is identified for cycle processing.
Reassign on Trigger Value – This allows management to assign the account to an owner until a table-derived Trigger is generated, indicating the ownership should end. The Trigger value specified in the CA rule is stored on the account record, and the account owner will stay in place until CACS is notified the Trigger should expire. The Account Ownership Trigger table is used to define this Trigger Value, and specify when this Trigger should be generated, causing all accounts with the associated Trigger to process through Account Ownership removal. In other words, when the date defined on the Account Ownership Trigger table arrives, the account ownership will be removed on accounts that have that Trigger in their record.
If an account has an Account Owner and the account is routed to a review state or a functional area in which the account owner has ownership rights but does not have the authority to work, the AO information is retained even though the user cannot work the account. Instead, the Responsible Manager ID may be used to assign work. The Responsible User field will still contain the ID of the account owner, while the ID of the Responsible Manager for that state is stored in a new Manager ID field. It is important to note the Manager ID field is populated based on collector assignment rules, so the rules must be defined appropriately for situations such as this.
When an AO account is in a review state and has the Manager ID field populated, the work lists are built based on Manager ID field rather than the Responsible User field. When accounts are routed out of a review state, the Manager ID is cleared.