Instructor Payroll : Setup : Create incentives : Define primary incentive conditions
 
Define primary incentive conditions
 
1. Go to SysManager > Activities > Payroll Activities > View/Edit Incentives.
2. Click the New button and the Incentive Edit dialog is displayed.
 
C:\Users\Jennifer Roth\Documents\DonationCoder\ScreenshotCaptor\Screenshots\Screenshot - 2013-02-19 , 12_25_29 PM.png
 
3. Enter a Nickname for the incentive.
4. Enter a Description for the Incentive.
5. Enter a Group for the Incentive.
 
Note: Incentives can be grouped together using the Group field. This allows multiple Incentives that represent different thresholds of the same payment method to be grouped together and amounts totaled when exporting to Kronos.
 
6. Select whether this Incentive is based on meeting the conditions (leave the box unchecked) or on being an exception to the conditions (check the ARE NOT check box).
 
Note: You can pay incentives based on parameters a given lesson meets or on parameters from which a given lesson is excluded.
 
7. Select which Lesson Types (see Edit lesson types for payroll) this Incentive is applied to if the defined conditions are met using the Apply to fields.
 
Note: The Apply to fields allow you to select which Lesson Types this Incentive applies to when processing events and their pay:
AnyLesson Types with any Category designation: Other, Private, Group or blank.
PrivateLesson Types with a Category of P.
GroupLesson Types with a Category of G.
TeachingLesson Types with a Category of P or G.
OtherLesson Types with a Category of O.
 
This field allows the payroll processing to be sped up by not processing events that don’t apply to an Incentive. In other words, if payroll processing is going through events to figure out whether an event is a “request private,” you can set the system up to only go through Private Lesson Types, instead of all Lesson Types.
 
8. Decide the primary type of value upon which to base the conditions of this particular incentive calculation and select it from the Incentive Base Type dropdown list. The following table summarizes the available Incentive Base Types:
 
Incentive Base Type
Explanation
Group – Headcount
The Incentive is satisfied if the number of students associated with the event satisfies the specified criteria.
Group – Level
The Incentive is satisfied if the Level for the event satisfies the specified criteria.
Group – Return
The Incentive is satisfied if the student is marked as a Return. This can automatically be determined based on the criteria specified in SysManager or can be set manually.
Group Lesson
This Incentive is satisfied if the Lesson Type category of the event is G.
Hours – Group
This Incentive is satisfied if the event (or part of the duration of the event) falls within or crosses the threshold set for the number of Group Hours (i.e., events with a Lesson Type category of G) that has been taught by the Instructor.
 
Note: All hour calculations can be expressed as a percent by selecting another hour calculation as a denominator (i.e., Hours – Private Request / Hours – Private yields the percent of private lessons that are requests).
Hours – Group Return
Same as above except the calculated number of Hours is for a Lesson Type category of G and it is marked as a Return.
Hours – Lesson
Same as above except the calculated number of Hours is for the specified Lesson.
Hours – Lesson Type
Same as above except the calculated number of Hours is for the specified Lesson Type.
Hours – Private
Same as above except the calculated number of Hours is for events with a Lesson Type category of P.
Hours – Private Request
Same as above except the calculated number of Hours is for events with a Lesson Type category of P and the event was a Request (i.e., requested Instructor matches the assigned Instructor, which also matches the event Instructor).
Hours – Taught
Same as above except the calculated number of Hours is for events with a Lesson Type category of G or P.
Hours – Worked
Same as above except the calculated number of Hours is for events with a Lesson Type category of G or P or O (but not blank).
Instructor – Experience
The Incentive is satisfied if the Instructor has an Experience falling within the range of the specified criteria.
Instructor – First Day
The Incentive is satisfied if the Instructor’s First Day falls within the range of the specified criteria.
Instructor – Hire Date
The Incentive is satisfied if the Instructor’s Hire Date falls within the range of the specified criteria.
Instructor – Part Time
The Incentive is satisfied if the Instructor is marked as a Part Time instructor.
Instructor – Status
The Incentive is satisfied if the Instructor is assigned the Status that matches the specified criteria.
 
