The template for Q4 salary increase reporting is attached to this email. Modest changes have been made to it – largely instructional – including:
- Updated Guidelines Tab
- Updated nomenclature, specifically to differentiate between old and new values. “June 30” information relates to information as it appeared on June 30, 2018. “Prior” values include values immediately preceding the action at hand. “New” values are the final values that exist following the action you’re reporting. Thus, the stages of salaries would be the June 30 Salary, the Prior Salary, and the New Salary.
- We eliminated the 1-time bonus column. No EHRA ARP values should be reported this late in the year.
In addition to the notes above, we caution you to remember a few important considerations:
- APPOINTMENT CHANGES. All salaries should be figured at the same appointment period. You should not, in other words, report a 9-month Prior Salary and a 12-month New Salary. Without annualizing the 9-month salary, your total increase will appear enormous, and you risk significantly over-reporting your quarterly numbers. This could impact future external reports, including those that affect budget or budgetary matters. In situation like this, you should make an effort to annualize the 9-month Prior Salary into its 12-month equivalent, so that it’s comparison to a 12-month new salary is proportionate. This is not a new requirement — just a reminder to what we’ve always expected.
- STRICT FTE or APPOINTMENT CHANGES. If the salary increase is caused strictly by an appointment conversion or FTE change – and there are no additional changes to the total rate of pay – you should not be reporting the change. Only report actual changes to rate of pay.
- EHRA TEMPORARY SALARIES. You should NOT be reporting temporary EHRA salary adjustments.
- DO NOT OVERRIDE CALCULATED FIELDS. Columns AH-AM are pre-calculated fields. Do NOT override them. Any data that you manually type in these fields will be lost. The cells only exist as a point of reference for you. When we review your data, we will perform new calculations based on the raw data you enter in Columns Q through AA.
If you’d like to discuss any of the above, please call me directly. Again, I stress that these are long-standing expectations. We’ve found that inconsistent application of them, however, lead to discrepancies on reporting. (For instance, items will appear large enough that they should have been pre-approved by the System Office or the Board of Governors, when in fact there was only an appointment conversion error.)
Final spreadsheets are due on August 16, 2019. Please email them directly to my attention.
Sent from Keith Dupuis