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
[{$applicationname}] 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.
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 one line
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 [{$applicationname}] 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 12 changed one line
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 [{$applicationname}] 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 18 changed one line
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]).
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 54 changed one line
!!Variable Rate Hours
!!Variable Rate Hours
At line 61 changed one line
!Example:
Example:\\
At line 66 changed one line
!Example:
Example:\\
At line 72 added 5 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.%%
At line 85 changed 8 lines
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}
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 101 changed one line
!Example:
Example:\\
At line 105 changed one line
Hourly Rate $16.0428 = $3000 / 22 / 8.5\\ \\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.
Hourly Rate $16.0428 = $3000 / 22 / 8.5\\ \\
At line 107 changed one line
!Example:
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:\\
At line 143 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 169 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 192 changed one line
01-Sep-2005 Projected Earnings($2,898.56)
01-Sep-2005 Projected Earnings($2,898.56)\\
At line 211 changed one line
01-Sep-2005 Projected Earnings($2,355.08)
01-Sep-2005 Projected Earnings($2,355.08)\\
At line 235 added one line
__{need screen shot}__\\
At line 238 added one line
__{need screen shot}__\\
At line 243 added one line
[SalaryRateMethods_01.jpg]
At line 245 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 247 changed one line
To be eligible for this force balance, the following conditions must be met.
%%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:
At line 251 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 256 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 271 added 5 lines
%%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 275 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 285 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 287 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 305 added 2 lines
%%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 309 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 313 changed one line
The user variable will point to the variance percentage
The user variable will point to the variance percentage.
At line 323 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 325 changed one line
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].
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 346 removed one line
At line 349 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 368 removed 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 371 changed 2 lines
![Discussion|Edit:Internal.USING SALARY RATE METHODS]
[{InsertPage page='Internal.USING 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 374 removed 3 lines
}]
This page (revision-24) was last changed on 26-Nov-2021 10:22 by kparrottTop