Administration Help   I   Financial Help  I   Performance Budgeting Help

940 Tax Reporting

For sites that utilize Advantage 940 Tax Reporting, the following configuration fields are required:

• Configuration Text Field 1 - This field is used to define the Employer ID Number (EID). Enter the 9-digit number that represents your site.

• Configuration Text Field 2 - This field is used to define the Employer Name.

• Configuration Text Field 3 -This field is used to define the Employer Trade Name.  

• Configuration Text Field 4 - This field is used to define the Employer Business Address.

• Configuration Text Field 5 - This field is used to define the Employer Business City.

• Configuration Text Field 6 - This field is used to define the Employer Business State. Enter the abbreviated state value for your site.

• Configuration Text Field 7 - This field is used to define the Employer Business Zip Code. Enter the 5-digit number for your site.

• Configuration Numeric Field 1 - This field is used to enter the Federal Unemployment Nonexempt Rate. Enter a two-digit decimal value.

Employee Tax Refund Processing

For sites that utilize Employee Tax Refund Processing, the following configuration fields are required:

• Configuration Text Field 1 - This field is used to define the FICA Benefit Type/Plan that is used for refunds on the One Time Deduction (OTDED) transactions. Enter comma separated Benefit Type and Benefit Plan values. For example, TYPE1, PLAN1.

• Configuration Text Field 2 - This field is used to define the Medicare Benefit Type/Plan that is used for refunds on the One Time Deduction (OTDED) transactions. Enter comma separated Benefit Type and Benefit Plan values. For example, TYPE1, PLAN1.

• Configuration Text Field 3 - This field is used to define the SDI Benefit Type/Plan that is for refunds on the One Time Deduction (OTDED) transactions for refunds. Enter comma separated Benefit Type and Benefit Plan values. For example, TYPE1, PLAN1.

• Configuration Text Field 4 - This field is used to define the Refund Pay Event that is used on the By-Pay-Type Supplemental Trigger (STRG) transactions generated. Enter a valid Pay Event.

• Configuration Text Field 5 - This field is used to define the Employer Business Address.

• Configuration Text Field 6 - This field is used to define the Employer Business City.

• Configuration Text Field 7 - This field is used to define the Employer Business Zip Code. Enter the 5-digit number for your site.

• Configuration Text Field 8 - This field is used to define the Employer Name.

• Configuration Numeric Field 1 - This field is used to define the FICA Minimum Wage Threshold. Enter the threshold value for the specific tax year.

• Configuration Numeric Field 2 - This field is used to define the Medicare Minimum Wage Threshold. Enter the threshold value for the specific tax year.

• Configuration Numeric Field 3 - This field is used to define the State Disability Insurance (SDI) Minimum Wage threshold. Enter the threshold value for the specific tax year.

Quarterly Catch Up Tax Processing

For sites that utilize Quarterly Catch Up Tax Processing, the following fields are required:

• Configuration Text Field 1 - This field is used to define the Pay Event that is set on the By-Pay-Type Supplemental Trigger (STRG) transactions generated. Enter a valid Pay Event.

• Configuration Numeric Field 1 - This field is used to define the Employer Wage Minimum threshold amount required to be met before taxes can be collected on FUTA (U), SUI (S), and ETT (E) taxes. Enter the government mandated threshold value for the specific tax year.   

NextGen Payroll Configuration

For sites that utilize the Next Generation Payroll service, the following fields are required:

• Configuration Text Field 1 - This field is used to define the default location for the files produced by NextGen Payroll. Enter the full path where the files should be written by NextGen Payroll. Example: /apps/CGIADV/RTFiles/payroll/ledgers

• Configuration Text Field 2 - This field is used to define the ledgers file location for NextGen Payroll. Enter the full path where the ledger files should be written by NextGen Payroll. Example: /apps/CGIADV/RTFiles/payroll/ledgers

• Configuration Text Field 3 - This field is used to define the spool file location for NextGen Payroll. Enter the full path where the spool files should be written by NextGen Payroll. Example: /apps/CGIADV/RTFiles/payroll/spool

• Configuration Numeric Field 1- Enter the maximum database table rows that the NextGen Payroll should be allowed to fetch in one database fetch operation. If left blank, the maximum prefetch rows defaults to 5000.

NextGen Payroll Cache Configuration

This Feature ID is used to define the cache configuration for Next Generation Payroll. Configuring the following fields supports faster processing time for batch processes that utilize the Next Generation Payroll service:

