Business

User Tools

Site Tools

Trace: • pmissetup_step1 • moving_10month_employees_cyr_payroll_step9 • pmis_roll_cy_tablesemployees_to_ny_payroll • moving_12month_employees_cyr_payroll_step16 • moving_12month_employees_cyr_payroll_step4
general:moving_12month_employees_cyr_payroll_step5

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
general:moving_12month_employees_cyr_payroll_step5 [2020/12/15 20:36] – emorenogeneral:moving_12month_employees_cyr_payroll_step5 [2021/11/29 20:39] (current) – emoreno
Line 6: Line 6:
 [[positionmanagement:utilities:salarysimulation:simulationoptions|Position Management > Utilities > Salary Simulation > Simulation Options]]  [[positionmanagement:utilities:salarysimulation:simulationoptions|Position Management > Utilities > Salary Simulation > Simulation Options]] 
  
-{{:general:updatenyrpositionsmoveemployeestocyr_salarysimulation12moemployee.jpg|PMIS Salary Simulation For 12 Month Employees}}+{{:general:updatenyrpositionsmoveemployeestocyr_salarysimulation12moemployee.jpg|PMIS Salary Simulation}}
  
 VCV Complete the following: VCV Complete the following:
Line 13: Line 13:
   * In the **Update Forecast** field, select //No//.     * In the **Update Forecast** field, select //No//.  
   * In the **Update Budget** field, select //N - Do Not Update Budget//.   * In the **Update Budget** field, select //N - Do Not Update Budget//.
-  * Include all first pay date codes for 12-month employees who receive their first paycheck in August. Include all local/annual, hourly/daily, midpoint (if applicable), and extra duty tables. +  * Include all first pay date codes for 12-month employees who receive their first paycheck in July. Include all local/annual, hourly/daily, midpoint (if applicable), and extra duty tables. 
   * If increases are not provided to 12-month employees in July, do not include an increase in the salary tables. If increases are provided to 12-month employees in July, update the salary tables with the increase data.   * If increases are not provided to 12-month employees in July, do not include an increase in the salary tables. If increases are provided to 12-month employees in July, update the salary tables with the increase data.
   * If the LEA decides to interface the simulation to Budget, add the deductions with the annual amount for the Employer Contribution.   * If the LEA decides to interface the simulation to Budget, add the deductions with the annual amount for the Employer Contribution.
-  +\\  
 VCV Click **Save**.  VCV Click **Save**. 
-\\ 
-<WRAP Box> 
-**Note**: Review the **Exp 373** field on the Extra Duty tab. If the table was changed (e.g., the **Exp 373** field is selected, but it was not selected last year), it is important that the current selection matches the Distribution tab for the supplement position in order to avoid errors.  
-</WRAP> 
- 
-{{:general:updatenyrpositionsmoveemployeestocyr_exp373.jpg|Extra Duty Tab With Expense 373}} 
- 
-{{:general:updatenyrpositionsmoveemployeestocyr_distributionexp373.jpg|Distribution Tab With Expense 373}} 
- 
-A user-created report is helpful to verify this information. Compare the report to the data on the [[personnel:tables:salaries:extraduty|Personnel > Tables > Salaries > Extra Duty]] tab.  
- 
  
 VCV Click **Execute**. Review the Simulation Process Error Listing and correct any errors prior to continuing the process.  VCV Click **Execute**. Review the Simulation Process Error Listing and correct any errors prior to continuing the process. 
general/moving_12month_employees_cyr_payroll_step5.1608064602.txt.gz · Last modified: 2020/12/15 15:36 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International

Americans with Disabilities Act (ADA) and Web Accessibility

The Texas Computer Cooperative (TCC) is committed to making its websites accessible to all users. It is TCC policy to ensure that new and updated content complies with Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. We welcome comments and suggestions to improve the accessibility of our websites. If the format of any material on our website interferes with your ability to access the information, use this form to leave a comment about the accessibility of our website.