This page (revision-24) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
24 26-Nov-2021 10:22 26 KB kparrott to previous
23 26-Nov-2021 10:22 25 KB rforbes to previous | to last
22 26-Nov-2021 10:22 25 KB jmyers to previous | to last
21 26-Nov-2021 10:22 26 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
USING SALARY RATE METHODS
USING SALARY RATE METHODS

Version management

Difference between version and

At line 4 changed one line
P2K provides for the ability to compute an hourly rate for salaried employees so that when hours are entered into the system from any of the various sources, the rate of pay is computed (Formula explained in this document) in such a way that the proper wages are generated.
Personality provides for the ability to compute an hourly rate for salaried employees so that when hours are entered into the system from any of the various sources, the rate of pay is computed in such a way that the proper wages are generated.
At line 6 changed 2 lines
In releases prior to 30502, generating hours and dollars for salaried employees required that the dollars be generated separate from the earnings since they did not necessarily balance with each other.
It is not recommended that P2K be configured to pay salaried employees by generating earnings from the hours keyed, accomplished by varying the wage rate.
In releases prior to 30502, generating hours and dollars for salaried employees required that the dollars be generated separate from the earnings since they did not necessarily balance with each other. It is not recommended that Personality be configured to pay salaried employees by generating earnings from the hours keyed, accomplished by varying the wage rate.
At line 9 changed one line
Since earnings are generated from the hours which are generated daily, it is likely that generated earnings will be off by pennies from the employee semi monthly or monthly wage. This is handled by ‘Force Balance’ logic, invoked when the transactions are brought into payroll (UPTR).
Since earnings are generated from the hours which are generated daily, it is likely that generated earnings will be off by pennies from the employee semi-monthly or monthly wage. This is handled by ‘Force Balance’ logic, invoked when the transactions are brought into payroll ([UPTR]).
At line 11 changed one line
In most situations only salary would be required at a variable rate. For those clients using ‘Cell Points’ pay line premiums, there may be a need to compute these premiums at a variable rate of pay based on the number of hours worked in the monthly or semi-monthly pay period. The setup requirement for these premiums is described at the end of this document.
In most situations only salary would be required at a variable rate. For those clients using Cell Points pay line premiums, there may be a need to compute these premiums at a variable rate of pay based on the number of hours worked in the monthly or semi-monthly pay period. __The setup requirement for these premiums is described at the end of this document.__
At line 13 changed 3 lines
There is also a new ‘Pay Line Based’ premium that can be used in place of the ‘UPTG Period $$$’ premium. The problem with the UPTG premium is that it creates ‘Dollars Only’ into the IPTR screen, which means that the premium dollars from the hours worked in the period are not naturally generated into payroll. If not generated from hours, the UPRETRO would not be able to create the retro in the past. The correct way to handle a ‘Pay Period Premium’ is to use this new type. It will be generated from the hours worked (which may vary), and the dollars assigned to each hour will be computed by P2K correctly so that the total will equal the Period Premium Amount. To account for any penny difference, the premium is ‘Force Balanced’ when the transaction is brought into payroll during the execution of UPTR.
\\
----
There is also a new Pay Line Based premium that can be used in place of the UPTG Period $$$ premium. The problem with the [UPTG] premium is that it creates ‘Dollars Only’ into the [IPTR] screen, which means that the premium dollars from the hours worked in the period are not naturally generated into payroll. If not generated from hours, the [UPRETRO] would not be able to create the retro in the past. The correct way to handle a Pay Period premium is to use this new type. It will be generated from the hours worked (which may vary), and the dollars assigned to each hour will be computed by Personality correctly so that the total will equal the Period Premium amount. To account for any penny difference, the premium is force balanced when the transaction is brought into payroll during the execution of [UPTR].
\\ \\
----
At line 17 changed one line
A new rate routine to calculate “Variable Rate”, and ‘Variable Time” method is created. See “Business Case Examples” later in this document.
A new rate routine to calculate the Variable Rate and Variable Time method is created. __See “Business Case Examples” later in this document.__
At line 19 changed one line
On the IPPC form, PC Details Rules tab, a new salary rate method is added to point individual pay components to the Variable Rate or Variable Time. This will allow the user to select a different rate calculation for different types of time (i.e. Regular or LWOP).
On the [IPPC] form in the PC Details Rules tab, a new salary rate method is added to point individual pay components to the Variable Rate or Variable Time. This will allow you to select a different rate calculation for different types of time (i.e. Regular or LWOP).
At line 21 changed one line
For Variable Rate Hours, the number of work days in the pay period is determined from the employee work calendar. Since these are salaried employees, these work days are full days using ‘Standard hours per day’. These hours are obtained from the work calendar if present.
For Variable Rate Hours, the number of work days in the pay period is determined from the employee work calendar. Since these are salaried employees, these work days are full days using ‘Standard Hours Per Day’. These hours are obtained from the work calendar if present.
At line 23 changed one line
For Variable Rate (Elem), the number of hours worked in a pay period is determined by an element. Generally, the variable rate is calculated by dividing the semi monthly wage by the number of hours in the period (totaled for the pay period by adding all the pay components in the element).
For Variable Rate (Elem), the number of hours worked in a pay period is determined by an element. Generally, the variable rate is calculated by dividing the semi-monthly wage by the number of hours in the period (totaled for the pay period by adding all the pay components in the element).
At line 27 changed one line
The employees will have their salary calculated based on time, not the current method of generating a SM/MO salary amount in UPTG. Using this method, UPTG will support pay period employee changes such as new hires, terminations, salary changes and leaves.
The employees will have their salary calculated based on time, not the current method of generating a SM/MO salary amount in [UPTG]. Using this method, [UPTG] will support pay period employee changes such as new hires, terminations, salary changes and leaves.
At line 29 changed one line
SM/MO clients will be able to use the retro program. Please note that from the time the client changes the set up from ‘generating salary’ to ‘generating hours ONLY’. The previous pay lines are salary based and Retro will not function properly.
SM/MO clients will be able to use the retro program.
At line 31 changed one line
Since the time will be generated by day and each day will have an associated dollar amount, the standard FLSA calculations will be supported.
%%information Please note that from the time the client changes the set up from ‘generating salary’ to ‘generating hours ONLY’,the previous pay lines are salary based and Retro will not function properly.%%
At line 32 added 2 lines
Since the time will be generated by day and each day will have an associated dollar amount, the standard [FLSA] calculations will be supported.
At line 34 changed one line
Pay period earnings are force balanced during UPTR to compensate for any earnings variance caused by earnings generation on a daily basis daily.
Pay period earnings are force balanced during [UPTR] to compensate for any earnings variance caused by earnings generation on a daily basis daily.
At line 38 added one line
At line 38 changed 2 lines
\\
----
\\ \\
----
At line 41 changed 3 lines
There is a new column (Salary Rate Method) at the ‘PC Detail’ level that controls the manner in which the wage rate is computed. The column has two values that invoke logic. It is IMPORTANT to use this set up ONLY for employees that are salaried and paid either monthly or Semi-Monthly. If you are using the same Pay Component for both Hourly and Salaried Employees, then you will require separate PC Rules Sets for each.
\\
----
The Salary Rate Method column on [IPPC] in the ‘PC Detail’ level controls the manner in which the wage rate is computed. The column has two values that invoke logic. It is IMPORTANT to use this set up ONLY for employees that are salaried and paid either monthly or semi-monthly. If you are using the same pay component for both hourly and salaried employees, then you will require separate PC Rules Sets for each.
\\ \\
----
At line 45 changed one line
The exact days that an employee is scheduled to work is determined by the ‘Work Calendar’ associated with the assignment record.
The exact days that an employee is scheduled to work is determined by the work calendar associated with the assignment record.
At line 50 changed one line
\\
\\ \\
At line 52 changed one line
!!Variable Rate Hours
!!Variable Rate Hours
At line 59 changed 4 lines
!Example:
22 days at 8 hours per day = 176 hours in the period
A monthly salary of 3,000 would provide an hourly rate of $17.05 in the month.
When the employee is hired, terminated, or has a mid-period rate change, the month wage is computed by taking the daily rate and extending it by standard hours.
Example:\\
22 days at 8 hours per day = 176 hours in the period\\
A monthly salary of 3,000 would provide an hourly rate of $17.05 in the month.\\
When the employee is hired, terminated, or has a mid-period rate change, the month wage is computed by taking the daily rate and extending it by standard hours.
At line 64 changed 4 lines
!Example:
Employee is paid 3,000/Month and gets an increase on March 14th to 3,500.
11 working days at (3,000/22) * 11 = $1500.00
11 working days at (3,500 / 22) * 11 = $1750.00
Example:\\
Employee is paid 3,000/month and gets an increase on March 14th to 3,500.\\
11 working days at (3,000/22) * 11 = $1500.00\\
11 working days at (3,500/22) * 11 = $1750.00\\
At line 69 changed 4 lines
\\
----
!!Variable Rate (Element)
The key to computation of the variable rate is to divide the semi monthly wage by a number of hours. The hours will be determined by the creation of an element which will hold the pay components to be used in determination of the number of hours worked in this pay period. The Variable Hours element may be a simple or compound element, defined on IPPE.
\\ \\
At line 73 added 8 lines
%%information For Salary Rate Method 'Variable Rate Hours#'
If Variable Rate Method is used but NOT using UPTG, the IDCL ‘DAILY CALENDAR’ should be extended annually
NOTE: it is ‘hard-coded’ that you cannot manually update the DAILY CALENDAR’, you must re-name it, extend it and re-name it back.%%
----
!!Variable Rate (Element)
The key to computation of the variable rate is to divide the semi-monthly wage by a number of hours. The hours will be determined by the creation of an element which will hold the pay components to be used in determination of the number of hours worked in this pay period. The Variable Hours element may be a simple or compound element, defined on [IPPE].
At line 75 changed 3 lines
Scenarios
#Employee works the same position throughout the period\\ \\Wage rate is determined on a semi month basis through the usual annualization routine. Hours worked are computed by summing pay lines in this period for the pay components included in the Variable Hours element.\\ \\Variable Rate = Semi Month wage divided by total hours included in this element.
#Employee changes rate in mid period\\ \\Wage rate is pro-rated based upon number of days in the period that the employee is at each wage. Variable rates are computed independently for each period (pro rata).\\ \\Wage Rate 1 = semi month wage * (# days at this wage rate / # days in period)\\ \\Wage Rate 2 = semi month wage * (# days at this wage rate / # days in period)\\Hours worked are computed independently for each wage period by summing pay lines as noted above.\\ \\Variable Rate 1 = Wage Rate 1 / hours worked in period 1\\ \\Variable Rate 2 = Wage Rate 2 / hours worked in period 2
!Scenarios
#Employee works the same position throughout the period\\ \\Wage rate is determined on a semi-monthly basis through the usual annualization routine. Hours worked are computed by summing pay lines in this period for the pay components included in the Variable Hours element.\\ \\Variable Rate = Semi Month wage divided by total hours included in this element.
#Employee changes rate in mid period\\ \\Wage rate is pro-rated based upon number of days in the period that the employee is at each wage. Variable rates are computed independently for each period (pro rata).\\ \\Wage Rate 1 = semi month wage * (# days at this wage rate / # days in period)\\ \\Wage Rate 2 = semi month wage * (# days at this wage rate / # days in period)\\Hours worked are computed independently for each wage period by summing pay lines as noted above.\\ \\Variable Rate 1 = Wage Rate 1 / hours worked in period 1\\ \\Variable Rate 2 = Wage Rate 2 / hours worked in period 2.
At line 80 changed 6 lines
The Variable Hours (Element) method requires that an element be set up in IPPE to hold the pay components to be considered when calculating the number of hours worked in a pay period. It can have any element code, but must be one of the ‘group elements’ in IDGR. The Group Element type MUST be set to ‘Variable Rate’.
!Sample Pay Line Detail Audit Text
The calculations used to derive the rate are stored for future reference in a USER FIELD ATTACHED TO THE PAY LINE DETAIL as shown below. This example is slightly misrepresenting since it indicates that the text is on the pay line. This was changed in November, 2008 to be recorded on the Pay Line details since it can vary at that level.
The Variable Hours (Element) method requires that an element be set up in [IPPE] to hold the pay components to be considered when calculating the number of hours worked in a pay period. It can have any element code, but must be one of the ‘group elements’ in [IDGR]. The Group Element type MUST be set to ‘Variable Rate’.
Sample Pay Line Detail Audit Text\\
__{need screen shot}__\\
The calculations used to derive the rate are stored for future reference in a USER FIELD ATTACHED TO THE PAY LINE DETAIL as shown below. This example is slightly misrepresenting since it indicates that the text is on the pay line. This was changed in November, 2008 to be recorded on the Pay Line details since it can vary at that level.\\
__{need screen shot}__
\\ \\
----
At line 92 changed 14 lines
!Example:
22 Scheduled Shifts
Standard hours (From IEAS) = 8.5
Monthly Salary of $3,000
Hourly Rate $16.0428 = $3000 / 22 / 8.5
When the employee is hired, terminated, or has a mid-period rate change, this formulae is NOT used and the system reverts to the ‘Variable Rate Hours’ method.
!Example:
Month 01-Sep-2005 to 30-Sep-2005
Employee Hired on 18-Sep-2004
Range Begin 01-Sep-2005
Range End 30-Sep-2005
EE is TM Scheduled, Using 'Variable Rate (Shifts/Month) Method'
Number of Scheduled Shifts in Sep-2005 ==> 22
Monthly Rate ($5,000.00) / Number Shifts (22) / Std Hours (8) = Variable Rate($28.4091)
Example:\\
22 Scheduled Shifts \\
Standard hours (From [IEAS]) = 8.5\\
Monthly Salary of $3,000\\
Hourly Rate $16.0428 = $3000 / 22 / 8.5\\ \\
At line 108 added 12 lines
When the employee is hired, terminated, or has a mid-period rate change, this formula is NOT used and the system reverts to the ‘Variable Rate Hours’ method.
Example:\\
Month 01-Sep-2005 to 30-Sep-2005\\
Employee Hired on 18-Sep-2004\\
Range Begin 01-Sep-2005\\
Range End 30-Sep-2005\\
EE is TM Scheduled, Using 'Variable Rate (Shifts/Month) Method'\\
Number of Scheduled Shifts in Sep-2005 ==> 22\\
Monthly Rate ($5,000.00) / Number Shifts (22) / Std Hours (8) = Variable Rate($28.4091)
\\ \\
----
At line 122 added one line
At line 124 added one line
At line 126 added one line
At line 128 added one line
At line 130 added one line
At line 132 added one line
At line 134 added one line
At line 136 added one line
At line 138 added one line
At line 118 changed one line
Period Earnings($4,166.67) / Sched Hours (184) = Variable Rate($22.6449)
Period Earnings($4,166.67) / Sched Hours (184) = Variable Rate($22.6449)
At line 144 added one line
At line 121 changed 3 lines
(1100) Salary Rate Method: Variable Rate
(1100)
Work Calendar is '5-8'
(1100) Salary Rate Method: Variable Rate\\
(1100) \\
Work Calendar is '5-8'\\
At line 147 changed 2 lines
01-Sep-2005 Projected Earnings($4,420.29)
Period Earnings($4,420.29) / Sched Hours (184) = Variable Rate($24.0233)
01-Sep-2005 Projected Earnings($4,420.29)\\
Period Earnings($4,420.29) / Sched Hours (184) = Variable Rate($24.0233)\\
At line 175 added one line
At line 153 changed 17 lines
10-Aug $4,166.67 / 128 * 8 = $181.16
13-Aug $4,166.67 / 128 * 8 = $181.16
14-Aug $4,166.67 / 128 * 8 = $181.16
15-Aug $4,166.67 / 128 * 8 = $181.16
16-Aug $4,166.67 / 128 * 8 = $181.16
17-Aug $4,166.67 / 128 * 8 = $181.16
18-Aug $4,166.67 / 128 * 8 = $181.16
19-Aug $4,166.67 / 128 * 8 = $181.16
20-Aug $4,166.67 / 128 * 8 = $181.16
23-Aug $4,166.67 / 128 * 8 = $181.16
24-Aug $4,166.67 / 128 * 8 = $181.16
25-Aug $4,166.67 / 128 * 8 = $181.16
26-Aug $4,166.67 / 128 * 8 = $181.16
27-Aug $4,166.67 / 128 * 8 = $181.16
30-Aug $4,166.67 / 128 * 8 = $181.16
31-Aug $4,166.67 / 128 * 8 = $181.16
01-Sep-2005 Projected Earnings($2,898.56)
|10-Aug| $4,166.67 / 128 * 8 = $181.16
|13-Aug| $4,166.67 / 128 * 8 = $181.16
|14-Aug| $4,166.67 / 128 * 8 = $181.16
|15-Aug| $4,166.67 / 128 * 8 = $181.16
|16-Aug| $4,166.67 / 128 * 8 = $181.16
|17-Aug| $4,166.67 / 128 * 8 = $181.16
|18-Aug| $4,166.67 / 128 * 8 = $181.16
|19-Aug| $4,166.67 / 128 * 8 = $181.16
|20-Aug| $4,166.67 / 128 * 8 = $181.16
|23-Aug| $4,166.67 / 128 * 8 = $181.16
|24-Aug| $4,166.67 / 128 * 8 = $181.16
|25-Aug| $4,166.67 / 128 * 8 = $181.16
|26-Aug| $4,166.67 / 128 * 8 = $181.16
|27-Aug| $4,166.67 / 128 * 8 = $181.16
|30-Aug| $4,166.67 / 128 * 8 = $181.16
|31-Aug| $4,166.67 / 128 * 8 = $181.16
01-Sep-2005 Projected Earnings($2,898.56)\\
At line 175 changed 14 lines
01-Aug $4,166.67 / 104 * 8 = $181.16
02-Aug $4,166.67 / 104 * 8 = $181.16
03-Aug $4,166.67 / 104 * 8 = $181.16
06-Aug $4,166.67 / 104 * 8 = $181.16
07-Aug $4,166.67 / 104 * 8 = $181.16
08-Aug $4,166.67 / 104 * 8 = $181.16
09-Aug $4,166.67 / 104 * 8 = $181.16
10-Aug $4,166.67 / 104 * 8 = $181.16
13-Aug $4,166.67 / 104 * 8 = $181.16
14-Aug $4,166.67 / 104 * 8 = $181.16
15-Aug $4,166.67 / 104 * 8 = $181.16
16-Aug $4,166.67 / 104 * 8 = $181.16
17-Aug $4,166.67 / 104 * 8 = $181.16
01-Sep-2005 Projected Earnings($2,355.08)
|01-Aug| $4,166.67 / 104 * 8 = $181.16
|02-Aug| $4,166.67 / 104 * 8 = $181.16
|03-Aug| $4,166.67 / 104 * 8 = $181.16
|06-Aug| $4,166.67 / 104 * 8 = $181.16
|07-Aug| $4,166.67 / 104 * 8 = $181.16
|08-Aug| $4,166.67 / 104 * 8 = $181.16
|09-Aug| $4,166.67 / 104 * 8 = $181.16
|10-Aug| $4,166.67 / 104 * 8 = $181.16
|13-Aug| $4,166.67 / 104 * 8 = $181.16
|14-Aug| $4,166.67 / 104 * 8 = $181.16
|15-Aug| $4,166.67 / 104 * 8 = $181.16
|16-Aug| $4,166.67 / 104 * 8 = $181.16
|17-Aug| $4,166.67 / 104 * 8 = $181.16
01-Sep-2005 Projected Earnings($2,355.08)\\
At line 190 changed one line
\\ \\
----
At line 201 changed one line
\\ \\
----
At line 204 changed 2 lines
The audit text output from the variable rate calculation is also stored in a separate user field attached to the pay line, for future reference.
Variable Rate Audit Text Sample
The audit text output from the variable rate calculation is also stored in a separate user field attached to the pay line, for future reference.
At line 207 changed one line
!Work Pattern Text Sample
!Variable Rate Audit Text Sample
__{need screen shot}__\\
At line 237 added 4 lines
!Work Pattern Text Sample
__{need screen shot}__\\
\\ \\
----
At line 211 changed one line
[SalaryRateMethods_01.jpg]
\\ \\
----
At line 217 changed one line
To deal with this issue, P2K will perform ‘Force Balancing’ for variable rate employees when the transactions are brought into payroll (UPTR). This balancing will occur after the last transaction for an employee has been loaded into IPPH. Please note that all transactions for an employee must be in the same execution of UPTR for force balancing to be invoked. UPTR can not be executed more than once for employees using a variable rate.
To deal with this issue, Personality will perform ‘Force Balancing’ for variable rate employees when the transactions are brought into payroll ([UPTR]). This balancing will occur after the last transaction for an employee has been loaded into [IPPH].
At line 219 changed 2 lines
To be eligible for this force balance, the following conditions must be met.
*the pay type (IDGR) must be set to ‘Salary’
%%information Please note that all transactions for an employee must be in the same execution of [UPTR] for force balancing to be invoked. [UPTR] can not be executed more than once for employees using a variable rate.%%
To be eligible for this force balance, the following conditions must be met:
*the pay type ([IDGR]) must be set to ‘Salary’
At line 223 changed 2 lines
*there must not be a change in the employee’s compensation within the pay period.
*there must be a pay component defined with the usage (Salary Force Balance).
*there must not be a change in the employee’s compensation within the pay period
*there must be a pay component defined with the usage (Salary Force Balance)
At line 226 changed one line
The Force Balance pay component must point to an element containing the pay components that are part of regular earnings. These earnings should contain anything that is generated from UPTG and as well as anything that may be entered as exceptions in IPTR that would be considered part of the employee’s regular earnings.
The Force Balance pay component must point to an element containing the pay components that are part of regular earnings. These earnings should contain anything that is generated from [UPTG] and as well as anything that may be entered as exceptions in [IPTR] that would be considered part of the employee’s regular earnings.
At line 228 changed one line
These will the earnings that are accumulated during force balance to determine if an adjustment due to rounding is required.
These will be the earnings that are accumulated during force balance to determine if an adjustment due to rounding is required.
At line 234 changed one line
Any computed Force Balance amount is recorded into a separate pay line in the current pay (IPPH).
Any computed Force Balance amount is recorded into a separate pay line in the current pay ([IPPH]).
%%information Force Balancing can now be allowed when there is a Wage, Position, or Job change in a Period, and also when an employee has more than one assignment.
The client must add User field (IMUF) 'VARIABLE RATE' to table P2K_CM_ENTITY_DETAILS. The conditions above will NOT prevent Force Balancing is the UDF contains the value '1'.
* Force Balancing happens in UPTR to ensure that Variable Rate employees receive their full SM/MO Salary in a Pay Period.%%
At line 279 added one line
[SalaryRateMethods_02.jpg]
At line 285 added 2 lines
[SalaryRateMethods_03.jpg]
At line 247 changed one line
%%information Note that the ‘output’ pay component can by any other component (‘Regular Earnings’ in the example below). This provides for flexibility when choosing the pay component that will hold the actual adjustment.%%
%%information Note that the ‘output’ pay component can be any other component. This provides for flexibility when choosing the pay component that will hold the actual adjustment.%%
At line 251 changed 2 lines
%%information Note that all transactions making up part of the employee regular earnings are generated from the scheduled hours, and therefore will be handled perfectly by Retroactive Pay (UPRETRO). Any Force Balance earnings will NOT be taken into consideration during UPRETRO, since generation is simply set to ‘Entered Value’.%%
%%information Note that all transactions making up part of the employee regular earnings are generated from the scheduled hours, and therefore will be handled perfectly by Retroactive Pay ([UPRETRO]). Any Force Balance earnings will NOT be taken into consideration during [UPRETRO], since generation is simply set to ‘Entered Value’.%%
\\ \\
----
At line 256 changed one line
Since the premium is generated from the hours worked multiplied by the variable rate on a daily basis, the generated premium can by wrong due to the mathematics in rounding.
Since the premium is generated from the hours worked multiplied by the variable rate on a daily basis, the generated premium can be wrong due to the mathematics in rounding.
At line 258 changed one line
To deal with this issue, P2K will perform force balancing for variable rate employees when the transactions are brought into payroll (UPTR). This balancing will occur after the last transaction for an employee has been loaded into IPPH. Please note that all transactions for an employee must be in the same execution of UPTR for force balancing to be invoked. UPTR can not be executed more than once for employees using a variable rate.
To deal with this issue, Personality will perform force balancing for variable rate employees when the transactions are brought into payroll ([UPTR]). This balancing will occur after the last transaction for an employee has been loaded into [IPPH].
At line 260 changed one line
It is important to note that the only place that balancing occurs is when the IPTR batches are brought into payroll during the execution of UPTR.
%%information Please note that all transactions for an employee must be in the same execution of [UPTR] for force balancing to be invoked. [UPTR] can not be executed more than once for employees using a variable rate.%%
At line 307 added 2 lines
It is important to note that the only place that balancing occurs is when the [IPTR] batches are brought into payroll during the execution of [UPTR].
At line 272 changed one line
Any computed Force Balance amount is recorded into a separate pay line in the current pay (IPPH). This pay line will have the same pay component as the Cell Point pay component.
Any computed Force Balance amount is recorded into a separate pay line in the current pay ([IPPH]). This pay line will have the same pay component as the Cell Point pay component.
At line 280 changed one line
%%information Note that the output pay component can by any other component (Regular Earnings in the example below). This provides for flexibility when choosing the pay component that will hold the actual adjustment.%%
%%information Note that the output pay component can be any other component. This provides for flexibility when choosing the pay component that will hold the actual adjustment.%%
At line 284 changed one line
The user variable will point to the variance percentage
The user variable will point to the variance percentage.
At line 288 changed 2 lines
%%information Note that all transactions making up part of the employee regular earnings are generated from the scheduled hours, and therefore will be handled perfectly by Retroactive Pay (UPRETRO). Any Force Balance earnings will NOT be taken into consideration during UPRETRO, since generation is simply set to ‘Entered Value’.%%
%%information Note that all transactions making up part of the employee regular earnings are generated from the scheduled hours, and therefore will be handled perfectly by Retroactive Pay ([UPRETRO]). Any Force Balance earnings will NOT be taken into consideration during [UPRETRO], since generation is simply set to ‘Entered Value’.%%
\\ \\
----
At line 291 changed one line
Pay Period premiums are a new feature as of September, 2005 and are designed to replace UPTG premiums. This type of premium is generated naturally from the hours worked in the pay period and is also ‘Force Balanced’ to ensure that the employee gets the exact premium amount when working a full pay period. Pay Period premiums are computed using a variable rate per hour depending on the number of hours that the employee is scheduled to work. If the employee is scheduled to work the entire pay period, the total of premium generated (by day) must equal the value of the Pay Period premium.
Pay Period premiums are a new feature as of September, 2005 and are designed to replace [UPTG] premiums. This type of premium is generated naturally from the hours worked in the pay period and is also ‘Force Balanced’ to ensure that the employee gets the exact premium amount when working a full pay period. Pay Period premiums are computed using a variable rate per hour depending on the number of hours that the employee is scheduled to work. If the employee is scheduled to work the entire pay period, the total of premium generated (by day) must equal the value of the Pay Period premium.
At line 293 changed one line
Since the premium generated from the hours worked are multiplied by the variable rate on a daily basis, the generated premium can by wrong due to the mathematics in rounding.
Since the premium generated from the hours worked are multiplied by the variable rate on a daily basis, the generated premium can be wrong due to the mathematics in rounding.
At line 295 changed 2 lines
To deal with this issue, P2K will perform ‘Force Balancing’ when the transactions are brought into payroll (UPTR). This balancing will occur after the last transaction for an employee has been loaded into IPPH.
%%information Please note that all transactions for an employee must be in the same execution of UPTR for force balancing to be invoked.%%
To deal with this issue, Personality will perform ‘Force Balancing’ when the transactions are brought into payroll ([UPTR]). This balancing will occur after the last transaction for an employee has been loaded into [IPPH].
At line 298 changed one line
It is important to note that the only place that balancing occurs is when the IPTR batches are brought into payroll during the execution of UPTR.
%%information Please note that all transactions for an employee must be in the same execution of [UPTR] for force balancing to be invoked.%%
At line 347 added 2 lines
It is important to note that the only place that balancing occurs is when the [IPTR] batches are brought into payroll during the execution of [UPTR].
At line 310 changed one line
Any computed Force Balance amount is recorded into a separate pay line in the current pay (IPPH ). This pay line will have the same pay component as the Pay Period Premium pay component.
Any computed Force Balance amount is recorded into a separate pay line in the current pay ([IPPH]). This pay line will have the same pay component as the Pay Period Premium pay component.
At line 316 removed one line
At line 319 changed one line
%%information Note that the output pay component can by any other component (Regular Earnings in the example below). This provides for flexibility when choosing the pay component that will hold the actual adjustment.%%
%%information Note that the output pay component can by any other component. This provides for flexibility when choosing the pay component that will hold the actual adjustment.%%
At line 327 changed one line
%%information Note that all transactions making up part of the employee regular earnings are generated from the scheduled hours, and therefore will be handled perfectly by retroactive pay (UPRETRO). Any Force Balance earnings will NOT be taken into consideration during UPRETRO, since generation is simply set to ‘Entered Value’.%%
%%information Note that all transactions making up part of the employee regular earnings are generated from the scheduled hours, and therefore will be handled perfectly by retroactive pay ([UPRETRO]). Any Force Balance earnings will NOT be taken into consideration during [UPRETRO], since generation is simply set to ‘Entered Value’.%%
At line 338 removed 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 341 changed 2 lines
![Discussion|Edit:Internal.SALARY RATE METHODS]
[{InsertPage page='Internal.SALARY RATE METHODS' default='Click to create a new discussion page'}]
![Notes|Edit:Internal.USING SALARY RATE METHODS]
[{InsertPage page='Internal.USING SALARY RATE METHODS' default='Click to create a new notes page'}]
At line 344 removed 3 lines
}]
This page (revision-24) was last changed on 26-Nov-2021 10:22 by kparrottTop