This chapter provides an overview of off-cycle functionality and discusses how to:
Make corrections.
Make additional payments.
Enter advances.
Record manual payments.
See Also
This section discusses:
The off-cycle process.
Types of off-cycle transactions.
Delivered off-cycle processing elements.
Off-cycle processing refers to processing payments and making corrections to payroll results outside of the normal payroll schedule. Off-cycle transactions are usually made to correct prior payments, to process late notification of a new hire, to make early termination payments that can't wait until the next scheduled payroll, to process unscheduled payments such as bonus or expense runs, or to process advance holiday pay
The four types of off-cycle transactions are:
Corrections
Corrections enable you to correct results of any finalized payroll. Examples include reversing an overpayment, processing late notification of a new hire, or correcting pay (for example, following late notification of a termination).
Additional payments
Additional payments enables you to enter one-time payments that fall outside the normal payroll process. Examples include one time bonuses or expense reimbursement.
Advances
Advances enables you to pay payees before their normally scheduled pay run. Examples include advance holiday pay or salary due on termination.
Manual payments
Manual payments enable you to enter payments that you have calculated and paid outside of the payroll system. Manual payments are unlikely to be required in the U.K. An example when a manual payment may be used is to record a payment to a terminated employee that is in cash.
Global Payroll for the U.K. delivers this processing structure for off-cycle processing:
The GBR PR OFFCYCLE process list.
The GBRRTOFF run type.
The GBR EG TAX NI LES limited element set.
Use this limited element set with manual payments, additional payments, and corrections to limit the elements resolved during the off-cycle process. GBR EG TAX NI LES contains the deductions for tax and NI.
Global Payroll for the U.K. also delivers an off-cycle configuration for the U.K. that provides default settings when you enter an off-cycle request. Refer to the PeopleSoft Enterprise Global Payroll 9.1 PeopleBook for details of Off-Cycle Configuration page.
See Also
Configuring Off Cycle Transactions
This section discusses:
Using corrections in the U.K.
Entering corrections.
Corrections enable you to correct the results of a finalized payroll before the next scheduled payroll run. Essentially, you use corrections to make changes that would normally be corrected by retroactivity processing in the next payroll.
Here are some examples when you may use corrections in the U.K:
Late notification of new employees.
Use corrections to pay employees who were hired in the previous period but were not processed in payroll.
Pay changes.
If an employee has a retrospective change in salary or other earnings, you can use corrections to calculate the changes and pay the employee before the next scheduled payroll run.
Late notification of terminations.
Use corrections to correct the payroll results of an employee who left employment in the previous period but was incorrectly processed as an active employee.
Retrospective NI category code changes.
Use corrections to recalculate National Insurance when an employee's NI category is retrospectively changed.
Retrospective change of hire date.
Use corrections to recalculate employees' pay and correct accumulators when an employee's pay has been processed using an incorrect hire, rehire, or transfer date.
Note. Corrections are only processed if retro triggers already exist.
See Also
Reviewing Triggers for the U.K.
Defining Retroactive Processing
Enter the correction details on the Correction Request Detail page. The two fields in the Method of Correction group box define how the correction works:
Type of Correction |
Select Replacement or Forced Reversal. A replacement is used when a calculation in the finalized payroll was incorrect, for example if a payee's overtime was incorrect. A forced reversal is used to correct payments made in error. |
Retro Method |
Select one of these values: Use Existing Retro Rules: To use the default retroactive method determined by the triggers generated. Forced Corrective: To use the corrective retroactive method. |
This table explains the four types of corrections that you can create and how these are used in the U.K:
Type of Correction |
Retro Method |
Description |
Replacement |
Use Existing Retro Rules |
This is a replacement using the retroactive method determined by the generated triggers. This is the most common type of correction you will make. |
Replacement |
Forced Corrective |
A replacement using the corrective retroactive method. No elements are forwarded and any deltas must be managed in another way. |
Forced Reversal |
Use Existing Retro Rules |
This is a reversal using the retroactive method determined by the triggers, which means that all elements are recalculated and forwarded and the retro process override list is ignored. |
Forced Reversal |
Forced Corrective |
A reversal using the corrective retroactive method. The original calculation is reversed and there are no elements forwarded. |
Example: Late Hire
Consider the example of an employee who was hired in a finalized period, but the employee was not processed. How you enter a correction for this employee depends on the timing of the correction:
If the accounting period is closed and the HM Revenue and Customs (HMRC) payment has been completed, select Replacement in the Type of Correction field and Use Existing Retro Rules in the Retro Method field.
For this type of correction, the Target Period is the next open period. The retro method processed depends on the retro method linked to the generated trigger.
If the hire occurred within the most recently processed period, the accounting period is not closed and the HMRC payment has not been made, select Replacement in the Type of Correction field and Forced Corrective in the Retro Method field.
Using these settings, the hire is processed within the period in which the hire actually occurred. Therefore, the Target Period is the most recently processed period.
Example: Change in Pay
In the example of a change to pay, there are three possibilities:
The employee is owed money.
Select Replacement in the Type of Correction field and Use Existing Retro Rules in the Retro Method field to use the retro method determined by the generated trigger. Select the next open period as the Target Period.
The employee was overpaid and he or she will be processed in the next scheduled payroll.
In this situation, we recommend that you do not use a correction, but let the retro calculation deduct the overpayment in the next regular payroll run. If overpayment is processed using off-cycle processing, the negative pay is forwarded to the next target period. However, because it is an off-cycle process, there is no positive pay from which to deduct the overpayment. The negative pay will then have to be managed, possibly as a deduction from the next regular payroll run.
The employee was overpaid and he or she will not be processed in the next scheduled payroll.
In this example, select Replacement in the Type of Correction field and either Use Existing Retro Rules or Forced Corrective in the Retro Method field. However, the result of the correction will be a negative net pay and you will need to determine how to collect the overpayment.
Example: Late Termination
Consider the example of an employee terminated in the previous (finalized) period who was processed as an active employee. You process this as a reversal as follows:
If the employee has already been paid (bank transfer is completed), select Forced Reversal in the Type of Correction field and Use Existing Retro Rules in the Retro Method field.
The Target Period is the next open period. This correction sets all results for the finalized period to zero and forwards the negative pay to the next open period.
If the employee has not been paid (bank transfer stopped), select Forced Reversal in the Type of Correction field and Forced Corrective in the Retro Method field.
The Target Period is the previous finalized period. In this case, the correction sets all results for the finalized period to zero and there are no elements forwarded.
This section discusses:
Using additional payments in the U.K.
Entering additional payments.
Additional payments are one-time payments such as a bonus payment or for reimbursement of expenses. Do not use additional payments for bonus payments that are paid at regular intervals; process regular payments in on-cycle processes.
Enter information about the additional payment on the Additional Payment Detail page:
Restrict element resolution to those elements with positive input, or by using a limited element set, depending on the payment type.
In the Element Selection group box, select Limited Element Set or Elements with Positive Input to restrict element resolution. If you select Elements with Positive Input, the system resolves only those elements for which you enter positive input. This means that tax and national insurance are not calculated. Typically, you would use this option for an expense payment that does not require tax and national insurance calculations.
If you select Limited Element Set, the system resolves the elements included in the limited element set in addition to those entered using positive input. Typically, you would use a limited element set when the payment is subject to tax and national insurance. Global Payroll for the U.K. delivers the limited element set GBR EG TAX NI LES for this purpose.
Enter supporting element overrides for the variables TAX VR PERIOD and TAX VR BGN YR.
On the Additional Payment Detail page, click the Supporting Element Overrides link to display the Payee Calendar SOVR page. Add the variables and assign the appropriate values on this page. The TAX VR PERIOD identifies the tax period and TAX VR BGN YR identifies the tax year in which the payment is made.
Additional payments are discussed in detail in the PeopleSoft Enterprise Global Payroll 9.1 PeopleBook.
See Also
This section discusses:
Using advances in the U.K.
Processing advances.
Advances provide a way to process payments before the next scheduled payroll run. Typically, you would use advances to:
Pay terminated employees before the normal payroll is run.
Pay holiday advances.
When you run the next scheduled payroll, employees who receive advances are not identified.
Enter the advance details on the Advance Request Detail page. Select the next scheduled (on-cycle) calendar group in the Calendar Group field.
We recommend that you process advances for whole pay periods only.
When you later process the next on-cycle calendar, the payroll process does not identify the employees whose pay was advanced.
Advances are discussed in detail in the PeopleSoft Enterprise Global Payroll 9.1 PeopleBook.
See Also
This section discusses:
Using manual payments in the U.K.
Entering manual payments.
Manual payments provide a way to record one-time payments that were calculated and paid outside of the payroll system. You should not use manual payments for regular payments because the payee would be identified for the payment during the normal on-cycle payroll process.
Manual payments are unlikely to be required in the U.K. In general, you should use additional payments to process payments that were paid outside of the payroll system and override the payment method to ensure that the payment is not processed by the banking process.
To enter a manual payment:
Calculate the employee's gross and net pay before you enter the manual payment.
When you click the Validate button on the Manual Payment Detail page, the system calculates the gross and net pay based on the earnings and deductions entered. If it does not match the values you have entered, the payment can't be processed.
Use a limited element set to restrict the elements that are resolved.
In the Element Selection group box select Limited Element Set and select the element set in the Limited Element Set field. Global Payroll for the U.K. delivers the GBR EG TAX NI LES for this purpose.
Enter supporting element overrides for the variables TAX VR PERIOD and TAX VR BGN YR.
On the Manual Payment Detail page, click the Supporting Element Overrides - Payment Level link to display the Payee Calendar SOVR page. Add the variables and assign the appropriate values on this page. The TAX VR PERIOD identifies the tax period and TAX VR BGN YR identifies the tax year that apply for the payment.
See Also