Note: The Statuses are configured in the Payroll tab of the Instructor Preferences in SysManager.
Lesson
The Incentive is satisfied if the event Lesson matches the specified criteria.
Lesson – Duration
The Incentive is satisfied if the event Duration falls within the range of the specified criteria.
Lesson – End Time
The Incentive is satisfied if the event End Time falls within the range of the specified criteria.
Lesson – Level
The Incentive is satisfied if the event Level falls within the range of the specified criteria.
Lesson – Location
The Incentive is satisfied if the event Location matches the specified criteria.
Lesson – Price
The Incentive is satisfied if the Price of the event falls within the range of the specified criteria.
Lesson – Start Time
The Incentive is satisfied if the event Start Time falls within the range of the specified criteria
Lesson Type
The Incentive is satisfied if the Lesson Type of the event matches the Lesson Type specified in the incentive.
Level – Alpine
The Incentive is satisfied if the Instructor has an assigned Alpine that falls within the range of the specified criteria.
Level – Other
The Incentive is satisfied if the Instructor has an assigned Other level that falls within the range of the specified criteria.
Level – Snowboard
The Incentive is satisfied if the Instructor has an assigned Snowboard level that falls within the range of the specified criteria.
Level – Telemark
The Incentive is satisfied if the Instructor has an assigned Telemark level that falls within the range of the specified criteria.
Private – Headcount
The Incentive is satisfied if the # of additionals value of the event falls within the range of the specified criteria.
Private – Request
The Incentive is satisfied if the event is a Private lesson and the event is a fulfilled Request (i.e., the requested Instructor matches the assigned Instructor).
Private – Unfulfilled Req
The Incentive is satisfied if the event is a request, but the assigned Instructor is not the requested Instructor.
Private Lesson
The Incentive is satisfied if the Lesson Type category of the event is P.
Revenue Earned Paid
Designed to be used with the base type Lesson Amount Paid. This incentive will calculate for the instructor in the resource1 field in b_sched and p_sched records. If the If conditions are used, the basis amount will consider the true lesson amount paid by the customer. This is the lesson price without taxes added in and with discounts taken out. Please see below for examples.
Revenue Earned Price
Designed to be used with the basis type Lesson Price. This incentive will calculate for the instructor in the resource1 field in b_sched and p_sched records. If the If conditions are used, the basis amount will consider the lesson price by the customer, before taxes and regardless of discounts. Please see below for examples.
Revenue Paid Requested
Designed to be used with basis type Lesson Amount Paid. This incentive will calculate for instructors which are in the resource1 field AND the resrc_req1 field. If the If conditions are used, the basis amount will consider the true lesson amount paid by the customer. This is the lesson price without taxes added in and with discounts taken out. Please see below for examples.
Revenue Price Requested
Designed to be used with basis type Lesson Price. This incentive will calculate for instructors which are in the resource1 field AND the resrc_req1 field. If the If conditions are used, the basis amount will consider the lesson price by the customer, before taxes and regardless of discounts. Please see below for examples.
Skills #1
The Incentive is satisfied if the value of the Skills #1 matches the value for criteria1 of the event. The values are based off of the Captions for List 1 of the Private Booking Preferences as defined in the SysManager > Preferences > Private Bookings > Captions tab.
Skills #2
The Incentive is satisfied if the value of the Skills #2 matches the value for criteria6 of the event. The values are based off of the Captions for List 2 of the Private Booking Preferences as defined in the SysManager > Preferences > Private Bookings > Captions tab.
Skills #3
The Incentive is satisfied if the value of the Skills #3 matches the value for criteria7 of the event. The values are based off of the Captions for List 3 of the Private Booking Preferences as defined in the SysManager > Preferences > Private Bookings > Captions tab.
 
Note: If the above Incentive Base Type list does not show in the dropdown, call Siriusware Technical Support.
 
