What is a Plan?
What is a Plan?
Within SimplyComp, a Plan is a collection of components shared by users within similar roles. These components include Quotas, Payment Rates, and Terms and Conditions. Once a user is assigned to a plan, they will be associated with all components on that plan. However, you have the option to set Payment Rates or Quotas that are specific to a user by creating User Specific Rules.
To some companies, their compensation rules are already broken out to clearly defined plans. For other companies, this may be a new concept as they have historically had specific rules per user. Either way, SimplyComp can work for you.
Best Practice Blog: How to Develop a Sales Incentive Compensation Plan
|
Note: To be assigned to a plan, a user need to have the 'Sales Representative' Permission Set. There are no limits to the amount of plans a User can be associated with. |
Plan and Calendar Relationships
Within SimplyComp, plans are not assigned to a given Calendar year. As such, a plan can span multiple years. Given this, you do not need to rebuild the plan every year. However, Quotas and Payments are associated to Calendar Groupings. See below for an explanation on how each component interacts with Calendar Groupings.
Payment Rules apply to all dates after the effective start date you specify and before the last day of the Calendar Grouping's time-range. Multiple versions of this payment rule can exist by creating Effective Versions.
Quotas are built out for a specific Calendar Year. Copy Quotas and their values into subsequent Calendar Years within the same Calendar Grouping. Any User Specific Overrides on Quotas will carry over during this copy.
Note: If you copy a quota forward, deleting this quota at any point in time will remove the quota in past, present, and future calendar years that this quota was present in. For example: If you copy forward your New Business Quota into 2021 from 2020 and then delete the New Business Quota in the 2021 calendar year view, the 2020 version will also be deleted.
Comments
0 comments
Article is closed for comments.