JOURNALIZE LABOR (PRE-PAYROLL)#

Processing Information#

Labor costs may be sent to the G/L system on a regular (daily, weekly, bi weekly etc.) or ‘on demand’ basis prior to the pay being calculated. Labor G/L processing (UPLG) takes place after the payroll batch has been entered into Wiki system.

The payroll batch can be generated by UPTR (from pay transactions), UPTG (system generated) or manually entered on the IPPH form. Labor G/L can process payroll batches that have been audited by the UPAUDT process or to optionally include un-audited pay lines to obtain labor costs on a timely basis.

For testing the G/L set up and balancing, it is recommended that Labor G/L be processed for one batch at a time.

For testing the G/L set up and balancing, it is recommended that Labor G/L be processed for one batch at a time. Labor G/L may take place prior to auditing a batch (set the Include Unaudited Transactions lexicon to ‘Yes’) and Labor G/L may be run in update or trial mode (set the Trial lexicon to ‘Yes’).

If Labor G/L is run in trial mode (in order to check the results) and the G/L Interface (UPGLF) is run in update mode, the journal entries will be updated to permanent journal entries.

On the IDGA form, the G/L account must have the ‘Pre Payroll’ toggle on in order to be processed by Labor G/L. Labor G/L does not balance Gross to Net and Deductions. The earnings that are to be journalized will be balanced against the G/L Account that has been set up with the Labor Clearing account usage in the G/L Accounts (IDGA) form.

The process for running Labor G/L is as follows:

  • UPAUDT
    • to audit transactions to be journalized
  • UPLG
    • in Trial or Update mode
  • RPGL
    • to view results of UPLG
  • UPGLF
    • to create the interface file
    • when run in Trial, use to test results
    • when run in non-Trial if UPLG is not run in Trial mode, use to commit journal entries and mark the Pay Lines as ‘Journalized'

Report Parameters & Filters#

Report Parameters
GL Company CodeMandatory, LOV Available
General Ledger Company that the pays must be journalized for. As set up in the
IDGC form. Only one G/L company may be processed at a time.
Batch EligibleOptional, LOV Available, <Both>
Transactions may be processed for batches that are marked eligible, not eligible or
both.
Person CodeOptional, LOV Available
You may specify one or more employees for processing.
As OfMandatory, Date, LOV Available
The date up to which the transactions are to be journalized. This date is used to pick
up all pay headers with a pay period end date up to and including this date. Then
the pay lines are picked up if the pay line date is up to and including this date.
Include Unaudited
Transactions
Optional, Toggle
If ‘On’, all pay lines including audited and un-audited transactions will be processed.
This should be used if you have a large volume for UPLG and time does not permit
UPAUDT to run prior to UPLG.
If ‘Off’, only audited pay line will be processed.
TrialOptional, Toggle
If ‘On’, the journal entries will be created with Journal Source = ‘Trial Labor G/L’.
This allows RPGL report to print for verification and UPLG may be run again.
If ‘Off’, the journal entries will be created with Journal Source = ‘Labor G/L’ and it
cannot be removed unless the UPLGUNDO process is run.
Exception LevelMandatory, LOV Available
You may increase the level of exception to user or utility levels for testing purposes
only.

Report Filters
EntityOptional and LOV Available
Limits the process to the entity specified. You should select only one entity.
PayrollOptional and LOV Available
The payroll code of the pays to be journalized. You should select only one payroll
code.
Batch NumberOptional, Multiple, and LOV Available
Batch numbers for the specified entity and payroll are displayed on this list. You
may select multiple batches.
Person CodeOptional, LOV Available
You may specify one or more employees for processing.


Notes #

Click to create a new notes page