Examples:
The following examples illustrate Revenue Earned Paid, Revenue Earned Price, Revenue Paid Requested and Revenue Price Requested.
Consider the following pricing:
1-Hour Private Ski Lesson: Base Price $50.00
Weekday discount - 5.00
Tax 3.88
 
2-Hour Private Ski Lesson: Base Price 90.00
Weekday discount - 9.00
Tax 6.98
 
Existing History in P_SCHED (fields which are not exact field names in parentheses)
 
Booking ID
Resource1
Resrc_req1
(Item)
(Price)
(Paid)
101001
LVONN
BMILLER
1-Hour Private
50.00
45.00
101002
LVONN
LVONN
2-Hour Private
90.00
81.00
101003
PSTREET
LVONN
1-Hour Private
50.00
45.00
101004
LVONN
 
2-Hour Private
90.00
81.00
 
History in B_SCHED:
 
Note: Records in B_SCHED remain even after they have been paid and created in P_SCHED. The system checks for a match on BookingID so as to not calculate that lesson twice. Only those records with pay_status of A or L will be considered for incentives.
 
Booking ID
Resource1
Resrc_req1
(Item)
(Price)
(Paid)
Pay_status
101001
LVONN
BMILLER
1-Hour Private
50.00
45.00
 
101002
LVONN
LVONN
2-Hour Private
90.00
81.00
 
101003
PSTREET
LVONN
1-Hour Private
50.00
45.00
 
101004
LVONN
 
2-Hour Private
90.00
81.00
 
101005
PSTREET
PSTREET
1-Hour Private
50.00
45.00
A
101006
LVONN
 
2-Hour Private
90.00
81.00
A
101007
LVONN
LVONN
2-Hour Private
90.00
81.00
A
 
Now, consider the following four incentives that exist:
REPAID (Revenue Earned Paid)
Pay 8 % for Values > $300
 
REPRICE (Revenue Earned Price)
Pay 8% for Values > $45
 
RQPAID (Revenue Paid Requested)
Pay 10% if Values > 100
 
RQPRICE (Revenue Price Requested)
Pay 10% if Values > 30
 
Booking ID
Instructor
Incentive
Incentive Amt
Basis
Explanation
101005
PSTREET
REPAID
None
90.00
Basis amount not > 300
 
 
REPRICE
$4.00
100.00
Basis amount met,
8% of current timecard price of $50
 
 
RQPAID
None
45.00
Basis amount not > 100
 
 
RQPRICE
$5.00
50.00
Basis amount met,
10% of current timecard price of $50
101006
LVONN
REPAID
None
288.00
Basis amount not
> 300
 
 
REPRICE
$7.20
320.00
Basis amount met, 8% of current timecard price of $90
 
 
RQPAID
None
 
Instructor was not requested
 
 
RQPRICE
None
 
Instructor was not requested
101007
LVONN
REPAID
$6.48
369.00
Basis amount met,
8% of current paid amount
 
 
REPRICE
$7.20
410.00
Basis amount met, 8% of current price
 
 
RQPAID
$8.10
162.00
Basis amount met, 10% of current paid amount
 
 
RQPRICE
$9.00
180.00
Basis amount met, 10% of current price
 
In this example, both types of incentives (price and paid) were used to illustrate the calculations. In a typical situation, one method or the other would be chosen.
It is important to note that the past history (p_sched) records are used only to determine eligibility of the incentive for current calculation. Once it has been established whether the incentive should calculate for this timecard, then the current amount for the timecard is what is used in calculating the incentive.
 
Example:
Review the figures used in determining incentives for timecard 101006. Please refer to the data above as the basis for the calculations.
Payroll is calculated for the three current timecards (bookings 101005, 101006, and 101007). Each one is evaluated separately. The following results are seen.
REPAID
1. Does Resource1 = LVONN? Yes
2. Has the If criterion been met?
 
