This page (revision-4) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
4 26-Nov-2021 10:22 3 KB kparrott to previous
3 26-Nov-2021 10:22 4 KB JEscott to previous | to last
2 26-Nov-2021 10:22 4 KB JEscott to previous | to last
1 26-Nov-2021 10:22 4 KB JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 4 changed one line
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 [{$applicationname}] system.
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 Personality system.
At line 10 changed one line
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’).
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’).