Wage History Table
What is the Wage History Table and How is it Used?
MSPCFO uses the payroll cost (hourly rate) information available from your PSA. If you do not provide cost for members in your PSA or if you would like to override the PSA values, you can add them in MSPCFO by using the Wage History Table under the Payroll tab. The values you enter in the Wage History Table are then used to propagate the Hourly Rates Report. The Payroll tab is only visible to an Administrative Level User.
Why use the Wage History Table?
1. No salaries are kept in the PSA.
2. Salaries are not correct in the PSA.
3. Currently there is a good salary for an engineer, but historically there is a gap when the salary was missing or incorrect.
Why would you use the Wage History Table going forward?
1. Keeping salaries in MSPCFO:
You may not want to keep salaries in your PSA: You can keep the salaries in MSPCFO both historically and going forward. If there is no end date in the salary records for an engineer in MSPCFO, the salary for an engineer will continue to be populated from the Wage History Table.
2. Filling a gap:
If the objective is only to correct historic costs and there is currently a good cost in the PSA, the MSPCFO salary will only fill a gap when the salary in the PSA was not correct. In this case, an end date is added to the salary wage history record and the program will use the PSA salary after this date. (If there are multiple records for the same engineer (change in salary, changing hourly to monthly, etc.), only the last record for the engineer should have an end date.)
The Payroll/Hourly Cost table is ONLY populated for members who have salary information in MSPCFO.. If salaries are included in your PSA only, there are no values in the Hourly Cost table.
Using the Wage History Table
Click on "Payroll" button and then "Wage History" button.
The Wage History Table contains:
1. Member ID - the member username
2. Date Change - the first date that the salary takes effect
3. Ended At - The date when salary reverts back to the PSA (This field is only used if you want to stop using the MSPCFO salary for this person and switch back to your PSA salary).
4. Monthly Salary OR
5. Hourly Rate
For 4. and 5 above or if using an hourly cost in your PSA: MSPCFO suggests that you include all costs that would disappear if the employee was no longer in employment (the burdened rate). For example, include payroll taxes, benefits, etc. Do not incude overhead to the company (rent, marketing, legal, etc.).
How much salary history is needed?
Salaries can be entered back to the beginning of your data history ( usually three years of data plus the current year).
If you are only looking at the last two years for reporting, you do not have to go back that far with salary history.
How to edit the Salary Table
A record can be Added, Edited, or Deleted
ADD A RECORD:
You can add a member salary by using the filters.
1. Member - A list of your members by memberID will be shown to pick from.
2. Date change (yyyy-mm-dd) - First month the cost will be used.
3. Ended at (yyyy-mm-dd) - ONLY put in an ended-at date if you want to use your PSA salaries going forward. If any record has an edned at date, no other record for this member will be used for another change. If you are going to keep salaries in MSPCFO only, never use an end-at date.
Note: You do not have to put an ended-at date in MSPCFO if the member leaves your company. There will be no additional time records for this person.
4. Monthly Salary - The value should have no monetary designation ($, £, etc.). No commas. Only a decimal point can be used with the amount.
5. Hourly Cost - The value should have no monetary designation ($, £, etc.). No commas. Only a decimal point can be used with the amount.
Note: On each line of salary information, only use monthly Salary OR Hourly Salary. A single line should only have one type of salary. For the same person who has multiple lines (salary has changed over time), you can change from hourly to monthly or visa versa as long as they are on separate lines.
When finished with the information for a single line of salary information, make sure you click "Save Wage History" A green message at the top right will indicate that the line is saved.
Member whose salary changes
An additional line is needed for each salary change for a member. For example for Member 191 the first record starts in January, 2022; then the person got a raise in April, 2023. The first salary remains as a monthly salary fromJanuary, 2022 until March, 2023. Then the second salary will start on April, 2023.
If a member leaves the company, you do not have to remove the salary records. There will not be any time entries against these records. You do not want to delete a member who is not currently with the company but may have been at the company during the time span of your reporting. If you delete the person from the file, the person will have an incorrect cost when doing work in this time frame.
Use Prefilled Wage Histories
When would the prefilled history be used?
If there is a good salary in the PSA currently, but a salary gap in the past, you can fill the gap with the pre-fill for the engineer. The pre-fill will show you the latest hourly cost which you can use to fill a gap.
For example in the Wage History table Member 334 has a salary override in the table that starts in June, 2023 and is ongoing in MSPCFO (no end date to go back to the PSA). The salary was entered as $43/hr. Time was found in the PSA going back to May, 2023. Just click the "Create" on the prefill to include the extra month when the member was putting in time.
In the case of Member 317, there is no override for wages in MSPCFO, but Member 317 put in time from Sept, 2022 until February, 2023 without a salary in the PSA. There is currently a salary of $38/hr. This salary can be used to fill the gap by just clicking on the "Create".
0 Comments
Add your comment