DEFINE PAY CALENDARS#
The Define Pay Calendars (IPCL) form is used to create and maintain Pay Calendars (sometimes known as pay schedules). Pay Calendars may contain pay periods that identify the period start and end dates, for specific time frames used in each payroll, as well as the issue date for the check and/or deposit.A separate pay calendar is required for each pay frequency. Payroll calendars are separate and distinct from the structural calendars created through the Define Business Calendars (IDCL) form.
Pay periods define the dates when work is performed, as well as the date an employee is being paid on (Pay Issue date). Not all weeks, unless paid weekly, are considered valid pay periods.
When initially defining the Pay calendar, users only need to enter one pay period’s information, then use the Extend Calendar function to generate one year of pay periods, with pay issue dates, up to the end of the year. Users can then verify, remove and regenerate information until the pay periods are correct.
The Extend Calendar button allows users to extend the calendar for one year.
Pay Calendar and Pay Period data is stored in the P2K_PR_PAY_CALENDARS and P2K_PR_PAY_PERIODS tables.
IPCL Field Descriptions#
| Field | Description |
|---|---|
| Pay Calendar | |
| Description | This field displays a description of the pay calendar code entered. |
| Pay Frequency | Defines the interval employees are paid. Personality supports weekly, biweekly, semimonthly and monthly pay frequencies. Special and non-scheduled payments can be made within all of these frequencies. |
| Weeks per Pay | This field defines the number of standard weeks in a pay period. Options are: * Weekly: 1 * Biweekly: 2 * Semimonthly: 2.1667 * Monthly: 4.3333 |
| Weeks per Year |
Pay Periods#
Pay periods are defined by a 6 digit number. The first 4 numbers identify the year and the last two numbers identify the pay period week within that year. Example:- 2017-01 The first pay period week in 2017
- 2017-02 The second pay period week in 2017
| Period | Defines the pay period number. |
| Week Ends | This field displays the last day of the week. For Canadian organizations: For EI purposes this date must be a Saturday. |
| Pay Start Date | This field defines the date of the first day of the pay period. The Pay Start Date’ must be earlier than the Week Ends Date. |
| Pay Ending Date | This field defines the date of the last day of the pay period. The ‘Period Ending Date’ must be on or after than the Week Ends Date. |
| Issue Date | This field defines the date the payment is issued for the pay period. The ‘Pay Issue Date’ must be on or after the Pay Ending Date. |
| # in Mth | This field defines the pay number that this pay falls within the calendar month, such as 1st, 2nd or 3rd. This number is normally based on the issue date. |
| # in Yr. | For each pay period, a pay number is provided to define which pay of the year it is. |
| Advance | This field defines the last date that pay advances should be processed for an employee going on leave. |
| #Remain(Ben) |
User Fields#
ROE Pay Frequency
According to HRSDC, the Pay Period type must be one of the following codes to be reported on ROE:
B - Biweekly
M - Monthly
O - Monthly Non-Standard
S - Semi-Monthly
E - Semi-Monthly Non-Standard
H - Thirteen per Year
W - Weekly
Users can enter one of the above letters in the ROE Pay Frequency field on IPCL, otherwise the first letter of the IPCL Pay Frequency description will be used.
Pays Per Year
If defined, this will override the # in Yr. - Pay of Year field on the Pay Periods and will be passed to the US tax calculation.
Notes #
Click to create a new notes pageScreen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation