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

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
33 26-Nov-2021 10:22 9 KB khiggs to previous
32 26-Nov-2021 10:22 9 KB mmcfarland to previous | to last
31 26-Nov-2021 10:22 9 KB mmcfarland to previous | to last
30 26-Nov-2021 10:22 9 KB kparrott to previous | to last
29 26-Nov-2021 10:22 9 KB kparrott to previous | to last
28 26-Nov-2021 10:22 9 KB jescott to previous | to last
27 26-Nov-2021 10:22 9 KB jescott to previous | to last
26 26-Nov-2021 10:22 9 KB khiggs to previous | to last
25 26-Nov-2021 10:22 9 KB khiggs to previous | to last
24 26-Nov-2021 10:22 9 KB khiggs to previous | to last
23 26-Nov-2021 10:22 8 KB jmyers to previous | to last
22 26-Nov-2021 10:22 9 KB jmyers to previous | to last
21 26-Nov-2021 10:22 9 KB JAiken to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed one line
__Payrolls__ define the pay frequency for various groups of employees. Separate Payrolls are defined for each pay frequency in which a group of employees are paid. This means that employees who are paid at different times will have separate payroll codes. E.G. employees paid every week; employees paid every two weeks. Employees who have the same pay frequency, pay dates, and payroll bank will belong to the same payroll and have the same payroll code.
[{TableOfContents }]
!!!DEFINE PAYROLLS
Payrolls are created and maintained on the Define Payrolls (IPPR) form. \\
Payrolls define the pay frequency for various groups of employees. Separate Payrolls are defined for each pay frequency that a group of employees are paid. Consequently, employees who are paid at different times will have separate payroll codes, such as employees paid every week and employees paid every two weeks. \\
At line 3 changed one line
An employee can be on only one payroll code per ‘Employment Type’. Employment type is defined for each employee on the [IEHR] (Establish Personnel Profiles) form. Examples of employment types would be ‘Employee’, ‘Contractor’ or ‘Retiree’.
Employees who have the same pay frequency, pay dates, and payroll bank will belong to the same payroll and have the same payroll code.
At line 5 changed one line
Each Payroll Code will need to be defined in full detail. You may create and maintain those payroll codes through the Define Payrolls (IPPR) form.
An employee can be on only one payroll code per ‘Employment Type’. Employment Types are defined for each employee on the [IEHR] (Establish Personnel Profiles) form. \\
At line 7 changed 2 lines
You may access this feature under the Screen/Form menu:
__Payroll > Setup and Definitions > Define Payrolls__
Examples of employment types:
* Employee
* Contractor
* Retiree
At line 10 changed 16 lines
__‘Define Payroll Information’ Usage and Examples__
Payroll Information data is stored in the [P2K_PR_PAYROLLS] table.
;[Entity|ENTITY_CODE]:This field displays the entity for which the payroll is defined. Entity_Code from [P2K_CM_ENTITIES] is a mandatory 16-character alphanumeric field that you must manually enter or use the LOV (F9) to choose an option.
;[Payroll|PAYROLL_CODE]:This field holds a user-defined code that uniquely identifies the payroll within the organization.
Payroll_Code is a 16-character alphanumeric mandatory field that you must manually enter.
;[Description|DESCRIPTION]:This field gives a short description of the payroll code. Description is an optional 50-character alphanumeric field that you may manually enter.
----
!!Define Payrolls (IPPR) - Payroll
;[Legislation|LEGISLATION]:This code indicates the primary country whose legislation governs the organization. Legislation is a mandatory fixed lexicon ([X_LEGISLATION]) that you may use to look up the value.
;[Pay Point Set|PAY_POINT_SET_CODE]:The pay point set is a set of payroll calculation instructions to be executed for this payroll
during the pay cycle. Pay_Point_Set_Code from [P2K_PAY_POINT_SETS] is a 16-character mandatory field that you must complete with a value from the LOV (F9) provided. These pay point sets are defined in the [IPPP] screen.
;[Pay Calendar|PAY_CALENDAR_CODE]:This field defines which calendar is to be used for this payroll. E.G. Pay Period dates, Pay Issue dates, etc. Pay_Calendar_Code from [P2K_PR_PAY_CALENDARS] is a mandatory 16- character field that you must complete with a value from the LOV (F9) provided. These values are defined in the [IPCL] screen.
;[Additional Tax Option|ADDITIONAL_TAX_OPTION]:This field is used when an employee opts to pay additional tax per pay period. You may specify one of the following:
*Always - Additional tax is always taken, regardless if the employee has tax withheld
*Only If Available - Additional tax is taken only if the employee has income tax removed.
Additional_Tax_Option is an optional fixed lexicon ([X_ADDITIONAL_TAX_OPTION]) that you may use to look up the value.
Each Payroll Code must be defined in full detail.
At line 27 changed one line
;[MTD Summary|MONTHLY_SUMMARIES]: MTD Summary is the month to date summary toggle. If the MTD Summary toggle is checked, the pay close process (UPCLOZ) will create and store month-to-date totals. If the MTD Summary toggle is not checked, no month-to-date totals will be kept. Monthly_Summaries is an optional toggle field.
Payroll Information data is stored in the [P2K_PR_PAYROLLS] table.\\ \\
At line 29 changed 3 lines
For Canadian Installations: MTD totals are required in order to store month-to-date totals required for the Canada Custom Revenue Agency (CCRA). All Canadian clients must keep Mtd information in order to retrieve the monthly information needed to do monthly remittance on the RPYEC report.
;[QTD Summary|.QUARTERLY_SUMMARIES]:QTD Summary is the quarter to date summary toggle.If the QTD Summary toggle is checked, the pay close process (UPCLOZ) will create and store quarter-to-date totals. If the QTD Summary toggle is not checked, no quarter-to-date totals will be kept.
__For U.S. installations__: Quarter-to-date totals are __mandatory__.
!IPPR Field Descriptions
__Details__\\
||Field||Description
|[Entity|ENTITY_CODE]|This field defines the entity for which the payroll is defined.
|[Payroll|PAYROLL_CODE]|This field displays the user-defined code that uniquely identifies the payroll within the organization.
|[Description|DESCRIPTION]|This field displays a short description of the payroll code.
\\ \\
__Payroll Tab__\\
||Field||Description
|[Legislation|LEGISLATION]|This code defines the primary country whose legislation governs the organization.
|[Pay Point Set|PAY_POINT_SET_CODE]|The pay point set is a set of payroll calculation instructions to be executed for the payroll during the pay cycle.
|[Pay Calendar|PAY_CALENDAR_CODE]|This field defines which calendar will be used for the payroll, such as Pay Period dates, Pay Issue dates, etc.
|[Additional Tax Option|ADDITIONAL_TAX_OPTION]|This field is defined when an employee opts to pay additional taxes per pay period. Users can define one of the following: \\*Always - Additional taxes are always taken, regardless if the employee has tax withheld. \\*Only If Available - Additional taxes are taken only if the employee has income tax removed.
|[MTD Summary|MONTHLY_SUMMARIES]|Month to Date Summary toggle. When this toggle is set to ON, the pay close process ([UPCLOZ]) will create and store the month-to-date totals. When this toggle is set to NO, no month-to-date totals are generated. This is an optional toggle.
At line 33 changed one line
__For Canadian Installations__: Quarter-to-date totals are __optional__.
%%information NOTE: For Canadian organizations, the MTD totals are required in order to store month-to-date totals required for the Canada Revenue Agency (CRA). All Canadian organizations must keep the MTD information in order to retrieve the monthly information to complete the monthly remittance on the [RPYEC] report.%%
At line 35 changed 3 lines
Quarterly_Summaries is an optional toggle field.
;[Fiscal Summary|FISCAL_SUMMARIES]: If the ‘Fiscal Summaries’ toggle is checked, the pay close process ([UPCLOZ]) will create and store fiscal-to-date totals.
If the ‘Fiscal Summaries’ toggle is not checked, no fiscal-to-date totals will be kept.
|[QTD Summary|QUARTERLY_SUMMARIES]|Quarter to Date Summary toggle. When this toggle is set to ON, the pay close process ([UPCLOZ]) will create and store the Quarter-to-Date totals. When this toggle is set to NO, no quarter-to-date totals are generated. This is an optional toggle.
At line 39 changed one line
If the fiscal year runs for a different 12-month period (e.g. April to March), or is based on a 13 period year, High Line recommends that separate fiscal totals be kept from the year-to-date totals.
%%information NOTE: __For U.S. installations__, the Quarter-to-Date totals are __mandatory__. __For Canadian Installations__, the Quarter-to-date totals are __optional__.%%
At line 41 changed 6 lines
Fiscal_Summaries is an optional toggle field.
;[Tax Exempt Point|TAX_EXEMPT_POINT]: __For Canadian Installations Only.__
This field indicates the minimum, midpoint or maximum of the TD1 claim code range amount that should be used when calculating taxes. The process for how the employee’s tax exemption should be calculated is based on the governmental tax tables. These toggles should be adjusted if, during payroll testing, users find that the taxation amounts are slightly off.
*Minimum
*Mid Point (default)
*Maximum
|[Fiscal Summary|FISCAL_SUMMARIES]|When this toggle is set to ON, the pay close process ([UPCLOZ]) will create and store Fiscal-to-Date totals. When this toggle is set to NO, no Fiscal-to-Date totals are generated. \\ \\If your organization's fiscal year runs for a different 12-month period, such as April to March, or is based on a 13 period year, High Line recommends that separate fiscal totals be kept from the Year-to-Date totals. This is an optional toggle.
|[Assignment Summary|ASSIGNMENT_SUMMARY]|When this toggle is set to ON, the Rebuild Todate Records process ([UPTODATE]) will process 'Assignments to Date' records.
|[Tax Exempt Point|TAX_EXEMPT_POINT]| __For Canadian Installations Only.__ Mandatory. This field defines the minimum, midpoint or maximum TD1 claim code range amounts that are used when calculating taxes. The calculation of an employee’s tax exemption is based on the governmental tax tables. This field should be adjusted if, during payroll testing, users find that the taxation amounts are slightly off. Mid-Point is the default. Tax_Exempt_Point is a mandatory fixed lexicon ([X_TAX_EXEMPT_POINT]).
|[Account for Checks|PBA_ID_CHECK]|This field defines the bank account funds are withdrawn from for check payments. Bank_Account from [P2K_PR_PAYROLL_BANK_ACCOUNTS] is an optional 30-character alphanumeric field that users can manually enter or use the LOV (F9) to select an option.
|[Account for Deposits|PBA_ID_DEPOSIT]|This field defines the bank account funds are withdrawn from for deposit payments. Bank_Account from [P2K_PR_PAYROLL_BANK_ACCOUNTS] is an optional 30-character alphanumeric field that users can manually enter or use the LOV (F9) to select an option.
|[Bank Name|BANK_NAME]|This field defines the name of the bank where the account for checks is held. The Bank Name will default in based on the Account for checks chosen from the Define Bank Accounts [IPBA] form. Bank accounts must be defined on this form prior to porcessing payrolls.
|[Bank Name|BANK_NAME]|This field defines the name of the bank where the account for deposits is held. The Bank Name will default in based on the Account for checks chosen from the Define Bank Accounts [IPBA] form. Bank accounts must be defined on this form prior to porcessing payrolls.
|[Detailed Pay Stub|DETAILED_PAY_STUB]|Users can define if details, such as wage rate, should or should not display on the View Disbursements (IPDS) form. The options are: \\* Include Wage Rate \\* No Wage Rate \\* Suppress Details
%%information NOTE: It is recommended that the Elements listed should be unique for use on this screen only. This will prevent changes to stub information from impacting payroll calculations%%
|[Earnings Element|PEL_ID_EARNINGS]|All current and Year-to-Date earnings that will be displayed on the stubs and/or notices must be defined in this field. The Gross Pay Element can be used.
|[Deductions Element|PEL_ID_DEDUCTIONS]| All current and Year-to-Date employee deductions that will be displayed on the stubs and/or notices must be defined in this field. The Total Deductions Pay Element can be used.
|[Benefits Elements|PEL_ID_BENEFITS]| All current and Year-to-Date employer contributions that will be displayed on the stubs and/or notices must be defined in this field.
|[Other Elements|PEL_ID_OTHER]|Any other current Pay Component amounts that will be displayed on the stubs and/or notices can be defined in this field.
|[Max. Gross|MAXIMUM_GROSS]|If a maximum gross amount is defined in this field, a warning will be issued on the payroll exception report when an employee’s gross amount exceeds this amount. Maximum_Gross is an optional 18 digit numeric field that users must enter manually.
|[Max. Net|MAXIMUM_NET]|If a maximum net amount is defined in this field, a warning will be issued on the payroll exception report when an employee’s net amount exceeds this amount. Maximum_Net is an optional 18 digit numeric field that users must enter manually.
At line 48 changed 9 lines
Tax_Exempt_Point is a mandatory fixed lexicon ([X_TAX_EXEMPT_POINT]).
;[Account for Checks|PBA_ID_CHECK]:This field indicates the bank account from which the funds are withdrawn for check payments.
Bank_Account from P2K_PR_PAYROLL_BANK_ACCOUNTS is an optional 30-character alphanumeric field that you may manually enter or use the LOV (F9) to choose an option.
;[Account for Deposits|PBA_ID_DEPOSIT]:This field displays the bank account from which the funds are withdrawn for deposit
payments. Bank_Account from P2K_PR_PAYROLL_BANK_ACCOUNTS is an optional 30-character alphanumeric field that you may manually enter or use the LOV (F9) to choose an option.
;[Bank Name|BANK_NAME]:This field identifies the bank where the account for checks is held. Bank Name will default based on the Account for checks chosen from IPBA, needs to be added.
;[Bank Name|BANK_NAME]:This field identifies the bank where the account for deposits is held. Bank Name will default based on the Account for deposits chosen from IPBA, needs to be added.
;[Detailed Pay Stub|DETAILED_PAY_STUB]:If the Detailed Pay Stub toggle is checked, the hours and rate associated to the earnings
are stored for printing on the check stub and/or deposit notices. If the toggle is not checked, then these details are not retained and only the earnings may be accessed. Detailed_Pay_Stub is an optional toggle field.
%%information NOTE: The maximum gross and net defined amounts do not affect how an employee’s pay is calculated.%%
|[Min. Net|MINIMUM_NET]|If a minimum net amount is defined in this field, a warning will be issued on the payroll exception report when an employee’s net amount is below this amount. \\The employee’s net pay will be adjusted to this amount. Consequently, one or more deductions may not be taken. \\Minimum_Net is an optional 18 digit numeric field that users must enter manually.
|[Starting Check #|STARTING_NUMBER]|This field defines the first check number in a series. The Starting_Number is a mandatory 10 digit numeric field that users can either enter manually or select from the LOV.
|[Ending|ENDING_NUMBER]|This field defines the last check number in a series. This field is for display purposes only. The values are defined on the [IPBA] form and cannot be edited directly in this form.
|[Last Used|LAST_NUMBER_USED]|This field defines the last check number issued for this account. This field is for display purposes only. The values are defined on the [IPBA] form and cannot be edited directly in this form.
\\ \\
__ADP Interface__\\
|[ADP Tax Company|ADP_TAX_COMPANY]|This field is used for organizations reporting payroll to ADP. This is an optional 50-character alphanumeric field that displays the name of the company that will be reported to ADP. \\ \\Each Payroll is linked to a specific “ADP Tax Company” and this information must be defined on this form. This is used for the Quarterly Reporting process to ADP.
|[ADP File Number|ADP_FILE_NUMBER]|This field is used for organizations reporting payroll to ADP. This is an optional 10-digit numeric field displays the ADP file number of the company that will be reported to ADP.
\\
__Batch Elements Tab__\\
The Batch Element tab is used to define a list of the Pay Elements used to balance the batch.\\
|[Element|ELEMENT_CODE]|The Batch Elements are lists of [pay components|PAY COMPONENTS] that are used to balance the ‘Actuals’ from the pay header transaction lines against the ‘Givens’ that users can define in the batch. The Element_Code from [P2K_PR_ELEMENTS] is an optional field that users can enter manually or use the LOV (F9) to select an option.
|[Description|DESCRIPTION]|This field provides a short description of the batch element. The Description is an optional 50-character alphanumeric field that defaults from the element code.
The sort order of batch balancing elements on the Transaction Audit Report ([UPAUDT]) is based on the “Element Description” from the Pay Elements on ([IPPE]), not the Pay Element code.
----
![Notes|Edit:Internal.IPPR]
[{InsertPage page='Internal.IPPR' default='Click to create a new notes page'}]