• Configuration Text Field 1 through 16 - Enter the comma separated list of tables that participate in caching process for Next Generation Payroll. Primarily, include the tables whose data does not change during the processing of jobs that utilize the Next Generation Payroll service. The list of tables entered will be in cached memory as long as the Begin Day batch job is not run. When the Begin Day batch job is run it resets and empty the cache. Caution must be taken while mentioning tables that are updated during normal business activities to avoid clearing out the cached information when running the Begin Day job. Most of the reference tables will fall into this category. Some tables whose data does change during the job processing can be included, but caution must be used and ensure that these table updates are not required for any other processing at the same time. A default list is provided.

• Configuration Numeric Field 1 - Enter the maximum database table rows that the Next Generation Payroll cache should hold before cache overflow occurs and elements are removed from the cache.

• Configuration Flag Field 1- Setting this flag to Yes enables Next Generation Payroll caching for your site. It is recommended to enable this flag along with NextGen Payroll Cache Preload Configuration Feature ID for better performance. When this is turned On, sites must run the Begin Day batch process to refresh the cache before the start of the batch cycles.

For online transactions such as Online Check and Paycheck Calculator, cache will be ignored irrespective of whether this flag is turned On or Off.

NextGen Payroll Cache Preload Configuration

This Feature ID defines the cache preload configuration for the Next Generation Payroll service. Configuring the following fields allows for faster processing time for batch processes that utilize the Next Generation Payroll service:

• Configuration Text Field 1 through 16 - Enter the comma separated list of tables that should be preloaded by the Begin Day batch process into the Next Generation Payroll cache. Include only the tables whose data does not change during the processing of batch processes that utilize the Next Generation Payroll service, and are very frequently used by the Next Generation Payroll batch processes. Data is gathered from these tables during Begin Day or when the Next Generation Payroll container is bounced. When the Begin Day batch job is executed it gathers all records from the tables mentioned and store all the information from it into memory. Any other job run after the Begin Day batch job, then the system will look from the stored cache information. Caution must be taken while mentioning tables that are updated during normal business activities to avoid running the Begin Day job frequently. Once the cache is loaded with table data information, it reuses only the information stored in cache memory and ignore any record updates that occurred in the tables.

• Configuration Numeric Field 1 - Enter the maximum database table rows per table that can be preloaded into the Next Generation Payroll cache.

• Configuration Flag Field 1- Setting this flag to Yes enables the preloading of the Next Generation Payroll cache. It is recommended for sites to enable the NextGen Payroll Cache Configuration Feature ID along with this feature ID for better performance. When this is turned Off, the Begin Day batch process will only clear the cache without pre-loading any tables into cache.

Feature ID

Description

Field ID Settings

California Garnishment

The California Garnishment Feature ID defines pay period hours and multipliers used in the California Garnishment calculation. This Feature ID is intended to be used with the California Garnishments Special Routine ID.  

• Configuration Numeric Field 1 - Used to define weekly pay period hours.

• Configuration Numeric Field 2 -Use to define bi-weekly pay period hours.

• Configuration Numeric Field 3 - Use to define semi-monthly pay period hours.

• Configuration Numeric Field 4 - Use to define monthly pay period hours.

• Configuration Numeric Field 5 - Use to define annual pay period hours.

• Configuration Numeric Field 6 - Used to define the percent multiplier. This value is multiplied by the Net Disposable Income (NDI) to determine the federal limit.

• Configuration Numeric Field 7 - Used to define the percent multiplier. This value is multiplied by the value determined from deducting the minimum wage multiplied by the pay period from the Net Disposable Income (NDI).

For more information, refer to the “California Garnishment (CAGN)” topic in the CGI Advantage Deduction Processing User Guide.

Check Print Configuration

The Check Print Configuration Feature ID allows to display additional employee related attributes and department return address location details in the XML file generated during Check Print processing.

• Configuration Text Field 1: Defines the Salary Reduction Category and the Warrant Branch Number to display the MICR details in the check print xml. The Salary Reduction Category code and its short description are comma separated. The Salary Reduction Category and the Warrant Branch Number are separated by a vertical bar.

• Configuration Text Field 2:
  Defines the Deduction Type and Deduction Plan for additional state tax to display the withholding amount. The Deduction Type and Deduction Plan are comma separated.

• Configuration Text Field 3:
  Defines the Deduction Type and Deduction Plan for additional state tax to display the withholding amount. The Deduction Type and Deduction Plan are comma separated.

