Pricing Discount Thresholds

Summary:

This document describes base functionality and setup of Pricing Discount Thresholds.

Functional Documentation

1. The Max Work Comp Discount field has been added to the State Master to define the maximum work comp discount allowed for the state. Since the competitive environment is highly dependent on the state, it makes sense to store at the state level. MaxWorkCompDiscount (% data type)

2. The Discount Threshold table has been added to define the max discount thresholds for members in a role. Work comp discount will be one of these definitions.

Role (role selector data type)
Work Comp Discount threshold % of Max (% data type): this will define the percentage of the max work comp discount (see above...new field on the state master) that is allowed for members of this role. Default this field to 100% on record create if the field is left blank.
Minimum Admin Per Head (money data type)
Minimum Admin Per Account (money data type)
Max SUTA discount (% data type)

This table is managed in the admin workspace. Validation insures that only one Discount Threshold can be setup per role.

3. A new field (submitted by user) has been added to the pricing batch form. This field determines the user rights that will be used to allow or disallow the desired level of discounting. PricingBatch.SubmittedByUser (user data type: read only)

4. Business logic has been added to the pricing batch submission to validate that the user submitting the batch is not discounting the work comp on any of the associated states more than their allowed maximum. If the user has set any of the PricingCode.WorkCompDiscount at a level that is more than they are allowed, a hard error will be raised when the batch is submitted. The error handles both initial quoting and repricing. The error states "Work comp discount exceeds max allowed for code 8810FL (max%), 8742FL (max%), etc".

The max discount % threshold is the highest discount level for any of the roles that the user is a member of. The max discounts are all stored at the state level. The user role will have the ability to use a portion of the max discount. For example: If the max Work Comp Discount for Florida is 30%, and a user is a member of a role that has authority to discount at 50% of the max discount, they will be able to discount at a 15% level If no record exists for any given state that is being submitted, for any role the user is a member of, the user is not allowed to discount codes in that state at all.
The validation is based on the user that is submitting the deal, not the salesperson and can be skipped using the 'Override Validations' checkbox, a secured field on the pricing batch dataform.
The validation business rule also sets the PricingBatch.SubmittedByUser.

5. The business rule that validates the minimum admin per head and per account that is currently stored on the Default Information form instead now validates at the user (role) level if there are any Discount Threshold records setup.

On submission of a pricing batch, the minimum Per Head and Per Account admin that the user is able to set are determined based on their roles. If no Threshold records are setup, then defaults are used from the Default Information Form.
Total Admin fee is calculated using the standard function (same as on pricing console). This Total Admin will be compared to the Minimum Admin Per Account. Validation of the minimum admin per head is done by dividing the total admin by the total number of EEs (part time and full time) on any active pricing code associated with the Pricing Batch that is being submitted.