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).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.
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. |
| 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 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. |
