GENERATE PAY TRANSACTIONS
Back to current versionRestore this version


Generation of batches of pay transactions is done for:

The Generate Pay Transactions (UPTG) form is used to create pay transactions for a selected number of employees based on their work rule definition.

The Enter Pay Transactions (IPTR) form is used to modify transactions already generated and to add new transactions with a minimum of data entry.

The Process Pay Transactions (UPTR) form is used to create batches, pay headers, and pay lines from transactions generated or entered though IPTR.

All transaction generation is based on work rules previously set up.

All HR changes that will affect the current payroll MUST be made prior to UPTG.

Generated pay transactions may be batched by department, department batch code, authorization area, location, or payroll (all in a single batch).

Generation is not done for “completed” or “cancelled” assignments.

Pay Type must be identified as “Salary” or “Hourly” - no generation is done for “Commission”.

Prior leaves will not be processed by UPTG. The UPPAL process must be run to pick up prior leaves. The prior leave date prompt has been removed from the UPTG program.

The 'Allow Duplicates' parameter has been removed from UPTG. The UPTG program has been updated to now process in the following manner:

Multiple runs of UPTG are allowed including runs for time only or salary only and for the purpose of picking up new hires.

New parameter added to UPTG 'Rate Method for Salary'. This is an option on UPTG for salary generation to allow clients to choose which way they want to compute the hourly rate that will be used for special situations. A special situation may be an employee starts or terminates part way through the pay period or has a pay increase part way through the pay period and their salary needs to be calculated. The options available for the parameter 'Rate Method for Salary' are:


Daily Time Generation#


Weekly/Period Time Generation#

If the Time Generation Rule is “By Week with Time”, “By Week w/o Time”, “By Period with Time” or “By Period w/o Time”, summary pay transactions will be created by week or pay period with the following exceptions:

Salary Generation#

If a Salary $ Time Code is specified, salary earnings will be generated on the last day of the qualifying time frame with the following exceptions:

When UPTG is requested to generate 'SALARY' in addition to 'HOURS' the FTE is not considered when computing the Period Earnings. UPTG looks at either the actual Work Calendar or Standard Hours depending on the method selected in the 'Rate Method for Salary' Report Parameter.

Once UPTG has the 'Actual' hours worked, the salary is calculated by taking their Full Time Hourly wage and multiplying it be the hours worked.

For Part Time employees, the scheduled or standard hours should be less than that worked by a Full time Employee.


Rate and Shift Premium Generation#

The rate on each pay transaction defaults to the rate defined on the assignment detail that is effective on the transaction date.

Leave Bank Balance Checking#

After all transactions for the qualifying time frame have been generated, a second pass is done to handle leaves that are governed by leave policies.

The system checks if the employee is able to take time with the time code, by checking the Leave Schedule (IALS). If a schedule exists that matches the employee’s person code, group, unit, or entity, the system will ensure that employees have enough time available in their bank, taking into consideration all leaves taken to date.

Leave bank balance checking is done in accordance with the leave policies.

If there is not enough time left in the bank and if leave cascade records exist on IALP, the cascade banks are checked and additional time codes are generated as appropriate to cover the time.

If there is still not enough time and the Time Warn Rule field on IALP indicates “Error, don’t allow”, the leave time is generated using the “LWOP Time Code” specified on the policy.

Exception messages are generated for all leave bank excesses.


Transactions#

The pay transaction 'Schedule Time' field (on IPTR) will only be populated if the work rule 'Regular Time Code' on the work rule (IDWR) has the 'Adjust Scheduled Time' toggle (on IDTC) turned on.

Nothing will be done to force balance time of the 'Schedule Time' field if it is empty, even if other time codes have the 'Adjust Scheduled Time' toggle on.

If the 'Schedule Time' and a time code have the 'Adjust Scheduled Time' toggle on, the 'Regular Time Code' hours will be reduced by the time exception.


Regenerating the Timesheet Details#

This will be done when assignment details change as follows:

Triggers:

  1. position is changed
  2. job is changed
  3. department is changed
  4. work rule is changed
  5. work calendar is changed
  6. hours per day is changed
  7. employment status is changed
  8. FTE is changed
  9. effective date is changed
  10. effective record is deleted

Rules: In general, regeneration occurs on any open timesheet for that EE with following exceptions:

  1. if there are more than 5 open timesheet the none of the timesheet will be regenerated
  2. if the timesheet is generated by assignment than we skip any open timesheet for other assignments
  3. we regenerate only the open timesheets for the changed assignment

The above process to rebuild the details will take place only the new preference 'EAS CHNG REBLD T" is set to YES - see detail description on IMPF, SYSTEM PREFERENCE


Notes #

Click to create a new notes page