Calculation
Basis Subtotal
Basis amount is calculated by summing the Paid amount for all P_SCHED records where LVONN is the Resource1
$207
Now add any previous timecards in b_sched in which LVONN is the Resource1
$0
 
Now add the Paid amount for the current timecard for which we are calculating basis amount ($81)
$288
 
Does $288 meet the incentive threshold of $300? No
 
No further calculation is done.
 
 
REPRICE
1. Does Resource1 = LVONN? Yes
2. Has the If criterion been met?
 
Calculation
Basis Subtotal
Basis amount is calculated by summing the Price amount for all P_SCHED records where LVONN is the Resource1
$230
Now add any previous timecards in b_sched in which LVONN is the Resource1
$0
 
Now add the Price amount for the current timecard for which we are calculating basis amount ($90)
$320
 
Does $288 meet the incentive threshold of $45? Yes
 
The current Price amount ($90) is multiplied by the incentive percent (8%) for an incentive of $7.20.
 
 
RQPAID
1. Do Resource1 and Resrc_req1 = LVONN? NO
2. No further calculations are performed.
 
RQPRICE
1. Do Resource1 and Resrc_req1 = LVONN? NO
2. No further calculations are performed.
 
9. If the Incentive is calculated based on a ratio relationship between the Incentive Base Type and another value, click the Divided by: check box. Once the check box has been selected, the field below it becomes active and you can select a denominator for the ratio relationship.
 
Example:
If you would like to use a ratio of request hours to total hours worked in the conditions for an incentive:
Hours – Private Request
---------------------------------
Hours – Worked
 
Then you would check Divide by and select Hours – Worked in the dropdown field below.
 
10. If the Incentive Base Type has more than one option associated with it, the Specific Incentive Base field becomes active and you must choose one of the selections upon which to base the conditions for calculating this incentive. The following table summarizes the Incentive Base Types which can have Specific Incentive Bases and from where the Specific Incentive Base list comes.
 
Incentive Base Type
Specific Incentive Base List Source
Hours – Lesson
The list includes all Lessons that are either private or pod bookings.
Hours – Lesson Type
The list includes all Lesson Types as defined in SysManager > Activities > Lesson Lists > Lesson Types.
Instructor – Status
The list includes all entries made into the six Option X text boxes on the Payroll tab in SysManager > Preferences > Instructors. One of these can be selected during Instructor setup as Employee Status on the SysManager > Activities > Instructors > New > Payroll tab.
Lesson
The list includes all Lessons that are either private or pod bookings.
Lesson – Location
The list includes all Lesson Locations as defined in SysManager > Activities > Lesson Lists > Lesson Locations.
Lesson Type
The list includes all Lesson Types as defined in SysManager > Activities > Lesson Lists > Lesson Types.
Skills #1
This list includes all entries under Values for List 1 in the SysManager > Preferences > Private Bookings > Captions tab.
Skills #2
This list includes all entries under Values for List 2 in the SysManager > Preferences > Private Bookings > Captions tab.
Skills #3
This list includes all entries under Values for List 3 in the SysManager > Preferences > Private Bookings > Captions tab.
 
11. The For Values fields allow you to define a specific value or range of values and the relationship that must exist between the calculated value (either the Incentive Base Type, a ratio of the Incentive Base Type to another value or the Specific Incentive Base) and the conditional value(s).
 
Example:
If in order to apply this Incentive for paying an Instructor the ratio of request hours to total hours worked must be greater than 10% but less than 25%, you would enter the following in the For Values fields:
> 0.10 and < 0.25
 
12. It is possible to define the duration for which the calculations are made, if you are calculating totals to satisfy a particular condition. The Duration for Calculating Totals section of the screen is active only for Hours-based Incentive Base Types. In the Duration for Calculating Totals section select For All Time if the total is to be calculated for all the existing data in your SiriusSQL database; select For the Last … Days and enter a number of days in the past (including today) on which to base the total if the total is to be calculated only for a certain number of days in the past; select From ... thru ... if the total is to be calculated based on a particular date range, and then enter the date range.