System Configuration - Revision history

Joel: /* Days In Accrual Year */

2023-07-26T22:48:49Z

‎Days In Accrual Year

Joel: /* Days In Accrual Year */

2023-07-26T22:07:53Z

‎Days In Accrual Year

Joel: /* Days In Accrual Year */

2023-07-26T22:04:14Z

‎Days In Accrual Year

Jeffrey: /* Accruals */

2023-07-25T19:50:54Z

‎Accruals

Joel: /* Time Clocks */

2023-07-14T15:32:07Z

‎Time Clocks

Joel: /* Defaults */

2020-02-19T16:15:55Z

‎Defaults

Joel: /* Time Clocks */

2019-01-03T15:20:41Z

‎Time Clocks

Joel: /* Accruals */

2018-07-05T14:27:45Z

‎Accruals

Joel: /* Time Clocks */

2018-05-15T22:09:01Z

‎Time Clocks

Joel: /* Time Clocks */

2018-05-15T22:00:06Z

‎Time Clocks

@@ Line 211: / Line 211: @@
 ======Days In Accrual Year======
-* ''Accrual Periods in Accrual Period Group'' - This option will take all accrual periods associated with a specific accrual year and then count up the number of days in each period and then sums the total to get the number of days in the accrual year. This can result in the total number of days having a large range (most years will be 52-weeks/26-biweeks or 364 days, but once in a while a year will be 53-weeks/27-biweeks or 371/378 days. It also allows for the switching between bi-weekly and weekly periods in middle of an accrual year. Please also note that you MUST BUILD the entire accrual year even if you start the accruals in middle of a year.
+* ''Accrual Periods in Accrual Period Group'' - This option will take all accrual periods associated with a specific accrual year and then count up the number of days in each period and then sums the total to get the number of days in the accrual year. Using this option will cause your weekly entitlements to potentially change from year to year since it is possible to have an extra period every few years. (Most years will be 52-weeks/26-biweeks or 364 days, but once in a while a year will be 53-weeks/27-biweeks or 371/378 days).
 * ''Actual days In Calendar Year'' - This option will count the number of days in that specific calendar year and divide your annual entitlement by that number. Most years will be 365, however a leap year will have 366. Selecting this option will mean that the period entitlement can change from year to year even though the annual entitlement is the same for each year.
 * ''364 Days'' - This option will take your annual entitlement and divide it by 364 days every year. Your period entitlement will never change with this method.
 * ''365 1/4 Days'' - This option will take your annual entitlement and divide it by 365.25 days every year. Your period entitlement will never change with this method.
 * ''Employee's Accrual Year (Anniv. to Anniv.)'' - This option is used if you want to see the full entitlement earned as of the employee anniversary (an employee who used no time, will have their exact annual entitlement on the day of the anniversary). When selecting this, the software will release each period's earnings in the next period. The accrual year is obtained by counting the number of accrual periods that are in the employee anniversary year and then dividing the annual entitlement by that number to get the amount earned per period. Using this option will cause your weekly entitlements to potentially change from year to year since it is possible to have an extra period every few years. If you are using this method you can never switch between bi-weekly and weekly periods at any point in time.
 ''Do Not Project Current accrual Period'' - Displays the actual balance for the current accrual period according to what the employee already worked so far in the period even though the period has not ended yet so we don't know what it will actually be on the end of the period. Unlike future periods which show a projected balance. This is useful to be able to see how much the employee accrued so far in the period.

@@ Line 215: / Line 215: @@
 * ''364 Days'' - This option will take your annual entitlement and divide it by 364 days every year. Your period entitlement will never change with this method.
 * ''365 1/4 Days'' - This option will take your annual entitlement and divide it by 365.25 days every year. Your period entitlement will never change with this method.
-* ''Employee's Accrual Year (Anniv. to Anniv.)'' - This option is used if you want to see the full entitlement earned as of the employee anniversary (an employee who used no time, will have their exact annual entitlement on the day of the anniversary). When selecting this, the software will release each period's earnings in the next period. The accrual year is obtained by counting the number of accrual periods that are in the employee anniversary year and then dividing the annual entitlement by that number to get the amount earned per period. Using this option will cause your weekly entitlements to potentially change from year to year since it is possible to have an extra period every few years. If you are using this method you can not change the accrual period from bi-weekly to weekly or vice versa.
+* ''Employee's Accrual Year (Anniv. to Anniv.)'' - This option is used if you want to see the full entitlement earned as of the employee anniversary (an employee who used no time, will have their exact annual entitlement on the day of the anniversary). When selecting this, the software will release each period's earnings in the next period. The accrual year is obtained by counting the number of accrual periods that are in the employee anniversary year and then dividing the annual entitlement by that number to get the amount earned per period. Using this option will cause your weekly entitlements to potentially change from year to year since it is possible to have an extra period every few years. If you are using this method you can never switch between bi-weekly and weekly periods at any point in time.
 ''Do Not Project Current accrual Period'' - Displays the actual balance for the current accrual period according to what the employee already worked so far in the period even though the period has not ended yet so we don't know what it will actually be on the end of the period. Unlike future periods which show a projected balance. This is useful to be able to see how much the employee accrued so far in the period.

@@ Line 211: / Line 211: @@
 ======Days In Accrual Year======
-* ''Accrual Periods in Accrual Period Group'' - This option will take all accrual periods associated with a specific accrual year and then count up the number of days in each period and then sums the total to get the number of days in the accrual year. This can result in the total number of days having a large range. It also allows for the switching between bi-weekly and weekly periods in middle of an accrual year. Please also note that you MUST BUILD the entire accrual year even if you start the accruals in middle of a year.
+* ''Accrual Periods in Accrual Period Group'' - This option will take all accrual periods associated with a specific accrual year and then count up the number of days in each period and then sums the total to get the number of days in the accrual year. This can result in the total number of days having a large range (most years will be 52-weeks/26-biweeks or 364 days, but once in a while a year will be 53-weeks/27-biweeks or 371/378 days. It also allows for the switching between bi-weekly and weekly periods in middle of an accrual year. Please also note that you MUST BUILD the entire accrual year even if you start the accruals in middle of a year.
 * ''Actual days In Calendar Year'' - This option will count the number of days in that specific calendar year and divide your annual entitlement by that number. Most years will be 365, however a leap year will have 366. Selecting this option will mean that the period entitlement can change from year to year even though the annual entitlement is the same for each year.
 * ''364 Days'' - This option will take your annual entitlement and divide it by 364 days every year. Your period entitlement will never change with this method.
-* ''365 1/4 Days'' - This option will take your annual entitlement and divide it by 364 days every year. Your period entitlement will never change with this method.
+* ''365 1/4 Days'' - This option will take your annual entitlement and divide it by 365.25 days every year. Your period entitlement will never change with this method.
-* ''Employee's Accrual Year (Anniv. to Anniv.)'' - This option is used if you want to see the full entitlement earned as of the employee anniversary (an employee who used no time, will have their exact annual entitlement on the day of the anniversary). When selecting this, the software will release each period's earnings in the next period. The accrual year is obtained by counting the number of accrual periods that are in the employee anniversary year and then dividing the annual entitlement by that number to get the amount earned per period. Using this option will cause your weekly entitlements to potentially change from year to year since it is possible to have an extra period every few years. If you are using this method you can not change the accrual period from bi-weekly to weekly
+* ''Employee's Accrual Year (Anniv. to Anniv.)'' - This option is used if you want to see the full entitlement earned as of the employee anniversary (an employee who used no time, will have their exact annual entitlement on the day of the anniversary). When selecting this, the software will release each period's earnings in the next period. The accrual year is obtained by counting the number of accrual periods that are in the employee anniversary year and then dividing the annual entitlement by that number to get the amount earned per period. Using this option will cause your weekly entitlements to potentially change from year to year since it is possible to have an extra period every few years. If you are using this method you can not change the accrual period from bi-weekly to weekly or vice versa.
 ''Do Not Project Current accrual Period'' - Displays the actual balance for the current accrual period according to what the employee already worked so far in the period even though the period has not ended yet so we don't know what it will actually be on the end of the period. Unlike future periods which show a projected balance. This is useful to be able to see how much the employee accrued so far in the period.

@@ Line 209: / Line 209: @@
 ''Projected Months'' - How far in advance the software should display projected accruals on the employee's Accrual Detail tab automatically. This affects the software speed when making time card edits, as for every edit all these future accrual months have to be recalculated. To speed up the software, lower the months and instead use the Recalculate-Accruals + Shift button to project a year in advance when needed.
-''Days In Accrual Year''
+======Days In Accrual Year======
-* Accrual Periods in Accrual Period Group
+* ''Accrual Periods in Accrual Period Group'' - This option will take all accrual periods associated with a specific accrual year and then count up the number of days in each period and then sums the total to get the number of days in the accrual year. This can result in the total number of days having a large range. It also allows for the switching between bi-weekly and weekly periods in middle of an accrual year. Please also note that you MUST BUILD the entire accrual year even if you start the accruals in middle of a year.
-* Actual days In Calendar Year
+* ''Actual days In Calendar Year'' - This option will count the number of days in that specific calendar year and divide your annual entitlement by that number. Most years will be 365, however a leap year will have 366. Selecting this option will mean that the period entitlement can change from year to year even though the annual entitlement is the same for each year.
-* 364 Days
+* ''364 Days'' - This option will take your annual entitlement and divide it by 364 days every year. Your period entitlement will never change with this method.
-* 365 1/4 Days
+* ''365 1/4 Days'' - This option will take your annual entitlement and divide it by 364 days every year. Your period entitlement will never change with this method.
-* Employee's Accrual Year (Anniv. to Anniv.) - This option will release each period's earnings in the next period.
+* ''Employee's Accrual Year (Anniv. to Anniv.)'' - This option is used if you want to see the full entitlement earned as of the employee anniversary (an employee who used no time, will have their exact annual entitlement on the day of the anniversary). When selecting this, the software will release each period's earnings in the next period. The accrual year is obtained by counting the number of accrual periods that are in the employee anniversary year and then dividing the annual entitlement by that number to get the amount earned per period. Using this option will cause your weekly entitlements to potentially change from year to year since it is possible to have an extra period every few years. If you are using this method you can not change the accrual period from bi-weekly to weekly
-''Do Not Project Current accrual Period'' - displays the actual balance for the current accrual period according to what the employee already worked so far in the period even though the period has not ended yet so we don't know what it will actually be on the end of the period. Unlike future periods which show a projected balance. This is useful to be able to see how much the employee accrued so far in the period.
+''Do Not Project Current accrual Period'' - Displays the actual balance for the current accrual period according to what the employee already worked so far in the period even though the period has not ended yet so we don't know what it will actually be on the end of the period. Unlike future periods which show a projected balance. This is useful to be able to see how much the employee accrued so far in the period.
 == Scheduled Tasks ==

@@ Line 65: / Line 65: @@
 ''Using Punching Zones'' – available when using the HandPunch 3000 and 4000 models, this enables punching restrictions using either schedule based restrictions or the punching zone drop-down on the employee's [[Employee Clock Info|Clock Info]] tab.
-''Remove Unlicensed Employee'' -
+''Remove Unlicensed Employee'' - will check the License 1 if the expire date is older then today or empty. It will ignore the expire date if the license is set to Not Applicable. This setting only works for a Hand Punch.
 ''Use Multiple Threads'' – HandPunch communication occurs in a serial manner, in that the software communicates to one HandPunch followed by the next HandPunch and so on. This setting allows the software to communicate to all HandPunches at the same time. However, multiple copies of the RSI communication DLL are required.

← Older revision		Revision as of 16:15, 19 February 2020
Line 42:		Line 42:

	Defaults for [[Pay Types Configuration\|Pay Type]] and [[Shifts Configuration\|Shift]] are required because calculations cannot be assigned to an unknown pay type or to an unknown shift. The other defaults are required on an “as needed” basis. For example, Available will not be a selection in Schedule Patterns if the Available Status Type has not been set.		Defaults for [[Pay Types Configuration\|Pay Type]] and [[Shifts Configuration\|Shift]] are required because calculations cannot be assigned to an unknown pay type or to an unknown shift. The other defaults are required on an “as needed” basis. For example, Available will not be a selection in Schedule Patterns if the Available Status Type has not been set.
		+
		+	''Latest Active Status is considered Hire Date'' - If having multiple Active Statuses on a single employee, the software will assume that the hire date is the last Active Status. By default the software assumes that the hire date is the earliest Active Status. (An employee can have only one real Hire Date even if they get rehired multiple times). As soon as an Is Hire Date check box gets selected on the Shift History it overrides any software assumptions and forces the software to use that as the hire date.

	== Time Clocks ==		== Time Clocks ==

@@ Line 47: / Line 47: @@
 [[image:System_Time_Clocks.png]]
-''Duplicate Punch Minutes'' – punches by the same employee that occur within this entered number of minutes from each other are considered to be "duplicate." The first punch of 2 or more punches that occur within this duplicate punch window is displayed, while the other punches are hidden (but not discarded). If explicit punching is being used, then the duplicate punch setting only applies to punches of the same punch type.
+''Duplicate Punch Minutes'' – punches by the same employee that occur within this entered number of minutes from each other are considered to be "duplicate." The first punch of 2 or more punches that occur within this duplicate punch window is displayed, while the other punches are hidden (but not discarded). (As an example, if this is set to 1, then the 2nd punch that has the same time as the first punch will be hidden. If the 2nd punch is 1 minute later then it will not be considered duplicate and will be displayed). If explicit punching is being used, then the duplicate punch setting only applies to punches of the same punch type.
 ''Unassigned Clock IDs Expiration Days'' – the number of days that you have to enter an employee into the software before the enrolled clock ID is considered unused and is removed from the clock. This stops the clock from getting filled up with incorrect numbers.

← Older revision		Revision as of 14:27, 5 July 2018
Line 204:		Line 204:

	[[image:System_Accruals.png]]		[[image:System_Accruals.png]]
		+
		+	''Projected Months'' - How far in advance the software should display projected accruals on the employee's Accrual Detail tab automatically. This affects the software speed when making time card edits, as for every edit all these future accrual months have to be recalculated. To speed up the software, lower the months and instead use the Recalculate-Accruals + Shift button to project a year in advance when needed.

	''Days In Accrual Year''		''Days In Accrual Year''

@@ Line 47: / Line 47: @@
 [[image:System_Time_Clocks.png]]
-Duplicate Punch Minutes – punches by the same employee that occur within this entered number of minutes from each other are considered to be "duplicate." The first punch of 2 or more punches that occur within this duplicate punch window is displayed, while the other punches are hidden (but not discarded). If explicit punching is being used, then the duplicate punch setting only applies to punches of the same punch type.
+''Duplicate Punch Minutes'' – punches by the same employee that occur within this entered number of minutes from each other are considered to be "duplicate." The first punch of 2 or more punches that occur within this duplicate punch window is displayed, while the other punches are hidden (but not discarded). If explicit punching is being used, then the duplicate punch setting only applies to punches of the same punch type.
-Unassigned Clock IDs Expiration Days – the number of days that you have to enter an employee into the software before the enrolled clock ID is considered unused and is removed from the clock. This stops the clock from getting filled up with incorrect numbers.
+''Unassigned Clock IDs Expiration Days'' – the number of days that you have to enter an employee into the software before the enrolled clock ID is considered unused and is removed from the clock. This stops the clock from getting filled up with incorrect numbers.
-Unassigned Clock IDs Expiration Date – any clock ID that was last used prior to this date and does not belong to an employee entered into the software will be removed.
+''Unassigned Clock IDs Expiration Date'' – any clock ID that was last used prior to this date and does not belong to an employee entered into the software will be removed.
-Hourly Tasks Minute - clock [[tasks]] that run hourly will run when they start in the same minute as this setting.
+''Hourly Tasks Minute'' - clock [[tasks]] that run hourly will run when they start in the same minute as this setting.
-Allow Multiple Clock IDs - used if it's required for an employee to punch with 2 clock ID's for the same time card. The 2nd clock ID can be used to automatically assign those hours with a different department or other labor level. On the Clock Info tab it will show a number on the top right corner which indicates 1st clock ID or 2nd Clock ID.
+''Allow Multiple Clock IDs'' - used if it's required for an employee to punch with 2 clock ID's for the same time card. The 2nd clock ID can be used to automatically assign those hours with a different department or other labor level. On the Clock Info tab it will show a number on the top right corner which indicates 1st clock ID or 2nd Clock ID.
-Allow Multi Facility All Time Clocks - used if it's required for an employee to punch in another facility which is not their home-facility. On the Clock Info tab it will show a check-box which can be used to display time clocks from other facilities. Please note that the software will not check for duplicate clock ID's accrues facilities. You will need to keep track on your own to make sure that these multi-facility employees have unique Clock ID's which no one else is using.
+''Allow Multi Facility All Time Clocks'' - used if it's required for an employee to punch in another facility which is not their home-facility. On the Clock Info tab it will show a check-box which can be used to display time clocks from other facilities. Please note that the software will not check for duplicate clock ID's accrues facilities. You will need to keep track on your own to make sure that these multi-facility employees have unique Clock ID's which no one else is using.
-Explicit Punching – explicit punching at the time clock and explicit punching in the software do not have to be identical. If explicit punching is turned on in the software, then punches entered in the software always require the designation of In, Out, Back from Break or Back from Lunch. This setting forces users to designate the punch type in the same manner as is required at the HandPunch.
+''Explicit Punching'' – explicit punching at the time clock and explicit punching in the software do not have to be identical. If explicit punching is turned on in the software, then punches entered in the software always require the designation of In, Out, Back from Break or Back from Lunch. This setting forces users to designate the punch type in the same manner as is required at the HandPunch.
-Using Punching Zones – available when using the HandPunch 3000 and 4000 models, this enables punching restrictions using either schedule based restrictions or the punching zone drop-down on the employee's [[Employee Clock Info|Clock Info]] tab.
+''Using Punching Zones'' – available when using the HandPunch 3000 and 4000 models, this enables punching restrictions using either schedule based restrictions or the punching zone drop-down on the employee's [[Employee Clock Info|Clock Info]] tab.
-Remove Unlicensed Employee -
+''Remove Unlicensed Employee'' -
-Use Multiple Threads – HandPunch communication occurs in a serial manner, in that the software communicates to one HandPunch followed by the next HandPunch and so on. This setting allows the software to communicate to all HandPunches at the same time. However, multiple copies of the RSI communication DLL are required.
+''Use Multiple Threads'' – HandPunch communication occurs in a serial manner, in that the software communicates to one HandPunch followed by the next HandPunch and so on. This setting allows the software to communicate to all HandPunches at the same time. However, multiple copies of the RSI communication DLL are required.
-No Communication Error Emails - when the software has an error communicating to a time clock, an automatic email is sent out. This setting turns this email notifications off.
+''No Communication Error Emails'' - when the software has an error communicating to a time clock, an automatic email is sent out. This setting turns this email notifications off.
-Hourly Communication Error Emails - if the clock task gets an error and started in the same minute as the Hourly Tasks Minute, then an email will be sent.
+''Hourly Communication Error Emails'' - if the clock task gets an error and started in the same minute as the Hourly Tasks Minute, then an email will be sent.
-Show Lunch Taken Exceptions - calculates exceptions on out punches where the employee did not answer Yes to the Lunch Taken question at the HandPunch.
+''Show Lunch Taken Exceptions'' - calculates exceptions on out punches for the Lunch questions asked at the HandPunch.
-Lunch Not taken Exception When No Lunch Deduction - Generates the Lunch-Not-Taken exception anytime the employee answered at the clock Lunch-Not-Taken even if the software didn't deduct lunch automatically, (the grace minutes below will also be ignored). This is useful if the software is customized to not deduct lunch automatically depending on the employee's answer at the clock.
+''Lunch Not taken Exception When No Lunch Deduction'' - Generates the Lunch-Not-Taken exception anytime the employee answered at the clock Lunch-Not-Taken even if the software didn't deduct lunch automatically, (the grace minutes below will also be ignored). This is useful if the software is customized to not deduct lunch automatically depending on the employee's answer at the clock.
-Lunch Unknown Exception - gets generated if the employee didn't answer at the clock the lunch question.
+''Lunch Unknown Exception'' - gets generated if the employee didn't answer at the clock the lunch question.
-Lunch Not Taken Exception - gets generated only if both are true, the employee answered at the clock Lunch-Not-Taken AND the software deducted lunch automatically.
+''Lunch Not Taken Exception'' - gets generated only if both are true, the employee answered at the clock Lunch-Not-Taken AND the software deducted lunch automatically.
-Lunch Taken exception - gets generated if the employee answered at the clock Lunch-Taken.
+''Lunch Taken exception'' - gets generated if the employee answered at the clock Lunch-Taken.
-Lunch Not Required Exception - gets generated only if a software user manually sets Lunch-Not-Required on the Punch.
+''Lunch Not Required Exception'' - gets generated only if a software user manually sets Lunch-Not-Required on the Punch.
 == Labor Levels ==