This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| humanresources:utilities:teamsubmission:datamaintenance:employeedataed:ed40contrandpos [2017/12/12 17:11] – emoreno | humanresources:utilities:teamsubmission:datamaintenance:employeedataed:ed40contrandpos [2020/08/11 17:21] (current) – removed emoreno | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======ED40 (Contract and Position) - HRS3900====== | ||
| - | |||
| - | <div # | ||
| - | |||
| - | //**Human Resources > Utilities > TEAM Submission > Data Maintenance > Employee Data (ED) > ED40 (Contr and Pos)**// | ||
| - | |||
| - | <WRAP round intro> | ||
| - | |||
| - | * The July record type 40 reports all employees who have a contract or work agreement beginning in July. It lists the amount of their July salary that belongs to the new year. The salary listed represents payment number one for the new year. If no salary is to be moved to the new year, there is no salary to report; therefore, the salary positions for July must be all zeros. | ||
| - | * The August record type 40 reports all employees who have a contract or work agreement beginning in August. It lists the amount of their August salary, if any, that belongs to the new year. The salary listed represents payment number one for the new year. If no salary is to be moved to the new year, there is no salary to report; therefore, the salary positions for August must be all zeros. | ||
| - | * The July and August record type 40 may contain a combination of July and August contracts and work agreements. These two months affect the employee’s annual statement because they are notice to TRS of money that needs to be moved to the new year. Therefore, these records must be submitted before TRS begins year-end processing. The employee annual statements are generated as a part of year-end processing. | ||
| - | * The September record type 40 reports all employee' | ||
| - | |||
| - | Multiple ED40 records should be submitted for an employee with multiple jobs. If the various jobs fall within the same position code, then only one record should be submitted per position code. In that scenario, the ED40 records should include the employee' | ||
| - | |||
| - | Click here to access the TEAM Report Formatting Guide - ISDs, Charters, and ESCs for additional reporting information and complete file record layouts. | ||
| - | |||
| - | This tab consists of a grid at the top and a free-form area at the bottom. | ||
| - | </ | ||
| - | |||
| - | |||
| - | ====Create an ED40 contract and position record:==== | ||
| - | |||
| - | ++++Select a student | {{page> | ||
| - | |||
| - | |||
| - | ^ Field ^ Description | ||
| - | ^Campus ID|++|{{page> | ||
| - | ^ Pass/ | ||
| - | |||
| - | Click **Save**.< | ||
| - | |||
| - | |||
| - | ====Other functions and features: | ||
| - | |||
| - | ^{{: | ||
| - | |||
| - | |||
| - | |||
| - | {{indexmenu_n> | ||
| - | |||
| - | |||
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.