PROCESS PAY TRANSACTIONS#
Processing Information#
The Process Pay Transactions (UPTR) form allows you to process pay transactions according to selection criteria, from IPTR (Pay Transactions) and create pay headers and pay lines. These new pays are then audited (UPAUDT) to prepare them for calculation (UPCALC).The UPTR processes one batch of pay transactions at a time and conditionally updates the Batch Status to 'Processed by UPTR' at the end of the batch.
- Transactions within a batch will be bypassed if the Time Code does not have an associated Pay Component in IDTC and also when the Associated Pay Component is not valid (Based on PCRULES) for the Employee Entity, Unit and Group.
- With the introduction of this Preference UPTR CLEANUP(System_Preference), the User can force UPTR to mark the Batch as ‘Processed by UPTR’.
- If UPTR locates this Preference with a value of ‘Y’, then it will mark the Batch as Processed regardless of any errors located on Transactions in the Batch.
- In addition, ANY Time codes that do NOT have an associated PC need to have the 'Bypass UPTR' toggle turned on (in IDTC) to allow the preference to work properly.
This form creates one batch per run and creates pay headers within that batch or adds to existing pay headers with matching EE, Pay Period and Pay Category.
If the Updating Existing Pays toggle is on, then UPTR will attempt to locate a pay to use before creating a new one.
This form will create pay headers and/or add information to existing pay headers with matching EE, pay period and pay category.
If multiple transaction batches are chosen in one UPTR run, any employees in multiple batches will have one pay header with multiple transactions.
What are the conditions when a UPTR will create a new pay header even if the employee has an existing pay header for the same payroll already?
- Many columns in a Pay Header are used for Taxation requirements as well as determining a ‘Payroll Code’.
- Whether or not a new Pay Header is created is determined by comparing the values in all of the columns and they all must match for the Employee Pay to be considered ‘Existing’.
- The parameter ‘Demographics Source’ will be used to determine which date to use when comparing columns from the employee’s information, which will then determine if changes in the employee’s data will cause a new pay header to be created.
- This determination is done one transaction at a time as the records are processed from IPTR. Theoretically, a separate Pay Header could be created from each Transaction.
- The information that must be identical are;
- Employment Pay Category
- Pay Period
- Group
- School District
- Work State/Province
- Home State/Province
- Work Jurisdiction
- Home Jurisdiction
- Determination on whether a new pay header is to be created will also be impacted by the ‘Prior Period Separate’ toggle setting in UPTR
- The determination of the ‘Group Code’ also depends on the setting in the GROUP_SOURCE column in IDWR
Report Parameters & Filters#
| Report Parameters | |
|---|---|
| Entity | Mandatory, LOV available Limits the process to the entity specified. |
| Pay Calendar | Mandatory, LOV Available The report will be limited to the pay calendars identified in this field. |
| Current Pay Period | Mandatory, LOV Available The report will be limited to the pay periods identified in this field. |
| Demographics Source | Mandatory, Date Source lexicon available This field is used to identify which date to use to get the employee’s information, which will then determine if changes in the employee’s data will cause a new pay header to be created. The values are: 01-Use the Transaction Date 02-Use Pay Period End Date (default value) 03-Use Pay Issue date 04-Use Pay Period Start Date (for use with UPCPAY created pay headers) |
| Pay Issue Period | Optional, LOV Available If this is not entered, the system will derive the IPPH Pay Issue Date from the Pay Transaction with the latest Transaction date. If a Pay Period is entered in this field, the system will use the associated Pay Issue date from the Pay Calendar. |
| Override Batch Code | Optional, Text |
| Pay By | Optional, Pay By lexicon available This field allows you to indicate the payment method |
| Prior Period Separate | Optional,Yes or No Default is No. If set to Yes, then transactions from a prior period will be put into a separate pay header. |
| Create as Eligible | Optional,Yes or No lexicon available Should the pay header batch be created as eligible? |
| Update Existing Pays | Optional,Yes or No lexicon available If a pay header already exists for this pay period and category and is not calculated or closed, should it be updated with the transactions being processed? |
| Bypass if Paid in Period | Optional,Yes or No lexicon available Should the pay header be bypassed if already paid in this period? |
| Exception Level | Optional, Exception Level lexicon available This field defines the exception level (report messages) required. |
| Report Filters | |
|---|---|
| Payroll | Optional, Multiple, and LOV available Multiple payrolls may be selected per execution of this function. |
| Pay Category | Optional, Multiple, and LOV available Users must indicate the category that the batches and pay headers are to be processed under. |
| Batch Number | Optional, Multiple, and LOV available This is the pay transaction batch that is to be processed. |
