Collections profiles categorize bill units for collections purposes. By default, profiles classify bill units based on currency. However, you can customize them to categorize bill units according to other attributes, such as credit score. For example, bill units with scores below a certain threshold can be assigned to one collections profile, while those with higher scores can be assigned to a different profile.

A bill unit's collections profile helps determine which collections scenario it is assigned to. For example, bill units in the low-credit-score profile may be assigned to scenarios with more aggressive collections actions and lower entry criteria. Conversely, bill units with high credit scores might be placed in scenarios with more lenient policies.

By default, all bill units belong to a single collections profile. If you do not need a more complex system, you do not need to define any additional profiles and can map all scenarios to the default profile.

To set up additional profiles, complete the following tasks:

1. Define collections profiles in Collections Configuration Center by specifying the profile name, description, and currency. See "Managing Collections Profiles" in Collections Configuration Center Online Help.

   When you create a new profile, Collections Configuration Center creates a /config/collections/profile object, which stores profile definitions.

2. Customize the PCM_OP_COLLECTIONS_POL_SELECT_PROFILE policy opcode to define the characteristics of collections profiles and map bill units to them. See "Mapping Bill Units to Collections Profiles" in BRM Opcode Guide.

   Note:

   This step requires programming.

When setting up additional profiles, you might need to increase the space allocated to the profiles data in the CM cache.

To increase the CM cache size for profiles data:

1. Open the CM configuration file (BRM_home/sys/cm/pin.conf) in a text editor.

2. Increase cache_size in the following entry:

   - cm_cache fm_collections_config_profiles_cache number_of_entries, cache_size, hash_size

   Note:

   The default is 20480 bytes.

3. Save and close the file.

4. Stop and restart the CM.