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

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

Page References

Incoming links Outgoing links
IDGA
IDGA

Version management

Difference between version and

At line 15 changed one line
;Account Usage:Indicates the purpose of the account, for example, as an expense, liability, clearing or other special type of account.
;Account Usage:Indicates the purpose of the account, for example, as an expense, liability, clearing or other special type of account. Account_Usage is an optional fixed lexicon ([X_ACCOUNT_USAGE]).
At line 36 added 39 lines
|Cash G/L Account 0201|
|Deposit G/L Account\\0202|
|Check G/L Account 0203|
;Posting Date Method:The Posting Date method controls the accounting period to which general ledger entries are to be attributed and by default, entries for a pay period are allocated based on the type of payment. Post all entries based on the ‘Pay Period End Date’ or the ‘Pay Issue Date’, or post by the ‘Derive Fiscal’ (most commonly used) method.
;:For the Derive Fiscal method, all pay line transactions use the Pay Line Start date to determine the fiscal period. All internally generated amounts are posted by the Pay Issue date’s fiscal period.
;:''For example, a pay period ending on the 28th November has a check issue date of 3rd December, which means the pay line transactions will be journalized against the November accounting period and the internally calculated amount such as taxes, company benefits will be journalized against the December accounting period. If there is a need to process all of the entries in December then all of the G/L Accounts should be set up with a Posting Date Method of ‘Pay Issue Fiscal’. If all the entries are to be journalized in November then ‘Pay Period End Fiscal’ should be the method. ''
;:Posting_Date_Method is an optional fixed lexicon ([X_POSTING_DATE_METHOD])
;Distribution Mask: This field holds the distribution code or distribution mask associated with this GL account code. Distribution_Format is a 50-character alphanumeric optional field that will default from the G/L Company chosen.
;Account Charge To:This field indicates if this G/L Account is to be charged to either the 'Wage’ or 'Benefit' accounts set up on IEAS distributions tab for each employee's assignment. The Account Charge To field will typically be set to ‘Wage Account’; for Benefit Burden G/L Accounts, you must manually set it to ‘Benefit Account’. UPGL will use the IEAS Distributions tab entries according to IDGA 'Account Charge To' set up as follows:
;:If IDGA’s Account Charge To field is set to ‘Benefit Account’, then the IEAS Distribution entries with the Split Rule field set to ‘Benefit Account’ will be used.
;:If the IEAS distribution entries with the ‘Benefit Account’ Split Rule are not set up, then the split rules will be used. Otherwise, IEAS distribution entries with other split Rule will be used. i.e. 'Split by Percent', etc.
;:Account_Charge_To is an optional fixed lexicon ([X_ACCOUNT_CHARGE_TO]).
----
!Account Toggles
;Affects Costing: If the Affects Costing toggle is ON, this account will create cost accounting entries for posting to a costing system. If the Affects Costing toggle is OFF, no costing entries will be created. Affects_Costing is an optional toggle field.
;Retain Detail: When interfacing to a G/L system, if the Retain Detail toggle is ON, no consolidation of payroll accounting entries will be performed. Detailed entries will be created by account, by person, by pay and by pay line detail. If the toggle is OFF, payroll accounting entries will be consolidated by general ledger account. Retain_Detail is an optional toggle field.
;Pre-Payroll: If the Pre-Payroll toggle is ON, any accounting process that runs prior to payroll processing (e.g. UPLG - labor distribution) will create accounting entries for posting to the general ledger and costing. If the Pre-Payroll toggle is OFF, these accounting processes will create no accounting entries. Pre_Payroll is an optional toggle field.
;Accrual Required:If the Accrual Required toggle is ON, this account will have accrual accounting entries created on the last payroll of a fiscal period. Accruals will be calculated based on the accrual method of the Employee's Group (IDGR). If the toggle is OFF, no accrual entries will be created for this account. Accrual_Required is an optional toggle field.
;Post Payroll:If the Post Payroll toggle is ON, the payroll process will create accounting entries for posting the general ledger (UPGL) and for costing purposes. If the Post Payroll toggle is OFF, the payroll process will create no accounting entries. Post_Payroll is an optional toggle field.
;InterCompany Required: If the InterCompany toggle is ON, inter-company accounting entries will be generated between entities. If the toggle is OFF, no inter-company accounting will be done. Intercompany_Required is an optional toggle field.
----
!Account Suffix
The Account Suffix area is used to allow G/L accounts to be varied by entity, unit, group, or legislative (state/prov, county, tax jurisdictions or school district) information.
You must define one ‘default’ G/L account entry without any Account Suffix information. Then set up the same G/L account with as many varying Accounting Information and Account Suffix entries as needed.
Finally, indicate on Acct/Arrears tab of IPPC if the pay component should be varied by Suffix Information.
;Entity: The G/L account should vary by the entity identified in this field. Entity_Code from P2K_CM_ENTITIES is an optional 16-character alphanumeric field that you may manually enter or select a value from the LOV (F9) provided.
;Unit: The G/L account will vary by the unit identified in this field. You must enter an entity prior to specifying the unit. Unit_Code from [P2K_CM_UNITS] is an optional 16-character alphanumeric field that you may manually enter or select a value from the LOV (F9) provided.
;Group: The G/L account should vary by the group identified in this field. You must enter an entity and unit prior to specifying the group. Group_Code from [P2K_CM_GROUPS] is an optional 16-character alphanumeric field that you may manually enter or select a value from the LOV (F9) provided.
;Other Suffix: This field is currently not being used. GL_Account_Sufx is an optional 30 character field that you may manually enter.
;State: The G/L account should vary by the state/province identified in this field. State_Province_Code from [P2K_CM_STATE_PROVINCES] is an optional 16-character field that you may manually enter or select a value from the LOV (F9) provided.
;County: The G/L account should vary by the county identified in this field. You must enter a state prior to specifying the county.
County_Code from P2K_CM_COUNTIES is an optional 16-character field that you may manually enter or select a value from the LOV (F9) provided.
;Geo: The G/L account should vary by the tax jurisdiction (i.e. Geo code) identified in this field. You must enter a state prior to specifying the tax jurisdiction. Jurisdiction from [P2K_CM_TAX_JURISDICTIONS] is an optional 16-character field that you may
manually enter or select a value from the LOV (F9) provided.
;School District:The G/L account should vary by the school district identified in this field. You must enter a state prior to specifying the school district. School_District_Code from [P2K_CM_SCHOOL_DISTRICTS] is an optional 16-character field that you may manually enter or select a value from the LOV (F9) provided.
This page (revision-12) was last changed on 26-Nov-2021 10:22 by JMyersTop