Oracle Payroll generates elements when you initiate earnings and deductions. Using the Element window, you can modify some of the processing information for these elements.
Do not change the following options:
Processing type (recurring or nonrecurring)
Indirect results only
The Additional Entry Allowed rule has no applicability for North American installations. It is available for use at sites outside North America, and benefit classifications do not apply in Canada.
In the Element window, query the generated element you are modifying.
To control the processing of entries to the element after employee termination, you can select an alternative termination rule.
If the termination rule is Actual Termination, and the element's processing type is recurring, entries to the element close down on the employee's termination date. If the element's processing type is nonrecurring, entries close down either on the last date of the pay period in which the employee leaves or on the date the assignment ends (the final process date) if this is earlier.
If the termination rule is Final Close, entries to the element stay open beyond the actual termination date. This makes it possible to pay bonuses, severance pay, and so on, and to make year end adjustments after the employee's actual termination date.
Note: Recurring elements with the Final Close rule only process in runs after the Last Standard Process Date if there is also a nonrecurring entry to process in that run.
If the termination rule is Last Standard Process, entries to the element are not processed after the Last Standard Process date. The Last Standard Process date defaults to the last day of the pay period in which the employee is terminated, but you can set it to a later period when you terminate an employee. This is the appropriate rule for many recurring earnings types.
You can prevent the element from accepting any new entries, either temporarily or permanently, as of a certain date. Set the effective date to the date from which you want to close down the element, and check Closed for Entry. This does not affect any existing entries.
Note: Use the Closed for Entry feature with caution. When you perform certain important tasks in Oracle HRMS, the system may automatically create or delete element entries. These tasks include hiring and terminating people, and updating assignments. Therefore, if you check Closed for Entry for an element, this might prevent users terminating employees and updating assignments. If there are standard links for the element, it will also prevent users hiring people who are eligible for the element.
You can control an element's availability for processing in runs by selecting or deselecting the Process in Run box.
To make third party payments from an earnings or deduction element, check the Third Party Payment box.
If you want to determine the order in which the element processes within its classification range, you can change the default priority number appearing in the Priority field. The payroll run processes elements with lower priority numbers first.
You can select a skip rule for the element in the Skip Rule field.
Define the balances required to hold amounts of the local currencies if you set up earnings types to produce payments in local currencies (instead of the ledger currency of the Business Group). The system does not generate these balances.
To make entries for the element in a currency other than the Business Group's ledger currency, select the currency in the Currency Input field.
For example, if the element represents a housing allowance of 500 pounds sterling paid monthly to a North American employee working in the UK, you select GBP as the input currency.
To produce run results in a currency other than the Business Group's ledger currency, select the currency in the Currency Output field.
If there is a minimum age for employees to receive the element, enter it in the Age field.
If employees must complete a minimum length of service before receiving the element, enter a number in the Length of Service field and select a unit of measure (such as months or years) in the Units field.
To automatically enter the element and its default input values for all eligible employees, check the Standard box.
You cannot check this box for nonrecurring elements, or for those with the rule Multiple Entries Allowed.
Note: The qualifying conditions and Standard check box provide defaults for the element. You can override them for particular groupings of employees when you build links for the element.
Pre-tax deductions are calculated iteratively to ensure that the maximum amount is deducted while ensuring that taxes and garnishments are paid in full, and net pay is zero or a positive amount. If multiple pre-tax elements are given to an employee, the element with the lowest processing priority (that is, the highest priority number) will be reduced first when there are insufficient earnings. You can also set an iterative priority.
Attention: Iterative priority numbers must be in the reverse sequence of the processing priority numbers. This means that the element that is processed first is reduced last.
Choose the Advanced tab.
Enter a value in the Iterative Priority field.
The element with the lowest iterative priority number is reduced first. If this deduction is reduced to zero and net pay is still insufficient to cover taxes and garnishments, the element with the next lowest priority number is reduced, and so on.
Note: Do not choose the Exclude Balances button for pre-tax deductions. You use the Exclude Balances window when you are defining net-to-gross earnings; it is not relevant for pre-tax deductions.