• Configuration Text Field 4:
  Defines the Deduction Type and Deduction Plan for additional state tax to display the withholding amount. The Deduction Type and Deduction Plan are comma separated.

• Configuration Text Field 5:
  Defines the Deduction Type and Deduction Plan for additional state tax to display the withholding amount. The Deduction Type and Deduction Plan are comma separated.

• Configuration Text Field 6:
  Defines the Deduction Type and Deduction Plan for additional state tax to display the withholding amount. The Deduction Type and Deduction Plan are comma separated.

• Configuration Text Field 7:
  Defines the Deduction Type and Deduction Plan for additional state tax to display the withholding amount. The Deduction Type and Deduction Plan are comma separated.

• Configuration Text Field 8:
  Defines the Deduction Type and Deduction Plan for additional state tax to display the withholding amount. The Deduction Type and Deduction Plan are comma separated.

• Configuration Text Field 9:
  Defines the Deduction Type and Deduction Plan for additional state tax to display the withholding amount. The Deduction Type and Deduction Plan are comma separated.

• Configuration Text Field 10:
  Defines the Deduction Type and Deduction Plan for additional state tax to display the withholding amount. The Deduction Type and Deduction Plan are comma separated.

• Configuration Text Field 11:
  Defines the Category codes for which the input amount (INPUT_AM) is prorated based on the Full-Time Equivalent (FTE) percentage. The Category Codes are comma separated.

• Configuration Text Field 12:
  Defines the Category code which is used to determine net pay. It excludes the display of deduction amounts contributing to net pay in Check Print xml.

• Configuration Flag 1: Acts as a feature flag that enables Configuration Text Fields 1 through 10, along with the following check box options on the Employee Fringe Benefit Type (BENT), Deduction Type (DEDT), and Employer Fringe Benefit Type (EFBT) reference pages:
  i.   Include Benefit Type on Check Print xml
  ii.  Include Deduction Type on Check Print xml
  iii. Include Fringe Type on Check Print xml

• Configuration Flag 2: Acts as a feature flag specifically for xml generation during Check Print processing. When Configuration Flag 1 is enabled, this flag determines whether the generated xml file is sent to the ExportImport location path defined in the ADV30Params.ini file.

• Configuration Flag 3: Indicates whether the Return Check Address feature is enabled. When enabled, the Return Address Location set on the Extended Department (DEPTX) reference page is set as the return address on the employee’s check.

• Configuration Flag 4: When enabled, this flag suppresses the display of the input amount (INPUT_AM) for dollar-based events. It also suppresses both the input amount (INPUT_AM) and contract pay amount (CNTRCT_PY_AM) for zero pay events. Note: For events where amounts are suppressed, the corresponding fields  appear as blank spaces in the xml.

• Configuration Flag 5: When enabled, this flag allows the display of additional attributes.
  i.   Include Benefit Type on Check Print xml 
  ii.  Include Deduction Type on Check Print xml
  iii. Include Fringe Type on Check Print xml

• Configuration Flag 6: When enabled, it combines the input amount (INPUT_AM) and contract pay amount (CNTRCT_PY_AM) for dollar-based and time-based events, provided they are associated with the same category code.

Note:

• Configuration Flag 3: for the Return Check Address functionality works independently from Configuration Flag 1.

FLSA Compensatory Time Off Processing

The FLSA Compensatory Time Off Processing Feature ID defines various Compensatory Time Off events, including accrual and reversal events, pay events for processing, leave categories for balance computation, validation rules for timesheet entries, as well as Transaction ID prefixes and date formats for compensatory payouts.

• Configuration Text Field 1: Defines the Compensatory Time Off Premium Accrual Events. The events are comma delimited.

• Configuration Text Field 2: Defines the Compensatory Time Off Premium Reversal Accrual Event. The events are comma delimited.

• Configuration Text Field 3: Defines the pay events used to pay out Compensatory Time Off due to Compensatory Time Off cap processing. The events are comma delimited.

• Configuration Text Field 4: Defines the Compensatory Time Off leave categories that should be included to compute employee’s current Compensatory Time Off leave balance. The events are comma delimited.

• Configuration Text Field 5: Defines  the Compensatory Time Off Pay Events on which no edit is performed to validate the events entered on timesheet. The events are comma delimited.

• Configuration Text Field 6: Defines the Transaction ID prefix for Compensatory Payout.

