Business

User Tools

Site Tools

Trace:
general:moving_11month_employees_cyr_payroll_step15

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_11month_employees_cyr_payroll_step15 [2019/02/13 23:39] – emorenogeneral:moving_11month_employees_cyr_payroll_step15 [2021/01/19 16:17] (current) – emoreno
Line 1: Line 1:
 \\  **<color #ed1c24>Log on to the next year.</color>** \\  **<color #ed1c24>Log on to the next year.</color>**
  
-[[humanresources:utilities:pmis:moveforecasttocyrpositionandpayroll|Human Resources > Utilities > PMIS > Move Forecast to CYR Position and Payroll]]+[[positionmanagement:utilities:moveforecasttocyrpositionandpayroll|Position Management > Utilities > Move Forecast to CYR Position and Payroll]]
  
 This process is used to move payroll and position forecast records to the current year PMIS with the same information that is set up in the next year PMIS records.  This process is used to move payroll and position forecast records to the current year PMIS with the same information that is set up in the next year PMIS records. 
  
-It also updates fields on the Human Resources > Maintenance > Staff Job/Pay Data > Employment Info, Pay Info, Job Info, and Distribution tabs.+It also updates fields on the following Maintenance tabs: Employment Info, Pay Info, Job Info, Distribution 
  
-In order to move position records from forecast to current, the **Accept Changes** field must be cleared; otherwise, position records cannot be moved. The **Accept Changes** field is cleared after running a simulation with the** Update Forecast** field set to //Yes//. Similarly, you cannot run a simulation for positions without the **Accept Changes** field selected.+The **Accept Changes** field must be cleared when moving position records from forecast to current; otherwise, position records cannot be moved. The **Accept Changes** field is cleared after running a simulation with the** Update Forecast** field set to //Yes//. Similarly, you cannot run a simulation for positions without the **Accept Changes** field selected.
  
-{{:academy:business:overview_guide:humanresources:move_forecast_to_cyr_position_and_payroll_11mo.jpg|Move Forecast To CYR Position And Payroll 11 Month Employees}}+{{:general:updatenyrpositionsmoveemployeestocyr_moveforecasttocyrpositionandpayroll.jpg|Move Forecast To CYR Position And Payroll 11 Month Employees}}
  
   * In the** Select Pay Frequency** field, select the payroll frequency to be updated. LEAs with multiple frequencies must individually process each frequency.   * In the** Select Pay Frequency** field, select the payroll frequency to be updated. LEAs with multiple frequencies must individually process each frequency.
   * Do not select **Include Vacant Supplements**.   * Do not select **Include Vacant Supplements**.
-  * Do not select **Validate Accounts against General Ledger** at this time.  Distribution accounts in next year PMIS reflect the fiscal year for the upcoming school year.  Finance still reflects the current year for the fiscal year in the general ledger. **Note** – When running this process, the error report reflects funds for employees who are included in the process.  It is necessary to create the funds with the new fiscal year on the Finance > Tables > Account Codes > Fund tab.  It is NOT necessary to set up codes in the Chart of Accounts.+  * Do not select **Validate Accounts against General Ledger** at this time.  Distribution accounts in next year PMIS reflect the fiscal year for the upcoming school year.  Finance still reflects the current year for the fiscal year in the general ledger. When running this process, the error report reflects funds for employees who are included in the process.  It is necessary to create the funds with the new fiscal year on the Finance > Tables > Account Codes > Fund tab.  It is NOT necessary to set up codes in the Chart of Accounts.
   * Select **Update TRS Year**. If an employee has this field selected but they are now a 10-month employee, the **TRS Year** field is cleared when the 10-month move is processed.   * Select **Update TRS Year**. If an employee has this field selected but they are now a 10-month employee, the **TRS Year** field is cleared when the 10-month move is processed.
