Additional Options
- Pay Cycle Control
Enter a code specifying whether to incorporate execution control into the payroll cycle steps. Valid codes are:
Y: You must set up execution control by version to determine who can execute the steps within the payroll cycle.
N: No execution control. The person who runs the first pre-payroll step must run all steps in the cycle. This value is the default.
- Spending Account Control
Enter a code indicating whether to use flexible spending accounts in processing payroll. Valid codes are:
Y: Use flexible spending accounts.
N: Do not use flexible spending accounts. This value is the default.
- P/R Register Edit (p___ r___ register edit)
Enter a code that specifies a type of error. The system always notes errors in the payroll register if the gross pay amount minus the taxes and applicable deductions does not equal net pay. Values are:
Y: Hard error. You must correct the error and run pre-payroll again. This value is the default.
N: Soft error. This error is noted on the payroll register but payroll cycle processing can continue. You must make the necessary corrections after the payroll cycle is complete.
- Employee Number Display Mode
Enter a code that specifies the type of employee number displayed on inquiry screens. Values are:
1: Display the eight-digit Address Book number (default).
2: Display the nine-digit Social Security number.
3: Display the eight-digit Additional Employee number preceded by a forward slash (/).
All forms of employee number remain valid.
- Enable Multi-currency Functionality
Enter a code that enables multicurrency functions within the JD Edwards EnterpriseOne Human Resources and JD Edwards EnterpriseOne Payroll systems. Values are:
Y or 1: Yes
N or 0: No
- Retrieve PDBA History System Flag (retrieve payroll deduction, benefit, and accrual history system flag)
Enter an option that identifies how the system retrieves PDBA history during payroll processing. You can set up the system to retrieve employee PDBA history for only the corporate tax ID in which the employee works during the pay period, or you can set up the system to retrieve all PDBA history for an employee, regardless of corporate tax ID.
You might choose to set up the system to retrieve PDBA history across all corporate tax IDs if employees in your organization frequently change companies. Retrieving PDBA history across multiple tax IDs allows the system to collect amounts that remain in arrears under one corporate tax ID if the employee moves to a company with a different corporate tax ID.
You can also determine how the system retrieves PDBA history at the PDBA level. Values are:
0: Use the information from PDBA setup to determine how the system retrieves PDBA history amounts.
1: Retrieve PDBA history only for the corporate tax ID in which the employee worked during the pay period, ignoring the setting at the PDBA level.
2: Retrieve PDBA history across all corporate tax IDs, ignoring the setting at the PDBA level.
3: Retrieve PDBA history for the corporate tax IDs that belong to the same company (that is, the first nine digits of the IDs are the same) in which the employee worked during the pay period, ignoring the setting at the PDBA level. PDBA history of all tax IDs that underwent rate code change (example, from U01 to U02) is retrieved.
Note: This option is applicable for Canadian employees.- Payment Check Date Flag
Enter an option that determines how the system derives payment dates for interim payments. You can set this option to derive the payment date using the master pay cycles, or you can set this option to override the master pay cycle dates using a system-calculated date.
If you choose to override the master pay cycle dates, the system derives the payment date by adding the number of days entered in the Payment Date Offset field on the Interim Header Entry form to the system date. For example, if you use a payment date offset of 4, the system calculates the payment date for all interims entered on Monday as Monday +4, which is Friday. You might use this option if you enter interims continuously throughout a pay period and you want them all to have the same payment date. However, to accomplish this, you must change the payment date offset number daily. Values are:
0: Derive payment date using master pay cycles (default).
1: Derive payment date using system date + payment date offset formula.
- G/L Integration (general ledger integration)
Enter a code that indicates how batches of payroll journals are posted to the general ledger. Values are:
A: Automatic. If batches are in balance and no errors have occurred, the system posts batches automatically during the final update step of the payroll cycle. This value is the default.
M: Manual. Each batch must be posted manually.
N: None. No general ledger interface is available.
T: Time accounting.
- A/P Integration (accounts payable integration)
Enter a value to specify the level of integration. A/P Integration is used to set the level of integration between the JD Edwards EnterpriseOne Payroll and JD Edwards EnterpriseOne Accounts Payable systems. Pro forma vouchers are created during the payroll journal entries step of the payroll cycle. Actual vouchers are created in Accounts Payable during the final update step. Values are:
N: No integration.
0: Create vouchers for both DBAs and taxes that were set up with A/P integration.
1: Create vouchers only for DBAs that were set up with A/P integration.
2: Create vouchers only for taxes that were set up with A/P integration.
- Step Progression Automation
Enter a code that specifies whether you want the system to process job step progression information during payroll cycle processing or whether you want to process the information as a stand-alone feature outside of the payroll cycle. Be aware that processing job step progression during the payroll cycle might significantly increase pay cycle processing time.
Note: This field works in conjunction with the Step Progression Process field on the Company Options form. To process job step progression information, the Step Progression History Update field must be set to 1 or 2. Also, this field is initially populated with the value from the Company Options setup. You can override the value here. However, if you change the value in the Company Options setup, then the system does not change the value in this field.Values are:
Y: Process job step progression information during payroll processing.
N: Process job step progression as a stand-alone feature (default).
- Step Progression Process
Enter a code that specifies whether the system updates Step Progression History tables and the level of detail in which the update occurs. Values are:
1: Update using Union, Job Type, and Job Step.
2: Update using Home Business Unit, Union, Job Type, and Job Step.
N: Do not update Step Progression History tables.
If you select 1, you must set up job step progression parameter tables for each union for which you want to process step progression information. If you select 2, you must set up job step progression parameter tables for each business unit and union combination for which you want to process step progression information. If you select 1 or 2, the companies within your organization are not required to process step progression information. However, if you select N, no companies in your organization can process step progression information.
- Maximum Deferral Rate
Enter the maximum percentage of pre-tax earnings that an employee is allowed to defer to a 401(k) plan. This rate is used in the 415 Nondiscrimination Test.
For example, to enter a rate of 12.75 percent, enter 12.75 in this field.
- Timecard Home Company Flag
Enter a code that determines whether the system overrides the value in the Home Company field on employee timecards with the home company from the Employee Master. Values are:
0: Override the Home Company field on the timecard with the home company from the Employee Master table (F060116). This value is the default.
1: Do not override the Home Company field on the timecard with the home company from the Employee Master table (F060116).
If you choose to override the value on the timecard, the system performs the override at different times depending on how the timecard is entered into the system. These examples illustrate when the override would occur if you set this option to 0 and entered a timecard with a home company that is different than the home company in the Employee Master:
If you enter a regular timecard, the system overrides the home company when the timecard is processed in pre-payroll.
If you enter a timecard using the Time Entry Interim Generator, the system overrides the home company when you exit the row in the detail area of the time entry form.
If you enter timecards for interim payments using the Interim Payment Workbench and if the Company field on the Interim Entry form is blank, then the system overrides the home company when you click OK during interim entry.
Note: The system never overrides the home company on timecards that are entered using the Interim Entry form if a value appears in the Company if Different than Home Company field that is also on the Interim Entry form. The Company if Different than Home Company field is intended to be used as an override to this functionality. The system does not consider the value in this field when determining whether to override the home company for the interim payment.Caution: If your organization has multiple home companies with the same corporate tax ID, and those companies use the same bank account for payroll payments, set this option to 0. Setting this option to 1 might cause undesirable results.- Process Employees by Business Unit
Enter a value that specifies how the system processes information. Values are:
1: Process employees by business unit (as set up in Auto Deposit Instructions for Business Units program (P07236)). This option should be used if different auto deposit information per business unit is needed.
0: Process employees as one large group regardless of the business unit they work in. If you enter 0, auto deposit information from business unit 1 is used. You must set up auto deposit information for business unit 1 in the Auto Deposit Instructions for Business Units program (P07236).
- Bypass Voids with Special Taxes
Enter 1 if you want to bypass voided payments if those payments contain special taxes. Leave this option blank if you want to process voided payments if those payments contain special taxes.