• Configuration Text Field 7: Defines the Date Format for Compensatory Payout.

• Configuration Text Field 8: Defines pay events that will not be included in Retroactive Pay processing.

• Configuration Flag 2: When selected indicates that Compensatory Time Off Processing for FLSA Exempt employees is enabled. When this flag is selected, the Sub-Title page allows a FLSA Profile code to be entered when the associated Title code is defined as FLSA Exempt.

Multi State Tax

The Multi State Tax Feature ID defines the default configurations for federal and state taxes, when an employee does not have any tax enrollment information available.  This entry is utilized when the MULTI_STATE_TAX APPCTRL entry is set to Y. Note, these values take the place of the Default Tax Site Parameters (SPAR).

• Configuration Text Field 1 - Enter the default FICA Class code used to identify the employee’s participation in the retirement and Medicare portion of FICA in the absence of employee specific data.

• Configuration Text Field 2 - Enter the default Tax Class code used in determining the federal tax withholdings to be calculated in the absence of employee specific data.

• Configuration Text Field 3 - Enter the default Tax Marital Status code that is used to calculate an employee’s federal tax withholding in the absence of the employee specific data. 

• Configuration Text Field 4 - Enter the default State Tax Class code that is used in determining the set of eligible state tax withholdings in the absence of the employee specific data.

• Configuration Text Field 5 -  Enter the default State ID code that is used in determining the state tax withholdings to calculate in the absence of the employee specific data.

• Configuration Text Field 6 - Enter the default Tax Marital Status code used to calculate an employee’s state tax withholding in the absence of employee specific data.

• Configuration Text Field 7 -  Enter the State Tax Class code to be used on the Employee State Tax Withholdings Certificate (ETAXS) transaction. The TAXCS indicated defines which states an employee is eligible to enroll in on ETAXS.

• Configuration Numeric Field 1 - Enter the default number of allowances used to calculate an employee’s federal tax withholding in the absence of employee specific data. Note, this only applies to employee’s hired prior to January 1, 2020 who have not submitted a Form W-4.

• Configuration Numeric Field 2 - Enter the default number of allowances used to calculate an employee’s state tax withholding in the absence of employee specific data.

Expandable Pay Rate Processing

The Expandable Pay Rate Processing Feature ID defines rules to create additional PPRT lines basis Configuration Text and numeric fields

• Configuration Text Field 1: Enter values with text pattern Pay Policy, Pay Event Type, Amount Basis ID, New Pay Event Type. This  creates a new PPRT entry for new Pay Event Type, 

• Configuration Numeric Field 1: Enter percentage at which the new pay event type lines to be created.

• Users can create up to a maximum of 10 such configuration text and numeric fields.

Exception Pay Work Hour Rate

Exception Pay Work Hour Rate Feature ID defines

• Configuration Text Field 1: Enter the pay event code that will be used to generate a rounding adjustment. The pay event should be a dollar-based event.

• Configuration Numeric Field 1: Enter values for the lower limit used for the rounding tolerance. The negative limit is stored on the Configuration Numeric Field 1.

• Configuration Numeric Field 2: Enter values for the upper limit used for the rounding tolerance. The positive limit is stored on the Configuration Numeric Field 2.

• Configuration Numeric Field 3: Enter the values 1, 2, and 3 to be by Gross-to-Net (GTN) process during Online, Supplemental, or Regular cycle: 
  i.    If the value is set to 1 (Current), only pending payments with the event dates within the current Pay Period (PERD) date will be included in the Rounding Adjustment process.   
  ii. If the value is set to 2 (Current and Prior Pay Period Adjustments), all pending payments (excluding pending payments generated from Retro Pay), regardless of event dates, will be included in the Rounding Adjustment process.  Prior pay period adjustments are timesheet adjustments with event dates prior to the current pay period.
  iii. If the value is set to 3 (Current, Prior, and Retro), all pending payments, regardless of event dates, will be included in the Rounding Adjustment process,
  If the Yes/No Flag is checked and if the value entered on the Numeric Value field is not equal to 1, 2, or 3, Rounding Adjustment process will not be invoked.

• Configuration Flag 1: The lower limit is used when Configuration Flag 1 is set to Yes.

• Configuration Flag 2: The upper limit is used when Configuration Flag 2 is set to Yes.

• Configuration Flag 3: The Rounding Adjustment process is used when Configuration Flag 3 is set to Yes.