-  * Select **Update Workers’ Comp Annual and Remaining Payments** if the LEA expenses workers' compensation in TxEIS. The system looks at the **# of months in Contract** and makes the **WC Ann Pymts** and **WC Remaining Pymts** match this field. +  * Select **Update Workers’ Comp Annual and Remaining Payments** if the LEA expenses worker's compensation in ASCENDER. The system references the** # of months in Contract** and makes the **WC Ann Pymts** and **WC Remaining Pymts** match this field. 
-  * Leave the **Additional Workers’ Comp Payments** field blank. It is not necessary to populate this field even if the LEA expenses workers' compensation in TxEIS. +  * Leave the **Additional Workers’ Comp Payments** field blank. It is not necessary to populate this field even if the LEA expenses workers' compensation in ASCENDER. 
-  * In the **Select a Stat Minimum Salary Table (CYR/NYR)** field, select the year (current or next ) that contains the updated tables. If it is a legislative year and the state minimum amounts are updated. +  * In the **Select a Stat Minimum Salary Table (CYR/NYR)** field, select the year (current or next ) that contains the tables with the updated amounts. If it is a legislative year and the state minimum amounts are updated. 
-  * In the **First Pay Date Codes or blank for ALL** field, select only the first pay date codes for employees who receive their first paycheck in August.+  * In the **First Pay Date Codes or blank for ALL** field, select only the first pay date codes for employees who receive their first paycheck in July.
   * Select **Include Extra Duty** to include the supplement pay with the regular pay.   * Select **Include Extra Duty** to include the supplement pay with the regular pay.
  
  
-{{page>general:humanresources:utilities:pmis:moveforecasttocyrpositionandpayroll:body1}}+VCV Click **Execute** to execute the process. The following reports are available:
  
 +{{:general:updatenyrpositionsmoveemployeestocyr_moveforecasttocyrpositionandpayroll_processingreports.jpg|Move Forecast to CYR Position and Payroll Processing Reports}}
  
-If corrections are processed, repeat this step. +  * Move Forecast Process Error Listing ++Important errors|{{page>general:moveforecasttocurrenterrors&inline}}++  
  
-Generate and save each report. Compare the Update CYR Positions From Forecast report to the user-created report that was previously generated to confirm that all 11-month employees are included. The last two reports contain the same information; one is sorted by employee name and the other by campus ID. These reports reflect the existing salary in the current year payroll and the new salary, which overwrites the current year payroll amounts. Review the reports for accuracy.+<div indent> 
 +{{:general:updatenyrpositionsmoveemployeestocyr_moveforecasttocyrpositionandpayroll_errorreport.jpg|Move Forecast Process Error Report}} 
 +</div> 
 +  * Update CYR Positions From Forecast - The error report lists any funds that need to be set up in the Finance tables.
  
 +<div indent>
 +{{:general:updatenyrpositionsmoveemployeestocyr_updatecyrpositionsfromforecast.jpg|Update CYR Positions From Forecast 
 + Report}}
 +</div>
 +  * Update CYR Payroll From Forecast by Employee Name  
 +<div indent>
 +{{:general:updatenyrpositionsmoveemployeestocyr_updatecurypayrollfromforecastbyempname.jpg|Update CYR Payroll From Forecast by Employee Name Report}}
 +
 +  * Update CYR Payroll From Forecast by Campus ID  
 +<div head3>
 +{{:general:updatenyrpositionsmoveemployeestocyr_updatecyrpayrollfromforecastbycampusid.jpg|Update CYR Payroll From Forecast by Campus ID Report}}
 +</div>
 +
 +VCV Click **Generate Reports**. The selected reports are displayed. [[general:printreport|Review the report.]]
 +
 +
 +VCV Click **Continue** to view the next report. Or, click **Return** to return to the report selection page.
 + 
 +VCV After reviewing all of the reports and correcting all errors, return to the report selection page and click **Process** to move the forecast records to the current year. You are prompted to create a [[general:pmis_updatesalarytables_backup|backup.]]
 +
 +<div indent> After the process is completed, the actual update is performed. If the update is successful, a message is displayed indicating that the move forecast updates were successfully processed.
 +</div>
 +\\ 
 +VCV Click **Cancel** to return to the Move Forecast to CYR Position and Payroll page without moving the forecast records to the current year.
 +
 +
 +
 +If corrections are processed, repeat this step. 
  
 +Generate and save each report. Compare the Update CYR Positions From Forecast report to the user-created report that was previously generated to confirm that all 12-month employees are included. The last two reports contain the same information; one is sorted by employee name and the other by campus ID. These reports reflect the existing salary in the current year payroll and the new salary, which overwrites the current year payroll amounts. Review the reports for accuracy.
general/moving_11month_employees_cyr_payroll_step15.1550101183.txt.gz · Last modified: 2019/02/13 18:39 (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.