Timesheet entry provides users the ability to enter all manual payroll transactions. Transactions may be entered against jobs, job cards or plant items.
Also, if the productivity module is active, the related transactions are reported in that module.
To make timesheet entries:Fields in the Time Sheet Entry Screen
This table provides the description for the fields in the Time Sheet Entry screen.
| Field | Description |
|---|---|
Entry Start Date |
Enter the date when the first transaction for an employee was entered. If you enter timesheets once a week and itemise them daily, this is the date of the first day of that week. |
Employee | Enter a valid employee number or '?' to scan a list of valid employee numbers. When a valid employee number is entered, the previous unprocessed transactions for that employee are displayed. |
Payslip | This field indicates the payslip where the transactions will be printed. If there is an entry in this field, it indicates that the transaction will be printed in a separate payslip. All the transactions with the same payslip flag value will be printed in the same payslip. |
Dkt | If you use docket numbers in your timesheets enter your docket number in this field. This field keeps the information of the previous entry to simplify the data entry process. |
Date | Enter the transaction date in this field. This date is used for RDO calculations and leave history. For the first entry the date will default to the date in the Entry Start Date, which you may change. Subsequent entries will default to the date of the previous transaction to simplify the data entry process. |
Tran Code | Enter the transaction code in this field. |
Hours/Occur | Enter the number of hours or occurrences for the transaction in this field (eg. normal hours, overtime, number of times an allowance is paid). |
Job/Asset | If Job/JC is "J", then enter a valid job number or select the search icon to view available job numbers. |
Job | Enter "J" to allocate the timesheet to a job, "A" to assign it to an asset or plant item or leave it blank it blank to code time to an overhead account. |
Cost Code/Item | If the Job /JC field is a "J" (job costing) then enter a valid cost code or work order number for the job in this field. If Job/JC is "A", then enter a valid plant item number. |
CT | If the Job/JC field is a "J" (job costing) then enter a valid cost type for the job and cost code or work order number. If the Job/JC field is a "A", then enter a valid cost type for the plant number. If the Job/JC field was a blank then leave this field blank. |
Resource | If resource or activity codes are used then enter a valid resource code if Job/JC is a "J". Otherwise, leave it blank. |
Prod Code | Enter a valid productivity code if you are using the productivity module (ie. the second character of the PAYROL System Parameter is 'Y'). |
Plant/Lab | If parameter "PLTSHT" is set to 'Y', enter a valid plant number when coding time to a plant. Otherwise, leave it blank, as this indicates the transaction is labour related. |
Rate Code | Enter a valid pay rate code if the pay rate to be used is different to the one assigned to the employee in the employee master record. |
Rate | If the system parameter "TSHENT" at position 3 is set to Y, the rate field becomes editable. Entering a value in this field will override the default rate specified in the employee master. If the Rate field is greyed out or left blank, and the rate code column is also blank, the system will use the rate from the employee master file or if a default pay rate code is configured, the rate is associated with that code. However, if the system parameter EPROVR is set to "Y", the system will always use the employee's pay rate from the master file, regardless of any default pay rate code defined. |
Amount | Enter the transaction amount for those transactions that cannot accept hours or occurrences (eg. Adjustments, Deductions). |
Wkid | Enter the work ID if the timesheet is allocated to a different work ID, triggering an intercompany charge. |
GL Account | Enter a GL Account when the transaction is to affect the GL account alone and not the jobs or plants. If jobs or plants are used then allow the default GL account. |