Retroactive Deduction Processing

The Retroactive Deduction Processing defines rules for processing a deduction during the Retroactive Deduction batch processes and creating retroactive deduction triggers. 

• Configuration Text Field 1: Pending Payments created by the indicated transaction codes will not be processed by the Retro Deduction Data Extract batch job.

• Configuration Text Field 2: Pending Payments with the indicated event type codes will not be processed by the Retro Deduction Data Extract batch job.

• Configuration Text Field 3: Indicates the cutoff day for determining if an employee has a trigger in a prior calendar year during the Retro Deduction Data Extract batch job.

• Configuration Numeric Field 1: Indicates the maximum number of months in the past a Retro Salary Increase can be processed for a Deduction - Salary Change trigger.

• Configuration Numeric Field 2: Indicates the maximum number of months in the past a Retro Salary Decrease can be processed for a Deduction - Salary Change trigger.

• Configuration Date 1: Indicates the earliest date that a Deduction - Ded Change trigger can be processed. Additionally, when creating Deduction – Ded Change triggers on ENRL, MISC, or PENS the trigger start date will be updated to this date if it is before.

• Configuration Date 2: Indicates the earliest date that Retroactive deduction adjustments can be created. Additionally, when creating Deduction - Salary Change triggers on ESMT, the trigger start date will be updated to this date if it is before.

Special In-Grade Salary Criteria

The Special In-Grade Salary Criteria Feature ID in Offline Process Configuration (OPROC) defines the number of qualifying months and percentage increase parameter values required for Merit Salary Adjustment (MSA) and Special In-Grade Salary Adjustment (SISA) processing. These configured parameters are referenced during the execution of the Process Salary Adjustments batch job to determine eligibility and calculate the applicable salary adjustments.

• Configuration Numeric Field 1: Indicates the number of qualifying months required for Special In-Grade Salary Adjustment (SISA) processing.

• Configuration Numeric Field 2: Indicates the number of qualifying months required for Merit Salary Adjustment (MSA) processing.

• Configuration Numeric Field 3: Indicates the percentage increase to be applied for non–table-driven employees during MSA or SISA processing. This value is used to calculate the revised Base Pay amount.

Feature ID

Field ID Settings

PAM Processing Configuration 

The PAM Processing Configuration OPROC defines configuration settings for Payroll Accounting Management processing. These configurations setting apply to the Payroll Check Processor and Payroll Labor Distribution Consolidation batch processes:

• Configuration Text Field 1: Enter the Account Override Processing Orders to be used for OPROC specific processing on Payroll Check Processor Accounting Overrides (PCPAO). Enter values separated by a comma.

• Configuration Text Field 2: Enter the Account Override Processing Orders to be used for OPROC specific processing on Payroll Check Processor Accounting Overrides (PCPAO). Enter values separated by a comma.

• Configuration Text Field 3: Enter the Account Override Processing Orders to be used for OPROC specific processing on Payroll Check Processor Accounting Overrides (PCPAO). Enter values separated by a comma.  

• Configuration Text Field 4: This field contains the Vendor Disbursement Format that is used during Populate Warrant Disbursement Information on PRLVP processing. For more information on Populate Warrant Disbursement Information on PRLV refer to the “Advanced - Special Processing” topic in the CGI Advantage PAM User Guide.

• Configuration Text Field 5: This field contains the Payroll Number that is used to set the Check Date for PRLVP Scheduled Payment Date calculations during Supplemental Payroll Processing. This field is required when Configuration Text Flag 4 is checked.

• Configuration Text Field 6: Enter the transaction types that utilizes the Accounting Period 13 process. Valid entries include: PRACR, PREXC, PREXP, PRLCE, PRLIA, PRLID, PRLLL, PRLNP, PRLVP.

• Configuration Flag 1: Indicates if Populate Warrant Disbursement Information on PRLVP processing is enabled.For more information on Populate Warrant Disbursement Information on PRLV refer to the “Advanced - Special Processing” topic in the CGI Advantage PAM User Guide.

• Configuration Flag 2: Indicates if Premium COA Allocation Crosswalk processing during the Payroll Check Processor batch process is enabled. 

• Configuration Flag 3: Indicates if records on PYRL_EXPS_JRNL_HST will be considered during Premium COA Allocation Crosswalk processing when determining which Straight Paid Overtime Events is used to allocate overrides.

