Docstoc

Salary Increase Calculations

Document Sample
Salary Increase Calculations Powered By Docstoc
					                      Compensation Workbench v3.0 Advisory
                                –        Issue Date: November 2008

The following issues have been identified in the CWB v3.0. Issues #1 and #2 do not affect the
individual ratings, shares, or payouts calculated in the CWB, or overall pay pool deliberations and
upload process. No further action is required for these issues. Most pay pools will not
encounter issues #3, #4, or #5. If you do, just import your data into CWB v3.1 to complete the pay
pool process. The updated version of the CWB (version 3.1) that corrects all these issues is available
on the NSPS Readiness Tool. Instructions for moving data from v3.0 to v3.1 are included at the
end of this advisory.


Issue #1 – Max salary increase split (%) column formula error
The formula in column AH (Max Salary Increase Split %) does not take into account the salary
increase the employee receives as a rate range adjustment and therefore the resulting maximum
increase split % displayed in AH is high. This calculation error is typically only noticeable if an
employee is near the top of his/her pay band and therefore cannot receive the entire payout as a
salary increase. For example, in the below CWB screen shows that Kevin Bularz (row 30) can
receive 27.45% of his payout as a salary increase. However, when 27.4% is entered into column AG
Kevin hits the maximum of the pay band. Kevin can actually only receive 13.56% of his payout as a
salary increase.
Any funds intended to be given as a salary increase, but can not because of a pay cap (control point
or pay band maximum) are automatically carried over to the bonus. The formula in column AH is
correct in CWB v3.1.




                                                                                                       1
Issue #2 – Objective form crashes if a non-rated employee’s row is hidden
The objective form will crash when you double click a row in the pay pool panel worksheet if an
employee’s row is hidden who was not rated in the CWB (column O = “No”). For example, if you
change an employee’s value in column O (Rated?) to “No,” and then hide the employee using the
hide row feature, when you double click on another employee’s row to open up the objective form
you receive the error below. To get around this error in v.3.0 simply select End when you receive
the Run-time error popup, and then unhide the hidden employee. This problem is corrected in
CWB v3.1.




                                                                                                    2
Issue #3 – Validation, statistics error, and disconnects between worksheets occur
if a row is hidden and then rows are deleted that span the hidden row
If you hide an employee’s row, and then subsequently delete rows on both sides of the hidden
employee several errors may occur in your CWB. This issue will become apparent to you if you see
#N/A in any columns in your CWB, in particular in the summary and statistics worksheets. If you
do delete employees from a CWB, simply delete one employee at a time and do not have any rows
hidden and this problem will not occur. This problem is corrected in CWB v3.1. If you encounter
this error, you should import your data into the CWB v3.1. to complete the pay pool process.
Double check your data in the new CWB to make sure everything came over correctly.




                                                                                                   3
Issue #4 – Validation error in first and last row of pay pool panel worksheet
If you click in cell O12 and then hide row 12, you will get a shares validation circle in row 12 when
you validate. If you click in cell below the last employee in your pay pool in column O and then
hide that row, you will get a shares validation circle in that when you validate. This problem is
corrected in CWB v3.1. If you encounter this error, you should import your data into the CWB
v3.1. to complete the pay pool process.




                                                                                                        4
Issue #5 – Rate range adjustment and performance-salary increase calculations for
retained pay employees
A retained pay flag (column N) comes down with the CWB extract data and is used in the CWB to
determine an employee’s eligibility for a performance-based salary increase in the CWB. CWB v3.0
does not correctly handle an employee who is on retained pay based on the 2008 pay band
maximum (column N = Yes), but comes off retained pay because of the increase to the maximum
of the pay band for 2009.
If an employee on retained pay (column N = Yes) has a base salary that is greater than or equal to
the new maximum for the pay band (colum AQ), then the CWB automatically distributes any
performance payout as bonus. In addition, the entire salary increase section is grayed out. An
employee in this situation is eligible to receive a salary increase in accordance with 5 CFR
9901.323(a)(1), but this increase is handled outside of the CWB. An example of this scenario is
shown below in row 14 – Kris Ballam. This situation is correctly handled in v3.0.
If an employee on retained pay (column N = Yes) has a base salary that is less than the new
maximum for the pay band, the CWB v3.0 does not correctly calculate the appropriate rate range
increase and performance salary increase. In v3.0, the rate range adjustment (column AD) and salary
increase columns (AF and AG) are zeroed out and locked. An example of this scenario is shown
below in row 13 – Caryn Armbruster. This problem is corrected in CWB v3.1. If you encounter
this situation, you should import your data into the CWB v3.1. to complete the pay pool process.




                                                                                                     5
How do I get my existing CWB data into the new CWB Version 3.1?
To move your data from your existing CWB to the new version, follow the steps below carefully.


Step 1 – Save a new (empty) CWB Version 3.1 in the same folder as your existing CWB. Rename it
          so that you can identify it.
Step 2 – Open the new CWB Version 3.1 and select Enable Macros.
Step 3 – Select the Import button on the custom menu bar.
Step 4 – In Step 1 of the import form, select pay pool data from sub-panel spreadsheet(s); then
          select continue.
Step 5 – Select the name of your existing CWB and select open. (The spreadsheet then imports your
         employees – select “Yes” when you are asked about the CWB version numbers).
Step 6 – Select "Yes" when you receive a confirmation saying “Data successfully imported. Would
         you like to save the spreadsheet?”
Step 7 – Enter your pay pool funding for Elements 1 and 3 in the Funding worksheet.
Step 8 – Validate that you have all your employees in the CWB and that all the ratings, shares, and
         payouts are accurate.


You are now ready to use the CWB Version 3.1 to support your pay pool panel meetings.
Note: Individual employees’ control point values contained in column AN of the Pay Pool Panel
worksheet will be imported into your new CWB. However, the control points values set by pay
schedule/band in the Control Points worksheet will not be imported. Therefore, you will have to
re-enter or copy and paste the values from your old CWB into the new CWB.




                                                                                                      6

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:30
posted:7/22/2011
language:English
pages:6
Description: Salary Increase Calculations document sample