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 28 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 30 added 2 lines
%%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 41 changed one line
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 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 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 71 changed 2 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].
!!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 76 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 82 changed 4 lines
!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.
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 94 changed 5 lines
!Example:
22 Scheduled Shifts
Standard hours (From [IEAS]) = 8.5
Monthly Salary of $3,000
Hourly Rate $16.0428 = $3000 / 22 / 8.5
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 100 changed 7 lines
!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
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\\
At line 136 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 162 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 185 changed one line
01-Sep-2005 Projected Earnings($2,898.56)
01-Sep-2005 Projected Earnings($2,898.56)\\
At line 204 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 238 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 240 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 244 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 249 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 268 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 278 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 280 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 302 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 306 changed one line
The user variable will point to the variance percentage
The user variable will point to the variance percentage.
At line 316 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 318 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 339 removed one line
At line 342 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 361 removed 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 364 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 367 removed 3 lines
}]
This page (revision-24) was last changed on 26-Nov-2021 10:22 by kparrottTop