• Configuration Flag 4: Indicates if the Scheduled Payment date processing is enabled to determine the scheduled payment date for advance payments. When selected, Configuration Text Field 5 is required.

• Configuration Flag 5: Indicates if the employee deduction amount and employer contribution amount towards a cafeteria benefit are summed on the PYRL_LIAB_JRNL entry. This occurs even if deduction amount is 0 for the deduction.

• Configuration Flag 6: Indicates if the SNGL_PYMT_IND_FL flag is set.
  If the flag for SNGL_PYMT_IND_FL is set, Deduction Type and Deduction Plan are added to the key for PRLVP header creation.

• Configuration Flag 7: Indicates if the 13th accounting period processes when enabled using the Fiscal Year from the Check Date minus 1 and a Fiscal Month of 13 when the Check Date is greater than or equal to 7/1 or less than or equal to 7/15 (regardless of year).

• Configuration Numeric Field 1: This field is used to set the Vendor Payment Lag Day for PRLVP Scheduled Payment Processing.

Bank Account Code overrides for PAM Transactions

Bank Account Code overrides for PAM Transactions feature on OPROC allows a default bank account code inferred during the Check Print process to be overridden by the Payroll Labor Distribution Consolidation batch job. 

Configuration Text Field 1 - 15 can be used to enter the PAM Transaction Type and the Bank Account code to be used during the Payroll Labor Distribution Consolidation process.

Each Configuration Text Field can be used to indicate the Bank Account code used for a particular PAM transaction. Comma separated text values are not supported.

• Configuration Text Field 1: E=A110

• Configuration Text Field 2: X=A111

• Configuration Text Field 3: I=A112 

The above entries mean Bank Account Code of A110 is applicable to Payroll Expense Type (PREXP) and Bank Account Code of A111 is applicable to Payroll Fringe Expense Type (PREXP) and Bank account code of A112 is applicable to Payroll Liability Journal Type (PRLIA).

Note: Bank Account code override for Adjustment Expense Journal Type Transactions (PREXC) is not  allowed.

Below is a reference of the available PAM transaction types represented by a specific code that can be set up on the Configurable Text Fields.

• For Payroll Liability Type (PRLIA), use the code L. For example. (L=99).

• For Payroll Expense Type (PREXP), use the code E For example (E=99) .

• For Payroll Fringe Expense Type (PREXP), use the code X. For example, (X=99).

• For Payroll Fringe Liability Type (PRLIA), use the code I. For eaxmple, (I=99).

• For Payroll Vendor Payable Fringe Type (PRLVP), use the code P. For example (P=99).

• For Payroll Net Pay Type (PRLNP), use the code N. For example, (N=99).

• For Payroll Vendor Payable Type (PRLVP), use the code V. For eaxmple, (V=99).

• For Payroll Internal Type (PRLID), use the code G. For example,. (G=99).

• For Payroll Internal Fringe Type (PRLID), use the code F. For example, (F=99).

• For Payroll Leave Liability Type (PRLLL), use the code B. For example, (B=99).

• For Payroll Contract Encumbrance Type (PRLCE), use the code C. For example, (C=99).

• For Contract Reserve Pay Type (PRLNP), use the code R. For example,. (R=99).

• For Payroll Accrued Expenditure Type (PRLNP), use the code A. For example, ,(A=99).

• For Payroll Expense Accrual Type (PRACR), use the code EA. For example, (EA=99).

• For Payroll Fringe Expense Accrual Type (PRACR), use the code XA. For example, (XA=99).

Preloaded Chain Jobs triggered by UI

Preloaded Chain jobs triggered by UI allows a user to trigger the payroll related chain jobs from Pay Period (PERD) and Trigger Management (TRGM) reference pages. The chain job Catalog ID’s need to be updated here as per the following guidelines.

• Configuration Number Field 1: Enter the Catalog ID for the Run Regular Payroll chain job.

• Configuration Number Field 2: Enter the catalog ID for the Run Preliminary Payroll chain job.

• Configuration Number Field 3: Enter the catalog ID for the Run Retro Pay Cycle chain job.

• Configuration Number Field 4: Enter the catalog ID for the Run Retro Deduction Cycle chain job.

• Configuration Number Field 5: Enter the catalog ID for the Run Retro Leave Cycle chain job.

• Configuration Number Field 6: Enter the catalog ID for the Run Supplemental Payroll chain job.

• Configuration Number Field 7: Enter the Job Manager Server ID for assigning the triggered chain jobs to the appropriate job manager.