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

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
12 26-Nov-2021 10:22 11 KB JEscott to previous
11 26-Nov-2021 10:22 10 KB JEscott to previous | to last
10 26-Nov-2021 10:22 10 KB JEscott to previous | to last
9 26-Nov-2021 10:22 10 KB JEscott to previous | to last
8 26-Nov-2021 10:22 10 KB JEscott to previous | to last
7 26-Nov-2021 10:22 6 KB JEscott to previous | to last
6 26-Nov-2021 10:22 5 KB JEscott to previous | to last
5 26-Nov-2021 10:22 5 KB JEscott to previous | to last
4 26-Nov-2021 10:22 5 KB JEscott to previous | to last
3 26-Nov-2021 10:22 5 KB JEscott to previous | to last
2 26-Nov-2021 10:22 5 KB JEscott to previous | to last
1 26-Nov-2021 10:22 368 bytes JEscott to last

Page References

Incoming links Outgoing links
GENERAL LEDGER
GENERAL LEDGER

Version management

Difference between version and

At line 4 changed one line
If a General Ledger Interface is going to be used between Personality and your general ledger system, then there are several forms and concepts that must be completed and reviewed.
If a General Ledger Interface is going to be used between [{$applicationname}] and your general ledger system, then there are several forms and concepts that must be completed and reviewed.
At line 20 changed one line
It is possible for Personality to ‘validate’ each segment of the distribution code defined in the G/L company. The G/L Segments ([IDGS]) form is used to enter all the segments you wish to validate. Once these segments have been defined, the Application will validate the distribution code via the Distribution Editor button for any forms that invoke this Distribution Editor, for example [IDDP] and [IDJB].
It is possible for [{$applicationname}] to ‘validate’ each segment of the distribution code defined in the G/L company. The G/L Segments ([IDGS]) form is used to enter all the segments you wish to validate. Once these segments have been defined, the Application will validate the distribution code via the Distribution Editor button for any forms that invoke this Distribution Editor, for example [IDDP] and [IDJB].
At line 64 removed one line
The [RPTR] function may be run to review pay transaction journal entries. These 'Trial Pay Tran G/L' journal entries will be removed by the [UPTR] process when the pay transactions are turned into Pay Headers pay lines. At that time, the actual cost of these pay lines will be journalized by [UPLG] or [UPGL] processes during the pay cycle.
At line 66 removed 2 lines
After [UPGLPTR] is run, the [RPGL] report may be run with the [MEX_ID] from [UPGLPTR].
At line 77 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 the Personality 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 the [{$applicationname}] system.
At line 140 removed 5 lines
----
![Notes|Edit:Internal.GENERAL+LEDGER]
[{InsertPage page='Internal.GENERAL+LEDGER' default='Click to create a new notes page'}]
This page (revision-12) was last changed on 26-Nov-2021 10:22 by JEscottTop