In addition to the deduction settings described above, both new and existing deduction types that exist on the system can be associated with a product. This allows deductions to be created at the case level for any cases that are based on that product. In addition to configuring details about the deduction type, each deduction can be assigned a priority which dictates the order in which it is processed when payments are generated for cases that are based on the product.
In addition to configuring details about the deduction type, each deduction can be assigned a priority which dictates the order in which it is processed when payments are generated for cases that are based on the product. If there is already a deduction associated to the product with the same priority as the new or updated deduction being associated to the product, the priority of the existing deduction will be automatically updated to have the next priority. The priority of any other existing deductions may also be impacted as a result. A sequencing function will automatically increase or decrease the priorities of any other deductions associated with the product. For example, if a deduction is added with a priority of 1, and there is already a deduction with a priority of 1, the new deduction will be stored with a priority of 1 and the existing deduction will be stored with a priority of 2.
Configuration is also available which provides the ability for the agency to define whether or not overlapping deductions are allowed. If a deduction is configured to prevent overlapping deductions, a validation will be displayed if a user tries to activate a deduction which already exists on the case for an overlapping time period. This can be configured for all categories of deductions (applied, unapplied and third party).
When a deduction type is associated with a benefit product, that deduction type is then automatically made available for selection at the case level. For more information on configuring deduction types, see the Cúram Deductions Guide.